azure / autorest.testserver
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 3 components.
  • 114 files, 10,295 LOC (23.2% vs. main code).
  • "legacy" is biggest, containing 65.61% of LOC.
  • "swagger" is smallest, containing 0.52% of LOC.


legacy6755 LOC (15%) 40 files
src3486 LOC (7%) 73 files
swagger54 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.
src81 commits (23%)
legacy60 commits (17%)
swagger1 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
src
8
1
94
112
legacy
1
42
44
63
32
swagger
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...

No temporal dependencies found.



2025-05-06 21:24