Graph endpoint
GET /graph/:scan_id
Nodes
Nodes expose labels, risk levels, node types, and metadata so clients can render intelligence objects directly.
Edges
Edges should carry relationship labels and source/target identifiers.
Traversal
Graph payloads are optimized for inspection, not just storage. Keep relationships explainable and stable.
Storage
The graph is persisted in Neo4j AuraDB (managed). The backend uses the neo4j-driver to store and traverse nodes and relationships; the API returns traversal-optimized payloads for clients.
Graph node
{
"id": "domain:example.com",
"type": "domain",
"risk_level": "HIGH"
}Graph clients
Frontend clients can render the graph directly and still derive tooltips, scores, and path context.