oss-forensics

Identify GitHub OSS supply chain compromises through multi-source evidence gathering.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/gqf2008/hermez-ai --skill oss-forensics-gqf2008
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/gqf2008/hermez-ai/tree/main/skills/security/oss-forensics
Command: npx skills add https://github.com/gqf2008/hermez-ai --skill oss-forensics-gqf2008

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and 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.

Core Features & Use Cases

  • 7-phase multi-agent investigation framework for researching open-source supply chain attacks.
  • Access to GitHub Archive, Wayback Machine, GitHub API, local git analysis, IOC extraction, evidence-backed hypothesis formation, and forensic report generation.
  • Anti-hallucination guardrails and strict evidence-citation requirements.

Quick Start

Use the oss-forensics skill to initialize a multi-source OSS supply chain investigation against a target repository.

Frequently Asked Questions about oss-forensics

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

FAQPage Schema
How do I investigate deleted commits and force-push history in a GitHub repository?

To investigate deleted commits and force-push history, this Skill recovers missing commits and detects force-push events by accessing the GitHub Archive and Wayback Machine, ensuring evidence-driven analysis of the repository timeline.

What is the best way to document a GitHub OSS supply chain compromise?

Documenting a GitHub supply chain compromise requires gathering multi-source evidence, extracting IOCs, and validating hypotheses. This Skill applies a 7-phase investigation framework to generate a structured forensic report with strict evidence citation.

How does forensic reporting handle secrets found during supply chain investigations?

Forensic reporting handles discovered secrets by applying redaction guardrails during evidence gathering. The final report ensures sensitive data is removed while maintaining the integrity of the cited supply chain attack evidence.

Can I use local git analysis alongside GitHub API data for OSS security forensics?

Yes, you can combine local git analysis with GitHub API data. The investigation framework cross-verifies evidence across local repositories, GitHub API, and historical archives to prevent hallucination and validate supply chain attack hypotheses.

When do I need multi-source evidence collection for open-source security analysis?

You need multi-source evidence collection when investigating suspected OSS security compromises. It allows you to recover deleted commits, extract IOCs, and cross-verify timelines using the Wayback Machine and GitHub Archive for accurate forensic reporting.