supply-chain-analysis

Analyze dependency closures and generate signed SBOMs for supply chain risks.

11|1|Updated May 4, 2026
One-click install
npx skills add https://github.com/dreadnode/capabilities --skill supply-chain-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supply-chain-analysis
Source: https://github.com/dreadnode/capabilities/tree/main/capabilities/secure-software/skills/supply-chain-analysis
Command: npx skills add https://github.com/dreadnode/capabilities --skill supply-chain-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the manual, error-prone work of tracking project dependencies, identifying vulnerable or unmaintained packages, and generating compliant software bill of materials (SBOMs) for supply chain security audits.

Core Features & Use Cases

  • Dependency Enumeration: Automatically parse common manifests like package.json, requirements.txt, Cargo.lock, and go.sum to inventory all direct and transitive dependencies, flagging unpinned transitive packages as a risk.
  • Risk Correlation: Cross-reference dependencies against OSV advisories, Spectra Assure reports, and OpenSSF Scorecards to identify malicious packages, critical CVEs, and unmaintained libraries with low bus factor.
  • SBOM Generation: Produce signed CycloneDX or SPDX SBOMs for compliance requirements, or lightweight custom SBOMs when no Spectra Assure Portal project exists. Use case: A development team can use this skill to assess the security posture of their application's dependency tree before a production release, prioritizing fixes for the highest-risk packages first.

Quick Start

Use the supply-chain-analysis skill to audit the dependencies of the project in your current working directory and generate a prioritized list of supply chain risks along with a saved SBOM file.

Frequently Asked Questions about supply-chain-analysis

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

FAQPage Schema
How do I generate a compliant SBOM from package manifests like package.json or Cargo.lock?

To generate a compliant SBOM from package.json or Cargo.lock, you parse the manifests to inventory dependencies and export the results as signed CycloneDX or SPDX files for compliance audits and security tracking.

How does dependency closure analysis identify malicious packages and unpatched vulnerabilities?

Dependency closure analysis identifies malicious packages by cross-referencing your full dependency tree against OSV advisories and OpenSSF Scorecards, flagging unmaintained libraries and unpinned transitive packages that pose supply chain security risks.

Can I audit transitive dependencies in Go or Python projects for supply chain risks?

Yes, you can audit transitive dependencies in Go or Python projects by parsing go.sum and requirements.txt manifests to enumerate the full dependency closure and prioritize risks based on OpenSSF Scorecard metrics.

What is the best way to prioritize critical CVEs in a software dependency tree?

The best way to prioritize critical CVEs in a software dependency tree is correlating advisories from OSV and Spectra Assure reports against your dependency manifests to deliver prioritized risk reporting for production releases.

Do I need a Spectra Assure Portal project to export a CycloneDX SBOM?

No, you do not need a Spectra Assure Portal project to export a CycloneDX SBOM; you can automatically generate lightweight custom SBOMs directly from your dependency manifests when no portal project exists.

Does supply chain security analysis work with requirements.txt and go.sum files?

Supply chain security analysis works directly with requirements.txt and go.sum files to enumerate dependencies, identify unpinned transitive packages, and assess supply chain risks before production deployment.