supply-chain-scan

supply-chain-scan

A 5-second morning safety check for the project you're about to work on. Before your first install/update of the day, scan its dependencies for known-malicious packages, CVEs, freshly-published (zero-hour) deps, and missing release-cooldown / digest pinning — across npm, PyPI and Docker, in one command.

npx supply-chain-scan

• 🛡️ Catches what npm audit misses — known-malicious packages (the OSV MAL- feed), not just CVEs.
• 🌅 Built for a morning routine — point it at the repo you're opening; get a clear go / review verdict.
• 🧩 npm + PyPI + Docker in a single pass.
• 📦 Zero runtime dependencies. A supply-chain tool shouldn't be a supply-chain risk — read all of it in 5 minutes.
• 💻 Cross-platform (Windows / Linux / macOS), no account, no CI, no telemetry.

---

Why

The 2025–26 wave of npm and PyPI supply-chain attacks (hijacked maintainers → malicious release → fast adoption) and malicious/typosquatted Docker images all exploit the same blind spot: tools that only know about already-reported CVEs. supply-chain-scan layers the free defenses that actually cover the gap:

Threat	Defense in this tool
Known-malicious package (npm/PyPI/Go/Rust)	osv-scanner + the OSV MAL- feed
Known CVE	osv-scanner + the package manager's audit
Zero-hour malicious release (not yet reported)	freshness heuristic (flag deps published < N days ago) + the release-cooldown config check
Mutable / hijackable Docker base image	digest-pinning check (@sha256:) + optional image CVE scan
Install-time code execution outside package.json scripts (the phantom gyp trick — Shai-Hulud/Miasma, 2026)	build-manifest scan: flags shell-command substitution in binding.gyp/Makefile/setup.py
Obfuscated worm payload dropped as a root JS file (e.g. bun_environment.js)	undeclared-large-JS check: oversized root .js/.ts that isn't a declared entry point
Repo config that auto-runs when you open the folder in an AI coding agent (the Miasma reaches Azure wave, 2026)	agent/IDE-config scan: flags on-open execution in .devcontainer, .vscode/tasks.json, .claude hooks, .mcp.json

No single open-source CLI combined these into a one-command morning verdict across all these ecosystems — so here it is.

The AI-agent config trigger

The June 2026 Miasma wave (which had GitHub disable 73 Microsoft Azure repos) did not require installing a poisoned package. It planted repository config files that execute the moment a developer opens the folder in Claude Code, Cursor, Gemini CLI or VS Code — a devcontainer.json postCreateCommand, a VS Code task set to runOn: folderOpen, a Claude Code hook, or an .mcp.json server command. The scan flags exactly those auto-on-open execution points (and nothing as noisy as an ordinary settings.json), so you see them before your editor runs them.

---

Install

One-time: the scan engine

supply-chain-scan drives Google's free osv-scanner for the malicious/CVE layer. Install it once, globally:

OS	Command
macOS / Linux	brew install osv-scanner
Windows	winget install Google.OSVScanner (or scoop install osv-scanner)
Any	a release binary from osv-scanner/releases, or go install github.com/google/osv-scanner/v2/cmd/osv-scanner@latest

(If it's missing, the scan tells you the exact command for your OS and still runs the other checks.)

The tool — pick one

As an npm CLI (any editor / terminal):

npx supply-chain-scan [project-dir]      # no install
npm install -g supply-chain-scan         # or install globally

As a Claude Code plugin (adds a /supply-chain-scan skill to your morning routine):

/plugin marketplace add Flo5k5/supply-chain-scan
/plugin install supply-chain-scan@flo5k5-tools

---

Usage

supply-chain-scan [project-dir]      # defaults to the current directory

  --fresh-days <N>   flag deps published less than N days ago   (default 3)
  --max-js-mb <N>    flag undeclared root JS/TS files larger than N MB (default 0.5)
  --no-recursive     scan only the root dir, not nested packages (recursive by default)
  --depth <N>        max directory depth for the recursive scan (default 5)
  --no-agent-configs skip the agent/IDE auto-exec-on-open check (on by default)
  --images           also pull & scan Docker base images for CVEs (slow, opt-in)
  --json             machine-readable output
  --no-color         disable ANSI colors
  -h, --help / -v, --version

Exit codes (scriptable): 0 clean · 1 review (findings) · 2 setup (osv-scanner not installed).

Monorepos (recursive by default)