oss-forensics

Name: oss-forensics
Availability: InStock
Author: adm-humanerd

Consolidate OSS supply-chain attack evidence from GitHub repositories using multi-source data.

Updated Aug 27, 2026

Search Tags:#investigation #github #archive #supply-chain #forensics #oss #evidence-store

Ready to run

npx skills add https://github.com/adm-humanerd/drewgent --skill oss-forensics-adm-humanerd

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

OSS-forensics provides a structured framework to systematically investigate open-source supply-chain attacks by coordinating multi-source evidence collection, hypothesis creation, and formal reporting.

Core Features & Use Cases

It orchestrates a 7-phase investigative workflow that spans GitHub Archive, Wayback Machine, GitHub REST API, local Git analysis, IOC enrichment, hypothesis validation, and final forensic reporting. Typical use cases include recovering deleted commits, detecting force-push events, retrieving archived issues/PRs, and generating a validated forensic report for disclosure and remediation.

Quick Start

Initiate a cross-source OSS-forensics investigation by collecting evidence from local git data, GitHub API, archives, and IOC enrichment to produce a validated final 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 deleted commits and force-push events in GitHub repositories?▼

To investigate deleted commits and force-push events, you can orchestrate a multi-source forensic workflow that queries the GitHub REST API and local git data to recover overwritten history and consolidate it into a structured evidence store.

Can I retrieve archived GitHub issues or PRs using the Wayback Machine for supply-chain forensics?▼

Yes, supply-chain forensics can retrieve archived GitHub issues or PRs by querying the Wayback CDX API for archived repository content, integrating the recovered artifacts into a validated evidence store for formal reporting.

What data sources do I need to uncover open-source supply-chain attack traces?▼

Uncovering open-source supply-chain attack traces requires querying multi-source data including GitHub REST API, local git data, Wayback CDX API, and BigQuery for GH Archive events to form evidence-backed hypotheses.

Does OSS supply-chain forensics require BigQuery access for GitHub Archive analysis?▼

Yes, GitHub Archive analysis requires BigQuery access to systematically query historical GH Archive events, which is essential for reconstructing repository timelines and detecting anomalous supply-chain activities.

How do I validate hypotheses during an OSS supply-chain investigation?▼

Validating hypotheses during an OSS supply-chain investigation involves consolidating multi-source evidence from archived content and IOC enrichment into a structured evidence store, enabling cross-verification before generating a final forensic report.

What is the best way to generate a forensic report for an open-source supply-chain attack?▼

Generating a forensic report for an open-source supply-chain attack is best done by orchestrating a 7-phase investigative workflow that collects, validates, and consolidates multi-source evidence into formal documentation for disclosure and remediation.