google-gemini/gemini-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 10 components.

packages219000 LOC (64%) 1,109 files
scripts8974 LOC (2%) 58 files
evals6450 LOC (1%) 41 files
tools4979 LOC (1%) 60 files
.github1386 LOC (<1%) 11 files
.gemini778 LOC (<1%) 14 files
ROOT651 LOC (<1%) 3 files
sea213 LOC (<1%) 1 file
.gcp98 LOC (<1%) 2 files
.allstar1 LOC (<1%) 1 file

scope details...
  • 1,300 files, 242,530 LOC (71.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.
packages4330 commits (67%)
scripts197 commits (3%)
ROOT103 commits (1%)
evals98 commits (1%)
.github35 commits (<1%)
tools28 commits (<1%)
.gemini21 commits (<1%)
.gcp4 commits (<1%)
sea2 commits (<1%)
.allstar1 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
packages
1962
2368
scripts
67
130
ROOT
44
59
evals
98
.github
21
14
tools
28
.gemini
11
10
.gcp
1
3
sea
2
.allstar
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["packages"]
    n1["tools"]
    n2["evals"]
    n3["scripts"]
    n4["ROOT"]
    n5[".github"]
    n0 ---|"282"| n0
    n1 ---|"21"| n1
    n2 ---|"19"| n0
    n3 ---|"10"| n0
    n2 ---|"10"| n2
    n3 ---|"8"| n3
    n0 ---|"5"| n4
    n3 ---|"3"| n2
    n5 ---|"2"| n5
    n0 ---|"2"| n5
    n1 ---|"1"| n4
    n3 ---|"1"| n4
    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:#00688b4C,stroke-width:1px
    linkStyle 3 stroke:#00688b4C,stroke-width:1px
    linkStyle 4 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 5 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 6 stroke:#00688b4C,stroke-width:1px
    linkStyle 7 stroke:#00688b4C,stroke-width:1px
    linkStyle 8 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 9 stroke:#00688b4C,stroke-width:1px
    linkStyle 10 stroke:#00688b4C,stroke-width:1px
    linkStyle 11 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-04 23:16