anthropics / tokio
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.

  • 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.
Logical Decompositions Overview

Analyzed system has 1 logical decomposition:

  • primary (10 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 10 components.
  • 479 files, 63,133 LOC (100.0% vs. main code).
  • "tokio" is biggest, containing 79.65% of LOC.
  • "tests-build" is smallest, containing 0% of LOC.


tokio50283 LOC (79%) 344 files
tokio-util6618 LOC (10%) 57 files
tokio-stream2449 LOC (3%) 46 files
benches2163 LOC (3%) 18 files
tokio-macros814 LOC (1%) 3 files
tokio-test746 LOC (1%) 4 files
ROOT49 LOC (<1%) 4 files
.github7 LOC (<1%) 1 file
tests-integration2 LOC (<1%) 1 file
tests-build2 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.
tokio1948 commits (43%)
tokio-util277 commits (6%)
tokio-macros124 commits (2%)
tokio-stream94 commits (2%)
tokio-test88 commits (1%)
benches47 commits (1%)
ROOT12 commits (<1%)
tests-build5 commits (<1%)
tests-integration2 commits (<1%)
.github1 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
tokio
108
206
206
268
274
289
423
174
tokio-util
6
42
33
29
47
41
64
15
tokio-stream
5
11
14
14
13
33
4
tokio-macros
4
6
8
11
9
19
29
38
benches
4
6
6
13
2
6
9
1
tokio-test
1
4
5
5
3
8
22
40
ROOT
5
3
1
3
tests-build
2
3
.github
1
tests-integration
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["tokio"]
    n1["tokio-macros"]
    n2["tokio-util"]
    n3["benches"]
    n4["tokio-stream"]
    n0 ---|"59"| n0
    n1 ---|"2"| n0
    n1 ---|"2"| n1
    n2 ---|"2"| n2
    n0 ---|"1"| n3
    n0 ---|"1"| n2
    n2 ---|"1"| n4
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a0FF,stroke-width:10px
    linkStyle 1 stroke:#00688b4C,stroke-width:1px
    linkStyle 2 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 3 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 4 stroke:#00688b4C,stroke-width:1px
    linkStyle 5 stroke:#00688b4C,stroke-width:1px
    linkStyle 6 stroke:#00688b4C,stroke-width:1px

2026-06-24 10:48