guardian / targeting-client
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 4 components.
  • 12 files, 370 LOC (100.0% vs. main code).
  • "client-play-json-v28" is biggest, containing 41.62% of LOC.
  • "project" is smallest, containing 5.68% of LOC.


client-play-json-v28154 LOC (41%) 4 files
client-play-json-v30154 LOC (41%) 4 files
ROOT41 LOC (11%) 2 files
project21 LOC (5%) 2 files
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
ROOT92 commits (53%)
project24 commits (14%)
client-play-json-v282 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 2019 2018 2017 2016
ROOT
8
10
5
9
14
12
12
32
client-play-json-v28
8
project
4
4
7
4
4
8


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