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

@kors/generate-changelog

v1.0.4

Published

Generate a changelog json from a git commit history

Readme

Supported Platforms

Generate structured changelog JSON from git commit history. Works with local repos and remote GitHub repositories.

Install

npm install @kors/generate-changelog

Usage

CLI

# Generate from local repo and write to changelog.json
npx @kors/generate-changelog --write

# Generate from a remote GitHub repo
npx @kors/generate-changelog --owner="StefKors" --repo="generate-changelog"

# Remote repo with a GitHub token (private repos, or to avoid unauthenticated rate limits)
GITHUB_TOKEN=ghp_xxx npx @kors/generate-changelog --owner="StefKors" --repo="my-private-repo"
# or pass the token explicitly
npx @kors/generate-changelog --owner="StefKors" --repo="my-private-repo" --token="ghp_xxx"

Programmatic

import { generateChangelog } from "@kors/generate-changelog"

const changelog = await generateChangelog({ write: true })
// or from a remote repo (optional githubToken for private repos / rate limits)
const remote = await generateChangelog({
  owner: "StefKors",
  repo: "generate-changelog",
  githubToken: process.env["GITHUB_TOKEN"],
})

CLI Options

| Flag | Short | Description | |------|-------|-------------| | --write | -w | Write output to changelog.json | | --owner | -o | GitHub repo owner (use with --repo) | | --repo | -r | GitHub repo name (use with --owner) | | --token | -t | GitHub token (optional; also reads GITHUB_TOKEN or GH_TOKEN if unset) | | --version | | Print current version | | --help | | Print help message |

Output Format

{
  "releases": {
    "1.2.0": [
      { "type": "Added", "message": "New feature description" },
      { "type": "Fixed", "message": "Bug fix description" }
    ],
    "1.1.0": [
      { "type": "Improved", "message": "Performance improvement" }
    ]
  }
}

Change types are auto-detected from commit messages: Added, Fixed, Improved, Removed.

GitHub authentication

When using --owner and --repo, the GitHub REST API is called without a token by default. That works for public repositories but is subject to lower rate limits. For private repositories, or to use authenticated rate limits, provide a token in either of these ways:

  • Environment variable: set GITHUB_TOKEN (or GH_TOKEN) before running the CLI. The CLI reads GITHUB_TOKEN automatically.
  • CLI flag: --token / -t overrides the environment when both are set.

Create a token under GitHub → Settings → Developer settings → Personal access tokens. The token needs read access to repository contents (for private repos, use a classic token with repo scope, or a fine-grained token with Contents read access).

Features

  • Parses git tags to group commits by version
  • Auto-classifies changes by type from commit messages
  • Filters out merge commits and version bumps
  • Supports local git repos and remote GitHub repos via Octokit
  • Outputs structured JSON for use in release notes, changelogs, or UIs

License

MIT