oss-forensics

Name: oss-forensics
Availability: InStock
Author: Nitish

Collect and analyze evidence from GitHub repositories for supply chain attack investigations.

Updated Jun 26, 2026

Search Tags:#GitHub #evidence collection #forensic analysis #repository security #supply chain investigation

Ready to run

npx skills add https://github.com/NITISH-gitbit/hermes-custom --skill oss-forensics-nitish-gitbit

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/NITISH-gitbit/hermes-custom/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/NITISH-gitbit/hermes-custom --skill oss-forensics-nitish-gitbit

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 streamlines the process of investigating and analyzing GitHub repositories for signs of supply chain attacks and forensic anomalies, providing a comprehensive toolset for evidence collection, analysis, and reporting.

Core Features & Use Cases

Supply Chain Investigation: Identifies and analyzes deleted commits, force-pushes, and other anomalies that may indicate a compromised repository.
Evidence Collection: Collects evidence from multiple sources, including GitHub Archive, Wayback Machine, GitHub API, local git repositories, and various public databases.
Hypothesis Formation and Validation: Facilitates the creation and validation of hypotheses through evidence-based analysis.
Structured Reporting: Generates detailed forensic reports with timelines, validated hypotheses, and evidence registry.

Quick Start

Run the 'oss-forensics' skill to begin an investigation on the repository 'OWNER/REPO'.

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 supply chain attacks?▼

To investigate a GitHub repository for supply chain attacks, you can automate evidence collection from the GitHub Archive, Wayback Machine, and GitHub API. This process identifies deleted commits and force-pushes to analyze forensic anomalies and generate structured reports.

What is forensic analysis of deleted commits and force-pushes in Git?▼

Forensic analysis of deleted commits and force-pushes in Git is the process of identifying compromised repository anomalies. It involves collecting evidence from public databases and local git repositories to form and validate hypotheses about supply chain incidents.

Do I need Python and external API access to collect GitHub forensic evidence?▼

Yes, you need Python and access to external APIs to collect GitHub forensic evidence. The automated evidence collection scripts utilize external sources like the GitHub Archive and Wayback Machine, requiring dependencies such as pypdf, pdfplumber, and pdf2image for analysis.

Can I use the Wayback Machine and GitHub Archive for repository security investigations?▼

Yes, you can use the Wayback Machine and GitHub Archive for repository security investigations. They serve as primary sources for collecting historical evidence, allowing you to track deleted commits and validate hypotheses regarding supply chain attacks.

What's the best way to report supply chain investigation findings?▼

The best way to report supply chain investigation findings is by generating structured forensic reports. These reports include detailed timelines, validated hypotheses, and an evidence registry compiled from local git repositories and public databases.

Why does my GitHub repository forensic analysis show anomalies in force-pushes?▼

Your GitHub repository forensic analysis shows anomalies in force-pushes because they often indicate a compromised repository. Investigating these force-pushes requires collecting evidence from the GitHub API and local git repositories to determine if a supply chain attack occurred.