anthropics/anthropic-sdk-go
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 15 components.

ROOT38937 LOC (69%) 106 files
internal8411 LOC (15%) 59 files
lib2625 LOC (4%) 5 files
tools1483 LOC (2%) 8 files
shared1311 LOC (2%) 2 files
packages745 LOC (1%) 7 files
config612 LOC (1%) 4 files
option411 LOC (<1%) 2 files
bedrock335 LOC (<1%) 2 files
mcp253 LOC (<1%) 1 file
googlecloud128 LOC (<1%) 2 files
vertex114 LOC (<1%) 1 file
toolrunner107 LOC (<1%) 1 file
foundry102 LOC (<1%) 1 file
aws66 LOC (<1%) 1 file

scope details...
  • 202 files, 55,640 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.
ROOT393 commits (45%)
internal221 commits (25%)
shared77 commits (8%)
packages41 commits (4%)
option25 commits (2%)
bedrock21 commits (2%)
lib16 commits (1%)
vertex15 commits (1%)
tools8 commits (<1%)
aws3 commits (<1%)
config3 commits (<1%)
foundry2 commits (<1%)
toolrunner2 commits (<1%)
googlecloud2 commits (<1%)
mcp1 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 2024
ROOT
261
104
28
internal
134
79
8
shared
55
21
1
packages
13
27
1
option
11
13
1
lib
16
bedrock
10
6
5
vertex
7
3
5
tools
8
aws
3
config
3
foundry
2
toolrunner
2
googlecloud
2
mcp
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... 

flowchart TB
    n0["ROOT"]
    n1["shared"]
    n2["internal"]
    n3["lib"]
    n4["option"]
    n5["tools"]
    n6["packages"]
    n7["bedrock"]
    n8["vertex"]
    n9["config"]
    n10["googlecloud"]
    n11["foundry"]
    n12["aws"]
    n0 ---|"99"| n0
    n1 ---|"44"| n0
    n2 ---|"21"| n0
    n2 ---|"15"| n2
    n3 ---|"12"| n0
    n1 ---|"10"| n2
    n4 ---|"9"| n2
    n3 ---|"9"| n1
    n5 ---|"7"| n5
    n3 ---|"7"| n2
    n4 ---|"5"| n0
    n6 ---|"5"| n2
    n3 ---|"5"| n3
    n6 ---|"4"| n0
    n1 ---|"4"| n6
    n1 ---|"4"| n4
    n5 ---|"4"| n3
    n5 ---|"4"| n0
    n7 ---|"4"| n2
    n6 ---|"3"| n4
    n8 ---|"3"| n7
    n2 ---|"3"| n9
    n4 ---|"2"| n4
    n6 ---|"2"| n6
    n1 ---|"2"| n1
    n5 ---|"2"| n1
    n10 ---|"2"| n0
    n9 ---|"2"| n0
    n9 ---|"2"| n4
    n9 ---|"2"| n9
    n7 ---|"2"| n0
    n5 ---|"2"| n2
    n7 ---|"1"| n1
    n11 ---|"1"| n0
    n11 ---|"1"| n2
    n11 ---|"1"| n1
    n11 ---|"1"| n7
    n3 ---|"1"| n4
    n3 ---|"1"| n6
    n3 ---|"1"| n7
    n3 ---|"1"| n11
    n4 ---|"1"| n7
    n8 ---|"1"| n4
    n12 ---|"1"| n7
    n12 ---|"1"| n8
    n12 ---|"1"| n0
    n12 ---|"1"| n1
    n10 ---|"1"| n1
    n10 ---|"1"| n12
    n10 ---|"1"| n10
    classDef default fill:#00b2ee,stroke:#ffffff,color:#000000;
    classDef highlighted fill:#00b2ee,stroke:#ffffff,color:#000000;
    linkStyle 0 stroke:#a0a0a0FF,stroke-width:10px
    linkStyle 1 stroke:#00688b93,stroke-width:4px
    linkStyle 2 stroke:#00688b70,stroke-width:2px
    linkStyle 3 stroke:#a0a0a05E,stroke-width:1px
    linkStyle 4 stroke:#00688b5E,stroke-width:1px
    linkStyle 5 stroke:#00688b5E,stroke-width:1px
    linkStyle 6 stroke:#00688b4C,stroke-width:1px
    linkStyle 7 stroke:#00688b4C,stroke-width:1px
    linkStyle 8 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 9 stroke:#00688b4C,stroke-width:1px
    linkStyle 10 stroke:#00688b4C,stroke-width:1px
    linkStyle 11 stroke:#00688b4C,stroke-width:1px
    linkStyle 12 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 13 stroke:#00688b4C,stroke-width:1px
    linkStyle 14 stroke:#00688b4C,stroke-width:1px
    linkStyle 15 stroke:#00688b4C,stroke-width:1px
    linkStyle 16 stroke:#00688b4C,stroke-width:1px
    linkStyle 17 stroke:#00688b4C,stroke-width:1px
    linkStyle 18 stroke:#00688b4C,stroke-width:1px
    linkStyle 19 stroke:#00688b4C,stroke-width:1px
    linkStyle 20 stroke:#00688b4C,stroke-width:1px
    linkStyle 21 stroke:#00688b4C,stroke-width:1px
    linkStyle 22 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 23 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 24 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 25 stroke:#00688b4C,stroke-width:1px
    linkStyle 26 stroke:#00688b4C,stroke-width:1px
    linkStyle 27 stroke:#00688b4C,stroke-width:1px
    linkStyle 28 stroke:#00688b4C,stroke-width:1px
    linkStyle 29 stroke:#a0a0a04C,stroke-width:1px
    linkStyle 30 stroke:#00688b4C,stroke-width:1px
    linkStyle 31 stroke:#00688b4C,stroke-width:1px
    linkStyle 32 stroke:#00688b4C,stroke-width:1px
    linkStyle 33 stroke:#00688b4C,stroke-width:1px
    linkStyle 34 stroke:#00688b4C,stroke-width:1px
    linkStyle 35 stroke:#00688b4C,stroke-width:1px
    linkStyle 36 stroke:#00688b4C,stroke-width:1px
    linkStyle 37 stroke:#00688b4C,stroke-width:1px
    linkStyle 38 stroke:#00688b4C,stroke-width:1px
    linkStyle 39 stroke:#00688b4C,stroke-width:1px
    linkStyle 40 stroke:#00688b4C,stroke-width:1px
    linkStyle 41 stroke:#00688b4C,stroke-width:1px
    linkStyle 42 stroke:#00688b4C,stroke-width:1px
    linkStyle 43 stroke:#00688b4C,stroke-width:1px
    linkStyle 44 stroke:#00688b4C,stroke-width:1px
    linkStyle 45 stroke:#00688b4C,stroke-width:1px
    linkStyle 46 stroke:#00688b4C,stroke-width:1px
    linkStyle 47 stroke:#00688b4C,stroke-width:1px
    linkStyle 48 stroke:#00688b4C,stroke-width:1px
    linkStyle 49 stroke:#a0a0a04C,stroke-width:1px
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 22:54