skills.rest
kotakbiasa
kotakbiasaCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

oss-forensics

Consolidate Git, GitHub API, Wayback, and GH Archive evidence into auditable forensic reports.

Updated Aug 27, 2026
Search Tags:#git#reporting#supply-chain#forensics#github-api#oss-forensics#evidence-store
One-click install
npx skills add https://github.com/kotakbiasa/hermes-agent --skill oss-forensics-kotakbiasa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/kotakbiasa/hermes-agent/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/kotakbiasa/hermes-agent --skill oss-forensics-kotakbiasa

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Supply chain security for open-source software is fragile and often under-detected. OSS projects can suffer deleted commits, force-pushed histories, and scattered evidence that complicates incident response. This skill provides a rigorous, multi-source framework to investigate repositories, recover vanished artifacts, and produce auditable forensic reports.

Core Features & Use Cases

  • Seven-phase investigation framework covering evidence gathering, IOC extraction, hypothesis formation and validation, and final reporting.
  • Multi-source integration: local git analysis, GitHub REST API, Wayback CDX, GH Archive, and an evidence store.
  • Secure, auditable reporting with chain-of-custody and redaction of secrets.

Quick Start

Create an investigation workspace, initialize the evidence store, and load the skill to begin Phase 0 initialization and Phase 1 data 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 deleted commits and force-push events in a GitHub repository?▼

OSS supply-chain forensics is the process of investigating open-source repositories to detect deleted commits, force-pushed histories, and scattered evidence. It works by consolidating data from Git, GitHub API, Wayback CDX, and GH Archive into a single auditable report for incident response.

How do I conduct a forensic investigation of an open-source supply chain incident?▼

Conducting a forensic investigation involves a seven-phase framework covering evidence gathering, IOC extraction, hypothesis formation and validation, and final reporting. You initialize an investigation workspace, load the evidence store, and collect data from local git, GitHub API, Wayback, and GH Archive.

Does the GitHub REST API provide enough data for supply-chain forensics on its own?▼

The GitHub REST API alone is insufficient for thorough supply-chain forensics because force-pushed histories and deleted commits often vanish from the live API. You must integrate local git data, Wayback CDX, and GH Archive to recover artifacts and validate hypotheses across multiple sources.

Can I use Wayback Machine and GH Archive to recover deleted git commits?▼

Yes, you can use Wayback CDX and GH Archive to recover deleted git commits by capturing historical snapshots and event logs that predate force-pushes. These sources feed into the evidence store, allowing you to reconstruct vanished artifacts and validate multi-source hypotheses for your report.

What's the best way to produce an auditable forensic report for an OSS incident?▼

The best way to produce an auditable forensic report is to use a framework that maintains a strict chain-of-custody through an evidence store and reporting template. It consolidates Git, GitHub API, Wayback, and GH Archive data while redacting secrets for secure output.

Do I need BigQuery access to investigate open-source repository incidents?▼

BigQuery access is optional for investigating open-source repository incidents. The core forensic framework relies on local git analysis, GitHub REST API, Wayback CDX, and GH Archive, but BigQuery can enhance GH Archive queries for large-scale event analysis.

Related Skills

Explore More Data & Analytics Skills→
gadievrongadievron
3.5k

oss-forensics/orchestration

Orchestrate OSS forensic investigations across public GitHub repositories with phase-driven workflows.

Community
Advanced
daemon-blockint-techdaemon-blockint-tech
7

digital-forensics-analyst

Identify and preserve forensic artifacts with chain-of-custody documentation.

Community
Advanced
Accelerated-InnovationAccelerated-Innovation
20

implementation-plan

Generate an evaluation-driven implementation plan with architecture mapping and task breakdown.

Official
Advanced
samuelmukotisamuelmukoti

oss-forensics

Reconstruct OSS supply-chain incidents from git history, GitHub API, Wayback, and BigQuery.

Community
Advanced