guardian/utils
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 12 components.

core492 LOC (40%) 6 files
compatibility208 LOC (16%) 6 files
sharing174 LOC (14%) 4 files
data123 LOC (10%) 4 files
ROOT57 LOC (4%) 2 files
timing46 LOC (3%) 2 files
string34 LOC (2%) 3 files
ajax29 LOC (2%) 1 file
dom27 LOC (2%) 4 files
array17 LOC (1%) 1 file
image15 LOC (1%) 1 file
detect4 LOC (<1%) 1 file

scope details...
  • 35 files, 1,226 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.
core3 commits (33%)
string3 commits (33%)
dom2 commits (22%)
ROOT2 commits (22%)
data2 commits (22%)
array2 commits (22%)
timing2 commits (22%)
detect2 commits (22%)
sharing2 commits (22%)
compatibility2 commits (22%)
image1 commits (11%)
ajax1 commits (11%)
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
image
1
core
3
dom
2
data
2
string
1
2
ROOT
2
array
2
timing
2
detect
2
sharing
2
ajax
1
compatibility
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...

No temporal dependencies found.

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 13:26