anthropics/s5cmd
Logical Components
An overview of source code logical components.

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

command4676 LOC (32%) 25 files
storage2245 LOC (15%) 6 files
benchmark468 LOC (3%) 2 files
bench444 LOC (3%) 1 file
log291 LOC (2%) 3 files
useragent106 LOC (<1%) 1 file
parallel101 LOC (<1%) 4 files
orderedwriter80 LOC (<1%) 1 file
ROOT74 LOC (<1%) 2 files
progressbar58 LOC (<1%) 1 file
error58 LOC (<1%) 1 file
strutil56 LOC (<1%) 1 file
version13 LOC (<1%) 1 file
.github12 LOC (<1%) 1 file

scope details...
  • 50 files, 8,682 LOC (59.8% vs. main code).
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
storage140 commits (18%)
command126 commits (16%)
ROOT39 commits (5%)
log18 commits (2%)
version18 commits (2%)
error9 commits (1%)
parallel9 commits (1%)
strutil4 commits (<1%)
bench3 commits (<1%)
benchmark3 commits (<1%)
.github3 commits (<1%)
orderedwriter2 commits (<1%)
progressbar2 commits (<1%)
useragent1 commits (<1%)
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 2016
storage
2
6
30
15
20
14
53
command
4
2
7
25
22
23
43
ROOT
2
6
3
3
1
19
1
4
bench
1
2
log
1
1
4
4
8
useragent
1
orderedwriter
1
1
error
1
1
1
6
version
5
2
10
1
.github
1
2
benchmark
2
1
strutil
1
1
1
1
parallel
1
1
1
1
5
progressbar
1
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... 

flowchart TB
    n0["command"]
    n1["storage"]
    n2["ROOT"]
    n0 ---|"3"| n0
    n1 ---|"2"| n1
    n2 ---|"2"| n0
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a082,stroke-width:3px
    linkStyle 1 stroke:#a0a0a070,stroke-width:2px
    linkStyle 2 stroke:#00688b70,stroke-width:2px
About This Analysis

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.

  • A software system can have one or more logical decompositions.
  • A logical decomposition can be defined in two ways in Sokrates.
  • First approach is based on the folders structure. Components are mapped to folders at defined folder depth relative to the source code root.
  • Second approach is based on explicit definition of each component. In such explicit definitions, components are explicitly named and their files are selected based on explicitly defined path and content filters.
  • A logical decomposition is considered invalid if a file is selected into two or more components. This constraint is introduced in order to facilitate measuring of dependencies among components.
  • Files not assigned to any component are put into a special "Unclassified" component.

2026-10-06 23:30