Executive summary
asdf-vm/asdf meets our standard for a preview release. It scores 68 out of 100 and is rated Strong, and all 29 of its critical findings are security problems.
Code Health, at 62, is the weakest lens and counts most in the score. The best first step is turning on missing-value checks, worth about 5 points. Handling the errors the code catches and ignores is another step, worth about 2 points. Raising Code Health to 67 would lift the score to about 70.
Twenty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Five secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. Giving the pull-request workflow read-only access would fix the pipeline that outsiders can trigger with write access.
The product code is 5,144 lines, about €14,000 to rebuild.
If Code Health rose from 62 to 67, the lowest score rated Strong, the score would rise from 68 to about 70.
New since the last survey: 3 findings
- Code Duplication · Edited copy of a member (31 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (12 corresponding lines) internal/git/git.go
- Code Duplication · Edited copy of a member (9 corresponding lines) internal/shims/shims.go
Fixed since the last survey: 4 findings
- Cyclomatic Complexity · checkstyle.main (cyclomatic 17) scripts/checkstyle.py
- Cyclomatic Complexity · checkstyle.lintfile (cyclomatic 16) scripts/checkstyle.py
- Cognitive Complexity · checkstyle.main (cognitive 37) scripts/checkstyle.py
- Cognitive Complexity · checkstyle.lintfile (cognitive 36) scripts/checkstyle.py
Rebuild cost: about €14,000 · Estimate
| Cost to rebuild | €4,600 to €23,000, for 76 to 241 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×1.0 at a score of 68. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,144 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 github.com/asdf-vm/asdf/cmd/asdf | 2 github.com/asdf-vm/asdf/internal/completions | 3 github.com/asdf-vm/asdf/internal/config | 4 github.com/asdf-vm/asdf/internal/data | 5 github.com/asdf-vm/asdf/internal/exec | 6 github.com/asdf-vm/asdf/internal/execute | 7 github.com/asdf-vm/asdf/internal/git | 8 github.com/asdf-vm/asdf/internal/paths | 9 github.com/asdf-vm/asdf/internal/repotest | 10 github.com/asdf-vm/asdf/internal/toolversions | 11 scripts | 12 scripts.checkstyle | 13 github.com/asdf-vm/asdf/internal/cli/set | 14 github.com/asdf-vm/asdf/internal/hook | 15 github.com/asdf-vm/asdf/internal/pluginindex | 16 github.com/asdf-vm/asdf/internal/plugins | 17 github.com/asdf-vm/asdf/internal/execenv | 18 github.com/asdf-vm/asdf/internal/help | 19 github.com/asdf-vm/asdf/internal/info | 20 github.com/asdf-vm/asdf/internal/installs | 21 github.com/asdf-vm/asdf/internal/installtest | 22 github.com/asdf-vm/asdf/internal/resolve | 23 github.com/asdf-vm/asdf/internal/shims | 24 github.com/asdf-vm/asdf/internal/versions | 25 github.com/asdf-vm/asdf/internal/cli |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 github.com/asdf-vm/asdf/cmd/asdf | |||||||||||||||||||||||||
| 2 github.com/asdf-vm/asdf/internal/completions | |||||||||||||||||||||||||
| 3 github.com/asdf-vm/asdf/internal/config | |||||||||||||||||||||||||
| 4 github.com/asdf-vm/asdf/internal/data | |||||||||||||||||||||||||
| 5 github.com/asdf-vm/asdf/internal/exec | |||||||||||||||||||||||||
| 6 github.com/asdf-vm/asdf/internal/execute | |||||||||||||||||||||||||
| 7 github.com/asdf-vm/asdf/internal/git | |||||||||||||||||||||||||
| 8 github.com/asdf-vm/asdf/internal/paths | |||||||||||||||||||||||||
| 9 github.com/asdf-vm/asdf/internal/repotest | |||||||||||||||||||||||||
| 10 github.com/asdf-vm/asdf/internal/toolversions | |||||||||||||||||||||||||
| 11 scripts | |||||||||||||||||||||||||
| 12 scripts.checkstyle | |||||||||||||||||||||||||
| 13 github.com/asdf-vm/asdf/internal/cli/set | 1 | ||||||||||||||||||||||||
| 14 github.com/asdf-vm/asdf/internal/hook | 1 | ||||||||||||||||||||||||
| 15 github.com/asdf-vm/asdf/internal/pluginindex | 2 | ||||||||||||||||||||||||
| 16 github.com/asdf-vm/asdf/internal/plugins | 2 | ||||||||||||||||||||||||
| 17 github.com/asdf-vm/asdf/internal/execenv | 1 | ||||||||||||||||||||||||
| 18 github.com/asdf-vm/asdf/internal/help | 1 | 1 | |||||||||||||||||||||||
| 19 github.com/asdf-vm/asdf/internal/info | 1 | 1 | |||||||||||||||||||||||
| 20 github.com/asdf-vm/asdf/internal/installs | 1 | 1 | 1 | ||||||||||||||||||||||
| 21 github.com/asdf-vm/asdf/internal/installtest | 1 | 1 | |||||||||||||||||||||||
| 22 github.com/asdf-vm/asdf/internal/resolve | 1 | 1 | |||||||||||||||||||||||
| 23 github.com/asdf-vm/asdf/internal/shims | 1 | 2 | 1 | ||||||||||||||||||||||
| 24 github.com/asdf-vm/asdf/internal/versions | 1 | 2 | 1 | ||||||||||||||||||||||
| 25 github.com/asdf-vm/asdf/internal/cli | 1 | 1 | 1 | 1 | 1 |
13→3 github.com/asdf-vm/asdf/internal/cli/set uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/cli/set uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/cli/set.set→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/cli/set uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/cli/set, while a change to github.com/asdf-vm/asdf/internal/cli/set can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/cli/set uses a module listed above it, which is the healthy direction.
14→3 github.com/asdf-vm/asdf/internal/hook uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/hook uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/hook.hook→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/hook uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/hook, while a change to github.com/asdf-vm/asdf/internal/hook can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/hook uses a module listed above it, which is the healthy direction.
15→7 github.com/asdf-vm/asdf/internal/pluginindex uses github.com/asdf-vm/asdf/internal/git✕
- Connections
- 2 pairs of types, where a type in github.com/asdf-vm/asdf/internal/pluginindex uses a type in github.com/asdf-vm/asdf/internal/git.
- The types involved
github.com/asdf-vm/asdf/internal/pluginindex.PluginIndex→github.com/asdf-vm/asdf/internal/git.Repoergithub.com/asdf-vm/asdf/internal/pluginindex.pluginindex→github.com/asdf-vm/asdf/internal/git.Repoer
- Direction
- github.com/asdf-vm/asdf/internal/pluginindex uses github.com/asdf-vm/asdf/internal/git, so a change to github.com/asdf-vm/asdf/internal/git can break github.com/asdf-vm/asdf/internal/pluginindex, while a change to github.com/asdf-vm/asdf/internal/pluginindex can't break github.com/asdf-vm/asdf/internal/git.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/pluginindex uses a module listed above it, which is the healthy direction.
16→3 github.com/asdf-vm/asdf/internal/plugins uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 2 pairs of types, where a type in github.com/asdf-vm/asdf/internal/plugins uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/plugins.Plugin→github.com/asdf-vm/asdf/internal/config.Configgithub.com/asdf-vm/asdf/internal/plugins.plugins→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/plugins uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/plugins, while a change to github.com/asdf-vm/asdf/internal/plugins can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/plugins uses a module listed above it, which is the healthy direction.
17→16 github.com/asdf-vm/asdf/internal/execenv uses github.com/asdf-vm/asdf/internal/plugins✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/execenv uses a type in github.com/asdf-vm/asdf/internal/plugins.
- The types involved
github.com/asdf-vm/asdf/internal/execenv.execenv→github.com/asdf-vm/asdf/internal/plugins.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/execenv uses github.com/asdf-vm/asdf/internal/plugins, so a change to github.com/asdf-vm/asdf/internal/plugins can break github.com/asdf-vm/asdf/internal/execenv, while a change to github.com/asdf-vm/asdf/internal/execenv can't break github.com/asdf-vm/asdf/internal/plugins.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/execenv uses a module listed above it, which is the healthy direction.
18→3 github.com/asdf-vm/asdf/internal/help uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/help uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/help.help→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/help uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/help, while a change to github.com/asdf-vm/asdf/internal/help can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/help uses a module listed above it, which is the healthy direction.
18→16 github.com/asdf-vm/asdf/internal/help uses github.com/asdf-vm/asdf/internal/plugins✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/help uses a type in github.com/asdf-vm/asdf/internal/plugins.
- The types involved
github.com/asdf-vm/asdf/internal/help.help→github.com/asdf-vm/asdf/internal/plugins.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/help uses github.com/asdf-vm/asdf/internal/plugins, so a change to github.com/asdf-vm/asdf/internal/plugins can break github.com/asdf-vm/asdf/internal/help, while a change to github.com/asdf-vm/asdf/internal/help can't break github.com/asdf-vm/asdf/internal/plugins.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/help uses a module listed above it, which is the healthy direction.
19→3 github.com/asdf-vm/asdf/internal/info uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/info uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/info.info→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/info uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/info, while a change to github.com/asdf-vm/asdf/internal/info can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/info uses a module listed above it, which is the healthy direction.
19→16 github.com/asdf-vm/asdf/internal/info uses github.com/asdf-vm/asdf/internal/plugins✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/info uses a type in github.com/asdf-vm/asdf/internal/plugins.
- The types involved
github.com/asdf-vm/asdf/internal/info.info→github.com/asdf-vm/asdf/internal/plugins.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/info uses github.com/asdf-vm/asdf/internal/plugins, so a change to github.com/asdf-vm/asdf/internal/plugins can break github.com/asdf-vm/asdf/internal/info, while a change to github.com/asdf-vm/asdf/internal/info can't break github.com/asdf-vm/asdf/internal/plugins.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/info uses a module listed above it, which is the healthy direction.
20→3 github.com/asdf-vm/asdf/internal/installs uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/installs uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/installs.installs→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/installs uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/installs, while a change to github.com/asdf-vm/asdf/internal/installs can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/installs uses a module listed above it, which is the healthy direction.
20→10 github.com/asdf-vm/asdf/internal/installs uses github.com/asdf-vm/asdf/internal/toolversions✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/installs uses a type in github.com/asdf-vm/asdf/internal/toolversions.
- The types involved
github.com/asdf-vm/asdf/internal/installs.installs→github.com/asdf-vm/asdf/internal/toolversions.Version
- Direction
- github.com/asdf-vm/asdf/internal/installs uses github.com/asdf-vm/asdf/internal/toolversions, so a change to github.com/asdf-vm/asdf/internal/toolversions can break github.com/asdf-vm/asdf/internal/installs, while a change to github.com/asdf-vm/asdf/internal/installs can't break github.com/asdf-vm/asdf/internal/toolversions.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/installs uses a module listed above it, which is the healthy direction.
20→16 github.com/asdf-vm/asdf/internal/installs uses github.com/asdf-vm/asdf/internal/plugins✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/installs uses a type in github.com/asdf-vm/asdf/internal/plugins.
- The types involved
github.com/asdf-vm/asdf/internal/installs.installs→github.com/asdf-vm/asdf/internal/plugins.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/installs uses github.com/asdf-vm/asdf/internal/plugins, so a change to github.com/asdf-vm/asdf/internal/plugins can break github.com/asdf-vm/asdf/internal/installs, while a change to github.com/asdf-vm/asdf/internal/installs can't break github.com/asdf-vm/asdf/internal/plugins.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/installs uses a module listed above it, which is the healthy direction.
21→3 github.com/asdf-vm/asdf/internal/installtest uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/installtest uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/installtest.installtest→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/installtest uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/installtest, while a change to github.com/asdf-vm/asdf/internal/installtest can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/installtest uses a module listed above it, which is the healthy direction.
21→16 github.com/asdf-vm/asdf/internal/installtest uses github.com/asdf-vm/asdf/internal/plugins✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/installtest uses a type in github.com/asdf-vm/asdf/internal/plugins.
- The types involved
github.com/asdf-vm/asdf/internal/installtest.installtest→github.com/asdf-vm/asdf/internal/plugins.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/installtest uses github.com/asdf-vm/asdf/internal/plugins, so a change to github.com/asdf-vm/asdf/internal/plugins can break github.com/asdf-vm/asdf/internal/installtest, while a change to github.com/asdf-vm/asdf/internal/installtest can't break github.com/asdf-vm/asdf/internal/plugins.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/installtest uses a module listed above it, which is the healthy direction.
22→3 github.com/asdf-vm/asdf/internal/resolve uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/resolve uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/resolve.resolve→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/resolve uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/resolve, while a change to github.com/asdf-vm/asdf/internal/resolve can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/resolve uses a module listed above it, which is the healthy direction.
22→16 github.com/asdf-vm/asdf/internal/resolve uses github.com/asdf-vm/asdf/internal/plugins✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/resolve uses a type in github.com/asdf-vm/asdf/internal/plugins.
- The types involved
github.com/asdf-vm/asdf/internal/resolve.resolve→github.com/asdf-vm/asdf/internal/plugins.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/resolve uses github.com/asdf-vm/asdf/internal/plugins, so a change to github.com/asdf-vm/asdf/internal/plugins can break github.com/asdf-vm/asdf/internal/resolve, while a change to github.com/asdf-vm/asdf/internal/resolve can't break github.com/asdf-vm/asdf/internal/plugins.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/resolve uses a module listed above it, which is the healthy direction.
23→3 github.com/asdf-vm/asdf/internal/shims uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/shims uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/shims.shims→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/shims uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/shims, while a change to github.com/asdf-vm/asdf/internal/shims can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/shims uses a module listed above it, which is the healthy direction.
23→10 github.com/asdf-vm/asdf/internal/shims uses github.com/asdf-vm/asdf/internal/toolversions✕
- Connections
- 2 pairs of types, where a type in github.com/asdf-vm/asdf/internal/shims uses a type in github.com/asdf-vm/asdf/internal/toolversions.
- The types involved
github.com/asdf-vm/asdf/internal/shims.shims→github.com/asdf-vm/asdf/internal/toolversions.ToolVersionsgithub.com/asdf-vm/asdf/internal/shims.shims→github.com/asdf-vm/asdf/internal/toolversions.Version
- Direction
- github.com/asdf-vm/asdf/internal/shims uses github.com/asdf-vm/asdf/internal/toolversions, so a change to github.com/asdf-vm/asdf/internal/toolversions can break github.com/asdf-vm/asdf/internal/shims, while a change to github.com/asdf-vm/asdf/internal/shims can't break github.com/asdf-vm/asdf/internal/toolversions.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/shims uses a module listed above it, which is the healthy direction.
23→16 github.com/asdf-vm/asdf/internal/shims uses github.com/asdf-vm/asdf/internal/plugins✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/shims uses a type in github.com/asdf-vm/asdf/internal/plugins.
- The types involved
github.com/asdf-vm/asdf/internal/shims.shims→github.com/asdf-vm/asdf/internal/plugins.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/shims uses github.com/asdf-vm/asdf/internal/plugins, so a change to github.com/asdf-vm/asdf/internal/plugins can break github.com/asdf-vm/asdf/internal/shims, while a change to github.com/asdf-vm/asdf/internal/shims can't break github.com/asdf-vm/asdf/internal/plugins.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/shims uses a module listed above it, which is the healthy direction.
24→3 github.com/asdf-vm/asdf/internal/versions uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/versions uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/versions.versions→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/versions uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/versions, while a change to github.com/asdf-vm/asdf/internal/versions can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/versions uses a module listed above it, which is the healthy direction.
24→10 github.com/asdf-vm/asdf/internal/versions uses github.com/asdf-vm/asdf/internal/toolversions✕
- Connections
- 2 pairs of types, where a type in github.com/asdf-vm/asdf/internal/versions uses a type in github.com/asdf-vm/asdf/internal/toolversions.
- The types involved
github.com/asdf-vm/asdf/internal/versions.VersionAlreadyInstalledError→github.com/asdf-vm/asdf/internal/toolversions.Versiongithub.com/asdf-vm/asdf/internal/versions.versions→github.com/asdf-vm/asdf/internal/toolversions.Version
- Direction
- github.com/asdf-vm/asdf/internal/versions uses github.com/asdf-vm/asdf/internal/toolversions, so a change to github.com/asdf-vm/asdf/internal/toolversions can break github.com/asdf-vm/asdf/internal/versions, while a change to github.com/asdf-vm/asdf/internal/versions can't break github.com/asdf-vm/asdf/internal/toolversions.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/versions uses a module listed above it, which is the healthy direction.
24→16 github.com/asdf-vm/asdf/internal/versions uses github.com/asdf-vm/asdf/internal/plugins✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/versions uses a type in github.com/asdf-vm/asdf/internal/plugins.
- The types involved
github.com/asdf-vm/asdf/internal/versions.versions→github.com/asdf-vm/asdf/internal/plugins.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/versions uses github.com/asdf-vm/asdf/internal/plugins, so a change to github.com/asdf-vm/asdf/internal/plugins can break github.com/asdf-vm/asdf/internal/versions, while a change to github.com/asdf-vm/asdf/internal/versions can't break github.com/asdf-vm/asdf/internal/plugins.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/versions uses a module listed above it, which is the healthy direction.
25→3 github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/config✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/cli uses a type in github.com/asdf-vm/asdf/internal/config.
- The types involved
github.com/asdf-vm/asdf/internal/cli.cli→github.com/asdf-vm/asdf/internal/config.Config
- Direction
- github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/config, so a change to github.com/asdf-vm/asdf/internal/config can break github.com/asdf-vm/asdf/internal/cli, while a change to github.com/asdf-vm/asdf/internal/cli can't break github.com/asdf-vm/asdf/internal/config.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/cli uses a module listed above it, which is the healthy direction.
25→10 github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/toolversions✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/cli uses a type in github.com/asdf-vm/asdf/internal/toolversions.
- The types involved
github.com/asdf-vm/asdf/internal/cli.cli→github.com/asdf-vm/asdf/internal/toolversions.ToolVersions
- Direction
- github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/toolversions, so a change to github.com/asdf-vm/asdf/internal/toolversions can break github.com/asdf-vm/asdf/internal/cli, while a change to github.com/asdf-vm/asdf/internal/cli can't break github.com/asdf-vm/asdf/internal/toolversions.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/cli uses a module listed above it, which is the healthy direction.
25→15 github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/pluginindex✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/cli uses a type in github.com/asdf-vm/asdf/internal/pluginindex.
- The types involved
github.com/asdf-vm/asdf/internal/cli.cli→github.com/asdf-vm/asdf/internal/pluginindex.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/pluginindex, so a change to github.com/asdf-vm/asdf/internal/pluginindex can break github.com/asdf-vm/asdf/internal/cli, while a change to github.com/asdf-vm/asdf/internal/cli can't break github.com/asdf-vm/asdf/internal/pluginindex.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/cli uses a module listed above it, which is the healthy direction.
25→16 github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/plugins✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/cli uses a type in github.com/asdf-vm/asdf/internal/plugins.
- The types involved
github.com/asdf-vm/asdf/internal/cli.cli→github.com/asdf-vm/asdf/internal/plugins.Plugin
- Direction
- github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/plugins, so a change to github.com/asdf-vm/asdf/internal/plugins can break github.com/asdf-vm/asdf/internal/cli, while a change to github.com/asdf-vm/asdf/internal/cli can't break github.com/asdf-vm/asdf/internal/plugins.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/cli uses a module listed above it, which is the healthy direction.
25→22 github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/resolve✕
- Connections
- 1 pair of types, where a type in github.com/asdf-vm/asdf/internal/cli uses a type in github.com/asdf-vm/asdf/internal/resolve.
- The types involved
github.com/asdf-vm/asdf/internal/cli.cli→github.com/asdf-vm/asdf/internal/resolve.ToolVersions
- Direction
- github.com/asdf-vm/asdf/internal/cli uses github.com/asdf-vm/asdf/internal/resolve, so a change to github.com/asdf-vm/asdf/internal/resolve can break github.com/asdf-vm/asdf/internal/cli, while a change to github.com/asdf-vm/asdf/internal/cli can't break github.com/asdf-vm/asdf/internal/resolve.
- Position
- Below the diagonal: github.com/asdf-vm/asdf/internal/cli uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 31 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 13 | High / Critical |
Roadmap
Top priorities: The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`); Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with shims.FindExecutable (cognitive 53), cli.installCommand (cognitive 45), cli.listLocalCommand (cognitive 36); Swallowed exception (caught, then discarded).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`). | +5.5 pts | Medium | Nullable reference types |
| Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +1.1 pts | Low | Static Analysis (SAST) |
| Swallowed exception (caught, then discarded) | +2.0 pts | Medium | Exception handling |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +0.9 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. | +0.8 pts | Low | Documentation Quality |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. | +0.7 pts | Low | Supply-chain Provenance & Signing |
| Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with shims.FindExecutable (cognitive 53), cli.installCommand (cognitive 45), cli.listLocalCommand (cognitive 36). | +2.8 pts | High | Cognitive Complexity |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 1.4 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| internal/plugins/plugins.go | 6.7 | Mixed | Explicit Debt: TodoComment |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| internal/shims/shims.go | 7.4 | Near-clean | Cyclomatic Complexity: shims.FindExecutable (cyclomatic 21) |
| internal/versions/versions.go | 7.8 | Near-clean | Cyclomatic Complexity: versions.InstallOneVersion (cyclomatic 27) |
| internal/cli/set/set.go | 7.8 | Near-clean | Cyclomatic Complexity: set.Main (cyclomatic 16) |
| internal/git/git.go | 8.5 | Near-clean | Code Duplication: Edited copy of a member (12 corresponding lines) |
| internal/resolve/resolve.go | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
| internal/help/help.go | 8.5 | Near-clean | Code Duplication: Duplicated block (5 lines × 2) |
| README.md | 9.5 | Near-clean | Documentation Quality: Documentation: no build, run or usage example |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 41 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 41 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 74 of 93 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a coverage step in CI (`go test -coverprofile`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.go), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Go module dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (REDACTED), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- ED5 Idempotency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Go is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Go is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala or Kotlin was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Go is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
6 function(s) exceeded the cyclomatic complexity threshold of 15; the worst was versions.InstallOneVersion at 27.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with versions.InstallOneVersion (cyclomatic 27), cli.pluginTestCommand (cyclomatic 21), shims.FindExecutable (cyclomatic 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 8.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
10 function(s) exceeded the cognitive complexity threshold of 15; the worst was shims.FindExecutable at 53.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with shims.FindExecutable (cognitive 53), cli.installCommand (cognitive 45), cli.listLocalCommand (cognitive 36). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 10 together lifts Cognitive Complexity from 6.8 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
2 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 1 FileTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
5 duplicated block group(s) detected. A further 3 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 1 Edited copy of a member (31 corresponding lines) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (12 corresponding lines) finding(s) in Code Duplication — start with git.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with shims.go. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 4 classes have LCOM4 above 3.
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (github.com/asdf-vm/asdf): measured (0 flaky).
D12 · Dependency Hygiene
9 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 49 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included. ★ COVERAGE OF THIS VERDICT: it grades this repository's Go module dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is internal/info/info.go. Counted over 15 of the 23 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
2 deducted task-comment markers across 5144 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 2 TodoComment finding(s) in Explicit Debt — start with plugins.go, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D19 · Documentation Quality
0 of 1 documentation facets pass in full; short on: F2 example. 96 document(s) read across 2 unit(s).
What to do
- Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D27 · Navigability
49 % of calls cross a namespace and 0 % go through an interface, but 17 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Resolve the 1 Scattered collaborators finding(s) in Navigability. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
31 finding(s): 0 critical, 28 high, 3 medium, 0 low. 21 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 21 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (21 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
5 finding(s): 0 critical, 0 high, 5 medium, 0 low.
What to do
- Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D34 · Knowledge Freshness
1 of 15 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is scripts/checkstyle.py. Counted over 15 of the 23 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
P3 · Security & performance tooling
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `gomod`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
- Dependabot is configured but does not watch `gomod` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
PF1 · Benchmark discipline
- A Go testing.B suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — internal/toolversions/toolversions_test.go
What to do
- Call b.ReportAllocs() in the benchmarks, or run them with `go test -bench . -benchmem`, so allocation regressions are visible, not just time.
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `if osErr != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/resolve/resolve.go:45
- `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — internal/installs/installs.go:82
What to do
- Swallowed exception (caught, then discarded)
X5 · Nullable reference types
- This repository commits no tsconfig, so whatever type-checks it uses tsc's own defaults, in which `strict` and `strictNullChecks` are OFF: `string` admits `null` and `undefined`, and a value that is null is compiled through to the property access that throws. If the build passes `--strict` on a command line instead, put it in a committed tsconfig — this check reads configuration, and configuration is all it can read.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 62% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 91% | Exemplary | Strongest area. |
| Maturity | 81% | Strong | Solid. |
| Readiness | 76% | Strong | Solid. |
| Security | 65% | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 85% | Exemplary | Solid. |
Unscored — 1 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 71 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~4041 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Go, Python not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go, .py source were not judged.
- D25 ADR Conformance — None of 1 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (4407 LoC, 46 module-visible types across 22 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 CQRS handler(s))
- ED5 Idempotency — Not assessed, and this one is on us: 1 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Go, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 29 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 43 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- TodoComment internal/plugins/plugins.go:322
- TodoComment REDACTED:825
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Swallowed exception (caught, then discarded) internal/resolve/resolve.go:45
- Swallowed exception (caught, then discarded) internal/installs/installs.go:82
- versions.InstallOneVersion (cyclomatic 27) internal/versions/versions.go:145
- cli.pluginTestCommand (cyclomatic 21) REDACTED:978
- shims.FindExecutable (cyclomatic 21) internal/shims/shims.go:66
- cli.installCommand (cyclomatic 16) REDACTED:1099
- cli.listLocalCommand (cyclomatic 16) REDACTED:1311
- set.Main (cyclomatic 16) internal/cli/set/set.go:19
- shims.FindExecutable (cognitive 53) internal/shims/shims.go:66
- cli.installCommand (cognitive 45) REDACTED:1099
- cli.listLocalCommand (cognitive 36) REDACTED:1311
- plugins.List (cognitive 33) internal/plugins/plugins.go:303
- cli.getExecutable (cognitive 27) REDACTED:680
- versions.InstallOneVersion (cognitive 27) internal/versions/versions.go:145
- cli.pluginTestCommand (cognitive 25) REDACTED:978
- set.Main (cognitive 22) internal/cli/set/set.go:19
- cli.currentCommand (cognitive 16) REDACTED:400
- cli.whereCommand (cognitive 16) REDACTED:1514
- REDACTED
- FileTooLong: REDACTED REDACTED
- FunctionTooLong: cli.Execute REDACTED:52
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (31 corresponding lines) REDACTED:772
- Edited copy of a member (12 corresponding lines) internal/git/git.go:59
- Edited copy of a member (9 corresponding lines) internal/shims/shims.go:206
- Duplicated block (18 lines × 2) REDACTED:548
- Duplicated block (12–13 lines × 2) REDACTED:1339
- Duplicated block (9 lines × 2) REDACTED:1301
- Duplicated block (10 lines × 2) internal/resolve/resolve.go:122
- Duplicated block (5 lines × 2) internal/help/help.go:126
- Coverage collected but not gated
Minor — 12 finding(s)
- Off-boarding risk: anonymized user #1
- Documentation: no build, run or usage example README.md:1
- Scattered collaborators
- Orphaned files with no living knowledge
- Orphaned file scripts/checkstyle.py:1
- REDACTED
- REDACTED
- REDACTED
- Dependabot does not watch gomod REDACTED:2
- No release approval gate
- Benchmarks don't track allocations internal/toolversions/toolversions_test.go
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 9 finding(s)
- Outdated: github.com/go-git/go-git/v5
- Outdated: github.com/mgechev/revive
- Outdated: github.com/otiai10/copy
- Outdated: github.com/rogpeppe/go-internal
- Outdated: github.com/urfave/cli/v3
- Outdated: golang.org/x/sys
- Outdated: gopkg.in/ini.v1
- Outdated: honnef.co/go/tools
- Outdated: mvdan.cc/gofumpt
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b07e4eff2d16453cb5451db4b4969370/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-b07e4eff2d16453cb5451db4b4969370/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 31 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 5 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |