supply-chain-forensics

Analyze software supply chains with SBOM generation, dependency verification, and SLSA mapping.

175|26|Updated Aug 14, 2025
One-click install
npx skills add https://github.com/jmagly/aiwg --skill supply-chain-forensics-jmagly
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: supply-chain-forensics
Source: https://github.com/jmagly/aiwg/tree/main/agentic/code/frameworks/forensics-complete/skills/supply-chain-forensics
Command: npx skills add https://github.com/jmagly/aiwg --skill supply-chain-forensics-jmagly

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill addresses the critical need to detect and prevent compromises within the software supply chain, ensuring the integrity of packages, build processes, and CI/CD pipelines.

Core Features & Use Cases

  • SBOM Analysis: Generates and validates Software Bill of Materials (SBOM) to identify components, licenses, and vulnerabilities.
  • Dependency Verification: Checks package integrity against registry hashes to detect tampering and typosquatting.
  • Build Pipeline Forensics: Scans CI/CD scripts and workflows for malicious patterns, unpinned actions, and unauthorized changes.
  • Reproducibility Checks: Assesses the reproducibility of build artifacts and maps findings to SLSA levels.
  • Use Case: A security team can use this skill to perform a comprehensive audit of a critical open-source project's supply chain, identifying potential vulnerabilities or signs of compromise before integrating it into their own systems.

Quick Start

Run a full supply chain audit on the current project.

Frequently Asked Questions about supply-chain-forensics

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

FAQPage Schema
How do I detect tampering and verify dependency integrity in my software supply chain?

To detect dependency tampering, supply chain forensics checks package integrity against registry hashes to identify anomalies and typosquatting. This process validates dependencies to ensure package integrity across your software supply chain.

What is the best way to audit CI/CD pipelines for malicious patterns and unauthorized changes?

Auditing CI/CD pipelines for malicious patterns involves scanning workflows for unpinned actions and unauthorized changes. Build pipeline forensics scans your scripts to detect tampering and map findings to MITRE ATT&CK techniques for supply chain attacks.

How do I generate and validate an SBOM to identify component vulnerabilities?

Generating and validating a Software Bill of Materials (SBOM) identifies components, licenses, and vulnerabilities. Supply chain forensics performs SBOM analysis using tools like CycloneDX to ensure component integrity and detect known vulnerabilities via OSV.dev.

Can I assess build reproducibility and map my findings to SLSA levels?

Yes, you can assess build reproducibility to determine if build artifacts can be consistently recreated. Supply chain forensics evaluates your build processes and maps the reproducibility findings directly to SLSA levels for compliance tracking.

Do I need specific security tools installed to perform supply chain security analysis?

Yes, supply chain security analysis requires external tools for package management, SBOM generation like CycloneDX, vulnerability scanning like OSV.dev, and Git history analysis to perform comprehensive dependency verification and build pipeline forensics.