Executive summary
Dogfalo/materialize is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 41 out of 100, which the At risk rating leaves unchanged.
Code Health, at 33, is the weakest lens and counts most in the score. The best first steps are adding type checking and finishing the stubs, each worth about 4 points. Raising Code Health to 70 would lift the score to about 47.
Eighty-seven known security holes in the packages the code depends on can be used by attackers. One password or key is open to anyone who can read the repository, and thirty-nine images have no description for people who can't see them. Updating the vulnerable packages, replacing the exposed password or key and describing the images would close these risks. The 30 pages or frames without a title need a descriptive title.
The product code is 9,879 lines, about €9,500 to rebuild.
If Code Health rose from 33 to 70, the lowest score rated Strong, the score would rise from 41 to about 47.
New since the last survey: 9 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dead Code · Dead file (~16 LoC) templates/masonry-template/js/init.js
- Visual & motion safety · Low contrast colour pair in CSS (3.0:1) sass/_style.scss
- Visual & motion safety · Low contrast colour pair in CSS (2.8:1) sass/components/_global.scss
Fixed since the last survey: 230 findings
- Secrets (history) · REDACTED: REDACTED 404.html
- Secrets (history) · REDACTED: REDACTED about.html
- Secrets (history) · REDACTED: REDACTED badges.html
- Secrets (history) · REDACTED: REDACTED breadcrumbs.html
- Secrets (history) · REDACTED: REDACTED buttons.html
- Secrets (history) · REDACTED: REDACTED cards.html
- Secrets (history) · REDACTED: REDACTED carousel.html
- Secrets (history) · REDACTED: REDACTED character-counter.html
- Secrets (history) · REDACTED: REDACTED chips.html
- Secrets (history) · REDACTED: REDACTED collapsible.html
- Secrets (history) · REDACTED: REDACTED collections.html
- Secrets (history) · REDACTED: REDACTED color.html
- Secrets (history) · REDACTED: REDACTED components.html
- Secrets (history) · REDACTED: REDACTED css-transitions.html
- Secrets (history) · REDACTED: REDACTED dialogs.html
- Secrets (history) · REDACTED: REDACTED dropdown.html
- Secrets (history) · REDACTED: REDACTED feature-discovery.html
- Secrets (history) · REDACTED: REDACTED footer.html
- Secrets (history) · REDACTED: REDACTED forms.html
- Secrets (history) · REDACTED: REDACTED fullscreen-slider-demo.html
- Secrets (history) · REDACTED: REDACTED getting_started.html
- Secrets (history) · REDACTED: REDACTED grid.html
- Secrets (history) · REDACTED: REDACTED helpers.html
- Secrets (history) · REDACTED: REDACTED icons.html
- Secrets (history) · REDACTED: REDACTED index.html
- Secrets (history) · REDACTED: REDACTED jade/page-contents/themes_content.html
- Secrets (history) · REDACTED: REDACTED javascript.html
- Secrets (history) · REDACTED: REDACTED media-css.html
- Secrets (history) · REDACTED: REDACTED media.html
- Secrets (history) · REDACTED: REDACTED mobile.html
- Secrets (history) · REDACTED: REDACTED modals.html
- Secrets (history) · REDACTED: REDACTED navbar.html
- Secrets (history) · REDACTED: REDACTED pagination.html
- Secrets (history) · REDACTED: REDACTED parallax-demo.html
- Secrets (history) · REDACTED: REDACTED parallax.html
- Secrets (history) · REDACTED: REDACTED preloader.html
- Secrets (history) · REDACTED: REDACTED pulse.html
- Secrets (history) · REDACTED: REDACTED pushpin.html
- Secrets (history) · REDACTED: REDACTED sass.html
- Secrets (history) · REDACTED: REDACTED scrollfire.html
- Secrets (history) · REDACTED: REDACTED scrollspy.html
- Secrets (history) · REDACTED: REDACTED shadow.html
- Secrets (history) · REDACTED: REDACTED showcase.html
- Secrets (history) · REDACTED: REDACTED side-nav.html
- Secrets (history) · REDACTED: REDACTED table.html
- Secrets (history) · REDACTED: REDACTED tabs.html
- Secrets (history) · REDACTED: REDACTED themes.html
- Secrets (history) · REDACTED: REDACTED themes.html
- Secrets (history) · REDACTED: REDACTED transitions.html
- Secrets (history) · REDACTED: REDACTED typography.html
- Secrets (history) · REDACTED: REDACTED waves.html
- Static Analysis (SAST) · Medium: insecure-request js/timepicker.js
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Text alternatives · <img> without a text alternative jade/page-contents/media_content.html
- Text alternatives · <img> without a text alternative jade/page-contents/media_content.html
- Text alternatives · <img> without a text alternative jade/page-contents/parallax_demo_content.html
- Text alternatives · <img> without a text alternative jade/page-contents/parallax_demo_content.html
- Text alternatives · <img> without a text alternative jade/page-contents/sidenav_content.html
- Text alternatives · <img> without a text alternative jade/page-contents/sidenav_content.html
- Text alternatives · <img> without a text alternative jade/parallax/parallax_content.html
- Text alternatives · <img> without a text alternative jade/parallax/parallax_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative jade/showcase/showcase_content.html
- Text alternatives · <img> without a text alternative templates/masonry-template/preview.html
- Text alternatives · <img> without a text alternative templates/masonry-template/preview.html
- Text alternatives · <img> without a text alternative templates/masonry-template/preview.html
- Text alternatives · <img> without a text alternative templates/masonry-template/preview.html
- Text alternatives · <img> without a text alternative templates/masonry-template/preview.html
- Page structure · Document without a <title> jade/modals.jade
- Page structure · Document without a <title> jade/navbar.jade
- Page structure · Heading level jumps from h1 to h4 jade/page-contents/404_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/autocomplete_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/autocomplete_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/badges_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/buttons_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/cards_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/cards_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/cards_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/carousel_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/chips_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/collapsible_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/collapsible_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/collapsible_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/color_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/dropdown_content.html
- Page structure · Heading level jumps from h3 to h5 jade/page-contents/featureDiscovery_content.html
Rebuild cost: about €9,500 · Estimate
| Cost to rebuild | €3,100 to €16,000, for 52 to 166 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 41. 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: 9,879 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 extras.noUiSlider | 3 jade.page-contents | 4 js | 5 js.component | 6 js.toasts | 7 js.autocomplete | 8 js.buttons | 9 js.carousel | 10 js.characterCounter | 11 js.chips | 12 js.collapsible | 13 js.datepicker | 14 js.dropdown | 15 js.materialbox | 16 js.modal | 17 js.parallax | 18 js.pushpin | 19 js.range | 20 js.scrollspy | 21 js.select | 22 js.sidenav | 23 js.slider | 24 js.tabs | 25 js.tapTarget | 26 js.timepicker | 27 js.tooltip |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 (global) | |||||||||||||||||||||||||||
| 2 extras.noUiSlider | |||||||||||||||||||||||||||
| 3 jade.page-contents | |||||||||||||||||||||||||||
| 4 js | |||||||||||||||||||||||||||
| 5 js.component | |||||||||||||||||||||||||||
| 6 js.toasts | |||||||||||||||||||||||||||
| 7 js.autocomplete | 1 | ||||||||||||||||||||||||||
| 8 js.buttons | 1 | ||||||||||||||||||||||||||
| 9 js.carousel | 1 | ||||||||||||||||||||||||||
| 10 js.characterCounter | 1 | ||||||||||||||||||||||||||
| 11 js.chips | 1 | ||||||||||||||||||||||||||
| 12 js.collapsible | 1 | ||||||||||||||||||||||||||
| 13 js.datepicker | 1 | ||||||||||||||||||||||||||
| 14 js.dropdown | 1 | ||||||||||||||||||||||||||
| 15 js.materialbox | 1 | ||||||||||||||||||||||||||
| 16 js.modal | 1 | ||||||||||||||||||||||||||
| 17 js.parallax | 1 | ||||||||||||||||||||||||||
| 18 js.pushpin | 1 | ||||||||||||||||||||||||||
| 19 js.range | 1 | ||||||||||||||||||||||||||
| 20 js.scrollspy | 1 | ||||||||||||||||||||||||||
| 21 js.select | 1 | ||||||||||||||||||||||||||
| 22 js.sidenav | 1 | ||||||||||||||||||||||||||
| 23 js.slider | 1 | ||||||||||||||||||||||||||
| 24 js.tabs | 1 | ||||||||||||||||||||||||||
| 25 js.tapTarget | 1 | ||||||||||||||||||||||||||
| 26 js.timepicker | 1 | ||||||||||||||||||||||||||
| 27 js.tooltip | 1 |
7→5 js.autocomplete uses js.component✕
- Connections
- 1 pair of types, where a type in js.autocomplete uses a type in js.component.
- The types involved
js.autocomplete.Autocomplete→js.component.Component
- Direction
- js.autocomplete uses js.component, so a change to js.component can break js.autocomplete, while a change to js.autocomplete can't break js.component.
- Position
- Below the diagonal: js.autocomplete uses a module listed above it, which is the healthy direction.
8→5 js.buttons uses js.component✕
- Connections
- 1 pair of types, where a type in js.buttons uses a type in js.component.
- The types involved
js.buttons.FloatingActionButton→js.component.Component
- Direction
- js.buttons uses js.component, so a change to js.component can break js.buttons, while a change to js.buttons can't break js.component.
- Position
- Below the diagonal: js.buttons uses a module listed above it, which is the healthy direction.
9→5 js.carousel uses js.component✕
- Connections
- 1 pair of types, where a type in js.carousel uses a type in js.component.
- The types involved
js.carousel.Carousel→js.component.Component
- Direction
- js.carousel uses js.component, so a change to js.component can break js.carousel, while a change to js.carousel can't break js.component.
- Position
- Below the diagonal: js.carousel uses a module listed above it, which is the healthy direction.
10→5 js.characterCounter uses js.component✕
- Connections
- 1 pair of types, where a type in js.characterCounter uses a type in js.component.
- The types involved
js.characterCounter.CharacterCounter→js.component.Component
- Direction
- js.characterCounter uses js.component, so a change to js.component can break js.characterCounter, while a change to js.characterCounter can't break js.component.
- Position
- Below the diagonal: js.characterCounter uses a module listed above it, which is the healthy direction.
11→5 js.chips uses js.component✕
- Connections
- 1 pair of types, where a type in js.chips uses a type in js.component.
- The types involved
js.chips.Chips→js.component.Component
- Direction
- js.chips uses js.component, so a change to js.component can break js.chips, while a change to js.chips can't break js.component.
- Position
- Below the diagonal: js.chips uses a module listed above it, which is the healthy direction.
12→5 js.collapsible uses js.component✕
- Connections
- 1 pair of types, where a type in js.collapsible uses a type in js.component.
- The types involved
js.collapsible.Collapsible→js.component.Component
- Direction
- js.collapsible uses js.component, so a change to js.component can break js.collapsible, while a change to js.collapsible can't break js.component.
- Position
- Below the diagonal: js.collapsible uses a module listed above it, which is the healthy direction.
13→5 js.datepicker uses js.component✕
- Connections
- 1 pair of types, where a type in js.datepicker uses a type in js.component.
- The types involved
js.datepicker.Datepicker→js.component.Component
- Direction
- js.datepicker uses js.component, so a change to js.component can break js.datepicker, while a change to js.datepicker can't break js.component.
- Position
- Below the diagonal: js.datepicker uses a module listed above it, which is the healthy direction.
14→5 js.dropdown uses js.component✕
- Connections
- 1 pair of types, where a type in js.dropdown uses a type in js.component.
- The types involved
js.dropdown.Dropdown→js.component.Component
- Direction
- js.dropdown uses js.component, so a change to js.component can break js.dropdown, while a change to js.dropdown can't break js.component.
- Position
- Below the diagonal: js.dropdown uses a module listed above it, which is the healthy direction.
15→5 js.materialbox uses js.component✕
- Connections
- 1 pair of types, where a type in js.materialbox uses a type in js.component.
- The types involved
js.materialbox.Materialbox→js.component.Component
- Direction
- js.materialbox uses js.component, so a change to js.component can break js.materialbox, while a change to js.materialbox can't break js.component.
- Position
- Below the diagonal: js.materialbox uses a module listed above it, which is the healthy direction.
16→5 js.modal uses js.component✕
- Connections
- 1 pair of types, where a type in js.modal uses a type in js.component.
- The types involved
js.modal.Modal→js.component.Component
- Direction
- js.modal uses js.component, so a change to js.component can break js.modal, while a change to js.modal can't break js.component.
- Position
- Below the diagonal: js.modal uses a module listed above it, which is the healthy direction.
17→5 js.parallax uses js.component✕
- Connections
- 1 pair of types, where a type in js.parallax uses a type in js.component.
- The types involved
js.parallax.Parallax→js.component.Component
- Direction
- js.parallax uses js.component, so a change to js.component can break js.parallax, while a change to js.parallax can't break js.component.
- Position
- Below the diagonal: js.parallax uses a module listed above it, which is the healthy direction.
18→5 js.pushpin uses js.component✕
- Connections
- 1 pair of types, where a type in js.pushpin uses a type in js.component.
- The types involved
js.pushpin.Pushpin→js.component.Component
- Direction
- js.pushpin uses js.component, so a change to js.component can break js.pushpin, while a change to js.pushpin can't break js.component.
- Position
- Below the diagonal: js.pushpin uses a module listed above it, which is the healthy direction.
19→5 js.range uses js.component✕
- Connections
- 1 pair of types, where a type in js.range uses a type in js.component.
- The types involved
js.range.Range→js.component.Component
- Direction
- js.range uses js.component, so a change to js.component can break js.range, while a change to js.range can't break js.component.
- Position
- Below the diagonal: js.range uses a module listed above it, which is the healthy direction.
20→5 js.scrollspy uses js.component✕
- Connections
- 1 pair of types, where a type in js.scrollspy uses a type in js.component.
- The types involved
js.scrollspy.ScrollSpy→js.component.Component
- Direction
- js.scrollspy uses js.component, so a change to js.component can break js.scrollspy, while a change to js.scrollspy can't break js.component.
- Position
- Below the diagonal: js.scrollspy uses a module listed above it, which is the healthy direction.
21→5 js.select uses js.component✕
- Connections
- 1 pair of types, where a type in js.select uses a type in js.component.
- The types involved
js.select.FormSelect→js.component.Component
- Direction
- js.select uses js.component, so a change to js.component can break js.select, while a change to js.select can't break js.component.
- Position
- Below the diagonal: js.select uses a module listed above it, which is the healthy direction.
22→5 js.sidenav uses js.component✕
- Connections
- 1 pair of types, where a type in js.sidenav uses a type in js.component.
- The types involved
js.sidenav.Sidenav→js.component.Component
- Direction
- js.sidenav uses js.component, so a change to js.component can break js.sidenav, while a change to js.sidenav can't break js.component.
- Position
- Below the diagonal: js.sidenav uses a module listed above it, which is the healthy direction.
23→5 js.slider uses js.component✕
- Connections
- 1 pair of types, where a type in js.slider uses a type in js.component.
- The types involved
js.slider.Slider→js.component.Component
- Direction
- js.slider uses js.component, so a change to js.component can break js.slider, while a change to js.slider can't break js.component.
- Position
- Below the diagonal: js.slider uses a module listed above it, which is the healthy direction.
24→5 js.tabs uses js.component✕
- Connections
- 1 pair of types, where a type in js.tabs uses a type in js.component.
- The types involved
js.tabs.Tabs→js.component.Component
- Direction
- js.tabs uses js.component, so a change to js.component can break js.tabs, while a change to js.tabs can't break js.component.
- Position
- Below the diagonal: js.tabs uses a module listed above it, which is the healthy direction.
25→5 js.tapTarget uses js.component✕
- Connections
- 1 pair of types, where a type in js.tapTarget uses a type in js.component.
- The types involved
js.tapTarget.TapTarget→js.component.Component
- Direction
- js.tapTarget uses js.component, so a change to js.component can break js.tapTarget, while a change to js.tapTarget can't break js.component.
- Position
- Below the diagonal: js.tapTarget uses a module listed above it, which is the healthy direction.
26→5 js.timepicker uses js.component✕
- Connections
- 1 pair of types, where a type in js.timepicker uses a type in js.component.
- The types involved
js.timepicker.Timepicker→js.component.Component
- Direction
- js.timepicker uses js.component, so a change to js.component can break js.timepicker, while a change to js.timepicker can't break js.component.
- Position
- Below the diagonal: js.timepicker uses a module listed above it, which is the healthy direction.
27→5 js.tooltip uses js.component✕
- Connections
- 1 pair of types, where a type in js.tooltip uses a type in js.component.
- The types involved
js.tooltip.Tooltip→js.component.Component
- Direction
- js.tooltip uses js.component, so a change to js.component can break js.tooltip, while a change to js.tooltip can't break js.component.
- Position
- Below the diagonal: js.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 | 125 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
| A08:2025 — Software or Data Integrity Failures | 1 | Medium |
Roadmap
Top priorities: 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; Bring the 13 bodies over 15 down to 15 or less in Cognitive Complexity — start with setHand (cognitive 50), _scroll (cognitive 41), render (cognitive 32); Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| 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. | +4.5 pts | Medium | Type Safety |
| Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for. | +3.6 pts | Medium | Incompleteness & stubs |
| Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package. | +3.6 pts | Medium | Large Files |
| Resolve the 22 Orphaned file finding(s) in Knowledge Freshness — start with dropdown.js, Gruntfile.js, sidenav.js. | +3.2 pts | Medium | Knowledge Freshness |
| Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. | +2.7 pts | Medium | Keyboard semantics |
| 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.2 pts | Medium | Text alternatives |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.0 pts | Medium | Architecture documentation |
| 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. | +1.9 pts | Medium | Visual & motion safety |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| js/datepicker.js | 7.1 | Mixed | Cyclomatic Complexity: Datepicker.render (cyclomatic 27) |
| js/timepicker.js | 7.1 | Mixed | Cyclomatic Complexity: Timepicker.setHand (cyclomatic 24) |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| js/dropdown.js | 7.4 | Mixed | Cyclomatic Complexity: _handleDropdownKeydown (cyclomatic 21) |
| js/carousel.js | 7.8 | Mixed | Cyclomatic Complexity: Carousel._scroll (cyclomatic 29) |
| js/tapTarget.js | 7.8 | Mixed | Cyclomatic Complexity: TapTarget._calculatePositioning (cyclomatic 18) |
| js/forms.js | 7.8 | Mixed | Cyclomatic Complexity: forms.M.textareaAutoResize (cyclomatic 17) |
| js/chips.js | 8.5 | Near-clean | Cognitive Complexity: Chips._handleChipsKeydown (cognitive 22) |
| js/tabs.js | 8.5 | Near-clean | Cognitive Complexity: Tabs._handleTabClick (cognitive 20) |
| js/select.js | 8.5 | Near-clean | Cognitive Complexity: _setupDropdown (cognitive 20) |
| js/sidenav.js | 8.5 | Near-clean | God Classes: TooManyMethods: Sidenav |
| Gruntfile.js | 9.5 | Near-clean | Comment Value: redundant comment |
| docs/js/init.js | 9.5 | Near-clean | Comment Value: redundant comment |
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 51 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 51 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, 448 of 458 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D4 Code Duplication — 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. The language model for this repository listed its production source (.html) but exposed no token stream for any of it, so nothing reached the token comparison.
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.js) and the coverage collector does support this ecosystem — it drives jest, vitest and mocha — but no test command in this repository names a runner the analyzer recognises, so it could not tell what to instrument. Read from the manifests: the root package has a `scripts.test` of `grunt travis`. Not scored — this is a gap in the analyzer's reading of test commands, not a missing .js runner and not a defect in this repository.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.js) and the reliability runner does support this ecosystem — it drives jest, vitest, mocha and egg-bin — but no test command in this repository names a runner the analyzer recognises, so it could not tell what to re-run. Read from the manifests: the root package has a `scripts.test` of `grunt travis`. So flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's reading of test commands, not a missing .js runner and not a finding about this repository.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's 1 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository's 1 committed lockfile(s) are in a format this engine does not resolve. The resolver reads pnpm-lock.yaml, REDACTED / npm-shrinkwrap.json at lockfileVersion 2 or 3, yarn.lock in both the classic and berry dialects, and bun's text bun.lock; what it cannot read is bun.lockb, a binary serialisation of bun's install graph with no published layout, and a lockfileVersion 1 REDACTED, which is a differently-shaped nested tree. So nothing here could be graded and registry.npmjs.org was never asked. This is OUR side and it is a COLLECTOR gap, not an environment fault: the remedy is to write the reader for the format this repository commits, and no change to the scan image or the egress allowlist can close it.
- D14 License Compliance — 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. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Every one of the 25 significant source file(s) was last meaningfully changed so long ago that no living knowledge remains, so there is no concentration to measure — the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
- 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 an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D44 Platform End-of-Life — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AC1 Text alternatives — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 24 further occurrence(s) are not listed individually; the score already reflects all 64.
- AC3 Page structure — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 123 further occurrence(s) are not listed individually; the score already reflects all 163.
- AC4 Keyboard semantics — 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. 19 further occurrence(s) are not listed individually; the score already reflects all 59.
- AC6 Visual & motion safety — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
- 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.
- AXB2 Runtime readiness — 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. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> materialize-css@1.0.0 dev / > grunt monitor / sh: 1: grunt: not found" No runtime evidence was gathered.
- 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 DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> materialize-css@1.0.0 dev / > grunt monitor / sh: 1: grunt: not found" No runtime evidence was gathered.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- 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.
- 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.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 REDACTED Scanning: REDACTED 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").
- 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.
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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.
- AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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
14 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was Carousel._scroll at 29.
What to do
- Bring the 7 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with Carousel._scroll (cyclomatic 29), Datepicker.render (cyclomatic 27), Timepicker.setHand (cyclomatic 24). — 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 7 together lifts Cyclomatic Complexity from 8.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
D2 · Cognitive Complexity
24 method(s) exceeded the cognitive complexity threshold of 15; the worst was setHand at 50.
What to do
- Bring the 13 bodies over 15 down to 15 or less in Cognitive Complexity — start with setHand (cognitive 50), _scroll (cognitive 41), render (cognitive 32). — 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 13 together lifts Cognitive Complexity from 6.8 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 3 TooManyMethods finding(s) in God Classes — start with datepicker.js, timepicker.js, sidenav.js. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 1 FileTooLong finding(s) in God Classes — start with datepicker.js. — One of this dimension's main actionable groups (1 warning-level).
D6 · Cohesion (LCOM4)
0 of 19 classes have LCOM4 above 3.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 60 tests.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 2 document(s) read across 1 unit(s).
D24 · Comment Value
2 of 289 judged comments only repeat the code they sit on (0.7 %). 19 comment(s) in another language or script were not judged.
What to do
- Resolve the 2 redundant comment finding(s) in Comment Value — start with Gruntfile.js, init.js. — One of this dimension's main actionable groups (2 recommendation-level).
D27 · Navigability
6 % 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)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
semgrep found no security issues.
D30 · Dependency Vulnerabilities
125 finding(s): 25 critical, 62 high, 33 medium, 5 low.
What to do
- Resolve the 57 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (57). — One of this dimension's main actionable groups (57 issue-level).
- Resolve the 24 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (24). — One of this dimension's main actionable groups (24 issue-level).
- Resolve the 5 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
D34 · Knowledge Freshness
25 of 25 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is js/datepicker.js. Counted over 25 of the 31 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 22 Orphaned file finding(s) in Knowledge Freshness — start with dropdown.js, Gruntfile.js, sidenav.js. — One of this dimension's main actionable groups (22 recommendation-level).
- Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with datepicker.js, carousel.js, timepicker.js. — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
What to do
- Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
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. (×39) — jade/about/about_content.html:36, jade/about/about_content.html:43, jade/about/about_content.html:50, …
- Video with no captions <track> offers no captions. Add a <track kind="captions"> pointing at a WebVTT file for this video (or confirm captions are provided another way). — jade/page-contents/media-css_content.html:81
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
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. (×2) — jade/_navbar.jade:26, jade/page-contents/text_inputs_content.html:329
- A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×3) — jade/index/index_content.html:32, templates/masonry-template/index.html:23, templates/masonry-template/preview.html:23
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×14) — jade/page-contents/range_content.html:37, jade/page-contents/select_content.html:14, jade/page-contents/select_content.html:28, …
- This <label> has no for and wraps no form control, so it names nothing: assistive tech never announces it, and clicking the caption focuses no field. Note that an id on the label is not an association — it is the TARGET of one, so a control still has to point at it. Give the label for="<the control's id>", move the control inside the label, or point the control's aria-labelledby at this label's id. (×8) — jade/page-contents/select_content.html:20, jade/page-contents/select_content.html:34, jade/page-contents/select_content.html:51, …
- A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — js/datepicker.js:961, js/datepicker.js:962
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — fab-toolbar-demo.html:2
- A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×27) — jade/404.jade:5, jade/about.jade:5, jade/auto-init.jade:5, …
- An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. (×3) — jade/_footer.html:19, jade/about/about_content.html:30, jade/getting_started/getting_started_content.html:85
- Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×9) — jade/about/about_content.html:6, jade/about/about_content.html:76, jade/getting_started/getting_started_content.html:6, …
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics
- An <a> with no href, role or tabindex isn't focusable or keyboard-activatable. Give it a real href, or use a <button> for an action. (×40) — fab-toolbar-demo.html:24, jade/_navbar.jade:21, jade/_navbar.jade:37, …
What to do
- Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness
AC6 · Visual & motion safety
- `.bsa-cpc .default-title:before` sets color: #fff on background-color: #ee6e73 — 3.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — sass/_style.scss:980
- `i.circle` sets color: #fff on background-color: #999 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — sass/components/_global.scss:551
- `#nav-mobile li.search .search-wrapper input#search:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/_style.scss:1198
- `#nav-mobile li.search .search-results a.focused` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/_style.scss:1232
- `.btn-large` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/components/_buttons.scss:49
- `.chips .input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/components/_chips.scss:63
- `.chips` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/components/_chips.scss:43
- `.collapsible-header:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/components/_collapsible.scss:11
- `.dropdown-content:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/components/_dropdown.scss:3
- `.modal:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/components/_modal.scss:3
- `input:not([type]):not(.browser-default)` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/components/forms/_input-fields.scss:31
- `input[type=range]:focus` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/components/forms/_range.scss:24
- `input[type=range]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — sass/components/forms/_range.scss:18
- `#nav-mobile li.search .search-wrapper` moves (`transition: margin .25s ease`) 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. — sass/_style.scss:1194
- `.collapsible.popout > li` moves (`transition: margin .35s cubic-bezier(0.250, 0.460, 0.450, 0.940)`) 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. — sass/components/_collapsible.scss:84
- `.progress .determinate` moves (`transition: width .3s 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. — sass/components/_global.scss:660
- `.progress .indeterminate:before` moves (`animation: indeterminate 2.1s cubic-bezier(0.650, 0.815, 0.735, 0.395) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — sass/components/_global.scss:673
- `.progress .indeterminate:after` moves (`animation: indeterminate-short 2.1s cubic-bezier(0.165, 0.840, 0.440, 1.000) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — sass/components/_global.scss:685
- `.preloader-wrapper.active` moves (`animation: container-rotate 1568ms linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — sass/components/_preloader.scss:49
- `.active .spinner-layer.spinner-blue` moves (`animation: fill-unfill-rotate 5332ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both, blue-fade-in-out 5332ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both`) 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. — sass/components/_preloader.scss:105
- `.active .spinner-layer.spinner-red` moves (`animation: fill-unfill-rotate 5332ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both, red-fade-in-out 5332ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both`) 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. — sass/components/_preloader.scss:111
- `.active .spinner-layer.spinner-yellow` moves (`animation: fill-unfill-rotate 5332ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both, yellow-fade-in-out 5332ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both`) 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. — sass/components/_preloader.scss:117
- `.active .spinner-layer.spinner-green` moves (`animation: fill-unfill-rotate 5332ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both, green-fade-in-out 5332ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both`) 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. — sass/components/_preloader.scss:123
- `.active .spinner-layer` moves (`animation: fill-unfill-rotate 5332ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both`) 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. — sass/components/_preloader.scss:134
- `.active .circle-clipper.left .circle` moves (`animation: left-spin 1333ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both`) 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. — sass/components/_preloader.scss:287
- `.active .circle-clipper.right .circle` moves (`animation: right-spin 1333ms cubic-bezier(0.4, 0.0, 0.2, 1) infinite both`) 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. — sass/components/_preloader.scss:293
- `#spinnerContainer.cooldown` moves (`animation: container-rotate 1568ms linear infinite, fade-out 400ms cubic-bezier(0.4, 0.0, 0.2, 1)`) 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. — sass/components/_preloader.scss:323
- `.pulse::before` moves (`transition: opacity .3s, transform .3s`) 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. — sass/components/_pulse.scss:12
- `.pulse::before` moves (`animation: pulse-animation 1s cubic-bezier(0.24, 0, 0.38, 1) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — sass/components/_pulse.scss:13
- `.tap-target-wrapper.open .tap-target` moves (`transition: transform .3s cubic-bezier(.42,0,.58,1), opacity .3s cubic-bezier(.42,0,.58,1)`) 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. — sass/components/_tapTarget.scss:17
- `.tap-target-wrapper.open .tap-target-wave::after` moves (`animation: pulse-animation 1s cubic-bezier(0.24, 0, 0.38, 1) infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — sass/components/_tapTarget.scss:27
- `.tap-target-wrapper.open .tap-target-wave::after` moves (`transition: opacity .3s, transform .3s, visibility 0s 1s`) 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. — sass/components/_tapTarget.scss:28
- `.tap-target` moves (`transition: transform .3s cubic-bezier(.42,0,.58,1), opacity .3s cubic-bezier(.42,0,.58,1)`) 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. — sass/components/_tapTarget.scss:45
- `.tap-target-wave::before` moves (`transition: transform .3s`) 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. — sass/components/_tapTarget.scss:68
- `.tap-target-wave::after` moves (`transition: opacity .3s, transform .3s, visibility 0s`) 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. — sass/components/_tapTarget.scss:72
- `.timepicker-dial` moves (`transition: transform 350ms, opacity 350ms`) 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. — sass/components/_timepicker.scss:106
- `.scale-transition.scale-out` moves (`transition: transform .2s`) 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. — sass/components/_transitions.scss:5
- `.scale-transition` moves (`transition: transform .3s cubic-bezier(0.53, 0.01, 0.36, 1.63)`) 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. — sass/components/_transitions.scss:12
- `[type="checkbox"].filled-in + span:not(.lever):before` moves (`transition: border .25s, background-color .25s, width .20s .1s, height .20s .1s, top .20s .1s, left .20s .1s`) 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. — sass/components/forms/_checkboxes.scss:119
- `.input-field > label` moves (`transition: transform .2s ease-out, color .2s ease-out`) 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. — sass/components/forms/_input-fields.scss:185
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
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. — js/tapTarget.js:229
What to do
- Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
M1 · Documentation (README)
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.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
- Most of the production code is in directories of its own, but 1 application file(s) sit at the repository root beside the build and tooling files (`package.js`).
M4 · Documentation accuracy
P1 · CI/CD gates
- The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `CONTRIBUTING.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
What to do
- Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `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`. — package.json:29
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/javascript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
R1 · Type Safety
- 0 typed · 30 plain JS — the untyped files are js/autocomplete.js, js/buttons.js, js/cards.js, js/carousel.js, js/characterCounter.js, js/chips.js (+24 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
- js/collapsible.js:1 · js/tabs.js:1 — the two spans are one implementation copied and then locally edited — 173 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. — js/collapsible.js:1
- js/characterCounter.js:1 · js/range.js:1 — 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. — js/characterCounter.js:1
- js/autocomplete.js:52 · js/select.js:41 — 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. — js/autocomplete.js:52
- js/slider.js:100 · js/tabs.js:51 — the two spans are one implementation copied and then locally edited — 113 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. — js/slider.js:100
- js/collapsible.js:58 · js/materialbox.js:54 — the two spans are one implementation copied and then locally edited — 114 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. — js/collapsible.js:58
- js/dropdown.js:84 · js/slider.js:100 — the two spans are one implementation copied and then locally edited — 100 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. — js/dropdown.js:84
- js/materialbox.js:51 · js/slider.js:100 — the two spans are one implementation copied and then locally edited — 113 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. — js/materialbox.js:51
- js/materialbox.js:51 · js/tabs.js:51 — the two spans are one implementation copied and then locally edited — 113 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. — js/materialbox.js:51
- js/sidenav.js:482 · js/sidenav.js:531 — 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. — js/sidenav.js:482
- js/buttons.js:55 · js/carousel.js:113 · js/tapTarget.js:40 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — js/buttons.js:55
- js/collapsible.js:58 · js/dropdown.js:86 — the two spans are one implementation copied and then locally edited — 95 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. — js/collapsible.js:58
- js/datepicker.js:912 · js/dropdown.js:558 — the two spans are one implementation copied and then locally edited — 75 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. — js/datepicker.js:912
- js/sidenav.js:69 · js/slider.js:100 — the two spans are one implementation copied and then locally edited — 83 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. — js/sidenav.js:69
- js/collapsible.js:172 · js/collapsible.js:206 — 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. — js/collapsible.js:172
- js/materialbox.js:51 · js/sidenav.js:69 — the two spans are one implementation copied and then locally edited — 79 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. — js/materialbox.js:51
- js/sidenav.js:69 · js/tabs.js:51 — the two spans are one implementation copied and then locally edited — 80 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. — js/sidenav.js:69
- js/datepicker.js:912 · js/tapTarget.js:265 — the two spans are one implementation copied and then locally edited — 61 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. — js/datepicker.js:912
- js/dropdown.js:84 · js/sidenav.js:69 — the two spans are one implementation copied and then locally edited — 73 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. — js/dropdown.js:84
- js/autocomplete.js:53 · js/characterCounter.js:29 · js/chips.js:70 · js/dropdown.js:84 · +10 more site(s) not listed — the 14 copies are spread across 14 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. — js/autocomplete.js:53
- js/modal.js:63 · js/parallax.js:32 · js/scrollspy.js:46 · js/tooltip.js:36 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — js/modal.js:63
- js/slider.js:82 · js/slider.js:276 — the two spans are one implementation copied and then locally edited — 71 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — js/slider.js:82
- js/carousel.js:149 · js/carousel.js:179 — 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. — js/carousel.js:149
- js/sidenav.js:222 · js/sidenav.js:289 — 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. — js/sidenav.js:222
- js/datepicker.js:204 · js/timepicker.js:89 — 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. — js/datepicker.js:204
- js/datepicker.js:765 · js/datepicker.js:778 — 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. — js/datepicker.js:765
- js/dropdown.js:493 · js/sidenav.js:547 — 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. — js/dropdown.js:493
- js/timepicker.js:344 · js/timepicker.js:360 — 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. — js/timepicker.js:344
- js/datepicker.js:719 · js/timepicker.js:108 — the two spans are one implementation copied and then locally edited — 83 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. — js/datepicker.js:719
- js/modal.js:124 · js/sidenav.js:172 — 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. — js/modal.js:124
- js/scrollspy.js:199 · js/scrollspy.js:225 — 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. — js/scrollspy.js:199
- js/tabs.js:299 · js/tabs.js:314 — 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. — js/tabs.js:299
- js/chips.js:115 · js/chips.js:128 — 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. — js/chips.js:115
- js/collapsible.js:135 · js/collapsible.js:185 — 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. — js/collapsible.js:135
- js/select.js:80 · js/select.js:93 — 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. — js/select.js:80
- js/buttons.js:90 · js/buttons.js:102 — 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. — js/buttons.js:90
- js/materialbox.js:338 · js/materialbox.js:408 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — js/materialbox.js:338
- js/modal.js:100 · js/modal.js:111 — 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. — js/modal.js:100
- js/dropdown.js:153 · js/dropdown.js:161 — 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. — js/dropdown.js:153
- js/tooltip.js:85 · js/tooltip.js:92 — 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. — js/tooltip.js:85
- js/sidenav.js:135 · js/sidenav.js:155 — 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. — js/sidenav.js:135
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
- _scroll has cyclomatic complexity 29 and cognitive complexity 41; 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. — js/carousel.js:462
- render has cyclomatic complexity 27 and cognitive complexity 32; 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. — js/datepicker.js:394
- setHand has cyclomatic complexity 24 and cognitive complexity 50; 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. — js/timepicker.js:487
- renderTitle has cyclomatic complexity 22 and cognitive complexity 29; 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. — js/datepicker.js:563
- _handleDropdownKeydown has cyclomatic complexity 21 and cognitive complexity 28; 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. — js/dropdown.js:257
- _calculatePositioning has cyclomatic complexity 18 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — js/tapTarget.js:177
- textareaAutoResize has cyclomatic complexity 17 and cognitive complexity 17; 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. — js/forms.js:50
- _handleChipsKeydown has cyclomatic complexity 14 and cognitive complexity 22; 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. — js/chips.js:165
- _getDropdownPosition has cyclomatic complexity 13 and cognitive complexity 24; 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. — js/dropdown.js:388
- _updateTimeFromInput has cyclomatic complexity 12 and cognitive complexity 16; 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. — js/timepicker.js:410
- _handleTabClick has cyclomatic complexity 11 and cognitive complexity 17; 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. — js/tabs.js:123
- validate_field has cyclomatic complexity 11 and cognitive complexity 15; 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. — js/forms.js:23
- _handleInputKeydown has cyclomatic complexity 11 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. — js/autocomplete.js:216
- _updatePosition has cyclomatic complexity 11 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. — js/pushpin.js:86
- draw 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. — js/datepicker.js:651
R3 · Large Files
- js/datepicker.js has 846 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — js/datepicker.js:1
- js/carousel.js has 635 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — js/carousel.js:1
- js/timepicker.js has 567 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — js/timepicker.js:1
- js/dropdown.js has 556 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — js/dropdown.js:1
- js/sidenav.js has 495 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — js/sidenav.js:1
- js/chips.js has 416 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — js/chips.js:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
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 eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 29 application, 1 tooling and 15 test entry point(s) detected in this repo. Nothing this repository declares compiles or type-checks these files, so a wrong deletion here would raise no compile error — gate removals on `npm test`, which loads the modules, and note that it only covers what it exercises. An undetected custom entry would make these reachable.
- no import path from any entry point (29 application, 1 tooling, 15 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — package.js, templates/masonry-template/js/init.js
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
S1 · Web-Security Posture
- `https://code.jquery.com/jquery-2.1.4.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 65 such include(s) across the repository's markup. — fab-toolbar-demo.html:36
What to do
- Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
X12 · Unreachable branch
X16 · Unfloored truncation loop
X21 · Side-effecting pattern guard
X24 · Document value interpolated into markup unescaped
- `el.getAttribute('label')` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the text of an element of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `el.getAttribute('label')` at this site, or validate it against the shape the position accepts before interpolating it. — js/select.js:209
- `iconUrl` carries text this program read out of a document — an attribute or a text node, which the DOM hands back already decoded, so an entity its author wrote is a live character again — and it is written straight into the `src` attribute of markup built here with nothing escaping it on the way. The value is chosen by whoever authored that document, not by this program, so it can close the attribute or element it sits in and open another — a crafted document becomes markup in what this code renders. Escape `iconUrl` at this site, or validate it against the shape the position accepts before interpolating it. — js/select.js:337
- `this.options.i18n.clear` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — js/datepicker.js:240
- `this.options.i18n.done` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — js/datepicker.js:243
- `this.options.i18n.cancel` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — js/datepicker.js:244
- ``${day}, ${month} ${date}`` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — js/datepicker.js:327
- `this.hours` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — js/timepicker.js:430
- `Timepicker._addLeadingZero(this.minutes)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — js/timepicker.js:431
- `Timepicker._addLeadingZero(value)` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — js/timepicker.js:551
- `this.message` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — js/toasts.js:209
- `this.options.html` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. (×2) — js/tooltip.js:71, js/tooltip.js:77
What to do
- Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X28 · Index access outside its own emptiness guard
X30 · Support guard that admits what it rejects
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 |
| AC4 · Keyboard semantics | 2.1.1, 2.4.3 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 33% | Weak — gated by R1, R3, IC1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Strongest area. |
| Maturity | 47% | Weak — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 46% | Weak — gated by R6, P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 86% | Strong | Solid. |
| Accessibility | 38% | Weak — gated by AC1, AC4, AC6 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
Unscored — 1 check(s) recorded observations but carry no score
- X10 Duplicated predicate — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- 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 dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> materialize-css@1.0.0 dev / > grunt monitor / sh: 1: grunt: not found" No runtime evidence was gathered. 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 — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — Test reliability not included — the test command names no runner the analyzer recognises
- D12 Dependency Hygiene — Dependency currency not established — no reader for this repository's lockfile format
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript, html 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
- D26 Project Cohesion — This repository is one build unit, `(repository root)` (9879 LoC, 33 module-visible types across 4 directories), within the size bounds. Not scored: a single unit of this size gives project cohesion nothing to grade.
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- 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.
- D4 Code Duplication — Duplication not measured — .html not exposed to the token comparison
- 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.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage not measured — the test command names no runner the analyzer recognises
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript source (1 module(s), 34 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R4 Test Coverage — 15 test file(s) reach none of 30 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
- 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
- X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X2 Cancellation propagation — 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.
- 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
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X3 Exception handling — 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. 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 — 186 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <img> without a text alternative jade/about/about_content.html:36
- <img> without a text alternative jade/about/about_content.html:43
- <img> without a text alternative jade/about/about_content.html:50
- <img> without a text alternative jade/about/about_content.html:64
- <img> without a text alternative jade/about/about_content.html:72
- <img> without a text alternative jade/about/about_content.html:84
- <img> without a text alternative jade/about/about_content.html:96
- <img> without a text alternative jade/about/about_content.html:108
- <img> without a text alternative jade/getting_started/getting_started_content.html:155
- <img> without a text alternative jade/getting_started/getting_started_content.html:163
- <img> without a text alternative jade/mobile/mobile_content.html:12
- <img> without a text alternative jade/mobile/mobile_content.html:21
- <img> without a text alternative jade/page-contents/cards_content.html:56
- <img> without a text alternative jade/page-contents/cards_content.html:106
- <img> without a text alternative jade/page-contents/cards_content.html:126
- <img> without a text alternative jade/page-contents/cards_content.html:170
- <img> without a text alternative jade/page-contents/cards_content.html:220
- <img> without a text alternative jade/page-contents/cards_content.html:263
- <img> without a text alternative jade/page-contents/cards_content.html:292
- <img> without a text alternative jade/page-contents/cards_content.html:437
- <img> without a text alternative jade/page-contents/cards_content.html:462
- <img> without a text alternative jade/page-contents/cards_content.html:487
- <img> without a text alternative jade/page-contents/carousel_content.html:14
- <img> without a text alternative jade/page-contents/carousel_content.html:17
- <img> without a text alternative jade/page-contents/carousel_content.html:20
- Document without a <title> jade/404.jade:5
- Document without a <title> jade/about.jade:5
- Document without a <title> jade/auto-init.jade:5
- Document without a <title> jade/autocomplete.jade:5
- Document without a <title> jade/badges.jade:5
- Document without a <title> jade/breadcrumbs.jade:5
- Document without a <title> jade/buttons.jade:5
- Document without a <title> jade/cards.jade:5
- Document without a <title> jade/carousel.jade:5
- Document without a <title> jade/checkboxes.jade:5
- Document without a <title> jade/chips.jade:5
- Document without a <title> jade/collapsible.jade:5
- Document without a <title> jade/collections.jade:5
- Document without a <title> jade/color.jade:5
- Document without a <title> jade/css-transitions.jade:5
- Document without a <title> jade/dropdown.jade:5
- Document without a <title> jade/feature-discovery.jade:5
- Document without a <title> jade/floating-action-button.jade:5
- Document without a <title> jade/footer.jade:5
- Document without a <title> jade/getting-started.jade:6
- Document without a <title> jade/grid.jade:5
- Document without a <title> jade/helpers.jade:5
- Document without a <title> jade/icons.jade:5
- Document without a <title> jade/index.jade:4
- Document without a <title> jade/media-css.jade:5
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- <select> without a programmatic label jade/page-contents/select_content.html:14
- <select> without a programmatic label jade/page-contents/select_content.html:28
- <select> without a programmatic label jade/page-contents/select_content.html:41
- <select> without a programmatic label jade/page-contents/select_content.html:59
- <select> without a programmatic label jade/page-contents/select_content.html:68
- <select> without a programmatic label jade/page-contents/select_content.html:83
- <select> without a programmatic label jade/page-contents/select_content.html:312
- <select> without a programmatic label jade/page-contents/select_content.html:324
- <select> without a programmatic label js/datepicker.js:595
- <select> without a programmatic label js/datepicker.js:613
- <label> that labels no control jade/page-contents/select_content.html:20
- <label> that labels no control jade/page-contents/select_content.html:34
- <label> that labels no control jade/page-contents/select_content.html:51
- <label> that labels no control jade/page-contents/select_content.html:65
- <label> that labels no control jade/page-contents/select_content.html:74
- <label> that labels no control jade/page-contents/select_content.html:82
- <label> that labels no control jade/page-contents/select_content.html:318
- <label> that labels no control jade/page-contents/select_content.html:323
- <input> without a programmatic label jade/_navbar.jade:26
- <input> without a programmatic label jade/page-contents/range_content.html:37
- <input> without a programmatic label jade/page-contents/text_inputs_content.html:300
- <input> without a programmatic label jade/page-contents/text_inputs_content.html:303
- <input> without a programmatic label jade/page-contents/text_inputs_content.html:326
- <input> without a programmatic label jade/page-contents/text_inputs_content.html:329
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Link with no accessible name jade/index/index_content.html:32
- Link with no accessible name templates/masonry-template/index.html:23
- Link with no accessible name templates/masonry-template/preview.html:23
- <iframe> without a title jade/_footer.html:19
- <iframe> without a title jade/about/about_content.html:30
- <iframe> without a title jade/getting_started/getting_started_content.html:85
- <button> with no accessible text js/datepicker.js:961
- <button> with no accessible text js/datepicker.js:962
- REDACTED
- REDACTED
Serious — 229 finding(s)
- Anchor without href fab-toolbar-demo.html:24
- Anchor without href jade/_navbar.jade:21
- Anchor without href jade/_navbar.jade:37
- Anchor without href jade/_navbar.jade:62
- Anchor without href jade/_navbar.jade:89
- Anchor without href jade/_navbar.jade:124
- Anchor without href jade/page-contents/buttons_content.html:10
- Anchor without href jade/page-contents/buttons_content.html:11
- Anchor without href jade/page-contents/buttons_content.html:12
- Anchor without href jade/page-contents/buttons_content.html:21
- Anchor without href jade/page-contents/buttons_content.html:33
- Anchor without href jade/page-contents/buttons_content.html:52
- Anchor without href jade/page-contents/buttons_content.html:53
- Anchor without href jade/page-contents/buttons_content.html:54
- Anchor without href jade/page-contents/buttons_content.html:66
- Anchor without href jade/page-contents/buttons_content.html:67
- Anchor without href jade/page-contents/buttons_content.html:68
- Anchor without href jade/page-contents/buttons_content.html:80
- Anchor without href jade/page-contents/buttons_content.html:81
- Anchor without href jade/page-contents/buttons_content.html:82
- Anchor without href jade/page-contents/buttons_content.html:83
- Anchor without href jade/page-contents/cards_content.html:108
- Anchor without href jade/page-contents/cards_content.html:127
- Anchor without href jade/page-contents/carousel_content.html:296
- Anchor without href jade/page-contents/featureDiscovery_content.html:12
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Animation without a prefers-reduced-motion guard sass/_style.scss:1194
- Animation without a prefers-reduced-motion guard sass/components/_collapsible.scss:84
- Animation without a prefers-reduced-motion guard sass/components/_global.scss:660
- Animation without a prefers-reduced-motion guard sass/components/_global.scss:673
- Animation without a prefers-reduced-motion guard sass/components/_global.scss:685
- Animation without a prefers-reduced-motion guard sass/components/_preloader.scss:49
- Animation without a prefers-reduced-motion guard sass/components/_preloader.scss:105
- Animation without a prefers-reduced-motion guard sass/components/_preloader.scss:111
- Animation without a prefers-reduced-motion guard sass/components/_preloader.scss:117
- Animation without a prefers-reduced-motion guard sass/components/_preloader.scss:123
- Animation without a prefers-reduced-motion guard sass/components/_preloader.scss:134
- Animation without a prefers-reduced-motion guard sass/components/_preloader.scss:287
- Animation without a prefers-reduced-motion guard sass/components/_preloader.scss:293
- Animation without a prefers-reduced-motion guard sass/components/_preloader.scss:323
- Animation without a prefers-reduced-motion guard sass/components/_pulse.scss:12
- Animation without a prefers-reduced-motion guard sass/components/_pulse.scss:13
- Animation without a prefers-reduced-motion guard sass/components/_tapTarget.scss:17
- Animation without a prefers-reduced-motion guard sass/components/_tapTarget.scss:27
- Animation without a prefers-reduced-motion guard sass/components/_tapTarget.scss:28
- Animation without a prefers-reduced-motion guard sass/components/_tapTarget.scss:45
- Animation without a prefers-reduced-motion guard sass/components/_tapTarget.scss:68
- Animation without a prefers-reduced-motion guard sass/components/_tapTarget.scss:72
- Animation without a prefers-reduced-motion guard sass/components/_timepicker.scss:106
- Animation without a prefers-reduced-motion guard sass/components/_transitions.scss:5
- Animation without a prefers-reduced-motion guard sass/components/_transitions.scss:12
- Focus outline removed in CSS without a :focus replacement sass/_style.scss:1198
- Focus outline removed in CSS without a :focus replacement sass/_style.scss:1232
- Focus outline removed in CSS without a :focus replacement sass/components/_buttons.scss:49
- Focus outline removed in CSS without a :focus replacement sass/components/_chips.scss:63
- Focus outline removed in CSS without a :focus replacement sass/components/_chips.scss:43
- Focus outline removed in CSS without a :focus replacement sass/components/_collapsible.scss:11
- Focus outline removed in CSS without a :focus replacement sass/components/_dropdown.scss:3
- Focus outline removed in CSS without a :focus replacement sass/components/_modal.scss:3
- Focus outline removed in CSS without a :focus replacement sass/components/forms/_input-fields.scss:31
- Focus outline removed in CSS without a :focus replacement sass/components/forms/_range.scss:24
- Focus outline removed in CSS without a :focus replacement sass/components/forms/_range.scss:18
- Untrusted text written into markup unescaped js/datepicker.js:240
- Untrusted text written into markup unescaped js/datepicker.js:243
- Untrusted text written into markup unescaped js/datepicker.js:244
- Untrusted text written into markup unescaped js/datepicker.js:327
- Untrusted text written into markup unescaped js/timepicker.js:430
- Untrusted text written into markup unescaped js/timepicker.js:431
- Untrusted text written into markup unescaped js/timepicker.js:551
- Untrusted text written into markup unescaped js/toasts.js:209
- Untrusted text written into markup unescaped js/tooltip.js:71
- Untrusted text written into markup unescaped js/tooltip.js:77
- Heading level jumps from h3 to h5 jade/getting_started/getting_started_content.html:30
- Heading level jumps from h3 to h5 jade/getting_started/getting_started_content.html:102
- Heading level jumps from h3 to h5 jade/getting_started/getting_started_content.html:154
- Heading level jumps from h3 to h5 jade/getting_started/getting_started_content.html:177
- Heading level jumps from h3 to h5 jade/getting_started/getting_started_content.html:201
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated block with local edits (22 matched lines × 2 locations) js/collapsible.js:58
- Duplicated block with local edits (22 matched lines × 2 locations) js/dropdown.js:84
- Duplicated block with local edits (22 matched lines × 2 locations) js/materialbox.js:51
- Duplicated block with local edits (22 matched lines × 2 locations) js/materialbox.js:51
- Duplicated block (11 lines × 2 locations) js/datepicker.js:204
- Duplicated block (11 lines × 2 locations) js/datepicker.js:765
- Duplicated block (11 lines × 2 locations) js/dropdown.js:493
- Duplicated block (11 lines × 2 locations) js/timepicker.js:344
- Heading level jumps from h1 to h4 jade/about/about_content.html:6
- Heading level jumps from h1 to h4 jade/getting_started/getting_started_content.html:6
- Heading level jumps from h1 to h4 jade/index/index_content.html:8
- TooManyMethods: Datepicker js/datepicker.js:112
- TooManyMethods: Timepicker js/timepicker.js:38
- TooManyMethods: Sidenav js/sidenav.js:19
- Duplicated block (10 lines × 2 locations) js/modal.js:124
- Duplicated block (10 lines × 2 locations) js/scrollspy.js:199
- Duplicated block (10 lines × 2 locations) js/tabs.js:299
- Duplicated block (9 lines × 2 locations) js/chips.js:115
- Duplicated block (9 lines × 2 locations) js/collapsible.js:135
- Duplicated block (9 lines × 2 locations) js/select.js:80
- Duplicated block with local edits (18 matched lines × 2 locations) js/datepicker.js:912
- Duplicated block with local edits (18 matched lines × 2 locations) js/sidenav.js:69
- Duplicated block with local edits (16 matched lines × 2 locations) js/materialbox.js:51
- Duplicated block with local edits (16 matched lines × 2 locations) js/sidenav.js:69
- Duplicated block with local edits (15 matched lines × 2 locations) js/datepicker.js:912
- Duplicated block with local edits (15 matched lines × 2 locations) js/dropdown.js:84
- Duplicated block (12 lines × 2 locations) js/carousel.js:149
- Duplicated block (12 lines × 2 locations) js/sidenav.js:222
- Duplicated block (6 lines × 2 locations) js/dropdown.js:153
- Duplicated block (6 lines × 2 locations) js/tooltip.js:85
- Document value reaches a markup attribute unescaped js/select.js:209
- Document value reaches a markup attribute unescaped js/select.js:337
- <video> without a captions track jade/page-contents/media-css_content.html:81
- Page without a main landmark fab-toolbar-demo.html:2
- Heading level jumps from h2 to h4 jade/about/about_content.html:76
- Low contrast colour pair in CSS (3.0:1) sass/_style.scss:980
- Low contrast colour pair in CSS (2.8:1) sass/components/_global.scss:551
- Carousel._scroll (cyclomatic 29) js/carousel.js:462
- Datepicker.render (cyclomatic 27) js/datepicker.js:394
- Timepicker.setHand (cyclomatic 24) js/timepicker.js:487
- Datepicker.renderTitle (cyclomatic 22) js/datepicker.js:563
- _handleDropdownKeydown (cyclomatic 21) js/dropdown.js:257
- TapTarget._calculatePositioning (cyclomatic 18) js/tapTarget.js:177
- forms.M.textareaAutoResize (cyclomatic 17) js/forms.js:50
- setHand (cognitive 50) js/timepicker.js:487
- _scroll (cognitive 41) js/carousel.js:462
- render (cognitive 32) js/datepicker.js:394
- renderTitle (cognitive 29) js/datepicker.js:563
- _handleDropdownKeydown (cognitive 28) js/dropdown.js:257
- _getDropdownPosition (cognitive 24) js/dropdown.js:388
- Chips._handleChipsKeydown (cognitive 22) js/chips.js:165
- Tabs._handleTabClick (cognitive 20) js/tabs.js:123
- _setupDropdown (cognitive 20) js/select.js:171
- _calculatePositioning (cognitive 20) js/tapTarget.js:177
- forms.M.textareaAutoResize (cognitive 17) js/forms.js:50
- Timepicker._buildHoursView (cognitive 16) js/timepicker.js:337
- _updateTimeFromInput (cognitive 16) js/timepicker.js:410
- FileTooLong: js/datepicker.js js/datepicker.js
- REDACTED
- Both branches are identical — the condition decides nothing js/tapTarget.js:229
- CI pipeline targets a decommissioned service
- Type Safety
- Duplicated block with local edits (31 matched lines × 2 locations) js/collapsible.js:1
- Duplicated block (25 lines × 2 locations) js/characterCounter.js:1
- Duplicated block (23 lines × 2 locations) js/autocomplete.js:52
- Duplicated block with local edits (23 matched lines × 2 locations) js/slider.js:100
- Duplicated block (21 lines × 2 locations) js/sidenav.js:482
- Duplicated block (20 lines × 3 locations) js/buttons.js:55
- Duplicated block with local edits (19 matched lines × 2 locations) js/collapsible.js:58
- Duplicated block (17 lines × 2 locations) js/collapsible.js:172
- Duplicated block (14 lines × 14 locations) js/autocomplete.js:53
- Duplicated block (14 lines × 4 locations) js/modal.js:63
- Duplicated block with local edits (14 matched lines × 2 locations) js/slider.js:82
- Duplicated block with local edits (10 matched lines × 2 locations) js/datepicker.js:719
- Duplicated block (8 lines × 2 locations) js/buttons.js:90
- Duplicated block with local edits (8 matched lines × 2 locations) js/materialbox.js:338
- Duplicated block (7 lines × 2 locations) js/modal.js:100
- Duplicated block (5 lines × 2 locations) js/sidenav.js:135
- Complex function _scroll (cyclomatic 29, cognitive 41) js/carousel.js:462
- Complex function render (cyclomatic 27, cognitive 32) js/datepicker.js:394
- Complex function setHand (cyclomatic 24, cognitive 50) js/timepicker.js:487
- Complex function renderTitle (cyclomatic 22, cognitive 29) js/datepicker.js:563
- Complex function _handleDropdownKeydown (cyclomatic 21, cognitive 28) js/dropdown.js:257
- Complex function _calculatePositioning (cyclomatic 18, cognitive 20) js/tapTarget.js:177
- Complex function textareaAutoResize (cyclomatic 17, cognitive 17) js/forms.js:50
- Complex function _handleChipsKeydown (cyclomatic 14, cognitive 22) js/chips.js:165
- Complex function _getDropdownPosition (cyclomatic 13, cognitive 24) js/dropdown.js:388
- Complex function _updateTimeFromInput (cyclomatic 12, cognitive 16) js/timepicker.js:410
- Complex function _handleTabClick (cyclomatic 11, cognitive 17) js/tabs.js:123
- Complex function validate_field (cyclomatic 11, cognitive 15) js/forms.js:23
- Complex function _handleInputKeydown (cyclomatic 11, cognitive 14) js/autocomplete.js:216
- Complex function _updatePosition (cyclomatic 11, cognitive 13) js/pushpin.js:86
- Complex function draw (cyclomatic 11, cognitive 12) js/datepicker.js:651
- js/datepicker.js: 846 lines of code js/datepicker.js:1
- js/carousel.js: 635 lines of code js/carousel.js:1
- js/timepicker.js: 567 lines of code js/timepicker.js:1
- js/dropdown.js: 556 lines of code js/dropdown.js:1
- js/sidenav.js: 495 lines of code js/sidenav.js:1
- js/chips.js: 416 lines of code js/chips.js:1
- No lint or typecheck script
- Dead file (~67 LoC) package.js
- Dead file (~16 LoC) templates/masonry-template/js/init.js
- Third-party script without Subresource Integrity fab-toolbar-demo.html:36
Minor — 42 finding(s)
- Orphaned file js/dropdown.js:1
- Orphaned file Gruntfile.js:1
- Orphaned file js/sidenav.js:1
- Orphaned file js/select.js:1
- Orphaned file js/global.js:1
- Orphaned file js/materialbox.js:1
- Orphaned file js/chips.js:1
- Orphaned file js/autocomplete.js:1
- Orphaned file js/tabs.js:1
- Orphaned file js/modal.js:1
- Orphaned file js/tapTarget.js:1
- Orphaned file js/buttons.js:1
- Orphaned file js/slider.js:1
- Orphaned file js/forms.js:1
- Orphaned file js/tooltip.js:1
- Orphaned file js/scrollspy.js:1
- Orphaned file js/toasts.js:1
- Orphaned file js/collapsible.js:1
- Orphaned file js/range.js:1
- Orphaned file js/parallax.js:1
- Orphaned file js/pushpin.js:1
- Orphaned file js/characterCounter.js:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Most significant orphaned file js/datepicker.js:1
- Most significant orphaned file js/carousel.js:1
- Most significant orphaned file js/timepicker.js:1
- redundant comment Gruntfile.js:615
- redundant comment docs/js/init.js:118
- Duplicated predicate js/global.js:178
- Duplicated predicate js/carousel.js:394
- REDACTED
- REDACTED
- Dormant codebase
- REDACTED
- No ADRs
- No architecture diagram/doc
- No src/ separation
- No SAST
- No dependency-update automation package.json:29
Minor — 1 finding(s)
- doc comments repeat the names js/autocomplete.js:67
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-ed75a93e7167454c98980d53336a6c33/history.json --exit-code 0 --source . | 62 | 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-ed75a93e7167454c98980d53336a6c33/tree.json --exit-code 0 --source . | 5 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude css --exclude dist --exclude extras --exclude jade/about --exclude jade/getting_started --exclude jade/index --exclude jade/mobile --exclude jade/page-contents --exclude jade/parallax --exclude jade/showcase --exclude test . | 0 | 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/** . | 125 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 1 | artifacts/raw/trivy-fs.json |