getzep/graphiti · graphiti_core/utils/maintenance
✓ No LLMThe graphiti_core/utils/maintenance module of getzep/graphiti — the files it contains, which are most load-bearing, and how it couples to the rest of the codebase. Derived from the import graph.
8
Files
35
Total in-degree
8
Modules imported
9
Importing modules
Files in this module
Ranked by in-degree — how many other files import each one. The top of the list is where the module's weight sits.
- graph_data_operations.py9 in · 3 out · radius 32
- edge_operations.py6 in · 18 out · radius 29
- node_operations.py6 in · 15 out · radius 30
- dedup_helpers.py5 in · 1 out · radius 34
- community_operations.py3 in · 12 out · radius 23
- attribute_utils.py3 in · 0 out · radius 34
- __init__.py2 in · 3 out · radius 2
- combined_extraction.py1 in · 11 out · radius 24
Depends on
Modules this one imports from (with the number of import edges).
Depended on by
Modules that import from this one — its blast radius if you change it.
Ask AI about getzep/graphiti
Grounded in the actual source code. Pick a starter question or write your own.
What does this repo do, in one paragraph?How would I get started using it?What are the main alternatives?Show me the entry point.
Or write your own questionInformational only. Module boundaries are inferred from source directories and the import graph at the time of analysis; they can be incomplete or stale.