github-evidence-kit

Collect and verify forensic evidence from GitHub API, GH Archive, and local Git sources.

482|72|Updated Apr 5, 2026

Search Tags:#github #verification #evidence #forensics #osint #evidence-store

Ready to run

npx skills add https://github.com/deonmenezes/mantishack --skill github-evidence-kit-deonmenezes

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: github-evidence-kit
Source: https://github.com/deonmenezes/mantishack/tree/main/.claude/skills/oss-forensics/github-evidence-kit
Command: npx skills add https://github.com/deonmenezes/mantishack --skill github-evidence-kit-deonmenezes

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

GitHub-forensics workflows require collecting, organizing, and validating evidence from multiple sources (GitHub API, GH Archive, and local Git). This skill provides a unified approach to generate, load, and verify forensic artifacts while preserving provenance.

Core Features & Use Cases

Collect evidence from GitHub API, GH Archive, and local Git repositories.
Store, load, and verify evidence with a central EvidenceStore, enabling re-verification against original sources.
Supports events (Push, Issue, PR), observations, IOCs, and external articles.

Quick Start

Invoke the GitHub Evidence Kit to collect, store, and verify forensic evidence from GitHub API, GH Archive, and local Git repositories.

Frequently Asked Questions about github-evidence-kit

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

FAQPage Schema

How do I collect and verify GitHub forensic evidence from multiple sources?▼

To collect GitHub forensic evidence, you can identify and validate artifacts across the GitHub API, GH Archive, and local Git repositories. This process ensures structured JSON storage with schema validation and end-to-end verification against original sources.

What types of GitHub artifacts can be stored and re-verified as forensic evidence?▼

GitHub forensic evidence supports commits, issues, pull requests, files, forks, and related artifacts. It also handles events like Push, Issue, and PR actions, alongside observations, IOCs, and external articles using a central EvidenceStore for re-verification.

Does this forensics approach work with local Git repositories and the GH Archive?▼

Yes, GitHub forensic evidence collection works with local Git repositories, the GH Archive, and the GitHub API. It applies end-to-end verification to commits, issues, PRs, and files while preserving provenance through structured JSON storage.

Why do I need schema validation when storing GitHub forensic evidence?▼

Schema validation is needed for GitHub forensic evidence to ensure structured JSON storage remains consistent and reliable. It enforces data integrity across collected commits, issues, and PRs, enabling accurate re-verification against original sources.

What is the best way to preserve provenance during GitHub evidence collection?▼

The best way to preserve provenance during GitHub evidence collection is using a central EvidenceStore to load and verify forensic artifacts. This approach maintains source links for commits and PRs, enabling end-to-end re-verification against GitHub API and Git sources.

Are there limitations when collecting forensic evidence from GitHub forks?▼

While the skill collects and verifies evidence from GitHub forks, commits, and files, it requires access to the GitHub API, GH Archive, or local Git sources. Re-verification depends on the continued availability and accessibility of these original upstream sources.