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

shieldrepo

v0.1.0

Published

Scan any GitHub repo for malicious code, secrets, and supply-chain risks before you npm install. 43 checks across 7 layers.

Readme

reposhield

CLI for RepoShield — scan any GitHub repository for malicious code, exfiltration payloads, exposed secrets, and supply-chain risks before you npm install.

43 checks across 7 layers (install hooks, dangerous code, network indicators, dependencies via OSV, CI/CD hardening, exposed secrets, repo-surface signals). Free, no signup.

Quickstart

No install needed — runs through npx:

npx shieldrepo https://github.com/sindresorhus/slugify

Short form (owner/repo):

npx shieldrepo expressjs/express

Machine-readable JSON (for CI pipelines):

npx shieldrepo vercel/next.js --json > report.json

With a Pro API key (private repos / unlimited rate limit):

REPOSHIELD_API_KEY=rs_... npx shieldrepo owner/private-repo
# or
npx shieldrepo owner/private-repo --key rs_...

Flags

| Flag | Default | What it does | |---|---|---| | --json | off | Print full ScanResult JSON to stdout (no progress to stderr). | | --quiet / -q | off | Suppress banner and progress bar. | | --key <KEY> / -k <KEY> | unset | API key. Falls back to REPOSHIELD_API_KEY env var. | | --fail-on <level> | caution | Exit non-zero on this verdict or worse. One of trust, caution, danger. | | --timeout <seconds> | 90 | Abort scan after N seconds. Network or CPU stall safety. | | --version | — | Print version + exit. | | --help | — | Print full help. |

Exit codes

| Code | Meaning | |---|---| | 0 | trust — safe to install | | 1 | caution — review findings before installing | | 2 | danger — do not install without review | | 3 | scan_error — network, auth, bad URL, or timeout (the tool itself failed) |

CI distinguishes "your repo is bad" (1, 2) from "the tool failed" (3) so a flaky network doesn't block your release pipeline.

CI integration

GitHub Actions

name: supply-chain-audit
on: [pull_request]
jobs:
  scan:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v4
      - run: npx shieldrepo ${{ github.repository }} --fail-on danger
        env:
          REPOSHIELD_API_KEY: ${{ secrets.REPOSHIELD_API_KEY }}

GitLab CI

reposhield:
  image: node:20
  script:
    - npx shieldrepo $CI_PROJECT_PATH --fail-on caution --json > report.json
  artifacts:
    paths: [report.json]
  variables:
    REPOSHIELD_API_KEY: $REPOSHIELD_API_KEY

CircleCI

jobs:
  audit:
    docker: [{ image: cimg/node:20.0 }]
    steps:
      - run: npx shieldrepo $CIRCLE_PROJECT_USERNAME/$CIRCLE_PROJECT_REPONAME --timeout 120

API endpoint

By default the CLI talks to https://reposhield.app. Override with REPOSHIELD_API_BASE for self-hosting or staging:

REPOSHIELD_API_BASE=https://staging.reposhield.app npx shieldrepo ...

Rate limits

  • Anonymous: 3 scans/day per IP
  • Free signed-in account: 10 scans/day
  • Pro: 100/day + /api/v1/scan REST API
  • Team: 1000/day + Team-tier checks

Upgrade: https://reposhield.app/pricing

What it does NOT do

  • Does not download or execute the repo on your machine.
  • Does not scan the npm tarball — only the GitHub repo source. (Tarball scanning ships in v1.1.)
  • Does not require auth tokens for public repos.

Methodology + every check ID with confidence label: https://reposhield.app/methodology

License

Apache-2.0. See LICENSE.