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

@thisismanta/semantic-version

v11.3.0

Published

The following commands respect [`packageManager`](https://github.com/nodejs/corepack?tab=readme-ov-file#when-authoring-packages) field first then [`devEngines.packageManager.name`](https://docs.npmjs.com/cli/v10/configuring-npm/package-json#devengines) in

Readme

The following commands respect packageManager field first then devEngines.packageManager.name in package.json, but fallback to npm if none is specified.


npx lint-commit-message <path>

The <path> must point to a text file containing commit message that complies with the following pattern:

<type>[!]: <subject>

Where

  • <type> can be either feat, fix, build or chore.
  • ! indicates that the commit contains a breaking change.
  • <subject> is the actual commit message where the first word must be written in lower cases.

Usage example with lefthook:

# lefthook.yml
commit-msg:
  commands:
    lint:
      run: npx lint-commit-message {1}

npx make-next-release [--dry-run]

This command is supposed to be run on GitHub Actions. It will run npm version <new-version>, which <new-version> is automatically derived from your commit messages according to the table below and then it creates a new entry on GitHub Releases.

| Commit message type | Trigger | | ------------------- | -------------------------- | | ! | npm version major | | feat | npm version minor | | fix or build | npm version patch | | Others | Does not run npm version |

// package.json
{
	"scripts": {
		"preversion": "npm run test",
		"version": "npm run build && git add lib",
		"postversion": "npm publish"
	}
}

By supplying --dry-run argument, it uses git push --dry-run, npm version --ignore-scripts and creates a new draft GitHub Release entry instead, which you may want to manually delete the draft release afterward.

# .github/workflows/push.yml
on:
   push:
     branches: [master]

permissions:
  contents: write # Grant Git push and GitHub Release write access to GITHUB_TOKEN

 jobs:
   release:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@v6
         with:
           fetch-depth: 0 # Ensure entire Git history and Git tags are accessible

       - uses: actions/setup-node@v6
         with:
           node-version: 22

       - run: npm install @thisismanta/semantic-version@11

       - run: npx make-next-release
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}