openai/tunnel-client
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.

pkg37877 LOC (49%) 178 files
cmd5957 LOC (7%) 28 files
adminui3807 LOC (4%) 23 files
plugins3222 LOC (4%) 14 files
scripts1266 LOC (1%) 6 files
wrappers665 LOC (<1%) 3 files
ROOT273 LOC (<1%) 1 file
testsupport93 LOC (<1%) 2 files
.codex27 LOC (<1%) 1 file

scope details...
  • 256 files, 53,187 LOC (68.8% 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.
pkg328 commits (53%)
cmd147 commits (23%)
plugins99 commits (16%)
adminui11 commits (1%)
scripts6 commits (<1%)
ROOT4 commits (<1%)
wrappers2 commits (<1%)
testsupport2 commits (<1%)
.codex1 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
pkg
321
7
cmd
146
1
plugins
99
adminui
11
scripts
6
ROOT
4
wrappers
2
testsupport
2
.codex
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["pkg"]
    n1["cmd"]
    n2["plugins"]
    n3["adminui"]
    n4["ROOT"]
    n5["scripts"]
    n6["wrappers"]
    n7["testsupport"]
    n0 ---|"188"| n0
    n1 ---|"120"| n0
    n1 ---|"105"| n1
    n2 ---|"90"| n0
    n2 ---|"89"| n1
    n3 ---|"6"| n0
    n2 ---|"6"| n2
    n3 ---|"5"| n3
    n4 ---|"3"| n0
    n5 ---|"3"| n5
    n6 ---|"2"| n0
    n6 ---|"2"| n1
    n6 ---|"2"| n6
    n3 ---|"2"| n1
    n5 ---|"1"| n0
    n7 ---|"1"| n0
    n7 ---|"1"| n1
    n2 ---|"1"| n3
    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:#00688bB7,stroke-width:6px
    linkStyle 2 stroke:#a0a0a0A5,stroke-width:5px
    linkStyle 3 stroke:#00688b93,stroke-width:4px
    linkStyle 4 stroke:#00688b93,stroke-width:4px
    linkStyle 5 stroke:#00688b4C,stroke-width:1px
    linkStyle 6 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 7 stroke:#a0a0a04C,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
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:07