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

@korkor/compare-spec-up-t-repos

v1.0.16

Published

This is a local-machine command line tool. People who prepare the comparison of two Spec-Up-T-based glossaries run this tool to see which terms match the two glossaries. The reason why people compare could be: - inventory of shared understanding, scope, o

Readme

Compare two Spec-Up-T repositories

This is a local-machine command line tool. People who prepare the comparison of two Spec-Up-T-based glossaries run this tool to see which terms match the two glossaries. The reason why people compare could be:

  • inventory of shared understanding, scope, or mental model
  • (partly) replace their definitions with references to the companion glossary Read below how to make a comparison that results in an index.html file with the results of an exact match (no fuzzy search possible yet)

Instructions

  • Go to the URL of the first repository in your browser and browse to the terms and definitions directory

  • Copy the URL of the directory where the terms and definitions are stored (usually /specs/terms-and-definitions) and save it somewhere

  • Do the same for the second repository

  • In your command line run:

npx @korkor/compare-spec-up-t-repos
  • Enter GitHub Personal Access Token (optional for public repositories, but recommended to avoid rate limits)
  • Enter a name for the output directory (you are free to choose any name)
  • Enter a name for the first repository (you are free to choose any name)
  • Enter the URL for the first repository
  • Enter a name for the second repository (you are free to choose any name)
  • Wait for the script to finish

Results

You now have a directory with the name you chose earlier. Inside the directory, you will find the downloaded terms and definitions from the two repositories. You will also find json files with the terms that are in both repositories and the terms that are in only one of the repositories.

In the root of the directory, you will find an index-<name of directory>.html file that you can open in your browser to see the results.