guardian/riff-raff
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 5 components.

riff-raff13909 LOC (66%) 175 files
magenta-lib6991 LOC (33%) 53 files
project146 LOC (<1%) 3 files
.github13 LOC (<1%) 1 file
.devcontainer7 LOC (<1%) 1 file

scope details...
  • 233 files, 21,066 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.
riff-raff1371 commits (31%)
project1175 commits (27%)
magenta-lib994 commits (22%)
.github3 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 2015 2014 2013 2012 2011
project
180
184
187
339
151
11
5
47
22
21
28
riff-raff
13
33
38
31
69
75
62
142
107
75
211
39
125
188
163
magenta-lib
3
23
23
33
73
47
51
48
35
68
228
41
106
99
110
6
.devcontainer
3
.github
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["riff-raff"]
    n0 ---|"5"| n0
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a0A5,stroke-width:5px
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:29