deepseek-ai/3FS
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 8 components.

src91566 LOC (94%) 876 files
configs2888 LOC (2%) 17 files
benchmarks1216 LOC (1%) 3 files
deploy689 LOC (<1%) 6 files
hf3fs_utils488 LOC (<1%) 4 files
hf3fs273 LOC (<1%) 2 files
hf3fs_fuse135 LOC (<1%) 4 files
ROOT124 LOC (<1%) 2 files

scope details...
  • 914 files, 97,379 LOC (100.0% 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.
src66 commits (58%)
benchmarks5 commits (4%)
configs2 commits (1%)
hf3fs_utils1 commits (<1%)
ROOT1 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
src
15
51
benchmarks
5
configs
2
hf3fs_utils
1
ROOT
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...

No temporal dependencies found.

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 14:30