oss-forensics

Investigate GitHub repositories for supply chain attacks using git and GitHub API analysis.

Updated Jun 9, 2026
One-click install
npx skills add https://github.com/zhouboyu-xreal/Hermes-Memory --skill oss-forensics-zhouboyu-xreal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/zhouboyu-xreal/Hermes-Memory/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/zhouboyu-xreal/Hermes-Memory --skill oss-forensics-zhouboyu-xreal

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pypdf, pdfplumber, pdf2image, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive framework for investigating GitHub repositories for potential supply chain attacks, including deleted commit recovery, force-push detection, and structured forensic reporting.

Core Features & Use Cases

  • Deleted Commit Recovery: Identifies and recovers deleted commits and force-pushes.
  • Force-Push Detection: Detects and analyzes force-push events that may indicate malicious activity.
  • IOC Extraction: Extracts Indicators of Compromise (IOCs) such as commit SHAs, file paths, package names, and more.
  • Multi-Source Evidence Collection: Collects evidence from local git, GitHub API, Wayback Machine, and GitHub Archive.
  • Hypothesis Formation and Validation: Formulates and validates hypotheses based on collected evidence.
  • Structured Forensic Reporting: Generates detailed forensic reports with executive summaries, timelines, and recommendations.

Quick Start

Run the skill with the command: 'oss-forensics investigate this repository'

Frequently Asked Questions about oss-forensics

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

FAQPage Schema
How do I recover deleted commits in a GitHub repository to investigate a supply chain attack?

To investigate a supply chain attack, you can recover deleted commits by utilizing the GitHub API, GitHub Archive, and local git analysis to identify and extract overwritten history caused by force-push events.

What is force-push detection in open-source software forensics?

Force-push detection in open-source software forensics is the process of analyzing GitHub repositories to identify events where commit history was overwritten, which often indicates an attempt to hide malicious supply chain activity.

How do I extract Indicators of Compromise from a compromised GitHub repository?

You extract Indicators of Compromise by performing forensic analysis on local git and GitHub API data to pull out commit SHAs, file paths, and package names associated with the supply chain attack.

Do I need BigQuery access to perform GitHub repository forensics?

Yes, you need BigQuery access along with GitHub API credentials to enable full multi-source evidence collection from the GitHub Archive for comprehensive supply chain attack investigations.

Can I collect evidence from the Wayback Machine during an OSS supply chain investigation?

Yes, you can collect evidence from the Wayback Machine as part of a multi-source evidence gathering process that also queries local git, the GitHub API, and GitHub Archive to validate forensic hypotheses.

How do I generate a structured forensic report for a supply chain attack?

You generate a structured forensic report by formulating and validating hypotheses from collected evidence, producing detailed documentation that includes executive summaries, timelines, and security recommendations.