Package Risk Radar (CVE, EPSS & OpenSSF Scorecard MCP)
Pricing
from $5.00 / 1,000 package auditeds
Package Risk Radar (CVE, EPSS & OpenSSF Scorecard MCP)
MCP-ready security & supply-chain auditor for npm, PyPI, Go, Cargo, and Maven. Fuses OSV.dev CVEs, FIRST EPSS, OpenSSF Scorecard, transitive deps, and abandonment signals into a compact safe/caution/block verdict.
Pricing
from $5.00 / 1,000 package auditeds
Rating
0.0
(0)
Developer
Nanda Leo Ardana
Maintained by CommunityActor stats
0
Bookmarked
1
Total users
0
Monthly active users
3 hours ago
Last modified
Categories
Features
Share
Package Risk Radar (pkg-risk-radar)
Fast, AI-agent-ready security and supply-chain auditor for npm, PyPI, Go, Cargo, and Maven packages.
Designed for Apify Standby Mode + MCP (StreamableHTTP) and standard Batch Dataset Runs with Pay-Per-Event (PPE) billing.
What It Checks
Fuses 4 orthogonal supply-chain signals into a single compact safe | caution | block | unknown verdict (0–100 risk score):
- Vulnerabilities & Exploitability: OSV.dev CVEs +
fixedInversions + FIRST EPSS exploit probability scores. - OpenSSF Scorecard: Project hygiene (
overallScoreand individual checks) via deps.dev. - Transitive Blast Radius: Direct and total transitive dependency counts via deps.dev.
- Abandonment & Existence Signals: Registry verification (fails closed as
unknownfor missing/typosquatted packages), deprecation/yanked flags, days since last release, and monthly download volume (npm / PyPI).
MCP Tools (Standby Mode — /mcp)
Connect any MCP client (Claude, Cursor, Windsurf, or mcp.apify.com) to the Standby URL /mcp:
audit_package:{ ecosystem, name, version? }— sub-second cached / ~1s live audit for a single package.audit_packages_batch:{ packages: string[], defaultEcosystem? }— audits up to 20 packages in parallel (ecosystem:name@versionformat).
Batch Input Example
{"packages": ["npm:lodash@4.17.15","pypi:requests@2.31.0","npm:zod@3.24.2"],"ecosystem": "npm"}
Pricing (Pay-Per-Event)
package-audited($0.005/ package): Charged only after a complete audit succeeds. Incomplete audits (e.g. registry miss or upstream timeout returningverdict: "unknown") are never charged.
Connect via MCP (Claude, Cursor, Windsurf)
{"mcpServers": {"pkg-risk-radar": {"type": "http","url": "https://shikitoka--pkg-risk-radar.apify.actor/mcp","headers": {"Authorization": "Bearer YOUR_APIFY_TOKEN"}}}}
Or via Apify's hosted MCP router: https://mcp.apify.com/?tools=shikitoka/pkg-risk-radar.
n8n / Make HTTP Integration
POST https://api.apify.com/v2/acts/shikitoka~pkg-risk-radar/run-sync-get-dataset-items?token=YOUR_APIFY_TOKENContent-Type: application/json{"packages": ["npm:lodash@4.17.15", "pypi:requests@2.31.0"]}