graph-evolution
SolidCompares Trailmark code graphs at two source code snapshots (git commits, tags, or directories) to surface security-relevant structural changes. Detects new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications that text diffs miss. Use when comparing code between commits or tags, analyzing structural evolution, detecting attack surface growth, reviewing what changed between audit snapshots, or finding security-relevant changes that text diffs miss.
Install
Quality Score: 90/100
Skill Content
Details
- Author
- trailofbits
- Repository
- trailofbits/skills
- Created
- 10 months ago
- Last Updated
- 6 days ago
- Language
- Python
- License
- CC-BY-SA-4.0
Similar Skills
Semantically similar based on skill content — not just same category
trailmark
Builds and queries multi-language source code graphs for security analysis. Includes pre-analysis passes for blast radius, taint propagation, privilege boundaries, and entry point enumeration. Use when analyzing call paths, mapping attack surface, finding complexity hotspots, enumerating entry points, tracing taint propagation, measuring blast radius, or building a code graph for audit prioritization. Supports 16 languages including Solidity, Cairo, Circom, Rust, Go, Python, C/C++, TypeScript.
graphtrail
Compatibility skill for structural code questions in an indexed repo. Use Brigade Code Graph through `brigade code` for callers, callees, impact, affected tests, context, cycles, and graph diffs. Never call the retired application or MCP server directly.
differential-review
Performs security-focused differential review of code changes. Adapts analysis depth to codebase size, uses git blame for context, calculates blast radius by counting callers, checks test coverage of modified code, and delivers a markdown report through `factory report`. Use when reviewing a PR, commit, or diff for security vulnerabilities, checking whether a change re-introduces a previously fixed bug, asking what else a change could break, or finding which modified code has no test covering it.