azure / peerd
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.
  • 43 files, 3,076 LOC (64.6% vs. main code).
  • "pkg" is biggest, containing 80.4% of LOC.
  • "tools" is smallest, containing 1.59% of LOC.


pkg2473 LOC (51%) 32 files
cmd221 LOC (4%) 2 files
api203 LOC (4%) 2 files
build130 LOC (2%) 4 files
tools49 LOC (1%) 3 files
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
pkg17 commits (21%)
cmd14 commits (17%)
build11 commits (14%)
api2 commits (2%)
tools2 commits (2%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2025 2024
pkg
10
47
cmd
3
15
build
5
10
tools
4
api
2


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 pkg pkg pkg--pkg 4 cmd cmd pkg--cmd 1 tools tools tools--tools 1 build build tools--build 2 cmd--build 1


2025-05-06 23:07