Executive summary
umputun/cronn falls short of our standard for production, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 56.7 out of 100 and is rated Adequate, and 29 of its 31 critical findings are security problems.
Accessibility, at 48.2, is the weakest lens and counts most in the score. The best first step is fixing focus, motion and contrast, worth about 7.4 points. Structuring the pages comes next, worth about 3.9 points. Raising Accessibility to 70 would lift the score to about 63.9.
Nineteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Six secrets can leak from the build pipeline, and one automatic update takes new releases before a bad one can be spotted. Pinning each tool to an exact version, limiting each secret to its own step and setting a waiting period for automatic updates would close these risks. Fixing the weaknesses the scanner points to would fix the security weakness in the code, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The two labels or groups of fields with no name need connecting to their fields or naming.
The product code is 5,289 lines, about €17,000 to rebuild.
If Accessibility rose from 48.2 to 70, the lowest score rated Strong, the score would rise from 56.7 to about 63.9.
Rebuild cost: about €17,000 · Estimate
| Cost to rebuild | €5,800 to €29,000, for 96 to 305 hours of work, about 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.8 at a score of 57. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it. |
| Size | Small: 5,289 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 app.web.static | 2 docs.plans.completed.dashboard-redesign.gen | 3 github.com/umputun/cronn/app/conditions | 4 github.com/umputun/cronn/app/crontab/internal/schema | 5 github.com/umputun/cronn/app/service/request | 6 github.com/umputun/cronn/app/web/enums | 7 github.com/umputun/cronn/app/crontab | 8 github.com/umputun/cronn/app/resumer | 9 github.com/umputun/cronn/app/web/persistence | 10 github.com/umputun/cronn/app/service | 11 github.com/umputun/cronn/app/notify | 12 github.com/umputun/cronn/app/web | 13 github.com/umputun/cronn/app |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 app.web.static | |||||||||||||
| 2 docs.plans.completed.dashboard-redesign.gen | |||||||||||||
| 3 github.com/umputun/cronn/app/conditions | |||||||||||||
| 4 github.com/umputun/cronn/app/crontab/internal/schema | |||||||||||||
| 5 github.com/umputun/cronn/app/service/request | |||||||||||||
| 6 github.com/umputun/cronn/app/web/enums | |||||||||||||
| 7 github.com/umputun/cronn/app/crontab | 1 | 2 | |||||||||||
| 8 github.com/umputun/cronn/app/resumer | 1 | ||||||||||||
| 9 github.com/umputun/cronn/app/web/persistence | 1 | 1 | |||||||||||
| 10 github.com/umputun/cronn/app/service | 2 | 2 | 3 | 1 | |||||||||
| 11 github.com/umputun/cronn/app/notify | 1 | ||||||||||||
| 12 github.com/umputun/cronn/app/web | 3 | 1 | 11 | 3 | |||||||||
| 13 github.com/umputun/cronn/app | 1 | 1 |
7→3 github.com/umputun/cronn/app/crontab uses github.com/umputun/cronn/app/conditions✕
- Connections
- 1 pair of types, where a type in github.com/umputun/cronn/app/crontab uses a type in github.com/umputun/cronn/app/conditions.
- The types involved
github.com/umputun/cronn/app/crontab.JobSpec→github.com/umputun/cronn/app/conditions.Config
- Direction
- github.com/umputun/cronn/app/crontab uses github.com/umputun/cronn/app/conditions, so a change to github.com/umputun/cronn/app/conditions can break github.com/umputun/cronn/app/crontab, while a change to github.com/umputun/cronn/app/crontab can't break github.com/umputun/cronn/app/conditions.
- Position
- Below the diagonal: github.com/umputun/cronn/app/crontab uses a module listed above it, which is the healthy direction.
7→10 github.com/umputun/cronn/app/crontab uses github.com/umputun/cronn/app/service part of a loop✕
- Connections
- 2 pairs of types, where a type in github.com/umputun/cronn/app/crontab uses a type in github.com/umputun/cronn/app/service.
- The types involved
github.com/umputun/cronn/app/crontab.Parser→github.com/umputun/cronn/app/service.CrontabParsergithub.com/umputun/cronn/app/crontab.Single→github.com/umputun/cronn/app/service.CrontabParser
- Direction
- github.com/umputun/cronn/app/crontab uses github.com/umputun/cronn/app/service, so a change to github.com/umputun/cronn/app/service can break github.com/umputun/cronn/app/crontab, while a change to github.com/umputun/cronn/app/crontab can't break github.com/umputun/cronn/app/service.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
8→10 github.com/umputun/cronn/app/resumer uses github.com/umputun/cronn/app/service part of a loop✕
- Connections
- 1 pair of types, where a type in github.com/umputun/cronn/app/resumer uses a type in github.com/umputun/cronn/app/service.
- The types involved
github.com/umputun/cronn/app/resumer.Resumer→github.com/umputun/cronn/app/service.Resumer
- Direction
- github.com/umputun/cronn/app/resumer uses github.com/umputun/cronn/app/service, so a change to github.com/umputun/cronn/app/service can break github.com/umputun/cronn/app/resumer, while a change to github.com/umputun/cronn/app/resumer can't break github.com/umputun/cronn/app/service.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
9→5 github.com/umputun/cronn/app/web/persistence uses github.com/umputun/cronn/app/service/request✕
- Connections
- 1 pair of types, where a type in github.com/umputun/cronn/app/web/persistence uses a type in github.com/umputun/cronn/app/service/request.
- The types involved
github.com/umputun/cronn/app/web/persistence.SQLiteStore→github.com/umputun/cronn/app/service/request.RecordExecution
- Direction
- github.com/umputun/cronn/app/web/persistence uses github.com/umputun/cronn/app/service/request, so a change to github.com/umputun/cronn/app/service/request can break github.com/umputun/cronn/app/web/persistence, while a change to github.com/umputun/cronn/app/web/persistence can't break github.com/umputun/cronn/app/service/request.
- Position
- Below the diagonal: github.com/umputun/cronn/app/web/persistence uses a module listed above it, which is the healthy direction.
9→12 github.com/umputun/cronn/app/web/persistence uses github.com/umputun/cronn/app/web part of a loop✕
- Connections
- 1 pair of types, where a type in github.com/umputun/cronn/app/web/persistence uses a type in github.com/umputun/cronn/app/web.
- The types involved
github.com/umputun/cronn/app/web/persistence.SQLiteStore→github.com/umputun/cronn/app/web.Persistence
- Direction
- github.com/umputun/cronn/app/web/persistence uses github.com/umputun/cronn/app/web, so a change to github.com/umputun/cronn/app/web can break github.com/umputun/cronn/app/web/persistence, while a change to github.com/umputun/cronn/app/web/persistence can't break github.com/umputun/cronn/app/web.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
10→3 github.com/umputun/cronn/app/service uses github.com/umputun/cronn/app/conditions✕
- Connections
- 2 pairs of types, where a type in github.com/umputun/cronn/app/service uses a type in github.com/umputun/cronn/app/conditions.
- The types involved
github.com/umputun/cronn/app/service.ConditionChecker→github.com/umputun/cronn/app/conditions.Configgithub.com/umputun/cronn/app/service.Scheduler→github.com/umputun/cronn/app/conditions.Config
- Direction
- github.com/umputun/cronn/app/service uses github.com/umputun/cronn/app/conditions, so a change to github.com/umputun/cronn/app/conditions can break github.com/umputun/cronn/app/service, while a change to github.com/umputun/cronn/app/service can't break github.com/umputun/cronn/app/conditions.
- Position
- Below the diagonal: github.com/umputun/cronn/app/service uses a module listed above it, which is the healthy direction.
10→5 github.com/umputun/cronn/app/service uses github.com/umputun/cronn/app/service/request✕
- Connections
- 2 pairs of types, where a type in github.com/umputun/cronn/app/service uses a type in github.com/umputun/cronn/app/service/request.
- The types involved
github.com/umputun/cronn/app/service.JobEventHandler→github.com/umputun/cronn/app/service/request.OnJobCompletegithub.com/umputun/cronn/app/service.JobEventHandler→github.com/umputun/cronn/app/service/request.OnJobStart
- Direction
- github.com/umputun/cronn/app/service uses github.com/umputun/cronn/app/service/request, so a change to github.com/umputun/cronn/app/service/request can break github.com/umputun/cronn/app/service, while a change to github.com/umputun/cronn/app/service can't break github.com/umputun/cronn/app/service/request.
- Position
- Below the diagonal: github.com/umputun/cronn/app/service uses a module listed above it, which is the healthy direction.
10→7 github.com/umputun/cronn/app/service uses github.com/umputun/cronn/app/crontab✕
- Connections
- 3 pairs of types, where a type in github.com/umputun/cronn/app/service uses a type in github.com/umputun/cronn/app/crontab.
- The types involved
github.com/umputun/cronn/app/service.CrontabParser→github.com/umputun/cronn/app/crontab.JobSpecgithub.com/umputun/cronn/app/service.Scheduler→github.com/umputun/cronn/app/crontab.JobSpecgithub.com/umputun/cronn/app/service.Scheduler→github.com/umputun/cronn/app/crontab.RepeaterConfig
- Direction
- github.com/umputun/cronn/app/service uses github.com/umputun/cronn/app/crontab, so a change to github.com/umputun/cronn/app/crontab can break github.com/umputun/cronn/app/service, while a change to github.com/umputun/cronn/app/service can't break github.com/umputun/cronn/app/crontab.
- Position
- Below the diagonal: github.com/umputun/cronn/app/service uses a module listed above it, which is the healthy direction.
10→8 github.com/umputun/cronn/app/service uses github.com/umputun/cronn/app/resumer✕
- Connections
- 1 pair of types, where a type in github.com/umputun/cronn/app/service uses a type in github.com/umputun/cronn/app/resumer.
- The types involved
github.com/umputun/cronn/app/service.Resumer→github.com/umputun/cronn/app/resumer.Cmd
- Direction
- github.com/umputun/cronn/app/service uses github.com/umputun/cronn/app/resumer, so a change to github.com/umputun/cronn/app/resumer can break github.com/umputun/cronn/app/service, while a change to github.com/umputun/cronn/app/service can't break github.com/umputun/cronn/app/resumer.
- Position
- Below the diagonal: github.com/umputun/cronn/app/service uses a module listed above it, which is the healthy direction.
11→10 github.com/umputun/cronn/app/notify uses github.com/umputun/cronn/app/service✕
- Connections
- 1 pair of types, where a type in github.com/umputun/cronn/app/notify uses a type in github.com/umputun/cronn/app/service.
- The types involved
github.com/umputun/cronn/app/notify.Service→github.com/umputun/cronn/app/service.Notifier
- Direction
- github.com/umputun/cronn/app/notify uses github.com/umputun/cronn/app/service, so a change to github.com/umputun/cronn/app/service can break github.com/umputun/cronn/app/notify, while a change to github.com/umputun/cronn/app/notify can't break github.com/umputun/cronn/app/service.
- Position
- Below the diagonal: github.com/umputun/cronn/app/notify uses a module listed above it, which is the healthy direction.
12→5 github.com/umputun/cronn/app/web uses github.com/umputun/cronn/app/service/request✕
- Connections
- 3 pairs of types, where a type in github.com/umputun/cronn/app/web uses a type in github.com/umputun/cronn/app/service/request.
- The types involved
github.com/umputun/cronn/app/web.Persistence→github.com/umputun/cronn/app/service/request.RecordExecutiongithub.com/umputun/cronn/app/web.Server→github.com/umputun/cronn/app/service/request.OnJobCompletegithub.com/umputun/cronn/app/web.Server→github.com/umputun/cronn/app/service/request.OnJobStart
- Direction
- github.com/umputun/cronn/app/web uses github.com/umputun/cronn/app/service/request, so a change to github.com/umputun/cronn/app/service/request can break github.com/umputun/cronn/app/web, while a change to github.com/umputun/cronn/app/web can't break github.com/umputun/cronn/app/service/request.
- Position
- Below the diagonal: github.com/umputun/cronn/app/web uses a module listed above it, which is the healthy direction.
12→7 github.com/umputun/cronn/app/web uses github.com/umputun/cronn/app/crontab✕
- Connections
- 1 pair of types, where a type in github.com/umputun/cronn/app/web uses a type in github.com/umputun/cronn/app/crontab.
- The types involved
github.com/umputun/cronn/app/web.JobsProvider→github.com/umputun/cronn/app/crontab.JobSpec
- Direction
- github.com/umputun/cronn/app/web uses github.com/umputun/cronn/app/crontab, so a change to github.com/umputun/cronn/app/crontab can break github.com/umputun/cronn/app/web, while a change to github.com/umputun/cronn/app/web can't break github.com/umputun/cronn/app/crontab.
- Position
- Below the diagonal: github.com/umputun/cronn/app/web uses a module listed above it, which is the healthy direction.
12→9 github.com/umputun/cronn/app/web uses github.com/umputun/cronn/app/web/persistence✕
- Connections
- 11 pairs of types, where a type in github.com/umputun/cronn/app/web uses a type in github.com/umputun/cronn/app/web/persistence.
- The types involved
github.com/umputun/cronn/app/web.Persistence→github.com/umputun/cronn/app/web/persistence.ExecutionInfogithub.com/umputun/cronn/app/web.Persistence→github.com/umputun/cronn/app/web/persistence.JobInfogithub.com/umputun/cronn/app/web.Server→github.com/umputun/cronn/app/web/persistence.ExecutionInfogithub.com/umputun/cronn/app/web.Server→github.com/umputun/cronn/app/web/persistence.JobInfogithub.com/umputun/cronn/app/web.TemplateData→github.com/umputun/cronn/app/web/persistence.JobInfogithub.com/umputun/cronn/app/web.inspectorData→github.com/umputun/cronn/app/web/persistence.ExecutionInfogithub.com/umputun/cronn/app/web.inspectorData→github.com/umputun/cronn/app/web/persistence.JobInfogithub.com/umputun/cronn/app/web.jobsStats→github.com/umputun/cronn/app/web/persistence.JobInfogithub.com/umputun/cronn/app/web.runOutputData→github.com/umputun/cronn/app/web/persistence.ExecutionInfogithub.com/umputun/cronn/app/web.web→github.com/umputun/cronn/app/web/persistence.ExecutionInfogithub.com/umputun/cronn/app/web.web→github.com/umputun/cronn/app/web/persistence.JobInfo
- Direction
- github.com/umputun/cronn/app/web uses github.com/umputun/cronn/app/web/persistence, so a change to github.com/umputun/cronn/app/web/persistence can break github.com/umputun/cronn/app/web, while a change to github.com/umputun/cronn/app/web can't break github.com/umputun/cronn/app/web/persistence.
- Position
- Below the diagonal: github.com/umputun/cronn/app/web uses a module listed above it, which is the healthy direction.
12→10 github.com/umputun/cronn/app/web uses github.com/umputun/cronn/app/service✕
- Connections
- 3 pairs of types, where a type in github.com/umputun/cronn/app/web uses a type in github.com/umputun/cronn/app/service.
- The types involved
github.com/umputun/cronn/app/web.Config→github.com/umputun/cronn/app/service.ManualJobRequestgithub.com/umputun/cronn/app/web.Server→github.com/umputun/cronn/app/service.JobEventHandlergithub.com/umputun/cronn/app/web.Server→github.com/umputun/cronn/app/service.ManualJobRequest
- Direction
- github.com/umputun/cronn/app/web uses github.com/umputun/cronn/app/service, so a change to github.com/umputun/cronn/app/service can break github.com/umputun/cronn/app/web, while a change to github.com/umputun/cronn/app/web can't break github.com/umputun/cronn/app/service.
- Position
- Below the diagonal: github.com/umputun/cronn/app/web uses a module listed above it, which is the healthy direction.
13→11 github.com/umputun/cronn/app uses github.com/umputun/cronn/app/notify✕
- Connections
- 1 pair of types, where a type in github.com/umputun/cronn/app uses a type in github.com/umputun/cronn/app/notify.
- The types involved
github.com/umputun/cronn/app.main→github.com/umputun/cronn/app/notify.Service
- Direction
- github.com/umputun/cronn/app uses github.com/umputun/cronn/app/notify, so a change to github.com/umputun/cronn/app/notify can break github.com/umputun/cronn/app, while a change to github.com/umputun/cronn/app can't break github.com/umputun/cronn/app/notify.
- Position
- Below the diagonal: github.com/umputun/cronn/app uses a module listed above it, which is the healthy direction.
13→12 github.com/umputun/cronn/app uses github.com/umputun/cronn/app/web✕
- Connections
- 1 pair of types, where a type in github.com/umputun/cronn/app uses a type in github.com/umputun/cronn/app/web.
- The types involved
github.com/umputun/cronn/app.main→github.com/umputun/cronn/app/web.SettingsInfo
- Direction
- github.com/umputun/cronn/app uses github.com/umputun/cronn/app/web, so a change to github.com/umputun/cronn/app/web can break github.com/umputun/cronn/app, while a change to github.com/umputun/cronn/app can't break github.com/umputun/cronn/app/web.
- Position
- Below the diagonal: github.com/umputun/cronn/app 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
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 37 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 7 | Medium |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Top priorities: 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; Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +7.4 pts | Medium | Visual & motion safety |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +3.9 pts | Medium | Page structure |
| Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label. | +3.6 pts | Medium | Forms & labels |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go. | +1.3 pts | Low | ADR Quality |
| Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +0.7 pts | Low | Static Analysis (SAST) |
| Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. | +0.7 pts | Low | IaC & Container Security |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.7 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 1.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.8 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 4.5 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.2 | Mixed | God Classes: TooManyMethods: Server |
| REDACTED | 5.3 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| app/main.go | 5.8 | Mixed | Cognitive Complexity: main.main (cognitive 20) |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 6.9 | Mixed | Dependency Vulnerabilities: Medium vulnerability: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| app/web/jobs.go | 7.3 | Mixed | Cognitive Complexity: Server.sortJobs (cognitive 19) |
| app/notify/notify.go | 7.4 | Mixed | Cognitive Complexity: notify.NewService (cognitive 17) |
| app/crontab/verify.go | 7.8 | Mixed | Cyclomatic Complexity: crontab.validateRequiredFields (cyclomatic 16) |
| REDACTED | 7.8 | Mixed | Code Duplication: Edited copy of a member (6 corresponding lines) |
| app/conditions/conditions.go | 8.5 | Near-clean | Cognitive Complexity: Checker.Check (cognitive 21) |
| app/crontab/crontab.go | 8.5 | Near-clean | Cognitive Complexity: Parser.Changes (cognitive 21) |
| app/resumer/resumer.go | 8.5 | Near-clean | Cognitive Complexity: Resumer.List (cognitive 16) |
| app/web/api.go | 8.5 | Near-clean | Code Duplication: Duplicated block (10 lines × 2) |
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 49 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 — 49 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, 90 of 108 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 · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ 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 Python distribution 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-maintainer repository — bus factor is not applicable (8 contributor(s) across 253 commit(s) sampled, automation and bot accounts excluded). One of them holds 91% of the history; the other 7 hold 1.3% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- 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.
- 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 DockerCompose (docker-compose.yml). the app booted but exposed no published HTTP port — nothing to crawl (publish the web service's port to unlock runtime evidence).
- 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, Python 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, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- 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.
- X5 Nullable reference types — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax and MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's Python 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- 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.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- 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.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- 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 REDACTED (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.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Scheduler.runJobWithCommand at 17.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Scheduler.runJobWithCommand (cyclomatic 17), crontab.validateRequiredFields (cyclomatic 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
10 method(s) exceeded the cognitive complexity threshold of 15; the worst was Scheduler.listenForManualTriggers at 25.
What to do
- Bring the 10 bodies over 15 down to 15 or less in Cognitive Complexity — start with Scheduler.listenForManualTriggers (cognitive 25), Scheduler.runJobWithCommand (cognitive 23), Checker.Check (cognitive 21). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 10 together lifts Cognitive Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
3 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 TooManyFields finding(s) in God Classes — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with main.go. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. 2.7 % of the production lines (145 of 5,289) are in a reported copy. A further 4 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (24 corresponding lines) finding(s) in Code Duplication — start with notify.go. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (18 corresponding lines) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copy of a member (21 corresponding lines) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
1 of 12 classes have LCOM4 above 3.
What to do
- Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D8 · Code Coverage
Line coverage 84.6% — 2 file(s) below 50%. Measured from the Go suite (github.com/umputun/cronn: `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. 8 line(s) in 2 file(s) were executed in some runs and not in others, so they are not counted.
What to do
- Resolve the 2 Low coverage finding(s) in Code Coverage — start with main.go (2). — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 Tests reach code only in some runs finding(s) in Code Coverage — start with jobs.go, REDACTED. — One of this dimension's main actionable groups (2 recommendation-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). Go (github.com/umputun/cronn): measured (0 flaky).
D12 · Dependency Hygiene
10 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 37 shipped Python distribution(s) use a banned license. Licences were resolved from PyPI over the distributions a consumer installs — this repository's 2 declared runtime requirement(s) closed transitively over each distribution's published `requires_dist` (35 reached that way). Requirements it states ONLY under an extra, a PEP 735 dependency group, a Poetry dev group or a dev-named requirements file are excluded: pip does not install any of them for a consumer. ★ This repository commits no dependency lockfile that this pass reads, so each licence is the one PyPI publishes for the distribution's CURRENT release rather than for a pinned version. 3 of them publish no licence on PyPI this pass can read; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Python distribution 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: REDACTED (3×17=51)
What to do
- Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D17 · Explicit Debt
0 deducted task-comment markers across 5289 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with main.go. — One of this dimension's main actionable groups (1 recommendation-level).
D22 · Internal API Consistency
0 API inconsistencies among 5 exposed members measured against a convention their peers follow.
D27 · Navigability
7 % of calls cross a namespace and 16 % go through an interface, but 74 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
38 finding(s): 0 critical, 28 high, 7 medium, 3 low. 19 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. semgrep hit a parse error in 3 file(s) — `app/web/templates/base.html` (line 1, line 11, line 12, …), `app/web/templates/login.html` (line 2, line 8, line 9, …), `app/web/templates/partials/neighbors.html` (lines 1–2, line 8, lines 10–13, …) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 19 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 (19 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low.
What to do
- Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 1 high, 3 medium, 1 low.
What to do
- Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 16 of the 24 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×2) — REDACTED:28, REDACTED:30
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — app/web/templates/login.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.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.search` sets color: #8b95a3 on background-color: #f6f7f9 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — docs/plans/completed/dashboard-redesign/gen/dash.css:18
- `.search` sets color: #6b7584 on background-color: #0b0e13 — 4.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — app/web/static/style.css:62
- `:where([data-keynav="false"]) :focus-visible` 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. — app/web/static/style.css:38
- `.search input` 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. — app/web/static/style.css:63
- `.spin` moves (`animation: spin .8s linear infinite`) 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. — app/web/static/style.css:241
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
AX4 · Dependency direction
AX6 · Interface segregation
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
- README.md names Go 1.25, but REDACTED:3 requires `go 1.26`: the code does not build on Go 1.25. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:651
What to do
- Reconcile the README with reality: README.md names Go 1.25, but REDACTED:3 requires `go 1.26`: the code does not build on Go 1.25.
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` schedules updates, but no `package-ecosystem` entry covers `github-actions`, `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entries to the `updates:` list. — REDACTED:7
What to do
- Dependabot is configured but does not watch `github-actions`, `pip` — add those `package-ecosystem` entries to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse. — REDACTED:63
- Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it. — REDACTED:63
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup
What to do
- Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
- No persistence guard on critical data stores — use Docker named volumes (or your orchestrator's persistent-volume equivalent) so the data store can't be wiped by a container recreate (or, in cloud, set purge-protection / soft-delete / prevent_destroy).
P6 · Release Hygiene
P7 · Outbound HTTP resilience
X2 · Cancellation propagation
- Only 0/1 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `fetchNeighborsHTTP` calls `http.NewRequestWithContext(…)` 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, …)`. — app/web/neighbors.go:122
What to do
- Thread a context.Context 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
- `if err != nil` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — app/main.go:290, REDACTED:458
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — app/web/static/ui.js:31
What to do
- Swallowed exception (caught, then discarded)
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 68.9 | Adequate | Acceptable, with room to improve. |
| Architecture | 81.4 | Strong | Strongest area. |
| Maturity | 65.1 | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 63.7 | Adequate | Acceptable, with room to improve. |
| Security | 61.5 | Checked 5 of 11 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 48.2 | Weak — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 2 check(s) recorded observations but carry no score
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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.
Not included — 63 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: this repository's 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.
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the app booted but exposed no published HTTP port — nothing to crawl (publish the web service's port to unlock runtime evidence) 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 — ~11684 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-maintainer 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.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1030 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, .py source were not judged.
- D25 ADR Conformance — no ADRs to check
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (5440 LoC, 63 module-visible types across 13 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- 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.
- D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 — applicable but not scored (1 of 2 signals for this style — below the bar we score at): 2 persistence-mapped domain entity/entities (gorm/bun/db/xorm-tagged)
- ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 event-sourced shape(s) (event folds / event-recording aggregates))
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 Go aggregate(s) recording domain events (own events-slice append / raise-record))
- 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
- 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 37 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.
- PF3 Async & latency hygiene — Not applicable: Go has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X12 Unreachable branch — X12 reached only 7% of this repository's production lines — go (5,068 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 — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — 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.
- X5 Nullable reference types — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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 — 31 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <label> that labels no control REDACTED:28
- <label> that labels no control REDACTED:30
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
Serious — 49 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Focus outline removed in CSS without a :focus replacement app/web/static/style.css:38
- Focus outline removed in CSS without a :focus replacement app/web/static/style.css:63
- Low coverage: app/crontab/internal/schema/main.go app/crontab/internal/schema/main.go:1
- Low coverage: app/main.go app/main.go:1
- Swallowed exception (caught, then discarded) app/main.go:290
- Swallowed exception (caught, then discarded) REDACTED:458
- Page without a main landmark app/web/templates/login.html:2
- Low contrast colour pair in CSS (2.8:1) docs/plans/completed/dashboard-redesign/gen/dash.css:18
- Low contrast colour pair in CSS (4.1:1) app/web/static/style.css:62
- Animation without a prefers-reduced-motion guard app/web/static/style.css:241
- Scheduler.runJobWithCommand (cyclomatic 17) REDACTED:203
- crontab.validateRequiredFields (cyclomatic 16) app/crontab/verify.go:43
- Hotspot: REDACTED REDACTED:203
- Scheduler.listenForManualTriggers (cognitive 25) REDACTED:479
- Scheduler.runJobWithCommand (cognitive 23) REDACTED:203
- Checker.Check (cognitive 21) app/conditions/conditions.go:79
- Parser.Changes (cognitive 21) app/crontab/crontab.go:186
- crontab.validateRequiredFields (cognitive 21) app/crontab/verify.go:43
- main.main (cognitive 20) app/main.go:107
- Server.sortJobs (cognitive 19) app/web/jobs.go:345
- Server.handleJobEvent (cognitive 18) app/web/jobs.go:238
- notify.NewService (cognitive 17) app/notify/notify.go:62
- Resumer.List (cognitive 16) app/resumer/resumer.go:65
- REDACTED
- REDACTED
- TooManyMethods: Server REDACTED:45
- TooManyFields: SettingsInfo REDACTED:187
- FunctionTooLong: main.main app/main.go:107
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Edited copy of a member (24 corresponding lines) app/notify/notify.go:143
- Edited copy of a member (18 corresponding lines) REDACTED:263
- Edited copy of a member (21 corresponding lines) REDACTED:206
- Edited copy of a member (6 corresponding lines) REDACTED:607
- Duplicated block (10 lines × 2) app/web/api.go:100
- Duplicated block (9 lines × 2) app/notify/notify.go:159
- Low cohesion: Server (LCOM4 6) REDACTED:45
- Coverage collected but not gated
- Function without context.Context: fetchNeighborsHTTP app/web/neighbors.go:122
- Swallowed exception (empty catch) app/web/static/ui.js:31
Minor — 18 finding(s)
- REDACTED
- REDACTED
- REDACTED
- Tests reach code only in some runs: app/web/jobs.go app/web/jobs.go:189
- Tests reach code only in some runs: REDACTED REDACTED:235
- No ADRs found app/main.go:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- README/code drift README.md:651
- Logging is not universal
- Dependabot does not watch github-actions/pip REDACTED:7
- No rollback/health safety REDACTED:63
- No release approval gate REDACTED:63
- Not all functions that make a request accept a context.Context
- Silent fallback default on error app/main.go:290
Minor — 10 finding(s)
- Outdated: github.com/go-pkgz/lgr
- Outdated: github.com/go-pkgz/notify
- Outdated: github.com/go-pkgz/rest
- Outdated: github.com/go-pkgz/routegroup
- Outdated: github.com/go-pkgz/syncs
- Outdated: github.com/mxschmitt/playwright-go
- Outdated: github.com/shirou/gopsutil/v4
- Outdated: github.com/stretchr/testify
- Outdated: golang.org/x/crypto
- Outdated: modernc.org/sqlite
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-ed4bbe82391944029b20bd538f455199/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=53" --report-format json --report-path /tmp/watchdog-gitleaks-ed4bbe82391944029b20bd538f455199/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-ed4bbe82391944029b20bd538f455199/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 --exclude app/notify/mocks --exclude app/service/mocks --exclude app/web/mocks --exclude vendor/modernc.org/libc/errno --exclude vendor/modernc.org/libc/fcntl --exclude vendor/modernc.org/libc/fts --exclude vendor/modernc.org/libc/grp --exclude vendor/modernc.org/libc/langinfo --exclude vendor/modernc.org/libc/limits --exclude vendor/modernc.org/libc/netdb --exclude vendor/modernc.org/libc/netinet --exclude vendor/modernc.org/libc/poll --exclude vendor/modernc.org/libc/pthread --exclude vendor/modernc.org/libc/pwd --exclude vendor/modernc.org/libc/stdio --exclude vendor/modernc.org/libc/stdlib --exclude vendor/modernc.org/libc/sys --exclude vendor/modernc.org/libc/termios --exclude vendor/modernc.org/libc/time --exclude vendor/modernc.org/libc/unistd --exclude vendor/modernc.org/libc/utime --exclude vendor/modernc.org/libc/uuid --exclude vendor/modernc.org/libc/wctype . | 38 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d0189eafd05f4b559c8b80520cad83a8 | 2 | artifacts/raw/osv-scanner.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| 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 | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . /tmp/codehealth-osv-sbom-d0189eafd05f4b559c8b80520cad83a8 | 0 | artifacts/raw/osv-scanner.json |