oss-forensics

Investigate GitHub repositories for supply chain compromise using multi-source forensic evidence collection.

Updated Jun 5, 2026
One-click install
npx skills add https://github.com/xu1713/openhorse --skill oss-forensics-xu1713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/xu1713/openhorse/tree/main/openhorse/openhorse/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/xu1713/openhorse --skill oss-forensics-xu1713

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Detecting and proving open-source supply chain attacks is hard because attackers erase evidence through force-pushes, deleted issues, and rewritten git history. This Skill provides a structured 7-phase forensic workflow that recovers deleted commits, cross-references tamper-proof data sources, and produces evidence-backed investigation reports. ## Core Features & Use Cases - Deleted Commit Recovery: Recover force-pushed commits via direct GitHub URLs, the GitHub API, git fsck dangling objects, and Wayback Machine snapshots. - Multi-Source Evidence Collection: Coordinate five specialist investigators covering local git analysis, GitHub REST API, Wayback Machine CDX, GitHub Archive BigQuery, and IOC enrichment. - Hypothesis Validation with Anti-Hallucination Guardrails: Every claim must cite evidence IDs verified against a SHA-256 integrity-checked evidence store before entering the final report. - Use Case: A maintainer suspects a contributor's account was compromised and used to push a backdoored CI workflow. The Skill extracts IOCs, detects force-push events in GH Archive, recovers the erased commit, validates the compromise hypothesis, and generates a forensic report with a chain of custody. ## Quick Start Ask the agent to investigate a GitHub repository for supply chain compromise, for example by saying: investigate owner/repo for a supply chain attack and recover any deleted commits.

Frequently Asked Questions about oss-forensics

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

FAQPage Schema
How do I recover force-pushed commits from a GitHub repository?

Force-pushed commits remain on GitHub's servers until garbage collection. Recover them via the direct URL github.com/OWNER/REPO/commit/SHA.patch, the API endpoint /git/commits/SHA, or git fetch origin SHA in a local clone.

How to detect a supply chain attack in an open-source repository?

Query GitHub Archive via BigQuery for PushEvents with distinct_size=0 (force-push indicator), DeleteEvents, and MemberEvents. Cross-reference these against the GitHub API and local git history to find discrepancies indicating erased evidence.

Does GitHub Archive investigation require Google Cloud credentials?

Yes, BigQuery queries require Google Cloud credentials via gcloud auth application-default login. If unavailable, the investigation proceeds with the other four investigators: local git, GitHub API, Wayback Machine, and IOC enrichment.

Can deleted GitHub issues and pull requests be recovered?

Deleted issues and PRs do not appear in the GitHub API. Recover them through the Wayback Machine CDX API by querying archived snapshots of the issue or PR URL, or find their event history in GitHub Archive.

What are the limitations of git fsck for forensic analysis?

git fsck only finds dangling objects in your local clone, not on GitHub's servers. For server-side recovery of force-pushed commits, use direct commit URLs or the GitHub API before garbage collection runs, typically within 30-90 days.