Public report of GoogleChrome/chrome-extensions-samples, published 15 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 15 November 2026, 04:17 UTC · Survey ID cd_15f807bd17e1483094bef2781b8b1dc9

GoogleChrome/chrome-extensions-samples

Measured 15 November 2026, 04:16 UTC, at code version 657a941

Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).

Knowledge freshness is not measured: Freshness signal contradicted by repo activity.

CAI score 43out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Up 1 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

A small codebase: 14,314 lines of product code in 9 projects, tests not counted · Estimated rebuild effort: under 0.1 person-years · Weakest lens: Accessibility, 30

Findings by how serious they are

99 critical 172 serious 107 minor

11 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
15 November 2026, 04:16 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

62of 62 dimensions measured by tools.
363of 378 findings point to an exact file and line, so you can open each one in the code. The other 15 concern the repository as a whole, such as missing documentation.
62dimensions across 7 lenses, read from 14,314 lines of product code in 9 projects.
Chapters

Executive summary

GoogleChrome/chrome-extensions-samples falls short of our standard for a template or a sample because it has controls that only work with a mouse and images with no text description. It scores 43 out of 100 and is rated Adequate, and five of its 99 critical findings are security problems.

Accessibility, at 30, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 5 points. Adding text alternatives comes next, worth about 4 points. Raising Accessibility to 58 would lift the score to about 51.

Twenty images have no description for people who can't see them. Eleven controls can't be used without a mouse, and thirty-six form fields can't be read by a screen reader. Making the controls work with a keyboard, describing the images and labelling the form fields would close these risks. Updating the vulnerable packages would fix the two packages with a known security hole, and the three passwords or keys in the code's history need replacing, with the old ones switched off. The 17 pages that don't say their language need their language set.

The product code is 14,314 lines, about €13,000 to rebuild.

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Accessibility 30 · counts for 46%Code Health 39 · counts for 25%Production Readiness 54 · counts for 14%Maturity 65 · counts for 8%Security and Compliance 79 · counts for 4%Architecture 93 · counts for 2%Performance 100 · counts for 1%

If Accessibility rose from 30 to 58, the lowest score rated Strong, the score would rise from 43 to about 51.

Code composition: what the lines of code are
Product code 99%Tests 1%
New since the last survey: 40 findings

These 40 critical or serious findings weren't in the previous survey, on 29 October 2026.

We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 570 findings

These 570 critical or serious findings were in the previous survey, on 29 October 2026, and are gone from this one. The first 100 are listed here.

  • REDACTED Scanning · Leaked secret: private-key functional-samples/ai.gemini-on-device-alt-texter/manifest.json
  • REDACTED Scanning · Leaked secret: private-key functional-samples/ai.gemini-on-device-audio-scribe/manifest.json
  • Secrets (history) · REDACTED: REDACTED appsquare/key.txt
  • Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
  • Documentation (README) · README may be stale
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Exception handling · Swallowed exception (empty catch) REDACTED
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/zoom/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/zoom/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/zoom/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/zoom/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/api/tabs/zoom/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/app_launcher/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/constant_context/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/download_images/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/download_images/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/gdocs/options.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/gdocs/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/gdocs/popup.html
  • Forms & labels · <textarea> without a programmatic label _archive/mv2/extensions/gdocs/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/gdocs/popup.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/irc/servlet/addChannel.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/irc/servlet/addChannel.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/irc/servlet/addServer.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/irc/servlet/addServer.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/irc/servlet/addServer.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/irc/servlet/index.html
  • Forms & labels · Custom control with no accessible name on <body> _archive/mv2/extensions/irc/servlet/notification.html
  • Forms & labels · <textarea> without a programmatic label _archive/mv2/extensions/news/javascript/options.js
  • Forms & labels · <textarea> without a programmatic label _archive/mv2/extensions/news/javascript/options.js
  • Forms & labels · Clickable <a> with no accessible name _archive/mv2/extensions/news/views/feed.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/news/views/feed.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <button> with no accessible text _archive/mv2/extensions/news/views/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/optional_permissions/newtab.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/proxy_configuration/popup.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/proxy_configuration/popup.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/proxy_configuration/popup.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/proxy_configuration/popup.html
  • Forms & labels · <fieldset> without a <legend> _archive/mv2/extensions/proxy_configuration/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/speak_selection/options.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/talking_alarm_clock/popup.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/talking_alarm_clock/popup.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/talking_alarm_clock/popup.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/talking_alarm_clock/popup.html
  • Forms & labels · <textarea> without a programmatic label _archive/mv2/extensions/talking_alarm_clock/popup.html
  • Forms & labels · <textarea> without a programmatic label _archive/mv2/extensions/ttsdemo/ttsdemo.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/ttsdemo/ttsdemo.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/ttsdemo/ttsdemo.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/extensions/ttsdemo/ttsdemo.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/ttsdemo/ttsdemo.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/ttsdemo/ttsdemo.html
  • Forms & labels · <input> without a programmatic label _archive/mv2/extensions/ttsdemo/ttsdemo.html
  • Forms & labels · <button> with no accessible text _archive/mv2/tutorials/broken_background_color/popup.html
  • Forms & labels · <button> with no accessible text _archive/mv2/tutorials/get_started/popup.html
  • Forms & labels · <button> with no accessible text _archive/mv2/tutorials/get_started_complete/popup.html
  • Forms & labels · <select> without a programmatic label _archive/mv2/tutorials/getstarted/popup.html
  • Forms & labels · <input> without a programmatic label api-samples/alarms/index.html
  • Forms & labels · <input> without a programmatic label api-samples/alarms/index.html
  • Forms & labels · <select> without a programmatic label api-samples/alarms/index.html
  • Forms & labels · <input> without a programmatic label api-samples/alarms/index.html
  • Forms & labels · <fieldset> without a <legend> api-samples/contentSettings/popup.html
  • Forms & labels · <input> without a programmatic label api-samples/downloads/download_links/popup.html
  • Forms & labels · <input> without a programmatic label api-samples/downloads/download_links/popup.html
  • Forms & labels · <input> without a programmatic label api-samples/downloads/download_manager/popup.html
  • Forms & labels · Link with no accessible name api-samples/downloads/download_manager/popup.html
  • Forms & labels · Link with no accessible name api-samples/downloads/download_manager/popup.html
  • Forms & labels · Link with no accessible name api-samples/downloads/download_manager/popup.html
  • Forms & labels · <select> without a programmatic label api-samples/fontSettings/fontSettings Advanced/options.html
  • Forms & labels · <select> without a programmatic label api-samples/fontSettings/fontSettings Advanced/options.html
  • Forms & labels · <select> without a programmatic label api-samples/fontSettings/fontSettings Advanced/options.html
  • Forms & labels · <select> without a programmatic label api-samples/fontSettings/fontSettings Advanced/options.html
  • Forms & labels · <select> without a programmatic label api-samples/fontSettings/fontSettings Advanced/options.html
  • Forms & labels · <input> without a programmatic label api-samples/history/historyOverride/history.html
  • Forms & labels · <textarea> without a programmatic label api-samples/identity/index.html
  • Forms & labels · <select> without a programmatic label api-samples/idle/history.html
  • Forms & labels · <input> without a programmatic label api-samples/nativeMessaging/extension/main.html
  • Forms & labels · <textarea> without a programmatic label api-samples/storage/stylizr/options.html
Rebuild cost: about €13,000 · Estimate
Cost to rebuild€4,200 to €21,000, for 69 to 220 hours of work, under 0.1 person-years for one engineer
Difficulty of the problemStandard, 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 43. 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.
SizeSmall: 14,314 lines of product code
What it is notNot 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.

How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 5 points · Medium effort · Keyboard semantics
2
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.
Raises the score by about 4 points · Medium effort · Text alternatives
3
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.
Raises the score by about 4 points · Medium effort · Type Safety

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €13,000 to build again, under 0.1 person-years of work. Its weakest lens is Accessibility, at 30 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

At a glance — Code Health · 39% · Weak · gated by R1, X5 ·

At a glance — Architecture · 93% · Exemplary ·

At a glance — Maturity · 65% · Adequate · gated by M2 ·

At a glance — Readiness · 54% · Adequate · gated by P3, P6 ·

At a glance — Security · 79% · Checked 3 of 9 ·

At a glance — Accessibility · 30% · Weak · gated by AC1, AC3, AC4 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures27High / Critical
A07:2025 — Authentication Failures4High / Critical
A05:2025 — Injection3Medium

Roadmap

Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; 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; 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.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.+5.1 ptsMediumKeyboard 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.+4.3 ptsMediumText alternatives
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.+3.5 ptsMediumType Safety
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.+3.3 ptsMediumPage structure
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.+1.5 ptsLowDocumentation Quality
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.+2.6 ptsMediumVisual & motion safety
Resolve the 2 No assertions finding(s) in Test Quality — start with index.test.js (2).+1.3 ptsLowTest Quality
Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with index.test.js (2).+1.3 ptsLowTest Quality

File quality

Per-file score 0–10 — a quality signature. Of 39 files carrying findings, judged against the Template bar: 0% slop · 15% mixed · 85% near-clean.

FileScoreBandWorst signal
REDACTED4.1MixedDependency Vulnerabilities: High CVE: REDACTED
REDACTED5.4MixedDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED5.4MixedDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED5.4MixedDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED5.8MixedSecrets (history): REDACTED: REDACTED
api-samples/downloads/download_manager/popup.js5.9MixedCyclomatic Complexity: DownloadItem.render (cyclomatic 39)
REDACTED6.2Near-cleanDependency Vulnerabilities: Medium CVE: REDACTED
REDACTED6.5Near-cleanDependency Vulnerabilities: High CVE: REDACTED
_archive/mv2/extensions/irc/servlet/src/org/chromium/IRCProxyWebSocket.java6.6Near-cleanExplicit Debt: TodoComment
REDACTED7.2Near-cleanSecrets (history): REDACTED: REDACTED
functional-samples/tutorial.terminate-sw/selenium/index.test.js7.8Near-cleanTest Quality: No assertions: can message service worker when terminated
functional-samples/tutorial.terminate-sw/puppeteer/index.test.js7.8Near-cleanTest Quality: No assertions: can message service worker when terminated
REDACTED7.9Near-cleanStatic Analysis (SAST): Medium: REDACTED
REDACTED7.9Near-cleanStatic Analysis (SAST): Medium: REDACTED
REDACTED7.9Near-cleanStatic Analysis (SAST): Medium: REDACTED
REDACTED7.9Near-cleanDependency Vulnerabilities: Medium CVE: REDACTED
_archive/apps/samples/dart/dart/balls.dart8.2Near-cleanExplicit Debt: TodoComment
api-samples/fontSettings/fontSettings Advanced/js/cr.js8.5Near-cleanCognitive Complexity: (anonymous).getSetter (cognitive 24)
api-samples/downloads/download_links/popup.js8.5Near-cleanCognitive Complexity: filterLinks (cognitive 20)
functional-samples/sample.bookmarks/popup.js8.5Near-cleanCognitive Complexity: dumpNode (cognitive 19)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 99

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.

Serious — 172

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.

Minor — 107

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 11

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 62 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.

