oss-forensics

Investigate GitHub repositories for supply chain attack evidence and generate forensic reports.

1|1|Updated May 25, 2026
One-click install
npx skills add https://github.com/aayushsoam/clawbot-agent --skill oss-forensics-aayushsoam
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-forensics
Source: https://github.com/aayushsoam/clawbot-agent/tree/main/optional-skills/security/oss-forensics
Command: npx skills add https://github.com/aayushsoam/clawbot-agent --skill oss-forensics-aayushsoam

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill provides a comprehensive framework for investigating and analyzing GitHub repositories to uncover supply chain attacks, recover deleted content, and generate forensic reports.

Core Features & Use Cases

  • Supply Chain Investigation: Multi-agent framework for researching open-source supply chain attacks.
  • Deleted Commit Recovery: Ability to recover deleted commits and detect force-pushes.
  • IOC Extraction: Extraction of Indicators of Compromise from various data sources.
  • Forensic Reporting: Generation of structured forensic reports with evidence citations.

Quick Start

To investigate a GitHub repository, use the oss-forensics skill with the command 'investigate this repository'.

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 evidence of a supply chain attack?

Recovering deleted commits involves analyzing local git history and utilizing the GitHub API to uncover force-pushes and deleted content. The investigation framework extracts this hidden evidence to reveal repository tampering.

Can I extract Indicators of Compromise from open-source repositories?

Yes, you can extract Indicators of Compromise from various repository data sources. The analysis gathers evidence from local git history, GitHub APIs, Wayback Machine, and BigQuery to identify malicious patterns.

What is the best way to generate a forensic report for repository investigation?

The best way to generate a forensic report is by using a multi-agent framework that aggregates evidence from multiple sources. It collects parallel inputs from git, APIs, and web archives to produce structured reports with evidence citations.

Do I need terminal and web capabilities to analyze deleted commits?

Yes, analyzing deleted commits requires terminal, web, file, and delegation capabilities. These permissions allow the system to execute local git commands, query the GitHub API, access the Wayback Machine, and run BigQuery.

How does Wayback Machine integration help uncover supply chain attacks?

Wayback Machine integration helps uncover supply chain attacks by retrieving historical snapshots of the repository. This allows the investigation to recover deleted content and track unauthorized modifications over time.

When should I use BigQuery for repository forensics?

You should use BigQuery for repository forensics when you need to analyze large-scale git history across multiple projects. It acts as a sub-agent to collect parallel evidence for complex supply chain investigations.