How anthropics/anthropic-sdk-python is laid out, and where to start for common changes.
C
Architecture grade
score 64/100
8+
Import cycles
lower is better
400
Files mapped
1,890 imports between them
93%
Layering
of imports point one way
From the map of which files import which, built when the code was last read in full. It shows what depends on what, not a reading order.
Module map
Shade byless more
25 modules, 116 links. A link means one module imports another; thicker lines mean more imports. Links come from 400 of 2,442 source files, so the real counts are higher. Select a module to trace it: blue lines go to what it uses, orange lines come from what uses it.
ModuleFilesUsed byUsesCommits, 90 daysRole
_utils151434Shared core
_types11325Shared core
_models11246Shared core
_compat1821Shared core
_base_client171514Orchestrator
_exceptions1715Shared core
_constants1606Foundation
_response1693Orchestrator
_streaming1666Shared core
lib9341266Orchestrator
__init__14125Orchestrator
_client141415Orchestrator
_files1323Shared core
_middleware1320Shared core
_request1342Orchestrator
_tracing1352Orchestrator
_version13031Foundation
types213721100+Shared core
resources13321695Orchestrator
_decoders1222Shared core
_qs1222Shared core
_resource1111Shared core
pagination111–Shared core
_data4002Standalone
_vendor4001Standalone
Where to start reading
Repository root
Repository root
Likely public API
Likely public API
Suggested starting pointAI
Suggested starting pointAI
Suggested starting pointAI
Suggested starting pointAI
Find files for a task
AI
Add a new cloud platform backend (e.g., Azure Batch)
Add credential chain provider for the platform
Add a new helper utility (e.g., structured output validator)
Export from src/anthropic/lib/__init__.py to make public