oss-forensics

Recover deleted commits and detect force-push events in GitHub repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Supply chain investigation, evidence recovery, and forensic analysis for GitHub repositories. Covers deleted commit recovery, force-push detection, IOC extraction, multi-source evidence collection, hypothesis formation/validation, and structured forensic reporting. Inspired by RAPTOR's 1800+ line OSS Forensics system.

Core Features & Use Cases

  • 7-phase multi-agent investigation framework for researching open-source supply chain attacks.
  • Recovery of deleted commits, detection of force-push events, IOC extraction, evidence-backed hypothesis formation and validation, and final forensic reporting.
  • Multi-source evidence collection across GitHub, GitHub Archive, Wayback Machine, and local git repositories.
  • Guided hypothesis validation and a structured final report to support responsible disclosure.

Quick Start

Invoke the OSS Forensics skill against a target repository to start Phase 0 initialization and begin evidence collection.

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 compromised open-source supply chain on GitHub?

Supply chain forensics identifies compromises by recovering deleted commits and detecting force-push events. It applies a structured 7-phase investigation workflow to collect evidence from Git, APIs, archives, and logs, validating hypotheses to produce a forensic report.

Can I recover deleted Git commits and detect force-push events during an investigation?

Yes, recovering deleted Git commits and detecting force-push events are core phases of this investigation workflow. The process collects evidence from local git data and GitHub APIs to extract IOCs and validate hypotheses about repository compromises.

What data sources do I need for open-source supply chain forensics?

Open-source supply chain forensics requires access to local git data, the GitHub REST API, archive services like the Wayback Machine and GH Archive, and a centralized evidence store. These sources enable cross-source validation during the investigation.

What is the best way to extract IOCs from a compromised GitHub repository?

The best way to extract IOCs from a compromised GitHub repository is using a structured multi-phase forensic workflow. This approach collects evidence across GitHub, GitHub Archive, and Wayback Machine to form and validate evidence-backed hypotheses.

How do I generate a structured forensic report for responsible disclosure?

To generate a structured forensic report for responsible disclosure, you complete a guided 7-phase investigation workflow. This process validates hypotheses using multi-source evidence collection from Git, APIs, and archives to support your final reporting.