oss-forensics

Investigate open-source supply-chain security incidents by using a structured, multi-agent forensics workflow that handles evidence collection, cross-source validation, and final reporting for GitHub-hosted repositories.

The best way to collect evidence during an OSS repository investigation is through cross-source validation using local git analysis, GitHub API data, Wayback Machine archives, and BigQuery, all stored in an auditable evidence store.

Yes, you can generate a standardized forensic report for supply-chain investigations using the built-in report template, which provides auditable traceability linking your hypotheses directly to collected evidence artifacts.

Yes, the forensics workflow supports analyzing historical repository data by integrating GH Archive and BigQuery data sources to enrich your incident investigation and validate evidence across multiple platforms.

To start an open-source software forensics investigation, you need access to the target GitHub repository and local git analysis tools, enabling Phase 0 initialization to seed the evidence store.

Use a structured forensics workflow for open-source repositories when investigating supply-chain incidents that require safety guardrails, hypothesis generation, and IOC enrichment to produce a traceable, auditable incident report.