oss-forensics

To investigate open-source supply chain compromise, aggregate evidence from local git history, GitHub API activity, Wayback snapshots, and BigQuery archives. Apply a 7-phase, multi-agent workflow to cross-verify events and produce a formal forensic report.

A defensible chain of custody during an OSS security investigation requires built-in guardrails and cross-source verification. This framework strictly governs evidence by cross-verifying events, redacting sensitive data, and maintaining an auditable history for conclusions.

Yes, you can reconstruct suspicious repository activity by coordinating local Git data with Wayback Machine snapshots and GH Archive history. This multi-source collection forms hypotheses and generates auditable conclusions suitable for disclosure.

No external dependencies are required to start collecting evidence. Initiate the forensics workflow directly against the target OWNER/REPO to orchestrate multi-source data collection and generate the final report without prerequisite installations.

A multi-agent workflow improves open-source supply chain incident reporting by applying a 7-phase process across local Git, GitHub API, Wayback, and BigQuery data. This structured approach ensures evidence integrity and generates an executive report.

Use an automated forensics framework instead of manual git log analysis when a repository shows suspicious activity and requires defensible, auditable conclusions. It orchestrates multi-source data collection and cross-verification for formal disclosure or remediation planning.