What we checked — 62 dimensions across the health lenses
D1D2D3D5D6D10D11D12D13D14D15D16D17D19D24D26D28D29D30D35D43AC1AC2AC3AC4AC5AC6AX10AX3AX4GD1IC1M1M2M3M4P1P10P2P3P6PF3R1R10R11R2R3R5R6R7R8R9S1X1X12X16X2X21X24X29X3X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 363 of 378 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1dd6c-12b0-7d4c-a99f-97156898b1cf.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • 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. Most of this repository's production source (.cpp, .ino, .pl) was not read by duplication detection: no source of those file kinds was exposed to the token comparison by any language model this pass could load. Duplication in .js is measured by R10 Code Duplication and is not part of this gap.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its crate dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
  • 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
  • D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D26 Project Cohesion — 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. Project size and spread are measured over build units whose source a code model reads. This repository's .cpp, .ino source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
  • D28 Secrets (history) — 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. D28's config-credential rule (WD-SECRET-0002) parses each committed `.json` config as a document and reads credential-named values; `_archive/mv2/extensions/news_i18n/_locales/es/messages.json` did not parse (JSON5, a template, several concatenated documents), so a credential bound there is UNMEASURED by that rule. gitleaks still scanned the same files as text.
  • D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 54 commits in the last 90 days, yet 37 of 44 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
  • 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.
  • AC2 Forms & labels — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 125 further occurrence(s) are not listed individually; the score already reflects all 165.
  • 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. 349 further occurrence(s) are not listed individually; the score already reflects all 389.
  • 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. 103 further occurrence(s) are not listed individually; the score already reflects all 143.
  • 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 (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
  • 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.
  • P2 Observability — 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.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.

Repo exclusion declarations: 8 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • 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.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 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").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • 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 Complexity8.8 / 10Strong✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.8 / 10 · rule-coverage 100% · ceiling Prevented

2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was DownloadItem.render at 39.

DownloadItem.render (cyclomatic 39)api-samples/downloads/download_manager/popup.js:306

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with DownloadItem.render (cyclomatic 39). — Refactoring it lifts Cyclomatic Complexity from 8.8 to about 10.0/10.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity8.0 / 10Strong✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 8.0 / 10 · rule-coverage 100% · ceiling Prevented

9 method(s) exceeded the cognitive complexity threshold of 15; the worst was render at 49.

helloworld_demo.__wbg_load (cognitive 16) · ×2functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:131
render (cognitive 49)api-samples/downloads/download_manager/popup.js:306
(anonymous).getSetter (cognitive 24)api-samples/fontSettings/fontSettings Advanced/js/cr.js:146
filterLinks (cognitive 20)api-samples/downloads/download_links/popup.js:52
dumpNode (cognitive 19)functional-samples/sample.bookmarks/popup.js:29

+ 1 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with render (cognitive 49). — Refactoring it lifts Cognitive Complexity from 8.0 to about 8.6/10.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

9 production modules (Cargo+npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations, and main-sequence distance (abstractness) is not computed for these modules yet.

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)7.6 / 10Strong✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 7.6 / 10 · rule-coverage 100% · ceiling Verified

1 of 5 classes have LCOM4 above 3.

Low cohesion: DownloadItem (LCOM4 5)api-samples/downloads/download_manager/popup.js:174

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D10 · Test Quality6.2 / 10Adequate✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 6.2 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 2 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3 tests.

No assertions: can message service worker when terminated · ×2functional-samples/tutorial.terminate-sw/selenium/index.test.js:75
Test project verifies nothing: functional-samples/tutorial.terminate-sw/puppeteer · ×2functional-samples/tutorial.terminate-sw/puppeteer/index.test.js:57

What to do

  1. Resolve the 2 No assertions finding(s) in Test Quality — start with index.test.js (2). — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 2 Test project verifies nothing finding(s) in Test Quality — start with index.test.js (2). — One of this dimension's main actionable groups (2 warning-level).

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 flaky across 1 measured tier(s). JavaScript/TypeScript (mocha via `npm ci --ignore-scripts` in .repo/sample-list-generator/ (17 tests); jest via `npm ci --ignore-scripts` in functional-samples/tutorial.puppeteer/ (0 tests); jest via `npm ci --ignore-scripts` in functional-samples/tutorial.terminate-sw/puppeteer/ (0 tests); jest via `npm ci --ignore-scripts` in functional-samples/tutorial.terminate-sw/selenium/ (1 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

D12 · Dependency Hygiene9.9 / 10Exemplary✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.9 / 10 · rule-coverage 100% · ceiling Verified

2 outdated, 0 yanked direct Cargo dependencies. Only DIRECT edges are graded: a transitive crate cannot be moved past what its parent's requirement admits, so reporting one would be advice its owner cannot take. A newer release is reported only where this repository's OWN requirement already admits it, so the remedy is `cargo update` and never a manifest edit — which means a release outside the declared range is deliberately NOT charged, because a written-down constraint is a decision rather than a defect. Note that a bare requirement is a CARET, and for a 0.x crate its ceiling is the minor. Whether any crate is UNMAINTAINED is not graded — crates.io publishes no maintenance status, and release age does not stand in for one. Known CVEs in this dependency graph are D30's question, read from Cargo.lock there.

Outdated: wasm-bindgen · ×2

✓ On the Gold path — maintain.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets. 2 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 15 shipped crate(s) use a banned license. Licences were resolved from crates.io over the crates a consumer compiles — this repository's Cargo.lock closed over its manifests' `[dependencies]` and `[build-dependencies]`. Crates it asks for ONLY under `[dev-dependencies]` are excluded: they are not compiled by anything that depends on this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's crate dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D16 · Bus Factor8.6 / 10Strong✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Documented

6 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is api-samples/downloads/download_manager/popup.js. Counted over 43 of the 190 production source files in this repository: 146 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.

Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)

What to do

  1. Resolve the 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.

D17 · Explicit Debt9.6 / 10Stronggated by 5 serious findings✓ Tool-verified

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Prevented

5 deducted task-comment markers across 710 LoC (0.2/KLoC) → score 9.6. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×5_archive/mv2/extensions/irc/servlet/src/org/chromium/IRCProxyWebSocket.java:70

What to do

  1. Resolve the 5 TodoComment finding(s) in Explicit Debt — start with IRCProxyWebSocket.java (4), balls.dart. — One of this dimension's main actionable groups (5 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D19 · Documentation Quality5.0 / 10Adequate✓ Tool-verified

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 5.0 / 10 · rule-coverage 100% · ceiling Documented

1 of 2 documentation facets pass in full; short on: F4 map. 106 document(s) read across 10 unit(s).

Documentation: no map of the repository's partsREADME.md:1

What to do

  1. Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.

D24 · Comment Value5.9 5.8 / 10Adequate✓ Tool-verified

What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).

Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.

Maturity: Documented → Verified → Prevented · effective 5.8 / 10 · rule-coverage 97% · ceiling Documented

16 of 394 judged comments only repeat the code they sit on (4.1 %). 12 comment(s) in another language or script were not judged.

redundant comment · ×16api-samples/bookmarks/popup.js:67
doc comments repeat the names · ×2api-samples/fontSettings/fontSettings Advanced/js/cr.js:20

What to do

  1. Resolve the 16 redundant comment finding(s) in Comment Value — start with service-worker.js (3), script.js (3), background.js (3). — One of this dimension's main actionable groups (16 recommendation-level).

Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.

D26 · Project Cohesion7.5 / 10Strong✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic.

Maturity: Documented → Verified → Prevented · effective 7.5 / 10 · rule-coverage 100% · ceiling Documented

1 of 8 build units (Cargo, npm) flagged as possibly oversized/incoherent. This repository's .cpp, .ino source was read by no build unit, so this covers part of the tree, not all of it.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 7.0 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED

What to do

  1. Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.

D29 · Static Analysis (SAST)8.6 / 10Strong✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Documented

3 finding(s): 0 critical, 0 high, 3 medium, 0 low. semgrep hit a parse error in 14 file(s) — `.repo/sample-list-generator/src/libs/api-detector.ts` (lines 15–18, line 18), `_archive/apps/samples/analytics/google-analytics-bundle.js`, `_archive/apps/samples/dart/dart/clock.dart.precompiled.js`, `_archive/apps/samples/mini-code-edit/cm/doc/manual.html` (lines 48–50), `_archive/apps/samples/mini-code-edit/cm/mode/coffeescript/index.html` (lines 62–242, lines 246–247, lines 248–252, …), … (+9 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities7.9 / 10Adequategated by 2 critical findings✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 7.9 / 10 · rule-coverage 100% · ceiling Documented

27 finding(s): 0 critical, 2 high, 17 medium, 8 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  2. Resolve the 17 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (17). — One of this dimension's main actionable groups (17 warning-level).
  3. Resolve the 8 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 recommendation-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AC1 · Text alternatives2.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

  • A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content. (×3) — _archive/mv2/api/pageAction/set_icon/background.html:6, _archive/mv2/extensions/imageinfo/info.html:23, _archive/mv2/extensions/talking_alarm_clock/popup.html:113
  • An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×20) — _archive/mv2/api/processes/show_tabs/popup.js:55, _archive/mv2/api/storage/stylizr/options.html:29, _archive/mv2/api/tabs/screenshot/screenshot.html:6, …

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 & labels4.4 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×32) — _archive/mv2/api/bookmarks/basic/popup.html:8, _archive/mv2/api/cookies/manager.html:28, _archive/mv2/api/downloads/download_links/popup.html:12, …
  • A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. — _archive/mv2/api/contentSettings/popup.html:11
  • 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. (×4) — _archive/mv2/api/downloads/download_links/popup.html:6, _archive/mv2/api/history/historyOverride/history.html:9, _archive/mv2/api/i18n/detectLanguage/popup.html:13, …
  • 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) — _archive/mv2/api/downloads/download_manager/popup.html:18, _archive/mv2/api/downloads/download_manager/popup.html:30, _archive/mv2/api/downloads/download_manager/popup.html:43

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 structure3.2 / 10Weak✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×17) — _archive/mv2/api/bookmarks/basic/popup.html:1, _archive/mv2/api/browserAction/set_page_color/popup.html:2, _archive/mv2/api/browsingData/basic/popup.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>. (×6) — _archive/mv2/api/bookmarks/basic/popup.html:1, _archive/mv2/api/cookies/manager.html:1, _archive/mv2/api/debugger/live-headers/headers.html:7, …
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×12) — _archive/mv2/api/bookmarks/basic/popup.html:1, _archive/mv2/api/browserAction/set_page_color/popup.html:2, _archive/mv2/api/contentSettings/popup.html:2, …
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="container">, so there is no content here to wrap — render the <main> from the component mounted into it. — _archive/mv2/api/debugger/live-headers/headers.html:7
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="deviceinfos">, so there is no content here to wrap — render the <main> from the component mounted into it. — _archive/mv2/api/deviceInfo/basic/popup.html:1
  • No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="deviceList">, so there is no content here to wrap — render the <main> from the component mounted into it. — _archive/mv2/api/displaySource/tabCast/main.html:7
  • A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope). — _archive/mv2/api/downloads/download_filename_controller/options.html:10
  • An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>. — _archive/mv2/api/downloads/download_manager/popup.html:2

What to do

  • Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

  • A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — _archive/mv2/api/i18n/getMessage/popup.html:18
  • An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. (×3) — _archive/mv2/api/processes/show_tabs/popup.js:58, _archive/mv2/extensions/gdocs/popup.html:95, _archive/mv2/extensions/gdocs/popup.html:96
  • 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. (×9) — _archive/mv2/api/topsites/magic8ball/newTab.html:19, _archive/mv2/extensions/calendar/views/options.html:17, _archive/mv2/extensions/news/javascript/feed.js:198, …
  • A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. (×3) — _archive/mv2/extensions/irc/servlet/index.html:381, _archive/mv2/extensions/irc/servlet/index.html:389, _archive/mv2/extensions/irc/servlet/notification.html:56
  • A script attaches a click listener to this <img>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. — _archive/mv2/extensions/mappy/popup.html:8
  • The repo's own CSS styles .label with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×3) — api-samples/tabs/inspector/window_and_tabs_manager.html:76, api-samples/tabs/inspector/window_and_tabs_manager.html:86, api-samples/tabs/inspector/window_and_tabs_manager.html:90
  • The repo's own CSS styles .chat-item with `cursor: pointer`, so this <li> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler. (×3) — functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/index.html:16, functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/index.html:20, functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/index.html:24

What to do

  • Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
AC5 · ARIA correctness10.0 / 10Exemplary○ Nothing flagged

Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.

Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

