oss-forensics

Name: oss-forensics
Availability: InStock
Author: zulumonkeymetallic

Correlate GitHub API, Archive, Wayback Machine, and local git evidence into a structured investigation report.

Updated Aug 23, 2026

Search Tags:#timeline #github #reporting #supply-chain #forensics #oss-forensics #evidence-registry

Ready to run

npx skills add https://github.com/zulumonkeymetallic/bob --skill oss-forensics-zulumonkeymetallic

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/zulumonkeymetallic/bob/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/zulumonkeymetallic/bob --skill oss-forensics-zulumonkeymetallic

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Supply chain investigations require combining data from multiple sources, recovering deleted artifacts, and producing defensible forensic reports. This skill automates evidence collection, cross-source correlation, and hypothesis-driven reporting for OSS repositories.

Core Features & Use Cases

Multi-source forensics: local git analysis, GitHub API, GH Archive, and Wayback Machine traces.
Evidence registry and chain-of-custody generation for reproducible investigations.
Forensic reporting templates and hypothesis validation workflows for OSS supply chains.

Quick Start

Start a new OSS forensics investigation on a target repository and begin evidence collection.

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 compromised open-source repository and recover deleted artifacts?▼

Open-source supply chain forensics identifies, collects, and correlates evidence across GitHub API, GitHub Archive, Wayback Machine, and local git to determine if a repository is compromised and reconstruct an accurate incident timeline.

How do I reconstruct a git commit timeline after a force-push event?▼

To reconstruct a git commit timeline after a force-push event, cross-reference local git history with GitHub Archive and Wayback Machine traces to recover overwritten commits and establish a defensible chronological sequence of repository changes.

Can I extract indicators of compromise from GitHub repositories?▼

Yes, you can extract indicators of compromise from GitHub repositories by applying multi-source forensic analysis to trace malicious commits, anomalous metadata, and unauthorized modifications across both live and archived data sources.

Does this supply chain investigation workflow require external dependencies?▼

No, this supply chain investigation workflow requires no external dependencies to start, as it directly queries GitHub API, GitHub Archive, and Wayback Machine traces while enforcing data redaction and cross-source verification guardrails.

What is the best way to generate a defensible forensic report for an OSS supply chain incident?▼

The best way to generate a defensible forensic report for an OSS supply chain incident is to use an evidence registry and chain-of-custody generation workflow that enforces evidence citation and hypothesis validation across multiple data sources.