oss-forensics

You investigate OSS supply chain compromises by executing a multi-phase forensics workflow that aggregates evidence from local git, GitHub API, Wayback Machine, and GH Archive to detect hidden alterations. This process recovers deleted commits, extracts IOCs, and validates hypotheses to produce a final forensic report.

The best way to recover deleted commits and detect force-pushes is through multi-source cross-referencing of local git history against GitHub API and GH Archive event logs. This approach identifies discrepancies caused by force-pushes and reconstructs deleted repository content for forensic analysis.

Cross-source evidence collection works by querying local git history, GitHub API, Wayback Machine, and GH Archive simultaneously to build a formal evidence store. It correlates repository events across these independent sources to validate hypotheses and ensure forensic integrity.

Yes, you can extract IOCs and generate standardized forensic reports for compromised repositories. The workflow collects indicators of compromise across multiple sources and outputs a final report with automated redaction of secrets for secure dissemination.

You do not need external tools beyond the integrated sources, as hypothesis validation is executed by cross-referencing local git analysis with GitHub API, Wayback Machine, and GH Archive data. This multi-source aggregation framework internally validates forensic findings.