agentforge-memory-neo4j
Neo4j-backed MemoryStore and GraphStore for the AgentForge
framework.
What this is
Neo4jMemoryStore—MemoryStore(claim audit log) over Neo4j. Claims map to(:Claim {…})nodes; queries become parameterised Cypher.Neo4jGraphStore—GraphStore(knowledge graph traversal) over Neo4j. Nodes and edges map directly to property graph nodes and relationships.match()andtraverse()compile to Cypher.
Both pass the locked agentforge_core.testing.run_*_conformance
suites — drop-in alternatives to agentforge-memory-sqlite when you
need real graph semantics, multi-writer concurrency, or production
operability (clustering, fine-grained auth, query planner).
Usage
from agentforge_memory_neo4j import Neo4jGraphStore
async with Neo4jGraphStore.from_url(
"bolt://localhost:7687",
auth=("neo4j", "password"),
database="neo4j",
) as store:
await store.add_node(GraphNode(id="paper:1", labels=("Doc",)))
...
Local development
docker compose -f docker-compose.dev.yml up -d
RUN_LIVE_NEO4J=1 NEO4J_URL=bolt://localhost:7687 \
NEO4J_USER=neo4j NEO4J_PASSWORD=test \
uv run pytest packages/agentforge-memory-neo4j/tests/integration -v
Capabilities
{"transactions", "cypher", "fulltext"} — Neo4j 5.x ships native
fulltext indexes; transactions are first-class (every write goes
through session.execute_write).
Vector search is not declared: Neo4j 5.x has vector indexes but
adopting them is tracked separately. Pair Neo4j with
agentforge-memory-postgres (pgvector) or agentforge-memory-sqlite
for embeddings.
Metadata
Release files for agentforge-memory-neo4j 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| agentforge_memory_neo4j-0.4.0.tar.gz | 24.5 kB | With provenance | Details for agentforge_memory_neo4j-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| agentforge_memory_neo4j-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for agentforge_memory_neo4j-0.4.0-py3-none-any.whl |
Total release size: 47.6 kB
Release files / agentforge_memory_neo4j-0.4.0.tar.gz
| Download URL | agentforge_memory_neo4j-0.4.0.tar.gz |
|---|---|
| Size | 24.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
e211145dabc9c76af622472432b0a1b2994f3f3827044e1b219aab817c26ef6c
|
|
BLAKE2b-256 checksum How to use checksums |
194bfbf34256841b35728d12d9ee3d8f597b663cb367b0998d03d3a50686f726
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 24, 2026.
Transparency logRelease files / agentforge_memory_neo4j-0.4.0-py3-none-any.whl
| Download URL | agentforge_memory_neo4j-0.4.0-py3-none-any.whl |
|---|---|
| Size | 23.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
42a142da3ab3ebc30d6a5d68699d6e2036445b340097a205e5d639ce668dfa71
|
|
BLAKE2b-256 checksum How to use checksums |
80e49ea5ae0f93bc4f8ea5a430fb10f875c2c6e15e773cbd55ff60e900ec5b50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 24, 2026.
Transparency logSecurity for agentforge-memory-neo4j 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for agentforge_memory_neo4j-0.4.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jun 24, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.