anthropics / anthropic-sdk-java
Source Code Overview

Analysis scope, overview of main, test, generated, deployment, build, and other code.

Source Code Analysis Scope
Files includes and excluded from analyses
pro
properties
gitattributes
  • 13 extensions are included in analyses: kt, java, kts, md, yaml, json, pro, properties, gitignore, gitattributes, toml, txt, bat
  • 1 criterion is used to exclude files from analysis:
    • exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
Overview of Analyzed Files
Basic stats on analyzed files
Intro
For analysis purposes we separate files in scope into several categories: main, test, generated, deployment and build, and other.

  • The main category contains all manually created source code files that are being used in the production.
  • Files in the main category are used as input for other analyses: logical decomposition, concerns, duplication, file size, unit size, and conditional complexity.
  • Test source code files are used only for testing of the product. These files are normally not deployed to production.
  • Build and deployment source code files are used to configure or support build and deployment process.
  • Generated source code files are automatically generated files that have not been manually changed after generation.
  • While a source code folder may contain a number of files, we are primarily interested in the source code files that are being written and maintained by developers.
  • Files containing binaries, documentation, or third-party libraries, for instance, are excluded from analysis. The exception are third-party libraries that have been changed by developers.

main12454 LOC (3%) 157 files
test15388 LOC (4%) 61 files
generated330696 LOC (91%) 2,034 files
build and deployment77 LOC (<1%) 3 files
other1215 LOC (<1%) 10 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
pro
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 157 files match defined criteria (12,454 LOC, 100.0% vs. main code):
    • 90 *.kt files (9,242 LOC)
    • 47 *.java files (2,397 LOC)
    • 18 *.kts files (700 LOC)
    • 1 *.toml files (89 LOC)
    • 1 *.pro files (26 LOC)
  • " *.kt" is biggest, containing 74.21% of LOC.
  • " *.pro" is smallest, containing 0.21% of LOC.


*.kt9242 LOC (74%) 90 files
*.java2397 LOC (19%) 47 files
*.kts700 LOC (5%) 18 files
*.toml89 LOC (<1%) 1 file
*.pro26 LOC (<1%) 1 file
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
pro
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*/[Tt]est/.*".
    • files with paths like ".*/test[.].*".
  • 61 files match defined criteria (15,388 LOC, 123.6% vs. main code):
    • 58 *.kt files (15,336 LOC)
    • 2 *.java files (45 LOC)
    • 1 *.pro files (7 LOC)
  • " *.kt" is biggest, containing 99.66% of LOC.
  • " *.pro" is smallest, containing 0.05% of LOC.


*.kt15336 LOC (99%) 58 files
*.java45 LOC (<1%) 2 files
*.pro7 LOC (<1%) 1 file
Generated Code
Automatically generated files, not manually changed after generation.
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.](kts?|java|go|py|cs)" AND any line of content like "[/][/][ ]*File generated from .*".
  • 2034 files match defined criteria (330,696 LOC, 2655.3% vs. main code). All matches are in *.kt files.


*.kt330696 LOC (100%) 2,034 files
Build and Deployment Code
Source code used to configure or support build and deployment process.
gitattributes
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]bat".
    • files with paths like ".*[.]git[a-z]+".
    • files with paths like ".*/[.]gitattributes".
    • files with paths like ".*/[.]gitignore".
  • 3 files match defined criteria (77 LOC, 0.6% vs. main code):
    • 1 *.bat files (64 LOC)
    • 1 *.gitignore files (8 LOC)
    • 1 *.gitattributes files (5 LOC)
  • " *.bat" is biggest, containing 83.12% of LOC.
  • " *.gitattributes" is smallest, containing 6.49% of LOC.


*.bat64 LOC (83%) 1 file
*.gitignore8 LOC (10%) 1 file
*.gitattributes5 LOC (6%) 1 file
Other Code
properties
Explore:   circles  |  sunburst
  • The following criteria are used to filter files:
    • files with paths like ".*[.]json".
    • files with paths like ".*[.]properties".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
  • 10 files match defined criteria (1,215 LOC, 9.8% vs. main code):
    • 6 *.md files (1,104 LOC)
    • 3 *.json files (86 LOC)
    • 1 *.properties files (25 LOC)
  • " *.md" is biggest, containing 90.86% of LOC.
  • " *.properties" is smallest, containing 2.06% of LOC.


*.md1104 LOC (90%) 6 files
*.json86 LOC (7%) 3 files
*.properties25 LOC (2%) 1 file
Analyzers
Info about analyzers used for source code examinations.
  • *.kt files are analyzed with KotlinAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis (based on imports and package statements)
  • *.java files are analyzed with JavaAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Advanced heuristic dependency analysis (based on package names)
  • *.kts files are analyzed with KotlinAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Advanced code cleaning (empty lines and comments removed for LOC calculations, additional cleaning for duplication calculations)
    • Unit size analysis
    • Conditional complexity analysis
    • Basic heuristic dependency analysis (based on imports and package statements)
  • *.toml files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis
  • *.pro files are analyzed with DefaultLanguageAnalyzer:
    • All basic standard analyses supported (source code overview, duplication, file size, concerns, findings, metrics, controls)
    • Basic code cleaning (empty lines removed for LOC calculations and duplication calculations)
    • No unit size analysis
    • No conditional complexity analysis
    • No dependency analysis

2026-06-24 10:44