guardian / pluto-atomresponder
Components

An overview of source code logical components.

Intro

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.

Logical Decompositions Overview

Analyzed system has 1 logical decomposition:

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 6 components.
  • 77 files, 2,483 LOC (100.0% vs. main code).
  • "atomresponder" is biggest, containing 42.13% of LOC.
  • "test-sending-tool" is smallest, containing 1.81% of LOC.


atomresponder1046 LOC (42%) 29 files
rabbitmq733 LOC (29%) 22 files
kinesisresponder382 LOC (15%) 18 files
ROOT165 LOC (6%) 6 files
cloudformation112 LOC (4%) 1 file
test-sending-tool45 LOC (1%) 1 file
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
rabbitmq39 commits (35%)
atomresponder29 commits (26%)
ROOT19 commits (17%)
kinesisresponder11 commits (10%)
test-sending-tool2 commits (1%)
cloudformation2 commits (1%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2025 2024 2023 2022 2021 2020
atomresponder
2
11
73
kinesisresponder
10
4
ROOT
22
test-sending-tool
2
rabbitmq
16
1
81
cloudformation
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.



2025-05-09 20:57