anthropics / tokio
Static Component Dependencies

An overview of static code dependencies among source code logical components.

Intro

Static code dependencies refer to the relationships between different modules, libraries, or components in a software system that are established at compile-time rather than at runtime. These dependencies are determined by the code itself, meaning that one module directly references another through imports, includes, or explicit references in the code. Examples include:

  • Library and Module Imports
  • Class Dependencies (Inheritance & Composition)
  • Function and Method Calls
  • Dependency Injection Without Runtime Resolution
Learn more...
  • To learn more about good practices on componentization and dependencies, Sokrates recommends the following resources:
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
Static Dependencies
Dependencies among components are static code dependencies among files in different components.

No component dependencies found.


2026-06-24 10:48