guardian/giant
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.

frontend29657 LOC (60%) 366 files
backend16301 LOC (32%) 203 files
cli1463 LOC (2%) 24 files
common708 LOC (1%) 25 files
transcription-worker-interface548 LOC (1%) 1 file
project358 LOC (<1%) 2 files
infra279 LOC (<1%) 8 files
ROOT66 LOC (<1%) 1 file
.devcontainer20 LOC (<1%) 1 file
util15 LOC (<1%) 1 file

scope details...
  • 632 files, 49,415 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.
backend796 commits (39%)
frontend625 commits (31%)
common77 commits (3%)
cli40 commits (1%)
ROOT39 commits (1%)
infra10 commits (<1%)
.devcontainer5 commits (<1%)
project4 commits (<1%)
util3 commits (<1%)
transcription-worker-interface2 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 2024 2023 2022 2021
backend
241
141
36
192
146
40
frontend
264
96
20
114
122
9
common
21
10
4
21
21
ROOT
14
5
5
4
11
cli
10
3
4
23
infra
10
.devcontainer
5
project
4
transcription-worker-interface
2
util
2
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["frontend"]
    n1["backend"]
    n2["common"]
    n3["cli"]
    n4["project"]
    n5["transcription-worker-interface"]
    n6["util"]
    n7["infra"]
    n8["ROOT"]
    n0 ---|"84"| n0
    n1 ---|"73"| n1
    n1 ---|"27"| n0
    n2 ---|"13"| n1
    n3 ---|"4"| n2
    n0 ---|"4"| n2
    n3 ---|"4"| n1
    n3 ---|"3"| n3
    n2 ---|"3"| n2
    n4 ---|"2"| n4
    n5 ---|"2"| n4
    n6 ---|"2"| n1
    n6 ---|"2"| n2
    n6 ---|"2"| n3
    n7 ---|"1"| n7
    n8 ---|"1"| n1
    n7 ---|"1"| n2
    n7 ---|"1"| n1
    n7 ---|"1"| n3
    n6 ---|"1"| n7
    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:#a0a0a0DB,stroke-width:8px
    linkStyle 2 stroke:#00688b82,stroke-width:3px
    linkStyle 3 stroke:#00688b5E,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:#a0a0a04C,stroke-width:1px
    linkStyle 8 stroke:#a0a0a04C,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:#00688b4C,stroke-width:1px
    linkStyle 13 stroke:#00688b4C,stroke-width:1px
    linkStyle 14 stroke:#a0a0a04C,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
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:14