guardian/ArchiveHunterProxyFramework
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 9 components.

cloudformation725 LOC (42%) 1 file
ProxyRequestLambda549 LOC (31%) 5 files
TranscoderReplyLambda159 LOC (9%) 2 files
docker84 LOC (4%) 1 file
utils81 LOC (4%) 1 file
SweeperLambda59 LOC (3%) 1 file
common36 LOC (2%) 4 files
ROOT24 LOC (1%) 1 file
project4 LOC (<1%) 1 file

scope details...
  • 17 files, 1,721 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.
ProxyRequestLambda35 commits (36%)
cloudformation21 commits (21%)
TranscoderReplyLambda10 commits (10%)
docker8 commits (8%)
utils7 commits (7%)
ROOT5 commits (5%)
common5 commits (5%)
SweeperLambda5 commits (5%)
project1 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
common
5
ROOT
5
TranscoderReplyLambda
10
ProxyRequestLambda
5
2
28
utils
7
project
1
SweeperLambda
5
cloudformation
21
docker
2
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...

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:45