oss-forensics

Automates OSS forensics investigations across GitHub repositories using git data and APIs.

1.2k|116|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/math-inc/OpenGauss --skill oss-forensics-math-inc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/math-inc/OpenGauss/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/math-inc/OpenGauss --skill oss-forensics-math-inc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OSS project supply chain investigations require coordinating evidence from multiple sources, preserving chain-of-custody, and producing defensible reports.

Core Features & Use Cases

  • Multi-source evidence collection (local git, GitHub API, Wayback, GH Archive) with cross-source verification.
  • Phase-driven investigation workflow (initialization, evidence consolidation, hypothesis formation, validation, and reporting).
  • Automated and auditable evidence registry with a formal report template.

Quick Start

Initiate a new OSS-forensics investigation against a target GitHub repository and begin collecting cross-source evidence.

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 security issues?

OSS supply chain forensics involves collecting and cross-verifying evidence from local git, GitHub API, and web archives to coordinate investigations and produce defensible forensic reports with a preserved chain-of-custody.

How can I recover commits lost during a force-push on GitHub?

Force-push recovery is supported by extracting evidence from local git data and GitHub API sources, consolidating artifacts into an auditable registry, and validating hypotheses through a phase-driven investigation workflow.

What is the best way to extract IOCs from open source repositories for forensics?

IOC extraction is performed by applying a phase-driven investigation workflow that collects cross-source evidence from GitHub repositories and web archives, validating indicators before incorporating them into a formal forensic report.

Does this forensics workflow support querying GitHub Archive data in BigQuery?

BigQuery access is optionally supported for querying GitHub Archive data, complementing local git, GitHub API, and Wayback evidence collection to enhance cross-source verification during supply chain investigations.

Can I use this for cross-source evidence collection across multiple GitHub repositories?

Cross-source evidence collection across GitHub repositories is the core capability, automating the consolidation of artifacts from local git, GitHub API, and web archives into an auditable evidence registry with formal reporting.