deepseek-ai/DeepSeek-Coder
Code Volume
Analysis scope, overview of main, test, generated, deployment, build, and other code.
Source Code Analysis Scope
Files includes and excluded from analyses
jsonl

scoping details...
  • 9 extensions are included in analyses: py, jsonl, md, json, txt, sh, yaml, css, gitignore
  • 6 criteria are used to exclude files from analysis:
    • exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (1 file).
    • 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) (1 file).
    • exclude files with path like ".*/_sokrates/.*" (Sokrates files) (0 files).
    • exclude files with path like ".*/_sokrates_landscape/.*" (Sokrates landscape files) (0 files).
    • exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (0 files).
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.
main6386 LOC (50%) 35 files
test30 LOC (<1%) 2 files
generated0 LOC (0%) 0 files
build and deployment11 LOC (<1%) 3 files
other6147 LOC (48%) 18 files
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
jsonl
Explore:   circles  |  sunburst

py4321 LOC (67%) 31 files
jsonl2065 LOC (32%) 4 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*".
  • 35 files match defined criteria (6,386 LOC, 100.0% vs. main code):
    • 31 py files (4,321 LOC)
    • 4 jsonl files (2,065 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
Explore:   circles  |  sunburst

yaml30 LOC (100%) 2 files

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/test_.*".
    • files with paths like ".*/test[.].*".
  • 2 files match defined criteria (30 LOC, 0.5% vs. main code). All matches are in yaml files.
Build and Deployment Code
Source code used to configure or support build and deployment process.
Explore:   circles  |  sunburst

sh8 LOC (72%) 2 files
gitignore3 LOC (27%) 1 file

scope details...
  • The following criteria are used to filter files:
    • 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 ".*[.]sh".
  • 3 files match defined criteria (11 LOC, 0.2% vs. main code):
    • 2 sh files (8 LOC)
    • 1 gitignore files (3 LOC)
Other Code
Explore:   circles  |  sunburst

json5328 LOC (86%) 4 files
md678 LOC (11%) 9 files
py101 LOC (1%) 1 file
txt26 LOC (<1%) 3 files
css14 LOC (<1%) 1 file

scope details...
  • The following criteria are used to filter files:
    • files with paths like ".*/[Dd]emos?/.*".
    • files with paths like ".*[.]txt".
    • files with paths like ".*[.]md".
    • files with paths like ".*/README[.][a-z0-9]+".
    • files with paths like ".*[.]json".
  • 18 files match defined criteria (6,147 LOC, 96.3% vs. main code):
    • 4 json files (5,328 LOC)
    • 9 md files (678 LOC)
    • 1 py files (101 LOC)
    • 3 txt files (26 LOC)
    • 1 css files (14 LOC)
About This Analysis
learn more about scopes (main, test, generated, build, 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.

learn more about used code analyzers...
  • *.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
  • *.jsonl files are analyzed with JsonAnalyzer:
    • 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