uber / scip-lsp 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

txt

proto

mod

mjs

15 extensions are included in analyses: go, java, py, md, yaml, ts, sh, json, bzl, txt, proto, mod, js, gitignore, mjs
4 criteria are used to exclude files from analysis:

exclude files with path like ".*/testdata/.*" (Test data) (1 file).
exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (2 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 391 files:

262 files are included in analyses.
129 files are excluded from analyses:

Explore all 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.

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.

148 files

95 files

3 files

4 files

13 files

Main Code

All manually created or maintained source code that defines logic of the product that is run in a production environment.

proto

mjs

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

148 files match defined criteria (13,655 LOC, 100.0% vs. main code):

110 *.go files (10,184 LOC)
16 *.java files (1,285 LOC)
10 *.py files (1,104 LOC)
3 *.ts files (542 LOC)
2 *.bzl files (330 LOC)
2 *.proto files (105 LOC)
4 *.yaml files (81 LOC)
1 *.mjs files (24 LOC)

" *.go" is biggest, containing 74.58% of LOC.
" *.mjs" is smallest, containing 0.18% of LOC.

Test Code

Used only for testing of the product. Normally not deployed in a production environment.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*_test[.].*".
files with paths like ".*/[Tt]est/.*".
files with paths like ".*[.][Tt]est[.].*".
files with paths like ".*[.]test[.].*".
files with paths like ".*/test_.*".

95 files match defined criteria (24,533 LOC, 179.7% vs. main code):

79 *.go files (21,855 LOC)
5 *.py files (1,477 LOC)
10 *.java files (1,192 LOC)
1 *.ts files (9 LOC)

" *.go" is biggest, containing 89.08% of LOC.
" *.ts" is smallest, containing 0.04% of LOC.

Generated Code

Automatically generated files, not manually changed after generation.

Explore: circles | sunburst

The following criteria are used to filter files:

files with any line of content like "//[ ]*Generated by .*".
files with paths like ".*/package[-]lock[.]json".

3 files match defined criteria (5,699 LOC, 41.7% vs. main code):

1 *.json files (4,874 LOC)
2 *.go files (825 LOC)

" *.json" is biggest, containing 85.52% of LOC.
" *.go" is smallest, containing 14.48% of LOC.

Build and Deployment Code

Source code used to configure or support build and deployment process.

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*([.]|/)webpack([.]|/).*".
files with paths like ".*/package[-]lock[.]json".
files with paths like ".*/package[.]json".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]sh".

4 files match defined criteria (112 LOC, 0.8% vs. main code):

3 *.sh files (76 LOC)
1 *.js files (36 LOC)

" *.sh" is biggest, containing 67.86% of LOC.
" *.js" is smallest, containing 32.14% of LOC.

Other Code

mod

txt

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/go[.]mod".
files with paths like ".*[.]md".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*[.]txt".
files with paths like ".*[.]json".
files with paths like ".*/[.]gitignore".

13 files match defined criteria (5,534 LOC, 40.5% vs. main code):

3 *.json files (5,070 LOC)
8 *.md files (332 LOC)
1 *.mod files (129 LOC)
1 *.txt files (3 LOC)

" *.json" is biggest, containing 91.62% of LOC.
" *.txt" is smallest, containing 0.05% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.go files are analyzed with GoLangAnalyzer:

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

*.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)

*.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

*.ts files are analyzed with TypeScriptAnalyzer:

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

*.bzl 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

*.proto 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

*.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

*.mjs 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-04-18 13:03