skills.rest
ChimeraFoundationa
ChimeraFoundationaCOMMUNITY
Explore all skills by this author →
GitHub

oss-forensics

Aggregate git history, GitHub API, Wayback Machine, and IOC evidence for OSS investigations.

Updated Mar 22, 2026
Search Tags:#investigation#github#reporting#evidence#supply-chain#forensics#oss
One-click install
npx skills add https://github.com/ChimeraFoundationa/Agentx --skill oss-forensics-chimerafoundationa
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/ChimeraFoundationa/Agentx/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/ChimeraFoundationa/Agentx --skill oss-forensics-chimerafoundationa

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

OSS-focused investigations are often manual, fragmented, and time-consuming. This skill streamlines supply chain forensics on GitHub repositories by orchestrating evidence collection across multiple data sources, including git history, GitHub API, Wayback Machine, GitHub Archive, and IOC enrichment, and by guiding hypothesis formation and structured reporting.

Core Features & Use Cases

  • End-to-end OSS forensic investigations: evidence collection, cross-source correlation, hypothesis validation, and final reporting.
  • Detects force-push, deleted content, IOCs, and provenance changes to protect open-source ecosystems; ideal for maintainers, researchers, and security teams.
  • Supports multi-phase workflows with an evidence store, chain-of-custody logs, and redact capabilities for sensitive data.

Quick Start

Initialize a new OSS forensics investigation for 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 GitHub repository for supply-chain security incidents?▼

OSS supply-chain investigations on GitHub repositories are conducted by aggregating evidence from local git history, GitHub API, Wayback Machine, GH Archive, and IOC enrichment to detect force-pushes, deleted issues, and anomalous contributor activity.

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

Yes, detecting force-pushes, deleted issues, and deleted pull requests is a core capability of OSS supply-chain forensics, achieved by cross-referencing local git history with GitHub API data and Wayback Machine archives.

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

The best way to collect forensic evidence is using an end-to-end investigation workflow that features an evidence store and chain-of-custody logs to aggregate and verify data from GitHub API, Wayback Machine, and GH Archive.

How do I generate a structured forensic report for an open-source supply-chain incident?▼

Structured forensic reporting for supply-chain incidents is generated by guiding hypothesis formation and cross-source verification after collecting evidence, utilizing redaction capabilities for sensitive data.

Does OSS forensics support multi-phase investigation workflows with IOC enrichment?▼

Yes, OSS forensics supports multi-phase investigation workflows that include IOC enrichment, cross-source correlation, and hypothesis validation to ensure comprehensive evidence collection and formal reporting.

Why do I need chain-of-custody logs for open-source repository investigations?▼

Chain-of-custody logs are required to maintain evidence integrity during open-source repository investigations, ensuring that collected data from git history and external sources remains verifiable for formal forensic reporting.

Related Skills

Explore More Education & Research Skills→
afel6afel6

github-auth

Configure GitHub authentication for git or gh CLI access.

Community
Intermediate
jeremylongshorejeremylongshore
2.6k

responding-to-security-incidents

Generate incident response playbooks for containment, eradication, and recovery.

Community
Advanced
SriRamkunamsettySriRamkunamsetty

oss-forensics

Correlate open-source supply chain compromise evidence across GitHub repositories.

Community
Advanced
LynxLabVNLynxLabVN

oss-forensics

Investigate GitHub repositories for supply chain attacks using git and API analysis.

Official
Advanced