oss-forensics

Analyzes GitHub supply chain incidents across multiple sources and generates auditable forensic reports.

2|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/CUexter/hermes-agent --skill oss-forensics-cuexter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/CUexter/hermes-agent/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/CUexter/hermes-agent --skill oss-forensics-cuexter

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Supply chain investigation, evidence recovery, and forensic analysis for GitHub repositories. This skill provides a structured methodology to investigate and document supply-chain compromises in open-source projects, collecting evidence across multiple data sources and producing auditable reports.

Core Features & Use Cases

  • 7-phase multi-agent investigation framework for researching open-source supply chain attacks
  • Cross-source evidence collection (GitHub Archive, Wayback Machine, GitHub API, local git)
  • Evidence formation, hypothesis creation, and rigorous validation with guardrails
  • Forensic reporting with structured evidence registry and redaction of secrets
  • Real-world use cases include force-push detection, IOC extraction, deleted content recovery, and comprehensive reporting

Quick Start

Run a full OSS-forensics investigation on a target repository using the built-in multi-agent workflow and generate the final 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 a supply chain security incident?

To investigate a GitHub supply chain security incident, you can run a multi-agent forensic workflow that collects evidence from local git, GitHub API, Wayback Machine, and GH Archive, then generates an auditable report.

What is the best way to recover deleted content and extract IOCs from an open source repository?

Recovering deleted content and extracting IOCs requires cross-source evidence collection across GitHub Archive and local git, forming hypotheses, and validating findings with guardrails to produce a structured forensic report.

Can I detect force-pushes in git history using automated forensic analysis?

Yes, automated forensic analysis can detect force-pushes by coordinating multi-source investigations across local git and the GitHub API, documenting the evidence in a structured store for validation.

How do I generate an auditable report for an open source supply chain attack?

Generating an auditable report for an open source supply chain attack involves collecting evidence across multiple data sources, validating hypotheses with guardrails, and structuring the findings with redaction of secrets.

Does OSS forensics work with Wayback Machine and GitHub Archive for historical evidence collection?

Yes, OSS forensics coordinates multi-source investigations across the Wayback Machine and GitHub Archive alongside local git and the GitHub API to comprehensively collect and validate historical evidence.

What are the limitations of using a structured evidence store for supply chain forensics?

Using a structured evidence store for supply chain forensics requires rigorous cross-source verification and guardrails for redacting secrets, meaning unvalidated hypotheses or uncoordinated data sources may limit the final auditable report.