AC6 · Visual & motion safety4.1 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

  • `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. (×4) — _archive/mv2/api/contextMenus/global_context_search/options.html:12, _archive/mv2/extensions/constant_context/popup.html:12, _archive/mv2/extensions/download_images/popup.html:12, …
  • `#apply-settings:enabled` sets color: #fbfafb on background-color: #4f7dd6 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — _archive/mv2/api/fontSettings/options.html:140, api-samples/fontSettings/fontSettings Advanced/options.html:155
  • `button` 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. (×10) — _archive/mv2/api/water_alarm_notification/popup.html:19, _archive/mv2/tutorials/broken_background_color/options.html:8, _archive/mv2/tutorials/broken_background_color/popup.html:8, …
  • `#title` sets color: white on background-color: #AAAAAA — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/mv2/extensions/irc/servlet/notification.html:21
  • `body.nooutline *` 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. — _archive/mv2/extensions/talking_alarm_clock/popup.html:99
  • `input#todo_value ~ input[type="submit"]` sets color: white on background-color: #4285F4 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — functional-samples/sample.optional_permissions/style.css:119, _archive/mv2/extensions/optional_permissions/style.css:99
  • `.ui-state-active, .ui-widget-content .ui-state-active, .ui-widget-header .ui-state-active, a.ui-button:active, .ui-button:active, .ui-button.ui-state-active:hover` sets color: #ffffff on background-color: #007fff — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — functional-samples/sample.bookmarks/third-party/jquery-ui.css:982, functional-samples/sample.bookmarks/third-party/jquery-ui.theme.css:113
  • `.result` sets color: white on background-color: #00aabb — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — functional-samples/ai.gemini-on-device-summarization/sidepanel/index.css:52
  • `#send-button` sets color: white on background-color: #007bff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/style.css:173
  • `.addButton` sets color: white on background-color: #aaaaaa — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/mv2/extensions/irc/servlet/styles.css:39
  • `.channelControls .removeButton` sets color: #999999 on background-color: white — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/mv2/extensions/irc/servlet/styles.css:96
  • `#entryText` sets color: white on background-color: #777777 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/mv2/extensions/irc/servlet/styles.css:149
  • `b, em, h3 a:link, h3 a:visited, h3 a:hover, li cite, div.crl` sets color: #000 on background-color: #000 — 1.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webview-samples/insert-css/inject.css:38
  • `.label, .badge` sets color: #ffffff on background-color: #999999 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:747
  • `.control-group.warning .input-prepend .add-on, .control-group.warning .input-append .add-on` sets color: #c09853 on background-color: #fcf8e3 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:1466
  • `.control-group.error .input-prepend .add-on, .control-group.error .input-append .add-on` sets color: #b94a48 on background-color: #f2dede — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:1500
  • `.control-group.info .input-prepend .add-on, .control-group.info .input-append .add-on` sets color: #3a87ad on background-color: #d9edf7 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:1568
  • `.btn-warning:hover, .btn-warning:active, .btn-warning.active, .btn-warning.disabled, .btn-warning[disabled]` sets color: #ffffff on background-color: #f89406 — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:2076
  • `.btn-success:hover, .btn-success:active, .btn-success.active, .btn-success.disabled, .btn-success[disabled]` sets color: #ffffff on background-color: #51a351 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:2138
  • `.btn-info:hover, .btn-info:active, .btn-info.active, .btn-info.disabled, .btn-info[disabled]` sets color: #ffffff on background-color: #2f96b4 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:2169
  • `.nav-list > .active > a, .nav-list > .active > a:hover` sets color: #ffffff on background-color: #0088cc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:2970
  • `.nav-pills > .active > a, .nav-pills > .active > a:hover` sets color: #ffffff on background-color: #0088cc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:3050
  • `.nav-tabs .open .dropdown-toggle, .nav-pills .open .dropdown-toggle, .nav > li.dropdown.open.active > a:hover` sets color: #ffffff on background-color: #999999 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:3131
  • `.navbar .btn-navbar:hover, .navbar .btn-navbar:active, .navbar .btn-navbar.active, .navbar .btn-navbar.disabled, .navbar .btn-navbar[disabled]` sets color: #ffffff on background-color: #e5e5e5 — 1.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:3513
  • `.pager .disabled a, .pager .disabled a:hover, .pager .disabled span` sets color: #999999 on background-color: #fff — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — _archive/apps/samples/webserver/styles/bootstrap.css:3869

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 composition10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs5.0 / 10Adequate✓ Tool-verified

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • `clearDisplay` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — api-samples/alarms/index.js:164
  • `checkState` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — api-samples/idle/history.js:42
  • `showAltText` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/ai.gemini-on-device-alt-texter/popup.js:26
  • `showSummary` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/ai.gemini-on-device-summarization/sidepanel/index.js:94
  • `updateWarning` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/ai.gemini-on-device-summarization/sidepanel/index.js:98
  • `reset` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/ai.gemini-on-device/sidepanel/index.js:33
  • `addToClipboardV2` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/cookbook.offscreen-clipboard-write/background.js:47
  • `handleMessages` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×3) — functional-samples/cookbook.offscreen-clipboard-write/offscreen.js:28, functional-samples/cookbook.offscreen-dom/background.js:46, functional-samples/cookbook.offscreen-dom/offscreen.js:22
  • `handleClipboardWrite` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/cookbook.offscreen-clipboard-write/offscreen.js:55
  • `handleAddExclamationMarkResult` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/cookbook.offscreen-dom/background.js:63
  • `__wbg_init_memory` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:178
  • `co2MeterConnected` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/sample.co2meter/background.js:34
  • `broadcastMessage` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/sample.co2meter/background.js:50
  • `init` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/sample.co2meter/modules/co2_meter.js:46
  • `stopRecording` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — functional-samples/sample.tabcapture-recorder/offscreen.js:80

What to do

  • Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)8.7 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation2.0 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure8.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability5.2 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • Only 2/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `_archive/apps/samples/dart`, `functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm`, `functional-samples/cookbook.wasm-helloworld-print/wasm`.
  • `functional-samples/tutorial.websockets/service-worker.js` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.websockets/service-worker.js:27
  • `functional-samples/tutorial.websockets/service-worker.js` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.websockets/service-worker.js:32
  • `functional-samples/tutorial.websockets/service-worker.js` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.websockets/service-worker.js:47
  • `functional-samples/tutorial.quick-api-reference/sw-omnibox.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.quick-api-reference/sw-omnibox.js:1
  • `functional-samples/tutorial.quick-api-reference/sw-tips.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.quick-api-reference/sw-tips.js:1
  • `functional-samples/tutorial.open-api-reference/sw-omnibox.js` reports through `console.*` at line 3 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.open-api-reference/sw-omnibox.js:3
  • `functional-samples/tutorial.open-api-reference/sw-tips.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.open-api-reference/sw-tips.js:1
  • `functional-samples/tutorial.hello-world/popup.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.hello-world/popup.js:1
  • `functional-samples/tutorial.getting-started/background.js` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.getting-started/background.js:5
  • `functional-samples/tutorial.broken-color/service-worker.js` reports through `console.*` at line 19 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/tutorial.broken-color/service-worker.js:19
  • `functional-samples/sample.co2meter/background.js` reports through `console.*` at line 67 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/sample.co2meter/background.js:67
  • `functional-samples/sample.co2meter/background.js` reports through `console.*` at line 113 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/sample.co2meter/background.js:113
  • `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 58 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/sample.co2meter/modules/co2_meter.js:58
  • `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 63 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/sample.co2meter/modules/co2_meter.js:63
  • `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 76 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/sample.co2meter/modules/co2_meter.js:76
  • `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 104 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/sample.co2meter/modules/co2_meter.js:104
  • `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/sample.co2meter/modules/co2_meter.js:110
  • `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 126 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/sample.co2meter/modules/co2_meter.js:126
  • `functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 139 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:139
  • `functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 173 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:173
  • `functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 176 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:176
  • `functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 132 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:132
  • `functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 166 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:166
  • `functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 169 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:169
  • `functional-samples/cookbook.sidepanel-site-specific/service-worker.js` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.sidepanel-site-specific/service-worker.js:20
  • `functional-samples/cookbook.sidepanel-global/sidepanel.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.sidepanel-global/sidepanel.js:1
  • `functional-samples/cookbook.push/background.js` reports through `console.*` at line 31 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.push/background.js:31
  • `functional-samples/cookbook.push/background.js` reports through `console.*` at line 34 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.push/background.js:34
  • `functional-samples/cookbook.push/background.js` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.push/background.js:44
  • `functional-samples/cookbook.push/background.js` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.push/background.js:48
  • `functional-samples/cookbook.push/background.js` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.push/background.js:53
  • `functional-samples/cookbook.push/background.js` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.push/background.js:54
  • `functional-samples/cookbook.permissions-addhostaccessrequest/background.js` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.permissions-addhostaccessrequest/background.js:45
  • `functional-samples/cookbook.offscreen-user-media/background.js` reports through `console.*` at line 93 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.offscreen-user-media/background.js:93
  • `functional-samples/cookbook.offscreen-user-media/offscreen/offscreen.js` reports through `console.*` at line 48 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.offscreen-user-media/offscreen/offscreen.js:48
  • `functional-samples/cookbook.offscreen-dom/background.js` reports through `console.*` at line 59 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.offscreen-dom/background.js:59
  • `functional-samples/cookbook.offscreen-dom/background.js` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.offscreen-dom/background.js:64
  • `functional-samples/cookbook.geolocation-offscreen/offscreen.js` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — functional-samples/cookbook.geolocation-offscreen/offscreen.js:28
  • `api-samples/webRequest/http-auth/service-worker.js` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — api-samples/webRequest/http-auth/service-worker.js:18

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/dependabot-auto-merge.yml:10
  • `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `cargo`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — .github/dependabot.yml:2

What to do

  • Add a SAST step to CI running what this repository's stack ships: the Dart analyzer's security lints plus `semgrep --config=auto` — so a security regression fails the build instead of landing.
  • Dependabot is configured but does not watch `cargo` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene3.0 / 10Weak✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

