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

corgit

v0.1.0

Published

Supercharge your git processes

Downloads

20

Readme

corgit

Prerequisits

Create a file in ~/.corgit/config.json with the following content:

{
  "github": {
    "pat": "9b9c9....54234cf"
  }
}

The pat is your github personnal access token. It is required to generate the changelog using github linked issue's title.

Usage

Install with npm i -g corgit or yarn global add corgit

cg [command]

cg bump generates a changelog & bump the version

Corgit bump goes through your commit history from the latest known version (that is on your package.json file),
looks up the kind of commit this is (feature / chore / fix / ...) and bumps the version accordingly (breaking => major, feature => minor, the rest => patch).

Corgit bump also generates a changelog like so:

# Version [major]

## v[major].[minor]

### [major].[minor].[patch]         //- The most recent is on top

#### Significant changes

- **[feat]**
  - [issue title] #[issue id]
  ...

#### Commits

- [link to commit]: message (@author)

Note:

  • Significant changes are classed as follow: feat > fix > refac > test > style > chore > doc > misc (the latest being used when we failed to identify the commit kinds)
  • Significant changes are based on the commit you made, in criticity order. That is, if you made a feat commit then a style one, the issue title will be in the feat section
  • Significant changes takes the title of the github issue, so make sure that your commit is in a pull request and that the pull request has a linked issue :)