apache / shiro-siteSource 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

htaccess

properties

18 extensions are included in analyses: html, svg, css, js, adoc, ftl, yaml, asciidoc, json, txt, md, yml, htaccess, gitignore, java, rdf, xml, properties
6 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (8 files).
exclude files with path like ".*/sokrates_.*?[.]json" (Sokrates conventions and configurations) (1 file).
exclude files with path like ".*/bootstrap[.](js|css|less|scss|styl)" (Bootstrap) (1 file).
exclude files with path like ".*[.]min[.]js" (Minimized JS library) (126 files).
exclude files with path like ".*/dist/.*" (Distributions) (2 files).
exclude files with path like "(?i).*/jquery.*[.]js" (jQuery files) (0 files).

The source code folder contains 6,009 files:

4,983 files are included in analyses.
1,026 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.

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.

1 file

Main Code

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

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*".

2642 files match defined criteria (514,294 LOC, 100.0% vs. main code):

2,155 *.html files (453,358 LOC)
330 *.css files (40,242 LOC)
6 *.js files (10,096 LOC)
125 *.adoc files (9,072 LOC)
18 *.ftl files (976 LOC)
3 *.yaml files (409 LOC)
4 *.asciidoc files (81 LOC)
1 *.java files (60 LOC)

" *.html" is biggest, containing 88.15% of LOC.
" *.java" is smallest, containing 0.01% 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 ".*[-]tests/.*".
files with paths like ".*[-]test[-].*".

146 files match defined criteria (36,849 LOC, 7.2% vs. main code):

118 *.html files (34,723 LOC)
28 *.css files (2,126 LOC)

" *.html" is biggest, containing 94.23% of LOC.
" *.css" is smallest, containing 5.77% 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 .*".

754 files match defined criteria (160,606 LOC, 31.2% vs. main code):

753 *.html files (160,252 LOC)
1 *.rdf files (354 LOC)

" *.html" is biggest, containing 99.78% of LOC.
" *.rdf" is smallest, containing 0.22% 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 ".*/pom[.]xml".
files with paths like ".*[.]git[a-z]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*/package[.]json".

1 file matches defined criteria (112 LOC, 0.0% vs. main code). All matches are in *.xml files.

Other Code

properties

txt

Explore: circles | sunburst

The following criteria are used to filter files:

files with paths like ".*[.]properties".
files with paths like ".*[.]json".
files with paths like ".*/README[.][a-z0-9]+".
files with paths like ".*/[.]gitignore".
files with paths like ".*[.]md".
files with paths like ".*[.]svg".
files with paths like ".*/[Ss]amples/.*".
files with paths like ".*[.]txt".
files with paths like ".*/[.]htaccess".

1451 files match defined criteria (16,585 LOC, 3.2% vs. main code):

118 *.html files (9,854 LOC)
1,324 *.svg files (4,530 LOC)
3 *.json files (1,892 LOC)
2 *.md files (237 LOC)
1 *.adoc files (35 LOC)
1 *.properties files (25 LOC)
2 *.txt files (12 LOC)

" *.html" is biggest, containing 59.42% of LOC.
" *.txt" is smallest, containing 0.07% of LOC.

Analyzers

Info about analyzers used for source code examinations.

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

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

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

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

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

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

2023-08-10 17:21