Executive summary
bluzky/salad_ui falls short of our standard for production because we found no access checks on the code's endpoints or handlers and nine of the dependencies have a known vulnerability. It scores 50 out of 100 and is rated Weak, and 17 of its 19 critical findings are security problems.
Security and Compliance, at 46, is the weakest lens, level with Production Readiness, and counts most in the score. The best first step is adding access checks, worth about 4 points. Adding text alternatives comes next, worth about 2 points.
Nine known security holes in the packages the code depends on can be used by attackers. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and two settings leave the servers or containers unsafe. Updating the vulnerable packages, pinning each tool to an exact version and correcting the unsafe settings would close these risks. The image with no text description needs a text description.
The product code is 16,466 lines, about €18,000 to rebuild.
The weakest lenses score close to each other, so improving any of them moves the score.
New since the last survey: 16 findings
- Code Duplication · Edited copy of a member (15 corresponding lines) storybook/storybook/salad_ui_component/chart.story.exs
- Code Duplication · Edited copies of one member (4 members, 15+ corresponding lines) lib/salad_ui/alert_dialog.ex
- Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) storybook/storybook/salad_ui_component/card.story.exs
- Code Duplication · Edited copy of a member (15 corresponding lines) lib/salad_ui/hover_card.ex
- Code Duplication · Edited copy of a member (109 corresponding lines) storybook/storybook/salad_ui_component/dropdown_menu.story.exs
- Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) lib/salad_ui/helpers.ex
- Code Duplication · Edited copy of a member (7 corresponding lines) lib/salad_ui/checkbox.ex
- Code Duplication · Edited copy of a member (10 corresponding lines) lib/mix/tasks/salad.install.ex
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 11 findings
- Test Reliability · Flaky test: assets/::add creates a visible card with title/description
- Secret Scanning · Leaked secret: high-entropy-secret storybook/config/test.exs
- Secret Scanning · Leaked secret: signing-key storybook/config/test.exs
- Secret Scanning · Leaked secret: high-entropy-secret storybook/config/dev.exs
- Secret Scanning · Leaked secret: signing-key storybook/config/dev.exs
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: EEF-[CVE redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Change Coupling · Change coupling: collapsible.ex ↔ sidebar.ex lib/salad_ui/collapsible.ex
- A11y enforcement · Accessibility enforcement below the top rung
Rebuild cost: about €18,000 · Estimate
| Cost to rebuild | €6,100 to €31,000, for 102 to 323 hours of work, about 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 50. 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: 16,466 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 (global) | 2 Jason.Encoder.Phoenix.LiveView | 3 Mix.Tasks.Salad | 4 SaladStorybook | 5 SaladStorybook.Helpers | 6 SaladUI.Mix.Tasks | 7 SaladUI.Patcher | 8 Storybook | 9 Storybook.SaladUIComponents | 10 assets | 11 assets.salad_ui.components | 12 assets.salad_ui.core | 13 assets.salad_ui.core.click-outside | 14 assets.salad_ui.core.collection | 15 assets.salad_ui.core.component | 16 assets.salad_ui.core.factory | 17 assets.salad_ui.core.focus-trap | 18 assets.salad_ui.core.portal | 19 assets.salad_ui.core.positioned-element | 20 assets.salad_ui.core.positioner | 21 assets.salad_ui.core.scroll-manager | 22 SaladStorybookWeb | 23 SaladUI | 24 assets.salad_ui.components.accordion | 25 assets.salad_ui.components.chart | 26 assets.salad_ui.components.collapsible | 27 assets.salad_ui.components.command | 28 assets.salad_ui.components.dialog | 29 assets.salad_ui.components.dropdown_menu | 30 assets.salad_ui.components.hover-card | 31 assets.salad_ui.components.menu | 32 assets.salad_ui.components.popover | 33 assets.salad_ui.components.radio_group | 34 assets.salad_ui.components.select | 35 assets.salad_ui.components.slider | 36 assets.salad_ui.components.switch | 37 assets.salad_ui.components.tabs | 38 assets.salad_ui.components.toast | 39 assets.salad_ui.components.toast-flash | 40 assets.salad_ui.components.tooltip |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | ||||||||||||||||||||||||||||||||||||||||
| 2 Jason.Encoder.Phoenix.LiveView | ||||||||||||||||||||||||||||||||||||||||
| 3 Mix.Tasks.Salad | ||||||||||||||||||||||||||||||||||||||||
| 4 SaladStorybook | ||||||||||||||||||||||||||||||||||||||||
| 5 SaladStorybook.Helpers | ||||||||||||||||||||||||||||||||||||||||
| 6 SaladUI.Mix.Tasks | ||||||||||||||||||||||||||||||||||||||||
| 7 SaladUI.Patcher | ||||||||||||||||||||||||||||||||||||||||
| 8 Storybook | ||||||||||||||||||||||||||||||||||||||||
| 9 Storybook.SaladUIComponents | ||||||||||||||||||||||||||||||||||||||||
| 10 assets | ||||||||||||||||||||||||||||||||||||||||
| 11 assets.salad_ui.components | ||||||||||||||||||||||||||||||||||||||||
| 12 assets.salad_ui.core | ||||||||||||||||||||||||||||||||||||||||
| 13 assets.salad_ui.core.click-outside | ||||||||||||||||||||||||||||||||||||||||
| 14 assets.salad_ui.core.collection | ||||||||||||||||||||||||||||||||||||||||
| 15 assets.salad_ui.core.component | ||||||||||||||||||||||||||||||||||||||||
| 16 assets.salad_ui.core.factory | ||||||||||||||||||||||||||||||||||||||||
| 17 assets.salad_ui.core.focus-trap | ||||||||||||||||||||||||||||||||||||||||
| 18 assets.salad_ui.core.portal | ||||||||||||||||||||||||||||||||||||||||
| 19 assets.salad_ui.core.positioned-element | ||||||||||||||||||||||||||||||||||||||||
| 20 assets.salad_ui.core.positioner | ||||||||||||||||||||||||||||||||||||||||
| 21 assets.salad_ui.core.scroll-manager | ||||||||||||||||||||||||||||||||||||||||
| 22 SaladStorybookWeb | 5 | |||||||||||||||||||||||||||||||||||||||
| 23 SaladUI | 39 | |||||||||||||||||||||||||||||||||||||||
| 24 assets.salad_ui.components.accordion | 2 | |||||||||||||||||||||||||||||||||||||||
| 25 assets.salad_ui.components.chart | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 assets.salad_ui.components.collapsible | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 assets.salad_ui.components.command | 1 | |||||||||||||||||||||||||||||||||||||||
| 28 assets.salad_ui.components.dialog | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 assets.salad_ui.components.dropdown_menu | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 assets.salad_ui.components.hover-card | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 assets.salad_ui.components.menu | 2 | |||||||||||||||||||||||||||||||||||||||
| 32 assets.salad_ui.components.popover | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 assets.salad_ui.components.radio_group | 1 | |||||||||||||||||||||||||||||||||||||||
| 34 assets.salad_ui.components.select | 2 | |||||||||||||||||||||||||||||||||||||||
| 35 assets.salad_ui.components.slider | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 assets.salad_ui.components.switch | 1 | |||||||||||||||||||||||||||||||||||||||
| 37 assets.salad_ui.components.tabs | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 assets.salad_ui.components.toast | 1 | |||||||||||||||||||||||||||||||||||||||
| 39 assets.salad_ui.components.toast-flash | 1 | |||||||||||||||||||||||||||||||||||||||
| 40 assets.salad_ui.components.tooltip | 1 |
22→1 SaladStorybookWeb uses (global)✕
- Connections
- 5 pairs of types, where a type in SaladStorybookWeb uses a type in (global).
- The types involved
SaladStorybookWeb.ErrorHTML→SaladStorybookWebSaladStorybookWeb.Layouts→SaladStorybookWebSaladStorybookWeb.PageController→SaladStorybookWebSaladStorybookWeb.PageHTML→SaladStorybookWebSaladStorybookWeb.Router→SaladStorybookWeb
- Direction
- SaladStorybookWeb uses (global), so a change to (global) can break SaladStorybookWeb, while a change to SaladStorybookWeb can't break (global).
- Position
- Below the diagonal: SaladStorybookWeb uses a module listed above it, which is the healthy direction.
23→1 SaladUI uses (global)✕
- Connections
- 39 pairs of types, where a type in SaladUI uses a type in (global). Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
- The types involved
SaladUI.Accordion→SaladUISaladUI.Alert→SaladUISaladUI.AlertDialog→SaladUISaladUI.Avatar→SaladUISaladUI.Badge→SaladUISaladUI.Breadcrumb→SaladUISaladUI.Button→SaladUISaladUI.Card→SaladUISaladUI.Chart→SaladUISaladUI.Checkbox→SaladUISaladUI.Collapsible→SaladUISaladUI.Command→SaladUISaladUI.Dialog→SaladUISaladUI.DropdownMenu→SaladUISaladUI.Form→SaladUISaladUI.HoverCard→SaladUISaladUI.Icon→SaladUISaladUI.Input→SaladUISaladUI.Label→SaladUISaladUI.Menu→SaladUISaladUI.Pagination→SaladUISaladUI.Popover→SaladUISaladUI.Progress→SaladUISaladUI.RadioGroup→SaladUISaladUI.ScrollArea→SaladUI
- Direction
- SaladUI uses (global), so a change to (global) can break SaladUI, while a change to SaladUI can't break (global).
- Position
- Below the diagonal: SaladUI uses a module listed above it, which is the healthy direction.
24→15 assets.salad_ui.components.accordion uses assets.salad_ui.core.component✕
- Connections
- 2 pairs of types, where a type in assets.salad_ui.components.accordion uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.accordion.AccordionComponent→assets.salad_ui.core.component.Componentassets.salad_ui.components.accordion.AccordionItem→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.accordion uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.accordion, while a change to assets.salad_ui.components.accordion can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.accordion uses a module listed above it, which is the healthy direction.
25→15 assets.salad_ui.components.chart uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.chart uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.chart.ChartComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.chart uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.chart, while a change to assets.salad_ui.components.chart can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.chart uses a module listed above it, which is the healthy direction.
26→15 assets.salad_ui.components.collapsible uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.collapsible uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.collapsible.CollapsibleComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.collapsible uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.collapsible, while a change to assets.salad_ui.components.collapsible can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.collapsible uses a module listed above it, which is the healthy direction.
27→15 assets.salad_ui.components.command uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.command uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.command.CommandComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.command uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.command, while a change to assets.salad_ui.components.command can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.command uses a module listed above it, which is the healthy direction.
28→15 assets.salad_ui.components.dialog uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.dialog uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.dialog.DialogComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.dialog uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.dialog, while a change to assets.salad_ui.components.dialog can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.dialog uses a module listed above it, which is the healthy direction.
29→15 assets.salad_ui.components.dropdown_menu uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.dropdown_menu uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.dropdown_menu.DropdownMenuComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.dropdown_menu uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.dropdown_menu, while a change to assets.salad_ui.components.dropdown_menu can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.dropdown_menu uses a module listed above it, which is the healthy direction.
30→15 assets.salad_ui.components.hover-card uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.hover-card uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.hover-card.HoverCardComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.hover-card uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.hover-card, while a change to assets.salad_ui.components.hover-card can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.hover-card uses a module listed above it, which is the healthy direction.
31→15 assets.salad_ui.components.menu uses assets.salad_ui.core.component✕
- Connections
- 2 pairs of types, where a type in assets.salad_ui.components.menu uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.menu.Menu→assets.salad_ui.core.component.Componentassets.salad_ui.components.menu.MenuItemBase→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.menu uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.menu, while a change to assets.salad_ui.components.menu can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.menu uses a module listed above it, which is the healthy direction.
32→15 assets.salad_ui.components.popover uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.popover uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.popover.PopoverComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.popover uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.popover, while a change to assets.salad_ui.components.popover can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.popover uses a module listed above it, which is the healthy direction.
33→15 assets.salad_ui.components.radio_group uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.radio_group uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.radio_group.RadioGroupComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.radio_group uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.radio_group, while a change to assets.salad_ui.components.radio_group can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.radio_group uses a module listed above it, which is the healthy direction.
34→15 assets.salad_ui.components.select uses assets.salad_ui.core.component✕
- Connections
- 2 pairs of types, where a type in assets.salad_ui.components.select uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.select.SelectComponent→assets.salad_ui.core.component.Componentassets.salad_ui.components.select.SelectItem→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.select uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.select, while a change to assets.salad_ui.components.select can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.select uses a module listed above it, which is the healthy direction.
35→15 assets.salad_ui.components.slider uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.slider uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.slider.SliderComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.slider uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.slider, while a change to assets.salad_ui.components.slider can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.slider uses a module listed above it, which is the healthy direction.
36→15 assets.salad_ui.components.switch uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.switch uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.switch.SwitchComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.switch uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.switch, while a change to assets.salad_ui.components.switch can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.switch uses a module listed above it, which is the healthy direction.
37→15 assets.salad_ui.components.tabs uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.tabs uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.tabs.TabsComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.tabs uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.tabs, while a change to assets.salad_ui.components.tabs can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.tabs uses a module listed above it, which is the healthy direction.
38→15 assets.salad_ui.components.toast uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.toast uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.toast.ToastComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.toast uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.toast, while a change to assets.salad_ui.components.toast can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.toast uses a module listed above it, which is the healthy direction.
39→15 assets.salad_ui.components.toast-flash uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.toast-flash uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.toast-flash.ToastFlashBridge→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.toast-flash uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.toast-flash, while a change to assets.salad_ui.components.toast-flash can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.toast-flash uses a module listed above it, which is the healthy direction.
40→15 assets.salad_ui.components.tooltip uses assets.salad_ui.core.component✕
- Connections
- 1 pair of types, where a type in assets.salad_ui.components.tooltip uses a type in assets.salad_ui.core.component.
- The types involved
assets.salad_ui.components.tooltip.TooltipComponent→assets.salad_ui.core.component.Component
- Direction
- assets.salad_ui.components.tooltip uses assets.salad_ui.core.component, so a change to assets.salad_ui.core.component can break assets.salad_ui.components.tooltip, while a change to assets.salad_ui.components.tooltip can't break assets.salad_ui.core.component.
- Position
- Below the diagonal: assets.salad_ui.components.tooltip uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Accessibility
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 26 | High / Critical |
| A05:2025 — Injection | 9 | High / Critical |
| A02:2025 — Security Misconfiguration | 5 | High / Critical |
Roadmap
Top priorities: Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video; Log through Elixir's `Logger` (with a JSON formatter such as logger_json) at meaningful points in the applications you run.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +4.0 pts | Medium | Access Controls |
| Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video. | +2.5 pts | Medium | Text alternatives |
| Log through Elixir's `Logger` (with a JSON formatter such as logger_json) at meaningful points in the applications you run. | +2.3 pts | Medium | Observability |
| Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). | +1.0 pts | Low | Dependency Vulnerabilities |
| Resolve the 1 No ADRs found finding(s) in ADR Quality — start with fly.toml. | +0.9 pts | Low | ADR Quality |
| Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh. | +1.7 pts | Medium | Page structure |
| Resolve the 17 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12), REDACTED (4), REDACTED. | +1.7 pts | Medium | Dependency Vulnerabilities |
| 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. | +1.6 pts | Medium | Type Safety |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.5 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 1.6 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.1 | Slop | IaC & Container Security: High IaC: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 5.8 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| REDACTED | 5.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| assets/salad_ui/components/toast.js | 7.1 | Mixed | Cyclomatic Complexity: ToastComponent.attachSwipeHandlers::onPointerMove (cyclomatic 16) |
| lib/mix/tasks/salad.install.ex | 7.4 | Mixed | Code Duplication: Edited copy of a member (10 corresponding lines) |
| assets/salad_ui/core/collection.js | 7.8 | Mixed | Cognitive Complexity: CollectionRegistry.getItem (cognitive 18) |
| REDACTED | 7.9 | Mixed | Dependency Vulnerabilities: Medium CVE: REDACTED |
| assets/salad_ui/core/component.js | 8.0 | Near-clean | God Classes: TooManyMethods: Component |
| lib/salad_ui/sidebar.ex | 8.5 | Near-clean | God Classes: FileTooLong: salad_ui/sidebar.ex |
| storybook/storybook/salad_ui_component/chart.story.exs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (15 corresponding lines) |
| lib/salad_ui/alert_dialog.ex | 8.5 | Near-clean | Code Duplication: Edited copies of one member (4 members, 15+ corresponding lines) |
| storybook/storybook/salad_ui_component/card.story.exs | 8.5 | Near-clean | Code Duplication: Edited copies of one member (3 members, 7+ corresponding lines) |
| lib/salad_ui/hover_card.ex | 8.5 | Near-clean | Code Duplication: Edited copy of a member (15 corresponding lines) |
| storybook/storybook/salad_ui_component/dropdown_menu.story.exs | 8.5 | Near-clean | Code Duplication: Edited copy of a member (109 corresponding lines) |
| lib/salad_ui/helpers.ex | 8.5 | Near-clean | Code Duplication: Edited copies of one member (4 members, 4+ corresponding lines) |
| lib/salad_ui/checkbox.ex | 8.5 | Near-clean | Code Duplication: Edited copy of a member (7 corresponding lines) |
| storybook/storybook/salad_ui_component/hover_card.story.exs | 8.5 | Near-clean | Code Duplication: Duplicated block (53–61 lines × 2) |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 56 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 56 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, 147 of 182 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- 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: this repository's production source spans .exs, and our analyzer cannot run the .exs test suite(s) — so no coverage was collected for the repository as a whole. The JavaScript/TypeScript half did build and run, and its own line coverage came back at 96.7% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
- D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 242 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 40 test source file(s) (.exs) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
- 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 reliability NOT SCORED: this repository's production source includes .exs, and the built-in reliability runner cannot re-run the .exs test suite(s) — so reliability was not measured for the repository as a whole. The JavaScript/TypeScript (node:test via `npm install --ignore-scripts` (no lockfile) in the repository root (242 tests); node:test via `npm ci --ignore-scripts` in assets/ (242 tests)): measured (0 flaky) suite(s) did re-run, and came back with 0 flaky across 1 measured tier(s) — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — test reliability is excluded from the score rather than counted.
- D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Hex package dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (mix.exs), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
- D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
- AX6 Interface segregation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence).
- C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'use Ecto.Repo' is imported (storybook/lib/salad_storybook/repo.ex:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C2 Access Controls — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
- C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'use Ecto.Repo' is imported (storybook/lib/salad_storybook/repo.ex:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'use Ecto.Repo' is imported (storybook/lib/salad_storybook/repo.ex:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'use Ecto.Repo' is imported (storybook/lib/salad_storybook/repo.ex:2), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Elixir is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Elixir is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's Elixir is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X3 Exception handling — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X7 Silent fallback defaults — 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. X7 measured the part of this repository it reads (C#, Python, TypeScript/JavaScript, Rust, Go, Java, Kotlin, Scala, PHP, Ruby, Swift and Dart), and its Elixir source is outside the check's reach, so the card covers only part of the product. That is a gap in this analyzer's language reach — not a finding that the unread source is free of silent defaults.
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.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- 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.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- 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.
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was ToastComponent.attachSwipeHandlers::onPointerMove at 16.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with ToastComponent.attachSwipeHandlers::onPointerMove (cyclomatic 16). — Refactoring it lifts Cyclomatic Complexity from 9.8 to about 10.0/10.
D2 · Cognitive Complexity
7 method(s) exceeded the cognitive complexity threshold of 15; the worst was ToastComponent.attachSwipeHandlers at 30.
What to do
- Bring the 5 bodies over 15 down to 15 or less in Cognitive Complexity — start with ToastComponent.attachSwipeHandlers (cognitive 30), attachSwipeHandlers::onPointerMove (cognitive 19), CollectionRegistry.getItem (cognitive 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cognitive Complexity from 8.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with toast.js, sidebar.ex. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with component.js. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 ClassTooLong finding(s) in God Classes — start with toast.js. — One of this dimension's main actionable groups (1 warning-level).
D4 · Code Duplication
7 duplicated block group(s) detected. A further 8 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
What to do
- Resolve the 2 Edited copy of a member (15 corresponding lines) finding(s) in Code Duplication — start with chart.story.exs, hover_card.ex. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 1 Edited copies of one member (4 members, 15+ corresponding lines) finding(s) in Code Duplication — start with alert_dialog.ex. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 Edited copies of one member (3 members, 7+ corresponding lines) finding(s) in Code Duplication — start with card.story.exs. — One of this dimension's main actionable groups (1 warning-level).
D5 · Coupling
3 production modules (npm+OTP), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 242 tests. Measured on the JavaScript/TypeScript suite only — at least 40 test source file(s) (.exs) went unread, so its test quality is unmeasured and is not in these counts.
D12 · Dependency Hygiene
22 outdated, 0 retired direct Hex dependencies, 0 pinning defect(s). Whether any of these packages is UNMAINTAINED is not graded — hex.pm publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: a Hex app name does not determine the modules it provides (`ecto_sql` provides Ecto.Adapters.SQL), and a large idiomatic class of BEAM dependencies — runtime adapters, codec plugins, protocol implementations and OTP applications the release starts — is correctly declared and never referenced in source, so absence of a reference is not evidence of an unused dependency. Known CVEs in this dependency graph are D30's question, read from REDACTED there.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets. 4 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
D14 · License Compliance
0 of 65 shipped Hex package(s) use a banned license. Licences were resolved from hex.pm over the packages a consumer installs — this repository's REDACTED closed over the declarations its mix.exs files do not gate behind `only:`. Packages it asks for ONLY under `only: [:dev, :test]` (or any other non-prod environment, such as `:docs`) are excluded: they are not installed by anything that depends on this repository. Each licence is the one hex.pm publishes for the package's current release. A further 1 package(s) the closure reaches resolve from git, a path or a local override and publish no licence this pass can read; they are outside this verdict. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's Hex package dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: assets/salad_ui/components/select.js (4 of 7 changes were fixes); lib/salad_ui/alert_dialog.ex (4 of 7 changes were fixes)
What to do
- Resolve the 2 Repeated repair finding(s) in Churn × Complexity Hotspots — start with select.js, alert_dialog.ex. — One of this dimension's main actionable groups (2 warning-level).
D16 · Bus Factor
32 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/salad_ui/dropdown_menu.ex. Counted over 60 of the 123 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 16466 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 15 document(s) read across 2 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality — start with fly.toml. — One of this dimension's main actionable groups (1 recommendation-level).
D24 · Comment Value
28 of 424 judged comments only repeat the code they sit on (6.6 %). 11 comment(s) in another language or script were not judged.
What to do
- Resolve the 23 redundant comment finding(s) in Comment Value — start with hover-card.js (3), select.js (3), tooltip.js (3). — One of this dimension's main actionable groups (23 recommendation-level).
D26 · Project Cohesion
1 of 4 build units (Mix, npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
10 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
9 finding(s): 0 critical, 6 high, 3 medium, 0 low. 6 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
- No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
26 finding(s): 0 critical, 9 high, 17 medium, 0 low.
What to do
- Resolve the 17 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (12), REDACTED (4), REDACTED. — One of this dimension's main actionable groups (17 warning-level).
- Resolve the 9 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (9). — One of this dimension's main actionable groups (9 issue-level).
D31 · IaC & Container Security
5 finding(s): 0 critical, 2 high, 3 medium, 0 low.
What to do
- Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
D34 · Knowledge Freshness
1 of 60 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is lib/salad_ui/command.ex. Counted over 60 of the 123 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AC1 · Text alternatives
- An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. — storybook/lib/salad_storybook_web/components/layouts/app.html.heex:5
What to do
- Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.
AC2 · Forms & labels
AC3 · Page structure
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. — storybook/lib/salad_storybook_web/components/layouts/root.html.heex:2
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — storybook/lib/salad_storybook_web/components/layouts/root.html.heex: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
- `.animate-indeterminate-progress` moves (`animation: indeterminate-progress 1.5s infinite linear`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — storybook/assets/css/storybook.dev.css:44, priv/static/assets/salad_ui.css:30
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
AX3 · Project dependency cycles
AX4 · Dependency direction
C2 · Access Controls
- This repository serves requests — a server (use Phoenix.Endpoint) (storybook/lib/salad_storybook_web/endpoint.ex:2) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — storybook/lib/salad_storybook_web/endpoint.ex:2
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
M1 · Documentation (README)
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 166 Elixir, JavaScript/TypeScript production file(s) this check read across 4 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; Elixir: Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Log through Elixir's `Logger` (with a JSON formatter such as logger_json) at meaningful points in the applications you run.
- Add a health-check endpoint (a /health route in your Phoenix router or Plug) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling
- `assets/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — assets/package.json:11
What to do
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- 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
P7 · Outbound HTTP resilience
- `:httpc.request(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — lib/mix/tasks/helpers/tw_animate_installer.ex:22
What to do
- Set an explicit timeout on every client — `recv_timeout:` for HTTPoison, `receive_timeout:` for Req and Finch, `Tesla.Middleware.Timeout` (or the adapter's `recv_timeout`) for Tesla, `timeout:` for `:httpc` — and add retries with back-off (`Tesla.Middleware.Retry`, Req's `retry:`) and a breaker (`:fuse`, `ExternalService`) around dependencies that fail.
R1 · Type Safety
- 0 typed · 61 plain JS — the untyped files are assets/salad_ui/components/accordion.js, assets/salad_ui/components/chart.js, assets/salad_ui/components/collapsible.js, assets/salad_ui/components/command.js, assets/salad_ui/components/dialog.js, assets/salad_ui/components/dropdown_menu.js (+55 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
- assets/salad_ui/components/hover-card.js:115 · assets/salad_ui/components/tooltip.js:123 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — assets/salad_ui/components/hover-card.js:115
- assets/salad_ui/components/dropdown_menu.js:144 · assets/salad_ui/components/select.js:255 — the two spans are one implementation copied and then locally edited — 237 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — assets/salad_ui/components/dropdown_menu.js:144
- assets/salad_ui/components/dropdown_menu.js:91 · assets/salad_ui/components/popover.js:69 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — assets/salad_ui/components/dropdown_menu.js:91
- assets/salad_ui/components/dropdown_menu.js:36 · assets/salad_ui/components/popover.js:18 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — assets/salad_ui/components/dropdown_menu.js:36
- assets/salad_ui/components/hover-card.js:35 · assets/salad_ui/components/tooltip.js:47 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — assets/salad_ui/components/hover-card.js:35
- assets/salad_ui/core/positioner.js:212 · assets/salad_ui/core/scroll-manager.js:143 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — assets/salad_ui/core/positioner.js:212
- assets/salad_ui/components/toast.js:731 · assets/salad_ui/components/toast.js:749 — 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. — assets/salad_ui/components/toast.js:731
- assets/salad_ui/components/menu.js:24 · assets/salad_ui/components/select.js:23 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — assets/salad_ui/components/menu.js:24
- assets/salad_ui/components/accordion.js:211 · assets/salad_ui/components/menu.js:247 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — assets/salad_ui/components/accordion.js:211
- assets/salad_ui/components/hover-card.js:9 · assets/salad_ui/components/tooltip.js:8 — the 2 copies are spread across 2 files, and each CITED SPAN is a SPECIALISATION DECLARATION — a type whose `extends` clause names a base and whose body hands that base its own values through `super(…)`. The shared module this dimension usually asks you to extract already exists: it is that base, every one of these sites already reaches it, and the `super(…)` call this row matched on is where each site passes its differences in. So do not read this as an extract-a-helper row — there is no missing helper, and what is left at each site is the declaration of one distinct specialisation, which cannot be deleted without deleting the thing it declares. Read what actually differs between the spans, because two different answers follow. Where the sites differ only in the values they hand the base — a type argument, a service, an alias, a cache — the repetition is a TEMPLATE, and the only moves that collapse it are to generate these declarations from the set they enumerate or to replace the repeated construction with one factory each site calls with its own values; where that set is the point, each site pinning one distinct thing, the repetition IS the enumeration and there is nothing to remove. Where instead a span carries logic OUTSIDE the delegation that is the same at every site, that logic is the part to move, and its home is the base type rather than a new module. Reported because the copies still drift apart the first time only one of them is edited. — assets/salad_ui/components/hover-card.js:9
- assets/salad_ui/components/radio_group.js:66 · assets/salad_ui/components/tabs.js:26 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — assets/salad_ui/components/radio_group.js:66
- assets/salad_ui/components/accordion.js:33 · assets/salad_ui/core/component.js:75 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — assets/salad_ui/components/accordion.js:33
- assets/salad_ui/components/accordion.js:177 · assets/salad_ui/components/select.js:157 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — assets/salad_ui/components/accordion.js:177
- assets/salad_ui/components/menu.js:253 · assets/salad_ui/components/select.js:221 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — assets/salad_ui/components/menu.js:253
- assets/salad_ui/components/radio_group.js:39 · assets/salad_ui/components/tabs.js:83 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — assets/salad_ui/components/radio_group.js:39
- assets/salad_ui/components/slider.js:144 · assets/salad_ui/components/slider.js:306 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — assets/salad_ui/components/slider.js:144
- storybook/assets/js/app.js:63 · storybook/assets/js/storybook.js:31 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — storybook/assets/js/app.js:63
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
- onPointerMove has cyclomatic complexity 16 and cognitive complexity 19; 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. — assets/salad_ui/components/toast.js:818
- getItem 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. — assets/salad_ui/core/collection.js:62
- getBasePosition has cyclomatic complexity 14 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 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. — assets/salad_ui/core/positioner.js:105
- getFlippedPlacement has cyclomatic complexity 13 and cognitive complexity 13; 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. — assets/salad_ui/core/positioner.js:173
- parseValues has cyclomatic complexity 12 and cognitive complexity 11; 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. — assets/salad_ui/components/slider.js:35
- restore has cyclomatic complexity 12 and cognitive complexity 11; 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. — assets/salad_ui/core/portal.js:55
- populateCard has cyclomatic complexity 11 and cognitive complexity 12; 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. — assets/salad_ui/components/toast.js:600
- endDrag has cyclomatic complexity 11 and cognitive complexity 10; 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. — assets/salad_ui/components/toast.js:845
R3 · Large Files
- assets/salad_ui/components/toast.js has 807 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — assets/salad_ui/components/toast.js:1
- assets/salad_ui/core/component.js has 557 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — assets/salad_ui/core/component.js:1
- assets/salad_ui/components/select.js has 504 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — assets/salad_ui/components/select.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×3) — assets/salad_ui/components/chart.js:1, storybook/assets/js/app.js:1, storybook/assets/js/storybook.js:1
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
- Declared in storybook/assets/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
- Set: Content-Security-Policy, Referrer-Policy, X-Content-Type-Options, X-Permitted-Cross-Domain-Policies. Missing: Strict-Transport-Security, X-Frame-Options — the four headers that carry the points of this card's security-headers term (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options), 0.5 each.(−1.0 on this card.) The server: storybook/lib/salad_storybook_web/endpoint.ex:2 — `Phoenix.Endpoint`.
- No handler of this repository's Elixir server answers 400, 413 or 422 (`put_status(conn, :bad_request)`, `:unprocessable_entity`, `send_resp(conn, 400, …)`), and nothing declares validation — no Ecto changeset `validate_required`/`validate_length`/`validate_format`, no OpenApiSpex `CastAndValidate`, ExJsonSchema or other schema validator, no `Plug.Parsers` `length:` cap — nothing shows inbound requests being checked, and refused, before a handler acts on them. A check that answers its failure with 200 and an error body is not seen. (−2.0 on this card.) The server: storybook/lib/salad_storybook_web/endpoint.ex:2 — `Phoenix.Endpoint`.
What to do
- Add Strict-Transport-Security, X-Frame-Options beside the headers the Elixir server already sets.
- Validate what the server reads from a request — path, query, headers, body size and shape — and answer what fails with 400 (413 for an oversized body, 422 for an invalid changeset) before a handler acts on it: cast params through an Ecto changeset with `validate_*` and render its errors with `put_status(:unprocessable_entity)`, or declare the request schema with OpenApiSpex's `CastAndValidate` plug.
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 | 60% | Adequate — gated by R1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 96% | Exemplary | Strongest area. |
| Maturity | 77% | Strong | Solid. |
| Readiness | 46% | Weak — gated by P2, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 46% | Weak — gated by C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 48% | Weak — gated by AC1 | 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 — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
- C3 Audit Trail — Not assessed: this repository stores data through 'use Ecto.Repo' (storybook/lib/salad_storybook/repo.ex:2) but declares no persisted model this check reads (Ecto schema fields, Ecto migration columns, Ash resource attributes). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'use Ecto.Repo' (storybook/lib/salad_storybook/repo.ex:2) but declares no persisted model this check reads (Ecto schema fields, Ecto migration columns, Ash resource attributes). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'use Ecto.Repo' (storybook/lib/salad_storybook/repo.ex:2) but declares no persisted model this check reads (Ecto schema fields, Ecto migration columns, Ash resource attributes). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 68 check(s) not relevant to this codebase
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: the BEAM has no dependency-injection container — state lives in processes, and no process is handed an instance whose lifetime another one scopes.
- AX2 Stateful singletons — Not applicable: Elixir processes share no mutable memory — state lives in a process's own mailbox — so there is no shared object to race on. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the image ran but published no HTTP port — nothing to crawl (EXPOSE the web port to unlock runtime evidence) This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — Not assessed: this repository stores data through 'use Ecto.Repo' (storybook/lib/salad_storybook/repo.ex:2) but declares no persisted model this check reads (Ecto schema fields, Ecto migration columns, Ash resource attributes). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D11 Test Reliability — Test reliability not scored — polyglot repository, one half has no runner
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; Elixir, JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- 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.
- D36 Supply-chain Provenance & Signing — The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 133 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (28 with fewer than two methods, 105 stateless), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
- DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 value object(s))
- 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
- GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
- IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 58 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for Benchee jobs (the entries of a `Benchee.run` job map) or Benchfella `bench "…"` blocks under `use Benchfella` in any `.ex`/`.exs` file, or benchee or benchfella in a mix.exs, 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: Elixir 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.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X12 Unreachable branch — X12 reached only 28% of this repository's production lines — elixir (16,466 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X16 Unfloored truncation loop — X16 reached only 28% of this repository's production lines — elixir (16,466 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X21 Side-effecting pattern guard — X21 reached only 28% of this repository's production lines — elixir (16,466 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. Elixir processes share no heap: a value sent to another process arrives as a copy, so no collection is reachable from two processes at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — not 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
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — X29 reached only 28% of this repository's production lines — elixir (16,466 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X3 Exception handling — X3 reached only 28% of this repository's production lines — elixir (16,466 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X5 Nullable reference types — Not applicable: this check asks whether the null-typed discipline a language offers is switched on, and how much of that the assertion operator takes back, and in this repository's languages there is no such switch and no such operator. Elixir's `nil` is an atom in a dynamically typed language: `@spec`s are checked by an external analysis that has no nullability operator, so there is no null-typed discipline in the language to adopt. Plain JavaScript carries no type annotations and commits no tsconfig, so it states no null-typed discipline for this check to grade: there is nothing here that switches null checking on or off, and TypeScript (or `// @ts-check`) is how a repository acquires one — advice, not a defect this card measures. Not a gap in the analyzer and not a finding about your code.
- 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 — 19 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <img> without a text alternative storybook/lib/salad_storybook_web/components/layouts/app.html.heex:5
- Document without a <title> storybook/lib/salad_storybook_web/components/layouts/root.html.heex:2
Serious — 90 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block (20 lines × 2 locations) assets/salad_ui/components/dropdown_menu.js:36
- Duplicated block (20 lines × 2 locations) assets/salad_ui/components/hover-card.js:35
- Duplicated block (20 lines × 2 locations) assets/salad_ui/core/positioner.js:212
- Duplicated block (8 lines × 2 locations) assets/salad_ui/components/accordion.js:177
- Duplicated block (8 lines × 2 locations) assets/salad_ui/components/menu.js:253
- Duplicated block (8 lines × 2 locations) assets/salad_ui/components/radio_group.js:39
- No test reaches this file assets/salad_ui/components/chart.js:1
- No test reaches this file storybook/assets/js/app.js:1
- No test reaches this file storybook/assets/js/storybook.js:1
- Animation without a prefers-reduced-motion guard storybook/assets/css/storybook.dev.css:44
- Animation without a prefers-reduced-motion guard priv/static/assets/salad_ui.css:30
- Repeated repair: assets/salad_ui/components/select.js assets/salad_ui/components/select.js:437
- Repeated repair: lib/salad_ui/alert_dialog.ex lib/salad_ui/alert_dialog.ex:70
- FileTooLong: components/toast.js assets/salad_ui/components/toast.js
- FileTooLong: salad_ui/sidebar.ex lib/salad_ui/sidebar.ex
- Edited copy of a member (15 corresponding lines) storybook/storybook/salad_ui_component/chart.story.exs:44
- Edited copy of a member (15 corresponding lines) lib/salad_ui/hover_card.ex:68
- Page without a main landmark storybook/lib/salad_storybook_web/components/layouts/root.html.heex:2
- No authorization storybook/lib/salad_storybook_web/endpoint.ex:2
- ToastComponent.attachSwipeHandlers::onPointerMove (cyclomatic 16) assets/salad_ui/components/toast.js:818
- ToastComponent.attachSwipeHandlers (cognitive 30) assets/salad_ui/components/toast.js:772
- attachSwipeHandlers::onPointerMove (cognitive 19) assets/salad_ui/components/toast.js:818
- CollectionRegistry.getItem (cognitive 18) assets/salad_ui/core/collection.js:62
- Selection.select (cognitive 17) assets/salad_ui/core/collection.js:206
- recomputeStackPositions (cognitive 17) assets/salad_ui/components/toast.js:500
- TooManyMethods: Component assets/salad_ui/core/component.js:33
- ClassTooLong: ToastComponent assets/salad_ui/components/toast.js:184
- Edited copies of one member (4 members, 15+ corresponding lines) lib/salad_ui/alert_dialog.ex:72
- Edited copies of one member (3 members, 7+ corresponding lines) storybook/storybook/salad_ui_component/card.story.exs:13
- Edited copy of a member (109 corresponding lines) storybook/storybook/salad_ui_component/dropdown_menu.story.exs:29
- Edited copies of one member (4 members, 4+ corresponding lines) lib/salad_ui/helpers.ex:117
- Edited copy of a member (7 corresponding lines) lib/salad_ui/checkbox.ex:43
- Edited copy of a member (10 corresponding lines) lib/mix/tasks/salad.install.ex:128
- Duplicated block (53–61 lines × 2) storybook/storybook/salad_ui_component/hover_card.story.exs:67
- Duplicated block (33 lines × 2) lib/mix/tasks/salad.install.ex:194
- Duplicated block (26–27 lines × 2) storybook/storybook/salad_ui_component/badge.story.exs:16
- Duplicated block (35 lines × 2) lib/salad_ui/alert.ex:66
- Duplicated block (18 lines × 2) lib/mix/tasks/salad.install.ex:166
- Duplicated block (8 lines × 2) lib/salad_ui/dropdown_menu.ex:162
- Duplicated block (7 lines × 2) storybook/storybook/salad_ui_component/command.story.exs:11
- No structured logging
- Outbound HTTP without resilience lib/mix/tasks/helpers/tw_animate_installer.ex:22
- Type Safety
- Duplicated block (34 lines × 2 locations) assets/salad_ui/components/hover-card.js:115
- Duplicated block with local edits (33 matched lines × 2 locations) assets/salad_ui/components/dropdown_menu.js:144
- Duplicated block (22 lines × 2 locations) assets/salad_ui/components/dropdown_menu.js:91
- Duplicated block (17 lines × 2 locations) assets/salad_ui/components/toast.js:731
- Duplicated block (15 lines × 2 locations) assets/salad_ui/components/menu.js:24
- Duplicated block (13 lines × 2 locations) assets/salad_ui/components/accordion.js:211
- Duplicated block (12 lines × 2 locations) assets/salad_ui/components/hover-card.js:9
- Duplicated block (10 lines × 2 locations) assets/salad_ui/components/radio_group.js:66
- Duplicated block with local edits (9 matched lines × 2 locations) assets/salad_ui/components/accordion.js:33
- Duplicated block (7 lines × 2 locations) assets/salad_ui/components/slider.js:144
- Duplicated block (6 lines × 2 locations) storybook/assets/js/app.js:63
- Complex function onPointerMove (cyclomatic 16, cognitive 19) assets/salad_ui/components/toast.js:818
- Complex function getItem (cyclomatic 14, cognitive 18) assets/salad_ui/core/collection.js:62
- Complex function getBasePosition (cyclomatic 14, cognitive 14) assets/salad_ui/core/positioner.js:105
- Complex function getFlippedPlacement (cyclomatic 13, cognitive 13) assets/salad_ui/core/positioner.js:173
- Complex function parseValues (cyclomatic 12, cognitive 11) assets/salad_ui/components/slider.js:35
- Complex function restore (cyclomatic 12, cognitive 11) assets/salad_ui/core/portal.js:55
- Complex function populateCard (cyclomatic 11, cognitive 12) assets/salad_ui/components/toast.js:600
- Complex function endDrag (cyclomatic 11, cognitive 10) assets/salad_ui/components/toast.js:845
- assets/salad_ui/components/toast.js: 807 lines of code assets/salad_ui/components/toast.js:1
- assets/salad_ui/core/component.js: 557 lines of code assets/salad_ui/core/component.js:1
- assets/salad_ui/components/select.js: 504 lines of code assets/salad_ui/components/select.js:1
- No typecheck script
- Unused dependency 'chartjs'
Minor — 50 finding(s)
- redundant comment assets/salad_ui/components/dialog.js:110
- redundant comment assets/salad_ui/components/dialog.js:175
- redundant comment assets/salad_ui/components/hover-card.js:27
- redundant comment assets/salad_ui/components/hover-card.js:133
- redundant comment assets/salad_ui/components/hover-card.js:158
- redundant comment assets/salad_ui/components/radio_group.js:138
- redundant comment assets/salad_ui/components/radio_group.js:203
- redundant comment assets/salad_ui/components/select.js:372
- redundant comment assets/salad_ui/components/select.js:380
- redundant comment assets/salad_ui/components/select.js:413
- redundant comment assets/salad_ui/components/slider.js:194
- redundant comment assets/salad_ui/components/tooltip.js:33
- redundant comment assets/salad_ui/components/tooltip.js:141
- redundant comment assets/salad_ui/components/tooltip.js:169
- redundant comment assets/salad_ui/core/click-outside.js:39
- redundant comment assets/salad_ui/core/click-outside.js:54
- redundant comment assets/salad_ui/core/component.js:340
- redundant comment assets/salad_ui/core/focus-trap.js:51
- redundant comment assets/salad_ui/core/portal.js:58
- redundant comment assets/salad_ui/core/portal.js:174
- redundant comment assets/salad_ui/core/scroll-manager.js:51
- redundant comment assets/salad_ui/core/scroll-manager.js:78
- redundant comment assets/salad_ui/core/state-machine.js:80
- Duplicated predicate lib/salad_ui/dropdown_menu.ex:163
- Duplicated predicate assets/salad_ui/core/positioner.js:216
- Duplicated predicate assets/salad_ui/components/menu.js:32
- Duplicated predicate assets/salad_ui/components/hover-card.js:151
- Duplicated predicate assets/salad_ui/components/hover-card.js:148
- Duplicated predicate assets/salad_ui/core/positioner.js:219
- Duplicated predicate assets/salad_ui/components/hover-card.js:145
- Duplicated predicate assets/salad_ui/components/hover-card.js:142
- Duplicated predicate assets/salad_ui/components/dropdown_menu.js:198
- Duplicated predicate assets/salad_ui/components/hover-card.js:31
- Duplicated predicate assets/salad_ui/components/hover-card.js:29
- Duplicated predicate assets/salad_ui/components/dropdown_menu.js:102
- Duplicated predicate assets/salad_ui/components/dropdown_menu.js:110
- Duplicated predicate assets/salad_ui/components/dropdown_menu.js:103
- Duplicated predicate assets/salad_ui/components/dropdown_menu.js:201
- Off-boarding risk: anonymized user #1
- Further sole-owners (lower concentration)
- No ADRs found storybook/fly.toml:1
- Projects may be oversized for their cohesion
- Orphaned files with no living knowledge
- Orphaned file lib/salad_ui/command.ex:1
- REDACTED
- No ADRs
- No dependency-update automation assets/package.json:11
- No release approval gate
- Security headers incomplete
- No inbound request validation detected
Minor — 23 finding(s)
- Outdated: dns_cluster
- Outdated: esbuild
- Outdated: ex_doc
- Outdated: finch
- Outdated: floki
- Outdated: igniter
- Outdated: lucide_icons
- Outdated: phoenix
- Outdated: phoenix_html
- Outdated: phoenix_live_reload
- Outdated: phoenix_live_view
- Outdated: phoenix_live_view
- Outdated: phoenix_storybook
- Outdated: postgrex
- Outdated: sourceror
- Outdated: styler
- Outdated: styler
- Outdated: swoosh
- Outdated: tailwind
- Outdated: tailwind
- Outdated: telemetry_metrics
- Outdated: tw_merge
- doc comments repeat the names assets/salad_ui/core/positioned-element.js:310
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-e0f36a0502f34ca6870585c7526d8360/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-e0f36a0502f34ca6870585c7526d8360/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 . | 9 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 26 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 5 | artifacts/raw/trivy-config.json |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |