oss-forensics

To investigate a GitHub repository for supply chain attacks, you analyze local git history, query the GitHub API, check the Wayback Machine, and review GitHub Archive data to detect malicious dependencies and deleted commits.

Dependency analysis for malware detection involves scanning project dependencies to identify compromised packages, deleted commits, and indicators of compromise, generating a detailed forensic report of the supply chain security investigation.

Yes, BigQuery access is required for full functionality when checking for compromised dependencies, alongside git and GitHub API access, to perform thorough GitHub Archive analysis and IOC enrichment during the forensic investigation.

Yes, you can retrieve deleted commits and their history from a GitHub repository by performing local git analysis and querying the GitHub API to recover evidence of potentially malicious supply chain modifications.

The best way to perform forensic analysis on compromised dependencies is combining local git analysis with GitHub API queries, Wayback Machine checks, and GitHub Archive analysis to produce a comprehensive forensic report.

Supply chain forensics requires multiple data sources because attackers often delete malicious commits or alter repositories, making cross-referencing across Wayback Machine, GitHub Archive, and IOC enrichment necessary to reconstruct the full attack timeline.