oss-forensics

Investigate OSS supply chain compromise across GitHub repositories with multi-source evidence collection.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a structured, end-to-end framework for investigating open-source supply chain attacks, enabling teams to systematically collect, verify, and report evidence across multiple data sources.

Core Features & Use Cases

  • 7-phase investigation framework (initialization, parallel evidence collection, consolidation, hypothesis, validation, final reporting, completion)
  • Multi-source integration: local Git data, GitHub REST API, GH Archive (BigQuery), Wayback Machine, IOC enrichment
  • Evidence registry and auditable chain-of-custody with guardrails to prevent hallucinations and ensure reproducibility
  • Generates a formal forensic report with executive summary, timeline, validated hypotheses, and recommendations

Quick Start

Create a new OSS-forensics investigation directory, initialize the evidence store, and load the forensic report template to begin.

Frequently Asked Questions about oss-forensics

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

FAQPage Schema
How do I investigate open-source supply chain attacks across multiple repositories?

To investigate open-source supply chain attacks, you can use a structured 7-phase framework that collects evidence across local Git data, GitHub API, GH Archive BigQuery, and Wayback Machine snapshots to produce defensible forensic findings.

What is the best way to collect forensic evidence of OSS compromise without hallucinated conclusions?

Collecting forensic evidence of OSS compromise safely requires an auditable evidence registry with enforced guardrails against hallucinated conclusions, coordinating phased evidence collection to ensure reproducibility and validated hypotheses.

How do I generate a structured forensic report for a GitHub repository compromise?

Generating a structured forensic report for a GitHub repository compromise involves consolidating multi-source evidence into a final document featuring an executive summary, validated timeline, and actionable recommendations.

Can I use Wayback snapshots and GH Archive data to trace a supply chain compromise?

Yes, you can use Wayback Machine snapshots and GH Archive BigQuery data alongside local git data and GitHub REST API queries to apply multi-source investigation techniques for tracing supply chain compromises.

Does OSS forensics require a specific evidence store setup before starting an investigation?

OSS forensics requires initializing a dedicated investigation directory and setting up an evidence store to maintain an auditable chain-of-custody before loading the forensic report template to begin.

What are the limitations of relying solely on local git data for supply chain forensics?

Relying solely on local git data limits supply chain forensics by missing external context, whereas integrating GitHub API, GH Archive, Wayback snapshots, and IOC enrichment provides a consolidated, defensible view of the compromise.