mozilla / nucleus - 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

ini

cfg

19 extensions are included in analyses: py, sh, html, yaml, json, js, md, txt, ini, in, groovy, css, dockerignore, jsx, rst, bat, cfg, gitignore, toml
5 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (4 files).
exclude files with path like ".*/bin/.*" (Binaries for distribution) (18 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).
exclude files with path like ".*/docs/.*" (Documentation) (5 files).

The source code folder contains 126 files:

80 files are included in analyses.
46 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.

60 files

8 files

1 file

2 files

10 files

Main Code

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

cfg

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

60 files match defined criteria (2,105 LOC, 100.0% vs. main code):

43 *.py files (1,556 LOC)
1 *.jsx files (171 LOC)
8 *.html files (164 LOC)
3 *.js files (96 LOC)
1 *.css files (43 LOC)
2 *.in files (38 LOC)
1 *.toml files (26 LOC)
1 *.cfg files (11 LOC)

" *.py" is biggest, containing 73.92% of LOC.
" *.cfg" is smallest, containing 0.52% 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 ".*/[Tt]ests/.*".
files with paths like ".*/test_.*".
files with paths like ".*_tests[.].*".

8 files match defined criteria (453 LOC, 21.5% vs. main code). All matches are in *.py files.

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 ".*/package[-]lock[.]json".

1 file matches defined criteria (4,543 LOC, 215.8% vs. main code). All matches are in *.json files.

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 ".*[.]sh".
files with paths like ".*/jenkins/.*[.]groovy".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]bat".
files with paths like ".*/package[.]json".
files with paths like ".*/package[-]lock[.]json".

2 files match defined criteria (77 LOC, 3.7% vs. main code). All matches are in *.groovy files.

Other Code

txt

ini

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]ini".
files with paths like ".*[.]txt".
files with paths like ".*[.]json".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[.]dockerignore".
files with paths like ".*[.](rst|rest|resttxt|rsttxt)".
files with paths like ".*[.]md".
files with paths like ".*/README[.][a-z0-9]+".

10 files match defined criteria (6,577 LOC, 312.4% vs. main code):

5 *.json files (4,834 LOC)
2 *.txt files (1,452 LOC)
1 *.ini files (179 LOC)
2 *.md files (112 LOC)

" *.json" is biggest, containing 73.5% of LOC.
" *.md" is smallest, containing 1.7% 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

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

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

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

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

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

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

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

2025-05-11 19:40