skills.rest
thisismynewfmail-ui
thisismynewfmail-uiCOMMUNITY
Explore all skills by this author →
GitHub

oss-forensics

Coordinate multi-source OSS forensics investigations to document supply-chain risks in GitHub repositories.

Updated Apr 12, 2026
Search Tags:#investigation#github#evidence#hypothesis#report#forensics#oss
One-click install
npx skills add https://github.com/thisismynewfmail-ui/Monika-agent --skill oss-forensics-thisismynewfmail-ui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/thisismynewfmail-ui/Monika-agent/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/thisismynewfmail-ui/Monika-agent --skill oss-forensics-thisismynewfmail-ui

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Investigates and documents OSS supply-chain risks in GitHub repositories by coordinating an end-to-end forensic workflow that aggregates evidence from multiple sources.

Core Features & Use Cases

  • 7-phase multi-agent investigation framework coordinating Local Git, GitHub API, Wayback Machine, GH Archive, and IOC enrichment.
  • Centralized evidence store with cross-source correlation, hypothesis formation, and validation to produce defensible final reports.
  • Use cases include recovering deleted content, tracing force-push events, and validating supply-chain compromise scenarios across open-source projects.

Quick Start

Start an OSS-forensics investigation by targeting a repository and running the multi-phase workflow to generate an evidence-backed 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 OSS supply-chain risks in GitHub repositories?▼

OSS supply-chain risk investigation aggregates cross-source evidence from local git history, GitHub REST API, Wayback Machine archives, and GH Archive BigQuery data to document potential compromises. It correlates findings to validate hypotheses and generate defensible forensic reports.

Can I trace force-push events and recover deleted content from git history?▼

Tracing force-push events and recovering deleted content is possible by coordinating local git history with GitHub REST API data. The investigation framework cross-references these sources to reconstruct repository modifications and document evidence of overwritten commits.

What is the best way to coordinate forensics across local git and Wayback Machine archives?▼

Coordinating forensic investigations across local git and Wayback Machine archives uses a centralized evidence store to correlate timestamps and repository states. This multi-source approach ensures defensible validation of supply-chain compromise scenarios.

Does OSS forensics support IOC enrichment for GitHub repository investigations?▼

IOC enrichment is supported within the forensic workflow to enhance supply-chain risk identification. It integrates with local git history, GitHub API data, and GH Archive BigQuery data to assemble cross-source evidence for hypothesis validation.

How do I formulate and validate hypotheses for a supply-chain compromise scenario?▼

Hypothesis formulation and validation occur within a structured forensic framework that enforces evidence-collection guardrails. It aggregates correlated data from local git, GitHub API, and Wayback Machine to test compromise scenarios against documented cross-source evidence.

What limitations exist when using GH Archive BigQuery data for repository forensics?▼

GH Archive BigQuery data provides event-level forensic evidence but requires correlation with local git history and GitHub REST API data to validate hypotheses. The framework enforces evidence-collection guardrails to ensure cross-source findings remain defensible.

Related Skills

Explore More Education & Research Skills→
NousResearchNousResearch
227.8k

github-repo-management

Manage GitHub repositories via gh CLI or REST API.

Official
Intermediate
gadievrongadievron
3.5k

oss-forensics/orchestration

Orchestrate OSS forensic investigations across public GitHub repositories with phase-driven workflows.

Community
Advanced
gquthiergquthier
14

oss-forensics

Correlate Git, GitHub API, archive, and IOC evidence to assess repository compromise.

Community
Advanced
redhat-etredhat-et
1

investigate-incident

Investigate platform incidents by gathering evidence and generating root cause documentation.

Official
Advanced