anthropics / python-tblib 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
- 10 extensions are included in analyses: py, rst, txt, yaml, ini, cfg, in, gitignore, toml, editorconfig
- 3 criteria are used to exclude files from analysis:
- exclude files with path like ".*/docs/.*" (Documentation) (10 files).
- exclude files with path like ".*/git[-]history[.]txt" (Git history) (1 file).
- exclude files with path like ".*/git[-][a-zA-Z0-9_]+[.]txt" (Git data exports for sokrates analyses) (0 files).
- The source code folder contains 41 files:
- 24 files are included in analyses.
- 17 files are excluded from analyses:
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.
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
- The following criteria are used to filter files:
- files with paths like ".*".
- 7 files match defined criteria (403 LOC, 100.0% vs. main code):
- 4 *.py files (345 LOC)
- 1 *.cfg files (22 LOC)
- 1 *.in files (19 LOC)
- 1 *.yaml files (17 LOC)
- " *.py" is biggest, containing 85.61% of LOC.
- " *.yaml" is smallest, containing 4.22% of LOC.
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Build and Deployment Code
Source code used to configure or support build and deployment process.
- The following criteria are used to filter files:
- files with paths like ".*/pyproject[.]toml".
- files with paths like ".*/requirements[a-zA-Z0-9._-]*[.]txt".
- files with paths like ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*[.]editorconfig".
- files with paths like "(.*/)?[.]editorconfig".
- files with paths like ".*/setup[.]py".
- 4 files match defined criteria (189 LOC, 46.9% vs. main code):
- 1 *.gitignore files (63 LOC)
- 1 *.py files (59 LOC)
- 1 *.toml files (51 LOC)
- 1 *.editorconfig files (16 LOC)
- " *.gitignore" is biggest, containing 33.33% of LOC.
- " *.editorconfig" is smallest, containing 8.47% of LOC.
Other Code
- The following criteria are used to filter files:
- files with paths like ".*[.](rst|rest|resttxt|rsttxt)".
- files with paths like ".*[.]txt".
- files with paths like ".*[.]ini".
- files with paths like ".*/README[.][a-z0-9]+".
- 7 files match defined criteria (828 LOC, 205.5% vs. main code):
- 4 *.rst files (722 LOC)
- 2 *.ini files (100 LOC)
- 1 *.txt files (6 LOC)
- " *.rst" is biggest, containing 87.2% of LOC.
- " *.txt" is smallest, containing 0.72% of LOC.
Analyzers
Info about analyzers used for source code examinations.
- *.py files are analyzed with PythonAnalyzer:
- 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
- *.cfg files are analyzed with CfgAnalyzer:
- 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)
- No unit size analysis
- No conditional complexity analysis
- No dependency analysis
- *.in files are analyzed with RustAnalyzer:
- 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
- No dependency analysis
- *.yaml files are analyzed with YamlAnalyzer:
- 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)
- No unit size analysis
- No conditional complexity analysis
- No dependency analysis
2026-06-24 10:44