openai/openai-cua-sample-app
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 7 components.

labs4674 LOC (36%) 17 files
console3394 LOC (26%) 13 files
python-app2172 LOC (17%) 19 files
javascript-app2152 LOC (16%) 15 files
contracts189 LOC (1%) 1 file
scripts160 LOC (1%) 1 file
ROOT18 LOC (<1%) 1 file

scope details...
  • 67 files, 12,759 LOC (100.0% 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.
labs9 commits (15%)
ROOT6 commits (10%)
console3 commits (5%)
javascript-app3 commits (5%)
python-app3 commits (5%)
contracts3 commits (5%)
scripts2 commits (3%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2026
labs
9
ROOT
6
console
3
javascript-app
3
python-app
3
contracts
3
scripts
2


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["labs"]
    n1["console"]
    n2["contracts"]
    n3["javascript-app"]
    n4["python-app"]
    n5["ROOT"]
    n6["scripts"]
    n0 ---|"4"| n0
    n1 ---|"3"| n1
    n2 ---|"3"| n1
    n3 ---|"3"| n1
    n3 ---|"3"| n2
    n3 ---|"3"| n3
    n4 ---|"3"| n1
    n4 ---|"3"| n2
    n4 ---|"3"| n3
    n4 ---|"3"| n4
    n0 ---|"3"| n5
    n5 ---|"2"| n1
    n5 ---|"2"| n2
    n3 ---|"2"| n5
    n0 ---|"2"| n1
    n0 ---|"2"| n2
    n0 ---|"2"| n3
    n4 ---|"2"| n5
    n4 ---|"2"| n0
    n6 ---|"2"| n1
    n6 ---|"2"| n2
    n6 ---|"2"| n5
    n6 ---|"2"| n3
    n6 ---|"2"| n0
    n6 ---|"2"| n4
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a093,stroke-width:4px
    linkStyle 1 stroke:#a0a0a082,stroke-width:3px
    linkStyle 2 stroke:#00688b82,stroke-width:3px
    linkStyle 3 stroke:#00688b82,stroke-width:3px
    linkStyle 4 stroke:#00688b82,stroke-width:3px
    linkStyle 5 stroke:#a0a0a082,stroke-width:3px
    linkStyle 6 stroke:#00688b82,stroke-width:3px
    linkStyle 7 stroke:#00688b82,stroke-width:3px
    linkStyle 8 stroke:#00688b82,stroke-width:3px
    linkStyle 9 stroke:#a0a0a082,stroke-width:3px
    linkStyle 10 stroke:#00688b82,stroke-width:3px
    linkStyle 11 stroke:#00688b70,stroke-width:2px
    linkStyle 12 stroke:#00688b70,stroke-width:2px
    linkStyle 13 stroke:#00688b70,stroke-width:2px
    linkStyle 14 stroke:#00688b70,stroke-width:2px
    linkStyle 15 stroke:#00688b70,stroke-width:2px
    linkStyle 16 stroke:#00688b70,stroke-width:2px
    linkStyle 17 stroke:#00688b70,stroke-width:2px
    linkStyle 18 stroke:#00688b70,stroke-width:2px
    linkStyle 19 stroke:#00688b70,stroke-width:2px
    linkStyle 20 stroke:#00688b70,stroke-width:2px
    linkStyle 21 stroke:#00688b70,stroke-width:2px
    linkStyle 22 stroke:#00688b70,stroke-width:2px
    linkStyle 23 stroke:#00688b70,stroke-width:2px
    linkStyle 24 stroke:#00688b70,stroke-width:2px
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 13:11