guardian/support-service-lambdas
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.

handlers62122 LOC (40%) 905 files
modules15933 LOC (10%) 197 files
cdk7665 LOC (4%) 65 files
lib6484 LOC (4%) 115 files
buildcheck1566 LOC (1%) 21 files
_templates282 LOC (<1%) 13 files
ROOT141 LOC (<1%) 3 files
project119 LOC (<1%) 1 file
.devcontainer30 LOC (<1%) 1 file
.github22 LOC (<1%) 1 file

scope details...
  • 1,322 files, 94,364 LOC (61.4% 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.
handlers5266 commits (44%)
cdk1179 commits (9%)
lib935 commits (7%)
project908 commits (7%)
modules822 commits (6%)
buildcheck79 commits (<1%)
_templates34 commits (<1%)
.github7 commits (<1%)
ROOT6 commits (<1%)
.devcontainer1 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
handlers
201
1117
864
583
382
191
645
510
773
modules
129
456
230
7
cdk
77
495
540
67
project
64
96
47
145
106
215
183
36
16
buildcheck
55
24
lib
16
51
58
60
24
12
220
224
270
_templates
4
7
15
8
ROOT
4
2
.github
1
4
2
.devcontainer
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["handlers"]
    n1["modules"]
    n2["cdk"]
    n3["buildcheck"]
    n4["lib"]
    n5["project"]
    n6["ROOT"]
    n7["_templates"]
    n0 ---|"89"| n0
    n1 ---|"52"| n1
    n0 ---|"51"| n1
    n0 ---|"31"| n2
    n0 ---|"26"| n3
    n2 ---|"21"| n3
    n1 ---|"19"| n3
    n2 ---|"19"| n1
    n2 ---|"13"| n2
    n3 ---|"8"| n3
    n4 ---|"8"| n0
    n4 ---|"5"| n4
    n5 ---|"2"| n0
    n1 ---|"2"| n4
    n5 ---|"1"| n2
    n1 ---|"1"| n5
    n6 ---|"1"| n0
    n7 ---|"1"| n3
    n7 ---|"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:#a0a0a0A5,stroke-width:5px
    linkStyle 2 stroke:#00688bA5,stroke-width:5px
    linkStyle 3 stroke:#00688b82,stroke-width:3px
    linkStyle 4 stroke:#00688b70,stroke-width:2px
    linkStyle 5 stroke:#00688b70,stroke-width:2px
    linkStyle 6 stroke:#00688b70,stroke-width:2px
    linkStyle 7 stroke:#00688b70,stroke-width:2px
    linkStyle 8 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 9 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 10 stroke:#00688b4C,stroke-width:1px
    linkStyle 11 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 12 stroke:#00688b4C,stroke-width:1px
    linkStyle 13 stroke:#00688b4C,stroke-width:1px
    linkStyle 14 stroke:#00688b4C,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:#a0a0a04C,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:11