oss-forensics

Correlate multi-source evidence of supply-chain compromise in GitHub repositories.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/travelinman1013/leroys-agent --skill oss-forensics-travelinman1013
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/travelinman1013/leroys-agent/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/travelinman1013/leroys-agent --skill oss-forensics-travelinman1013

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Open-source software supply chains are vulnerable to attacks that are hard to detect with ad-hoc checks. This skill provides a structured framework to investigate, recover evidence, form hypotheses, and generate a defensible forensic report for GitHub repositories.

Core Features & Use Cases

  • 7-phase multi-agent investigation framework covering local git history, GitHub API, Wayback Machine, and GH Archive.
  • Evidence collection, cross-source correlation, hypothesis validation, and formal reporting.
  • Use cases include force-push detection, IOC extraction, deleted content recovery, and post-incident remediation planning.

Quick Start

Initiate an OSS forensics investigation on a target repository to start collecting evidence and generate a structured forensic report.

Frequently Asked Questions about oss-forensics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate a GitHub repository for supply-chain compromise?

To investigate GitHub supply-chain compromise, you need a structured forensic framework that collects evidence across local git history, GitHub API, Wayback Machine, and GH Archive to detect anomalies and generate a validated report.

What is the best way to detect force-pushes and deleted content in OSS repositories?

Detecting force-pushes and recovering deleted content in OSS repositories requires correlating local git history with GitHub API data and Wayback Machine snapshots to identify overwritten commits and extract hidden indicators of compromise.

Can I extract IOCs and anomalous actor activity from GitHub repositories?

Yes, you can extract IOCs and identify anomalous actor activity by querying the GH Archive and GitHub API to track suspicious commit patterns, unauthorized changes, and malicious metadata across multiple data sources.

Does GitHub forensics work with multi-source data like Wayback Machine and GH Archive?

GitHub forensics relies on multi-source data correlation, using Wayback Machine to recover deleted repository content and GH Archive to analyze historical actor activity, ensuring cross-source consistency for a defensible report.

How do I generate a defensible forensic report for an open-source security incident?

Generating a defensible forensic report requires collecting evidence through a multi-phase investigation, validating hypotheses across local and remote sources, and applying redaction guardrails to ensure traceability and protect exposed secrets.

What tools do I need for open-source software supply-chain forensics?

Open-source supply-chain forensics requires optional scripted tools and a structured evidence store to query git history, GitHub APIs, and web archives, ensuring evidence collection remains traceable and verified across sources.