Executive summary
refinery/refinerycms falls short of our standard for production, held back most by its Security and Compliance lens, the code's security and compliance. It scores 47 out of 100 and is rated Weak, and nine of its 15 critical findings are security problems in the build pipeline and in its code.
Security and Compliance, at 39, is the weakest lens and counts most in the score. The best first step is naming the access rules, worth about 7 points. Fixing the security flaws the scanner found comes next, worth about 2 points. Raising Security and Compliance to 70 would lift the score to about 54.
Seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two weaknesses in the code could be used by an attacker. Pinning each tool to an exact version and fixing the weaknesses the scanner points to would close both risks. The three labels or groups of fields with no name need connecting to their fields or naming.
The product code is 6,358 lines, about €11,000 to rebuild.
If Security and Compliance rose from 39 to 70, the lowest score rated Strong, the score would rise from 47 to about 54.
New since the last survey: 7 findings
- Code Duplication · Edited copy of a member (17 corresponding lines) REDACTED
- Code Duplication · Edited copy of a member (8 corresponding lines) pages/db/migrate/20150720155305_update_slug_and_title_in_refinery_page_parts.rb
- Dependency Vulnerabilities · REDACTED
- Visual & motion safety · Low contrast colour pair in CSS (2.6:1) core/app/assets/stylesheets/refinery/sections/_layout.scss
- Visual & motion safety · Low contrast colour pair in CSS (2.7:1) core/app/assets/stylesheets/refinery/sections/_layout.scss
- Visual & motion safety · Low contrast colour pair in CSS (2.7:1) core/app/assets/stylesheets/refinery/sections/_layout.scss
- Visual & motion safety · Low contrast colour pair in CSS (1.9:1) core/app/assets/stylesheets/refinery/plugins/_ui.scss
Fixed since the last survey: 7 findings
- Dependency Hygiene · Floating git dependency: decorators
- Dependency Vulnerabilities · Medium vulnerability: [GHSA redacted] REDACTED
- Text alternatives · <img> without a text alternative core/app/assets/javascripts/refinery/admin.js.erb
- Text alternatives · <img> without a text alternative core/app/assets/javascripts/refinery/admin.js.erb
- Page structure · <iframe> without a title core/app/assets/javascripts/refinery/admin.js.erb
- Page structure · <iframe> without a title core/app/assets/javascripts/refinery/modal_dialogs.js.erb
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,700 to €19,000, for 62 to 197 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 47. 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: 6,358 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 — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 Refinery.Admin.ImagePresenter | 3 Refinery.Crud | 4 Refinery.ExtensionGeneration | 5 Refinery.Generators | 6 Refinery.Images.Validators | 7 Refinery.Page | 8 Refinery.PagesController | 9 Refinery.PagesController.Finders | 10 Refinery.Resources.Validators | 11 Refinery.Testing | 12 Refinery.Testing.ControllerMacros | 13 Refinery.Testing.FeatureMacros | 14 Refinery.ThumbnailDimensions | 15 WillPaginate | 16 WillPaginate.ActionView | 17 core.app.assets.javascripts.refinery | 18 Refinery.Core | 19 Refinery.Images | 20 Refinery.Pages | 21 Refinery.Resources | 22 Refinery.Admin | 23 Refinery.Pages.Finder | 24 Refinery.Pages.Url | 25 Refinery | 26 Refinery.Dragonfly | 27 Refinery.Pages.Admin |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||||||||
| 2 Refinery.Admin.ImagePresenter | |||||||||||||||||||||||||||
| 3 Refinery.Crud | |||||||||||||||||||||||||||
| 4 Refinery.ExtensionGeneration | |||||||||||||||||||||||||||
| 5 Refinery.Generators | |||||||||||||||||||||||||||
| 6 Refinery.Images.Validators | |||||||||||||||||||||||||||
| 7 Refinery.Page | |||||||||||||||||||||||||||
| 8 Refinery.PagesController | |||||||||||||||||||||||||||
| 9 Refinery.PagesController.Finders | |||||||||||||||||||||||||||
| 10 Refinery.Resources.Validators | |||||||||||||||||||||||||||
| 11 Refinery.Testing | |||||||||||||||||||||||||||
| 12 Refinery.Testing.ControllerMacros | |||||||||||||||||||||||||||
| 13 Refinery.Testing.FeatureMacros | |||||||||||||||||||||||||||
| 14 Refinery.ThumbnailDimensions | |||||||||||||||||||||||||||
| 15 WillPaginate | |||||||||||||||||||||||||||
| 16 WillPaginate.ActionView | |||||||||||||||||||||||||||
| 17 core.app.assets.javascripts.refinery | |||||||||||||||||||||||||||
| 18 Refinery.Core | 1 | ||||||||||||||||||||||||||
| 19 Refinery.Images | 1 | ||||||||||||||||||||||||||
| 20 Refinery.Pages | 1 | ||||||||||||||||||||||||||
| 21 Refinery.Resources | 1 | ||||||||||||||||||||||||||
| 22 Refinery.Admin | 1 | 12 | |||||||||||||||||||||||||
| 23 Refinery.Pages.Finder | 2 | ||||||||||||||||||||||||||
| 24 Refinery.Pages.Url | 3 | ||||||||||||||||||||||||||
| 25 Refinery | 1 | 1 | 4 | 1 | 1 | 1 | 1 | ||||||||||||||||||||
| 26 Refinery.Dragonfly | 1 | ||||||||||||||||||||||||||
| 27 Refinery.Pages.Admin | 1 | 1 | 3 |
18→25 Refinery.Core uses Refinery part of a loop✕
- Connections
- 1 pair of types, where a type in Refinery.Core uses a type in Refinery.
- The types involved
Refinery.Core.Engine→Refinery.Engine
- Direction
- Refinery.Core uses Refinery, so a change to Refinery can break Refinery.Core, while a change to Refinery.Core can't break Refinery.
- 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.
19→25 Refinery.Images uses Refinery part of a loop✕
- Connections
- 1 pair of types, where a type in Refinery.Images uses a type in Refinery.
- The types involved
Refinery.Images.Engine→Refinery.Engine
- Direction
- Refinery.Images uses Refinery, so a change to Refinery can break Refinery.Images, while a change to Refinery.Images can't break Refinery.
- 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.
20→25 Refinery.Pages uses Refinery part of a loop✕
- Connections
- 1 pair of types, where a type in Refinery.Pages uses a type in Refinery.
- The types involved
Refinery.Pages.Engine→Refinery.Engine
- Direction
- Refinery.Pages uses Refinery, so a change to Refinery can break Refinery.Pages, while a change to Refinery.Pages can't break Refinery.
- 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.
21→25 Refinery.Resources uses Refinery part of a loop✕
- Connections
- 1 pair of types, where a type in Refinery.Resources uses a type in Refinery.
- The types involved
Refinery.Resources.Engine→Refinery.Engine
- Direction
- Refinery.Resources uses Refinery, so a change to Refinery can break Refinery.Resources, while a change to Refinery.Resources can't break Refinery.
- 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.
22→20 Refinery.Admin uses Refinery.Pages✕
- Connections
- 1 pair of types, where a type in Refinery.Admin uses a type in Refinery.Pages.
- The types involved
Refinery.Admin.PagesController→Refinery.Pages.InstanceMethods
- Direction
- Refinery.Admin uses Refinery.Pages, so a change to Refinery.Pages can break Refinery.Admin, while a change to Refinery.Admin can't break Refinery.Pages.
- Position
- Below the diagonal: Refinery.Admin uses a module listed above it, which is the healthy direction.
22→25 Refinery.Admin uses Refinery part of a loop✕
- Connections
- 12 pairs of types, where a type in Refinery.Admin uses a type in Refinery.
- The types involved
Refinery.Admin.CoreController→Refinery.AdminControllerRefinery.Admin.DialogsController→Refinery.AdminControllerRefinery.Admin.ImagePresenter→Refinery.ActionHelperRefinery.Admin.ImagePresenter→Refinery.BasePresenterRefinery.Admin.ImagePresenter→Refinery.TranslationHelperRefinery.Admin.ImagesController→Refinery.AdminControllerRefinery.Admin.ImagesController→Refinery.ImageRefinery.Admin.PagePartsController→Refinery.AdminControllerRefinery.Admin.PagesController→Refinery.AdminControllerRefinery.Admin.PagesController→Refinery.PageRefinery.Admin.ResourcesController→Refinery.AdminControllerRefinery.Admin.ResourcesController→Refinery.Resource
- Direction
- Refinery.Admin uses Refinery, so a change to Refinery can break Refinery.Admin, while a change to Refinery.Admin can't break Refinery.
- 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.
23→20 Refinery.Pages.Finder uses Refinery.Pages✕
- Connections
- 2 pairs of types, where a type in Refinery.Pages.Finder uses a type in Refinery.Pages.
- The types involved
Refinery.Pages.Finder.FinderBySlug→Refinery.Pages.FinderRefinery.Pages.Finder.FinderByTitle→Refinery.Pages.Finder
- Direction
- Refinery.Pages.Finder uses Refinery.Pages, so a change to Refinery.Pages can break Refinery.Pages.Finder, while a change to Refinery.Pages.Finder can't break Refinery.Pages.
- Position
- Below the diagonal: Refinery.Pages.Finder uses a module listed above it, which is the healthy direction.
24→20 Refinery.Pages.Url uses Refinery.Pages✕
- Connections
- 3 pairs of types, where a type in Refinery.Pages.Url uses a type in Refinery.Pages.
- The types involved
Refinery.Pages.Url.Localised→Refinery.Pages.UrlRefinery.Pages.Url.Marketable→Refinery.Pages.UrlRefinery.Pages.Url.Normal→Refinery.Pages.Url
- Direction
- Refinery.Pages.Url uses Refinery.Pages, so a change to Refinery.Pages can break Refinery.Pages.Url, while a change to Refinery.Pages.Url can't break Refinery.Pages.
- Position
- Below the diagonal: Refinery.Pages.Url uses a module listed above it, which is the healthy direction.
25→5 Refinery uses Refinery.Generators✕
- Connections
- 1 pair of types, where a type in Refinery uses a type in Refinery.Generators.
- The types involved
Refinery.EngineGenerator→Refinery.Generators.NamedBase
- Direction
- Refinery uses Refinery.Generators, so a change to Refinery.Generators can break Refinery, while a change to Refinery can't break Refinery.Generators.
- Position
- Below the diagonal: Refinery uses a module listed above it, which is the healthy direction.
25→14 Refinery uses Refinery.ThumbnailDimensions✕
- Connections
- 1 pair of types, where a type in Refinery uses a type in Refinery.ThumbnailDimensions.
- The types involved
Refinery.ThumbnailDimensions→Refinery.ThumbnailDimensions.Geometry
- Direction
- Refinery uses Refinery.ThumbnailDimensions, so a change to Refinery.ThumbnailDimensions can break Refinery, while a change to Refinery can't break Refinery.ThumbnailDimensions.
- Position
- Below the diagonal: Refinery uses a module listed above it, which is the healthy direction.
25→18 Refinery uses Refinery.Core✕
- Connections
- 4 pairs of types, where a type in Refinery uses a type in Refinery.Core.
- The types involved
Refinery.Image→Refinery.Core.BaseModelRefinery.Page→Refinery.Core.BaseModelRefinery.PagePart→Refinery.Core.BaseModelRefinery.Resource→Refinery.Core.BaseModel
- Direction
- Refinery uses Refinery.Core, so a change to Refinery.Core can break Refinery, while a change to Refinery can't break Refinery.Core.
- Position
- Below the diagonal: Refinery uses a module listed above it, which is the healthy direction.
25→19 Refinery uses Refinery.Images✕
- Connections
- 1 pair of types, where a type in Refinery uses a type in Refinery.Images.
- The types involved
Refinery.Image→Refinery.Images.Validators
- Direction
- Refinery uses Refinery.Images, so a change to Refinery.Images can break Refinery, while a change to Refinery can't break Refinery.Images.
- Position
- Below the diagonal: Refinery uses a module listed above it, which is the healthy direction.
25→20 Refinery uses Refinery.Pages✕
- Connections
- 1 pair of types, where a type in Refinery uses a type in Refinery.Pages.
- The types involved
Refinery.PagesController→Refinery.Pages.RenderOptions
- Direction
- Refinery uses Refinery.Pages, so a change to Refinery.Pages can break Refinery, while a change to Refinery can't break Refinery.Pages.
- Position
- Below the diagonal: Refinery uses a module listed above it, which is the healthy direction.
25→21 Refinery uses Refinery.Resources✕
- Connections
- 1 pair of types, where a type in Refinery uses a type in Refinery.Resources.
- The types involved
Refinery.Resource→Refinery.Resources.Validators
- Direction
- Refinery uses Refinery.Resources, so a change to Refinery.Resources can break Refinery, while a change to Refinery can't break Refinery.Resources.
- Position
- Below the diagonal: Refinery uses a module listed above it, which is the healthy direction.
25→22 Refinery uses Refinery.Admin✕
- Connections
- 1 pair of types, where a type in Refinery uses a type in Refinery.Admin.
- The types involved
Refinery.AdminController→Refinery.Admin.BaseController
- Direction
- Refinery uses Refinery.Admin, so a change to Refinery.Admin can break Refinery, while a change to Refinery can't break Refinery.Admin.
- Position
- Below the diagonal: Refinery uses a module listed above it, which is the healthy direction.
26→25 Refinery.Dragonfly uses Refinery✕
- Connections
- 1 pair of types, where a type in Refinery.Dragonfly uses a type in Refinery.
- The types involved
Refinery.Dragonfly.Engine→Refinery.Engine
- Direction
- Refinery.Dragonfly uses Refinery, so a change to Refinery can break Refinery.Dragonfly, while a change to Refinery.Dragonfly can't break Refinery.
- Position
- Below the diagonal: Refinery.Dragonfly uses a module listed above it, which is the healthy direction.
27→20 Refinery.Pages.Admin uses Refinery.Pages✕
- Connections
- 1 pair of types, where a type in Refinery.Pages.Admin uses a type in Refinery.Pages.
- The types involved
Refinery.Pages.Admin.PreviewController→Refinery.Pages.RenderOptions
- Direction
- Refinery.Pages.Admin uses Refinery.Pages, so a change to Refinery.Pages can break Refinery.Pages.Admin, while a change to Refinery.Pages.Admin can't break Refinery.Pages.
- Position
- Below the diagonal: Refinery.Pages.Admin uses a module listed above it, which is the healthy direction.
27→22 Refinery.Pages.Admin uses Refinery.Admin✕
- Connections
- 1 pair of types, where a type in Refinery.Pages.Admin uses a type in Refinery.Admin.
- The types involved
Refinery.Pages.Admin.PreviewController→Refinery.Admin.BaseController
- Direction
- Refinery.Pages.Admin uses Refinery.Admin, so a change to Refinery.Admin can break Refinery.Pages.Admin, while a change to Refinery.Pages.Admin can't break Refinery.Admin.
- Position
- Below the diagonal: Refinery.Pages.Admin uses a module listed above it, which is the healthy direction.
27→25 Refinery.Pages.Admin uses Refinery✕
- Connections
- 3 pairs of types, where a type in Refinery.Pages.Admin uses a type in Refinery.
- The types involved
Refinery.Pages.Admin.PreviewController→Refinery.ApplicationControllerRefinery.Pages.Admin.PreviewController→Refinery.PageRefinery.Pages.Admin.PreviewController→Refinery.PagesController
- Direction
- Refinery.Pages.Admin uses Refinery, so a change to Refinery can break Refinery.Pages.Admin, while a change to Refinery.Pages.Admin can't break Refinery.
- Position
- Below the diagonal: Refinery.Pages.Admin 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 — Domain Modelling
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 20 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 9 | Medium |
Roadmap
Top priorities: Name the access rules — Pundit or Action Policy classes (a PostPolicy), a CanCanCan Ability, or rolify roles — and consult them where access is checked (authorize @record, load_and_authorize_resource, authorize!), so the rule set is reviewable and testable on its own; Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Name the access rules — Pundit or Action Policy classes (a PostPolicy), a CanCanCan Ability, or rolify roles — and consult them where access is checked (authorize @record, load_and_authorize_resource, authorize!), so the rule set is reviewable and testable on its own. | +7.2 pts | Medium | Access Controls |
| Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). | +2.2 pts | Low | Static Analysis (SAST) |
| Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. | +1.9 pts | Low | Supply-chain Provenance & Signing |
| Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up. | +2.7 pts | Medium | Type Safety |
| Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). | +1.3 pts | Low | Static Analysis (SAST) |
| Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive. | +2.3 pts | Medium | Nullable reference types |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.9 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. | +0.9 pts | Low | Supply-chain Provenance & Signing |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 3.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.0 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 5.1 | Mixed | Static Analysis (SAST): High: REDACTED |
| core/app/assets/javascripts/refinery/sortable_list.js | 7.4 | Mixed | Cyclomatic Complexity: create_sortable_list (cyclomatic 16) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| pages/lib/refinery/pages/admin/instance_methods.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/lib/refinery/plugins.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/lib/refinery/admin/base_controller.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| core/app/helpers/refinery/admin_helper.rb | 8.2 | Near-clean | Explicit Debt: TodoComment |
| pages/app/controllers/refinery/admin/pages_controller.rb | 8.5 | Near-clean | Cognitive Complexity: PagesController.update (cognitive 17) |
| pages/app/controllers/refinery/admin/pages_dialogs_controller.rb | 8.5 | Near-clean | Cognitive Complexity: PagesDialogsController.link_to (cognitive 16) |
| core/lib/refinery/extension_generation.rb | 8.5 | Near-clean | God Classes: TooManyMethods: ExtensionGeneration |
| dragonfly/lib/refinery/dragonfly/extension_configuration.rb | 8.5 | Near-clean | God Classes: TooManyMethods: ExtensionConfiguration |
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 64 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 64 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, 87 of 104 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.rb) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
- D11 Test Reliability — 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. Test source is present (.rb) and this repository declares a Ruby test suite (RSpec: 5 bundle roots), but it was not re-run: no test result was produced. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
- 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. All 28 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 16 of the 157 production source files in this repository: 129 are under the ~2,400-byte size floor this dimension measures over, and the remaining 12 have no attributable history left to measure.
- D19 Documentation Quality — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- 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.
- AC1 Text alternatives — 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 renders user interface from a TEMPLATE LANGUAGE — 2 Rails (ERB) template file(s) carrying 56 markup element(s) (e.g. resources/app/views/refinery/admin/resources/_existing_resource.html.erb, pages/app/views/refinery/admin/pages_dialogs/link_to.html.erb) — and the accessibility cards on this run were measured over the 67 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC2 Forms & labels — 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 renders user interface from a TEMPLATE LANGUAGE — 2 Rails (ERB) template file(s) carrying 56 markup element(s) (e.g. resources/app/views/refinery/admin/resources/_existing_resource.html.erb, pages/app/views/refinery/admin/pages_dialogs/link_to.html.erb) — and the accessibility cards on this run were measured over the 67 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC3 Page structure — 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 renders user interface from a TEMPLATE LANGUAGE — 2 Rails (ERB) template file(s) carrying 56 markup element(s) (e.g. resources/app/views/refinery/admin/resources/_existing_resource.html.erb, pages/app/views/refinery/admin/pages_dialogs/link_to.html.erb) — and the accessibility cards on this run were measured over the 67 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC4 Keyboard semantics — 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 repository renders user interface from a TEMPLATE LANGUAGE — 2 Rails (ERB) template file(s) carrying 56 markup element(s) (e.g. resources/app/views/refinery/admin/resources/_existing_resource.html.erb, pages/app/views/refinery/admin/pages_dialogs/link_to.html.erb) — and the accessibility cards on this run were measured over the 67 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC5 ARIA correctness — 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 renders user interface from a TEMPLATE LANGUAGE — 2 Rails (ERB) template file(s) carrying 56 markup element(s) (e.g. resources/app/views/refinery/admin/resources/_existing_resource.html.erb, pages/app/views/refinery/admin/pages_dialogs/link_to.html.erb) — and the accessibility cards on this run were measured over the 67 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AC6 Visual & motion safety — 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 renders user interface from a TEMPLATE LANGUAGE — 2 Rails (ERB) template file(s) carrying 56 markup element(s) (e.g. resources/app/views/refinery/admin/resources/_existing_resource.html.erb, pages/app/views/refinery/admin/pages_dialogs/link_to.html.erb) — and the accessibility cards on this run were measured over the 67 parsed markup document(s) ONLY. The markup model reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs; the file(s) above were REFUSED rather than unsupported — a template whose element NAME comes from an expression, or an Astro component whose frontmatter fence is never closed, leaves the element's identity unknown, and every accessibility rule is a statement about a NAMED element — so those views were not merely unparsed but unenumerated: not one of their elements entered the population any card scored. Their absence from the counts above is a gap in this analyzer's frontend coverage — not a finding that they carry text alternatives, labels, keyboard semantics or correct ARIA.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 67 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P7 Outbound HTTP resilience — 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 recognises outbound HTTP clients, their timeouts and resilience policies, and service entry points in .NET, Go, JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang. The JavaScript/TypeScript, Ruby source it reads makes no outbound call, and the rest of this repository's production source is , which it does not read yet — the calls may well be there — a gap in this analyzer's language reach, not a finding about the code.
- 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. 156 Ruby file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a REDACTED 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.
- AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
- 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.
- DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
3 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was _mouseDrag at 60. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being sortable_list.create_sortable_list at 16 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: core/app/assets/javascripts/refinery/sortable_list.js (sortable_list.create_sortable_list at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with _mouseDrag (cyclomatic 60). — Refactoring it lifts Cyclomatic Complexity from 8.3 to about 9.0/10.
D2 · Cognitive Complexity
8 method(s) exceeded the cognitive complexity threshold of 15; the worst was _mouseDrag at 90.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with _mouseDrag (cognitive 90). — Refactoring it lifts Cognitive Complexity from 7.5 to about 8.6/10.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 3 TooManyMethods finding(s) in God Classes — start with extension_generation.rb, extension_configuration.rb, page.rb. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 FunctionTooLong finding(s) in God Classes — start with sortable_list.js. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
2 duplicated block group(s) detected. 1.0 % of the production lines (62 of 6,358) are in a reported copy. A further 2 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
What to do
- Resolve the 1 Edited copy of a member (17 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 (8 corresponding lines) finding(s) in Code Duplication — start with 20150720155305_update_slug_and_title_in_refinery_page_parts.rb. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
7 production modules (RubyGems), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.
D6 · Cohesion (LCOM4)
2 of 20 classes have LCOM4 above 3.
What to do
- Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with preview_controller.rb, admin_controller.rb. — One of this dimension's main actionable groups (2 warning-level).
D7 · Architectural Integrity
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
D12 · Dependency Hygiene
0 outdated direct gem(s), 4 pinning defect(s). 77 declaration(s) graded against rubygems.org, none of them against a committed REDACTED.lock — this repository commits none, which a published gem correctly does not, so currency is read off the declared requirements: a declaration that does not cap below the current release resolves to it on `bundle install`. 11 declaration(s) carry a requirement that EXCLUDES the current release; that is a deliberate constraint (a supported-version ceiling or a held-back CI pin) and is counted, not charged. 77 of 79 gradable declaration(s) were graded against rubygems.org (0 not published there, 2 carrying a version or requirement this pass cannot order). Whether any of these gems is DEPRECATED or YANKED is not graded — rubygems.org publishes no deprecation marker, and a yank removes a version rather than flagging it. Whether any is UNMAINTAINED is not graded either: no registry publishes a maintenance status, and release age does not stand in for one. Whether any is UNUSED is a source question, not a registry one. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 4 Floating git dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (4 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 45 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 45 runtime gem(s) this repository declares. It commits no REDACTED.lock to close that set over, so the verdict covers the declarations rather than the whole resolved graph. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. 2 of them publish no licence on rubygems.org; that is missing data, not a violation, and none of them is charged. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
4 deducted task-comment markers across 6358 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with instance_methods.rb, plugins.rb, base_controller.rb. — One of this dimension's main actionable groups (4 warning-level).
D20 · ADR Quality
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (4 contexts). Contexts: core, images, pages, resources.
D26 · Project Cohesion
0 of 7 build units (Bundler, RubyGems) flagged as possibly oversized/incoherent.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
21 finding(s): 0 critical, 9 high, 12 medium, 0 low. 7 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 48 file(s) — `core/config/locales/cs.yml`, `core/config/locales/da.yml`, `core/config/locales/de.yml`, `core/config/locales/hu.yml`, `core/config/locales/ko.yml`, … (+43 more) — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
What to do
- Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- No action in Static Analysis (SAST) — all 7 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 (7 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
2 finding(s): 0 critical, 0 high, 2 medium, 0 low. 4 known-vulnerable gem advisory(ies) across 56 declared gem(s). This repository commits no REDACTED.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 79 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over. 1 declaration(s) could not be resolved to a published release — an unreadable requirement, or one no release satisfies — and are not covered by this verdict.
What to do
- Resolve the 2 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
D34 · Knowledge Freshness
8 of 28 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is dragonfly/lib/refinery/dragonfly/extension_configuration.rb. Counted over 28 of the 157 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 8 Orphaned file finding(s) in Knowledge Freshness — start with extension_configuration.rb, image_presenter.rb, REDACTED. — One of this dimension's main actionable groups (8 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — 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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious. 4 known-vulnerable gem advisory(ies) across 56 declared gem(s). This repository commits no REDACTED.lock — which a published gem correctly does not — so osv-scanner had no resolved graph to read, and the question was put to osv.dev instead over the releases `bundle install` resolves this repository's 79 declared requirement(s) to. The verdict therefore covers the DIRECT declarations at their resolved releases, not the transitive graph a lock would close over. 1 declaration(s) could not be resolved to a published release — an unreadable requirement, or one no release satisfies — and are not covered by this verdict.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 79 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
AC1 · Text alternatives
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. (×3) — core/app/views/refinery/admin/_locale_picker.html.erb:3, images/app/views/refinery/admin/images/_form.html.erb:26, images/app/views/refinery/admin/images/_form.html.erb:65
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
- The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×3) — core/public/404.html:2, core/public/422.html:2, core/public/500.html:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×3) — core/public/404.html:2, core/public/422.html:2, core/public/500.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
- `&.active, &:hover, &:focus` sets color: white on background-color: rgba(37, 169, 244, 1) — 2.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — core/app/assets/stylesheets/refinery/sections/_layout.scss:525
- `a` sets color: white on background-color: #22A7F2 — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — core/app/assets/stylesheets/refinery/sections/_layout.scss:1076
- `input.button, a.button, #content a.button, span.button-wrapper, span.button-wrapper input` sets color: white on background-color: #22a7f2 — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — core/app/assets/stylesheets/refinery/sections/_layout.scss:1509
- `.ui-tabs .ui-state-default a` sets color: white on background-color: #bcbcbc — 1.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — core/app/assets/stylesheets/refinery/plugins/_ui.scss:100
- `a:focus` 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. (×2) — core/app/assets/stylesheets/refinery/formatting.scss:31, core/app/assets/stylesheets/refinery/sections/_layout.scss:1259
- `.ui-dialog[aria-describedby=editor_dialog] .ui-dialog-titlebar .ui-dialog-titlebar-close` 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. (×2) — core/app/assets/stylesheets/refinery/plugins/_ui.scss:228, core/app/assets/stylesheets/refinery/components/_dialog.scss:187
- `.ui-dialog[aria-describedby=editor_dialog]` 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. (×2) — core/app/assets/stylesheets/refinery/plugins/_ui.scss:192, core/app/assets/stylesheets/refinery/components/_dialog.scss:158
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
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
- Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
- Name the access rules — Pundit or Action Policy classes (a PostPolicy), a CanCanCan Ability, or rolify roles — and consult them where access is checked (authorize @record, load_and_authorize_resource, authorize!), so the rule set is reviewable and testable on its own.
- Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
DM6 · Domain ↔ infrastructure boundary
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
M2 · Architecture documentation
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
- A CI pipeline exists but no build step was matched — changes may merge without the build ever running. A build step may be invoked directly as a command, or declared as a task that a runner named in the pipeline resolves.
What to do
- Add an explicit build step to your CI pipeline — your stack's own build command, or, if the pipeline delegates to a task runner, a build task that runner executes in CI — so every change is built before merge.
P10 · Library API & versioning
P2 · Observability
- Only 3/4 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 (Rails' /up (rails/health#show) or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:7
What to do
- Add a SAST step to CI running what this repository's stack ships: brakeman for Rails apps, otherwise `semgrep --config=auto` or CodeQL's ruby pack — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
- Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
P6 · Release Hygiene
P8 · Schema migrations
R1 · Type Safety
- 0 typed · 13 plain JS — the untyped files are core/app/assets/config/refinery_core_manifest.js, core/app/assets/javascripts/admin.js, core/app/assets/javascripts/application.js, core/app/assets/javascripts/refinery/ajaxy_pagination.js, core/app/assets/javascripts/refinery/application.js, core/app/assets/javascripts/refinery/image_crop.js (+7 more).
What to do
- Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication
- REDACTED:145 · REDACTED:158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:145
- core/app/assets/javascripts/refinery/sortable_list.js:102 · core/app/assets/javascripts/refinery/sortable_list.js:129 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — core/app/assets/javascripts/refinery/sortable_list.js:102
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R2 · Cyclomatic Complexity
- _mouseDrag has cyclomatic complexity 60 and cognitive complexity 90; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:47
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:249
- _isAllowed has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:398
R3 · Large Files
R7 · Dead Code
- Unreachable from the 11 application, 0 tooling and 1 test entry point(s) detected in this repo. This repository declares no build, type-check or test script, so nothing here would fail on a wrong deletion — confirm by hand that nothing loads each file (including by a path built at runtime) before removing it. An undetected custom entry would make these reachable.
- no import path from any entry point (11 application, 0 tooling, 1 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — core/lib/generators/refinery/dummy/templates/rails/application.js, core/lib/generators/refinery/dummy/templates/rails/manifest.js
R9 · Circular Imports
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
- `newCrop` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — core/app/assets/javascripts/refinery/image_crop.js:74
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X3 · Exception handling
- `… rescue {}` 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. — core/app/helpers/refinery/image_helper.rb:29
What to do
- Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 156 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
- Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC1 · Text alternatives | 1.1.1, 1.2.2, 1.2.5 | Partial signal |
| 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 | 45% | Weak — gated by R1, X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 93% | Exemplary | Solid. |
| Maturity | 83% | Strong | Solid. |
| Readiness | 54% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 39% | Weak — gated by D29, D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Accessibility | 53% | Adequate — gated by AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase
- AC4 Keyboard semantics — AC4 could not be measured here. This repository renders user interface from a template language — 2 Rails (ERB) template file(s) carrying 56 markup element(s) (e.g. resources/app/views/refinery/admin/resources/_existing_resource.html.erb, pages/app/views/refinery/admin/pages_dialogs/link_to.html.erb) — which this analyzer's markup model does not read (it reads .html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx, html`…` templates and DOM-assigned HTML strings in .ts/.js, the .erb/.ejs/.eex/.heex/.leex/.twig/.jinja/.j2/.liquid/.njk/.hbs/.mustache/.blade.php/.gohtml template languages, .astro/.templ/.pug/.jade/.haml/.slim, and the kotlinx.html/Compose HTML/kotlin-react, Giraffe/Falco/Fable.React/Feliz/Bolero and Jaspr builder DSLs), so no interactive element from it could enter the population. The parsed markup carried none either, but that is a gap in our frontend coverage, NOT a statement that this repository has no interactive element.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Ruby 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no data at rest for these controls to protect.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (an ActiveRecord model, Sequel, pg, mysql2, Mongo) in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, db/schema.rb or a Mongoid document — and no database client (ActiveRecord, Sequel, pg, mysql2, mongo, …) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in an ActiveRecord or Sequel migration, a db/schema.rb table or a Mongoid document — and no database or data-store client (an ActiveRecord model, Sequel, pg, mysql2, sqlite3, Mongo, …) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
- D10 Test Quality — ~6006 lines of test source are present (.rb) 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.
- D11 Test Reliability — Test reliability not included — the .rb suite was found but not re-run
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D19 Documentation Quality — D19 withholds "Documentation: empty section": 1 candidate(s) were measured and not published.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (1048 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed Ruby surface was not measured.
- D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .rb source were not judged.
- D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D8 Code Coverage — Coverage not included — suite not readable by the collector
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — not 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
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `x.report(…)` entries in a `Benchmark.ips`/`bm`/`bmbm`/`benchmark`/`memory` block, `benchmark:` entries in a benchmark-driver YAML under a bench* directory, rspec-benchmark `perform_*` expectations where the gem is installed, or benchmark-ips, benchmark-memory, rspec-benchmark or benchmark-driver in a REDACTED or gemspec, 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: Ruby has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 1 test file(s) reach none of 13 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- R6 Tooling — no package.json in the repository — test/lint/typecheck wiring is read from package.json scripts (corroborated against CI), so this project's own toolchain isn't measured here
- R8 Dependency Hygiene — Not measured — no package.json declares any dependency, so there is nothing to check imports against (imports may resolve through a host runtime rather than node).
- S1 Web-Security Posture — Not assessed: 156 Ruby file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for Ruby: this reading covers the code's own cryptography and the TLS connections it opens as a client, and a Rails, Rack or Sinatra application's transport, header and validation settings are not modelled. Their absence here is not a finding about this repository.
- 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
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — no C# was loaded; this repository's Ruby was read, and no request in it can be cancelled by a caller — a Ruby request takes no token: Net::HTTP, Faraday and async-http are stopped from outside the call (Async::Task#stop, Thread#raise, Timeout), not through a parameter
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X27 Collection changed while being enumerated — not 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
- 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 Ruby was read, and it logs through none: the standard library's Logger, which Rails.logger is, takes one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. The console gem (`Console.info`), SemanticLogger, Ougai and dry-logger would be judged.
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 15 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <label> that labels no control core/app/views/refinery/admin/_locale_picker.html.erb:3
- <label> that labels no control images/app/views/refinery/admin/images/_form.html.erb:26
- <label> that labels no control images/app/views/refinery/admin/images/_form.html.erb:65
- <html> without a lang core/public/404.html:2
- <html> without a lang core/public/422.html:2
- <html> without a lang core/public/500.html:2
- REDACTED
- REDACTED
Serious — 68 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Focus outline removed in CSS without a :focus replacement core/app/assets/stylesheets/refinery/formatting.scss:31
- Focus outline removed in CSS without a :focus replacement core/app/assets/stylesheets/refinery/sections/_layout.scss:1259
- Focus outline removed in CSS without a :focus replacement core/app/assets/stylesheets/refinery/plugins/_ui.scss:228
- Focus outline removed in CSS without a :focus replacement core/app/assets/stylesheets/refinery/plugins/_ui.scss:192
- Focus outline removed in CSS without a :focus replacement core/app/assets/stylesheets/refinery/components/_dialog.scss:187
- Focus outline removed in CSS without a :focus replacement core/app/assets/stylesheets/refinery/components/_dialog.scss:158
- Floating git dependency: refinerycms-i18n
- Floating git dependency: refinerycms-acts-as-indexed
- Floating git dependency: refinerycms
- Floating git dependency: refinerycms-testing
- TodoComment pages/lib/refinery/pages/admin/instance_methods.rb:11
- TodoComment core/lib/refinery/plugins.rb:23
- TodoComment core/lib/refinery/admin/base_controller.rb:76
- TodoComment core/app/helpers/refinery/admin_helper.rb:5
- Page without a main landmark core/public/404.html:2
- Page without a main landmark core/public/422.html:2
- Page without a main landmark core/public/500.html:2
- TooManyMethods: ExtensionGeneration core/lib/refinery/extension_generation.rb:2
- TooManyMethods: ExtensionConfiguration dragonfly/lib/refinery/dragonfly/extension_configuration.rb:3
- TooManyMethods: Page pages/app/models/refinery/page.rb:9
- Low contrast colour pair in CSS (2.7:1) core/app/assets/stylesheets/refinery/sections/_layout.scss:1076
- Low contrast colour pair in CSS (2.7:1) core/app/assets/stylesheets/refinery/sections/_layout.scss:1509
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low cohesion: PreviewController (LCOM4 9) pages/app/controllers/refinery/pages/admin/preview_controller.rb:4
- Low cohesion: AdminController (LCOM4 7) core/app/controllers/refinery/admin_controller.rb:4
- Dead file (~0 LoC) core/lib/generators/refinery/dummy/templates/rails/application.js
- Dead file (~0 LoC) core/lib/generators/refinery/dummy/templates/rails/manifest.js
- Low contrast colour pair in CSS (2.6:1) core/app/assets/stylesheets/refinery/sections/_layout.scss:525
- Low contrast colour pair in CSS (1.9:1) core/app/assets/stylesheets/refinery/plugins/_ui.scss:100
- _mouseDrag (cyclomatic 60) REDACTED:47
- serialize (cyclomatic 19) REDACTED:243
- create_sortable_list (cyclomatic 16) core/app/assets/javascripts/refinery/sortable_list.js:1
- _mouseDrag (cognitive 90) REDACTED:47
- create_sortable_list (cognitive 22) core/app/assets/javascripts/refinery/sortable_list.js:1
- ImagesController.create (cognitive 19) REDACTED:45
- ImagesController.update (cognitive 18) REDACTED:87
- _isAllowed (cognitive 18) REDACTED:398
- PagesController.update (cognitive 17) pages/app/controllers/refinery/admin/pages_controller.rb:25
- serialize (cognitive 17) REDACTED:243
- PagesDialogsController.link_to (cognitive 16) pages/app/controllers/refinery/admin/pages_dialogs_controller.rb:7
- FunctionTooLong: sortable_list.create_sortable_list core/app/assets/javascripts/refinery/sortable_list.js:1
- REDACTED
- Edited copy of a member (17 corresponding lines) REDACTED:26
- Edited copy of a member (8 corresponding lines) pages/db/migrate/20150720155305_update_slug_and_title_in_refinery_page_parts.rb:3
- Duplicated block (7 lines × 2) REDACTED:29
- Duplicated block (13 lines × 2) images/lib/refinery/images.rb:16
- Type Safety
- Duplicated block (10 lines × 2 locations) REDACTED:145
- Duplicated block with local edits (5 matched lines × 2 locations) core/app/assets/javascripts/refinery/sortable_list.js:102
- Complex function _mouseDrag (cyclomatic 60, cognitive 90) REDACTED:47
- Complex function (anonymous) (cyclomatic 16, cognitive 14) REDACTED:249
- Complex function _isAllowed (cyclomatic 14, cognitive 18) REDACTED:398
- Untrusted text written into markup unescaped core/app/assets/javascripts/refinery/image_crop.js:74
- Swallowed exception (caught, then discarded) core/app/helpers/refinery/image_helper.rb:29
Minor — 21 finding(s)
- Orphaned file dragonfly/lib/refinery/dragonfly/extension_configuration.rb:1
- Orphaned file images/app/presenters/refinery/admin/image_presenter.rb:1
- Orphaned file REDACTED:1
- Orphaned file dragonfly/lib/refinery/dragonfly/dragonfly.rb:1
- Orphaned file dragonfly/lib/refinery/dragonfly/configuration.rb:1
- Orphaned file pages/app/presenters/refinery/pages/section_presenter.rb:1
- Orphaned file images/app/presenters/refinery/admin/group_presenter.rb:1
- Orphaned file images/app/models/refinery/thumbnail_dimensions.rb:1
- No named authorization policies
- Thin authorization enforcement
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- CI build step not evidenced
- Logging is not universal
- No SAST REDACTED:7
- No release approval gate
- Duplicated predicate images/app/models/refinery/image.rb:77
- Ruby's type checker does not check nil everywhere
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-16542fd89f454e8b813afd0bb3bb1d52/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-16542fd89f454e8b813afd0bb3bb1d52/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 . | 21 | artifacts/raw/semgrep.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |