graph-evolution

Name: graph-evolution
Availability: InStock
Author: manuelbrandner85

Compare Trailmark code graphs across snapshots to detect security-relevant structural changes.

Updated Nov 23, 2025

Search Tags:#code analysis #security #audit #evolution #graph #trailmark

Ready to run

npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill graph-evolution-manuelbrandner85

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: graph-evolution
Source: https://github.com/manuelbrandner85/Weltenbibliothekapp/tree/main/.agents/skills/graph-evolution
Command: npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill graph-evolution-manuelbrandner85

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the problem of identifying security-relevant structural changes in codebases that traditional text-based diffs fail to detect, such as new attack paths or privilege boundary shifts.

Core Features & Use Cases

Structural Diffing: Compares code graphs to identify changes in complexity, blast radius, and taint propagation.
Security Auditing: Automatically surfaces new entrypoints and trust-boundary crossings between git commits or tags.
Use Case: Use this during a pre-release audit to verify that refactoring hasn't inadvertently created new attack paths or removed critical security validation logic.

Quick Start

Run the graph evolution skill to compare the structural differences between the current branch and the previous release tag.

Frequently Asked Questions about graph-evolution

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

FAQPage Schema

How do I detect new attack paths introduced by code refactoring?▼

Structural code graph diffing surfaces security-relevant changes by comparing two source code snapshots to identify new attack paths, complexity shifts, blast radius growth, and taint propagation changes that text-based diffs miss.

How do I audit security blast radius changes between git commits?▼

Run a structural graph comparison between git tags or commits to automatically audit security blast radius growth, taint propagation changes, and privilege boundary modifications across your codebase snapshots.

Do I need Python and Trailmark to analyze code structure for security vulnerabilities?▼

Yes, analyzing code structure for security vulnerabilities requires the trailmark tool and a Python environment to execute structural analysis and generate security reports for your codebase.

What is the best way to check for privilege boundary modifications before a release?▼

The best way to check for privilege boundary modifications pre-release is comparing Trailmark code graphs between your current branch and the previous release tag to verify refactoring hasn't removed critical security validation logic.

Why does my text-based diff miss new security vulnerabilities in refactored code?▼

Text-based diffs miss security vulnerabilities because they cannot detect structural changes in code graphs like new attack paths, taint propagation shifts, or privilege boundary modifications that structural graph comparison surfaces.