oss-forensics

To investigate deleted commits and force-push events in a GitHub repository, you can run a forensic analysis that recovers missing history and identifies rewritten commits. This multi-agent investigation locates evidence directly from GitHub APIs and local git analysis to detect supply chain compromises.

Extracting and enriching Indicators of Compromise (IOCs) from open-source supply chain attacks involves gathering evidence from repository history and validating it against multiple sources. This forensic process creates structured, verifiable reports to summarize the investigation results.

Web archive data retrieval for supply chain forensics works by leveraging BigQuery to analyze historical archives alongside GitHub repository evidence. This method helps validate investigation hypotheses by comparing recovered deleted commits with archived repository states.

Yes, you can use GitHub APIs and local git analysis to detect supply chain vulnerabilities in your repositories. This forensic investigation requires extensive knowledge of GitHub APIs to recover evidence, identify force-pushes, and generate structured reports on potential compromises.

A 7-phase open-source supply chain forensic investigation involves evidence recovery from GitHub, BigQuery archive analysis, IOC extraction and enrichment, and hypothesis validation. The process concludes with generating structured forensic reports summarizing the detected supply chain vulnerabilities.