oss-forensics

To investigate a GitHub repository for deleted commits and force-pushes, perform in-depth forensic analysis using local git analysis, GitHub Archive, and external sources to detect suspicious activity and collect evidence.

GitHub repository forensics for supply chain security is the process of detecting compromised accounts and malicious code by analyzing force-pushed commits, deleted content, and indicators of compromise across multiple data sources.

Yes, you can detect indicators of compromise in a local git repository by utilizing local git analysis combined with GitHub API data to identify suspicious activity and collect forensic evidence.

Yes, GitHub forensics works with the Wayback Machine for evidence collection by retrieving historical repository data alongside GitHub Archive and local git analysis to document suspicious activity.

To generate a forensic report for a compromised GitHub repository, form and validate hypotheses about the compromise, then document the collected evidence, analysis, and findings from your repository investigation.

Yes, you need extensive knowledge of GitHub events and data retrieval for repository investigation, as the forensic analysis relies on understanding these events to detect suspicious activity and deleted commits.