openai/codex
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 9 components.

codex-rs857512 LOC (96%) 3,165 files
scripts10022 LOC (1%) 29 files
sdk6352 LOC (<1%) 36 files
.github4074 LOC (<1%) 32 files
tools714 LOC (<1%) 16 files
ROOT400 LOC (<1%) 6 files
codex-cli378 LOC (<1%) 1 file
bazel340 LOC (<1%) 2 files
.cargo5 LOC (<1%) 1 file

scope details...
  • 3,288 files, 879,797 LOC (99.3% 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.
codex-rs8780 commits (73%)
sdk84 commits (<1%)
scripts62 commits (<1%)
.github61 commits (<1%)
ROOT22 commits (<1%)
codex-cli14 commits (<1%)
tools10 commits (<1%)
bazel4 commits (<1%)
.cargo1 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 2025
codex-rs
7448
1332
sdk
58
26
scripts
56
6
.github
55
6
ROOT
19
3
codex-cli
8
6
tools
10
bazel
4
.cargo
1


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["codex-rs"]
    n1["sdk"]
    n2["scripts"]
    n3[".github"]
    n4["codex-cli"]
    n5["tools"]
    n6["bazel"]
    n7["ROOT"]
    n0 ---|"4341"| n0
    n1 ---|"29"| n1
    n2 ---|"18"| n2
    n3 ---|"16"| n3
    n1 ---|"13"| n0
    n0 ---|"11"| n2
    n0 ---|"8"| n3
    n4 ---|"5"| n2
    n5 ---|"5"| n0
    n5 ---|"4"| n5
    n1 ---|"2"| n2
    n6 ---|"2"| n0
    n7 ---|"2"| n7
    n2 ---|"2"| n3
    n7 ---|"2"| n0
    n7 ---|"2"| n3
    n3 ---|"1"| n5
    n4 ---|"1"| n5
    n4 ---|"1"| n0
    n4 ---|"1"| n3
    n7 ---|"1"| n5
    n7 ---|"1"| n4
    n2 ---|"1"| n5
    n2 ---|"1"| n7
    n6 ---|"1"| n6
    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:#a0a0a04C,stroke-width:1px
    linkStyle 2 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 3 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 4 stroke:#00688b4C,stroke-width:1px
    linkStyle 5 stroke:#00688b4C,stroke-width:1px
    linkStyle 6 stroke:#00688b4C,stroke-width:1px
    linkStyle 7 stroke:#00688b4C,stroke-width:1px
    linkStyle 8 stroke:#00688b4C,stroke-width:1px
    linkStyle 9 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 10 stroke:#00688b4C,stroke-width:1px
    linkStyle 11 stroke:#00688b4C,stroke-width:1px
    linkStyle 12 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 13 stroke:#00688b4C,stroke-width:1px
    linkStyle 14 stroke:#00688b4C,stroke-width:1px
    linkStyle 15 stroke:#00688b4C,stroke-width:1px
    linkStyle 16 stroke:#00688b4C,stroke-width:1px
    linkStyle 17 stroke:#00688b4C,stroke-width:1px
    linkStyle 18 stroke:#00688b4C,stroke-width:1px
    linkStyle 19 stroke:#00688b4C,stroke-width:1px
    linkStyle 20 stroke:#00688b4C,stroke-width:1px
    linkStyle 21 stroke:#00688b4C,stroke-width:1px
    linkStyle 22 stroke:#00688b4C,stroke-width:1px
    linkStyle 23 stroke:#00688b4C,stroke-width:1px
    linkStyle 24 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:04