openai/openai-cli
Logical Components
An overview of source code logical 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 6 components.

internal14028 LOC (27%) 130 files
pkg8683 LOC (16%) 66 files
scripts3529 LOC (6%) 19 files
.github510 LOC (<1%) 3 files
ROOT112 LOC (<1%) 2 files
cmd64 LOC (<1%) 1 file

scope details...
  • 221 files, 26,926 LOC (52.5% vs. main code).
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
pkg95 commits (25%)
ROOT66 commits (17%)
internal60 commits (15%)
scripts14 commits (3%)
cmd9 commits (2%)
.github3 commits (<1%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2026
pkg
95
ROOT
66
internal
60
scripts
14
cmd
9
.github
3


Dependencies between components in same commits (past 180 days)
The number on the lines shows the number of shared commits.
See detailed temporal dependencies report... 

flowchart TB
    n0["internal"]
    n1["pkg"]
    n2["scripts"]
    n3["cmd"]
    n4["ROOT"]
    n5[".github"]
    n0 ---|"27"| n0
    n1 ---|"26"| n1
    n0 ---|"19"| n1
    n2 ---|"11"| n2
    n2 ---|"8"| n1
    n1 ---|"6"| n3
    n0 ---|"6"| n3
    n2 ---|"5"| n0
    n2 ---|"3"| n4
    n1 ---|"2"| n4
    n3 ---|"2"| n2
    n0 ---|"1"| n4
    n3 ---|"1"| n4
    n5 ---|"1"| n5
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a0FF,stroke-width:10px
    linkStyle 1 stroke:#a0a0a0ED,stroke-width:9px
    linkStyle 2 stroke:#00688bC9,stroke-width:7px
    linkStyle 3 stroke:#a0a0a093,stroke-width:4px
    linkStyle 4 stroke:#00688b70,stroke-width:2px
    linkStyle 5 stroke:#00688b70,stroke-width:2px
    linkStyle 6 stroke:#00688b70,stroke-width:2px
    linkStyle 7 stroke:#00688b5E,stroke-width:1px
    linkStyle 8 stroke:#00688b5E,stroke-width:1px
    linkStyle 9 stroke:#00688b4C,stroke-width:1px
    linkStyle 10 stroke:#00688b4C,stroke-width:1px
    linkStyle 11 stroke:#00688b4C,stroke-width:1px
    linkStyle 12 stroke:#00688b4C,stroke-width:1px
    linkStyle 13 stroke:#a0a0a04C,stroke-width:1px
About This Analysis

Logical decomposition is a representation of the organization of the main source code, where every and each file is put in exactly one logical component.

  • A software system can have one or more logical decompositions.
  • A logical decomposition can be defined in two ways in Sokrates.
  • First approach is based on the folders structure. Components are mapped to folders at defined folder depth relative to the source code root.
  • Second approach is based on explicit definition of each component. In such explicit definitions, components are explicitly named and their files are selected based on explicitly defined path and content filters.
  • A logical decomposition is considered invalid if a file is selected into two or more components. This constraint is introduced in order to facilitate measuring of dependencies among components.
  • Files not assigned to any component are put into a special "Unclassified" component.

2026-10-07 12:05