npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

open-checklists

v0.2.1

Published

Sharable checklist format

Readme

Open Checklists

So the idea is very simple - we often use checklists, almost everywhere, think about it:

  • Shopping list
  • PR checklist
  • New employee onboarding
  • To-do lists
  • ... and many more

Inspired by OpenStories, I decided to create something with that - OpenChecklists.

Spec

Here's a full example of a checklist in Open Checklists format:

{
  "title": "How to get your first task in our project",
  "description": "This list describes how you can start working on our project",
  "created_at": "2025-07-17",
  "authors": [
    {
      "name": "John Doe",
      "url": "mailto:[email protected]",
      "avatar": "https://example.com/avatar/johndoe.png"
    }
  ],
  "items": [
    {
      "id": "1",
      "title": "Register on github",
      "content_text": "Register on https://github.com",
      "blocking": true
    },
    {
      "id": "2",
      "title": "Pick a task from the onboarding category",
      "content_text": "Open github issues board and inspect issues from the \"onboarding\" category.\nPick the one you want to work on and leave a comment with \"I want to work on it\" text.",
      "blocking": true
    },
    {
      "id": "3",
      "title": "Create pull request",
      "content_text": "Create a pull request. We attached a small video instruction on how to create pull requests",
      "blocking": true,
      "attachments": [
        {
          "url": "https://example.com/video/pullrequest.mp4",
          "mime_type": "video/mp4",
          "alt": "How to create pull requests"
        }
      ]
    }
  ]
}

And here's a minimal version:

{
  "items": [
    {
      "id": "1",
      "title": "Buy milk"
    },
    {
      "id": "2",
      "title": "Buy bread"
    },
    {
      "id": "3",
      "title": "Buy juice"
    }
  ]
}

Extensions

Clients can extend open checklists object. All additional fields (even nested ones) should start from the "_" symbol, for example:

{
  "_id": "local_id_1",
  "items": [
    {
      "id": "1",
      "title": "Buy milk"
    },
    {
      "id": "2",
      "title": "Buy bread"
    },
    {
      "id": "3",
      "title": "Buy juice",
      "_meta": {
        "_original_url": "https://example.com"
      }
    }
  ]
}