Graph-native Analysis

Follow semantic relationships beyond the edited lines to expose downstream security impact

Warning

Graph-native analysis is coming soon. The explorer previews how it works.

Catch what the diff misses

A diff shows changed lines. Bevor follows semantic relationships to reveal what those changes can affect.

⌄src/core/ImprintRWA.sol
+2-1
@@ -184,1 +184,2 @@ supportsInterface
184-return super.supportsInterface(interfaceId);
184+return interfaceId == type(IERC721).interfaceId
185+ || super.supportsInterface(interfaceId);
Change one return branch→ 194 affected nodes
⌘   581 nodes   1397 edges
‹/› Code⌘ Graph
Impact of the selected code diff across the product code graphThe selected small diff affects 194 connected code entities. Affected nodes are colored and the rest of the graph is muted.
98%3Findings
supportsInterface()

src/core/ImprintRWA.sol

A small change to supportsInterface() expands to 194 connected nodes before analysis begins.

Select a small diff to reveal its downstream blast radius. Toggle All code for the surrounding context.

What the graph represents

Nodes are code entities

Contracts, functions, modifiers, interfaces, storage, errors, and other meaningful program elements become addressable entities.

Edges carry meaning

Calls, reads, writes, inheritance, guards, and other relationships explain how behavior moves through the codebase.

Starting from changed symbols, Bevor expands across semantic edges to form the analysis scope. Relevant findings and prior decisions stay attached to that context across versions.

Info

The explorer uses a small curated Solidity graph to make the relationship model legible. Production graphs can contain thousands of nodes and edges, clustered by code structure and analysis context.

See security posture over time

See how findings and remediations form a measurable trajectory.

On this page