oss-forensics

To investigate a GitHub repository for a supply chain attack, coordinate multi-agent data collection from git history, GitHub APIs, BigQuery, and web archives to validate security hypotheses and detect unauthorized code modifications.

Yes, recovering deleted git commits helps find indicators of compromise by analyzing anomalous maintainer activity and force-pushed history, automatically gathering evidence from local git and GitHub Archive to extract verified IOCs.

Yes, you need python3, gcloud, and jq installed to perform forensic analysis, as the investigation requires querying BigQuery for GitHub Archive data and executing scripts for evidence-based reporting.

The best way to detect unauthorized code modifications is through a 7-phase forensic validation process that enforces strict anti-hallucination guardrails and gathers multi-source evidence to ensure high-confidence security assessments.

Yes, supply chain forensics works with the Wayback Machine by querying web archives alongside GitHub APIs and BigQuery to recover historical repository states, validating security hypotheses and detecting malicious injections.

Using a hypothesis validation framework for open-source security assessments prevents false positives by enforcing strict evidence-based reporting, coordinating multi-source data collection to extract IOCs and verify unauthorized changes.