oss-forensics

Analyze GitHub repositories for supply chain attacks using multi-source evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python3, bq, git, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This skill provides a structured, evidence-based framework for investigating potential open-source supply chain compromises, ensuring that forensic findings are verifiable and reproducible.

Core Features & Use Cases

  • Multi-Source Investigation: Correlates data from local git repositories, the GitHub API, the Wayback Machine, and the GitHub Archive (BigQuery).
  • Evidence-First Reporting: Enforces strict anti-hallucination guardrails, requiring every claim to be backed by a unique, verifiable evidence ID.
  • Use Case: If a repository suddenly force-pushes history or a maintainer account shows anomalous activity, this skill helps you recover deleted commits, identify Indicators of Compromise (IOCs), and generate a professional forensic report.

Quick Start

Use the oss-forensics skill to investigate the repository owner/repo for potential supply chain compromise.

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 attack?

To investigate a GitHub repository for a supply chain attack, you can run a multi-agent forensic analysis that collects evidence from local git, GitHub API, Wayback Machine, and BigQuery to reconstruct incident timelines and identify Indicators of Compromise.

Can I recover deleted git commits to find evidence of a compromised maintainer account?

Yes, you can recover deleted git commits to find evidence of a compromised maintainer account by correlating anomalous repository activity with historical data from the Wayback Machine and GitHub Archive.

What is the best way to generate verifiable forensic reports for open-source compromises?

The best way to generate verifiable forensic reports for open-source compromises is to enforce strict anti-hallucination guardrails, requiring every claim to be backed by a unique, verifiable evidence ID collected during the investigation.

Do I need BigQuery to detect force-pushed history in a git repository?

Yes, BigQuery is used to query the GitHub Archive for anomalous historical events, which helps validate whether force-pushed history in a git repository indicates a potential supply chain compromise.

How does evidence-backed hypothesis validation work for open-source security incidents?

Evidence-backed hypothesis validation for open-source security incidents works by cross-referencing local git artifacts with external sources like the GitHub API, ensuring every identified Indicator of Compromise is reproducible before generating a structured report.