getzep/graphiti · graphiti_core/search
✓ No LLMThe graphiti_core/search 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.
6
Files
49
Total in-degree
7
Modules imported
14
Importing modules
A file in this module participates in a circular import — see the architecture overview.
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.
- search_filters.py19 in · 2 out · radius 154
- search_utils.py9 in · 8 out · radius 53
- search_config.py9 in · 3 out · radius 37
- search_config_recipes.py7 in · 1 out · radius 30
- search.py4 in · 12 out · radius 32
- search_helpers.py1 in · 3 out · radius 3
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.
- tests/utils/search11
- graphiti_core6
- graphiti_core/utils/maintenance6
- tests4
- examples/quickstart3
- graphiti_core/driver/neptune/operations2
- mcp_server/src2
- graphiti_core/driver/falkordb/operations1
- graphiti_core/driver/kuzu/operations1
- graphiti_core/driver/neo4j/operations1
- graphiti_core/driver/operations1
- examples/podcast1
- mcp_server/tests1
- tests/utils/maintenance1
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.