guardian/media-census
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 16 components.

common3002 LOC (29%) 66 files
frontend1815 LOC (17%) 26 files
mxs-copy-components1386 LOC (13%) 30 files
app631 LOC (6%) 21 files
remove-archived-nearline501 LOC (4%) 9 files
unclognearline432 LOC (4%) 7 files
collectionscanner429 LOC (4%) 5 files
vs-fix-missing-files427 LOC (4%) 10 files
fix-orphaned-media378 LOC (3%) 9 files
public315 LOC (3%) 2 files
archivescanner294 LOC (2%) 5 files
cronscanner241 LOC (2%) 2 files
deletescanner145 LOC (1%) 1 file
findarchivednearline140 LOC (1%) 4 files
nearlinescanner136 LOC (1%) 1 file
conf40 LOC (<1%) 1 file

scope details...
  • 199 files, 10,312 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.
common167 commits (57%)
frontend64 commits (22%)
app49 commits (17%)
cronscanner37 commits (12%)
unclognearline28 commits (9%)
nearlinescanner21 commits (7%)
public19 commits (6%)
deletescanner17 commits (5%)
conf17 commits (5%)
fix-orphaned-media14 commits (4%)
collectionscanner14 commits (4%)
archivescanner10 commits (3%)
remove-archived-nearline9 commits (3%)
vs-fix-missing-files7 commits (2%)
mxs-copy-components4 commits (1%)
findarchivednearline3 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
app
6
43
findarchivednearline
3
vs-fix-missing-files
7
cronscanner
2
35
conf
4
13
deletescanner
3
14
collectionscanner
14
fix-orphaned-media
14
nearlinescanner
1
20
public
2
17
common
42
125
remove-archived-nearline
1
8
unclognearline
28
archivescanner
2
8
frontend
8
56
mxs-copy-components
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...

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 12:44