guardian/facia-tool
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.

fronts-client47111 LOC (60%) 403 files
app17433 LOC (22%) 170 files
public10898 LOC (13%) 139 files
scripts1748 LOC (2%) 9 files
cdk795 LOC (1%) 2 files
conf213 LOC (<1%) 15 files
grunt-configs123 LOC (<1%) 6 files
ROOT57 LOC (<1%) 3 files
.devcontainer17 LOC (<1%) 1 file
nginx5 LOC (<1%) 1 file

scope details...
  • 749 files, 78,400 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.
ROOT1865 commits (20%)
app1498 commits (16%)
fronts-client1117 commits (12%)
public516 commits (5%)
grunt-configs140 commits (1%)
conf59 commits (<1%)
scripts56 commits (<1%)
cdk15 commits (<1%)
.devcontainer9 commits (<1%)
nginx3 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 2015 2014 2013 2012
fronts-client
233
227
432
18
31
18
158
app
103
83
217
23
15
110
174
500
148
26
81
8
10
public
14
57
35
13
3
10
20
36
57
53
210
8
scripts
18
4
28
1
5
ROOT
9
6
6
7
7
3
2
13
8
268
897
639
cdk
15
.devcontainer
9
conf
3
2
16
4
2
30
2
grunt-configs
4
4
3
1
2
1
2
4
81
38
nginx
1
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["fronts-client"]
    n1["app"]
    n2["ROOT"]
    n3["cdk"]
    n4["conf"]
    n5["public"]
    n6[".devcontainer"]
    n0 ---|"94"| n0
    n1 ---|"48"| n1
    n1 ---|"7"| n0
    n2 ---|"6"| n3
    n4 ---|"3"| n1
    n5 ---|"3"| n5
    n3 ---|"2"| n3
    n6 ---|"1"| n1
    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:#a0a0a0A5,stroke-width:5px
    linkStyle 2 stroke:#00688b4C,stroke-width:1px
    linkStyle 3 stroke:#00688b4C,stroke-width:1px
    linkStyle 4 stroke:#00688b4C,stroke-width:1px
    linkStyle 5 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 6 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 7 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:13