azure / azure-openai-samples - Source Code Overview

Source Code Analysis Scope

Files includes and excluded from analyses

txt

jinja2

cfg

jsonl

cmd

ini

14 extensions are included in analyses: json, txt, ipynb, py, md, yaml, jinja2, cfg, jsonl, cmd, ini, gitignore, sql, sh
3 criteria are used to exclude files from analysis:

exclude files with path like ".*/[.][a-zA-Z0-9_]+.*" (Hidden files and folders) (45 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 440 files:

256 files are included in analyses.
184 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.

22 files

234 files

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

22 files match defined criteria (8,215 LOC, 100.0% vs. main code). All matches are in *.ipynb files.

Other Code

txt

jinja2

cfg

ini

jsonl

cmd

Explore: circles | sunburst

The following criteria are used to filter files:

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

234 files match defined criteria (8,516 LOC, 103.7% vs. main code):

10 *.ipynb files (2,924 LOC)
35 *.py files (2,118 LOC)
67 *.txt files (1,146 LOC)
67 *.json files (959 LOC)
23 *.md files (649 LOC)
15 *.yaml files (439 LOC)
8 *.jinja2 files (203 LOC)
3 *.cfg files (39 LOC)
1 *.ini files (24 LOC)
1 *.sh files (9 LOC)
2 *.jsonl files (4 LOC)
2 *.cmd files (2 LOC)

" *.ipynb" is biggest, containing 34.34% of LOC.
" *.cmd" is smallest, containing 0.02% of LOC.

Analyzers

Info about analyzers used for source code examinations.

*.ipynb 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 22:54