R1 · Type Safety0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 0 typed · 190 plain JS — the untyped files are api-samples/action/background.js, api-samples/alarms/background.js, api-samples/alarms/bg-wrapper.js, api-samples/alarms/index.js, api-samples/bookmarks/popup.js, api-samples/browsingData/popup.js (+184 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 Duplication7.8 / 10Strong✓ Tool-verified

React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.

  • 8 duplicated blocks under functional-samples/ have copies in at least two of the sibling directories ai.gemini-in-the-cloud, ai.gemini-on-device, cookbook.geolocation-contentscript, cookbook.geolocation-offscreen, cookbook.geolocation-popup, cookbook.sidepanel-open (+5 more sibling(s) not listed) — 7 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:18
  • functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:18 · functional-samples/ai.gemini-on-device/sidepanel/index.js:4 — the two spans are one implementation copied and then locally edited — 387 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. — functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:18
  • functional-samples/tutorial.open-api-reference/sw-omnibox.js:3 · functional-samples/tutorial.quick-api-reference/sw-omnibox.js:1 — the two spans are one implementation copied and then locally edited — 174 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. — functional-samples/tutorial.open-api-reference/sw-omnibox.js:3
  • functional-samples/tutorial.focus-mode-debugging/background.js:25 · functional-samples/tutorial.focus-mode-debugging/fixed/background.js:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — functional-samples/tutorial.focus-mode-debugging/background.js:25
  • functional-samples/tutorial.open-api-reference/sw-tips.js:1 · functional-samples/tutorial.quick-api-reference/sw-tips.js:1 — the two spans are one implementation copied and then locally edited — 162 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. — functional-samples/tutorial.open-api-reference/sw-tips.js:1
  • api-samples/tabs/inspector/window_and_tabs_manager.js:70 · api-samples/tabs/inspector/window_and_tabs_manager.js:112 — 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. — api-samples/tabs/inspector/window_and_tabs_manager.js:70
  • functional-samples/cookbook.geolocation-contentscript/content-script.js:19 · functional-samples/cookbook.geolocation-popup/popup.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — functional-samples/cookbook.geolocation-contentscript/content-script.js:19
  • functional-samples/tutorial.focus-mode-debugging/background.js:15 · functional-samples/tutorial.focus-mode-debugging/fixed/background.js:15 · functional-samples/tutorial.focus-mode/background.js:15 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — functional-samples/tutorial.focus-mode-debugging/background.js:15
  • api-samples/tabs/inspector/window_and_tabs_manager.js:267 · api-samples/tabs/inspector/window_and_tabs_manager.js:313 — 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. — api-samples/tabs/inspector/window_and_tabs_manager.js:267
  • functional-samples/tutorial.open-api-reference/content.js:17 · functional-samples/tutorial.quick-api-reference/content.js:12 — 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. — functional-samples/tutorial.open-api-reference/content.js:17
  • api-samples/favicon/popup.js:1 · functional-samples/sample.favicon-cs/content.js:1 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — api-samples/favicon/popup.js:1
  • api-samples/tabs/inspector/window_and_tabs_manager.js:181 · api-samples/tabs/inspector/window_and_tabs_manager.js:351 — 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. — api-samples/tabs/inspector/window_and_tabs_manager.js:181
  • functional-samples/cookbook.geolocation-contentscript/content-script.js:21 · functional-samples/cookbook.geolocation-offscreen/service_worker.js:75 · functional-samples/cookbook.geolocation-popup/popup.js:21 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — functional-samples/cookbook.geolocation-contentscript/content-script.js:21
  • functional-samples/cookbook.offscreen-user-media/background.js:40 · functional-samples/cookbook.offscreen-user-media/offscreen/offscreen.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — functional-samples/cookbook.offscreen-user-media/background.js:40
  • api-samples/history/historyOverride/logic.js:5 · api-samples/topSites/magic8ball/newTab.js:15 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — api-samples/history/historyOverride/logic.js:5
  • api-samples/printing/printers.js:65 · api-samples/printing/printers.js:78 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — api-samples/printing/printers.js:65
  • api-samples/alarms/background.js:8 · api-samples/web-accessible-resources/service-worker.js:1 — the two spans are one implementation copied and then locally edited — 50 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. — api-samples/alarms/background.js:8

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.
R11 · Import Boundaries8.8 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:1 reaches into another package with a relative path (../node_modules/@google/genai/dist/index.mjs) — import the package by name instead. — functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:1
  • functional-samples/ai.gemini-on-device-calendar-mate/background.js:1 reaches into another package with a relative path (./node_modules/any-date-parser/dist/index.mjs) — import the package by name instead. — functional-samples/ai.gemini-on-device-calendar-mate/background.js:1

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity9.9 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

  • render has cyclomatic complexity 37 and cognitive complexity 43; 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. — api-samples/downloads/download_manager/popup.js:306
  • dumpNode has cyclomatic complexity 12 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — functional-samples/sample.bookmarks/popup.js:29
  • updateUI has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — api-samples/scripting/index.js:87
  • (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — functional-samples/ai.gemini-on-device-audio-scribe/sidepanel.js:15
R3 · Large Files9.6 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

  • api-samples/fontSettings/fontSettings Advanced/options.js has 932 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — api-samples/fontSettings/fontSettings Advanced/options.js:1
  • api-samples/downloads/download_manager/popup.js has 712 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — api-samples/downloads/download_manager/popup.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 Freshness10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

R6 · Tooling6.7 / 10Strong✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.

What to do

  • Add type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • 2 file(s) (~120 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js imports '../node_modules/@google/genai/dist/index.mjs', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — functional-samples/ai.gemini-in-the-cloud
  • 2 file(s) (~168 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: functional-samples/ai.gemini-on-device-calendar-mate/background.js imports './node_modules/any-date-parser/dist/index.mjs', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — functional-samples/ai.gemini-on-device-calendar-mate
  • Unreachable from the 181 application, 9 tooling and 6 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (181 application, 9 tooling, 6 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 (×4) — functional-samples/tutorial.reading-time/scripts/content.js, functional-samples/tutorial.focus-mode-debugging/fixed/background.js, functional-samples/tutorial.focus-mode-debugging/fixed/focus-mode.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 Hygiene7.5 / 10Exemplary✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
  • Only test files import it (first: functional-samples/tutorial.puppeteer/index.test.js:16) — move it to devDependencies. — functional-samples/tutorial.puppeteer/package.json:6
  • Only test files import it (first: functional-samples/tutorial.terminate-sw/puppeteer/index.test.js:17) — move it to devDependencies. — functional-samples/tutorial.terminate-sw/puppeteer/package.json:6

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports10.0 / 10Exemplary✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • `https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.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. 6 such include(s) across the repository's markup. — _archive/mv2/api/bookmarks/basic/popup.html:3

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.
X1 · Async correctness7.9 / 10Strong✓ Tool-verified

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

  • `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. — api-samples/downloads/download_manager/service-worker.js:219

What to do

  • `async` callback passed to `forEach`
X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation4.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).

Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.

  • Only 0/7 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `updateTip` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — functional-samples/tutorial.quick-api-reference/sw-tips.js:4, functional-samples/tutorial.open-api-reference/sw-tips.js:4
  • `fireEvent` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — functional-samples/tutorial.google-analytics/scripts/google-analytics.js:75
  • `getMilestoneForRevId` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:33
  • `__wbg_init` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:214, functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:207
  • `generateAltText` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — functional-samples/ai.gemini-on-device-alt-texter/background.js:8

What to do

  • Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling6.4 / 10Strong✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — REDACTED:13, REDACTED:42, REDACTED:48

What to do

  • Swallowed exception (empty catch)
X5 · Nullable reference types2.0 / 10Weak✓ Tool-verified

Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 0/1 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.

What to do

  • Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

DimensionWCAG 2.2 A/AA criteriaCoverage
AC1 · Text alternatives1.1.1, 1.2.2, 1.2.5Partial signal
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC3 · Page structure1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2Partial signal
AC4 · Keyboard semantics2.1.1, 2.4.3Partial signal
AC5 · ARIA correctness4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health39%Weak — gated by R1, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture93%ExemplarySolid.
Maturity65%Adequate — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness54%Adequate — gated by P3, P6Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security79%Checked 3 of 9Solid.
Accessibility30%Weak — gated by AC1, AC3, AC4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 26 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • 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 — 62 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AX1 Captive dependencies — Not applicable: this repository's Dart imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Python 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; Rust with no dependency-injection crate has no container to hand one lifetime's instance to another — every value is owned by the code that builds it, and the borrow checker rejects a longer-lived value keeping a borrow of a shorter-lived one.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant. Rust's compiler refuses unsynchronised shared mutation — a value shared across threads must be Sync — so the race this check looks for cannot be written. 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 — no public interfaces
  • 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 start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" 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 — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • 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 — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
  • D21 Naming Consistency — Naming consistency does not read html yet; 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
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
  • 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).
  • 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 — .cpp, .ino, .pl 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
  • 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 JavaScript/TypeScript half could not be measured — the jest suite in functional-samples/tutorial.puppeteer/ ran and not one test passed (FAIL ./index.test.js), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); its 1 aggregate(s) are ORM models only — persistence, not behaviour: a CRUD model, measured, not claimed as DDD)
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
  • ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and a call made through an inferred or generic receiver has no resolvable owner in the source. Reported as guidance rather than measured
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript, Rust 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.
  • R4 Test Coverage — 6 test file(s) reach none of 181 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.
  • 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
  • X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Rust was read, and it logs through none: the `log` crate's macros take one finished message (as log4net does in C#; its `kv` values are an opt-in its backends mostly drop), `println!`/`eprintln!` are not loggers, or it makes no log call outside its tests and examples at all. Calls through `tracing` (`tracing::info!`, or `info!` imported from it) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 99 finding(s)
AC2 · Forms & labels · <input> without a programmatic label · ×27
  • <input> without a programmatic label _archive/mv2/api/bookmarks/basic/popup.html:8 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/cookies/manager.html:28 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/downloads/download_links/popup.html:6 — 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.
  • <input> without a programmatic label _archive/mv2/api/downloads/download_links/popup.html:12 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/downloads/download_manager/popup.html:16 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/history/historyOverride/history.html:9 — 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.
  • <input> without a programmatic label _archive/mv2/api/nativeMessaging/app/main.html:14 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/notifications/options.html:24 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/preferences/allowThirdPartyCookies/popup.html:10 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/preferences/allowThirdPartyCookies/popup.html:13 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/preferences/allowThirdPartyCookies/popup.html:16 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/preferences/enableReferrer/popup.html:10 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/preferences/enableReferrer/popup.html:13 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/preferences/enableReferrer/popup.html:16 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabCapture/options.html:8 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabCapture/options.html:10 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html:14 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html:15 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html:16 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html:17 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html:18 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html:19 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html:28 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html:29 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <input> without a programmatic label _archive/mv2/api/tabs/inspector/tabs_api.html:37 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • + 2 more in this group — see findings.md.
AC1 · Text alternatives · <img> without a text alternative · ×20
  • <img> without a text alternative _archive/mv2/api/processes/show_tabs/popup.js:55 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/api/storage/stylizr/options.html:29 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/api/tabs/screenshot/screenshot.html:6 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/api/water_alarm_notification/popup.html:34 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/email_this_page/options.html:22 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/gmail/background.html:1 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/imageinfo/info.html:17 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/mappy/popup.html:8 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/news/javascript/feed.js:200 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/news/javascript/feed.js:203 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/news/javascript/feed.js:206 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/news/views/feed.html:136 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/news/views/options.html:25 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/news_i18n/feed.html:8 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/talking_alarm_clock/credits.html:13 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/talking_alarm_clock/popup.html:155 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative _archive/mv2/extensions/talking_alarm_clock/popup.html:166 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative api-samples/storage/stylizr/options.html:33 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative api-samples/tabs/screenshot/screenshot.html:10 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
  • <img> without a text alternative functional-samples/sample.water_alarm_notification/popup.html:32 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
AC3 · Page structure · <html> without a lang · ×17
  • <html> without a lang _archive/mv2/api/bookmarks/basic/popup.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/browserAction/set_page_color/popup.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/browsingData/basic/popup.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/contentSettings/popup.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/contextMenus/global_context_search/options.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/cookies/manager.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/debugger/live-headers/headers.html:7 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/desktopCapture/index.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/deviceInfo/basic/popup.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/displaySource/tabCast/main.html:7 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/document_scan/scan.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/downloads/download_filename_controller/options.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/downloads/download_links/popup.html:1 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/downloads/download_manager/icons.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/downloads/download_manager/popup.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/extension/isAllowedAccess/popup.html:7 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
  • <html> without a lang _archive/mv2/api/fontSettings/options.html:2 — The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC2 · Forms & labels · <select> without a programmatic label · ×7
  • <select> without a programmatic label _archive/mv2/api/fontSettings/options.html:200 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label _archive/mv2/api/fontSettings/options.html:216 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label _archive/mv2/api/fontSettings/options.html:220 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label _archive/mv2/api/fontSettings/options.html:224 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label _archive/mv2/api/fontSettings/options.html:258 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label _archive/mv2/api/idle/idle_simple/history.html:22 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
  • <select> without a programmatic label _archive/mv2/api/notifications/options.html:26 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC3 · Page structure · Document without a <title> · ×6
  • Document without a <title> _archive/mv2/api/bookmarks/basic/popup.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> _archive/mv2/api/cookies/manager.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> _archive/mv2/api/debugger/live-headers/headers.html:7 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> _archive/mv2/api/desktopCapture/index.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> _archive/mv2/api/deviceInfo/basic/popup.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
  • Document without a <title> _archive/mv2/api/downloads/download_links/popup.html:1 — A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC4 · Keyboard semantics · Clickable element isn't keyboard-operable · ×6
  • Clickable element isn't keyboard-operable api-samples/tabs/inspector/window_and_tabs_manager.html:76 — The repo's own CSS styles .label with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable api-samples/tabs/inspector/window_and_tabs_manager.html:86 — The repo's own CSS styles .label with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable api-samples/tabs/inspector/window_and_tabs_manager.html:90 — The repo's own CSS styles .label with `cursor: pointer`, so this <div> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/index.html:16 — The repo's own CSS styles .chat-item with `cursor: pointer`, so this <li> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/index.html:20 — The repo's own CSS styles .chat-item with `cursor: pointer`, so this <li> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Clickable element isn't keyboard-operable functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/index.html:24 — The repo's own CSS styles .chat-item with `cursor: pointer`, so this <li> is a control — but it has no role, no tabindex="0" and no key handler, so it can only be reached with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
AC2 · Forms & labels · Link with no accessible name · ×3
  • Link with no accessible name _archive/mv2/api/downloads/download_manager/popup.html:18 — 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.
  • Link with no accessible name _archive/mv2/api/downloads/download_manager/popup.html:30 — 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.
  • Link with no accessible name _archive/mv2/api/downloads/download_manager/popup.html:43 — 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.
AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×3
  • Click handler on a non-interactive <div> _archive/mv2/api/i18n/getMessage/popup.html:18 — A script attaches a click listener to this <div>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> _archive/mv2/extensions/irc/servlet/index.html:381 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
  • Click handler on a non-interactive <div> _archive/mv2/extensions/irc/servlet/index.html:389 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
D28 · Secrets (history) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
AC2 · Forms & labels · <textarea> without a programmatic label · ×2
  • <textarea> without a programmatic label _archive/mv2/api/i18n/detectLanguage/popup.html:13 — 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.
  • <textarea> without a programmatic label _archive/mv2/api/storage/stylizr/options.html:33 — 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.
D30 · Dependency Vulnerabilities · High CVE · ×2
  • REDACTED
  • REDACTED
AC3 · Page structure · Document <title> is empty · ×1
  • Document <title> is empty _archive/mv2/api/downloads/download_manager/popup.html:2 — An empty <title> gives no page name in the tab, history or screen-reader page list. Put descriptive text in the <title>.
AC4 · Keyboard semantics · Click handler on a non-interactive <body> · ×1
  • Click handler on a non-interactive <body> _archive/mv2/extensions/irc/servlet/notification.html:56 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.
AC4 · Keyboard semantics · Click handler on a non-interactive <img> · ×1
  • Click handler on a non-interactive <img> _archive/mv2/extensions/mappy/popup.html:8 — A script attaches a click listener to this <img>, but it has no role, no tabindex and no key handler, so it can only be operated with a mouse. Use a <button>, or add role + tabindex="0" + a key handler.
Serious — 172 finding(s)
D30 · Dependency Vulnerabilities · Medium CVE · ×17
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Fake-async · ×16
  • Fake-async — async method never awaits api-samples/alarms/index.js:164 — `clearDisplay` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits api-samples/idle/history.js:42 — `checkState` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/ai.gemini-on-device-alt-texter/popup.js:26 — `showAltText` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/ai.gemini-on-device-summarization/sidepanel/index.js:94 — `showSummary` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/ai.gemini-on-device-summarization/sidepanel/index.js:98 — `updateWarning` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/ai.gemini-on-device/sidepanel/index.js:33 — `reset` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/cookbook.offscreen-clipboard-write/background.js:47 — `addToClipboardV2` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/cookbook.offscreen-clipboard-write/offscreen.js:28 — `handleMessages` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/cookbook.offscreen-clipboard-write/offscreen.js:55 — `handleClipboardWrite` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/cookbook.offscreen-dom/background.js:46 — `handleMessages` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/cookbook.offscreen-dom/background.js:63 — `handleAddExclamationMarkResult` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/cookbook.offscreen-dom/offscreen.js:22 — `handleMessages` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/sample.co2meter/background.js:34 — `co2MeterConnected` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/sample.co2meter/background.js:50 — `broadcastMessage` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/sample.co2meter/modules/co2_meter.js:46 — `init` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
  • Fake-async — async method never awaits functional-samples/sample.tabcapture-recorder/offscreen.js:80 — `stopRecording` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
AC3 · Page structure · Page without a main landmark · ×15
  • Page without a main landmark _archive/mv2/api/bookmarks/basic/popup.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/browserAction/set_page_color/popup.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/contentSettings/popup.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/contextMenus/global_context_search/options.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/cookies/manager.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/debugger/live-headers/headers.html:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="container">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark _archive/mv2/api/desktopCapture/index.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/deviceInfo/basic/popup.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="deviceinfos">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark _archive/mv2/api/displaySource/tabCast/main.html:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <div id="deviceList">, so there is no content here to wrap — render the <main> from the component mounted into it.
  • Page without a main landmark _archive/mv2/api/document_scan/scan.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/downloads/download_filename_controller/options.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/downloads/download_links/popup.html:1 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/downloads/download_manager/icons.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/downloads/download_manager/popup.html:2 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
  • Page without a main landmark _archive/mv2/api/extension/isAllowedAccess/popup.html:7 — No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×15
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/api/contextMenus/global_context_search/options.html:12 — `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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/api/water_alarm_notification/popup.html:19 — `button` 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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/extensions/constant_context/popup.html:12 — `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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/extensions/download_images/popup.html:12 — `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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/extensions/talking_alarm_clock/popup.html:99 — `body.nooutline *` 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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/tutorials/broken_background_color/options.html:8 — `button` 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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/tutorials/broken_background_color/popup.html:8 — `button` 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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/tutorials/get_started/options.html:8 — `button` 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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/tutorials/get_started/popup.html:8 — `button` 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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/tutorials/get_started_complete/options.html:8 — `button` 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.
  • Focus outline removed in CSS without a :focus replacement _archive/mv2/tutorials/get_started_complete/popup.html:8 — `button` 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.
  • Focus outline removed in CSS without a :focus replacement api-samples/contextMenus/global_context_search/popup.html:13 — `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.
  • Focus outline removed in CSS without a :focus replacement functional-samples/sample.water_alarm_notification/popup.html:20 — `button` 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.
  • Focus outline removed in CSS without a :focus replacement functional-samples/tutorial.broken-color/options.html:8 — `button` 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.
  • Focus outline removed in CSS without a :focus replacement functional-samples/tutorial.broken-color/popup.html:8 — `button` 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.
AC4 · Keyboard semantics · Anchor without href · ×9
  • Anchor without href _archive/mv2/api/topsites/magic8ball/newTab.html:19 — 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.
  • Anchor without href _archive/mv2/extensions/calendar/views/options.html:17 — 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.
  • Anchor without href _archive/mv2/extensions/news/javascript/feed.js:198 — 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.
  • Anchor without href _archive/mv2/extensions/news/javascript/feed.js:201 — 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.
  • Anchor without href _archive/mv2/extensions/news/javascript/feed.js:204 — 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.
  • Anchor without href _archive/mv2/extensions/news/views/feed.html:135 — 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.
  • Anchor without href _archive/mv2/extensions/news_i18n/feed.html:8 — 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.
  • Anchor without href api-samples/topSites/magic8ball/newTab.html:29 — 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.
  • Anchor without href functional-samples/cookbook.offscreen-user-media/popup.html:21 — 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.
X2 · Cancellation propagation · Async function without AbortSignal · ×7
  • Async function without AbortSignal: updateTip functional-samples/tutorial.quick-api-reference/sw-tips.js:4 — `updateTip` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: updateTip functional-samples/tutorial.open-api-reference/sw-tips.js:4 — `updateTip` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: fireEvent functional-samples/tutorial.google-analytics/scripts/google-analytics.js:75 — `fireEvent` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: getMilestoneForRevId REDACTED:33 — `getMilestoneForRevId` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: __wbg_init functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:214 — `__wbg_init` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: __wbg_init functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:207 — `__wbg_init` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
  • Async function without AbortSignal: generateAltText functional-samples/ai.gemini-on-device-alt-texter/background.js:8 — `generateAltText` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.9 · ×5
  • Low contrast colour pair in CSS (3.9:1) _archive/mv2/api/fontSettings/options.html:140 — `#apply-settings:enabled` sets color: #fbfafb on background-color: #4f7dd6 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.9:1) api-samples/fontSettings/fontSettings Advanced/options.html:155 — `#apply-settings:enabled` sets color: #fbfafb on background-color: #4f7dd6 — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.9:1) _archive/apps/samples/webserver/styles/bootstrap.css:1500 — `.control-group.error .input-prepend .add-on, .control-group.error .input-append .add-on` sets color: #b94a48 on background-color: #f2dede — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.9:1) _archive/apps/samples/webserver/styles/bootstrap.css:2970 — `.nav-list > .active > a, .nav-list > .active > a:hover` sets color: #ffffff on background-color: #0088cc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.9:1) _archive/apps/samples/webserver/styles/bootstrap.css:3050 — `.nav-pills > .active > a, .nav-pills > .active > a:hover` sets color: #ffffff on background-color: #0088cc — 3.9:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.8 · ×5
  • Low contrast colour pair in CSS (2.8:1) functional-samples/ai.gemini-on-device-summarization/sidepanel/index.css:52 — `.result` sets color: white on background-color: #00aabb — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.8:1) _archive/mv2/extensions/irc/servlet/styles.css:96 — `.channelControls .removeButton` sets color: #999999 on background-color: white — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.8:1) _archive/apps/samples/webserver/styles/bootstrap.css:747 — `.label, .badge` sets color: #ffffff on background-color: #999999 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.8:1) _archive/apps/samples/webserver/styles/bootstrap.css:3131 — `.nav-tabs .open .dropdown-toggle, .nav-pills .open .dropdown-toggle, .nav > li.dropdown.open.active > a:hover` sets color: #ffffff on background-color: #999999 — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.8:1) _archive/apps/samples/webserver/styles/bootstrap.css:3869 — `.pager .disabled a, .pager .disabled a:hover, .pager .disabled span` sets color: #999999 on background-color: #fff — 2.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D17 · Explicit Debt · TodoComment · ×5
  • TodoComment _archive/mv2/extensions/irc/servlet/src/org/chromium/IRCProxyWebSocket.java:70 — // TODO Auto-generated catch block — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment _archive/mv2/extensions/irc/servlet/src/org/chromium/IRCProxyWebSocket.java:73 — // TODO Auto-generated catch block — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment _archive/mv2/extensions/irc/servlet/src/org/chromium/IRCProxyWebSocket.java:82 — // TODO Auto-generated catch block — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment _archive/mv2/extensions/irc/servlet/src/org/chromium/IRCProxyWebSocket.java:92 — // TODO Auto-generated catch block — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment _archive/apps/samples/dart/dart/balls.dart:74 — // TODO: move balls apart. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
AC1 · Text alternatives · <canvas> without a text alternative · ×3
  • <canvas> without a text alternative _archive/mv2/api/pageAction/set_icon/background.html:6 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative _archive/mv2/extensions/imageinfo/info.html:23 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
  • <canvas> without a text alternative _archive/mv2/extensions/talking_alarm_clock/popup.html:113 — A <canvas> with no aria-label/title and no inner fallback content can't be described by assistive tech. Add a name or fallback content.
AC4 · Keyboard semantics · Link used as a button (placeholder href) · ×3
  • Link used as a button (placeholder href) _archive/mv2/api/processes/show_tabs/popup.js:58 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) _archive/mv2/extensions/gdocs/popup.html:95 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
  • Link used as a button (placeholder href) _archive/mv2/extensions/gdocs/popup.html:96 — An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.3 · ×3
  • Low contrast colour pair in CSS (2.3:1) _archive/mv2/extensions/irc/servlet/notification.html:21 — `#title` sets color: white on background-color: #AAAAAA — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.3:1) _archive/mv2/extensions/irc/servlet/styles.css:39 — `.addButton` sets color: white on background-color: #aaaaaa — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (2.3:1) _archive/apps/samples/webserver/styles/bootstrap.css:2076 — `.btn-warning:hover, .btn-warning:active, .btn-warning.active, .btn-warning.disabled, .btn-warning[disabled]` sets color: #ffffff on background-color: #f89406 — 2.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
