Executive summary
tmorin/plantuml-libs is rated At risk because critical security findings are open, all of them in the packages it uses. It scores 52.4 out of 100, which the At risk rating leaves unchanged.
Code Health, at 43.8, is the weakest lens and counts most in the score. The best first step is removing the copied code, worth about 4.4 points. Adding a diagnostic log comes next, worth about 3.8 points. Raising Code Health to 70 would lift the score to about 58.3.
Five known security holes in the packages the code depends on can be used by attackers. One form field can't be read by a screen reader. Updating the vulnerable packages and labelling the form fields would close both risks. The use of a package that isn't listed needs adding to the project's list of dependencies.
The product code is 7,162 lines, about €7,400 to rebuild.
If Code Health rose from 43.8 to 70, the lowest score rated Strong, the score would rise from 52.4 to about 58.3.
Rebuild cost: about €7,400 · Estimate
| Cost to rebuild | €2,500 to €12,000, for 41 to 131 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 | ×0.7 at a score of 52. 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: 7,162 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 bin | 2 docs.wav.wav-003-workdir-generation-hardening.run.run-0014-workdir-reference-validation.workflows | 3 docs.wav.wav-003-workdir-generation-hardening.run.run-0015-archive-integrity.workflows | 4 docs.wav.wav-003-workdir-generation-hardening.run.run-0016-aws-families-and-resolver.workflows | 5 docs.wav.wav-003-workdir-generation-hardening.run.run-0017-distribution-regen-aws-on-ci.workflows | 6 docs.wav.wav-003-workdir-generation-hardening.workflows | 7 scripts | 8 source.generator | 9 source.generator.website.config | 10 source.generator.website.templates | 11 source.generator.workdir.manifest | 12 source | 13 source.generator.website | 14 source.generator.website.sitemap | 15 source.generator.website.stage | 16 source.generator.workdir.factories | 17 source.library.packages | 18 source.generator.website.resource | 19 source.generator.website.summary | 20 source.generator.workdir | 21 source.library.packages.aws | 22 source.library.packages.azure | 23 source.library.packages.c4k8s | 24 source.library.packages.c4model | 25 source.library.packages.c4nord | 26 source.library.packages.domainstorytelling | 27 source.library.packages.eip | 28 source.library.packages.eventstorming | 29 source.library.packages.fontawesome | 30 source.library.packages.gcp | 31 source.library.packages.material | 32 source.library.packages.simpleicons | 33 source.generator.website.extract | 34 source.generator.website.transform | 35 source.generator.website.load |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 bin | |||||||||||||||||||||||||||||||||||
| 2 docs.wav.wav-003-workdir-generation-hardening.run.run-0014-workdir-reference-validation.workflows | |||||||||||||||||||||||||||||||||||
| 3 docs.wav.wav-003-workdir-generation-hardening.run.run-0015-archive-integrity.workflows | |||||||||||||||||||||||||||||||||||
| 4 docs.wav.wav-003-workdir-generation-hardening.run.run-0016-aws-families-and-resolver.workflows | |||||||||||||||||||||||||||||||||||
| 5 docs.wav.wav-003-workdir-generation-hardening.run.run-0017-distribution-regen-aws-on-ci.workflows | |||||||||||||||||||||||||||||||||||
| 6 docs.wav.wav-003-workdir-generation-hardening.workflows | |||||||||||||||||||||||||||||||||||
| 7 scripts | |||||||||||||||||||||||||||||||||||
| 8 source.generator | |||||||||||||||||||||||||||||||||||
| 9 source.generator.website.config | |||||||||||||||||||||||||||||||||||
| 10 source.generator.website.templates | |||||||||||||||||||||||||||||||||||
| 11 source.generator.workdir.manifest | |||||||||||||||||||||||||||||||||||
| 12 source | 2 | ||||||||||||||||||||||||||||||||||
| 13 source.generator.website | 1 | 1 | |||||||||||||||||||||||||||||||||
| 14 source.generator.website.sitemap | 1 | ||||||||||||||||||||||||||||||||||
| 15 source.generator.website.stage | 1 | ||||||||||||||||||||||||||||||||||
| 16 source.generator.workdir.factories | 1 | ||||||||||||||||||||||||||||||||||
| 17 source.library.packages | 1 | ||||||||||||||||||||||||||||||||||
| 18 source.generator.website.resource | 3 | 1 | |||||||||||||||||||||||||||||||||
| 19 source.generator.website.summary | 3 | ||||||||||||||||||||||||||||||||||
| 20 source.generator.workdir | 2 | 3 | |||||||||||||||||||||||||||||||||
| 21 source.library.packages.aws | 2 | 2 | |||||||||||||||||||||||||||||||||
| 22 source.library.packages.azure | 2 | 2 | |||||||||||||||||||||||||||||||||
| 23 source.library.packages.c4k8s | 1 | 1 | |||||||||||||||||||||||||||||||||
| 24 source.library.packages.c4model | 1 | 1 | |||||||||||||||||||||||||||||||||
| 25 source.library.packages.c4nord | 1 | 1 | |||||||||||||||||||||||||||||||||
| 26 source.library.packages.domainstorytelling | 1 | 2 | |||||||||||||||||||||||||||||||||
| 27 source.library.packages.eip | 2 | 2 | |||||||||||||||||||||||||||||||||
| 28 source.library.packages.eventstorming | 1 | 2 | |||||||||||||||||||||||||||||||||
| 29 source.library.packages.fontawesome | 1 | 2 | |||||||||||||||||||||||||||||||||
| 30 source.library.packages.gcp | 2 | 2 | |||||||||||||||||||||||||||||||||
| 31 source.library.packages.material | 1 | 2 | |||||||||||||||||||||||||||||||||
| 32 source.library.packages.simpleicons | 1 | 2 | |||||||||||||||||||||||||||||||||
| 33 source.generator.website.extract | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||
| 34 source.generator.website.transform | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 35 source.generator.website.load | 1 | 1 | 1 |
12→11 source uses source.generator.workdir.manifest✕
- Connections
- 2 pairs of types, where a type in source uses a type in source.generator.workdir.manifest.
- The types involved
source.index→source.generator.workdir.manifest.Librarysource.index→source.generator.workdir.manifest.Package
- Direction
- source uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source, while a change to source can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source uses a module listed above it, which is the healthy direction.
13→9 source.generator.website uses source.generator.website.config✕
- Connections
- 1 pair of types, where a type in source.generator.website uses a type in source.generator.website.config.
- The types involved
source.generator.website.templates→source.generator.website.config.Config
- Direction
- source.generator.website uses source.generator.website.config, so a change to source.generator.website.config can break source.generator.website, while a change to source.generator.website can't break source.generator.website.config.
- Position
- Below the diagonal: source.generator.website uses a module listed above it, which is the healthy direction.
13→10 source.generator.website uses source.generator.website.templates✕
- Connections
- 1 pair of types, where a type in source.generator.website uses a type in source.generator.website.templates.
- The types involved
source.generator.website.templates→source.generator.website.templates.SimplePage
- Direction
- source.generator.website uses source.generator.website.templates, so a change to source.generator.website.templates can break source.generator.website, while a change to source.generator.website can't break source.generator.website.templates.
- Position
- Below the diagonal: source.generator.website uses a module listed above it, which is the healthy direction.
14→18 source.generator.website.sitemap uses source.generator.website.resource part of a loop✕
- Connections
- 1 pair of types, where a type in source.generator.website.sitemap uses a type in source.generator.website.resource.
- The types involved
source.generator.website.sitemap.Sitemap→source.generator.website.resource.InputResource
- Direction
- source.generator.website.sitemap uses source.generator.website.resource, so a change to source.generator.website.resource can break source.generator.website.sitemap, while a change to source.generator.website.sitemap can't break source.generator.website.resource.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→9 source.generator.website.stage uses source.generator.website.config✕
- Connections
- 1 pair of types, where a type in source.generator.website.stage uses a type in source.generator.website.config.
- The types involved
source.generator.website.stage.Stage→source.generator.website.config.Config
- Direction
- source.generator.website.stage uses source.generator.website.config, so a change to source.generator.website.config can break source.generator.website.stage, while a change to source.generator.website.stage can't break source.generator.website.config.
- Position
- Below the diagonal: source.generator.website.stage uses a module listed above it, which is the healthy direction.
16→11 source.generator.workdir.factories uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.generator.workdir.factories uses a type in source.generator.workdir.manifest.
- The types involved
source.generator.workdir.factories.PackageFactory→source.generator.workdir.manifest.Package
- Direction
- source.generator.workdir.factories uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.generator.workdir.factories, while a change to source.generator.workdir.factories can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.generator.workdir.factories uses a module listed above it, which is the healthy direction.
17→11 source.library.packages uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.library.packages uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.index→source.generator.workdir.manifest.Item
- Direction
- source.library.packages uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages, while a change to source.library.packages can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages uses a module listed above it, which is the healthy direction.
18→9 source.generator.website.resource uses source.generator.website.config✕
- Connections
- 3 pairs of types, where a type in source.generator.website.resource uses a type in source.generator.website.config.
- The types involved
source.generator.website.resource.BinaryCopyResource→source.generator.website.config.Configsource.generator.website.resource.BufferedResource→source.generator.website.config.Configsource.generator.website.resource.MdtoHtmlResource→source.generator.website.config.Config
- Direction
- source.generator.website.resource uses source.generator.website.config, so a change to source.generator.website.config can break source.generator.website.resource, while a change to source.generator.website.resource can't break source.generator.website.config.
- Position
- Below the diagonal: source.generator.website.resource uses a module listed above it, which is the healthy direction.
18→14 source.generator.website.resource uses source.generator.website.sitemap✕
- Connections
- 1 pair of types, where a type in source.generator.website.resource uses a type in source.generator.website.sitemap.
- The types involved
source.generator.website.resource.MdtoHtmlResource→source.generator.website.sitemap.Sitemap
- Direction
- source.generator.website.resource uses source.generator.website.sitemap, so a change to source.generator.website.sitemap can break source.generator.website.resource, while a change to source.generator.website.resource can't break source.generator.website.sitemap.
- Position
- Below the diagonal: source.generator.website.resource uses a module listed above it, which is the healthy direction.
19→14 source.generator.website.summary uses source.generator.website.sitemap✕
- Connections
- 3 pairs of types, where a type in source.generator.website.summary uses a type in source.generator.website.sitemap.
- The types involved
source.generator.website.summary.ItemsSummaryAsJson→source.generator.website.sitemap.Sitemapsource.generator.website.summary.SideSummaryAsHtml→source.generator.website.sitemap.Sitemapsource.generator.website.summary.Summary→source.generator.website.sitemap.Sitemap
- Direction
- source.generator.website.summary uses source.generator.website.sitemap, so a change to source.generator.website.sitemap can break source.generator.website.summary, while a change to source.generator.website.summary can't break source.generator.website.sitemap.
- Position
- Below the diagonal: source.generator.website.summary uses a module listed above it, which is the healthy direction.
20→11 source.generator.workdir uses source.generator.workdir.manifest✕
- Connections
- 2 pairs of types, where a type in source.generator.workdir uses a type in source.generator.workdir.manifest.
- The types involved
source.generator.workdir.discovery→source.generator.workdir.manifest.Itemsource.generator.workdir.validation→source.generator.workdir.manifest.Package
- Direction
- source.generator.workdir uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.generator.workdir, while a change to source.generator.workdir can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.generator.workdir uses a module listed above it, which is the healthy direction.
20→16 source.generator.workdir uses source.generator.workdir.factories✕
- Connections
- 3 pairs of types, where a type in source.generator.workdir uses a type in source.generator.workdir.factories.
- The types involved
source.generator.workdir.archive→source.generator.workdir.factories.PackageContextsource.generator.workdir.discovery→source.generator.workdir.factories.PackageFactorysource.generator.workdir.paths→source.generator.workdir.factories.PackageContext
- Direction
- source.generator.workdir uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.generator.workdir, while a change to source.generator.workdir can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.generator.workdir uses a module listed above it, which is the healthy direction.
21→11 source.library.packages.aws uses source.generator.workdir.manifest✕
- Connections
- 2 pairs of types, where a type in source.library.packages.aws uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.aws.AwsFactory→source.generator.workdir.manifest.Itemsource.library.packages.aws.AwsFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.aws uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.aws, while a change to source.library.packages.aws can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.aws uses a module listed above it, which is the healthy direction.
21→16 source.library.packages.aws uses source.generator.workdir.factories✕
- Connections
- 2 pairs of types, where a type in source.library.packages.aws uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.aws.AwsFactory→source.generator.workdir.factories.PackageContextsource.library.packages.aws.AwsFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.aws uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.aws, while a change to source.library.packages.aws can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.aws uses a module listed above it, which is the healthy direction.
22→11 source.library.packages.azure uses source.generator.workdir.manifest✕
- Connections
- 2 pairs of types, where a type in source.library.packages.azure uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.azure.AzureFactory→source.generator.workdir.manifest.Itemsource.library.packages.azure.AzureFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.azure uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.azure, while a change to source.library.packages.azure can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.azure uses a module listed above it, which is the healthy direction.
22→16 source.library.packages.azure uses source.generator.workdir.factories✕
- Connections
- 2 pairs of types, where a type in source.library.packages.azure uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.azure.AzureFactory→source.generator.workdir.factories.PackageContextsource.library.packages.azure.AzureFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.azure uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.azure, while a change to source.library.packages.azure can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.azure uses a module listed above it, which is the healthy direction.
23→11 source.library.packages.c4k8s uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.library.packages.c4k8s uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.c4k8s.C4K8sFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.c4k8s uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.c4k8s, while a change to source.library.packages.c4k8s can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.c4k8s uses a module listed above it, which is the healthy direction.
23→16 source.library.packages.c4k8s uses source.generator.workdir.factories✕
- Connections
- 1 pair of types, where a type in source.library.packages.c4k8s uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.c4k8s.C4K8sFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.c4k8s uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.c4k8s, while a change to source.library.packages.c4k8s can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.c4k8s uses a module listed above it, which is the healthy direction.
24→11 source.library.packages.c4model uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.library.packages.c4model uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.c4model.C4modelFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.c4model uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.c4model, while a change to source.library.packages.c4model can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.c4model uses a module listed above it, which is the healthy direction.
24→16 source.library.packages.c4model uses source.generator.workdir.factories✕
- Connections
- 1 pair of types, where a type in source.library.packages.c4model uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.c4model.C4modelFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.c4model uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.c4model, while a change to source.library.packages.c4model can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.c4model uses a module listed above it, which is the healthy direction.
25→11 source.library.packages.c4nord uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.library.packages.c4nord uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.c4nord.C4nordFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.c4nord uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.c4nord, while a change to source.library.packages.c4nord can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.c4nord uses a module listed above it, which is the healthy direction.
25→16 source.library.packages.c4nord uses source.generator.workdir.factories✕
- Connections
- 1 pair of types, where a type in source.library.packages.c4nord uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.c4nord.C4nordFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.c4nord uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.c4nord, while a change to source.library.packages.c4nord can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.c4nord uses a module listed above it, which is the healthy direction.
26→11 source.library.packages.domainstorytelling uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.library.packages.domainstorytelling uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.domainstorytelling.DomainstorytellingFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.domainstorytelling uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.domainstorytelling, while a change to source.library.packages.domainstorytelling can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.domainstorytelling uses a module listed above it, which is the healthy direction.
26→16 source.library.packages.domainstorytelling uses source.generator.workdir.factories✕
- Connections
- 2 pairs of types, where a type in source.library.packages.domainstorytelling uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.domainstorytelling.DomainstorytellingFactory→source.generator.workdir.factories.PackageContextsource.library.packages.domainstorytelling.DomainstorytellingFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.domainstorytelling uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.domainstorytelling, while a change to source.library.packages.domainstorytelling can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.domainstorytelling uses a module listed above it, which is the healthy direction.
27→11 source.library.packages.eip uses source.generator.workdir.manifest✕
- Connections
- 2 pairs of types, where a type in source.library.packages.eip uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.eip.EipFactory→source.generator.workdir.manifest.Itemsource.library.packages.eip.EipFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.eip uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.eip, while a change to source.library.packages.eip can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.eip uses a module listed above it, which is the healthy direction.
27→16 source.library.packages.eip uses source.generator.workdir.factories✕
- Connections
- 2 pairs of types, where a type in source.library.packages.eip uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.eip.EipFactory→source.generator.workdir.factories.PackageContextsource.library.packages.eip.EipFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.eip uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.eip, while a change to source.library.packages.eip can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.eip uses a module listed above it, which is the healthy direction.
28→11 source.library.packages.eventstorming uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.library.packages.eventstorming uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.eventstorming.EventstormingFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.eventstorming uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.eventstorming, while a change to source.library.packages.eventstorming can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.eventstorming uses a module listed above it, which is the healthy direction.
28→16 source.library.packages.eventstorming uses source.generator.workdir.factories✕
- Connections
- 2 pairs of types, where a type in source.library.packages.eventstorming uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.eventstorming.EventstormingFactory→source.generator.workdir.factories.PackageContextsource.library.packages.eventstorming.EventstormingFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.eventstorming uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.eventstorming, while a change to source.library.packages.eventstorming can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.eventstorming uses a module listed above it, which is the healthy direction.
29→11 source.library.packages.fontawesome uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.library.packages.fontawesome uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.fontawesome.FontawesomeFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.fontawesome uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.fontawesome, while a change to source.library.packages.fontawesome can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.fontawesome uses a module listed above it, which is the healthy direction.
29→16 source.library.packages.fontawesome uses source.generator.workdir.factories✕
- Connections
- 2 pairs of types, where a type in source.library.packages.fontawesome uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.fontawesome.FontawesomeFactory→source.generator.workdir.factories.PackageContextsource.library.packages.fontawesome.FontawesomeFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.fontawesome uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.fontawesome, while a change to source.library.packages.fontawesome can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.fontawesome uses a module listed above it, which is the healthy direction.
30→11 source.library.packages.gcp uses source.generator.workdir.manifest✕
- Connections
- 2 pairs of types, where a type in source.library.packages.gcp uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.gcp.GcpFactory→source.generator.workdir.manifest.Itemsource.library.packages.gcp.GcpFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.gcp uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.gcp, while a change to source.library.packages.gcp can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.gcp uses a module listed above it, which is the healthy direction.
30→16 source.library.packages.gcp uses source.generator.workdir.factories✕
- Connections
- 2 pairs of types, where a type in source.library.packages.gcp uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.gcp.GcpFactory→source.generator.workdir.factories.PackageContextsource.library.packages.gcp.GcpFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.gcp uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.gcp, while a change to source.library.packages.gcp can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.gcp uses a module listed above it, which is the healthy direction.
31→11 source.library.packages.material uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.library.packages.material uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.material.MaterialFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.material uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.material, while a change to source.library.packages.material can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.material uses a module listed above it, which is the healthy direction.
31→16 source.library.packages.material uses source.generator.workdir.factories✕
- Connections
- 2 pairs of types, where a type in source.library.packages.material uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.material.MaterialFactory→source.generator.workdir.factories.PackageContextsource.library.packages.material.MaterialFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.material uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.material, while a change to source.library.packages.material can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.material uses a module listed above it, which is the healthy direction.
32→11 source.library.packages.simpleicons uses source.generator.workdir.manifest✕
- Connections
- 1 pair of types, where a type in source.library.packages.simpleicons uses a type in source.generator.workdir.manifest.
- The types involved
source.library.packages.simpleicons.SimpleiconsFactory→source.generator.workdir.manifest.Package
- Direction
- source.library.packages.simpleicons uses source.generator.workdir.manifest, so a change to source.generator.workdir.manifest can break source.library.packages.simpleicons, while a change to source.library.packages.simpleicons can't break source.generator.workdir.manifest.
- Position
- Below the diagonal: source.library.packages.simpleicons uses a module listed above it, which is the healthy direction.
32→16 source.library.packages.simpleicons uses source.generator.workdir.factories✕
- Connections
- 2 pairs of types, where a type in source.library.packages.simpleicons uses a type in source.generator.workdir.factories.
- The types involved
source.library.packages.simpleicons.SimpleiconsFactory→source.generator.workdir.factories.PackageContextsource.library.packages.simpleicons.SimpleiconsFactory→source.generator.workdir.factories.PackageFactory
- Direction
- source.library.packages.simpleicons uses source.generator.workdir.factories, so a change to source.generator.workdir.factories can break source.library.packages.simpleicons, while a change to source.library.packages.simpleicons can't break source.generator.workdir.factories.
- Position
- Below the diagonal: source.library.packages.simpleicons uses a module listed above it, which is the healthy direction.
33→9 source.generator.website.extract uses source.generator.website.config✕
- Connections
- 1 pair of types, where a type in source.generator.website.extract uses a type in source.generator.website.config.
- The types involved
source.generator.website.extract.ExtractStage→source.generator.website.config.Config
- Direction
- source.generator.website.extract uses source.generator.website.config, so a change to source.generator.website.config can break source.generator.website.extract, while a change to source.generator.website.extract can't break source.generator.website.config.
- Position
- Below the diagonal: source.generator.website.extract uses a module listed above it, which is the healthy direction.
33→14 source.generator.website.extract uses source.generator.website.sitemap✕
- Connections
- 1 pair of types, where a type in source.generator.website.extract uses a type in source.generator.website.sitemap.
- The types involved
source.generator.website.extract.ExtractStageOutput→source.generator.website.sitemap.Sitemap
- Direction
- source.generator.website.extract uses source.generator.website.sitemap, so a change to source.generator.website.sitemap can break source.generator.website.extract, while a change to source.generator.website.extract can't break source.generator.website.sitemap.
- Position
- Below the diagonal: source.generator.website.extract uses a module listed above it, which is the healthy direction.
33→15 source.generator.website.extract uses source.generator.website.stage✕
- Connections
- 1 pair of types, where a type in source.generator.website.extract uses a type in source.generator.website.stage.
- The types involved
source.generator.website.extract.ExtractStage→source.generator.website.stage.Stage
- Direction
- source.generator.website.extract uses source.generator.website.stage, so a change to source.generator.website.stage can break source.generator.website.extract, while a change to source.generator.website.extract can't break source.generator.website.stage.
- Position
- Below the diagonal: source.generator.website.extract uses a module listed above it, which is the healthy direction.
33→18 source.generator.website.extract uses source.generator.website.resource✕
- Connections
- 2 pairs of types, where a type in source.generator.website.extract uses a type in source.generator.website.resource.
- The types involved
source.generator.website.extract.ExtractStage→source.generator.website.resource.InputResourcesource.generator.website.extract.ExtractStageOutput→source.generator.website.resource.InputResource
- Direction
- source.generator.website.extract uses source.generator.website.resource, so a change to source.generator.website.resource can break source.generator.website.extract, while a change to source.generator.website.extract can't break source.generator.website.resource.
- Position
- Below the diagonal: source.generator.website.extract uses a module listed above it, which is the healthy direction.
34→9 source.generator.website.transform uses source.generator.website.config✕
- Connections
- 1 pair of types, where a type in source.generator.website.transform uses a type in source.generator.website.config.
- The types involved
source.generator.website.transform.TransformStage→source.generator.website.config.Config
- Direction
- source.generator.website.transform uses source.generator.website.config, so a change to source.generator.website.config can break source.generator.website.transform, while a change to source.generator.website.transform can't break source.generator.website.config.
- Position
- Below the diagonal: source.generator.website.transform uses a module listed above it, which is the healthy direction.
34→14 source.generator.website.transform uses source.generator.website.sitemap✕
- Connections
- 1 pair of types, where a type in source.generator.website.transform uses a type in source.generator.website.sitemap.
- The types involved
source.generator.website.transform.TransformStageInput→source.generator.website.sitemap.Sitemap
- Direction
- source.generator.website.transform uses source.generator.website.sitemap, so a change to source.generator.website.sitemap can break source.generator.website.transform, while a change to source.generator.website.transform can't break source.generator.website.sitemap.
- Position
- Below the diagonal: source.generator.website.transform uses a module listed above it, which is the healthy direction.
34→15 source.generator.website.transform uses source.generator.website.stage✕
- Connections
- 1 pair of types, where a type in source.generator.website.transform uses a type in source.generator.website.stage.
- The types involved
source.generator.website.transform.TransformStage→source.generator.website.stage.Stage
- Direction
- source.generator.website.transform uses source.generator.website.stage, so a change to source.generator.website.stage can break source.generator.website.transform, while a change to source.generator.website.transform can't break source.generator.website.stage.
- Position
- Below the diagonal: source.generator.website.transform uses a module listed above it, which is the healthy direction.
34→18 source.generator.website.transform uses source.generator.website.resource✕
- Connections
- 1 pair of types, where a type in source.generator.website.transform uses a type in source.generator.website.resource.
- The types involved
source.generator.website.transform.TransformStageInput→source.generator.website.resource.InputResource
- Direction
- source.generator.website.transform uses source.generator.website.resource, so a change to source.generator.website.resource can break source.generator.website.transform, while a change to source.generator.website.transform can't break source.generator.website.resource.
- Position
- Below the diagonal: source.generator.website.transform uses a module listed above it, which is the healthy direction.
34→33 source.generator.website.transform uses source.generator.website.extract✕
- Connections
- 1 pair of types, where a type in source.generator.website.transform uses a type in source.generator.website.extract.
- The types involved
source.generator.website.transform.TransformStage→source.generator.website.extract.ExtractStageOutput
- Direction
- source.generator.website.transform uses source.generator.website.extract, so a change to source.generator.website.extract can break source.generator.website.transform, while a change to source.generator.website.transform can't break source.generator.website.extract.
- Position
- Below the diagonal: source.generator.website.transform uses a module listed above it, which is the healthy direction.
35→9 source.generator.website.load uses source.generator.website.config✕
- Connections
- 1 pair of types, where a type in source.generator.website.load uses a type in source.generator.website.config.
- The types involved
source.generator.website.load.LoadStage→source.generator.website.config.Config
- Direction
- source.generator.website.load uses source.generator.website.config, so a change to source.generator.website.config can break source.generator.website.load, while a change to source.generator.website.load can't break source.generator.website.config.
- Position
- Below the diagonal: source.generator.website.load uses a module listed above it, which is the healthy direction.
35→15 source.generator.website.load uses source.generator.website.stage✕
- Connections
- 1 pair of types, where a type in source.generator.website.load uses a type in source.generator.website.stage.
- The types involved
source.generator.website.load.LoadStage→source.generator.website.stage.Stage
- Direction
- source.generator.website.load uses source.generator.website.stage, so a change to source.generator.website.stage can break source.generator.website.load, while a change to source.generator.website.load can't break source.generator.website.stage.
- Position
- Below the diagonal: source.generator.website.load uses a module listed above it, which is the healthy direction.
35→34 source.generator.website.load uses source.generator.website.transform✕
- Connections
- 1 pair of types, where a type in source.generator.website.load uses a type in source.generator.website.transform.
- The types involved
source.generator.website.load.LoadStage→source.generator.website.transform.TransformStageOutput
- Direction
- source.generator.website.load uses source.generator.website.transform, so a change to source.generator.website.transform can break source.generator.website.load, while a change to source.generator.website.load can't break source.generator.website.transform.
- Position
- Below the diagonal: source.generator.website.load 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 10 | High / Critical |
| A02:2025 — Security Misconfiguration | 1 | Medium |
Roadmap
Top priorities: Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; 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 `?`).
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract. | +4.4 pts | Medium | Code Duplication |
| Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce. | +3.8 pts | Medium | Observability |
| 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 `?`). | +3.2 pts | Medium | Nullable reference types |
| TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants. | +3.2 pts | Medium | Async & latency hygiene |
| Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). | +1.6 pts | Low | Dependency Hygiene |
| Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up. | +2.2 pts | Medium | Cancellation propagation |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. | +0.9 pts | Low | ADR Quality |
| Add tests that import the unreached modules (directly or through their public entry). | +1.7 pts | Medium | Test Coverage |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 6.3 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| docs/wav/wav-003-workdir-generation-hardening/workflows/001-wave.js | 7.2 | Mixed | Cyclomatic Complexity: 001-wave.runViaWorkflows (cyclomatic 36) |
| docs/wav/wav-003-workdir-generation-hardening/workflows/002-wave.js | 7.2 | Mixed | Cyclomatic Complexity: 002-wave.runViaWorkflows (cyclomatic 36) |
| docs/wav/wav-003-workdir-generation-hardening/workflows/003-wave.js | 7.2 | Mixed | Cyclomatic Complexity: 003-wave.runViaWorkflows (cyclomatic 36) |
| package.json | 7.3 | Mixed | Dependency Hygiene: Deprecated: @types/extract-zip |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| REDACTED | 7.9 | Mixed | Supply-chain Provenance & Signing: REDACTED |
| test/archive.spec.js | 9.0 | Near-clean | Test Quality: No direct assertions: should write the body of a 2xx response |
| test/aws-families.spec.js | 9.0 | Near-clean | Test Quality: No direct assertions: should list the families without a row, sorted and without duplicate |
| test/workdir-validation.spec.js | 9.0 | Near-clean | Test Quality: No direct assertions: should pass a valid package |
| test/gdiag.spec.js | 9.1 | Near-clean | Test Quality: No direct assertions: should not render missing diagrams |
| REDACTED | 9.3 | Near-clean | Vulnerability-disclosure Policy: REDACTED |
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 62 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 62 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, 119 of 129 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
- 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. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- 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 an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D26 Project Cohesion — 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. `(repository root)` (7162 LoC, 89 module-visible types across 22 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: 11 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- 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. 42 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- 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, Rust, Go, Swift, Erlang, F# and Visual Basic 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.
- 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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- 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.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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 (go.mod, 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- 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 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was 001-wave.runViaWorkflows at 36.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with 001-wave.runViaWorkflows (cyclomatic 36), 002-wave.runViaWorkflows (cyclomatic 36), 003-wave.runViaWorkflows (cyclomatic 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 6 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
6 method(s) exceeded the cognitive complexity threshold of 15; the worst was 001-wave.runViaWorkflows at 64.
What to do
- Bring the 6 bodies over 15 down to 15 or less in Cognitive Complexity — start with 001-wave.runViaWorkflows (cognitive 64), 002-wave.runViaWorkflows (cognitive 64), 003-wave.runViaWorkflows (cognitive 64). — 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 Cognitive Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 9 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 25 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 29 tests (1 harness-style project(s) excluded from the assertion penalty).
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (mocha via `npm ci --ignore-scripts` in the repository root (33 tests)): measured (0 flaky).
D12 · Dependency Hygiene
1 outdated direct production npm dependency(ies) of 3 graded, 0 pinning defect(s), across 1 package.json (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry 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, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with package.json (2). — One of this dimension's main actionable groups (2 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 21 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 21 package(s) this repository's committed lockfile installs for a consumer — its 3 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 30 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 2956 LoC (0.0/KLoC) → score 10.0. 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.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 67 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
0 of 157 judged comments only repeat the code they sit on (0.0 %). 3 comment(s) in another language or script were not judged.
D27 · Navigability
26 % of calls cross a namespace and 6 % go through an interface, but 85 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
10 finding(s): 1 critical, 4 high, 4 medium, 1 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- 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).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. 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.
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
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 1 platform declaration(s) and 3 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
AC2 · Forms & labels
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — source/generator/website/templates.ts:101
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
AC5 · ARIA correctness
AC6 · Visual & motion safety
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `setLatestRun` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — bin/gdiag.js:92
- `cleanLatestRun` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — bin/gdiag.js:97
- `cleanDirectory` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — bin/gdiag.js:104
- `renderPuml` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — bin/gdiag.js:170
What to do
- Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
M1 · Documentation (README)
What to do
- 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
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
What to do
- Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with REDACTED/dependency-review-action`. — package.json:55
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
- `Fe.rmSync` in `execute` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/generator/website/load.ts:26
- `Fe.mkdirSync` in `execute` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/generator/website/load.ts:30
- `F.mkdirSync` in `download` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/generator/workdir/archive.ts:27
- `F.existsSync` in `download` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — source/generator/workdir/archive.ts:28, source/generator/workdir/archive.ts:32
- `F.rmSync` in `download` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — source/generator/workdir/archive.ts:30, source/generator/workdir/archive.ts:57
- `F.statSync` in `download` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/generator/workdir/archive.ts:49
- `F.renameSync` in `download` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/generator/workdir/archive.ts:55
- `F.existsSync` in `extractArchive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/generator/workdir/archive.ts:68
- `F.rmSync` in `extractArchive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — source/generator/workdir/archive.ts:72, source/generator/workdir/archive.ts:78
- `F.mkdirSync` in `extractArchive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/generator/workdir/archive.ts:73
- `F.renameSync` in `extractArchive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/generator/workdir/archive.ts:76
- `F.readFileSync` in `renderBootstrap` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/library/packages/domainstorytelling/index.ts:123
- `F.readFileSync` in `create` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — source/library/packages/eventstorming/index.ts:53
What to do
- TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety
R10 · Code Duplication
- 17 duplicated blocks under source/library/packages/ have copies in at least two of the sibling directories aws, azure, c4k8s, c4model, domainstorytelling, eip (+4 more sibling(s) not listed) — 14 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 17 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 17 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 17 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — source/library/packages/material/index.ts:13
- source/library/packages/material/index.ts:13 · source/library/packages/simpleicons/index.ts:13 — the two spans are one implementation copied and then locally edited — 333 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — source/library/packages/material/index.ts:13
- source/library/packages/fontawesome/index.ts:6 · source/library/packages/material/index.ts:4 — these 2 files are line-for-line copies of one another — 60 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — source/library/packages/fontawesome/index.ts:6
- source/library/packages/domainstorytelling/index.ts:59 · source/library/packages/material/index.ts:38 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/domainstorytelling/index.ts:59
- scripts/resolve-aws-icons.mjs:7 · scripts/resolve-azure-icons.mjs:7 — the two spans are one implementation copied and then locally edited — 240 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/resolve-aws-icons.mjs:7
- source/library/packages/azure/index.ts:76 · source/library/packages/gcp/index.ts:85 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/azure/index.ts:76
- source/library/packages/azure/index.ts:114 · source/library/packages/gcp/index.ts:128 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/azure/index.ts:114
- source/library/packages/eip/index.ts:19 · source/library/packages/gcp/index.ts:50 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/eip/index.ts:19
- source/library/packages/c4k8s/index.ts:12 · source/library/packages/c4k8s/index.ts:37 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/c4k8s/index.ts:12
- source/library/packages/c4k8s/index.ts:29 · source/library/packages/c4model/index.ts:37 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/c4k8s/index.ts:29
- source/library/packages/gcp/index.ts:38 · source/library/packages/material/index.ts:26 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — source/library/packages/gcp/index.ts:38
- source/library/packages/aws/index.ts:107 · source/library/packages/azure/index.ts:59 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/aws/index.ts:107
- source/library/packages/c4k8s/index.ts:67 · source/library/packages/c4model/index.ts:74 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/c4k8s/index.ts:67
- source/library/packages/c4k8s/index.ts:86 · source/library/packages/c4model/index.ts:102 · source/library/packages/eip/index.ts:149 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/c4k8s/index.ts:86
- source/library/packages/azure/index.ts:35 · source/library/packages/fontawesome/index.ts:27 · source/library/packages/material/index.ts:34 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/azure/index.ts:35
- source/library/packages/domainstorytelling/index.ts:142 · source/library/packages/fontawesome/index.ts:89 · source/library/packages/material/index.ts:94 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/domainstorytelling/index.ts:142
- source/library/packages/aws/index.ts:184 · source/library/packages/aws/index.ts:192 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/aws/index.ts:184
- source/library/packages/eip/index.ts:102 · source/library/packages/fontawesome/index.ts:84 · source/library/packages/material/index.ts:89 · source/library/packages/simpleicons/index.ts:74 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/eip/index.ts:102
- source/library/packages/c4model/index.ts:21 · source/library/packages/c4model/index.ts:45 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — source/library/packages/c4model/index.ts:21
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- validatePackage has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — source/generator/workdir/validation.ts:13
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×13) — source/library/packages/domainstorytelling/index.ts:1, source/library/packages/eip/index.ts:1, source/library/packages/gcp/index.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — eslint.config.mjs:2
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3) — package.json:74, package.json:77, package.json:78
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
X1 · Async correctness
X12 · Unreachable branch
X16 · Unfloored truncation loop
X2 · Cancellation propagation
- Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `downloadPlantUML` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — bin/gdiag.js:151
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
- ~2.5 `!` null assertions per 1k TypeScript source lines — 8 assertion(s) across the 3237 source line(s) of the 31 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: source/generator/workdir/factories.ts (6), source/library/packages/eip/index.ts (1), source/library/packages/eventstorming/index.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 43.8 | Weak — gated by R10, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 99.6 | Exemplary | Strongest area. |
| Maturity | 77.0 | Strong | Solid. |
| Readiness | 46.1 | Weak — gated by R4, P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 85.0 | Strong | Solid. |
| Accessibility | 82.3 | Strong | Solid. |
| Performance | 60.0 | Adequate | Acceptable, with room to improve. |
Unscored — 1 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 5 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript 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; this repository's TypeScript 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 — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D16 Bus Factor — bus factor 1 — one contributor carries 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 — N/A — too few peers to establish a naming convention (934 declarations, no unit with a dominant convention).
- 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"]`.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
- 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.
- D4 Code Duplication — This repository's production source (.js, .mjs, .ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- 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 npm 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.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the repository root runs mocha but declares no coverage provider, so the suite can run and still produce no lcov — add `c8` (or `nyc`) as a devDependency so the suite can be wrapped for coverage. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the 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
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- 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.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- S1 Web-Security Posture — Not assessed: 42 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is 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.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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
- 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.
- 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 applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X28 Index access outside its own emptiness guard — 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 — 7 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <input> without a programmatic label source/generator/website/templates.ts:101
- REDACTED
- Unlisted import 'globals' eslint.config.mjs:2
Serious — 83 finding(s)
- Sync-over-async blocking source/generator/website/load.ts:26
- Sync-over-async blocking source/generator/website/load.ts:30
- Sync-over-async blocking source/generator/workdir/archive.ts:27
- Sync-over-async blocking source/generator/workdir/archive.ts:28
- Sync-over-async blocking source/generator/workdir/archive.ts:30
- Sync-over-async blocking source/generator/workdir/archive.ts:32
- Sync-over-async blocking source/generator/workdir/archive.ts:49
- Sync-over-async blocking source/generator/workdir/archive.ts:55
- Sync-over-async blocking source/generator/workdir/archive.ts:57
- Sync-over-async blocking source/generator/workdir/archive.ts:68
- Sync-over-async blocking source/generator/workdir/archive.ts:72
- Sync-over-async blocking source/generator/workdir/archive.ts:73
- Sync-over-async blocking source/generator/workdir/archive.ts:76
- Sync-over-async blocking source/generator/workdir/archive.ts:78
- Sync-over-async blocking source/library/packages/domainstorytelling/index.ts:123
- Sync-over-async blocking source/library/packages/eventstorming/index.ts:53
- No test reaches this file source/library/packages/domainstorytelling/index.ts:1
- No test reaches this file source/library/packages/eip/index.ts:1
- No test reaches this file source/library/packages/gcp/index.ts:1
- No test reaches this file source/library/packages/azure/index.ts:1
- No test reaches this file source/library/packages/eventstorming/index.ts:1
- No test reaches this file source/library/packages/material/index.ts:1
- No test reaches this file source/library/packages/fontawesome/index.ts:1
- No test reaches this file source/library/packages/c4model/index.ts:1
- No test reaches this file source/library/packages/simpleicons/index.ts:1
- No test reaches this file source/library/packages/c4k8s/index.ts:1
- No test reaches this file source/library/index.ts:1
- No test reaches this file source/generator/workdir/index.ts:1
- No test reaches this file source/library/packages/c4nord/index.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Fake-async — async method never awaits bin/gdiag.js:92
- Fake-async — async method never awaits bin/gdiag.js:97
- Fake-async — async method never awaits bin/gdiag.js:104
- Fake-async — async method never awaits bin/gdiag.js:170
- REDACTED
- REDACTED
- REDACTED
- Deprecated: @types/extract-zip package.json:58
- Deprecated: @types/yaml package.json:65
- Duplicated block (13 lines × 2 locations) source/library/packages/c4k8s/index.ts:29
- Duplicated block (13 lines × 2 locations) source/library/packages/gcp/index.ts:38
- Duplicated block (10 lines × 3 locations) source/library/packages/azure/index.ts:35
- Duplicated block (10 lines × 3 locations) source/library/packages/domainstorytelling/index.ts:142
- 001-wave.runViaWorkflows (cyclomatic 36) docs/wav/wav-003-workdir-generation-hardening/workflows/001-wave.js:358
- 002-wave.runViaWorkflows (cyclomatic 36) docs/wav/wav-003-workdir-generation-hardening/workflows/002-wave.js:358
- 003-wave.runViaWorkflows (cyclomatic 36) docs/wav/wav-003-workdir-generation-hardening/workflows/003-wave.js:358
- 001-wave.planByCopy (cyclomatic 27) docs/wav/wav-003-workdir-generation-hardening/workflows/001-wave.js:341
- 002-wave.planByCopy (cyclomatic 27) docs/wav/wav-003-workdir-generation-hardening/workflows/002-wave.js:341
- 003-wave.planByCopy (cyclomatic 27) docs/wav/wav-003-workdir-generation-hardening/workflows/003-wave.js:341
- bus factor 1 — one contributor carries this repository
- 001-wave.runViaWorkflows (cognitive 64) docs/wav/wav-003-workdir-generation-hardening/workflows/001-wave.js:358
- 002-wave.runViaWorkflows (cognitive 64) docs/wav/wav-003-workdir-generation-hardening/workflows/002-wave.js:358
- 003-wave.runViaWorkflows (cognitive 64) docs/wav/wav-003-workdir-generation-hardening/workflows/003-wave.js:358
- 001-wave.planByCopy (cognitive 29) docs/wav/wav-003-workdir-generation-hardening/workflows/001-wave.js:341
- 002-wave.planByCopy (cognitive 29) docs/wav/wav-003-workdir-generation-hardening/workflows/002-wave.js:341
- 003-wave.planByCopy (cognitive 29) docs/wav/wav-003-workdir-generation-hardening/workflows/003-wave.js:341
- REDACTED
- REDACTED
- Coverage not measured — JavaScript/TypeScript suite
- No structured logging
- Duplication concentrated across 10 sibling directories (17 clone groups) source/library/packages/material/index.ts:13
- Duplicated block with local edits (67 matched lines × 2 locations) source/library/packages/material/index.ts:13
- Wholesale file copy (60 identical lines × 2 files) source/library/packages/fontawesome/index.ts:6
- Duplicated block (45 lines × 2 locations) source/library/packages/domainstorytelling/index.ts:59
- Duplicated block with local edits (42 matched lines × 2 locations) scripts/resolve-aws-icons.mjs:7
- Duplicated block (30 lines × 2 locations) source/library/packages/azure/index.ts:76
- Duplicated block (24 lines × 2 locations) source/library/packages/azure/index.ts:114
- Duplicated block (18 lines × 2 locations) source/library/packages/eip/index.ts:19
- Duplicated block (17 lines × 2 locations) source/library/packages/c4k8s/index.ts:12
- Duplicated block (12 lines × 2 locations) source/library/packages/aws/index.ts:107
- Duplicated block (11 lines × 2 locations) source/library/packages/c4k8s/index.ts:67
- Duplicated block (11 lines × 3 locations) source/library/packages/c4k8s/index.ts:86
- Duplicated block (8 lines × 2 locations) source/library/packages/aws/index.ts:184
- Duplicated block (8 lines × 4 locations) source/library/packages/eip/index.ts:102
- Duplicated block (6 lines × 2 locations) source/library/packages/c4model/index.ts:21
- Complex function validatePackage (cyclomatic 16, cognitive 20) source/generator/workdir/validation.ts:13
- Unused dependency 'html-minifier-terser' package.json:74
- Unused dependency 'marked-gfm-heading-id' package.json:77
- Unused dependency 'marked-mangle' package.json:78
- Async function without AbortSignal: downloadPlantUML bin/gdiag.js:151
Minor — 38 finding(s)
- No direct assertions: should write the body of a 2xx response test/archive.spec.js:101
- No direct assertions: should reject ${name} and leave no file behind test/archive.spec.js:123
- No direct assertions: should not fetch again when the archive is already cached test/archive.spec.js:131
- No direct assertions: should discard a cached file that is not a zip and fetch it again test/archive.spec.js:140
- No direct assertions: should leave no file when a cached non-zip file cannot be fetched again test/archive.spec.js:150
- No direct assertions: should extract a complete archive test/archive.spec.js:172
- No direct assertions: should leave no directory when the extraction fails, then extract a good archive test/archive.spec.js:180
- No direct assertions: should clear a stale part directory left by a killed run test/archive.spec.js:190
- No direct assertions: should not extract again when the directory is complete test/archive.spec.js:200
- No direct assertions: should exit non-zero when the generation fails test/archive.spec.js:210
- No direct assertions: should list the families without a row, sorted and without duplicate test/aws-families.spec.js:26
- No direct assertions: should ignore the items without family test/aws-families.spec.js:40
- No direct assertions: should return nothing when every family has a row test/aws-families.spec.js:45
- No direct assertions: should throw naming the package, the families and families.csv test/aws-families.spec.js:58
- No direct assertions: should pass when every family has a row test/aws-families.spec.js:72
- No direct assertions: should have no duplicate name and be sorted by name test/aws-families.spec.js:80
- No direct assertions: should only use colors defined by bootstrap.tera test/aws-families.spec.js:89
- No direct assertions: should not render missing diagrams test/gdiag.spec.js:36
- No direct assertions: should render updated sources test/gdiag.spec.js:51
- No direct assertions: should clean before render test/gdiag.spec.js:73
- No direct assertions: should pass a valid package test/workdir-validation.spec.js:29
- No direct assertions: should throw naming the package and the missing template test/workdir-validation.spec.js:45
- No direct assertions: should throw naming the package and the dangling reference test/workdir-validation.spec.js:61
- No direct assertions: should report both faults in one message with two lines test/workdir-validation.spec.js:85
- No direct assertions: should pass a reference to an item of another module of the package test/workdir-validation.spec.js:108
- Deprecated: node-domexception REDACTED:4143
- Deprecated: q REDACTED:4518
- Deprecated: stringify-package REDACTED:5146
- No ADRs found package.json:21
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No dependency-update automation package.json:55
- Not all async functions that make a request accept an AbortSignal
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) override strict null checking
Minor — 1 finding(s)
- Outdated (npm): glob
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 --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-5297ac364d024214b264be096d73fc11/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=359" --report-format json --report-path /tmp/watchdog-gitleaks-5297ac364d024214b264be096d73fc11/history-1.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history-1.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-5297ac364d024214b264be096d73fc11/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 . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 10 | 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 |