# Neo4j

Describes Keryn 0.5.2 and keryn-rules 0.8.0.

> Write the evidence graph to Neo4j over its Query API: address, user, password, database, and what is sent.

Source: https://keryn.dev/docs/reference/connectors/neo4j/

The same evidence graph as the [FalkorDB](https://keryn.dev/docs/reference/connectors/falkordb/) connector writes (one scan, its files, rules, findings and AI components), sent over Neo4j's Query API. A free Neo4j Aura instance works.

## Endpoint and protocol

|  |  |
|---|---|

## Fields

| Field | Kind | Default | Notes |
|---|---|---|---|
| Address | address |  | for example `https://<id>.databases.neo4j.io` |
| User | text | `neo4j` |  |
| Password | secret |  |  |
| Database | text | `neo4j` |  |

How keys and values are stored is on the [connectors overview](https://keryn.dev/docs/reference/connectors/#storage).

## What leaves your machine

> **Leaves your machine, only when you press Send and have entered a relay address:** The statements go to the relay you entered, and to nowhere else. No code excerpts are included.
>
> - Statements that create Scan, Finding, File, Rule, Taxon, Component nodes: the scan's subject and revision, file paths, rule ids, each finding's id, severity, message, line, engine, proof level, verdict and taxonomy ids, and each AI component's key, name, kind, category, provider and the files that use it.
> - Relationships: REPORTED, IN_FILE, VIOLATES, TAGGED, RELATES_TO, INVENTORIED, USES.
> - The relay token, as the bearer.

*Generated from the product's connector catalog (monorepo 27434c1bb57f) by `tools/extract-product-facts.mjs`.*
