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

@hsorby/changelog

v3.0.2

Published

Generate a changelog for pull requests referencing issues in a repo workflow.

Readme

@hsorby/changelog

A streamlined changelog generator that maps GitHub Issue Types to categorized release notes. Unlike standard generators that rely on PR labels, this tool looks at the issues linked to your Pull Requests to determine where changes belong.

Usage

# Run via npx
npx @hsorby/changelog --from v1.0.0

# Or via yarn
yarn lerna-changelog --from v1.0.0

How it works

  1. Finds Commits: Identifies all commits between your specified tags on the target ref, default main.
  2. Links PRs: Maps those commits back to their parent Pull Requests.
  3. Inspects Issues: Looks at the Issues linked to those PRs.
  4. Categorizes: Matches the issueType of the linked issue against your configuration to place the change in the correct section (e.g., Bug Fix, Feature).

Configuration

Add a changelog key to your package.json. Even though the key is still called labels, it now maps to the Type field found in your GitHub Issues (this should change in the future).

{
  "changelog": {
    "repo": "hsorby/my-project",
    "labels": {
      "feature": "🚀 New Features",
      "bug": "🐛 Bug Fixes",
      "documentation": "📝 Documentation",
      "internal": "🏠 Internal Task"
    },
    "ignoreCommitters": [
      "dependabot",
      "github-actions"
    ]
  }
}

The repo key is optional, the package will try and determine the repository from the repo key in the package.json itself.

Options

| Option | Description | | --- | --- | | repo | Your org/repo (Inferred from package.json if omitted). | | nextVersion | The header for the latest changes (e.g., Latest Changes). | | labels | Maps Issue Types to Section Headers. | | ignoreCommitters | Array of usernames to exclude from the contributor list. |


Enhanced Features

📸 Clean Contributor Grids

No more messy inline lists. This fork renders a clean, centered grid of contributors with high-resolution avatars:

| | | | --- | --- | | @hsorby | @octocat |

🌳 Branch Awareness

The generator uses a target reference to ensure that only commits belonging to your primary branch are included, preventing "noise" from unmerged or side-feature branches.

⚡ Smart Caching

Includes an internal caching layer to prevent redundant GitHub API calls when multiple commits belong to the same Pull Request.


GitHub Token

To avoid API rate limiting, export a personal access token:

export GITHUB_AUTH="your_token_here"

Requires public_repo scope for public repositories.


License

MIT ©