R10 · Code Duplication · Duplicated block (9 lines × 2 locations) · ×3
  • Duplicated block (9 lines × 2 locations) api-samples/favicon/popup.js:1 — api-samples/favicon/popup.js:1 · functional-samples/sample.favicon-cs/content.js:1 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (9 lines × 2 locations) api-samples/tabs/inspector/window_and_tabs_manager.js:181 — api-samples/tabs/inspector/window_and_tabs_manager.js:181 · api-samples/tabs/inspector/window_and_tabs_manager.js:351 — 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.
  • Duplicated block (9 lines × 2 locations) functional-samples/cookbook.offscreen-user-media/background.js:40 — functional-samples/cookbook.offscreen-user-media/background.js:40 · functional-samples/cookbook.offscreen-user-media/offscreen/offscreen.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
X3 · Exception handling · Swallowed exception (empty catch) · ×3
  • Swallowed exception (empty catch) REDACTED:13 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:42 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
  • Swallowed exception (empty catch) REDACTED:48 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.6 · ×2
  • Low contrast colour pair in CSS (3.6:1) functional-samples/sample.optional_permissions/style.css:119 — `input#todo_value ~ input[type="submit"]` sets color: white on background-color: #4285F4 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.6:1) _archive/mv2/extensions/optional_permissions/style.css:99 — `input#todo_value ~ input[type="submit"]` sets color: white on background-color: #4285F4 — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.8 · ×2
  • Low contrast colour pair in CSS (3.8:1) functional-samples/sample.bookmarks/third-party/jquery-ui.css:982 — `.ui-state-active, .ui-widget-content .ui-state-active, .ui-widget-header .ui-state-active, a.ui-button:active, .ui-button:active, .ui-button.ui-state-active:hover` sets color: #ffffff on background-color: #007fff — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
  • Low contrast colour pair in CSS (3.8:1) functional-samples/sample.bookmarks/third-party/jquery-ui.theme.css:113 — `.ui-state-active, .ui-widget-content .ui-state-active, .ui-widget-header .ui-state-active, a.ui-button:active, .ui-button:active, .ui-button.ui-state-active:hover` sets color: #ffffff on background-color: #007fff — 3.8:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D10 · Test Quality · No assertions · ×2
  • No assertions: can message service worker when terminated functional-samples/tutorial.terminate-sw/selenium/index.test.js:75 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: can message service worker when terminated functional-samples/tutorial.terminate-sw/puppeteer/index.test.js:57 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D10 · Test Quality · Test project verifies nothing · ×2
  • Test project verifies nothing: functional-samples/tutorial.terminate-sw/puppeteer functional-samples/tutorial.terminate-sw/puppeteer/index.test.js:57 — No conventional assertion call was detected in 1 of 1 tests in `functional-samples/tutorial.terminate-sw/puppeteer` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: functional-samples/tutorial.terminate-sw/selenium functional-samples/tutorial.terminate-sw/selenium/index.test.js:75 — No conventional assertion call was detected in 1 of 1 tests in `functional-samples/tutorial.terminate-sw/selenium` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
D2 · Cognitive Complexity · helloworld_demo.__wbg_load (cognitive 16) · ×2
  • helloworld_demo.__wbg_load (cognitive 16) functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:131 — helloworld_demo.__wbg_load has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • helloworld_demo.__wbg_load (cognitive 16) functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:124 — helloworld_demo.__wbg_load has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
