huggingface / ai-blueprint Components

huggingface / ai-blueprint

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 (2 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 2 components.

2 files, 616 LOC (100.0% vs. main code).

"rag" is biggest, containing 93.67% of LOC.
"ROOT" is smallest, containing 6.33% of LOC.

Component Commits

Components ordered by number of commits

Total Commits per Component

All commits, some commits may include files from multiple components.

Yearly File Updates Trend per Components

The number of file changes in commits

animated commit history: all time cumulative | 12 months window

	2025
ROOT	18
rag	10

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

2025-06-30 09:12