oss-forensics

Analyze GitHub repositories to detect supply-chain compromises and generate structured forensic reports.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill provides a systematic framework for open-source forensics on GitHub repositories, enabling investigators to collect evidence, form testable hypotheses, and deliver structured forensic reports.

Core Features & Use Cases

  • Multi-source evidence collection from local git history, GitHub REST API, Wayback Machine, and GH Archive to reconstruct events.
  • Evidence-driven hypothesis formation with a built-in chain-of-custody and verification workflow.
  • Comprehensive final reports including executive summaries, timelines, validated hypotheses, and an auditable evidence registry.

Quick Start

Provide a target repository and an optional time window to begin an investigation, and the system will initialize the workspace, collect evidence, and generate a 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 perform a forensic investigation on a GitHub repository?

To perform a forensic investigation, you provide a target GitHub repository and an optional time window. The system initializes a workspace, collects multi-source evidence, and generates a structured forensic report with validated conclusions.

What sources are used for open-source forensics evidence collection?

Open-source forensics evidence collection uses local git history, GitHub REST API, Wayback Machine, and GH Archive. These coordinated sources reconstruct events to detect supply-chain compromises within the target repository.

How does this method ensure forensic evidence is not hallucinated or tampered with?

This method enforces evidence citations and anti-hallucination guardrails to prevent fabricated conclusions. It uses a tamper-evident evidence store with hash integrity checks to maintain a verifiable chain-of-custody throughout the investigation.

Can I investigate supply-chain compromises across a specific time window in git history?

Yes, you can investigate supply-chain compromises by providing an optional time window when starting the analysis. The system coordinates evidence from git history and GitHub archives to reconstruct events within that specified period.

What is included in the final structured forensic report?

The final structured forensic report includes executive summaries, reconstructed timelines, validated hypotheses, and an auditable evidence registry. This structure ensures that all conclusions are backed by verifiable evidence.

Do I need any external dependencies to run a GitHub repository forensics analysis?

No external dependencies are required to run a GitHub repository forensics analysis. The system operates independently to collect evidence from local git history and external APIs, generating structured reports without additional environment setup.