oss-forensics

To investigate GitHub repositories for supply chain attacks, you need a structured forensic framework that recovers deleted commits, detects force-pushes, and validates unauthorized CI/CD modifications using a rigorous 7-phase validation process.

Yes, you can recover deleted git commits hidden by force-pushes by aggregating multi-source evidence from local git repositories, the GitHub API, GitHub Archive on BigQuery, and the Wayback Machine to reconstruct the hidden commit SHAs.

Multi-source evidence collection in open-source forensics aggregates data from local git repositories, GitHub API, GitHub Archive via BigQuery, and the Wayback Machine to verify supply chain compromises and validate security hypotheses.

Yes, you need Python3, gcloud, and jq installed to perform forensic analysis on GitHub repositories, as these dependencies are required to query the GitHub API and access the GitHub Archive on BigQuery.

Forensic reporting documents indicators of compromise for open-source software by generating structured, evidence-backed reports that establish clear timelines of malicious code injection using cross-referenced data.

The best way to detect unauthorized CI/CD modifications in a compromised repository is applying a rigorous 7-phase validation framework that cross-references local git data with GitHub API evidence.