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

gitpaper

v0.0.2

Published

📰 The first ever generator of non-boring and actually detailed release notes

Readme

gitpaper

The first ever generator of non-boring and actually detailed release notes

[!NOTE] The project is still under development and can already be used in some real-world cases, but the settings/principle of operation may change without notice before the first major version is released, so don't be upset if something breaks.

🛠️ Usage

npx gitpaper

gitpaper will automatically generate release notes starting from the last release to the last commit by default.

Here is an example of the generated Markdown:

   🚀 Enhancements

  • Add support for terminal hyperlinks  -  by Dev Khalid (7e21c)

Now terminal links are clickable in supported environments, making logs and CLI output more interactive (and less copy-pasty).

   🐛 Fixes

  • Resolve crash when reading empty config files  -  by Mei-Ling Zhou (c1d45)

Prevented an edge case crash when config files exist but contain... absolutely nothing. Now it fails gracefully and logs a warning.


The main feature is extended descriptions of changes in release notes, which makes it much clearer for your users

To have these descriptions appear in your release notes, you need to insert a special ::: changelog section in the extended commit description:

Multiline strings were inconsistently parsed when using backticks inside templates.

Tested on macOS, Ubuntu, and Windows 11 (PowerShell and Git Bash).

::: changelog
Enhanced the parser to correctly capture multiline strings, especially those using backticks.
No more chopped-off input on line breaks in the final output.
:::

Fixes #123

Co-authored-by: Chloe Nakamura <[email protected]>
Co-authored-by: Viktor Petrov <[email protected]>

So you decide what exactly should be written in the release notes.

❤️ Support

If you like this project, consider supporting it by starring ⭐ it on GitHub, sharing it with your friends, or buying me a coffee ☕

📜 License

MIT License © 2025-present Yurii Bogdan

👨‍🏭 Contributors

Thank you to everyone who helped with the project!

Contributors