restrict transitive traversal to call edges#32
Merged
tob-scott-a merged 1 commit intotrailofbits:mainfrom Apr 29, 2026
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
reachable_from,ancestors_of,paths_betweenand entrypoint path queries were traversing every edge in the graph. Structural edges like CONTAINS would thus show up as call reachability.This changes transitive traversal to use a call-only graph and updates blast-radius preanalysis to use the same call-only view.
Let me know if the test changes aren't needed, great project btw.
AI Disclosure: This code was written with ChatGPT 5.5 (Codex) and the changes were reviewed by ChatGPT 5.5 (Codex) & Gemini 3.1 Pro (Jules).