mneme-graph
Local code knowledge graph for mneme. Extracts GraphNode/GraphEdge from Python
source files via tree-sitter. Derived and rebuildable — the ground truth is
always the source files; graph.json is a derived artifact.
Part of the mneme memory engine.
Scope (v1)
This package is deliberately small and honest about its limits.
- Python only. Extraction uses tree-sitter for Python source. TypeScript, JavaScript, Rust, and other languages are not yet supported.
callsresolution is heuristic. A call edge resolves to a local function/method by unqualified name within the same vault, withINFERREDconfidence. There is no cross-file binding or precise symbol resolution; a call with no local name match points at an<external>node (EXTRACTED).- Derived, never source of truth.
graph.jsonis rebuilt from source on everybuild; the source files remain the ground truth.
Deferred (not implemented yet)
- Community detection / clustering.
- Pull-request impact analysis.
- Entity canonicalization and a merge queue (to avoid ghost-duplicate nodes across renames and aliases).
- Multi-language extraction.
These are roadmap items, not present capabilities.
Metadata
Release files for mneme-graph 4.1.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 |
|---|---|---|---|---|
| mneme_graph-4.1.0.tar.gz | 81.7 kB | With provenance | Details for mneme_graph-4.1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| mneme_graph-4.1.0-py3-none-any.whl | Python 3 | none | any | Details for mneme_graph-4.1.0-py3-none-any.whl |
Total release size: 135.2 kB
Release files / mneme_graph-4.1.0.tar.gz
| Download URL | mneme_graph-4.1.0.tar.gz |
|---|---|
| Size | 81.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
85e6a6c459e53548290aa1aa072b1adc3dc30ea8968bab2bd5caefae0a53f5ea
|
|
BLAKE2b-256 checksum How to use checksums |
af3fb3d73d38ec9fc7f8ffdfc9291d246809a1ef4b5b6871b188ac6d8cce39af
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 31, 2026.
Transparency logRelease files / mneme_graph-4.1.0-py3-none-any.whl
| Download URL | mneme_graph-4.1.0-py3-none-any.whl |
|---|---|
| Size | 53.6 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
8937027d5743c524a807320e741b283224a7b7cbc2539124f19736045f793e9a
|
|
BLAKE2b-256 checksum How to use checksums |
c1575592fa20c7e772bc85d76fbb513918f77e436b7fe05fb6840ac7d1432845
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Aug 31, 2026.
Transparency logSecurity for mneme-graph 4.1.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
All 2 files in this release have been uploaded with provenance metadata.
Attestation for mneme_graph-4.1.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 Aug 31, 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.