oss-forensics

Analyze GitHub repositories for supply chain attack indicators via API and git analysis.

4|Updated May 14, 2026
One-click install
npx skills add https://github.com/liumeixin/hermes-skills --skill oss-forensics-liumeixin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/liumeixin/hermes-skills/tree/main/security/oss-forensics
Command: npx skills add https://github.com/liumeixin/hermes-skills --skill oss-forensics-liumeixin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python, requests, bq, json, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill provides a comprehensive forensics investigation for GitHub repositories, helping to uncover and analyze supply chain attacks.

Core Features & Use Cases

  • Supply Chain Investigation: Analyzes GitHub repositories for signs of compromised dependencies or code.
  • Deleted Commit Recovery: Recovers deleted commits to uncover malicious activities.
  • Forensic Analysis: Performs in-depth analysis to identify compromised packages, maintainers, and malicious behavior.
  • Use Case: When a repository is suspected of being compromised, this Skill can be used to investigate and provide evidence of the attack.

Quick Start

To begin an investigation, run the following command:

hermes agent trigger oss-forensics investigate [repository_name]

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, run the trigger command with the repository name. The Skill analyzes compromised dependencies, force-pushes, and deleted commits to uncover malicious behavior.

Can I recover deleted commits to find malicious code in a compromised package?

Yes, you can recover deleted commits to find malicious code. The forensic analysis identifies compromised packages and maintainers by utilizing local git analysis alongside GitHub Archive and Wayback Machine data.

Do I need BigQuery access to analyze GitHub repository forensics?

Yes, you need BigQuery access for full GitHub repository forensics functionality. The investigation requires BigQuery to thoroughly analyze GitHub Archive data for indicators of a supply chain attack.

What is the best way to detect force-pushes indicating a compromised maintainer?

The best way to detect force-pushes from a compromised maintainer is using this Skill's forensic analysis. It queries the GitHub API and local git history to identify suspicious repository modifications.

Does this GitHub forensics Skill work with Python and requests?

Yes, this GitHub forensics Skill works with Python and requests. It relies on Python, the requests library, and json to execute scripts that investigate repositories for malicious supply chain activities.

Why does repository investigation require the Wayback Machine?

Repository investigation requires the Wayback Machine to retrieve historical snapshots of compromised dependencies. This helps uncover deleted commits and malicious code that supply chain attackers attempt to hide.

Related Skills