epam / ai-stacks
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.

Learn more...
Logical Decompositions Overview

Analyzed system has 1 logical decomposition:

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 5 components.
  • 41 files, 1,874 LOC (100.0% vs. main code).
  • "apps" is biggest, containing 39.06% of LOC.
  • "serving-azure" is smallest, containing 2.4% of LOC.


apps732 LOC (39%) 23 files
kubeflow-gcp468 LOC (24%) 6 files
kubeflow-rancher416 LOC (22%) 7 files
serving-rancher213 LOC (11%) 3 files
serving-azure45 LOC (2%) 2 files
Component Commits
Components ordered by number of commits
Total Commits per Component
All commits, some commits may include files from multiple components.
kubeflow-gcp19 commits (22%)
apps18 commits (21%)
kubeflow-rancher15 commits (17%)
serving-azure2 commits (2%)
serving-rancher2 commits (2%)
Yearly File Updates Trend per Components
The number of file changes in commits
animated commit history: all time cumulative | 12 months window
2025 2024 2023 2022
kubeflow-gcp
6
25
serving-azure
3
kubeflow-rancher
11
25
serving-rancher
5
apps
5
60


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.



2025-01-10 14:18