• File size measurements show the distribution of size of files.
• Files are classified in four categories based on their size (lines of code): 1-100 (very small files), 101-200 (small files), 201-500 (medium size files), 501-1000 (long files), 1001+(very long files).
• It is a good practice to keep files small. Long files may become "bloaters", code that have increased to such gargantuan proportions that they are hard to work with.

• There are 19 files with 1,640 lines of code.
• 0 very long files (0 lines of code)
• 0 long files (0 lines of code)
• 3 medium size files (851 lines of codeclsfd_ftr_w_mp_ins)
• 1 small files (118 lines of code)
• 15 very small files (671 lines of code)

There are 15 files with lines longer than 120 characters. In total, there are 108 long lines.

File	# lines	# units	# long lines
Invoke-AvmGitHubTeamLinter.ps1 in utilities/pipelines/sharedScripts/teamLinter	349	-	51
Get-ModulesFeatureOutline.ps1 in utilities/tools/platform/helper	272	-	23
Set-EnvironmentOnAgent.ps1 in utilities/pipelines/sharedScripts	230	-	7
Set-ApiSpecsFile.ps1 in utilities/tools/platform	57	-	6
Get-PipelineStatusUrl.ps1 in utilities/tools/platform/helper	42	-	4
Set-AvmGitHubTeamsIssue.ps1 in utilities/pipelines/sharedScripts/teamLinter	68	-	3
Parse-WAF-Security-Recommendations.py in utilities/tools/platform	118	2	3
New-AvmGitHubTeamsIssue.ps1 in utilities/pipelines/sharedScripts/teamLinter	42	-	2
Get-AvmGitHubTeamRepoConfiguration.ps1 in utilities/pipelines/sharedScripts/teamLinter	46	-	2
Set-BicepModulesFeatureCSV.ps1 in utilities/tools/platform	49	-	2
Get-AvmCsvData.ps1 in utilities/pipelines/sharedScripts/teamLinter	58	-	1
Test-AvmGitHubTeamPermission.ps1 in utilities/pipelines/sharedScripts/teamLinter	52	-	1
Get-AvmGitHubTeamsData.ps1 in utilities/pipelines/sharedScripts/teamLinter	70	-	1
Set-BicepModuleStatusBadgesTable.ps1 in utilities/tools/platform	40	-	1
Get-PipelineFileName.ps1 in utilities/tools/platform/helper	26	-	1