oss-forensics

Recovering deleted GitHub commits involves reconstructing repository history across local git, GitHub API, and GH Archive. The forensics workflow detects force-push events and recovers deleted commits to prove unauthorized history modifications.

Evidence validation for open-source supply chain attacks enforces an internal evidence registry with cross-source proof guardrails. It requires mechanically validated hypotheses from multiple public sources before producing a final forensic report, preventing unsubstantiated claims.

You can extract IOCs from GitHub repositories using Python3 by collecting evidence across local git, GitHub API, GH Archive, and Wayback Machine. The workflow cross-references these sources to identify indicators of compromise during supply chain investigations.

You need Python3 installed to run the supply chain forensics workflow. It is the only runtime dependency required to reconstruct repository history, extract IOCs, and generate evidence-backed incident reports for suspected GitHub compromises.

The best way to detect suspicious workflow changes in GitHub repositories is applying a multi-source evidence collection approach. By reconstructing repository history and cross-referencing local git, GitHub API, and Wayback Machine, you can validate unauthorized modifications.