graph-evolution

Detect security-relevant structural changes in code graphs between two snapshots.

6.5k|561|Updated Jan 14, 2026
One-click install
npx skills add https://github.com/trailofbits/skills --skill graph-evolution-trailofbits
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: graph-evolution
Source: https://github.com/trailofbits/skills/tree/main/plugins/trailmark/skills/graph-evolution
Command: npx skills add https://github.com/trailofbits/skills --skill graph-evolution-trailofbits

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill identifies security-relevant structural changes in code graphs, enabling deeper security analysis and detection of issues missed by text diffs.

Core Features & Use Cases

  • Graph Comparison: Compare code graphs from different code snapshots to detect structural changes.
  • Security Analysis: Identify new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications.
  • Use Case: When analyzing the evolution of a codebase between two commits, this Skill can help uncover security vulnerabilities that text diffs might miss.

Quick Start

Use the graph-evolution skill to compare the code graph of a project between two commits.

Frequently Asked Questions about graph-evolution

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

FAQPage Schema
How do I detect security vulnerabilities in a codebase that text diffs miss?

To detect security vulnerabilities missed by text diffs, you compare code graphs between two code snapshots to identify structural changes like new attack paths, taint propagation changes, and blast radius growth.

How do I compare code graphs between two commits to find new attack paths?

You compare code graphs between two commits by analyzing structural changes to identify new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications.

Do I need trailmark to analyze codebase evolution and structural changes?

Yes, you need trailmark for codebase evolution analysis because it handles the graph building and pre-analysis required to detect security-relevant structural changes in code graphs.

What is structural code graph comparison and when do I need it for security analysis?

Structural code graph comparison detects security-relevant changes between code snapshots. You need it for security analysis when evaluating codebase evolution to uncover new attack paths and privilege boundary modifications.

Does graph comparison detect taint propagation changes and privilege boundary modifications?

Yes, graph comparison detects taint propagation changes and privilege boundary modifications by identifying security-relevant structural changes in code graphs between two code snapshots.

Best way to track blast radius growth and complexity shifts across codebase updates?

The best way to track blast radius growth and complexity shifts is comparing code graphs between two code snapshots to detect security-relevant structural changes throughout codebase evolution.