R10 · Code Duplication · Duplicated block (7 lines × 2 locations) · ×2
  • Duplicated block (7 lines × 2 locations) api-samples/history/historyOverride/logic.js:5 — api-samples/history/historyOverride/logic.js:5 · api-samples/topSites/magic8ball/newTab.js:15 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
  • Duplicated block (7 lines × 2 locations) api-samples/printing/printers.js:65 — api-samples/printing/printers.js:65 · api-samples/printing/printers.js:78 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R11 · Import Boundaries · Boundary violation [package · ×2
  • Boundary violation [package:relative-cross-package] functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:1 — functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:1 reaches into another package with a relative path (../node_modules/@google/genai/dist/index.mjs) — import the package by name instead.
  • Boundary violation [package:relative-cross-package] functional-samples/ai.gemini-on-device-calendar-mate/background.js:1 — functional-samples/ai.gemini-on-device-calendar-mate/background.js:1 reaches into another package with a relative path (./node_modules/any-date-parser/dist/index.mjs) — import the package by name instead.
AC2 · Forms & labels · <fieldset> without a <legend> · ×1
  • <fieldset> without a <legend> _archive/mv2/api/contentSettings/popup.html:11 — A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
AC3 · Page structure · Data table has no header cells · ×1
  • Data table has no header cells _archive/mv2/api/downloads/download_filename_controller/options.html:10 — A <table> with data cells but no <th> gives assistive technology no way to associate cells with their headers. Mark the header row/column cells as <th> (with a scope).
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.0 · ×1
  • Low contrast colour pair in CSS (4.0:1) functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/style.css:173 — `#send-button` sets color: white on background-color: #007bff — 4.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (4.4 · ×1
  • Low contrast colour pair in CSS (4.4:1) _archive/mv2/extensions/irc/servlet/styles.css:149 — `#entryText` sets color: white on background-color: #777777 — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.0 · ×1
  • Low contrast colour pair in CSS (1.0:1) _archive/apps/samples/webview-samples/insert-css/inject.css:38 — `b, em, h3 a:link, h3 a:visited, h3 a:hover, li cite, div.crl` sets color: #000 on background-color: #000 — 1.0:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (2.5 · ×1
  • Low contrast colour pair in CSS (2.5:1) _archive/apps/samples/webserver/styles/bootstrap.css:1466 — `.control-group.warning .input-prepend .add-on, .control-group.warning .input-append .add-on` sets color: #c09853 on background-color: #fcf8e3 — 2.5:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.3 · ×1
  • Low contrast colour pair in CSS (3.3:1) _archive/apps/samples/webserver/styles/bootstrap.css:1568 — `.control-group.info .input-prepend .add-on, .control-group.info .input-append .add-on` sets color: #3a87ad on background-color: #d9edf7 — 3.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.1 · ×1
  • Low contrast colour pair in CSS (3.1:1) _archive/apps/samples/webserver/styles/bootstrap.css:2138 — `.btn-success:hover, .btn-success:active, .btn-success.active, .btn-success.disabled, .btn-success[disabled]` sets color: #ffffff on background-color: #51a351 — 3.1:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (3.4 · ×1
  • Low contrast colour pair in CSS (3.4:1) _archive/apps/samples/webserver/styles/bootstrap.css:2169 — `.btn-info:hover, .btn-info:active, .btn-info.active, .btn-info.disabled, .btn-info[disabled]` sets color: #ffffff on background-color: #2f96b4 — 3.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety · Low contrast colour pair in CSS (1.3 · ×1
  • Low contrast colour pair in CSS (1.3:1) _archive/apps/samples/webserver/styles/bootstrap.css:3513 — `.navbar .btn-navbar:hover, .navbar .btn-navbar:active, .navbar .btn-navbar.active, .navbar .btn-navbar.disabled, .navbar .btn-navbar[disabled]` sets color: #ffffff on background-color: #e5e5e5 — 1.3:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
D1 · Cyclomatic Complexity · DownloadItem.render (cyclomatic 39) · ×1
  • DownloadItem.render (cyclomatic 39) api-samples/downloads/download_manager/popup.js:306 — DownloadItem.render has cyclomatic complexity 39 (threshold 15). Of this number, 37 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · render (cognitive 49) · ×1
  • render (cognitive 49) api-samples/downloads/download_manager/popup.js:306 — render has cognitive complexity 49 (threshold 15). Drivers by points: if/else 23 (32 pts), boolean chains 11, ternaries 6 (nesting depth added 9). Of this number, 43 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level. This file is where this pass's cognitive complexity CONCENTRATES: api-samples/downloads/download_manager/popup.js holds 2 of the 7 methods over the threshold — including the worst — and 35 of the 55 points over it (64%), 3.9× the next-largest file (api-samples/fontSettings/fontSettings Advanced/js/cr.js at 9). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D2 · Cognitive Complexity · (anonymous).getSetter (cognitive 24) · ×1
  • (anonymous).getSetter (cognitive 24) api-samples/fontSettings/fontSettings Advanced/js/cr.js:146 — (anonymous).getSetter has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (23 pts), match/switch 1 (nesting depth added 13). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 161, 173, 150). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · filterLinks (cognitive 20) · ×1
  • filterLinks (cognitive 20) api-samples/downloads/download_links/popup.js:52 — filterLinks has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (18 pts), loops 1 (2 pts) (nesting depth added 13). Most of this is not in the body itself: 2 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 60, 55). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
