openai / openai-knowledge-retrieval
Static Component Dependencies

An overview of static code dependencies among source code logical components.

Intro

Static code dependencies refer to the relationships between different modules, libraries, or components in a software system that are established at compile-time rather than at runtime. These dependencies are determined by the code itself, meaning that one module directly references another through imports, includes, or explicit references in the code. Examples include:

  • Library and Module Imports
  • Class Dependencies (Inheritance & Composition)
  • Function and Method Calls
  • Dependency Injection Without Runtime Resolution
Learn more...
  • To learn more about good practices on componentization and dependencies, Sokrates recommends the following resources:
Logical Decompositions Overview

Analyzed system has 1 logical decomposition:

  • primary (13 components)

Logical Decomposition #1: PRIMARY

The decompositions is based on the folder structure at level 1 (relative to the source code root).

Bubble Chart | Tree Map
Component Sizes (Lines of Code)
The "primary" logical decomposition has 13 components.
  • 88 files, 6,889 LOC (63.9% vs. main code).
  • "app" is biggest, containing 28.41% of LOC.
  • "docker" is smallest, containing 0.1% of LOC.


app1957 LOC (18%) 26 files
evals1582 LOC (14%) 19 files
templates632 LOC (5%) 6 files
ingestion624 LOC (5%) 19 files
cli547 LOC (5%) 3 files
retrieval494 LOC (4%) 5 files
stores483 LOC (4%) 3 files
models291 LOC (2%) 1 file
configs191 LOC (1%) 2 files
extensions59 LOC (<1%) 1 file
telemetry11 LOC (<1%) 1 file
prompts11 LOC (<1%) 1 file
docker7 LOC (<1%) 1 file
Static Dependencies
Dependencies among components are static code dependencies among files in different components.

No component dependencies found.


2026-06-24 10:41