azure / eno
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 5 components.
  • 81 files, 9,085 LOC (81.6% vs. main code).
  • "internal" is biggest, containing 54.87% of LOC.
  • "dev" is smallest, containing 1.5% of LOC.


internal4985 LOC (44%) 42 files
api2838 LOC (25%) 13 files
pkg831 LOC (7%) 23 files
cmd295 LOC (2%) 2 files
dev136 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.
internal186 commits (61%)
api66 commits (21%)
cmd56 commits (18%)
pkg15 commits (4%)
dev13 commits (4%)
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
internal
131
222
39
api
49
127
28
cmd
15
44
4
pkg
16
23
dev
1
11
1


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...

G internal internal internal--internal 29 api api internal--api 16 api--api 8 cmd cmd cmd--internal 15 cmd--api 5 pkg pkg pkg--pkg 5


2025-05-06 22:54