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
Static Dependencies
Dependencies among components are static code dependencies among files in different components.
  • Analyzed system has 19 links (arrows) between components.
  • The number on the arrow represents the number of files from referring component that depend on files in referred component.
  • These 19 links contain 46 dependencies.
flowchart TB
    n0["archivescanner"]
    n1["nearlinescanner"]
    n2["app"]
    n3["fix-orphaned-media"]
    n4["frontend"]
    n5["remove-archived-nearline"]
    n6["cronscanner"]
    n7["unclognearline"]
    n8["mxs-copy-components"]
    n9["findarchivednearline"]
    n10["common"]
    n11["public"]
    n12["deletescanner"]
    n13["vs-fix-missing-files"]
    n14["conf"]
    n15["collectionscanner"]
    n2 -->|"5"| n10
    n2 -->|"4"| n3
    n2 -->|"4"| n5
    n2 -->|"4"| n8
    n2 -->|"4"| n9
    n13 -->|"4"| n10
    n3 -->|"3"| n10
    n15 -->|"3"| n10
    n13 -->|"2"| n3
    n13 -->|"2"| n5
    n13 -->|"2"| n8
    n13 -->|"2"| n9
    n0 -->|"1"| n10
    n3 -->|"1"| n7
    n3 -->|"1"| n8
    n3 -->|"1"| n15
    n6 -->|"1"| n10
    n9 -->|"1"| n10
    n13 -->|"1"| n2
    classDef default fill:#808080,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    class n0,n1,n2,n3,n4,n5,n6,n7,n8,n9,n10,n11,n12,n13,n14,n15 highlighted;
    linkStyle 0 stroke:#00688bA5,stroke-width:5px
    linkStyle 1 stroke:#00688b93,stroke-width:4px
    linkStyle 2 stroke:#00688b93,stroke-width:4px
    linkStyle 3 stroke:#00688b93,stroke-width:4px
    linkStyle 4 stroke:#00688b93,stroke-width:4px
    linkStyle 5 stroke:#00688b93,stroke-width:4px
    linkStyle 6 stroke:#00688b82,stroke-width:3px
    linkStyle 7 stroke:#00688b82,stroke-width:3px
    linkStyle 8 stroke:#00688b70,stroke-width:2px
    linkStyle 9 stroke:#00688b70,stroke-width:2px
    linkStyle 10 stroke:#00688b70,stroke-width:2px
    linkStyle 11 stroke:#00688b70,stroke-width:2px
    linkStyle 12 stroke:#00688b5E,stroke-width:1px
    linkStyle 13 stroke:#00688b5E,stroke-width:1px
    linkStyle 14 stroke:#00688b5E,stroke-width:1px
    linkStyle 15 stroke:#00688b5E,stroke-width:1px
    linkStyle 16 stroke:#00688b5E,stroke-width:1px
    linkStyle 17 stroke:#00688b5E,stroke-width:1px
    linkStyle 18 stroke:#00688b5E,stroke-width:1px




Explore: 2D force graph | 3D force graph

Show more details about dependencies...
From Component
 --> To Component
From Component
(files with dependencies)
Details
app
  --> common
5 files, 276 LOC (43%)
5 source files
app
  --> fix-orphaned-media
4 files, 194 LOC (30%)
4 source files
app
  --> remove-archived-nearline
4 files, 194 LOC (30%)
4 source files
app
  --> mxs-copy-components
4 files, 194 LOC (30%)
4 source files
app
  --> findarchivednearline
4 files, 194 LOC (30%)
4 source files
vs-fix-missing-files
  --> common
4 files, 188 LOC (44%)
4 source files
fix-orphaned-media
  --> common
3 files, 155 LOC (41%)
3 source files
collectionscanner
  --> common
3 files, 244 LOC (56%)
3 source files
vs-fix-missing-files
  --> fix-orphaned-media
2 files, 150 LOC (35%)
2 source files
vs-fix-missing-files
  --> remove-archived-nearline
2 files, 150 LOC (35%)
2 source files
vs-fix-missing-files
  --> mxs-copy-components
2 files, 150 LOC (35%)
2 source files
vs-fix-missing-files
  --> findarchivednearline
2 files, 150 LOC (35%)
2 source files
archivescanner
  --> common
1 file, 66 LOC (22%)
1 source file
fix-orphaned-media
  --> unclognearline
1 file, 20 LOC (5%)
1 source file
fix-orphaned-media
  --> mxs-copy-components
1 file, 20 LOC (5%)
1 source file
fix-orphaned-media
  --> collectionscanner
1 file, 20 LOC (5%)
1 source file
cronscanner
  --> common
1 file, 37 LOC (15%)
1 source file
findarchivednearline
  --> common
1 file, 39 LOC (27%)
1 source file
vs-fix-missing-files
  --> app
1 file, 108 LOC (25%)
1 source file
About This Analysis

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:


2026-10-07 12:44