oss-forensics

To investigate open-source supply-chain risks in GitHub repositories, apply a structured framework to coordinate multi-source evidence collection, validate hypotheses, and generate formal forensic reports analyzing recovered deleted content and force-push history rewrites.

Yes, you can recover deleted content and analyze force-push history rewrites by applying a multi-agent investigation workflow that extracts indicators of compromise and collects evidence across local git data, GitHub REST API, Wayback Machine, and GH Archive.

OSS supply-chain forensics requires access to local git data, the GitHub REST API, Wayback Machine data, and GH Archive results to feed into evidence management scripts and strict validation guardrails for accurate forensic reporting.

You generate executive-ready forensic reports with a documented chain of custody and traceable evidence by completing a 7-phase investigation workflow that adapts the RAPTOR framework for OSS forensics, including evidence collection, hypothesis validation, and reporting.

Yes, GitHub forensics requires access to the GitHub REST API, Wayback Machine data, and GH Archive results, which must be configured during the Phase 0 initialization steps when creating an investigation workspace.

Use an automated forensics framework when you need to detect deleted content, force-push history rewrites, and extract indicators of compromise across GitHub repositories, providing structured evidence management and strict validation guardrails for formal reporting.