guardian/coverdrop
Code Volume Analysis scope, overview of main, test, generated, deployment, build, and other code. |
Source Code Analysis Scope
Files includes and excluded from analyses
scoping details...
- 30 extensions are included in analyses: rs, json, kt, swift, sql, ts, md, tsx, sh, toml, xml, txt, gitignore, dockerfile, svg, plist, pro, kts, properties, yaml, js, yml, html, gradle, css, py, dockerignore, bat, npmrc, pub
- 10 criteria are used to exclude files from analysis:
- exclude files with path like ".*/docs/.*" (Documentation) (23 files).
- exclude files with path like ".*/proguard[-]rules[.]pro" (ProGuard) (5 files).
- exclude files with path like ".*/gradle/wrapper/.*" (Gradle) (1 file).
- exclude files with path like ".*/git[-]commit[-]trailers[.]txt" (Git history trailers) (1 file).
- exclude files with path like ".*\.d\.ts" (Typescript definition files) (3 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) (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).
- The source code folder contains 2,073 files:
- 1,803 files are included in analyses.
- 270 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.
Main Code
All manually created or maintained source code that defines logic of the product that is run in a production environment.
scope details...
- The following criteria are used to filter files:
- files with paths like ".*".
- 1029 files match defined criteria (86,645 LOC, 100.0% vs. main code):
- 545 rs files (43,166 LOC)
- 149 kt files (13,076 LOC)
- 161 swift files (12,373 LOC)
- 52 tsx files (6,413 LOC)
- 12 xml files (4,491 LOC)
- 6 toml files (3,221 LOC)
- 23 ts files (2,097 LOC)
- 64 sql files (1,040 LOC)
- 5 kts files (456 LOC)
- 4 yaml files (116 LOC)
- 1 css files (98 LOC)
- 2 js files (66 LOC)
- 2 html files (24 LOC)
- 2 pro files (7 LOC)
- 1 pub files (1 LOC)
Test Code
Used only for testing of the product. Normally not deployed in a production environment.
scope details...
- The following criteria are used to filter files:
- files with paths like ".*/[Tt]ests/.*".
- files with paths like ".*/test_.*".
- files with paths like ".*/tests[.]rs".
- files with paths like ".*[-]tests/.*".
- files with paths like ".*[-]test[-].*".
- files with paths like ".*_test[.].*".
- files with paths like ".*_tests[.].*".
- files with paths like ".*/src/androidTest/.*".
- files with paths like ".*/mock[^/]*/.*".
- files with paths like ".*/[Mm]ocks/.*".
- files with paths like ".*[.]spec[.]ts".
- files with paths like ".*/vitest[.].*".
- 210 files match defined criteria (17,494 LOC, 20.2% vs. main code):
- 68 rs files (7,306 LOC)
- 71 kt files (6,972 LOC)
- 39 swift files (2,532 LOC)
- 5 xml files (201 LOC)
- 16 sh files (184 LOC)
- 1 sql files (83 LOC)
- 3 toml files (82 LOC)
- 1 kts files (69 LOC)
- 2 ts files (58 LOC)
- 4 gitignore files (7 LOC)
Generated Code
Automatically generated files, not manually changed after generation.
scope details...
- The following criteria are used to filter files:
- files with paths like ".*/generated/.*".
- files with any line of content like "// This file was generated .*".
- 37 files match defined criteria (240 LOC, 0.3% vs. main code):
- 35 ts files (173 LOC)
- 1 swift files (39 LOC)
- 1 kt files (28 LOC)
Build and Deployment Code
Source code used to configure or support build and deployment process.
scope details...
- The following criteria are used to filter files:
- files with paths like ".*/Cargo[.]toml".
- files with paths like ".*[.]sh".
- files with paths like ".*[.]git[a-z]+".
- files with paths like ".*/[.]gitignore".
- files with paths like ".*/docker[-]compose[.]yml".
- files with paths like ".*/[.]dockerignore".
- files with paths like "(.*/)?[.]dockerignore".
- files with paths like ".*/AndroidManifest[.]xml".
- files with paths like ".*[.]gradle".
- files with paths like ".*[.]bat".
- files with paths like ".*[.]npmrc".
- files with paths like "(.*/)?[.]npmrc".
- files with paths like ".*/package[.]json".
- 74 files match defined criteria (1,591 LOC, 1.8% vs. main code):
- 22 toml files (745 LOC)
- 27 sh files (520 LOC)
- 14 gitignore files (96 LOC)
- 1 bat files (68 LOC)
- 5 xml files (61 LOC)
- 1 dockerignore files (45 LOC)
- 2 gradle files (35 LOC)
- 1 yaml files (16 LOC)
- 1 npmrc files (5 LOC)
Other Code
scope details...
- The following criteria are used to filter files:
- files with paths like ".*[.]md".
- files with paths like ".*/README[.][a-z0-9]+".
- files with paths like ".*/LICENSE[.][a-z0-9]+".
- files with paths like ".*[.]json".
- files with paths like ".*[.]txt".
- files with paths like ".*[.]svg".
- files with paths like ".*[.]plist".
- files with paths like ".*[.]properties".
- 453 files match defined criteria (31,907 LOC, 36.8% vs. main code):
- 17 txt files (23,581 LOC)
- 384 json files (7,101 LOC)
- 38 md files (841 LOC)
- 7 plist files (268 LOC)
- 4 svg files (72 LOC)
- 3 properties files (44 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...
- *.rs 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
- *.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)
- *.swift files are analyzed with SwiftAnalyzer:
- 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
- *.tsx 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
- *.xml files are analyzed with XmlAnalyzer:
- 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
- *.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
- *.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
- *.sql files are analyzed with SqlAnalyzer:
- 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
- *.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)
- *.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
- *.css files are analyzed with CssAnalyzer:
- 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
- *.js files are analyzed with JavaScriptAnalyzer:
- 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
- *.html files are analyzed with HtmlAnalyzer:
- 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
- *.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
- *.pub 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