investigate-repo

Audit third-party GitHub repositories for supply-chain risks via static analysis.

7|Updated May 28, 2026
One-click install
npx skills add https://github.com/zcaceres/skills --skill investigate-repo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: investigate-repo
Source: https://github.com/zcaceres/skills/tree/main/skills/investigate-repo
Command: npx skills add https://github.com/zcaceres/skills --skill investigate-repo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill eliminates the uncertainty of using unfamiliar third-party code by performing a deep, automated security audit to identify malicious patterns before you ever run the software.

Core Features & Use Cases

  • Malicious Pattern Detection: Scans for eval, obfuscated payloads, hardcoded exfiltration URLs, and dangerous install-time hooks.
  • Evidence-Based Verdicts: Provides a clear, defensible verdict (SAFE, SUSPICIOUS, DANGEROUS, INCONCLUSIVE) with specific file and line number citations.
  • Use Case: Before installing a new npm package or cloning a GitHub project, use this skill to verify that the repository does not contain hidden credential harvesters or unauthorized network beacons.

Quick Start

Invoke the investigate-repo skill by providing the GitHub URL of the repository you wish to audit.

Frequently Asked Questions about investigate-repo

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

FAQPage Schema
How do I audit a GitHub repository for malicious code before installing it?

Static analysis detects supply-chain risks like malicious install scripts and obfuscated code in third-party repositories. It targets unauthorized network exfiltration patterns through deep tree traversal and pattern matching, ensuring safety before you run the software.

Can I detect npm package supply-chain risks using static analysis?

Yes, you can detect npm package supply-chain risks using static analysis to scan for eval statements, unauthorized network beacons, and hidden credential harvesters. This provides an evidence-based verdict with specific file and line citations before installation.

Do I need ripgrep and GitHub CLI to scan third-party repositories for security risks?

Yes, ripgrep and GitHub CLI are required to execute deep tree traversal and pattern matching during the security audit. Git is also necessary to perform the comprehensive static analysis without executing the target code.

What is the best way to check for unauthorized network exfiltration in unfamiliar code?

The best way to check for unauthorized network exfiltration is automated static analysis that identifies hardcoded URLs and dangerous install-time hooks. This yields a defensible verdict with specific file and line number citations.

How do I perform a security audit on a GitHub repo without executing its code?

You perform a security audit without executing code by running static analysis and pattern matching across the repository's file tree. This safely identifies malicious patterns like obfuscated payloads and credential harvesters.

When should I use automated static analysis instead of manual code review for supply-chain security?

Automated static analysis is ideal when you need to quickly evaluate unfamiliar third-party code for supply-chain risks. It instantly provides evidence-based verdicts with specific file citations, eliminating the uncertainty of manual review before installation.