oss-forensics

To recover deleted commits after a force push on GitHub, this Skill utilizes GitHub Archive and local git recovery techniques to find force-pushed or removed commit history. It extracts missing data for in-depth supply chain investigation.

IOC extraction for open-source repository investigation works by pulling indicators of compromise from local git analysis, GitHub API calls, and Wayback Machine queries. These indicators are then enriched using various public sources for structured reporting.

Yes, you need BigQuery access to comprehensively investigate GitHub repository supply chain attacks. The forensic framework requires BigQuery alongside GitHub API, local git repository access, and Wayback Machine queries to detect deleted commits and extract IOCs.

The best way to analyze suspicious open-source repositories is using a multi-agent framework that runs concurrent investigations across GitHub Archive, local git, and Wayback Machine. This approach mechanically validates hypotheses and generates structured forensic reports.

Yes, you can generate a structured forensic report from GitHub repository analysis. The framework produces detailed documentation featuring an evidence registry, timeline, hypotheses, and recommendations based on a comprehensive 7-phase investigation.

Wayback Machine web archive querying matters for supply chain security because it captures historical repository states before malicious force-pushes or deletions occur. Comparing archived data against current local git states reveals hidden tampering and security anomalies.