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

repo-check

v2.0.0

Published

Maintain order in repositories chaos

Readme

Repo Checker

Project license Code Climate maintainability npm version npm monthly downloads Visitors

Package Quality Publish size Install size

logo

Cli mode

Run repo-check :

demo

UI mode

Run repo-check ui :

demo-ui

Usage

Run it in a folder of projects to check them all against your GitHub account, or inside one project to check only that one. It needs git and an authenticated GitHub CLI (gh auth login), and the report changes nothing unless you add --fix, which applies the file fixes (a file you already changed gets the fix merged into your changes, and nothing is committed, git diff shows it). repo-check ui can fix things too, always after a confirmation that says what will happen.

npx repo-check

From a clone of this repository: pnpm install then pnpm start --target=~/Projects. To look at the dashboard without your own repos, pnpm run build then pnpm demo starts it on a fake account (see demo/README.md).

npx repo-check ui (or pnpm start:ui from a clone) starts a local server on 127.0.0.1:4747 instead. Open the printed URL: the project list fills in as the scan streams, with filters, summary tiles and a Rescan button, and a click on a project opens its findings and git state, refreshed live while the page is open. Run inside one project, it opens straight on that project. Every action runs after a confirmation that says what will happen, and the server proves again, with a fresh fetch, that it is still safe:

  • fix the files the checks complain about (a diff per file to confirm, a file you have already changed gets the fix merged into your changes and stays out of the commit), fix the git issues of a clone, check out the default branch
  • clone a repo you do not have yet, open a project in VS Code, sync its description and homepage with GitHub, set the GitHub settings the checks want
  • archive or unarchive a repo, save the unpushed work of an archived repo (unarchive, push, archive again), discard the unsaved work of an archived clone
  • delete the local clone of an archived repo that holds nothing that is not on GitHub, the local branches of a clone, a fork that is provably pristine, or a whole project (its GitHub repo and its clone). The GitHub deletes need the delete_repo scope: gh auth refresh -s delete_repo
  • ignore a check on a project for 24 hours, or update a project with Claude (/update-project)

The report groups the findings by severity (errors, warnings, info) and ends with a summary line. It exits with an error code when a finding is an error. Every check is listed in docs/checks.md.

Options

  • --target=path folder to scan, the current one by default
  • --owner=name GitHub account to compare with, the gh login by default
  • --fix apply the file fixes, the same as in the ui: a file you already changed gets the fix merged into your changes, and nothing is committed
  • --nitpick also run the nitpick checks (small details like outdated-minor-dependency and lighthouse-budget), the ui has a Nitpick mode toggle in its Actions menu
  • --no-fetch skip git fetch and the automatic fast forward that follows it, faster but unpushed work is measured against stale remote refs
  • --verbose also list every passed and skipped check, per project
  • --port=number port of the ui server, 4747 by default
  • --no-open do not open the browser (ui only)

Configuration

A .repo-checker.json file in a project tells repo-check what it cannot detect, for example:

{
  "license": "MIT",
  "maxSizeKo": 100,
  "webUrl": "https://my-website.com"
}

webUrl is the url of the deployed website or web app. It is not the homepage of the package.json: that one is the homepage of the source code, so it must be the url of the GitHub repo (the package-homepage check fills it that way). The homepage shown on the GitHub repo is the deployed website, and the "Sync infos" action of the UI keeps it in line with webUrl: it shows what the project and GitHub say side by side, lets you edit the description and the homepage, then writes the description in the package.json (and on GitHub) and the homepage as webUrl (and on GitHub). The homepage of the package.json is never changed by it.

themeColor is the color of the project, like "#024eb8". Without it, repo-check reads it from the web manifest, then the theme-color meta tag of a page, then the VS Code title bar, and never invents one. It then checks that the manifest theme_color, the meta tag and the VS Code colors follow it, with a darker shade for the manifest background_color and the VS Code activity bar.

For autocompletion in your editor, point it to the schema shipped with the package:

{
  "$schema": "./node_modules/repo-check/schema.json"
}

Thanks

  • Boxy Svg : simple & effective svg editor
  • Bun : super fast runtime for JavaScript and TypeScript
  • pnpm : fast, disk space efficient package manager
  • Github : for all their great work year after year, pushing OSS forward
  • HeroUI : beautiful and accessible React components
  • Hono : small and fast web framework, the server of the dashboard
  • Knip : super tool to find & fix problems
  • Oxc : a lovely super-fast collection of JavaScript tools written in Rust
  • React : great library for web and native user interfaces
  • Repo-checker : oxlint covers the /src code and this tool the rest ^^
  • Shields.io : for the nice badges on top of this readme
  • Shuutils : collection of pure JS utils
  • Svg Omg : the great king of svg file size reduction
  • TailwindCss : awesome lib to produce maintainable style
  • Turborepo : runs the scripts in parallel and caches them
  • V8 : simple & effective cli for code coverage
  • Vite : super fast frontend tooling
  • Vitest : super fast vite-native testing framework