oss-forensics

Conduct end-to-end OSS supply chain forensic investigations across GitHub repositories.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill oss-forensics-rawgrowth-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/Rawgrowth-Consulting/rawclaw-agent/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/Rawgrowth-Consulting/rawclaw-agent --skill oss-forensics-rawgrowth-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Supply chain security incidents in open-source projects require structured, repeatable investigations that collect evidence, reason across data sources, and produce a defensible report.

Core Features & Use Cases

  • Phase-guided, multi-source investigations across GitHub repos
  • Evidence-driven hypothesis formation and validation
  • Final forensic reporting with citations to evidence IDs

Quick Start

Ask the agent to start OSS forensics on a target repository.

Frequently Asked Questions about oss-forensics

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I investigate an open-source supply chain incident on GitHub?

Open-source supply chain investigations are conducted using a 7-phase forensic framework that extracts IOCs, queries the GitHub API and local git data, and consolidates evidence into a defensible report with cited evidence IDs.

What data sources can I use for OSS forensics and evidence collection?

OSS forensics evidence collection utilizes local git data, GitHub API, Wayback Machine, and GH Archive to perform cross-source verification and IOC enrichment during the investigation.

How does hypothesis validation work in supply chain security investigations?

Hypothesis validation in supply chain security investigations works by forming theories from consolidated multi-source evidence and rigorously testing them against cross-referenced data before final reporting.

Can I generate a defensible disclosure report for a compromised repository?

Yes, you can generate a defensible disclosure report for a compromised repository; the final forensic output references specific EV-IDs, enforces strict evidence tracking, and includes redacted secrets.

What is the best way to ensure redaction of secrets during open-source forensics?

The best way to ensure redaction of secrets during open-source forensics is to apply strict evidence tracking and cross-source verification rules throughout the 7-phase investigation and final reporting.