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

envdiffer

v0.1.0

Published

Solve "works on my machine" — snapshot and diff dev environments across machines.

Readme

envdiff

CI

Solve "works on my machine" in 30 seconds.

Snapshot a dev environment on two machines, diff them, and see the differences ranked by how likely they are to be the culprit — tool versions first, env noise last. Secrets are masked before anything touches disk.

envdiff compare demo

Why

"Works on my machine" is never magic. It's a different Node version, a missing tool on PATH, or one env var. Finding which one by hand takes an hour. envdiff finds it in seconds.

Install

npx envdiff-cli snapshot -o mine.json

No install needed. (Or npm i -g envdiff-cli.)

Usage

# On your machine (where it works)
envdiff snapshot -o mine.json

# On the machine where it breaks (send them the one-liner)
npx envdiff-cli snapshot -o theirs.json

# Anywhere — compare
envdiff compare mine.json theirs.json

Output:

7 difference(s) — most suspicious first
left = merts-laptop, right = ci-runner

[tools]
  ~ node: v24.18.0 → v18.19.0
  - docker (only left)
[system]
  ~ platform: win32 → linux
[env]
  ~ NODE_ENV: development → production
...

Exit code is 1 when differences exist (diff convention), so it drops into scripts and CI.

"Why does it only break in CI?"

envdiff init-ci

Writes .github/workflows/envdiff.yml — every CI run uploads a snapshot of the runner's environment as an artifact. Download it and diff against your machine:

gh run download -n envdiff-snapshot
envdiff compare mine.json ci-snapshot.json

What gets captured

| Section | Contents | |---|---| | system | OS, arch, CPU count, RAM, shell, locale, timezone | | tools | Versions of 24 common dev tools (node, python, go, docker, git, ...) | | env | Environment variables — values matching secret patterns are masked | | path | Deduplicated PATH entries |

Security

Env values are masked by name pattern (*KEY*, *TOKEN*, *SECRET*, ...) and by value shape (long high-entropy strings), before the snapshot is written. Review the JSON before sharing anyway — it's your environment.

Roadmap

  • [x] init-ci: snapshot your CI runner via GitHub Actions artifact
  • [ ] Custom tool probes via .envdiffrc
  • [x] envdiff compare --json machine-readable output

License

MIT