oss-forensics

To investigate deleted commits and force-pushed histories in GitHub repositories, this skill coordinates multi-source evidence gathering from the GitHub API, GH Archive, Wayback Machine, and local git data to reconstruct events and validate claims.

Open-source supply chain forensics across multiple data sources requires fusing GitHub API, GH Archive, Wayback Machine, and local git data. This skill applies a centralized, phase-driven investigation framework to reconstruct events and generate a formal forensic report with an evidence registry.

Yes, you can use this forensics framework to analyze compromised maintainers and malicious releases. It is specifically designed to investigate open-source supply chain incidents involving compromised maintainers, malicious releases, and cross-source discrepancies across GitHub repositories.

To generate a formal forensic report with a chain-of-custody for a security incident, this skill enforces a structured final-report workflow that includes an evidence registry. It applies anti-hallucination guardrails and evidence verification throughout the investigation.

The investigation framework prevents hallucinations when reconstructing deleted GitHub issues or PRs by enforcing anti-hallucination guardrails and evidence verification. It cross-references multiple sources like the GitHub API and GH Archive to validate claims before reporting.

To start an OSS-forensics investigation for a compromised repository, initialize the investigation and begin multi-source evidence collection using the Phase 0 setup. This phase-driven approach systematically uncovers evidence for supply chain incidents.