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

app5611 LOC (62%) 100 files
roles1822 LOC (20%) 181 files
cdk762 LOC (8%) 5 files
imageCopier492 LOC (5%) 9 files
public198 LOC (2%) 4 files
conf35 LOC (<1%) 2 files
.github28 LOC (<1%) 1 file
ROOT27 LOC (<1%) 1 file
.devcontainer8 LOC (<1%) 1 file

scope details...
  • 304 files, 8,983 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.
roles568 commits (17%)
app525 commits (15%)
cdk118 commits (3%)
public56 commits (1%)
ROOT33 commits (<1%)
.github24 commits (<1%)
imageCopier15 commits (<1%)
conf10 commits (<1%)
.devcontainer3 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 2020 2019 2018 2017 2016
roles
41
65
38
53
30
65
45
22
94
49
66
app
15
51
21
39
59
71
37
34
66
45
87
cdk
8
12
4
35
8
51
.github
1
2
3
18
.devcontainer
3
ROOT
2
1
6
4
10
8
2
imageCopier
2
1
2
3
7
conf
1
3
2
2
2
public
15
14
2
2
2
8
13


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["roles"]
    n1["app"]
    n2["cdk"]
    n3[".devcontainer"]
    n0 ---|"8"| n0
    n1 ---|"7"| n1
    n2 ---|"2"| n2
    n2 ---|"1"| n1
    n3 ---|"1"| n1
    n1 ---|"1"| n0
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a0DB,stroke-width:8px
    linkStyle 1 stroke:#a0a0a0C9,stroke-width:7px
    linkStyle 2 stroke:#a0a0a070,stroke-width:2px
    linkStyle 3 stroke:#00688b5E,stroke-width:1px
    linkStyle 4 stroke:#00688b5E,stroke-width:1px
    linkStyle 5 stroke:#00688b5E,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:27