azure / k6ctl
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.
  • 32 files, 1,570 LOC (100.0% vs. main code).
  • "internal" is biggest, containing 83.5% of LOC.
  • "ROOT" is smallest, containing 2.23% of LOC.


internal1311 LOC (83%) 22 files
cmd149 LOC (9%) 4 files
sample75 LOC (4%) 3 files
ROOT35 LOC (2%) 3 files
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
internal7 commits (43%)
cmd6 commits (37%)
sample3 commits (18%)
ROOT2 commits (12%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2025 2024
internal
35
cmd
9
sample
6
ROOT
3


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-06 23:06