guardian/media-atom-maker
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 15 components.

public15296 LOC (53%) 225 files
common5095 LOC (17%) 86 files
app4645 LOC (16%) 59 files
uploader2091 LOC (7%) 30 files
cloudformation543 LOC (1%) 1 file
pluto-message-ingestion464 LOC (1%) 11 files
scripts133 LOC (<1%) 2 files
expirer123 LOC (<1%) 2 files
conf91 LOC (<1%) 2 files
scheduler73 LOC (<1%) 2 files
ROOT55 LOC (<1%) 1 file
project37 LOC (<1%) 1 file
.github17 LOC (<1%) 1 file
.devcontainer9 LOC (<1%) 1 file
nginx4 LOC (<1%) 1 file

scope details...
  • 425 files, 28,676 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.
public1297 commits (23%)
app1173 commits (21%)
common717 commits (12%)
uploader331 commits (5%)
cloudformation140 commits (2%)
conf104 commits (1%)
expirer46 commits (<1%)
pluto-message-ingestion31 commits (<1%)
ROOT20 commits (<1%)
scheduler18 commits (<1%)
project11 commits (<1%)
nginx8 commits (<1%)
scripts6 commits (<1%)
.github4 commits (<1%)
.devcontainer4 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
public
367
438
14
73
4
2
16
21
264
98
app
150
145
27
28
29
12
11
25
73
453
220
common
141
132
16
8
24
21
21
26
62
266
uploader
176
77
6
2
2
2
3
4
59
cloudformation
36
9
2
3
2
7
2
67
12
pluto-message-ingestion
18
13
conf
9
18
2
5
2
7
55
6
ROOT
15
5
expirer
11
2
2
6
25
scheduler
7
2
2
7
project
4
2
5
.github
4
.devcontainer
4
nginx
1
1
1
5
scripts
6


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["public"]
    n1["app"]
    n2["common"]
    n3["uploader"]
    n4["pluto-message-ingestion"]
    n5["cloudformation"]
    n6["ROOT"]
    n7[".devcontainer"]
    n8["project"]
    n9["conf"]
    n0 ---|"151"| n0
    n1 ---|"54"| n1
    n2 ---|"44"| n1
    n2 ---|"40"| n2
    n3 ---|"39"| n3
    n0 ---|"33"| n1
    n2 ---|"28"| n3
    n2 ---|"27"| n0
    n3 ---|"22"| n1
    n4 ---|"15"| n2
    n0 ---|"14"| n5
    n4 ---|"13"| n1
    n4 ---|"13"| n0
    n1 ---|"12"| n5
    n2 ---|"12"| n5
    n4 ---|"7"| n5
    n6 ---|"7"| n1
    n6 ---|"5"| n0
    n3 ---|"4"| n0
    n7 ---|"3"| n6
    n1 ---|"3"| n7
    n8 ---|"2"| n3
    n9 ---|"2"| n1
    n9 ---|"2"| n3
    n9 ---|"2"| n2
    n3 ---|"2"| n5
    n6 ---|"1"| n5
    n7 ---|"1"| n0
    n2 ---|"1"| n6
    n3 ---|"1"| n6
    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:#a0a0a082,stroke-width:3px
    linkStyle 2 stroke:#00688b70,stroke-width:2px
    linkStyle 3 stroke:#a0a0a070,stroke-width:2px
    linkStyle 4 stroke:#a0a0a070,stroke-width:2px
    linkStyle 5 stroke:#00688b70,stroke-width:2px
    linkStyle 6 stroke:#00688b5E,stroke-width:1px
    linkStyle 7 stroke:#00688b5E,stroke-width:1px
    linkStyle 8 stroke:#00688b5E,stroke-width:1px
    linkStyle 9 stroke:#00688b4C,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:#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:#00688b4C,stroke-width:1px
    linkStyle 19 stroke:#00688b4C,stroke-width:1px
    linkStyle 20 stroke:#00688b4C,stroke-width:1px
    linkStyle 21 stroke:#00688b4C,stroke-width:1px
    linkStyle 22 stroke:#00688b4C,stroke-width:1px
    linkStyle 23 stroke:#00688b4C,stroke-width:1px
    linkStyle 24 stroke:#00688b4C,stroke-width:1px
    linkStyle 25 stroke:#00688b4C,stroke-width:1px
    linkStyle 26 stroke:#00688b4C,stroke-width:1px
    linkStyle 27 stroke:#00688b4C,stroke-width:1px
    linkStyle 28 stroke:#00688b4C,stroke-width:1px
    linkStyle 29 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:24