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

create-issue-status

v0.1.3

Published

Create new issue-status projects with scaffolding templates

Readme

create-issue-status

Scaffolding your first issue status page

With NPM:

$ npm create issue-status@latest

With Yarn:

$ yarn create issue-status

With PNPM:

$ pnpm create issue-status

With Bun:

$ bun create issue-status

Then follow the prompts!

You can also directly specify the project name and the template you want to use via additional command line options. For example, to scaffold an Issue Status project, run:

# npm 7+, extra double-dash is needed:
npm create issue-status@latest my-status-page -- --template static

# yarn
yarn create issue-status my-status-page --template static

# pnpm
pnpm create issue-status my-status-page --template static

# bun
bun create issue-status my-status-page --template static

Currently supported template presets include:

  • static - Simple static data (good for getting started)
  • github - Use GitHub Issues as data source
  • custom - Implement your own provider

Generated Project Structure

my-status-page/
├── issue-status.config.ts  # Your configuration
├── package.json           # Dependencies and scripts
└── node_modules/          # Installed dependencies

Available Scripts

In the generated project:

  • npm run dev - Start development server
  • npm run build - Build for production
  • npm run preview - Preview production build

Provider Types

Static Provider

Perfect for getting started. Uses static data defined in your config file.

GitHub Provider

Uses GitHub Issues as your data source. Requires:

  • Issues labeled with issue status + component for components
  • Issues labeled with issue status + incident for incidents
  • Status labels: operational, degraded performance, partial outage, major outage

Custom Provider

Implement your own data source by completing the provider interface in the generated config file.