azure / autorest - 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

npmignore

eslintignore

gitattributes

editorconfig

npmrc

mjs

prettierignore

24 extensions are included in analyses: json, cs, ts, md, java, txt, yaml, rb, js, py, go, npmignore, gitignore, eslintignore, css, ps1, gitattributes, sh, editorconfig, html, npmrc, svg, mjs, prettierignore
5 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (73 files).
exclude files with path like ".*\.d\.ts" (Typescript definition files) (8 files).
exclude files with path like ".*/[Pp]ackages\/.+\.\d+\/.*" (NuGet) (185 files).
exclude files with path like ".*/docs/.*" (Documentation) (64 files).
exclude files with path like ".*/normalize[.](css|less|scss|styl)" (Normalize css) (0 files).

The source code folder contains 5,261 files:

4,553 files are included in analyses.
708 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.

6 files

Main Code

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

mjs

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

463 files match defined criteria (37,020 LOC, 100.0% vs. main code):

437 *.ts files (35,618 LOC)
14 *.js files (995 LOC)
9 *.yaml files (283 LOC)
2 *.ps1 files (106 LOC)
1 *.mjs files (18 LOC)

" *.ts" is biggest, containing 96.21% of LOC.
" *.mjs" is smallest, containing 0.05% 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 ".*/jest[.][a-zA-Z0-9\.]+".
files with paths like ".*[.][Tt]est[.].*".
files with paths like ".*[.]test[.].*".
files with paths like ".*/[Tt]est/.*".
files with paths like ".*[.]spec[.]ts".
files with paths like ".*[-]test[-].*".
files with paths like ".*/testing[.].*".
files with paths like ".*/test[.].*".
files with paths like ".*[-]tests/.*".

170 files match defined criteria (10,826 LOC, 29.2% vs. main code):

94 *.ts files (8,554 LOC)
49 *.yaml files (1,996 LOC)
24 *.js files (194 LOC)
2 *.py files (56 LOC)
1 *.ps1 files (26 LOC)

" *.ts" is biggest, containing 79.01% of LOC.
" *.ps1" is smallest, containing 0.24% 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 paths like ".*/generated/.*".

97 files match defined criteria (3,100 LOC, 8.4% vs. main code):

3 *.yaml files (3,006 LOC)
94 *.rb files (94 LOC)

" *.yaml" is biggest, containing 96.97% of LOC.
" *.rb" is smallest, containing 3.03% 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[.]json".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[.]gitattributes".
files with paths like ".*[.]sh".

6 files match defined criteria (131 LOC, 0.4% vs. main code):

5 *.js files (125 LOC)
1 *.sh files (6 LOC)

" *.js" is biggest, containing 95.42% of LOC.
" *.sh" is smallest, containing 4.58% of LOC.

Other Code

txt

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*/[.]prettierignore".
files with paths like ".*[.]json".
files with paths like ".*[.]md".
files with paths like ".*[.]npmrc".
files with paths like ".*/[.]gitignore".
files with paths like ".*/[.]npmignore".
files with paths like ".*/[.]eslintignore".
files with paths like ".*[.]txt".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*/[Ee]xamples/.*".
files with paths like ".*/[Ss]amples/.*".
files with paths like ".*/LICENSE[.][a-z0-9]+".
files with paths like ".*[.]svg".
files with paths like ".*[.]editorconfig".

3914 files match defined criteria (322,594 LOC, 871.4% vs. main code):

2,564 *.json files (300,639 LOC)
24 *.yaml files (11,657 LOC)
159 *.md files (8,155 LOC)
138 *.txt files (1,114 LOC)
680 *.cs files (680 LOC)
145 *.java files (145 LOC)
94 *.rb files (94 LOC)
54 *.py files (54 LOC)
41 *.js files (41 LOC)
15 *.go files (15 LOC)

" *.json" is biggest, containing 93.19% of LOC.
" *.go" is smallest, containing 0% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

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

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

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

2025-05-06 21:11