oss-forensics

To investigate open-source supply chain compromises, this Skill coordinates multi-source evidence collection and hypothesis testing across GitHub, Wayback, and local Git data. It maps compromises by detecting force-push erasures, deleted issues, and extracting IOCs within a defined investigation window.

Detecting force-push erasures and deleted GitHub issues is achieved by cross-referencing GitHub API data with Wayback Machine and archival records. The Skill forms and validates evidence-backed hypotheses to confirm whether erasures occurred during the specified investigation window.

Yes, you can extract IOCs and generate structured forensic reports from open-source repositories. The Skill outputs a final report containing an evidence registry and chain-of-custody records to ensure traceability and support reproducible investigations.

Yes, this supply chain investigation approach enforces strict anti-hallucination guardrails and evidence provenance. It uses an integrated evidence store and chain-of-custody records to ensure all extracted IOCs and mapped compromises remain traceable to their original sources.

Mapping supply chain compromises with Wayback Machine and GitHub archival data involves a 7-phase multi-agent framework. This framework coordinates evidence collection from multiple sources, validates findings, and outputs a structured forensic report with an evidence registry.

To start an open-source forensics investigation for supply chain security, you initialize the workflow for a target repository. The Skill then coordinates multi-source evidence collection across GitHub and Wayback Machine, requiring no additional dependencies to begin the 7-phase process.