Executive summary
verbumby/verbum falls short of our standard for production, held back most by its Production Readiness lens, the way the code is tested, built, released and run. It scores 49.4 out of 100 and is rated Weak, and 16 of its 24 critical findings are security problems in the build pipeline and in the packages it uses.
Production Readiness, at 40.2, is the weakest lens and counts most in the score. The best first step is adding tests for untested code, worth about 6.3 points. Adding tests for the code no test reaches would lift Production Readiness itself, worth about 4.6 points. Raising Production Readiness to 70 would lift the score to about 55.7.
Thirteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three known security holes in the packages the code depends on can be used by attackers, and six controls can't be used without a mouse. Pinning each tool to an exact version, updating the vulnerable packages and making the controls work with a keyboard would close these risks. The page or frame without a title needs a descriptive title.
The product code is 7,290 lines, about €8,900 to rebuild.
If Production Readiness rose from 40.2 to 70, the lowest score rated Strong, the score would rise from 49.4 to about 55.7.
Rebuild cost: about €8,900 · Estimate
| Cost to rebuild | €2,900 to €15,000, for 49 to 156 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 49. 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,290 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 frontend.browser | 2 frontend.common.abbrevs | 3 frontend.common.theme | 4 frontend.common.urlsearch | 5 frontend.icons | 6 frontend.pages.dict.abbr | 7 frontend.pages.dict.dict | 8 frontend.pages.dict.letterfilter | 9 frontend.pages.dict.preface | 10 frontend.pages.support | 11 frontend.theme | 12 github.com/verbumby/verbum/backend/chttp | 13 github.com/verbumby/verbum/backend/config | 14 github.com/verbumby/verbum/backend/ctl | 15 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser | 16 github.com/verbumby/verbum/backend/dictionary | 17 github.com/verbumby/verbum/backend/htmlui | 18 github.com/verbumby/verbum/backend/storage | 19 github.com/verbumby/verbum/backend/textutil | 20 github.com/verbumby/verbum/backend/verbum | 21 github.com/verbumby/verbum/frontend | 22 frontend | 23 frontend.common | 24 frontend.pages.article | 25 frontend.pages.dict | 26 frontend.pages.index | 27 frontend.verbum.client | 28 github.com/verbumby/verbum/backend/article | 29 github.com/verbumby/verbum/backend/ctl/dictimport | 30 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/dsl | 31 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/grammardb | 32 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html | 33 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/stardict | 34 github.com/verbumby/verbum/backend/handlers | 35 frontend.verbum.browser | 36 frontend.verbum.server |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 frontend.browser | ||||||||||||||||||||||||||||||||||||
| 2 frontend.common.abbrevs | ||||||||||||||||||||||||||||||||||||
| 3 frontend.common.theme | ||||||||||||||||||||||||||||||||||||
| 4 frontend.common.urlsearch | ||||||||||||||||||||||||||||||||||||
| 5 frontend.icons | ||||||||||||||||||||||||||||||||||||
| 6 frontend.pages.dict.abbr | ||||||||||||||||||||||||||||||||||||
| 7 frontend.pages.dict.dict | ||||||||||||||||||||||||||||||||||||
| 8 frontend.pages.dict.letterfilter | ||||||||||||||||||||||||||||||||||||
| 9 frontend.pages.dict.preface | ||||||||||||||||||||||||||||||||||||
| 10 frontend.pages.support | ||||||||||||||||||||||||||||||||||||
| 11 frontend.theme | ||||||||||||||||||||||||||||||||||||
| 12 github.com/verbumby/verbum/backend/chttp | ||||||||||||||||||||||||||||||||||||
| 13 github.com/verbumby/verbum/backend/config | ||||||||||||||||||||||||||||||||||||
| 14 github.com/verbumby/verbum/backend/ctl | ||||||||||||||||||||||||||||||||||||
| 15 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser | ||||||||||||||||||||||||||||||||||||
| 16 github.com/verbumby/verbum/backend/dictionary | ||||||||||||||||||||||||||||||||||||
| 17 github.com/verbumby/verbum/backend/htmlui | ||||||||||||||||||||||||||||||||||||
| 18 github.com/verbumby/verbum/backend/storage | ||||||||||||||||||||||||||||||||||||
| 19 github.com/verbumby/verbum/backend/textutil | ||||||||||||||||||||||||||||||||||||
| 20 github.com/verbumby/verbum/backend/verbum | ||||||||||||||||||||||||||||||||||||
| 21 github.com/verbumby/verbum/frontend | ||||||||||||||||||||||||||||||||||||
| 22 frontend | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 23 frontend.common | 1 | |||||||||||||||||||||||||||||||||||
| 24 frontend.pages.article | 1 | |||||||||||||||||||||||||||||||||||
| 25 frontend.pages.dict | 4 | |||||||||||||||||||||||||||||||||||
| 26 frontend.pages.index | 1 | |||||||||||||||||||||||||||||||||||
| 27 frontend.verbum.client | 1 | |||||||||||||||||||||||||||||||||||
| 28 github.com/verbumby/verbum/backend/article | 2 | |||||||||||||||||||||||||||||||||||
| 29 github.com/verbumby/verbum/backend/ctl/dictimport | 1 | 3 | ||||||||||||||||||||||||||||||||||
| 30 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/dsl | 1 | |||||||||||||||||||||||||||||||||||
| 31 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/grammardb | 1 | |||||||||||||||||||||||||||||||||||
| 32 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 33 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/stardict | 1 | |||||||||||||||||||||||||||||||||||
| 34 github.com/verbumby/verbum/backend/handlers | 1 | |||||||||||||||||||||||||||||||||||
| 35 frontend.verbum.browser | 1 | |||||||||||||||||||||||||||||||||||
| 36 frontend.verbum.server | 1 |
22→3 frontend uses frontend.common.theme✕
- Connections
- 1 pair of types, where a type in frontend uses a type in frontend.common.theme.
- The types involved
frontend.theme→frontend.common.theme.ThemeID
- Direction
- frontend uses frontend.common.theme, so a change to frontend.common.theme can break frontend, while a change to frontend can't break frontend.common.theme.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
22→6 frontend uses frontend.pages.dict.abbr✕
- Connections
- 1 pair of types, where a type in frontend uses a type in frontend.pages.dict.abbr.
- The types involved
frontend.store→frontend.pages.dict.abbr.AbbrState
- Direction
- frontend uses frontend.pages.dict.abbr, so a change to frontend.pages.dict.abbr can break frontend, while a change to frontend can't break frontend.pages.dict.abbr.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
22→8 frontend uses frontend.pages.dict.letterfilter✕
- Connections
- 1 pair of types, where a type in frontend uses a type in frontend.pages.dict.letterfilter.
- The types involved
frontend.store→frontend.pages.dict.letterfilter.LetterFilterState
- Direction
- frontend uses frontend.pages.dict.letterfilter, so a change to frontend.pages.dict.letterfilter can break frontend, while a change to frontend can't break frontend.pages.dict.letterfilter.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
22→9 frontend uses frontend.pages.dict.preface✕
- Connections
- 1 pair of types, where a type in frontend uses a type in frontend.pages.dict.preface.
- The types involved
frontend.store→frontend.pages.dict.preface.PrefaceState
- Direction
- frontend uses frontend.pages.dict.preface, so a change to frontend.pages.dict.preface can break frontend, while a change to frontend can't break frontend.pages.dict.preface.
- Position
- Below the diagonal: frontend uses a module listed above it, which is the healthy direction.
23→4 frontend.common uses frontend.common.urlsearch✕
- Connections
- 1 pair of types, where a type in frontend.common uses a type in frontend.common.urlsearch.
- The types involved
frontend.common.hooks→frontend.common.urlsearch.URLSearch
- Direction
- frontend.common uses frontend.common.urlsearch, so a change to frontend.common.urlsearch can break frontend.common, while a change to frontend.common can't break frontend.common.urlsearch.
- Position
- Below the diagonal: frontend.common uses a module listed above it, which is the healthy direction.
24→4 frontend.pages.article uses frontend.common.urlsearch✕
- Connections
- 1 pair of types, where a type in frontend.pages.article uses a type in frontend.common.urlsearch.
- The types involved
frontend.pages.article.article→frontend.common.urlsearch.URLSearch
- Direction
- frontend.pages.article uses frontend.common.urlsearch, so a change to frontend.common.urlsearch can break frontend.pages.article, while a change to frontend.pages.article can't break frontend.common.urlsearch.
- Position
- Below the diagonal: frontend.pages.article uses a module listed above it, which is the healthy direction.
25→4 frontend.pages.dict uses frontend.common.urlsearch✕
- Connections
- 4 pairs of types, where a type in frontend.pages.dict uses a type in frontend.common.urlsearch.
- The types involved
frontend.pages.dict.abbr→frontend.common.urlsearch.URLSearchfrontend.pages.dict.dict→frontend.common.urlsearch.URLSearchfrontend.pages.dict.letterfilter→frontend.common.urlsearch.URLSearchfrontend.pages.dict.preface→frontend.common.urlsearch.URLSearch
- Direction
- frontend.pages.dict uses frontend.common.urlsearch, so a change to frontend.common.urlsearch can break frontend.pages.dict, while a change to frontend.pages.dict can't break frontend.common.urlsearch.
- Position
- Below the diagonal: frontend.pages.dict uses a module listed above it, which is the healthy direction.
26→4 frontend.pages.index uses frontend.common.urlsearch✕
- Connections
- 1 pair of types, where a type in frontend.pages.index uses a type in frontend.common.urlsearch.
- The types involved
frontend.pages.index.search→frontend.common.urlsearch.URLSearch
- Direction
- frontend.pages.index uses frontend.common.urlsearch, so a change to frontend.common.urlsearch can break frontend.pages.index, while a change to frontend.pages.index can't break frontend.common.urlsearch.
- Position
- Below the diagonal: frontend.pages.index uses a module listed above it, which is the healthy direction.
27→2 frontend.verbum.client uses frontend.common.abbrevs✕
- Connections
- 1 pair of types, where a type in frontend.verbum.client uses a type in frontend.common.abbrevs.
- The types involved
frontend.verbum.client.VerbumAPIClientImpl→frontend.common.abbrevs.Abbrevs
- Direction
- frontend.verbum.client uses frontend.common.abbrevs, so a change to frontend.common.abbrevs can break frontend.verbum.client, while a change to frontend.verbum.client can't break frontend.common.abbrevs.
- Position
- Below the diagonal: frontend.verbum.client uses a module listed above it, which is the healthy direction.
28→16 github.com/verbumby/verbum/backend/article uses github.com/verbumby/verbum/backend/dictionary✕
- Connections
- 2 pairs of types, where a type in github.com/verbumby/verbum/backend/article uses a type in github.com/verbumby/verbum/backend/dictionary.
- The types involved
github.com/verbumby/verbum/backend/article.Article→github.com/verbumby/verbum/backend/dictionary.Dictionarygithub.com/verbumby/verbum/backend/article.article→github.com/verbumby/verbum/backend/dictionary.Dictionary
- Direction
- github.com/verbumby/verbum/backend/article uses github.com/verbumby/verbum/backend/dictionary, so a change to github.com/verbumby/verbum/backend/dictionary can break github.com/verbumby/verbum/backend/article, while a change to github.com/verbumby/verbum/backend/article can't break github.com/verbumby/verbum/backend/dictionary.
- Position
- Below the diagonal: github.com/verbumby/verbum/backend/article uses a module listed above it, which is the healthy direction.
29→15 github.com/verbumby/verbum/backend/ctl/dictimport uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser✕
- Connections
- 1 pair of types, where a type in github.com/verbumby/verbum/backend/ctl/dictimport uses a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- The types involved
github.com/verbumby/verbum/backend/ctl/dictimport.commandController→github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.Article
- Direction
- github.com/verbumby/verbum/backend/ctl/dictimport uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser, so a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser can break github.com/verbumby/verbum/backend/ctl/dictimport, while a change to github.com/verbumby/verbum/backend/ctl/dictimport can't break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- Position
- Below the diagonal: github.com/verbumby/verbum/backend/ctl/dictimport uses a module listed above it, which is the healthy direction.
29→16 github.com/verbumby/verbum/backend/ctl/dictimport uses github.com/verbumby/verbum/backend/dictionary✕
- Connections
- 3 pairs of types, where a type in github.com/verbumby/verbum/backend/ctl/dictimport uses a type in github.com/verbumby/verbum/backend/dictionary.
- The types involved
github.com/verbumby/verbum/backend/ctl/dictimport.IDGen→github.com/verbumby/verbum/backend/dictionary.Dictionarygithub.com/verbumby/verbum/backend/ctl/dictimport.commandController→github.com/verbumby/verbum/backend/dictionary.Dictionarygithub.com/verbumby/verbum/backend/ctl/dictimport.dictimport→github.com/verbumby/verbum/backend/dictionary.Dictionary
- Direction
- github.com/verbumby/verbum/backend/ctl/dictimport uses github.com/verbumby/verbum/backend/dictionary, so a change to github.com/verbumby/verbum/backend/dictionary can break github.com/verbumby/verbum/backend/ctl/dictimport, while a change to github.com/verbumby/verbum/backend/ctl/dictimport can't break github.com/verbumby/verbum/backend/dictionary.
- Position
- Below the diagonal: github.com/verbumby/verbum/backend/ctl/dictimport uses a module listed above it, which is the healthy direction.
30→15 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/dsl uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser✕
- Connections
- 1 pair of types, where a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/dsl uses a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- The types involved
github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/dsl.dsl→github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.Article
- Direction
- github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/dsl uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser, so a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser can break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/dsl, while a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/dsl can't break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- Position
- Below the diagonal: github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/dsl uses a module listed above it, which is the healthy direction.
31→15 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/grammardb uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser✕
- Connections
- 1 pair of types, where a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/grammardb uses a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- The types involved
github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/grammardb.grammardb→github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.Article
- Direction
- github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/grammardb uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser, so a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser can break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/grammardb, while a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/grammardb can't break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- Position
- Below the diagonal: github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/grammardb uses a module listed above it, which is the healthy direction.
32→15 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser✕
- Connections
- 1 pair of types, where a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html uses a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- The types involved
github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html.html→github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.Article
- Direction
- github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser, so a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser can break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html, while a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html can't break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- Position
- Below the diagonal: github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html uses a module listed above it, which is the healthy direction.
32→16 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html uses github.com/verbumby/verbum/backend/dictionary✕
- Connections
- 1 pair of types, where a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html uses a type in github.com/verbumby/verbum/backend/dictionary.
- The types involved
github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html.html→github.com/verbumby/verbum/backend/dictionary.IndexSettings
- Direction
- github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html uses github.com/verbumby/verbum/backend/dictionary, so a change to github.com/verbumby/verbum/backend/dictionary can break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html, while a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html can't break github.com/verbumby/verbum/backend/dictionary.
- Position
- Below the diagonal: github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/html uses a module listed above it, which is the healthy direction.
33→15 github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/stardict uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser✕
- Connections
- 1 pair of types, where a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/stardict uses a type in github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- The types involved
github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/stardict.stardict→github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.Article
- Direction
- github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/stardict uses github.com/verbumby/verbum/backend/ctl/dictimport/dictparser, so a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser can break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/stardict, while a change to github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/stardict can't break github.com/verbumby/verbum/backend/ctl/dictimport/dictparser.
- Position
- Below the diagonal: github.com/verbumby/verbum/backend/ctl/dictimport/dictparser/stardict uses a module listed above it, which is the healthy direction.
34→12 github.com/verbumby/verbum/backend/handlers uses github.com/verbumby/verbum/backend/chttp✕
- Connections
- 1 pair of types, where a type in github.com/verbumby/verbum/backend/handlers uses a type in github.com/verbumby/verbum/backend/chttp.
- The types involved
github.com/verbumby/verbum/backend/handlers.handlers→github.com/verbumby/verbum/backend/chttp.Context
- Direction
- github.com/verbumby/verbum/backend/handlers uses github.com/verbumby/verbum/backend/chttp, so a change to github.com/verbumby/verbum/backend/chttp can break github.com/verbumby/verbum/backend/handlers, while a change to github.com/verbumby/verbum/backend/handlers can't break github.com/verbumby/verbum/backend/chttp.
- Position
- Below the diagonal: github.com/verbumby/verbum/backend/handlers uses a module listed above it, which is the healthy direction.
35→27 frontend.verbum.browser uses frontend.verbum.client✕
- Connections
- 1 pair of types, where a type in frontend.verbum.browser uses a type in frontend.verbum.client.
- The types involved
frontend.verbum.browser.VerbumAPIClientBrowser→frontend.verbum.client.VerbumAPIClientImpl
- Direction
- frontend.verbum.browser uses frontend.verbum.client, so a change to frontend.verbum.client can break frontend.verbum.browser, while a change to frontend.verbum.browser can't break frontend.verbum.client.
- Position
- Below the diagonal: frontend.verbum.browser uses a module listed above it, which is the healthy direction.
36→27 frontend.verbum.server uses frontend.verbum.client✕
- Connections
- 1 pair of types, where a type in frontend.verbum.server uses a type in frontend.verbum.client.
- The types involved
frontend.verbum.server.VerbumAPIClientServer→frontend.verbum.client.VerbumAPIClientImpl
- Direction
- frontend.verbum.server uses frontend.verbum.client, so a change to frontend.verbum.client can break frontend.verbum.server, while a change to frontend.verbum.server can't break frontend.verbum.client.
- Position
- Below the diagonal: frontend.verbum.server 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 |
|---|---|---|
| A05:2025 — Injection | 19 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | High / Critical |
Roadmap
Top priorities: Resolve the 31 Low coverage finding(s) in Code Coverage — start with query.go (2), load.go, handlers.go; Add tests that import the unreached modules (directly or through their public entry); Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 31 Low coverage finding(s) in Code Coverage — start with query.go (2), load.go, handlers.go. | +6.3 pts | Medium | Code Coverage |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. | +4.2 pts | Low | ADR Quality |
| Add tests that import the unreached modules (directly or through their public entry). | +4.6 pts | Medium | Test Coverage |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +3.2 pts | Medium | Keyboard semantics |
| Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally. | +3.0 pts | Medium | Security & performance tooling |
| Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail. | +3.0 pts | Medium | Outbound HTTP resilience |
| Expand the README with getting-started, architecture overview and a project map. | +2.5 pts | Medium | Documentation (README) |
| 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. | +2.3 pts | Medium | Architecture documentation |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.3 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| backend/ctl/dictimport/dictparser/grammardb/parser.go | 5.6 | Mixed | Cyclomatic Complexity: grammardb.grammarCategories (cyclomatic 86) |
| backend/ctl/dictimport/dictimport.go | 5.6 | Mixed | Cyclomatic Complexity: commandController.indexArticles (cyclomatic 21) |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 5.8 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| backend/dictionary/dictionary.go | 5.9 | Mixed | Cyclomatic Complexity: dictionary.InitDictionaries (cyclomatic 36) |
| backend/dictionary/abbrev.go | 6.3 | Mixed | Cyclomatic Complexity: dictionary.loadDSLAbbrevs (cyclomatic 17) |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| backend/ctl/cleanup.go | 7.0 | Mixed | Code Duplication: Edited copy of a member (8 corresponding lines) |
| backend/handlers/api_search.go | 7.4 | Mixed | Cyclomatic Complexity: handlers.APISearch (cyclomatic 22) |
| frontend/common/SearchControl.tsx | 7.4 | Mixed | Cyclomatic Complexity: SearchControl.useSuggestions (cyclomatic 20) |
| backend/ctl/dictimport/dictparser/html/parser.go | 7.8 | Mixed | Cyclomatic Complexity: html.parseArticle (cyclomatic 17) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| backend/ctl/dictimport/idgen_test.go | 8.2 | Near-clean | Explicit Debt: TodoComment |
| backend/ctl/dictimport/dictparser/dsl/parser.go | 8.5 | Near-clean | Cognitive Complexity: dsl.ParseReader (cognitive 21) |
| backend/handlers/api_suggest.go | 8.5 | Near-clean | Cognitive Complexity: handlers.APISuggest (cognitive 17) |
| frontend/pages/dict/DefaultSection.tsx | 8.5 | Near-clean | God Classes: FunctionTooLong: DefaultSection.DefaultSection |
| frontend/pages/index/IndexPage.tsx | 8.5 | Near-clean | God Classes: FunctionTooLong: IndexPage.IndexPage |
| backend/handlers/api_dictionary_abbrevs.go | 8.5 | Near-clean | Code Duplication: Edited copy of a member (11 corresponding lines) |
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 58 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, the weighted average across measured dimensions.
What we checked — 58 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, 124 of 132 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
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Go module (REDACTED/go.sum), but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Go dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D16 Bus Factor — 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. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 991 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- 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)` (7290 LoC, 108 module-visible types across 24 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.
- D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 276 sampled here came from .go files. This repository's .tsx source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via ToolchainServer (.). `go` is not on PATH — this repository boots from its toolchain's own run entry point (package main in backend/verbum starts an HTTP listener), so the tier cannot start it without that toolchain No runtime accessibility evidence was produced for this scan. This is a statement about THIS RUN's environment, not about the application: nothing here says the app is inaccessible, only that it was never rendered.
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
- C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Go is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Go is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
- X1 Async correctness — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X12 Unreachable branch — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X21 Side-effecting pattern guard — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X25 Inert configuration knob — 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's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- 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.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- 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.
- 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.
- D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- 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.
- AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
- 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".
Dimensions
D1 · Cyclomatic Complexity
9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was grammardb.grammarCategories at 86.
What to do
- Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with grammardb.grammarCategories (cyclomatic 86). — Refactoring it lifts Cyclomatic Complexity from 6.8 to about 7.3/10.
D2 · Cognitive Complexity
11 method(s) exceeded the cognitive complexity threshold of 15; the worst was grammardb.ParseDirectory at 93.
What to do
- Bring the 1 body over 60 down to 60 or less in Cognitive Complexity — start with grammardb.ParseDirectory (cognitive 93). — Refactoring it lifts Cognitive Complexity from 6.0 to about 6.7/10.
D3 · God Classes
7 over-large unit(s) detected — types, modules or files that carry too much.
What to do
- Resolve the 7 FunctionTooLong finding(s) in God Classes — start with parser.go (2), dictionary.go, api_search.go. — One of this dimension's main actionable groups (7 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. 0.9 % of the production lines (65 of 7,290) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .tsx (27% of production source) was not exposed to THIS dimension's token comparison and is not in this count; duplication there is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream.
What to do
- Resolve the 1 Edited copy of a member (11 corresponding lines) finding(s) in Code Duplication — start with api_dictionary_abbrevs.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (8 corresponding lines) finding(s) in Code Duplication — start with cleanup.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with seo.go. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
2 production modules (npm+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 1 of the 2 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D6 · Cohesion (LCOM4)
0 of 7 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 16.7% — 31 file(s) below 50%. Measured from the Go suite (github.com/verbumby/verbum: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
What to do
- Resolve the 31 Low coverage finding(s) in Code Coverage — start with query.go (2), load.go, handlers.go. — One of this dimension's main actionable groups (31 warning-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (github.com/verbumby/verbum): measured (0 flaky).
D12 · Dependency Hygiene
2 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 173 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 173 package(s) this repository's committed lockfile installs for a consumer — its 23 production, optional and peer dependency(ies), across 1 product REDACTED manifest(s), and everything those install in turn. Its 0 `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. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. Third-party code that ships WITHOUT a manifest entry was read too: 2 component(s) whose licence travels in the tree (vendored or copied-in directories, licence comments preserved in committed bundles, compiled wasm modules) and 0 bundled package(s) named only by a bundle's module path, graded on the registry; 0 use a banned licence. 1 vendored, copied-in or compiled component(s) state no licence this pass can read — missing data, not charged. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares a Go module (REDACTED/go.sum), and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
Top hotspots: backend/dictionary/dictionary.go (2×36=72)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with dictionary.go. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
1 deducted task-comment markers across 7290 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.
What to do
- Resolve the 1 TodoComment finding(s) in Explicit Debt — start with idgen_test.go. — One of this dimension's main actionable groups (1 warning-level).
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 REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D22 · Internal API Consistency
0 API inconsistencies among 20 exposed members measured against a convention their peers follow.
D27 · Navigability
55 % of calls cross a namespace and 18 % go through an interface, but 60 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .go source only — this repository's .tsx was not sampled for call sites, so this score covers part of the tree, not all of it.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
19 finding(s): 0 critical, 13 high, 6 medium, 0 low. 13 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- No action in Static Analysis (SAST) — all 13 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (13 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
7 finding(s): 0 critical, 3 high, 4 medium, 0 low.
What to do
- Resolve the 3 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 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 25 of the 123 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: ArticlePage.tsx↔IndexPage.tsx 73%; App.tsx↔IndexPage.tsx 50%
What to do
- Resolve the 2 Change coupling finding(s) in Change Coupling — start with ArticlePage.tsx, App.tsx. — One of this dimension's main actionable groups (2 warning-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 23 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
AC3 · Page structure
- A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — REDACTED:207
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — frontend/index.html:2
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — frontend/index.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — frontend/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×5) — frontend/common/SearchControl.tsx:136, frontend/common/Suggestions.tsx:18, frontend/common/dictsfilter.tsx:64, …
- The repo's own CSS styles .suggestions with `cursor: pointer`, so this <ul> is a control — but it has no role, no tabIndex={0} and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabIndex={0} + a key handler. — frontend/common/Suggestions.tsx:16
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.search-input .button-search` sets color: white on background-color: red — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — frontend/styles.css:89
- `.btn-check:focus-visible + .btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/bootstrap.gen.css:776
- `textarea` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/styles.css:52
- `.article .buttons .btn` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — frontend/styles.css:275
- `.search-input .button-control:active svg` moves (`animation-name: search-input-button-control-active`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/styles.css:122
What to do
- Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition
AX2 · Stateful singletons
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
AX9 · CQS / query purity
M1 · Documentation (README)
- The root README is 5 words, against a bar of 120. Of the three newcomer-critical sections this check looks for by heading, in the README and in the repository documents it links, it found no a build/run or getting-started section, no a testing section, no an architecture or project-map section. Sections are matched on HEADING text only, so material written under a heading this check does not recognise — or with no heading at all — is not seen and this row may understate what the document covers. — README.md:1
What to do
- Expand the README with getting-started, architecture overview and a project map.
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation
- 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
P1 · CI/CD gates
P2 · Observability
- Only 1/2 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Add a health-check endpoint (a /healthz handler) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `REDACTED` 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 `actions/dependency-review-action`. — REDACTED:17
What to do
- Your ecosystem's static analyzer is declared as a dependency but is not wired into CI — run it as a required step on push/PR (e.g. `composer phpstan` / `mix sobelow` / `bundle exec brakeman` / the spotbugs Gradle task / `sbt scalafixAll --check` / `golangci-lint run` / `rebar3 lint`) so a regression fails the build instead of relying on someone running it locally.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P7 · Outbound HTTP resilience
- `http.DefaultClient` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — backend/storage/query.go:43
What to do
- Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- frontend/pages/dict/AbbrSection.tsx:10 · frontend/pages/dict/PrefaceSection.tsx:10 — 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. — frontend/pages/dict/AbbrSection.tsx:10
- frontend/pages/dict/dict.ts:27 · frontend/pages/dict/letterfilter.ts:14 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — frontend/pages/dict/dict.ts:27
- frontend/pages/dict/abbr.ts:28 · frontend/pages/dict/preface.ts:28 — 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. — frontend/pages/dict/abbr.ts:28
- frontend/pages/article/article.ts:42 · frontend/pages/dict/letterfilter.ts:48 — 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. — frontend/pages/article/article.ts:42
- frontend/pages/index/IndexPage.tsx:53 · frontend/pages/index/IndexPage.tsx:78 — 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. — frontend/pages/index/IndexPage.tsx:53
- frontend/pages/article/ArticlePage.tsx:47 · frontend/pages/support/SupportPage.tsx:4 — 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. — frontend/pages/article/ArticlePage.tsx:47
- frontend/pages/article/ArticlePage.tsx:13 · frontend/pages/dict/DictPage.tsx:11 — the two spans are one implementation copied and then locally edited — 58 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. — frontend/pages/article/ArticlePage.tsx:13
- frontend/verbum/browser.ts:4 · frontend/verbum/server.ts:16 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — frontend/verbum/browser.ts:4
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
R3 · Large Files
R4 · Test Coverage
- 0% of 55 production file(s) reachable from 0 test file(s) via the import graph — 'production' here is the RESIDUE: every source file left once tests, tooling, generated output, config, declarations and declaration-only modules, fixture corpora, type fixtures, behaviour-free data modules, re-export barrels, registration/constant data modules and service workers are set aside, so the percentage is taken over a smaller denominator than the workspace's file count
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- 65 file(s) (~3189 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it.
R8 · Dependency Hygiene
R9 · Circular Imports
X2 · Cancellation propagation
- Only 4/5 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial) accept a context.Context or an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` (Go: `ctx context.Context`) 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.
- `Query` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — backend/storage/query.go:17
What to do
- Thread a context.Context or an AbortSignal through functions that make requests, so the work stops when its caller gives up.
X27 · Collection changed while being enumerated
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — frontend/common/SearchControl.tsx:246
What to do
- Swallowed exception (empty catch)
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.
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 |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | 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 | 64.1 | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 98.2 | Exemplary | Solid. |
| Maturity | 51.0 | Adequate — gated by M1, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 40.2 | Weak — gated by R4, P3, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 91.1 | Checked 4 of 10 | Solid. |
| Accessibility | 46.7 | Weak — gated by AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100.0 | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D36 Supply-chain Provenance & Signing — 1 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.
- X6 Hand-rolled structured-format parsing — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
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.
- AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; 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.
- AX4 Dependency direction — not applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — `go` is not on PATH — this repository boots from its toolchain's own run entry point (package main in backend/verbum starts an HTTP listener), so the tier cannot start it without that toolchain No runtime accessibility evidence was produced for this scan. This is a statement about THIS RUN's environment, not about the application: nothing here says the app is inaccessible, only that it was never rendered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- D10 Test Quality — ~658 lines of test source are present (.go) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
- D16 Bus Factor — single-contributor repository — bus factor is not applicable
- 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.
- D19 Documentation Quality — D19 reads .NET projects and npm packages as units; 1 folder(s) declared by REDACTED were not judged for an overview, an example or the map.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (728 declarations, no unit with a dominant convention).
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go source were not judged.
- 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.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- 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.
- 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
- DM1 Domain Modelling — not scored — this repository shows none of the 2 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 CQRS handler(s))
- ED5 Idempotency — 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
- 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'.
- 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 data present for 42 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for a `func BenchmarkXxx(b *testing.B)` in any `_test.go` file, 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: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — X1 reached only 39% of this repository's production lines — go (4,421 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 39% of this repository's production lines — go (4,421 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 39% of this repository's production lines — go (4,421 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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.
- X21 Side-effecting pattern guard — X21 reached only 39% of this repository's production lines — go (4,421 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- 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 — X24 reached only 39% of this repository's production lines — go (4,421 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X25 Inert configuration knob — X25 reached only 39% of this repository's production lines — go (4,421 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Go was read, and it logs through none: the standard library's `log` takes one finished line, or it makes no log call outside its tests at all, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through log/slog, zap, logrus, zerolog, hclog, go-kit's log or logr would be judged.
- 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 — 24 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Click handler on a non-interactive <span> frontend/common/SearchControl.tsx:136
- Click handler on a non-interactive <span> frontend/common/dictsfilter.tsx:64
- Click handler on a non-interactive <span> frontend/common/dictsfilter.tsx:68
- Click handler on a non-interactive <span> frontend/common/dictsfilter.tsx:145
- REDACTED
- REDACTED
- REDACTED
- <html> without a lang frontend/index.html:2
- Document without a <title> frontend/index.html:2
- Clickable element isn't keyboard-operable frontend/common/Suggestions.tsx:16
- Click handler on a non-interactive <li> frontend/common/Suggestions.tsx:18
Serious — 96 finding(s)
- Low coverage: backend/article/load.go backend/article/load.go:1
- Low coverage: backend/chttp/handlers.go backend/chttp/handlers.go:1
- Low coverage: backend/chttp/middleware.go backend/chttp/middleware.go:1
- Low coverage: backend/config/config.go backend/config/config.go:1
- Low coverage: backend/ctl/cleanup.go backend/ctl/cleanup.go:1
- Low coverage: backend/ctl/dictimport/dictimport.go backend/ctl/dictimport/dictimport.go:1
- Low coverage: backend/ctl/dictimport/dictparser/grammardb/parser.go backend/ctl/dictimport/dictparser/grammardb/parser.go:1
- Low coverage: backend/ctl/export.go backend/ctl/export.go:1
- Low coverage: backend/dictionary/abbrev.go backend/dictionary/abbrev.go:1
- Low coverage: backend/dictionary/common.go backend/dictionary/common.go:1
- Low coverage: backend/dictionary/dictionary.go backend/dictionary/dictionary.go:1
- Low coverage: backend/dictionary/dsl.go backend/dictionary/dsl.go:1
- Low coverage: backend/dictionary/get.go backend/dictionary/get.go:1
- Low coverage: backend/dictionary/grammardb.go backend/dictionary/grammardb.go:1
- Low coverage: backend/dictionary/html.go backend/dictionary/html.go:1
- Low coverage: backend/dictionary/sections.go backend/dictionary/sections.go:1
- Low coverage: backend/dictionary/stardict.go backend/dictionary/stardict.go:1
- Low coverage: backend/htmlui/letter_filter.go backend/htmlui/letter_filter.go:1
- Low coverage: backend/htmlui/query_param_bool.go backend/htmlui/query_param_bool.go:1
- Low coverage: backend/htmlui/query_param_in_dicts.go backend/htmlui/query_param_in_dicts.go:1
- Low coverage: backend/htmlui/query_param_integer.go backend/htmlui/query_param_integer.go:1
- Low coverage: backend/htmlui/query_param_string.go backend/htmlui/query_param_string.go:1
- Low coverage: backend/htmlui/url_query.go backend/htmlui/url_query.go:1
- Low coverage: backend/storage/bulk.go backend/storage/bulk.go:1
- Low coverage: backend/storage/index.go backend/storage/index.go:1
- FunctionTooLong: dictionary.InitDictionaries backend/dictionary/dictionary.go:30
- FunctionTooLong: grammardb.grammarCategories backend/ctl/dictimport/dictparser/grammardb/parser.go:307
- FunctionTooLong: handlers.APISearch backend/handlers/api_search.go:28
- FunctionTooLong: DefaultSection.DefaultSection frontend/pages/dict/DefaultSection.tsx:23
- FunctionTooLong: IndexPage.IndexPage frontend/pages/index/IndexPage.tsx:21
- FunctionTooLong: grammardb.ParseDirectory backend/ctl/dictimport/dictparser/grammardb/parser.go:122
- FunctionTooLong: SearchControl.SearchControl frontend/common/SearchControl.tsx:22
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Focus outline removed in CSS without a :focus replacement frontend/bootstrap.gen.css:776
- Focus outline removed in CSS without a :focus replacement frontend/styles.css:52
- Focus outline removed in CSS without a :focus replacement frontend/styles.css:275
- REDACTED
- REDACTED
- Change coupling: ArticlePage.tsx ↔ IndexPage.tsx frontend/pages/article/ArticlePage.tsx:1
- Change coupling: App.tsx ↔ IndexPage.tsx frontend/App.tsx:1
- Data table has no header cells REDACTED:207
- Page without a main landmark frontend/index.html:2
- Low contrast colour pair in CSS (4.0:1) frontend/styles.css:89
- Animation without a prefers-reduced-motion guard frontend/styles.css:122
- grammardb.grammarCategories (cyclomatic 86) backend/ctl/dictimport/dictparser/grammardb/parser.go:307
- dictionary.InitDictionaries (cyclomatic 36) backend/dictionary/dictionary.go:30
- grammardb.ParseDirectory (cyclomatic 35) backend/ctl/dictimport/dictparser/grammardb/parser.go:122
- handlers.APISearch (cyclomatic 22) backend/handlers/api_search.go:28
- commandController.indexArticles (cyclomatic 21) backend/ctl/dictimport/dictimport.go:232
- SearchControl.useSuggestions (cyclomatic 20) frontend/common/SearchControl.tsx:179
- commandController.run (cyclomatic 19) backend/ctl/dictimport/dictimport.go:129
- html.parseArticle (cyclomatic 17) backend/ctl/dictimport/dictparser/html/parser.go:108
- dictionary.loadDSLAbbrevs (cyclomatic 17) backend/dictionary/abbrev.go:33
- Hotspot: backend/dictionary/dictionary.go backend/dictionary/dictionary.go:30
- TodoComment backend/ctl/dictimport/idgen_test.go:15
- grammardb.ParseDirectory (cognitive 93) backend/ctl/dictimport/dictparser/grammardb/parser.go:122
- commandController.indexArticles (cognitive 50) backend/ctl/dictimport/dictimport.go:232
- grammardb.grammarCategories (cognitive 44) backend/ctl/dictimport/dictparser/grammardb/parser.go:307
- handlers.APISearch (cognitive 43) backend/handlers/api_search.go:28
- dictionary.InitDictionaries (cognitive 35) backend/dictionary/dictionary.go:30
- dictionary.loadDSLAbbrevs (cognitive 32) backend/dictionary/abbrev.go:33
- SearchControl.useSuggestions (cognitive 29) frontend/common/SearchControl.tsx:179
- html.parseArticle (cognitive 24) backend/ctl/dictimport/dictparser/html/parser.go:108
- dsl.ParseReader (cognitive 21) backend/ctl/dictimport/dictparser/dsl/parser.go:13
- commandController.run (cognitive 20) backend/ctl/dictimport/dictimport.go:129
- handlers.APISuggest (cognitive 17) backend/handlers/api_suggest.go:51
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (11 corresponding lines) backend/handlers/api_dictionary_abbrevs.go:13
- Edited copy of a member (8 corresponding lines) backend/ctl/cleanup.go:28
- Duplicated block (7 lines × 2) backend/handlers/seo.go:67
- Duplicated block (8 lines × 2) backend/ctl/dictimport/dictimport.go:159
- Outbound HTTP without resilience backend/storage/query.go:43
- Duplicated block (30 lines × 2 locations) frontend/pages/dict/AbbrSection.tsx:10
- Duplicated block (24 lines × 2 locations) frontend/pages/dict/dict.ts:27
- Duplicated block (22 lines × 2 locations) frontend/pages/dict/abbr.ts:28
- Duplicated block (14 lines × 2 locations) frontend/pages/article/article.ts:42
- Duplicated block (12 lines × 2 locations) frontend/pages/index/IndexPage.tsx:53
- Duplicated block (11 lines × 2 locations) frontend/pages/article/ArticlePage.tsx:47
- Duplicated block with local edits (9 matched lines × 2 locations) frontend/pages/article/ArticlePage.tsx:13
- Duplicated block (7 lines × 2 locations) frontend/verbum/browser.ts:4
- Test Coverage
- Function without context.Context: Query backend/storage/query.go:17
- Swallowed exception (empty catch) frontend/common/SearchControl.tsx:246
Minor — 10 finding(s)
- Hand-rolled JSON/XML parsing via regex backend/ctl/export.go:16
- Hand-rolled JSON/XML parsing via regex backend/ctl/dictimport/dictparser/html/parser.go:105
- No ADRs found REDACTED:1
- REDACTED
- Thin README README.md:1
- No ADRs
- Logging is not universal
- No dependency-update automation REDACTED:17
- Not all functions that make a request accept a context.Context or an AbortSignal
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 2 finding(s)
- Outdated: github.com/go-chi/chi/v5
- Outdated: golang.org/x/text
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-0814184ba70a48259cec53d33575cd36/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=791" --report-format json --report-path /tmp/watchdog-gitleaks-0814184ba70a48259cec53d33575cd36/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-0814184ba70a48259cec53d33575cd36/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 . | 19 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 7 | 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 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 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 |