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-scanner

v0.1.0

Published

Fast, local git repo health scanner — scores your repo across docs, security, quality, and structure

Readme

repo-health

Fast, local git repo health scanner.
Scans any repository and gives you a score + actionable findings — no sign-up, no network calls, no AI.

npx repo-scanner .

Example output

╭──────────────────────────────────────────────────────────────╮
│  repo-health  /home/user/my-project                          │
╰──────────────────────────────────────────────────────────────╯

  DOCUMENTATION
  ✓  README found (README.md)
  ●  No license file found

  SECURITY
  ✓  .gitignore found
  ✗  Potential secret files tracked in git: .env

  QUALITY
  ✓  Test script found in package.json
  ●  No CI configuration found
  ✓  Lint/format config found (.eslintrc.json)

  STRUCTURE
  ✓  Git repository detected
  ✓  Lockfile found (package-lock.json)
  ✓  No tracked files over 10 MB

  ────────────────────────────────────────────────────────────
    Score   ████████████████░░░░░░░░   68/100   Fair
  ────────────────────────────────────────────────────────────

  Suggestions:
    → Add a LICENSE file so others know how they can use your project
    → Add a CI workflow (e.g. GitHub Actions) to automate tests and builds
    → Remove secret files from git history and add them to .gitignore

Install

One-off scan (no install needed):

npx repo-scanner .

Global install:

npm install -g repo-scanner
repo-health .

Usage

# Scan current directory
repo-health .

# Scan a specific path
repo-health /path/to/repo

# Machine-readable JSON output
repo-health . --json

# Strict mode — WARNs count as zero points (useful in CI)
repo-health . --strict

# Custom rule weights via config file
repo-health . --config repo-health.json

# Generate a shareable HTML report
repo-health . --html report.html

Checks

10 checks across 4 categories. Each has a weight; the final score is 0–100.

| # | Category | Check | Weight | PASS | WARN | FAIL | |---|---|---|:---:|---|---|---| | 1 | Documentation | README | 10 | exists & non-empty | too short | missing | | 2 | Documentation | License | 5 | LICENSE file found | missing | — | | 3 | Security | Tracked secrets | 15 | no secret files in git | — | .env, keys, certs tracked | | 4 | Security | .gitignore | 10 | exists | — | missing | | 5 | Quality | Tests | 10 | test script / dir found | none detected | — | | 6 | Quality | Lint / Format | 5 | ESLint/Prettier/Ruff config | none detected | — | | 7 | Quality | CI config | 10 | GitHub Actions / GitLab CI etc. | none detected | — | | 8 | Structure | Git repo | 15 | valid .git directory | — | not a repo | | 9 | Structure | Lockfile | 10 | lockfile found | manifest without lockfile | — | | 10 | Structure | Large files | 10 | no tracked files > 10 MB | large files tracked | — |

Scoring: PASS = weight × 1.0, WARN = weight × 0.5, FAIL = weight × 0


Config file

Create a repo-health.json to override weights or disable checks:

{
  "rules": {
    "license":  { "enabled": false },
    "ci":       { "weight": 15 },
    "secrets":  { "weight": 20 }
  }
}

Then run:

repo-health . --config repo-health.json

Exit codes

| Code | Meaning | |---|---| | 0 | Score ≥ 50 | | 1 | Score < 50 | | 2 | Unexpected error |

This makes repo-health --strict a useful CI gate:

# .github/workflows/health.yml
- name: Check repo health
  run: npx repo-scanner . --strict

Philosophy

  • Free — no accounts, no tokens
  • Local-first — reads only your filesystem and git history
  • Fast — typically < 1 second
  • Honest — gives you a real score, not just green checkmarks

License

MIT © Efe Görkem Bildi