supply-chain-risk-auditor

Audits project dependencies for supply chain takeover and exploitation risk factors.

Updated Apr 5, 2026
One-click install
npx skills add https://github.com/marumo333/atrox --skill supply-chain-risk-auditor-marumo333
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: supply-chain-risk-auditor
Source: https://github.com/marumo333/atrox/tree/main/.claude/skills/trailofbits/plugins/supply-chain-risk-auditor/skills/supply-chain-risk-auditor
Command: npx skills add https://github.com/marumo333/atrox --skill supply-chain-risk-auditor-marumo333

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh.

What problem does it solve? Security teams need to know which project dependencies are at heightened risk of exploitation or maintainer takeover before an engagement, but manually researching every dependency's maintenance status, popularity, and history is slow and error-prone. ## Core Features & Use Cases - Risk Factor Evaluation: Assesses each dependency against six criteria including single-maintainer projects, unmaintained code, low popularity, high-risk features like FFI or deserialization, past CVEs, and missing security contacts. - Accurate GitHub Data: Uses the gh CLI to query exact star counts, open issues, and repository status so every cited number is verifiable. - Structured Report Generation: Produces a results.md report with a high-risk dependencies table, suggested alternatives, risk factor counts, and an executive summary. - Use Case: Before scoping a security audit of a web application, run this Skill to flag that a core parsing library is maintained by one anonymous developer with unpatched CVEs, and get a drop-in replacement recommendation. ## Quick Start Audit this project's dependencies for supply chain risk and generate a report of high-risk packages with suggested alternatives.

Frequently Asked Questions about supply-chain-risk-auditor

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit project dependencies for supply chain risk?▼

Run the audit to locate each direct dependency's git repository, then evaluate it against risk criteria like single maintainers, staleness, low popularity, and past CVEs. The result is a report listing only high-risk dependencies with suggested alternatives.

What makes a dependency high risk for supply chain attacks?▼

A dependency is flagged if it has a single or anonymous maintainer, is unmaintained or deprecated, has low popularity, implements risky features like FFI or deserialization, has high-severity CVEs, or lacks a security contact.

Does this replace npm audit or pip-audit vulnerability scanning?▼

No. This Skill evaluates structural takeover and exploitation risk, not known vulnerability databases. Use dedicated scanners like npm audit or pip-audit for active CVE detection, and this Skill for maintainer and ecosystem health analysis.

What tools are required to run a dependency risk audit?▼

The GitHub gh CLI must be installed and available, since the audit queries exact repository data such as star counts and open issues. The Skill will ask you to install gh if it is not found.

When should I not use supply chain dependency auditing?▼

Avoid it for active vulnerability scanning, runtime dependency analysis, and license compliance auditing. It is designed for static, pre-engagement evaluation of dependency maintenance and takeover risk.