oss-forensics

Consolidate OSS forensics data from GitHub repositories to detect supply-chain threats.

Updated Apr 16, 2026

Search Tags:#automation #git #investigation #evidence #supply-chain #forensics #oss

Ready to run

npx skills add https://github.com/jacardl/New-Radar --skill oss-forensics-jacardl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/jacardl/New-Radar/tree/main/backend/frameworks/hermes-agent/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/jacardl/New-Radar --skill oss-forensics-jacardl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Detecting and documenting open-source supply-chain incidents requires collecting and correlating evidence from multiple sources, reconstructing timelines, and producing auditable reports that respect disclosure guardrails.

Core Features & Use Cases

Unified evidence collection: aggregates data from local Git, GitHub REST API, GH Archive, and Wayback Machine to support end-to-end forensic investigations.
Recovery and verification capabilities: detects force-pushes, deleted issues/PRs, and reconstructs deleted content with cross-source verification.
IOC enrichment and reporting: extracts IOCs from repositories, enriches them from passive sources, and generates structured forensic reports with chain-of-custody.

Quick Start

Identify a target repository and run an end-to-end OSS forensic investigation to generate a report.

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 threats?▼

To investigate GitHub repository supply-chain threats, you consolidate forensic data from local Git, GitHub API, GH Archive, and Wayback Machine to detect force-pushes, deleted issues/PRs, and extract IOCs into a structured auditable report.

Can I detect deleted issues and force-pushes in open-source repositories?▼

Yes, detecting deleted issues and force-pushes in open-source repositories is possible by cross-referencing local Git data with GitHub API and GH Archive to reconstruct deleted content and verify evidence across multiple sources.

What is the best way to collect forensic evidence from Git and GitHub?▼

The best way to collect forensic evidence from Git and GitHub is to aggregate data across local Git, GitHub REST API, GH Archive, and Wayback Machine, enforcing evidence verification and secret redaction to maintain a proper chain-of-custody.

Do I need GitHub API access to reconstruct deleted repository content?▼

You need GitHub API access alongside local Git data, GH Archive, and Wayback Machine to cross-verify and reconstruct deleted repository content, ensuring the investigation report remains auditable and verified across sources.

How does IOC extraction work for supply-chain threat detection?▼

IOC extraction for supply-chain threat detection works by pulling indicators of compromise from repository data, enriching them from passive sources, and generating a structured forensic report that enforces redaction of secrets and chain-of-custody.

What are the limitations of open-source supply-chain forensics?▼

Open-source supply-chain forensics limitations include dependency on cross-source availability from GH Archive and Wayback Machine to verify deleted content, and the strict requirement to enforce evidence verification and secret redaction before reporting.