graph-evolution

To detect new attack paths in code between git commits, you can analyze code graph evolution to identify security-relevant structural changes that text diffs miss. This includes spotting new attack paths, taint propagation changes, and privilege boundary modifications.

Code graph evolution analysis finds security-relevant structural changes such as new attack paths, complexity shifts, blast radius growth, taint propagation changes, and privilege boundary modifications that traditional text diffs often miss.

Yes, you need trailmark to analyze code graph evolution because it is required for building and analyzing the code graphs used to identify security-relevant changes between git commits or tags.

Yes, you can use code graph analysis for codebase security audits by comparing code between commits or tags. It detects structural changes like increased complexity and blast radius growth that introduce security vulnerabilities.

Text diff misses security-relevant changes because it only shows line-level modifications, whereas code graph evolution analysis maps structural relationships to detect new attack paths, complexity shifts, and blast radius growth across the codebase.