oss-forensics

Investigate GitHub repositories for supply chain compromise and recover deleted evidence.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve? Open-source supply chain attacks often involve erased commits, deleted issues, and rewritten git history that hide malicious activity. This Skill provides a structured 7-phase forensic framework to investigate GitHub repositories, recover deleted evidence, and produce evidence-backed reports without hallucinated claims. ## Core Features & Use Cases - Multi-Source Evidence Collection: Coordinates five specialist investigators covering local git analysis, GitHub REST API, Wayback Machine, GitHub Archive via BigQuery, and IOC enrichment. - Deleted Commit Recovery: Recovers force-pushed commits via direct GitHub URLs, API git endpoints, git fetch by SHA, and dangling commit detection with git fsck. - Hypothesis Validation with Anti-Hallucination Guardrails: Every claim must cite evidence IDs verified against a SHA-256 integrity-checked evidence store, with mechanical validation before acceptance. - Use Case: A maintainer suspects a contributor's account was compromised and used to push a backdoored workflow file. The Skill extracts IOCs, queries GH Archive for force-push events, recovers the erased commit, validates the compromise hypothesis, and generates a forensic report with a full 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 suspicious force-pushes 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. Access 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 compromise in a GitHub repo?▼

Query GitHub Archive via BigQuery for PushEvents with distinct_size=0 (force-push indicator), DeleteEvents for branches, and MemberEvent permission changes. Cross-reference with the GitHub API to find commits present in archive events but missing from current history.

Does GitHub Archive investigation require Google Cloud credentials?▼

Yes, BigQuery queries against the githubarchive dataset require a Google Cloud account with BigQuery enabled. If unavailable, the other four investigators (local git, GitHub API, Wayback Machine, IOC enrichment) still cover most investigation needs.

Can deleted GitHub issues and pull requests be recovered?▼

Deleted issues and PRs do not appear in the GitHub API, but the Wayback Machine CDX API often has archived snapshots. Query web.archive.org/cdx/search/cdx for the issue or PR URL, then fetch the best snapshot by timestamp.

What are the limitations of git fsck for finding deleted commits?▼

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, the GitHub API git endpoints, or git fetch by SHA before garbage collection runs.