D2 · Cognitive Complexity · dumpNode (cognitive 19) · ×1
  • dumpNode (cognitive 19) functional-samples/sample.bookmarks/popup.js:29 — dumpNode has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 4 (8 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · constructor (cognitive 16) · ×1
  • constructor (cognitive 16) api-samples/downloads/download_manager/popup.js:175 — constructor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 3, loops 1 (nesting depth added 1). Of this number, 10 points are the body's own statements and 6 belong to 14 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This file is where this pass's cognitive complexity CONCENTRATES: api-samples/downloads/download_manager/popup.js holds 2 of the 7 methods over the threshold — including the worst — and 35 of the 55 points over it (64%), 3.9× the next-largest file (api-samples/fontSettings/fontSettings Advanced/js/cr.js at 9). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: DownloadItem (LCOM4 5) api-samples/downloads/download_manager/popup.js:174 — DownloadItem's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in functional-samples/tutorial.puppeteer/ ran and not one test passed (FAIL ./index.test.js), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
IC1 · Incompleteness & stubs · Empty method body · ×1
  • Empty method body — does nothing with its inputs functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:178 — `__wbg_init_memory` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 190 plain JS — the untyped files are api-samples/action/background.js, api-samples/alarms/background.js, api-samples/alarms/bg-wrapper.js, api-samples/alarms/index.js, api-samples/bookmarks/popup.js, api-samples/browsingData/popup.js (+184 more).
R10 · Code Duplication · Duplication concentrated across 11 sibling directories (8 clone groups) · ×1
  • Duplication concentrated across 11 sibling directories (8 clone groups) functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:18 — 8 duplicated blocks under functional-samples/ have copies in at least two of the sibling directories ai.gemini-in-the-cloud, ai.gemini-on-device, cookbook.geolocation-contentscript, cookbook.geolocation-offscreen, cookbook.geolocation-popup, cookbook.sidepanel-open (+5 more sibling(s) not listed) — 7 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplicated block with local edits (66 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (66 matched lines × 2 locations) functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:18 — functional-samples/ai.gemini-in-the-cloud/sidepanel/index.js:18 · functional-samples/ai.gemini-on-device/sidepanel/index.js:4 — the two spans are one implementation copied and then locally edited — 387 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.
R10 · Code Duplication · Duplicated block with local edits (23 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (23 matched lines × 2 locations) functional-samples/tutorial.open-api-reference/sw-omnibox.js:3 — functional-samples/tutorial.open-api-reference/sw-omnibox.js:3 · functional-samples/tutorial.quick-api-reference/sw-omnibox.js:1 — the two spans are one implementation copied and then locally edited — 174 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.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×1
  • Duplicated block (20 lines × 2 locations) functional-samples/tutorial.focus-mode-debugging/background.js:25 — functional-samples/tutorial.focus-mode-debugging/background.js:25 · functional-samples/tutorial.focus-mode-debugging/fixed/background.js:25 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (19 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (19 matched lines × 2 locations) functional-samples/tutorial.open-api-reference/sw-tips.js:1 — functional-samples/tutorial.open-api-reference/sw-tips.js:1 · functional-samples/tutorial.quick-api-reference/sw-tips.js:1 — the two spans are one implementation copied and then locally edited — 162 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.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×1
  • Duplicated block (17 lines × 2 locations) api-samples/tabs/inspector/window_and_tabs_manager.js:70 — api-samples/tabs/inspector/window_and_tabs_manager.js:70 · api-samples/tabs/inspector/window_and_tabs_manager.js:112 — 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.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×1
  • Duplicated block (16 lines × 2 locations) functional-samples/cookbook.geolocation-contentscript/content-script.js:19 — functional-samples/cookbook.geolocation-contentscript/content-script.js:19 · functional-samples/cookbook.geolocation-popup/popup.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (16 lines × 3 locations) · ×1
  • Duplicated block (16 lines × 3 locations) functional-samples/tutorial.focus-mode-debugging/background.js:15 — functional-samples/tutorial.focus-mode-debugging/background.js:15 · functional-samples/tutorial.focus-mode-debugging/fixed/background.js:15 · functional-samples/tutorial.focus-mode/background.js:15 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) api-samples/tabs/inspector/window_and_tabs_manager.js:267 — api-samples/tabs/inspector/window_and_tabs_manager.js:267 · api-samples/tabs/inspector/window_and_tabs_manager.js:313 — 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.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×1
  • Duplicated block (11 lines × 2 locations) functional-samples/tutorial.open-api-reference/content.js:17 — functional-samples/tutorial.open-api-reference/content.js:17 · functional-samples/tutorial.quick-api-reference/content.js:12 — 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.
R10 · Code Duplication · Duplicated block (9 lines × 3 locations) · ×1
  • Duplicated block (9 lines × 3 locations) functional-samples/cookbook.geolocation-contentscript/content-script.js:21 — functional-samples/cookbook.geolocation-contentscript/content-script.js:21 · functional-samples/cookbook.geolocation-offscreen/service_worker.js:75 · functional-samples/cookbook.geolocation-popup/popup.js:21 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (6 matched lines × 2 locations) api-samples/alarms/background.js:8 — api-samples/alarms/background.js:8 · api-samples/web-accessible-resources/service-worker.js:1 — the two spans are one implementation copied and then locally edited — 50 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.
R2 · Cyclomatic Complexity · Complex function render (cyclomatic 37, cognitive 43) · ×1
  • Complex function render (cyclomatic 37, cognitive 43) api-samples/downloads/download_manager/popup.js:306 — render has cyclomatic complexity 37 and cognitive complexity 43; 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.
R2 · Cyclomatic Complexity · Complex function dumpNode (cyclomatic 12, cognitive 19) · ×1
  • Complex function dumpNode (cyclomatic 12, cognitive 19) functional-samples/sample.bookmarks/popup.js:29 — dumpNode has cyclomatic complexity 12 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function updateUI (cyclomatic 11, cognitive 10) · ×1
  • Complex function updateUI (cyclomatic 11, cognitive 10) api-samples/scripting/index.js:87 — updateUI has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 11, cognitive 10) · ×1
  • Complex function (anonymous) (cyclomatic 11, cognitive 10) functional-samples/ai.gemini-on-device-audio-scribe/sidepanel.js:15 — (anonymous) has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files · api-samples/fontSettings/fontSettings Advanced/options.js · ×1
  • api-samples/fontSettings/fontSettings Advanced/options.js: 932 lines of code api-samples/fontSettings/fontSettings Advanced/options.js:1 — api-samples/fontSettings/fontSettings Advanced/options.js has 932 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · api-samples/downloads/download_manager/popup.js · ×1
  • api-samples/downloads/download_manager/popup.js: 712 lines of code api-samples/downloads/download_manager/popup.js:1 — api-samples/downloads/download_manager/popup.js has 712 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — 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.
R7 · Dead Code · Dead file (~71 LoC) · ×1
  • Dead file (~71 LoC) functional-samples/tutorial.reading-time/scripts/content.js — no import path from any entry point (181 application, 9 tooling, 6 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
R7 · Dead Code · Dead file (~44 LoC) · ×1
  • Dead file (~44 LoC) functional-samples/tutorial.focus-mode-debugging/fixed/background.js — no import path from any entry point (181 application, 9 tooling, 6 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
R7 · Dead Code · Dead file (~24 LoC) · ×1
  • Dead file (~24 LoC) functional-samples/tutorial.focus-mode-debugging/fixed/focus-mode.js — no import path from any entry point (181 application, 9 tooling, 6 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
R7 · Dead Code · Dead file (~2 LoC) · ×1
  • Dead file (~2 LoC) functional-samples/libraries-xhr-in-sw/sidepanel/script.js — no import path from any entry point (181 application, 9 tooling, 6 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
R8 · Dependency Hygiene · Unused dependency 'chrome-types' · ×1
  • Unused dependency 'chrome-types' — Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
S1 · Web-Security Posture · Third-party script without Subresource Integrity · ×1
  • Third-party script without Subresource Integrity _archive/mv2/api/bookmarks/basic/popup.html:3 — `https://ajax.googleapis.com/ajax/libs/jquery/1.10.2/jquery.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. 6 such include(s) across the repository's markup.
X1 · Async correctness · `async` callback passed to `forEach` · ×1
  • `async` callback passed to `forEach` api-samples/downloads/download_manager/service-worker.js:219 — `forEach` ignores what its callback returns, so the Promise each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early), and a rejection is never handled — in Node.js an unhandled rejection terminates the process by default, and in a browser it is lost. Iterate with `for (const item of items) { await … }` when the work must run in order, or `await Promise.all(items.map(async (item) => { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
Minor — 103 finding(s)
P2 · Observability · Console output used as the logging channel · ×39
  • Console output used as the logging channel functional-samples/tutorial.websockets/service-worker.js:27 — `functional-samples/tutorial.websockets/service-worker.js` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/tutorial.websockets/service-worker.js:32 — `functional-samples/tutorial.websockets/service-worker.js` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/tutorial.websockets/service-worker.js:47 — `functional-samples/tutorial.websockets/service-worker.js` reports through `console.*` at line 47 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/tutorial.quick-api-reference/sw-omnibox.js:1 — `functional-samples/tutorial.quick-api-reference/sw-omnibox.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/tutorial.quick-api-reference/sw-tips.js:1 — `functional-samples/tutorial.quick-api-reference/sw-tips.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/tutorial.open-api-reference/sw-omnibox.js:3 — `functional-samples/tutorial.open-api-reference/sw-omnibox.js` reports through `console.*` at line 3 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/tutorial.open-api-reference/sw-tips.js:1 — `functional-samples/tutorial.open-api-reference/sw-tips.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/tutorial.hello-world/popup.js:1 — `functional-samples/tutorial.hello-world/popup.js` reports through `console.*` at line 1 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/tutorial.getting-started/background.js:5 — `functional-samples/tutorial.getting-started/background.js` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/tutorial.broken-color/service-worker.js:19 — `functional-samples/tutorial.broken-color/service-worker.js` reports through `console.*` at line 19 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/sample.co2meter/background.js:67 — `functional-samples/sample.co2meter/background.js` reports through `console.*` at line 67 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/sample.co2meter/background.js:113 — `functional-samples/sample.co2meter/background.js` reports through `console.*` at line 113 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/sample.co2meter/modules/co2_meter.js:58 — `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 58 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/sample.co2meter/modules/co2_meter.js:63 — `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 63 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/sample.co2meter/modules/co2_meter.js:76 — `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 76 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/sample.co2meter/modules/co2_meter.js:104 — `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 104 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/sample.co2meter/modules/co2_meter.js:110 — `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 110 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/sample.co2meter/modules/co2_meter.js:126 — `functional-samples/sample.co2meter/modules/co2_meter.js` reports through `console.*` at line 126 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:139 — `functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 139 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:173 — `functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 173 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:176 — `functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 176 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:132 — `functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 132 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:166 — `functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 166 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js:169 — `functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js` reports through `console.*` at line 169 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • Console output used as the logging channel functional-samples/cookbook.sidepanel-site-specific/service-worker.js:20 — `functional-samples/cookbook.sidepanel-site-specific/service-worker.js` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
  • + 14 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×26
  • Duplicated predicate _archive/mv2/api/fontSettings/js/cr.js:32 — `!parts.length && opt_object !== undefined` appears character-identically in 3 files — _archive/mv2/api/fontSettings/js/cr.js, _archive/mv2/extensions/plugin_settings/domui/js/cr.js, api-samples/fontSettings/fontSettings Advanced/js/cr.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/bookmarks/basic/popup.js:120 — `bookmarkNode.children && bookmarkNode.children.length > 0` appears character-identically in 2 files — _archive/mv2/api/bookmarks/basic/popup.js, functional-samples/sample.bookmarks/popup.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js:17 — `cachedUint8Memory0 === null || cachedUint8Memory0.byteLength === 0` appears character-identically in 2 files — functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/pkg/helloworld_demo.js, functional-samples/cookbook.wasm-helloworld-print/wasm/pkg/helloworld_demo.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/gdocs/chrome_ex_oauth.js:74 — `changeInfo.url && changeInfo.url.substr(0, url_match.length) === url_match && changeInfo.url != tabs[tabId] && window.chromeExOAuthRequestin…` appears character-identically in 2 files — _archive/mv2/extensions/gdocs/chrome_ex_oauth.js, _archive/mv2/extensions/oauth_contacts/chrome_ex_oauth.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/tabCapture/eventPage.js:12 — `chrome.runtime.lastError.message || 'UNKNOWN'` appears character-identically in 2 files — _archive/mv2/api/tabCapture/eventPage.js, api-samples/tabCapture/receiver.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/fontSettings/js/cr.js:282 — `ctor.instance_ || (ctor.instance_ = new ctor())` appears character-identically in 3 files — _archive/mv2/api/fontSettings/js/cr.js, _archive/mv2/extensions/plugin_settings/domui/js/cr.js, api-samples/fontSettings/fontSettings Advanced/js/cr.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/downloads/download_manager/popup.js:346 — `item.byExtensionId && item.byExtensionName` appears character-identically in 2 files — _archive/mv2/api/downloads/download_manager/popup.js, api-samples/downloads/download_manager/popup.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/downloads/download_manager/popup.js:229 — `item.getElement('more') && (pointInElement(mouse, item.div) || pointInElement(mouse, item.getElement('more')))` appears character-identically in 2 files — _archive/mv2/api/downloads/download_manager/popup.js, api-samples/downloads/download_manager/popup.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/fontSettings/options.js:473 — `levelOfControl == 'controllable_by_this_extension' || levelOfControl == 'controlled_by_this_extension'` appears character-identically in 4 files — _archive/mv2/api/fontSettings/options.js, _archive/mv2/api/preferences/allowThirdPartyCookies/popup.js, _archive/mv2/api/preferences/enableReferrer/popup.js, api-samples/fontSettings/fontSettings Advanced/options.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/talking_alarm_clock/background.js:78 — `localStorage['a1_ampm'] || DEFAULT_A1_AMPM` appears character-identically in 2 files — _archive/mv2/extensions/talking_alarm_clock/background.js, _archive/mv2/extensions/talking_alarm_clock/popup.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/talking_alarm_clock/background.js:92 — `localStorage['a2_ampm'] || DEFAULT_A2_AMPM` appears character-identically in 2 files — _archive/mv2/extensions/talking_alarm_clock/background.js, _archive/mv2/extensions/talking_alarm_clock/popup.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/talking_alarm_clock/common.js:143 — `localStorage['phrase'] || DEFAULT_PHRASE` appears character-identically in 2 files — _archive/mv2/extensions/talking_alarm_clock/common.js, _archive/mv2/extensions/talking_alarm_clock/popup.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/gdocs/chrome_ex_oauth.js:27 — `opt_args && opt_args['app_name'] || "ChromeExOAuth Library"` appears character-identically in 2 files — _archive/mv2/extensions/gdocs/chrome_ex_oauth.js, _archive/mv2/extensions/oauth_contacts/chrome_ex_oauth.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/gdocs/chrome_ex_oauth.js:31 — `opt_args && opt_args['callback_page'] || "chrome_ex_oauth.html"` appears character-identically in 2 files — _archive/mv2/extensions/gdocs/chrome_ex_oauth.js, _archive/mv2/extensions/oauth_contacts/chrome_ex_oauth.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/gdocs/chrome_ex_oauth.js:474 — `opt_args && opt_args['url_callback'] || window && window.top && window.top.location && window.top.location.href` appears character-identically in 2 files — _archive/mv2/extensions/gdocs/chrome_ex_oauth.js, _archive/mv2/extensions/oauth_contacts/chrome_ex_oauth.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/gdocs/chrome_ex_oauth.js:478 — `opt_args && opt_args['url_callback_param'] || "chromeexoauthcallback"` appears character-identically in 2 files — _archive/mv2/extensions/gdocs/chrome_ex_oauth.js, _archive/mv2/extensions/oauth_contacts/chrome_ex_oauth.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/fontSettings/js/cr.js:236 — `opt_cancelable === undefined || opt_cancelable` appears character-identically in 3 files — _archive/mv2/api/fontSettings/js/cr.js, _archive/mv2/extensions/plugin_settings/domui/js/cr.js, api-samples/fontSettings/fontSettings Advanced/js/cr.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/gdocs/chrome_ex_oauth.js:146 — `opt_params && opt_params['body'] || null` appears character-identically in 2 files — _archive/mv2/extensions/gdocs/chrome_ex_oauth.js, _archive/mv2/extensions/oauth_contacts/chrome_ex_oauth.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/gdocs/chrome_ex_oauth.js:145 — `opt_params && opt_params['method'] || 'GET'` appears character-identically in 2 files — _archive/mv2/extensions/gdocs/chrome_ex_oauth.js, _archive/mv2/extensions/oauth_contacts/chrome_ex_oauth.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/fileSystemProvider/archive/background.js:101 — `options.mode != 'READ' || options.create` appears character-identically in 2 files — _archive/mv2/api/fileSystemProvider/archive/background.js, _archive/mv2/api/fileSystemProvider/basic/background.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/extensions/news/javascript/feed.js:86 — `parentTag != 'item' && parentTag != 'entry'` appears character-identically in 2 files — _archive/mv2/extensions/news/javascript/feed.js, _archive/mv2/extensions/news_a11y/feed.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/downloads/download_manager/popup.js:129 — `parseInt(document.body.style.minHeight) || 0` appears character-identically in 2 files — _archive/mv2/api/downloads/download_manager/popup.js, api-samples/downloads/download_manager/popup.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/downloads/download_manager/popup.js:124 — `parseInt(document.body.style.minWidth) || 0` appears character-identically in 2 files — _archive/mv2/api/downloads/download_manager/popup.js, api-samples/downloads/download_manager/popup.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate functional-samples/tutorial.focus-mode-debugging/background.js:26 — `tab.url?.startsWith(extensions) || tab.url?.startsWith(webstore)` appears character-identically in 2 files — functional-samples/tutorial.focus-mode-debugging/background.js, functional-samples/tutorial.focus-mode-debugging/fixed/background.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate _archive/mv2/api/downloads/download_manager/popup.js:625 — `term.match(/\s/) && term[0].match(/["']/) && term[term.length - 1] == term[0]` appears character-identically in 2 files — _archive/mv2/api/downloads/download_manager/popup.js, api-samples/downloads/download_manager/popup.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • + 1 more in this group — see findings.md.
D24 · Comment Value · redundant comment · ×16
  • redundant comment api-samples/bookmarks/popup.js:67 — "Add click event listeners to the buttons" repeats the code it sits on: 5 of its 5 words (add, click, event, listeners, buttons) are already in `document.getElementById('addButton').addEventListener('click', addBookmark);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment api-samples/fontSettings/fontSettings Advanced/js/cr/ui/overlay.js:66 — "Close the overlay on clicking any of the pages' close buttons." repeats the code it sits on: 4 of its 5 words (close, overlay, pages, buttons) are already in `let closeButtons = overlay.querySelectorAll('.page > .close-button');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment api-samples/fontSettings/fontSettings Advanced/options.js:610 — "Set the event listener for file selection" repeats the code it sits on: 4 of its 5 words (event, listener, file, selection) are already in `fileInput.addEventListener('change', handleFileSelection);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment api-samples/privacy/service-worker.js:16 — "Set default value for credit card autofill enabled" repeats the code it sits on: 6 of its 7 words (set, value, credit, card, autofill, enabled) are already in `chrome.privacy.services.autofillCreditCardEnabled.set({ value: true });`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment api-samples/readingList/index.js:122 — "Add item button click handler" repeats the code it sits on: 4 of its 5 words (add, item, button, click) are already in `document`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment api-samples/tabCapture/service-worker.js:31 — "Send a message to the receiver tab" repeats the code it sits on: 4 of its 4 words (send, message, receiver, tab) are already in `chrome.tabs.sendMessage(receiverTabId, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment api-samples/tabs/screenshot/service-worker.js:18 — "Send screenshotUrl to the tab." repeats the code it sits on: 4 of its 4 words (send, screenshot, url, tab) are already in `chrome.tabs.sendMessage(tabId, { msg: 'screenshot', data: screenshotUrl });`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment api-samples/userScripts/options.js:99 — "Register listener for save button click." repeats the code it sits on: 4 of its 5 words (listener, save, button, click) are already in `document.getElementById(SAVE_BUTTON_ID).addEventListener('click', onSave);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/script.js:49 — "Play/Pause Button" repeats the code it sits on: 3 of its 3 words (play, pause, button) are already in `const playPauseButton = document.createElement('button');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/script.js:71 — "Append custom controls to the message element" repeats the code it sits on: 4 of its 5 words (append, controls, message, element) are already in `messageElement.appendChild(controlsContainer);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment functional-samples/ai.gemini-on-device-audio-scribe/demo-chat-app/script.js:208 — "Add active class to clicked item" repeats the code it sits on: 4 of its 5 words (add, active, class, item) are already in `item.classList.add('active');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment functional-samples/tutorial.focus-mode-debugging/background.js:32 — "Set the action badge to the next state" repeats the code it sits on: 5 of its 5 words (set, action, badge, next, state) are already in `await chrome.action.setBadgeText({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment functional-samples/tutorial.focus-mode-debugging/fixed/background.js:32 — "Set the action badge to the next state" repeats the code it sits on: 5 of its 5 words (set, action, badge, next, state) are already in `await chrome.action.setBadgeText({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment functional-samples/tutorial.focus-mode/background.js:32 — "Set the action badge to the next state" repeats the code it sits on: 5 of its 5 words (set, action, badge, next, state) are already in `await chrome.action.setBadgeText({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment functional-samples/tutorial.google-analytics/scripts/google-analytics.js:112 — "Fire a page view event." repeats the code it sits on: 4 of its 4 words (fire, page, view, event) are already in `async firePageViewEvent(pageTitle, pageLocation, additionalParams = {})`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment functional-samples/tutorial.google-analytics/scripts/google-analytics.js:121 — "Fire an error event." repeats the code it sits on: 3 of its 3 words (fire, error, event) are already in `async fireErrorEvent(error, additionalParams = {})`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D30 · Dependency Vulnerabilities · Low CVE · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R8 · Dependency Hygiene · Test-only dependency 'puppeteer' in production deps · ×2
  • Test-only dependency 'puppeteer' in production deps functional-samples/tutorial.puppeteer/package.json:6 — Only test files import it (first: functional-samples/tutorial.puppeteer/index.test.js:16) — move it to devDependencies.
  • Test-only dependency 'puppeteer' in production deps functional-samples/tutorial.terminate-sw/puppeteer/package.json:6 — Only test files import it (first: functional-samples/tutorial.terminate-sw/puppeteer/index.test.js:17) — move it to devDependencies.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: api-samples/downloads/download_manager/popup.js, api-samples/downloads/download_links/popup.js. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (6 single-owned of 43 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 43 of the 190 production source files in this repository met that bar). They are anonymized user #2 (1 file(s)), anonymized user #3 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: api-samples/fontSettings/fontSettings Advanced/js/cr.js, api-samples/idle/history.js.
D19 · Documentation Quality · Documentation · ×1
  • Documentation: no map of the repository's parts README.md:1 — The repository has 9 units (`sample-list-generator`, `ai.gemini-in-the-cloud`, `ai.gemini-on-device`, `ai.gemini-on-device-calendar-mate`, `ai.gemini-on-device-summarization`, ...); `README.md` and the documents it links name none of them. Add a short list of the parts and what each does.
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 1 of 8 project(s) overshoot their size bounds, lowering Project Cohesion to 7.5/10. The most over is `(repository root)` (11110 LoC, 693 module-visible types across 379 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — 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.
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 2/5 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `_archive/apps/samples/dart`, `functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm`, `functional-samples/cookbook.wasm-helloworld-print/wasm`.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST .github/workflows/dependabot-auto-merge.yml:10 — No static application security testing detected. For this repository's stack, add the Dart analyzer's security lints plus `semgrep --config=auto` as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · Dependabot does not watch cargo · ×1
  • Dependabot does not watch cargo .github/dependabot.yml:2 — `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `cargo`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 0 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/7 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Java packages are not null-marked everywhere · ×1
  • Java packages are not null-marked everywhere — 0/1 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Minor — 4 finding(s)
D12 · Dependency Hygiene · Outdated · ×2
  • Outdated: wasm-bindgen — `wasm-bindgen` is locked at 0.2.85 but 0.2.130 is the current stable release on crates.io, and it already satisfies the `"0.2.84"` requirement declared in functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p wasm-bindgen` and commit the updated Cargo.lock.
  • Outdated: web-sys — `web-sys` is locked at 0.3.62 but 0.3.107 is the current stable release on crates.io, and it already satisfies the `"0.3.61"` requirement declared in functional-samples/cookbook.wasm-helloworld-print-nomodule/wasm/Cargo.toml — so the lockfile is behind this repository's own declared range. Run `cargo update -p web-sys` and commit the updated Cargo.lock.
D24 · Comment Value · doc comments repeat the names · ×2
  • doc comments repeat the names api-samples/fontSettings/fontSettings Advanced/js/cr.js:20 — 1 of 50 documented parameters and 1 of 47 summaries in `chrome-extensions-samples` only repeat the member or parameter name (e.g. "The global object." for `global`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names functional-samples/tutorial.terminate-sw/puppeteer/index.test.js:43 — 1 of 4 documented parameters and 0 of 2 summaries in `puppeteer-demo` only repeat the member or parameter name (e.g. "Browser instance" for `browser`). Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-ce3e168d22264218b668312c1be77a81/history.json --exit-code 0 --source .4artifacts/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-ce3e168d22264218b668312c1be77a81/tree.json --exit-code 0 --source .1artifacts/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 _archive/apps/samples/appengine-channelapi/appengine/static --exclude _archive/apps/samples/calculator/jquery --exclude _archive/apps/samples/calculator/tests --exclude _archive/apps/samples/clock/lib --exclude _archive/apps/samples/clock/tests --exclude _archive/apps/samples/dart/css --exclude _archive/apps/samples/dart/js --exclude _archive/apps/samples/diff/css --exclude _archive/apps/samples/diff/js --exclude _archive/apps/samples/diff/lib --exclude _archive/apps/samples/filesystem-access/js --exclude _archive/apps/samples/gdrive/js --exclude _archive/apps/samples/hello-world/styles --exclude _archive/apps/samples/identity/sample_support --exclude _archive/apps/samples/instagram-auth/_locales --exclude _archive/apps/samples/instagram-auth/styles --exclude _archive/apps/samples/io2012-presentation/css --exclude _archive/apps/samples/io2012-presentation/diff-sample-files --exclude _archive/apps/samples/io2012-presentation/js --exclude _archive/apps/samples/managed-in-app-payments/css --exclude _archive/apps/samples/managed-in-app-payments/scripts --exclude _archive/apps/samples/manga-cam/css --exclude _archive/apps/samples/mini-code-edit/cm/demo --exclude _archive/apps/samples/mini-code-edit/cm/keymap --exclude _archive/apps/samples/mini-code-edit/cm/lib --exclude _archive/apps/samples/mini-code-edit/cm/mode/clike --exclude _archive/apps/samples/mini-code-edit/cm/mode/clojure --exclude _archive/apps/samples/mini-code-edit/cm/mode/css --exclude _archive/apps/samples/mini-code-edit/cm/mode/diff --exclude _archive/apps/samples/mini-code-edit/cm/mode/ecl --exclude _archive/apps/samples/mini-code-edit/cm/mode/erlang --exclude _archive/apps/samples/mini-code-edit/cm/mode/gfm --exclude _archive/apps/samples/mini-code-edit/cm/mode/go --exclude _archive/apps/samples/mini-code-edit/cm/mode/groovy --exclude _archive/apps/samples/mini-code-edit/cm/mode/haskell --exclude _archive/apps/samples/mini-code-edit/cm/mode/htmlembedded --exclude _archive/apps/samples/mini-code-edit/cm/mode/htmlmixed --exclude _archive/apps/samples/mini-code-edit/cm/mode/javascript --exclude _archive/apps/samples/mini-code-edit/cm/mode/jinja2 --exclude _archive/apps/samples/mini-code-edit/cm/mode/less --exclude _archive/apps/samples/mini-code-edit/cm/mode/lua --exclude _archive/apps/samples/mini-code-edit/cm/mode/markdown --exclude _archive/apps/samples/mini-code-edit/cm/mode/mysql --exclude _archive/apps/samples/mini-code-edit/cm/mode/ntriples --exclude _archive/apps/samples/mini-code-edit/cm/mode/php --exclude _archive/apps/samples/mini-code-edit/cm/mode/pig --exclude _archive/apps/samples/mini-code-edit/cm/mode/plsql --exclude _archive/apps/samples/mini-code-edit/cm/mode/properties --exclude _archive/apps/samples/mini-code-edit/cm/mode/rpm --exclude _archive/apps/samples/mini-code-edit/cm/mode/rst --exclude _archive/apps/samples/mini-code-edit/cm/mode/rust --exclude _archive/apps/samples/mini-code-edit/cm/mode/scheme --exclude _archive/apps/samples/mini-code-edit/cm/mode/shell --exclude _archive/apps/samples/mini-code-edit/cm/mode/smalltalk --exclude _archive/apps/samples/mini-code-edit/cm/mode/smarty --exclude _archive/apps/samples/mini-code-edit/cm/mode/sparql --exclude _archive/apps/samples/mini-code-edit/cm/mode/stex --exclude _archive/apps/samples/mini-code-edit/cm/mode/tiddlywiki --exclude _archive/apps/samples/mini-code-edit/cm/mode/tiki --exclude _archive/apps/samples/mini-code-edit/cm/mode/vbscript --exclude _archive/apps/samples/mini-code-edit/cm/mode/velocity --exclude _archive/apps/samples/mini-code-edit/cm/mode/verilog --exclude _archive/apps/samples/mini-code-edit/cm/mode/xml --exclude _archive/apps/samples/mini-code-edit/cm/mode/xquery/test --exclude _archive/apps/samples/mini-code-edit/cm/mode/yaml --exclude _archive/apps/samples/mini-code-edit/cm/test --exclude _archive/apps/samples/mini-code-edit/cm/theme --exclude _archive/apps/samples/one-time-payment/css --exclude _archive/apps/samples/one-time-payment/scripts --exclude _archive/apps/samples/parrot-ar-drone/lib --exclude _archive/apps/samples/parrot-ar-drone/scripts --exclude _archive/apps/samples/parrot-ar-drone/styles --exclude _archive/apps/samples/parrot-ar-drone/third-party --exclude _archive/apps/samples/sandbox/styles --exclude _archive/apps/samples/sandboxed-content/styles --exclude _archive/apps/samples/serial/adkjs/app/css --exclude _archive/apps/samples/serial/adkjs/app/js --exclude _archive/apps/samples/syncfs-editor/css --exclude _archive/apps/samples/syncfs-editor/js --exclude _archive/apps/samples/tcpserver/commands --exclude _archive/apps/samples/tcpserver/styles --exclude _archive/apps/samples/text-editor/lib/ace/commands --exclude _archive/apps/samples/text-editor/lib/ace/edit_session --exclude _archive/apps/samples/text-editor/lib/ace/ext --exclude _archive/apps/samples/text-editor/lib/ace/keyboard --exclude _archive/apps/samples/text-editor/lib/ace/layer --exclude _archive/apps/samples/text-editor/lib/ace/lib --exclude _archive/apps/samples/text-editor/lib/ace/mode --exclude _archive/apps/samples/text-editor/lib/ace/model --exclude _archive/apps/samples/text-editor/lib/ace/mouse --exclude _archive/apps/samples/text-editor/lib/ace/narcissus --exclude _archive/apps/samples/text-editor/lib/ace/requirejs --exclude _archive/apps/samples/text-editor/lib/ace/test --exclude _archive/apps/samples/text-editor/lib/ace/theme --exclude _archive/apps/samples/text-editor/lib/ace/worker --exclude _archive/apps/samples/text-editor/lib/pilot --exclude _archive/apps/samples/todomvc/bower_components/director --exclude _archive/apps/samples/todomvc/js --exclude _archive/apps/samples/udp/server --exclude _archive/apps/samples/usb-label-printer/styles --exclude _archive/apps/samples/weather/lib --exclude _archive/apps/samples/web-store/css --exclude _archive/apps/samples/web-store/js --exclude _archive/apps/samples/webgl-pointer-lock/js --exclude _archive/apps/samples/webgl-pointer-lock/obj --exclude _archive/apps/samples/webgl-pointer-lock/styles --exclude _archive/apps/samples/webserver/_locales --exclude _archive/apps/samples/webserver/styles --exclude _archive/apps/samples/window-options/js --exclude _archive/apps/samples/windows/scripts --exclude _archive/apps/samples/windows/styles --exclude _archive/mv2/api/browserAction/make_page_red --exclude _archive/mv2/api/commands --exclude _archive/mv2/api/contextMenus/basic --exclude _archive/mv2/api/contextMenus/event_page --exclude _archive/mv2/api/devtools --exclude _archive/mv2/api/document_scan --exclude _archive/mv2/api/downloads/download_filename_controller --exclude _archive/mv2/api/downloads/download_links --exclude _archive/mv2/api/downloads/download_manager/_locales --exclude _archive/mv2/api/downloads/download_open/_locales --exclude _archive/mv2/api/downloads/downloads_overwrite --exclude _archive/mv2/api/fileSystemProvider/basic --exclude _archive/mv2/api/fontSettings/css --exclude _archive/mv2/api/fontSettings/js --exclude _archive/mv2/api/i18n/cld --exclude _archive/mv2/api/i18n/getMessage/_locales --exclude _archive/mv2/api/i18n/localizedHostedApp/_locales --exclude _archive/mv2/api/omnibox/simple-example --exclude _archive/mv2/api/override --exclude _archive/mv2/api/power/_locales --exclude _archive/mv2/api/tabs/inspector --exclude _archive/mv2/api/topsites/magic8ball --exclude _archive/mv2/api/ttsEngine --exclude _archive/mv2/api/webNavigation/basic/_locales --exclude _archive/mv2/api/webview --exclude _archive/mv2/extensions/calendar/_locales --exclude _archive/mv2/extensions/calendar/javascript --exclude _archive/mv2/extensions/calendar/views --exclude _archive/mv2/extensions/catblock --exclude _archive/mv2/extensions/catifier --exclude _archive/mv2/extensions/chrome_search --exclude _archive/mv2/extensions/gdocs/js --exclude _archive/mv2/extensions/gmail/_locales --exclude _archive/mv2/extensions/irc/app --exclude _archive/mv2/extensions/irc/servlet/jstemplate --exclude _archive/mv2/extensions/managed_bookmarks --exclude _archive/mv2/extensions/news/_locales --exclude _archive/mv2/extensions/news/css --exclude _archive/mv2/extensions/news/javascript --exclude _archive/mv2/extensions/news/views --exclude _archive/mv2/extensions/news_i18n/_locales --exclude _archive/mv2/extensions/no_cookies --exclude _archive/mv2/extensions/plugin_settings/_locales --exclude _archive/mv2/extensions/plugin_settings/css --exclude _archive/mv2/extensions/plugin_settings/domui/css --exclude _archive/mv2/extensions/plugin_settings/domui/js --exclude _archive/mv2/extensions/plugin_settings/js --exclude _archive/mv2/extensions/plugin_settings/options/css --exclude _archive/mv2/extensions/plugin_settings/options/js --exclude _archive/mv2/extensions/proxy_configuration/_locales --exclude _archive/mv2/extensions/proxy_configuration/test --exclude _archive/mv2/howto/tab_shortcuts --exclude _archive/mv2/tutorials/oauth_starter --exclude _archive/mv2/tutorials/oauth_tutorial_complete .3artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .27artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—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—
D36 · Supply-chain Provenance & Signingprovenance—provenance: not applicable — 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).0—
D37 · Vulnerability-disclosure Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1dd6c-12b0-7d4c-a99f-97156898b1cf · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md