oss-forensics

To investigate a GitHub repository for supply chain attacks, you can automate evidence collection from the GitHub Archive, Wayback Machine, and GitHub API. This process identifies deleted commits and force-pushes to analyze forensic anomalies and generate structured reports.

Forensic analysis of deleted commits and force-pushes in Git is the process of identifying compromised repository anomalies. It involves collecting evidence from public databases and local git repositories to form and validate hypotheses about supply chain incidents.

Yes, you need Python and access to external APIs to collect GitHub forensic evidence. The automated evidence collection scripts utilize external sources like the GitHub Archive and Wayback Machine, requiring dependencies such as pypdf, pdfplumber, and pdf2image for analysis.

Yes, you can use the Wayback Machine and GitHub Archive for repository security investigations. They serve as primary sources for collecting historical evidence, allowing you to track deleted commits and validate hypotheses regarding supply chain attacks.

The best way to report supply chain investigation findings is by generating structured forensic reports. These reports include detailed timelines, validated hypotheses, and an evidence registry compiled from local git repositories and public databases.

Your GitHub repository forensic analysis shows anomalies in force-pushes because they often indicate a compromised repository. Investigating these force-pushes requires collecting evidence from the GitHub API and local git repositories to determine if a supply chain attack occurred.