endor-fetch-and-search-call-graph

Static symbol reachability determines whether a specific callable in your code can invoke another through direct edges or multi-hop paths. It uses decoded call graph artifacts and method-id joins to trace dependencies across wrapper methods.

You can decode zstd call graph artifacts by fetching the project's exported graph bundles and decompressing the payloads into searchable callable and edge JSON. This decoded JSON is required to perform accurate method-id joins and path searches.

Yes, you can trace multi-hop dependencies hidden by wrapper methods by running safe breadth-first searches on the decoded call graph. This approach traverses multiple edges to reveal the actual static symbol-to-symbol dependency chain.

Yes, accurate static call graph analysis requires package-version scoped graph selection to ensure method-id joins and direct-edge checks reflect the true project dependencies. Scoping prevents mismatched callable and edge JSON from invalidating path search results.

Static graph facts identify whether a callable reaches another through direct edges or multi-hop paths, while CVE reachability analysis determines if vulnerable code is actually exploitable. This Skill focuses on static graph facts rather than CVE reachability.

You should avoid static call graph path search when you need runtime call resolution or CVE exploitability analysis, as this Skill provides static graph facts using decoded JSON artifacts rather than dynamic execution or vulnerability analysis.