Check-Pack is a supply chain safety tool designed to protect "vibe coders"—developers heavily utilizing LLMs like Claude, Cursor, and Copilot—against malicious, hallucinated, or abandoned packages. It acts as a zero-trust enforcer, intercepting package manager commands (npm install, pip install, docker pull) and generating a rigorous security scorecard before allowing the package manager to download code.
- OSV.dev Vulnerability Scanning: Checks packages against the global Open Source Vulnerability database for Critical and High severity CVEs.
- Pre-Flight Transitive DAG Scan: Recursively resolves a package's full dependency tree from registry metadata in-memory, without installing anything to disk. Catches deeply nested vulnerabilities (like log4j) before code touches the machine.
- Workspace SBOM Scanning: Generates a Software Bill of Materials using
syftand audits the entire installed dependency tree withgrypeto catch transitive vulnerabilities (--deep). - Component Health Analysis: Computes a 100-point security scorecard based on release cadence, maintainer count, and abandonment signals via the NPM and PyPI registries.
- Native Hook Interception: Lightweight shell hooks bind to your
npm,pip, anddockerinvocations, requiring zero project configuration changes. - MCP Server: Exposes all scan capabilities as Model Context Protocol tools so your AI agent (Cursor, Claude Code, RooCode, Antigravity) can validate packages before writing code that depends on them.
Check-Pack is designed for zero-friction deployment. No repository cloning or manual dotfile editing required.
npx @edgebird.dev/check-pack install-hooksWhat this does automatically:
- Installs the Check-Pack native system hooks (
alias npm,alias pip,alias docker) into your terminal profile (~/.zshrc/~/.bashrc). - Outputs the MCP JSON configuration block ready to paste into Cursor (
.cursor/mcp.json), RooCode/Cline (cline_mcp_settings.json), Claude Code, or Antigravity.
# Analyze a single package
check-pack npm express
check-pack pypi requests
# Pre-flight scan: resolve full transitive dependency tree (no install)
check-pack --preflight express
# Deep SBOM scan on an existing workspace
check-pack --deep .Add the following to your agent's MCP configuration file (e.g. .cursor/mcp.json):
{
"mcpServers": {
"check-pack": {
"command": "check-pack-mcp"
}
}
}Available MCP tools:
analyze_package_security— Score a single npm or PyPI packageanalyze_preflight_deps— Recursively scan the full transitive dependency graph before installationanalyze_workspace_deep— Run a full SBOM audit on a directoryanalyze_container— Scan a Docker image for OS-layer CVEs
When Check-Pack analyzes a package, it starts at 100 points and applies penalties based on real-world supply chain risk vectors:
| Status | Score Range | Meaning |
|---|---|---|
| PASS | 80 - 100 | Clean bill of health. Package is maintained and free of known vulnerabilities. |
| WARN | 50 - 79 | Moderate/low CVEs present, or package not updated in over a year. Installation proceeds. |
| FAIL | < 50 | Critical/High CVEs found, or package severely abandoned. Installation is blocked. |
Check-Pack Hook intervening for [flatmap-stream]...
Checking [flatmap-stream] in [npm]...
=========================================
Package: flatmap-stream
Score: 15/100
Status: FAIL
=========================================
[CRITICAL FAILURES]:
- Found 2 Critical/High CVEs (e.g. GHSA-9x64-5r7x-2q53)
- Package is severely abandoned (Last updated > 2 years ago).
[WARNINGS]:
- Only 1 maintainer listed. Low bus factor.
Check-Pack blocked installation of flatmap-stream due to security failures.
Halting dependency installation. Please review the scorecard above.
To bypass the alias and invoke the raw package manager directly:
\npm install <package>
\pip install <package>
\docker pull <image>The --deep, --preflight transitive workspace scan, and Docker shield features require:
brew install syft grypeISC