guardian/janus-app
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.

app6077 LOC (63%) 70 files
frontend1910 LOC (19%) 10 files
configTools742 LOC (7%) 10 files
setup427 LOC (4%) 6 files
example307 LOC (3%) 8 files
project49 LOC (<1%) 2 files
scripts35 LOC (<1%) 1 file
conf32 LOC (<1%) 1 file
.github13 LOC (<1%) 1 file
.devcontainer10 LOC (<1%) 1 file

scope details...
  • 110 files, 9,602 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.
app373 commits (19%)
frontend162 commits (8%)
configTools40 commits (2%)
example37 commits (1%)
project10 commits (<1%)
conf10 commits (<1%)
.devcontainer8 commits (<1%)
setup6 commits (<1%)
.github6 commits (<1%)
scripts3 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
app
167
161
18
11
5
6
5
frontend
65
97
configTools
14
13
2
2
2
7
example
7
6
2
3
19
project
10
.devcontainer
8
setup
6
conf
5
2
2
1
scripts
3
.github
2
4


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["app"]
    n1["frontend"]
    n2["setup"]
    n3["conf"]
    n4["configTools"]
    n5["example"]
    n0 ---|"42"| n0
    n0 ---|"20"| n1
    n2 ---|"6"| n2
    n3 ---|"4"| n0
    n4 ---|"3"| n0
    n1 ---|"3"| n1
    n0 ---|"2"| n5
    n4 ---|"2"| n4
    n5 ---|"2"| n5
    n1 ---|"2"| n5
    n2 ---|"1"| n0
    n2 ---|"1"| n3
    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:#00688b93,stroke-width:4px
    linkStyle 2 stroke:#a0a0a05E,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:#00688b4C,stroke-width:1px
    linkStyle 7 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 8 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 9 stroke:#00688b4C,stroke-width:1px
    linkStyle 10 stroke:#00688b4C,stroke-width:1px
    linkStyle 11 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:28