oss-forensics

Open-source supply chain investigation involves collecting and correlating evidence from multiple sources like git analyses, GitHub API responses, GitHub Archive data, and Wayback snapshots. It structures the detection and verification of suspicious repository activities into defined phases for credible reporting.

Yes, GitHub repository forensics can detect deleted commits and force-pushes by correlating local git analyses with Wayback snapshots and GitHub Archive data. This multi-source approach identifies discrepancies indicating removed or overwritten repository history.

Generate an auditable chain-of-custody report by processing collected evidence through structured phases: collection, consolidation, hypothesis formation, validation, and final reporting. This workflow produces a detailed investigation report with an auditable evidence registry.

No specific external dependencies are required to run this supply chain forensics workflow. It operates using internal scripts and references to analyze archived repository content, GH Archive data, and Wayback snapshots without additional environment setup.

Use a structured forensics methodology for a repository security incident when you need to detect, verify, and report supply chain compromises. It is essential for maintaining an auditable evidence registry and ensuring secrets are redacted during multi-source data validation.