azure / checkaccess-v2-go-sdk

Intro

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.

File Size Overall

Legend:

1001+

501-1000

201-500

101-200

1-100

File Size per Extension

1001+

501-1000

201-500

101-200

1-100

File Size per Logical Decomposition

primary

1001+

501-1000

201-500

101-200

1-100

Longest Files (Top 5)

File	# lines	# units
client.go in client	109	4
types.go in client	70	-
token.go in client/internal/token	14	1
const.go in client	12	-
types.go in client/internal	10	-

Files With Most Units (Top 2)

File	# lines	# units
client.go in client	109	4
token.go in client/internal/token	14	1

Files With Long Lines (Top 1)

There is only one file with lines longer than 120 characters. In total, there are 3 long lines.

File	# lines	# units	# long lines
client.go in client	109	4	3

Correlations

File Size vs. Commits (all time): 5 points

		109.0	lines of code min: 10.0 average: 43.0 25th percentile: 11.0 median: 14.0 75th percentile: 89.5 max: 109.0
0	14.0
commits (all time) min: 2.0 \| average: 4.8 \| 25th percentile: 2.0 \| median: 3.0 \| 75th percentile: 8.5 \| max: 14.0

		109.0	lines of code min: 10.0 average: 43.0 25th percentile: 11.0 median: 14.0 75th percentile: 89.5 max: 109.0
0	4.0
contributors (all time) min: 2.0 \| average: 2.4 \| 25th percentile: 2.0 \| median: 2.0 \| 75th percentile: 3.0 \| max: 4.0

No data for "commits (30d)" vs. "lines of code".

No data for "contributors (30d)" vs. "lines of code".

No data for "commits (90d)" vs. "lines of code".

No data for "contributors (90d)" vs. "lines of code".