uber / arachne
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 7 components.
  • 21 files, 2,410 LOC (100.0% vs. main code).
  • "internal" is biggest, containing 46.31% of LOC.
  • "arachned" is smallest, containing 1.29% of LOC.


internal1116 LOC (46%) 11 files
config532 LOC (22%) 1 file
collector434 LOC (18%) 1 file
ROOT164 LOC (6%) 3 files
metrics95 LOC (3%) 2 files
defines38 LOC (1%) 1 file
arachned31 LOC (1%) 2 files
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
internal12 commits (44%)
config11 commits (40%)
defines9 commits (33%)
ROOT8 commits (29%)
collector6 commits (22%)
metrics4 commits (14%)
arachned3 commits (11%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2026 2025 2024 2023 2022 2021 2020 2019 2018 2017
internal
31
ROOT
12
arachned
1
4
metrics
8
config
1
10
collector
6
defines
9


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.



2026-04-18 12:56