gitlab-org / pubsubbeat
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.
  • 4 files, 298 LOC (100.0% vs. main code).
  • "beater" is biggest, containing 73.83% of LOC.
  • "ROOT" is smallest, containing 3.36% of LOC.


beater220 LOC (73%) 1 file
config57 LOC (19%) 1 file
cmd11 LOC (3%) 1 file
ROOT10 LOC (3%) 1 file
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
beater30 commits (38%)
config12 commits (15%)
cmd8 commits (10%)
ROOT4 commits (5%)
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
ROOT
2
2
beater
4
12
1
13
cmd
5
1
2
config
2
3
7


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-16 13:35