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

repoviz

v0.1.0

Published

Visualize a git repo's history over time with pretty charts

Readme

repoviz

Visualize a git repo's history over time with pretty charts.

npx repoviz           # run in the current git repo
npx repoviz /path     # or point at any local repo

It walks the main branch (default: last year, one week per sample), snapshots line counts and commit activity, then opens a local web UI.

Flags

  • --months <n> — how far back to walk (default 12)
  • --bucket-days <n> — days aggregated per bar (default 7; try 1 for per-day granularity)
  • --port <n> — server port (default random)
  • --no-open — don't auto-open the browser
  • --keep-workspace — leave the temp clone under /tmp for debugging

What gets measured

  • Commits per day on the main branch — total and by the current git user (git config user.email)
  • Lines of source code (.ts .tsx .js .jsx .py .rb .go .rs ...)
  • Lines of config (.json .yaml .toml ...)
  • Lines of docs (.md .mdx .rst ...)

Files ignored by the repo's own .gitignore are automatically excluded — repoviz works off git ls-files.

How it works

  1. git clone --local the target into /tmp/repoviz-* (hardlinks — fast and safe; your working tree is never touched).
  2. For each day in the window, find the last main-branch commit ≤ end-of-day, check it out, count tracked lines by category.
  3. Commit counts come from a single git log pass.
  4. Serve the prebuilt React UI locally and stream the report to it.