supply-chain-risk-auditor

Audits project dependencies for supply chain risk factors and generates a structured report.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/TECH-HY/SKILLS --skill supply-chain-risk-auditor-tech-hy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supply-chain-risk-auditor
Source: https://github.com/TECH-HY/SKILLS/tree/main/skills/supply-chain-risk-auditor
Command: npx skills add https://github.com/TECH-HY/SKILLS --skill supply-chain-risk-auditor-tech-hy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manually evaluating every dependency in a project for takeover or exploitation risk is slow and error-prone. This Skill systematically checks each dependency against defined risk criteria and produces a structured report highlighting the ones that need attention. ## Core Features & Use Cases - Risk Factor Evaluation: Flags dependencies with single or anonymous maintainers, stale maintenance, low popularity, high-risk features like FFI or deserialization, past CVEs, or missing security contacts. - Accurate Data via GitHub CLI: Uses the gh tool to query real numbers for stars, open issues, and repository activity instead of guessing. - Structured Report with Alternatives: Generates a results.md report from a template, including counts by risk factor, a high-risk dependency table, and suggested better-maintained replacements. - Use Case: Before a security engagement, run the audit on a client's repository to identify unmaintained or single-maintainer dependencies and recommend drop-in replacements. ## 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 evaluate each dependency against risk criteria like single maintainers, staleness, low popularity, past CVEs, and missing security contacts. The result is a report listing 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 archived, has low popularity, implements risky features like FFI or deserialization, has past high-severity CVEs, or lacks a security contact.

Does this replace vulnerability scanners like npm audit or pip-audit?

No. It does not perform active vulnerability scanning, runtime analysis, or license compliance checks. Use dedicated tools like npm audit or pip-audit for known-vulnerability detection alongside this risk assessment.

What tools are required to run a dependency risk audit?

The GitHub CLI (`gh`) must be installed and available. It is used to query accurate data such as star counts, open issues, and repository activity for each dependency.

How are suggested alternative dependencies chosen?

For each high-risk dependency, the audit suggests a replacement that performs the same function but is more popular and better maintained. Direct successors and drop-in replacements are preferred, with a short justification for each suggestion.