Public report of borealBytes/hermes-wearos, published 17 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 reportMeasured 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, 17 November 2026, 08:25 UTC · Survey ID cd_e39864860dbb42f0af20447c51cabe27
borealBytes/hermes-wearos
Measured 17 November 2026, 08:24 UTC, at code version 50b65cd
First survey, so nothing to compare with yet
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
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 medium codebase: 31,224 lines of product code in 3 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Accessibility, 43.5
Findings by how serious they are
49 critical320 serious38 minor
15 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 08:24 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 ▸
72of 72 dimensions measured by tools.
398of 407 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
72dimensions across 8 lenses, read from 31,224 lines of product code in 3 projects.
borealBytes/hermes-wearos falls short of our standard for a preview release, held back most by its Accessibility lens, the interface's usability with a keyboard or assistive technology. It scores 52.5 out of 100 and is rated Adequate, and 37 of its 49 critical findings are security problems.
Accessibility, at 43.5, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the password or key in the code, worth about 3.8 points. Making the controls keyboard-usable would lift Accessibility itself, worth about 5.8 points. Raising Accessibility to 65 would lift the score to about 58.9.
Thirty-one pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Three pipeline steps run downloads nobody checks, and ten form fields can't be read by a screen reader. Pinning each tool to an exact version, checking each download against a checksum and labelling the form fields would close these risks. The unsafe setting in infrastructure or container files needs changing to safe values. The set of files in separate parts that keep changing together needs that dependency made explicit.
The product code is 31,224 lines, about €43,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 forThe 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.
If Accessibility rose from 43.5 to 65, the lowest score rated Strong, the score would rise from 52.5 to about 58.9.
Code composition: what the lines of code are
Product code 80%Tests 20%
Rebuild cost: about €43,000 · Estimate
Cost to rebuild
€14,000 to €72,000, for 240 to 763 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 53. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 31,224 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
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
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Raises the score by about 3.8 points · Low effort · REDACTED Scanning
2
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 5.8 points · Medium effort · Keyboard semantics
3
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.1 points · Medium effort · Text alternatives
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 €43,000 to build again, about 0.3 person-years of work. Its weakest lens is Accessibility, at 43.5 (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
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 3.8 points for low effort, because it clears the 1 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.0 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 5% to 11% on every change. The history of the code shows how much it changes: about 81,001 lines over the last 90 days, which is about 328,504 lines a year. At that pace, the extra work comes to an estimated 41.8 to 250.7 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
111 modules, with 105 dependencies between them. 2 loops run through 11 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 71 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
dev.hermes.wearos.data uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos.data, while a change to dev.hermes.wearos.data can't break dev.hermes.wearos.domain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
dev.hermes.wearos.domain.AwayWatch.Kind uses dev.hermes.wearos.domain.AwayWatch, so a change to dev.hermes.wearos.domain.AwayWatch can break dev.hermes.wearos.domain.AwayWatch.Kind, while a change to dev.hermes.wearos.domain.AwayWatch.Kind can't break dev.hermes.wearos.domain.AwayWatch.
Position
Below the diagonal: dev.hermes.wearos.domain.AwayWatch.Kind uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain.BackRing.Action uses dev.hermes.wearos.domain.BackRing, so a change to dev.hermes.wearos.domain.BackRing can break dev.hermes.wearos.domain.BackRing.Action, while a change to dev.hermes.wearos.domain.BackRing.Action can't break dev.hermes.wearos.domain.BackRing.
Position
Below the diagonal: dev.hermes.wearos.domain.BackRing.Action uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain.ChatMessage.Role uses dev.hermes.wearos.domain.ChatMessage, so a change to dev.hermes.wearos.domain.ChatMessage can break dev.hermes.wearos.domain.ChatMessage.Role, while a change to dev.hermes.wearos.domain.ChatMessage.Role can't break dev.hermes.wearos.domain.ChatMessage.
Position
Below the diagonal: dev.hermes.wearos.domain.ChatMessage.Role uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain.ChatSession uses dev.hermes.wearos.domain.ModelCatalog, so a change to dev.hermes.wearos.domain.ModelCatalog can break dev.hermes.wearos.domain.ChatSession, while a change to dev.hermes.wearos.domain.ChatSession can't break dev.hermes.wearos.domain.ModelCatalog.
Position
Below the diagonal: dev.hermes.wearos.domain.ChatSession uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.health uses dev.hermes.wearos.health.BodySnapshot, so a change to dev.hermes.wearos.health.BodySnapshot can break dev.hermes.wearos.health, while a change to dev.hermes.wearos.health can't break dev.hermes.wearos.health.BodySnapshot.
Position
Below the diagonal: dev.hermes.wearos.health uses a module listed above it, which is the healthy direction.
24→27 dev.hermes.wearos.net.PairingClient.Outcome uses dev.hermes.wearos.net.PairingClientpart of a loop✕
Connections
11 pairs of types, where a type in dev.hermes.wearos.net.PairingClient.Outcome uses a type in dev.hermes.wearos.net.PairingClient.
dev.hermes.wearos.net.PairingClient.Outcome uses dev.hermes.wearos.net.PairingClient, so a change to dev.hermes.wearos.net.PairingClient can break dev.hermes.wearos.net.PairingClient.Outcome, while a change to dev.hermes.wearos.net.PairingClient.Outcome can't break dev.hermes.wearos.net.PairingClient.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→29 dev.hermes.wearos.net.PairingClient.Outcome uses dev.hermes.wearos.netpart of a loop✕
Connections
2 pairs of types, where a type in dev.hermes.wearos.net.PairingClient.Outcome uses a type in dev.hermes.wearos.net.
dev.hermes.wearos.net.PairingClient.Outcome uses dev.hermes.wearos.net, so a change to dev.hermes.wearos.net can break dev.hermes.wearos.net.PairingClient.Outcome, while a change to dev.hermes.wearos.net.PairingClient.Outcome can't break dev.hermes.wearos.net.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→28 dev.hermes.wearos.ui.md uses dev.hermes.wearos.ui.md.MdBlockpart of a loop✕
Connections
3 pairs of types, where a type in dev.hermes.wearos.ui.md uses a type in dev.hermes.wearos.ui.md.MdBlock.
dev.hermes.wearos.ui.md uses dev.hermes.wearos.ui.md.MdBlock, so a change to dev.hermes.wearos.ui.md.MdBlock can break dev.hermes.wearos.ui.md, while a change to dev.hermes.wearos.ui.md can't break dev.hermes.wearos.ui.md.MdBlock.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
26→35 dev.hermes.wearos.voice.MicCodec uses dev.hermes.wearos.voicepart of a loop✕
Connections
1 pair of types, where a type in dev.hermes.wearos.voice.MicCodec uses a type in dev.hermes.wearos.voice.
dev.hermes.wearos.voice.MicCodec uses dev.hermes.wearos.voice, so a change to dev.hermes.wearos.voice can break dev.hermes.wearos.voice.MicCodec, while a change to dev.hermes.wearos.voice.MicCodec can't break dev.hermes.wearos.voice.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
dev.hermes.wearos.net.PairingClient uses dev.hermes.wearos.net.PairingClient.Outcome, so a change to dev.hermes.wearos.net.PairingClient.Outcome can break dev.hermes.wearos.net.PairingClient, while a change to dev.hermes.wearos.net.PairingClient can't break dev.hermes.wearos.net.PairingClient.Outcome.
Position
Below the diagonal: dev.hermes.wearos.net.PairingClient uses a module listed above it, which is the healthy direction.
27→29 dev.hermes.wearos.net.PairingClient uses dev.hermes.wearos.netpart of a loop✕
Connections
1 pair of types, where a type in dev.hermes.wearos.net.PairingClient uses a type in dev.hermes.wearos.net.
dev.hermes.wearos.net.PairingClient uses dev.hermes.wearos.net, so a change to dev.hermes.wearos.net can break dev.hermes.wearos.net.PairingClient, while a change to dev.hermes.wearos.net.PairingClient can't break dev.hermes.wearos.net.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
dev.hermes.wearos.ui.md.MdBlock uses dev.hermes.wearos.ui.md, so a change to dev.hermes.wearos.ui.md can break dev.hermes.wearos.ui.md.MdBlock, while a change to dev.hermes.wearos.ui.md.MdBlock can't break dev.hermes.wearos.ui.md.
Position
Below the diagonal: dev.hermes.wearos.ui.md.MdBlock uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net uses dev.hermes.wearos.domain.ModelCatalog, so a change to dev.hermes.wearos.domain.ModelCatalog can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.domain.ModelCatalog.
Position
Below the diagonal: dev.hermes.wearos.net uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net uses dev.hermes.wearos.domain.SessionHistory, so a change to dev.hermes.wearos.domain.SessionHistory can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.domain.SessionHistory.
Position
Below the diagonal: dev.hermes.wearos.net uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net uses dev.hermes.wearos.domain.SttProviders, so a change to dev.hermes.wearos.domain.SttProviders can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.domain.SttProviders.
Position
Below the diagonal: dev.hermes.wearos.net uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net uses dev.hermes.wearos.health.BodySnapshot, so a change to dev.hermes.wearos.health.BodySnapshot can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.health.BodySnapshot.
Position
Below the diagonal: dev.hermes.wearos.net uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net uses dev.hermes.wearos.net.GatewaySessions, so a change to dev.hermes.wearos.net.GatewaySessions can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.net.GatewaySessions.
Position
Below the diagonal: dev.hermes.wearos.net uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net uses dev.hermes.wearos.net.HermesApi, so a change to dev.hermes.wearos.net.HermesApi can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.net.HermesApi.
Position
Below the diagonal: dev.hermes.wearos.net uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net uses dev.hermes.wearos.net.PrivateLane, so a change to dev.hermes.wearos.net.PrivateLane can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.net.PrivateLane.
Position
Below the diagonal: dev.hermes.wearos.net uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net uses dev.hermes.wearos.data, so a change to dev.hermes.wearos.data can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.data.
Position
Below the diagonal: dev.hermes.wearos.net uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net uses dev.hermes.wearos.net.PairingClient, so a change to dev.hermes.wearos.net.PairingClient can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.net.PairingClient.
Position
Below the diagonal: dev.hermes.wearos.net uses a module listed above it, which is the healthy direction.
29→30 dev.hermes.wearos.net uses dev.hermes.wearos.domainpart of a loop✕
Connections
5 pairs of types, where a type in dev.hermes.wearos.net uses a type in dev.hermes.wearos.domain.
dev.hermes.wearos.net uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos.net, while a change to dev.hermes.wearos.net can't break dev.hermes.wearos.domain.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.AwayWatch, so a change to dev.hermes.wearos.domain.AwayWatch can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.AwayWatch.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.BackRing, so a change to dev.hermes.wearos.domain.BackRing can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.BackRing.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.BottomLayout, so a change to dev.hermes.wearos.domain.BottomLayout can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.BottomLayout.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.ChatMessage, so a change to dev.hermes.wearos.domain.ChatMessage can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.ChatMessage.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.ModelCatalog, so a change to dev.hermes.wearos.domain.ModelCatalog can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.ModelCatalog.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.NotificationDeepLink, so a change to dev.hermes.wearos.domain.NotificationDeepLink can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.NotificationDeepLink.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.RoundScreen, so a change to dev.hermes.wearos.domain.RoundScreen can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.RoundScreen.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.SessionHistory, so a change to dev.hermes.wearos.domain.SessionHistory can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.SessionHistory.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.SessionHit, so a change to dev.hermes.wearos.domain.SessionHit can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.SessionHit.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.SplashIntro, so a change to dev.hermes.wearos.domain.SplashIntro can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.SplashIntro.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.SttProviders, so a change to dev.hermes.wearos.domain.SttProviders can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.SttProviders.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.net.GatewaySessions, so a change to dev.hermes.wearos.net.GatewaySessions can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.net.GatewaySessions.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.net.HermesApi, so a change to dev.hermes.wearos.net.HermesApi can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.net.HermesApi.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.data, so a change to dev.hermes.wearos.data can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.data.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.domain.ChatSession, so a change to dev.hermes.wearos.domain.ChatSession can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.domain.ChatSession.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain uses dev.hermes.wearos.net, so a change to dev.hermes.wearos.net can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.net.
Position
Below the diagonal: dev.hermes.wearos.domain uses a module listed above it, which is the healthy direction.
30→38 dev.hermes.wearos.domain uses dev.hermes.wearospart of a loop✕
Connections
1 pair of types, where a type in dev.hermes.wearos.domain uses a type in dev.hermes.wearos.
dev.hermes.wearos.domain uses dev.hermes.wearos, so a change to dev.hermes.wearos can break dev.hermes.wearos.domain, while a change to dev.hermes.wearos.domain can't break dev.hermes.wearos.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
dev.hermes.wearos.net.PrivateLane.Outcome uses dev.hermes.wearos.net.PrivateLane, so a change to dev.hermes.wearos.net.PrivateLane can break dev.hermes.wearos.net.PrivateLane.Outcome, while a change to dev.hermes.wearos.net.PrivateLane.Outcome can't break dev.hermes.wearos.net.PrivateLane.
Position
Below the diagonal: dev.hermes.wearos.net.PrivateLane.Outcome uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.net.PrivateLane.Outcome uses dev.hermes.wearos.net, so a change to dev.hermes.wearos.net can break dev.hermes.wearos.net.PrivateLane.Outcome, while a change to dev.hermes.wearos.net.PrivateLane.Outcome can't break dev.hermes.wearos.net.
Position
Below the diagonal: dev.hermes.wearos.net.PrivateLane.Outcome uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain.ApprovalMode uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos.domain.ApprovalMode, while a change to dev.hermes.wearos.domain.ApprovalMode can't break dev.hermes.wearos.domain.
Position
Below the diagonal: dev.hermes.wearos.domain.ApprovalMode uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain.Catalog uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos.domain.Catalog, while a change to dev.hermes.wearos.domain.Catalog can't break dev.hermes.wearos.domain.
Position
Below the diagonal: dev.hermes.wearos.domain.Catalog uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.domain.CommandGroup uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos.domain.CommandGroup, while a change to dev.hermes.wearos.domain.CommandGroup can't break dev.hermes.wearos.domain.
Position
Below the diagonal: dev.hermes.wearos.domain.CommandGroup uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.voice uses dev.hermes.wearos.voice.SpeakAloud, so a change to dev.hermes.wearos.voice.SpeakAloud can break dev.hermes.wearos.voice, while a change to dev.hermes.wearos.voice can't break dev.hermes.wearos.voice.SpeakAloud.
Position
Below the diagonal: dev.hermes.wearos.voice uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.voice uses dev.hermes.wearos.data, so a change to dev.hermes.wearos.data can break dev.hermes.wearos.voice, while a change to dev.hermes.wearos.voice can't break dev.hermes.wearos.data.
Position
Below the diagonal: dev.hermes.wearos.voice uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.voice uses dev.hermes.wearos.voice.MicCodec, so a change to dev.hermes.wearos.voice.MicCodec can break dev.hermes.wearos.voice, while a change to dev.hermes.wearos.voice can't break dev.hermes.wearos.voice.MicCodec.
Position
Below the diagonal: dev.hermes.wearos.voice uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.voice uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos.voice, while a change to dev.hermes.wearos.voice can't break dev.hermes.wearos.domain.
Position
Below the diagonal: dev.hermes.wearos.voice uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.WearApp uses dev.hermes.wearos.domain.SplashIntro, so a change to dev.hermes.wearos.domain.SplashIntro can break dev.hermes.wearos.WearApp, while a change to dev.hermes.wearos.WearApp can't break dev.hermes.wearos.domain.SplashIntro.
Position
Below the diagonal: dev.hermes.wearos.WearApp uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.WearApp uses dev.hermes.wearos.net.HermesApi, so a change to dev.hermes.wearos.net.HermesApi can break dev.hermes.wearos.WearApp, while a change to dev.hermes.wearos.WearApp can't break dev.hermes.wearos.net.HermesApi.
Position
Below the diagonal: dev.hermes.wearos.WearApp uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.WearApp uses dev.hermes.wearos.data, so a change to dev.hermes.wearos.data can break dev.hermes.wearos.WearApp, while a change to dev.hermes.wearos.WearApp can't break dev.hermes.wearos.data.
Position
Below the diagonal: dev.hermes.wearos.WearApp uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.WearApp uses dev.hermes.wearos.net, so a change to dev.hermes.wearos.net can break dev.hermes.wearos.WearApp, while a change to dev.hermes.wearos.WearApp can't break dev.hermes.wearos.net.
Position
Below the diagonal: dev.hermes.wearos.WearApp uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.WearApp uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos.WearApp, while a change to dev.hermes.wearos.WearApp can't break dev.hermes.wearos.domain.
Position
Below the diagonal: dev.hermes.wearos.WearApp uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.WearApp uses dev.hermes.wearos.voice, so a change to dev.hermes.wearos.voice can break dev.hermes.wearos.WearApp, while a change to dev.hermes.wearos.WearApp can't break dev.hermes.wearos.voice.
Position
Below the diagonal: dev.hermes.wearos.WearApp uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui uses dev.hermes.wearos.domain.ModelCatalog, so a change to dev.hermes.wearos.domain.ModelCatalog can break dev.hermes.wearos.ui, while a change to dev.hermes.wearos.ui can't break dev.hermes.wearos.domain.ModelCatalog.
Position
Below the diagonal: dev.hermes.wearos.ui uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui uses dev.hermes.wearos.domain.RoundScreen, so a change to dev.hermes.wearos.domain.RoundScreen can break dev.hermes.wearos.ui, while a change to dev.hermes.wearos.ui can't break dev.hermes.wearos.domain.RoundScreen.
Position
Below the diagonal: dev.hermes.wearos.ui uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui uses dev.hermes.wearos.domain.SplashIntro, so a change to dev.hermes.wearos.domain.SplashIntro can break dev.hermes.wearos.ui, while a change to dev.hermes.wearos.ui can't break dev.hermes.wearos.domain.SplashIntro.
Position
Below the diagonal: dev.hermes.wearos.ui uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui uses dev.hermes.wearos.net.GatewaySessions, so a change to dev.hermes.wearos.net.GatewaySessions can break dev.hermes.wearos.ui, while a change to dev.hermes.wearos.ui can't break dev.hermes.wearos.net.GatewaySessions.
Position
Below the diagonal: dev.hermes.wearos.ui uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui uses dev.hermes.wearos.data, so a change to dev.hermes.wearos.data can break dev.hermes.wearos.ui, while a change to dev.hermes.wearos.ui can't break dev.hermes.wearos.data.
Position
Below the diagonal: dev.hermes.wearos.ui uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui uses dev.hermes.wearos.ui.md.MdBlock, so a change to dev.hermes.wearos.ui.md.MdBlock can break dev.hermes.wearos.ui, while a change to dev.hermes.wearos.ui can't break dev.hermes.wearos.ui.md.MdBlock.
Position
Below the diagonal: dev.hermes.wearos.ui uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos.ui, while a change to dev.hermes.wearos.ui can't break dev.hermes.wearos.domain.
Position
Below the diagonal: dev.hermes.wearos.ui uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui uses dev.hermes.wearos.voice, so a change to dev.hermes.wearos.voice can break dev.hermes.wearos.ui, while a change to dev.hermes.wearos.ui can't break dev.hermes.wearos.voice.
Position
Below the diagonal: dev.hermes.wearos.ui uses a module listed above it, which is the healthy direction.
dev.hermes.wearos uses dev.hermes.wearos.domain.BottomLayout, so a change to dev.hermes.wearos.domain.BottomLayout can break dev.hermes.wearos, while a change to dev.hermes.wearos can't break dev.hermes.wearos.domain.BottomLayout.
Position
Below the diagonal: dev.hermes.wearos uses a module listed above it, which is the healthy direction.
dev.hermes.wearos uses dev.hermes.wearos.domain.SplashIntro, so a change to dev.hermes.wearos.domain.SplashIntro can break dev.hermes.wearos, while a change to dev.hermes.wearos can't break dev.hermes.wearos.domain.SplashIntro.
Position
Below the diagonal: dev.hermes.wearos uses a module listed above it, which is the healthy direction.
dev.hermes.wearos uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos, while a change to dev.hermes.wearos can't break dev.hermes.wearos.domain.
Position
Below the diagonal: dev.hermes.wearos uses a module listed above it, which is the healthy direction.
dev.hermes.wearos uses dev.hermes.wearos.ui, so a change to dev.hermes.wearos.ui can break dev.hermes.wearos, while a change to dev.hermes.wearos can't break dev.hermes.wearos.ui.
Position
Below the diagonal: dev.hermes.wearos uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui.GwDraft uses dev.hermes.wearos.domain, so a change to dev.hermes.wearos.domain can break dev.hermes.wearos.ui.GwDraft, while a change to dev.hermes.wearos.ui.GwDraft can't break dev.hermes.wearos.domain.
Position
Below the diagonal: dev.hermes.wearos.ui.GwDraft uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.ui.GwDraft uses dev.hermes.wearos.ui, so a change to dev.hermes.wearos.ui can break dev.hermes.wearos.ui.GwDraft, while a change to dev.hermes.wearos.ui.GwDraft can't break dev.hermes.wearos.ui.
Position
Below the diagonal: dev.hermes.wearos.ui.GwDraft uses a module listed above it, which is the healthy direction.
dev.hermes.wearos.Screen uses dev.hermes.wearos, so a change to dev.hermes.wearos can break dev.hermes.wearos.Screen, while a change to dev.hermes.wearos.Screen can't break dev.hermes.wearos.
Position
Below the diagonal: dev.hermes.wearos.Screen uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 66.7 · Adequate · gated by D1, D2 ·
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 category
Findings
Severity
A05:2025 — Injection
41
High / Critical
A03:2025 — Software Supply Chain Failures
7
Medium
A07:2025 — Authentication Failures
3
High / Critical
A02:2025 — Security Misconfiguration
3
High / Critical
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; Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
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.
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Code Duplication: Edited copy of a member (10 corresponding lines)
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 — 49
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 — 320
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 — 38
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 15
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 72 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
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 — 72 dimensions across the health lenses
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
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, 398 of 407 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.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: this repository's production source spans .py, .kt, and our analyzer cannot run the .kt test suite(s) — so no coverage was collected for the repository as a whole. The Python half did build and run, and its own line coverage came back at 35.1% — but that is a figure for one half of the product, and we do not publish a partial one as if it were complete. This is OUR limitation, not a defect in the repo — coverage is excluded from the score rather than counted as a near-zero.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-contributor repository — bus factor is not applicable (1 contributor(s) across 481 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — 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. 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 — 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. 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. A language sidecar this run needed FAILED, so the code model the non-MSBuild public-API collector reads was never built — this is a DEGRADED run, not a settled gap, and the surface may well be collectable on a re-run: The Go sidecar exited 0 and produced a model, but its own source census reports it opened ZERO Go files — while the engine's presence probe found Go source in this tree. The model is therefore empty for a reason on OUR side, not the repository's, and Go is recorded as unread rather than as clean.
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.
D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 1075 sampled here came from .kt files. This repository's .py source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
D32 Data Compliance (PII/GDPR) — 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. `app/src/main/java/dev/hermes/wearos/MainActivity.kt`, `app/src/main/java/dev/hermes/wearos/WearApp.kt`, `app/src/main/java/dev/hermes/wearos/data/AppSettings.kt`, `app/src/main/java/dev/hermes/wearos/domain/SttProviders.kt`, `app/src/main/java/dev/hermes/wearos/domain/TailnetState.kt`, … (+8 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in REDACTED, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. An image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository. (rule: registry). The renderer reported: docker build failed (exit 1) — 16 | >>> FROM hermes-film:dev 17 | 18 | COPY hermes-plugin/ /opt/wearos/plugin/ -------------------- ERROR: failed to solve: hermes-film:dev: failed to resolve source metadata for docker.io/library/hermes-film:dev: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — 16 | >>> FROM hermes-film:dev 17 | 18 | COPY hermes-plugin/ /opt/wearos/plugin/ -------------------- ERROR: failed to solve: hermes-film:dev: failed to resolve source metadata for docker.io/library/hermes-film:dev: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
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.
DM8 Value-object opportunities — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check finds primitive parameters that travel together through several signatures of the domain (a missing value object). Its deterministic rule has not yet shown 95 % precision on adjudicated rows, so the clumps it finds are counted here and not published as findings, and the card carries no score. That is a limit of the analyzer, not a finding about your code.
DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
DM9 Scattered domain decisions — 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Go, Kotlin, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Go, Kotlin, Python is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X16 Unfloored truncation loop — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X18 Disposal-pattern correctness — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X29 Per-element action decided by a fixed element — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X3 Exception handling — 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. 51 further occurrence(s) are not listed individually; the score already reflects all 91.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
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.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
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.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
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.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
61 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was WearKitPane at 187. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being MdTextKt.MdBlockView at 17 — they are counted neither in the figure above nor in this dimension's score.
+ 43 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 6 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with WearKitPane (cyclomatic 187), SettingsScreenKt.SettingsScreen (cyclomatic 164), MainActivity.onCreate (cyclomatic 146). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 6 together lifts Cyclomatic Complexity from 3.5 to about 5.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 71 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 10 bodies over 60 down to 60 or less in Cognitive Complexity — start with SettingsScreenKt.SettingsScreen (cognitive 363), plugin.WearKitPane (cognitive 274), MainActivity.onCreate (cognitive 165). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 10 together lifts Cognitive Complexity from 2.0 to about 4.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.4 / 10Strong✓ 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.
Resolve the 11 FileTooLong finding(s) in God Classes — start with SettingsScreen.kt, MainActivity.kt, REDACTED. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 6 TooManyMethods finding(s) in God Classes — start with AppSettings.kt, ChatSession.kt, WearApp.kt. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 MethodTooLong finding(s) in God Classes — start with MainActivity.kt, DevAskReceiver.kt, VoiceEnroll.kt. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
39 duplicated block group(s) detected. 4.0 % of the production lines (1,242 of 31,224) are in a reported copy. A further 26 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 65 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:353
+ 32 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with WearApp.kt (2), stt_install.py (2), RunKeeperService.kt. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 6 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with WearApp.kt, SessionsScreen.kt, PromptEditor.kt. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with SettingsScreen.kt (2), ApprovalModeDialog.kt, claim_server.py. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
3 production modules (Gradle+Go), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 0 module(s) off the main sequence, with abstractness counted on 2 of the 3 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
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.
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.
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.
1 outdated, 0 author-deprecated direct Go module(s), 0 pinning or checksum defect(s). Whether any of these modules is UNMAINTAINED is not graded — proxy.golang.org publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, not a registry one. Known CVEs in this module graph are D30's question, read from REDACTED and go.sum there.
Outdated: tailscale.com
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
0 of 6 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 3 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. A further 20 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict.
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.
Resolve the 17 Hotspot finding(s) in Churn × Complexity Hotspots — start with plugin.js, MainActivity.kt, SettingsScreen.kt. — One of this dimension's main actionable groups (17 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with SplashIntro.kt. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 deducted task-comment markers across 31224 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
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.
2 of 2 documentation facets pass in full. 14 document(s) read across 4 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
1 naming inconsistencies among 30 declarations measured against a convention their peers follow.
`authURL` spells `URL` where 29 names in the project spell it `Url`app/src/main/java/dev/hermes/wearos/domain/TailnetState.kt:42
What to do
Resolve the 1 `authURL` spells `URL` where 29 names in the project spell it `Url` finding(s) in Naming Consistency — start with TailnetState.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 of 2 build units (Gradle) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionapp/build.gradle.kts:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle.kts. — 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.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
62 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .kt source only — this repository's .py was not sampled for call sites, so this score covers part of the tree, not all of it.
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.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
41 finding(s): 0 critical, 34 high, 3 medium, 4 low. 31 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `docker/wearos-demo/run-rig.sh` (lines 18–90), `REDACTED` (line 48, line 49), `scripts/circle-shot.sh` (line 39), `scripts/setup.sh` (lines 106–111, line 123) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
No action in Static Analysis (SAST) — all 31 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (31 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 Medium vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 109 of the 137 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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.
Resolve the 1 Boundary-crossing change coupling finding(s) in Change Coupling — start with DevAskReceiver.kt. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Change coupling finding(s) in Change Coupling — start with Watchkit.kt. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
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.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 26 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives3.5 / 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. — docker/wearos-demo/pane-mock/pane.html:54
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.
Do you agree with this assessment?
AC2 · Forms & labels5.1 / 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. (×6) — docker/wearos-demo/pane-mock/pane.html:44, docker/wearos-demo/pane-mock/pane.html:52, hermes-plugin/desktop/plugin.js:952, …
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) — hermes-plugin/desktop/plugin.js:530, hermes-plugin/desktop/plugin.js:805, hermes-plugin/desktop/plugin.js:1080, …
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.
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.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — docker/wearos-demo/pane-mock/pane.html:5
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.
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 click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0". — hermes-plugin/desktop/plugin.js:1250
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
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.
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.
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.
Other · Architecture — Whether singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
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.
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.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
DM10 · One transaction, one aggregate10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether a single operation mutates more than one aggregate root. An aggregate is a consistency boundary, so saving two together fuses them into one — the second's invariants come to depend on the first's transaction, and the pair can no longer be separated. Reads of other aggregates are not counted.
Method: Neutral body surface (DDD-gated): every method body scanned for repository WRITE calls (Add/Update/Save/Remove/Delete/Insert/Store and their async forms), keyed on the ARGUMENT type rather than the repository type — three `IRepository<T>` writes collapse to one repository but are three distinct aggregates. Reads (Get/Find/Load/Query) are excluded, so loading another aggregate for context never counts. Score is offending methods over methods that write at all. Deterministic.
Do you agree with this assessment?
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged
Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.
Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.
Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.
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.
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.
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.
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.
Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `tailnet/go`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
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 spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 5 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:4
`REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:5
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
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.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
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.
`fs.readFileSync` in `handleCatalog` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:247
`fs.existsSync` in `handleSearch` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:326
`fs.existsSync` in `openStore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:445
`fs.existsSync` in `handleRender` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — server/watchkit/watchkit.mjs:796, server/watchkit/watchkit.mjs:809
`fs.readFileSync` in `handleRender` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:797
`fs.mkdtempSync` in `handleRender` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:801
`fs.rmSync` in `handleRender` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:818
`fs.realpathSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:874
`fs.statSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:882
`fs.readFileSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — server/watchkit/watchkit.mjs:894, server/watchkit/watchkit.mjs:909, server/watchkit/watchkit.mjs:910
`fs.existsSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — server/watchkit/watchkit.mjs:907, server/watchkit/watchkit.mjs:915
`fs.writeFileSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:930
`fs.rmSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:936
`fs.existsSync` in `mediaDerivative` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:1007
`fs.rmSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:1041
`fs.realpathSync` in `handleMedia` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:1084
`fs.statSync` in `handleMedia` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — server/watchkit/watchkit.mjs:1089, server/watchkit/watchkit.mjs:1102
`fs.existsSync` in `handleStt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:1158
`fs.rmSync` in `handleStt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:1177
`fs.existsSync` in `handleSessions` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:1234
`fs.readdirSync` in `handleApprovalsWaiting` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:1333
`fs.existsSync` in `callback to filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:1339
`fs.existsSync` in `handleSessionMessages` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — server/watchkit/watchkit.mjs:1423
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
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.
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.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. 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 `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
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.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether functions that make a cancellable request accept or pass on an AbortSignal or the coroutine's cancellation (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 1/6 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; Ktor, OkHttp newCall, URL streams) accept an AbortSignal or the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` () and hand it to the request; in a Kotlin suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`ok` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/dev/hermes/wearos/net/EndpointResolver.kt:188
`capabilities` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:237
`steerRun` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:249
`forkSession` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:267
`push` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`. — app/src/main/java/dev/hermes/wearos/net/SnapshotPusher.kt:105
What to do
Thread an AbortSignal or the coroutine's cancellation through functions that make requests, so the work stops when its caller gives up.
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.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. 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 `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a `for` loop leaves the `dict`, `set` or `deque` it is walking alone — CPython's iterators over those check that the collection has not changed size since the loop began, so a body that removes from (or empties) the very collection the loop is walking makes the next step raise `RuntimeError: dictionary changed size during iteration` and the remaining items are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for … range` leaves the slice or map it is walking alone — Go raises nothing, but the walk and the collection part: a range evaluates its slice once, so an element appended in the body is never visited and a removal by reslicing (`s = append(s[:i], s[i+1:]...)`, `slices.Delete`) shifts the next element under the index, which is then skipped while the last is read twice; a reslice, a reassignment or a sort leaves every later `s[i]` naming another element; and a map's order is unspecified, so deleting another key (or clearing the map) changes from run to run which entries the loop still sees.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
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.
`b, _ := json.Marshal(out)` writes the call's error to `_` and then uses `b` as if the call succeeded. When `json.Marshal` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. (×3) — REDACTED:289, REDACTED:295, REDACTED:303
`logs, _ := tailnet.LogsJSON()` writes the call's error to `_` and then uses `logs` as if the call succeeded. When `tailnet.LogsJSON` fails, `logs` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `logs` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — tailnet/go/cmd/smoketest/main.go:65
`tailnet.Stop()` returns an error, and the statement drops it: when `tailnet.Stop` fails nothing records it and the code after it runs as if it had succeeded. Check it (`if err := tailnet.Stop(); err != nil { … }`) and return or log it with what was being done, or assign it to `_` with a comment saying why the failure cannot matter. — tailnet/go/cmd/smoketest/main.go:107
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. (×29) — server/watchkit/stt_stream_ws.mjs:79, server/watchkit/stt_stream_ws.mjs:91, server/watchkit/stt_stream_ws.mjs:223, …
`except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×6) — REDACTED:111, REDACTED:134, REDACTED:219, …
What to do
Discarded error (assigned to `_`, then its result used)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
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).
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.
Unscored — 3 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 — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 15 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 49 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 analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — 16 | >>> FROM hermes-film:dev 17 | 18 | COPY hermes-plugin/ /opt/wearos/plugin/ -------------------- ERROR: failed to solve: hermes-film:dev: failed to resolve source metadata for docker.io/library/hermes-film:dev: pull access denied, repository does not exist or may require authorization: server message: insufficient_scope: authorization failed; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~7901 lines of test source are present (.py, .kt) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D16 Bus Factor — single-contributor repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 13 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not measured — polyglot repository, one half has no runner
DM1 Aggregate boundaries — no aggregates detected — aggregate-boundary check not applicable
DM11 Constructible invalid state — no entities detected — construction-time invariants not assessable
DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM4 Rich vs anemic model — no data-bearing entities detected — rich-vs-anemic model not assessable
DM5 Encapsulated state — no domain entities found — DM5 grades how entities protect their state, and this repository declares none
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
DM8 Value-object opportunities — not scored — the deterministic rule found 2 candidate clump(s); its rows are withheld until it has a measured precision of 95 % (a sample of fewer than 10 rows cannot show one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 12 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, 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.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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
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
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
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.
AC2 · Forms & labels· <input> without a programmatic label · ×8
<input> without a programmatic label docker/wearos-demo/pane-mock/pane.html:44— 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 hermes-plugin/desktop/plugin.js:530— 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 hermes-plugin/desktop/plugin.js:805— 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 hermes-plugin/desktop/plugin.js:1080— 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 hermes-plugin/desktop/plugin.js:1130— 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 hermes-plugin/desktop/plugin.js:1177— 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 hermes-plugin/desktop/plugin.js:1212— 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 hermes-plugin/desktop/plugin.js:1290— 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.
AC2 · Forms & labels· <textarea> without a programmatic label · ×1
<textarea> without a programmatic label docker/wearos-demo/pane-mock/pane.html:52— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <select> without a programmatic label · ×1
<select> without a programmatic label hermes-plugin/desktop/plugin.js:952— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC4 · Keyboard semantics· Click handler on a non-interactive <span> · ×1
Click handler on a non-interactive <span> hermes-plugin/desktop/plugin.js:1250— A click handler on a plain element with no role and no tabindex: even where another element's key handler can reach it, assistive tech can neither focus it nor announce what it is. Use a <button>, or add role + tabindex="0".
Boundary-crossing change coupling: DevAskReceiver.kt ↔ Watchkit.kt app/src/debug/java/dev/hermes/wearos/DevAskReceiver.kt:1— `app/src/debug/java/dev/hermes/wearos/DevAskReceiver.kt` (context debug) and `app/src/main/java/dev/hermes/wearos/net/Watchkit.kt` (context main) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `245c583b` voice: in-app Vosk model install (gateway-cached zip, Range resume, m…; `8eef8632` docs: renumber the batch-3 SPEC sections (tool-activity §12.12, hand-…; `59fe19f0` dev hook -e screen <chat|chats|settings|sessions> (⌘ popup swallows i… — run `git show` on any of them.
Swallowed exception (empty catch) server/watchkit/stt_stream_ws.mjs:79— 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) server/watchkit/stt_stream_ws.mjs:91— 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) server/watchkit/stt_stream_ws.mjs:223— 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) server/watchkit/stt_stream_ws.mjs:229— 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) server/watchkit/stt_stream_ws.mjs:230— 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) server/watchkit/stt_stream_ws.mjs:234— 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) server/watchkit/stt_stream_ws.mjs:235— 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) server/watchkit/watchkit.mjs:148— 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) server/watchkit/watchkit.mjs:154— 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) server/watchkit/watchkit.mjs:238— 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) server/watchkit/watchkit.mjs:250— 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) server/watchkit/watchkit.mjs:411— 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) server/watchkit/watchkit.mjs:518— 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) server/watchkit/watchkit.mjs:521— 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) server/watchkit/watchkit.mjs:522— 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) server/watchkit/watchkit.mjs:549— 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) server/watchkit/watchkit.mjs:599— 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) server/watchkit/watchkit.mjs:627— 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) server/watchkit/watchkit.mjs:630— 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) server/watchkit/watchkit.mjs:909— 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) server/watchkit/watchkit.mjs:1283— 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) server/watchkit/watchkit.mjs:1335— 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) server/watchkit/watchkit.mjs:1361— 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) server/watchkit/watchkit.mjs:1388— 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) server/watchkit/watchkit.mjs:1389— 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.
Sync-over-async blocking server/watchkit/watchkit.mjs:247— `fs.readFileSync` in `handleCatalog` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:326— `fs.existsSync` in `handleSearch` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:445— `fs.existsSync` in `openStore` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:796— `fs.existsSync` in `handleRender` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:797— `fs.readFileSync` in `handleRender` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:801— `fs.mkdtempSync` in `handleRender` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:809— `fs.existsSync` in `handleRender` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:818— `fs.rmSync` in `handleRender` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:874— `fs.realpathSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:882— `fs.statSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:894— `fs.readFileSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:907— `fs.existsSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:909— `fs.readFileSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:910— `fs.readFileSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:915— `fs.existsSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:930— `fs.writeFileSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:936— `fs.rmSync` in `handleImg` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:1007— `fs.existsSync` in `mediaDerivative` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:1041— `fs.rmSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:1084— `fs.realpathSync` in `handleMedia` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:1089— `fs.statSync` in `handleMedia` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:1102— `fs.statSync` in `handleMedia` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:1158— `fs.existsSync` in `handleStt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:1177— `fs.rmSync` in `handleStt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking server/watchkit/watchkit.mjs:1234— `fs.existsSync` in `handleSessions` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Hotspot: hermes-plugin/desktop/plugin.js hermes-plugin/desktop/plugin.js:578— hermes-plugin/desktop/plugin.js changed 50 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 185 in plugin.WearKitPane at line 578. 17 of those changes were fix/bug commits, and the other 33 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- hermes-plugin/desktop/plugin.js`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/MainActivity.kt app/src/main/java/dev/hermes/wearos/MainActivity.kt:211— app/src/main/java/dev/hermes/wearos/MainActivity.kt changed 59 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 146 in MainActivity.onCreate at line 211. 11 of those changes were fix/bug commits, and the other 48 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/MainActivity.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:107— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt changed 45 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 164 in SettingsScreenKt.SettingsScreen at line 107. 11 of those changes were fix/bug commits, and the other 34 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:581— REDACTED changed 48 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 46 in hermes-plugin._lane_voice at line 581. 14 of those changes were fix/bug commits, and the other 34 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/debug/java/dev/hermes/wearos/DevAskReceiver.kt app/src/debug/java/dev/hermes/wearos/DevAskReceiver.kt:46— app/src/debug/java/dev/hermes/wearos/DevAskReceiver.kt changed 30 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 63 in DevAskReceiver.onReceive at line 46. 5 of those changes were fix/bug commits, and the other 25 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/debug/java/dev/hermes/wearos/DevAskReceiver.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: server/watchkit/watchkit.mjs server/watchkit/watchkit.mjs:1464— server/watchkit/watchkit.mjs changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 68 in watchkit.server at line 1464. 4 of those changes were fix/bug commits, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- server/watchkit/watchkit.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/ui/ChatScreen.kt app/src/main/java/dev/hermes/wearos/ui/ChatScreen.kt:70— app/src/main/java/dev/hermes/wearos/ui/ChatScreen.kt changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 59 in ChatScreenKt.ChatScreen at line 70. 4 of those changes were fix/bug commits, and the other 14 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/ui/ChatScreen.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: hermes-plugin/dashboard/plugin_api.py hermes-plugin/dashboard/plugin_api.py:270— hermes-plugin/dashboard/plugin_api.py changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in plugin_api.voice_post at line 270. 6 of those changes were fix/bug commits, and the other 17 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- hermes-plugin/dashboard/plugin_api.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:1088— app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in ChatSession.catchUpActive at line 1088. 5 of those changes were fix/bug commits, and the other 23 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt:340— app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in WatchMarkdown.parseInline at line 340. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: hermes-plugin/voiceout.py hermes-plugin/voiceout.py:638— hermes-plugin/voiceout.py changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in voiceout.synthesize at line 638. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- hermes-plugin/voiceout.py`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: server/watchkit/stt_stream_ws.mjs server/watchkit/stt_stream_ws.mjs:217— server/watchkit/stt_stream_ws.mjs changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 47 in stt_stream_ws.pipeSession at line 217. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- server/watchkit/stt_stream_ws.mjs`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/ui/VoiceEnroll.kt app/src/main/java/dev/hermes/wearos/ui/VoiceEnroll.kt:89— app/src/main/java/dev/hermes/wearos/ui/VoiceEnroll.kt changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in VoiceEnrollKt.VoiceEnroll at line 89. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/ui/VoiceEnroll.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/voice/TalkOrb.kt app/src/main/java/dev/hermes/wearos/voice/TalkOrb.kt:70— app/src/main/java/dev/hermes/wearos/voice/TalkOrb.kt changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 27 in TalkOrbKt.TalkOrb at line 70. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/voice/TalkOrb.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:51— app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in SessionsScreenKt.SessionsScreen at line 51. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/voice/GatewayStt.kt app/src/main/java/dev/hermes/wearos/voice/GatewayStt.kt:93— app/src/main/java/dev/hermes/wearos/voice/GatewayStt.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in GatewayStt.start at line 93. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/voice/GatewayStt.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: app/src/main/java/dev/hermes/wearos/ui/IntroVideo.kt app/src/main/java/dev/hermes/wearos/ui/IntroVideo.kt:96— app/src/main/java/dev/hermes/wearos/ui/IntroVideo.kt changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in IntroVideoKt.IntroVideo at line 96. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/ui/IntroVideo.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: ui/SettingsScreen.kt app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt— FileTooLong — 1447 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 947 over it, 2.89× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: wearos/MainActivity.kt app/src/main/java/dev/hermes/wearos/MainActivity.kt— FileTooLong — 1321 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 821 over it, 2.64× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1307 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 807 over it, 2.61× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: watchkit/watchkit.mjs server/watchkit/watchkit.mjs— FileTooLong — 1111 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 611 over it, 2.22× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: desktop/plugin.js hermes-plugin/desktop/plugin.js— FileTooLong — 990 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 60% of them inside a single declaration: WearKitPane (578-1371). The bar is 500 significant lines; this is 490 over it, 1.98× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: domain/ChatSession.kt app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt— FileTooLong — 907 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: ChatSession (74-1499). The bar is 500 significant lines; this is 407 over it, 1.81× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: hermes-plugin/tts_air.py hermes-plugin/tts_air.py— FileTooLong — 732 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 232 over it, 1.46× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: wearos/WearApp.kt app/src/main/java/dev/hermes/wearos/WearApp.kt— FileTooLong — 588 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: WearApp (43-1066). The bar is 500 significant lines; this is 88 over it, 1.18× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: hermes-plugin/pairing.py hermes-plugin/pairing.py— FileTooLong — 530 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 30 over it, 1.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: hermes-plugin/voiceout.py hermes-plugin/voiceout.py— FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 18 over it, 1.04× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: data/AppSettings.kt app/src/main/java/dev/hermes/wearos/data/AppSettings.kt— FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: AppSettings (33-920). The bar is 500 significant lines; this is 12 over it, 1.02× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
TooManyMethods: AppSettings app/src/main/java/dev/hermes/wearos/data/AppSettings.kt:33— TooManyMethods — 126 methods. The bar is 30 methods; this is 96 over it, 4.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ChatSession app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:74— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Graph app/src/main/java/dev/hermes/wearos/WearApp.kt:50— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SpeakAloud app/src/main/java/dev/hermes/wearos/voice/SpeakAloud.kt:29— TooManyMethods — 39 methods. The bar is 30 methods; this is 9 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PairingEngine hermes-plugin/pairing.py:191— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Watchkit app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:33— TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (7 lines × 2) app/src/main/java/dev/hermes/wearos/WearApp.kt:578— app/src/main/java/dev/hermes/wearos/WearApp.kt:578-584 | app/src/main/java/dev/hermes/wearos/WearApp.kt:598-604 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/WearApp.kt:578` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) app/src/main/java/dev/hermes/wearos/WearApp.kt:595— app/src/main/java/dev/hermes/wearos/WearApp.kt:595-601 | app/src/main/java/dev/hermes/wearos/WearApp.kt:635-641 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/WearApp.kt:595` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) app/src/main/java/dev/hermes/wearos/notify/RunKeeperService.kt:53— app/src/main/java/dev/hermes/wearos/notify/RunKeeperService.kt:53-59 | app/src/main/java/dev/hermes/wearos/notify/TailnetService.kt:129-135 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1073— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1073-1079 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1167-1173 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1073` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) hermes-plugin/stt_install.py:195— hermes-plugin/stt_install.py:195-201 | hermes-plugin/tts_air.py:434-440 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) hermes-plugin/stt_install.py:344— hermes-plugin/stt_install.py:344-350 | hermes-plugin/tts_air.py:530-536 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) app/src/main/java/dev/hermes/wearos/WearApp.kt:555— app/src/main/java/dev/hermes/wearos/WearApp.kt:555-560 | app/src/main/java/dev/hermes/wearos/WearApp.kt:638-643 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/WearApp.kt:555` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:267— app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:267-272 | app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:318-323 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:267` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:223— app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:223-228 | app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:229-235 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:223` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:598— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:598-603 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:724-729 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:598` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) app/src/main/java/dev/hermes/wearos/domain/SessionHistory.kt:47— app/src/main/java/dev/hermes/wearos/domain/SessionHistory.kt:47-52 | app/src/main/java/dev/hermes/wearos/domain/SessionHistory.kt:77-82 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/domain/SessionHistory.kt:47` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) hermes-plugin/stt_install.py:245— hermes-plugin/stt_install.py:245-250 | hermes-plugin/tts_air.py:425-430 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Swallowed exception (caught, then discarded) REDACTED:111— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:134— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:219— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:274— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:328— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) REDACTED:443— `except Exception` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
MethodTooLong: MainActivity.onCreate app/src/main/java/dev/hermes/wearos/MainActivity.kt:211— MethodTooLong — onCreate runs 645 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 545 over it, 6.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DevAskReceiver.onReceive app/src/debug/java/dev/hermes/wearos/DevAskReceiver.kt:46— MethodTooLong — onReceive runs 213 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 113 over it, 2.13× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: VoiceEnrollKt.VoiceEnroll app/src/main/java/dev/hermes/wearos/ui/VoiceEnroll.kt:89— MethodTooLong — VoiceEnroll runs 138 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 38 over it, 1.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: MediaViewerKt.ZoomableMediaViewer app/src/main/java/dev/hermes/wearos/ui/md/MediaViewer.kt:91— MethodTooLong — ZoomableMediaViewer runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Graph.init app/src/main/java/dev/hermes/wearos/WearApp.kt:297— MethodTooLong — init runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Duplicated block (8 lines × 2) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:513— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:513-520 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:949-956 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:513` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) app/src/main/java/dev/hermes/wearos/ui/ApprovalModeDialog.kt:65— app/src/main/java/dev/hermes/wearos/ui/ApprovalModeDialog.kt:65-72 | app/src/main/java/dev/hermes/wearos/ui/ModelPickerDialog.kt:84-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/ApprovalModeDialog.kt:65` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1490— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1490-1497 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1514-1521 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1490` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) hermes-plugin/claim_server.py:97— hermes-plugin/claim_server.py:97-104 | REDACTED:113-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) hermes-plugin/stt_install.py:301— hermes-plugin/stt_install.py:301-310 | hermes-plugin/tts_air.py:516-523 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `hermes-plugin/stt_install.py:311` calls `setdefault`, `str`, `cpu_count` and `hermes-plugin/tts_air.py:524` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
X2 · Cancellation propagation· Suspend function with a blocking request · ×5
Suspend function with a blocking request: ok app/src/main/java/dev/hermes/wearos/net/EndpointResolver.kt:188— `ok` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: capabilities app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:237— `capabilities` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: steerRun app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:249— `steerRun` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: forkSession app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:267— `forkSession` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
Suspend function with a blocking request: push app/src/main/java/dev/hermes/wearos/net/SnapshotPusher.kt:105— `push` suspends, but makes its request with `newCall(…).execute()`, which blocks: its caller's cancellation cannot reach the request, so it runs to its end after whatever wanted it has given up — `withContext(Dispatchers.IO)` moves it off the caller's thread and does not change that. Make the request with a call that suspends: Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` over `enqueue` that cancels the `Call` in `invokeOnCancellation`.
ClassTooLong: ChatSession app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:74— ClassTooLong — 851 significant lines (blank, comment-only and punctuation-only lines excluded), 57 methods. The bar is 400 significant lines; this is 451 over it, 2.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MainActivity app/src/main/java/dev/hermes/wearos/MainActivity.kt:142— ClassTooLong — 695 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 295 over it, 1.74× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WearApp app/src/main/java/dev/hermes/wearos/WearApp.kt:43— ClassTooLong — 548 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 148 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AppSettings app/src/main/java/dev/hermes/wearos/data/AppSettings.kt:33— ClassTooLong — 484 significant lines (blank, comment-only and punctuation-only lines excluded), 126 methods. The bar is 400 significant lines; this is 84 over it, 1.21× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (5 lines × 2) app/src/main/java/dev/hermes/wearos/ui/ChatsScreen.kt:75— app/src/main/java/dev/hermes/wearos/ui/ChatsScreen.kt:75-79 | app/src/main/java/dev/hermes/wearos/ui/ChatsScreen.kt:125-131 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/ChatsScreen.kt:75` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt:386— app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt:386-390 | app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt:403-407 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt:386` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) hermes-plugin/tts_air.py:508— hermes-plugin/tts_air.py:508-512 | hermes-plugin/weight_cache.py:55-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) tools/demo/canvas_build.py:22— tools/demo/canvas_build.py:22-26 | tools/demo/gif_build.py:50-54 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
X3 · Exception handling· Discarded error (assigned to `_`, then its result used) · ×4
Discarded error (assigned to `_`, then its result used) REDACTED:289— `b, _ := json.Marshal(out)` writes the call's error to `_` and then uses `b` as if the call succeeded. When `json.Marshal` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) REDACTED:295— `b, _ := json.Marshal(out)` writes the call's error to `_` and then uses `b` as if the call succeeded. When `json.Marshal` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) REDACTED:303— `b, _ := json.Marshal(out)` writes the call's error to `_` and then uses `b` as if the call succeeded. When `json.Marshal` fails, `b` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `b` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
Discarded error (assigned to `_`, then its result used) tailnet/go/cmd/smoketest/main.go:65— `logs, _ := tailnet.LogsJSON()` writes the call's error to `_` and then uses `logs` as if the call succeeded. When `tailnet.LogsJSON` fails, `logs` is its zero value (nil for a pointer, a map or an interface), so the program panics later or goes on with a default it never chose, and nothing records why. Check the error before using `logs` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:353— app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:353-367 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:380-392 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:492-509 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:517-533 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:401— app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:401-415 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:426-440 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:448-461 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:464-477 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:196— app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:196-285 | app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:298-336 | app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:346-433 | app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:506-633 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) app/src/main/java/dev/hermes/wearos/voice/MicCodec.kt:169— app/src/main/java/dev/hermes/wearos/voice/MicCodec.kt:169-184 | app/src/main/java/dev/hermes/wearos/voice/MicCodec.kt:186-200 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) app/src/main/java/dev/hermes/wearos/notify/RunKeeperService.kt:52— app/src/main/java/dev/hermes/wearos/notify/RunKeeperService.kt:52-66 | app/src/main/java/dev/hermes/wearos/notify/TailnetService.kt:128-142 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) hermes-plugin/claim_server.py:232— hermes-plugin/claim_server.py:232-249 | REDACTED:326-340 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×3
Edited copy of a member (6 corresponding lines) app/src/main/java/dev/hermes/wearos/net/PairingClient.kt:159— app/src/main/java/dev/hermes/wearos/net/PairingClient.kt:159-166 | app/src/main/java/dev/hermes/wearos/net/PrivateLane.kt:135-140 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) app/src/main/java/dev/hermes/wearos/net/PairingClient.kt:135— app/src/main/java/dev/hermes/wearos/net/PairingClient.kt:135-141 | app/src/main/java/dev/hermes/wearos/net/PrivateLane.kt:118-123 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) hermes-plugin/align_parakeet.py:107— hermes-plugin/align_parakeet.py:107-112 | hermes-plugin/pairing.py:89-102 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (10 lines × 2) app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:361— app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:361-370 | app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:431-440 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:361` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1219— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1219-1228 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1262-1271 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1219` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1272` calls `VoicePickRow`, `setVoiceFallback` and `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1229` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:210— app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:210-219 | app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:367-376 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:210` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) app/src/main/java/dev/hermes/wearos/domain/ProfileLogic.kt:25— app/src/main/java/dev/hermes/wearos/domain/ProfileLogic.kt:25-36 | app/src/main/java/dev/hermes/wearos/domain/ProfileLogic.kt:43-55 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) hermes-plugin/claim_server.py:82— hermes-plugin/claim_server.py:82-94 | REDACTED:99-110 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) app/src/main/java/dev/hermes/wearos/domain/GatewayModel.kt:242— app/src/main/java/dev/hermes/wearos/domain/GatewayModel.kt:242-250 | app/src/main/java/dev/hermes/wearos/domain/GatewayModel.kt:258-266 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) hermes-plugin/claim_server.py:258— hermes-plugin/claim_server.py:258-267 | REDACTED:348-356 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:187— app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:187-193 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:247-254 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:1226— app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:1226-1233 | app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:1236-1242 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
AC1 · Text alternatives· <canvas> without a text alternative · ×1
<canvas> without a text alternative docker/wearos-demo/pane-mock/pane.html:54— 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.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark docker/wearos-demo/pane-mock/pane.html:5— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
WearKitPane (cyclomatic 187) hermes-plugin/desktop/plugin.js:578— WearKitPane has cyclomatic complexity 187 (threshold 15). Of this number, 139 points are the body's own statements and 48 belong to 56 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SettingsScreenKt.SettingsScreen (cyclomatic 164) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:107— SettingsScreenKt.SettingsScreen has cyclomatic complexity 164 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainActivity.onCreate (cyclomatic 146) app/src/main/java/dev/hermes/wearos/MainActivity.kt:211— MainActivity.onCreate has cyclomatic complexity 146 (threshold 15). 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.
watchkit.server (cyclomatic 68) server/watchkit/watchkit.mjs:1464— watchkit.server has cyclomatic complexity 68 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous) (cyclomatic 68) server/watchkit/watchkit.mjs:1464— (anonymous) has cyclomatic complexity 68 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DevAskReceiver.onReceive (cyclomatic 63) app/src/debug/java/dev/hermes/wearos/DevAskReceiver.kt:46— DevAskReceiver.onReceive has cyclomatic complexity 63 (threshold 15). 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.
ChatScreenKt.ChatScreen (cyclomatic 59) app/src/main/java/dev/hermes/wearos/ui/ChatScreen.kt:70— ChatScreenKt.ChatScreen has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
stt_stream_ws.pipeSession (cyclomatic 47) server/watchkit/stt_stream_ws.mjs:217— stt_stream_ws.pipeSession has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 4 of the 47 points are its own statements and the rest belongs to 11 function items inside it that branch (a function literal at line 295, cleanup, a function literal at line 251, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
hermes-plugin._lane_voice (cyclomatic 46) REDACTED:581— hermes-plugin._lane_voice has cyclomatic complexity 46 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
plugin_api.voice_post (cyclomatic 43) hermes-plugin/dashboard/plugin_api.py:270— plugin_api.voice_post has cyclomatic complexity 43 (threshold 15). 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.
WatchMarkdown.parseInline (cyclomatic 42) app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt:340— WatchMarkdown.parseInline has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WatchMarkdown.parse (cyclomatic 38) app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt:152— WatchMarkdown.parse has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MainActivityKt.ChatBody (cyclomatic 32) app/src/main/java/dev/hermes/wearos/MainActivity.kt:1373— MainActivityKt.ChatBody has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
toolResult (cyclomatic 32) server/watchkit/watchkit.mjs:654— toolResult has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GatewayStt.start (cyclomatic 31) app/src/main/java/dev/hermes/wearos/voice/GatewayStt.kt:93— GatewayStt.start has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
watchkit.handleSessionFork (cyclomatic 31) server/watchkit/watchkit.mjs:452— watchkit.handleSessionFork has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
handleImg (cyclomatic 31) server/watchkit/watchkit.mjs:857— handleImg has cyclomatic complexity 31 (threshold 15). 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.
handleSearch (cyclomatic 30) server/watchkit/watchkit.mjs:309— handleSearch has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
watchkit.mediaDerivative (cyclomatic 29) server/watchkit/watchkit.mjs:1000— watchkit.mediaDerivative has cyclomatic complexity 29 (threshold 15). Of this number, 15 points are the body's own statements and 14 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
IntroVideoKt.IntroVideo (cyclomatic 28) app/src/main/java/dev/hermes/wearos/ui/IntroVideo.kt:96— IntroVideoKt.IntroVideo has cyclomatic complexity 28 (threshold 15). 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.
TalkOrbKt.TalkOrb (cyclomatic 27) app/src/main/java/dev/hermes/wearos/voice/TalkOrb.kt:70— TalkOrbKt.TalkOrb has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
weight_cache.fetch (cyclomatic 27) hermes-plugin/weight_cache.py:91— weight_cache.fetch has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
handleMedia (cyclomatic 26) server/watchkit/watchkit.mjs:1069— handleMedia has cyclomatic complexity 26 (threshold 15). 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.
VoiceEnrollKt.VoiceEnroll (cyclomatic 25) app/src/main/java/dev/hermes/wearos/ui/VoiceEnroll.kt:89— VoiceEnrollKt.VoiceEnroll has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hermes-plugin.delegate_enablement (cyclomatic 24) REDACTED:1113— hermes-plugin.delegate_enablement has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hermes-plugin.local_checks (cyclomatic 23) REDACTED:823— hermes-plugin.local_checks has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MediaViewerKt.ZoomableMediaViewer (cyclomatic 22) app/src/main/java/dev/hermes/wearos/ui/md/MediaViewer.kt:91— MediaViewerKt.ZoomableMediaViewer has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
hermes-plugin._fix_serve (cyclomatic 22) REDACTED:1339— hermes-plugin._fix_serve has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CommandsOverlayKt.CommandRow (cyclomatic 21) app/src/main/java/dev/hermes/wearos/ui/CommandsOverlay.kt:179— CommandsOverlayKt.CommandRow has cyclomatic complexity 21 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
plugin.voSoundTest (cyclomatic 21) hermes-plugin/desktop/plugin.js:159— plugin.voSoundTest has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 177, 166). 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.
watchkit.handleApprovalsWaiting (cyclomatic 21) server/watchkit/watchkit.mjs:1325— watchkit.handleApprovalsWaiting has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
MainActivityKt.OrbCluster (cyclomatic 20) app/src/main/java/dev/hermes/wearos/MainActivity.kt:1753— MainActivityKt.OrbCluster has cyclomatic complexity 20 (threshold 15). 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.
MdTextKt.ActivityRunCard (cyclomatic 20) app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:190— MdTextKt.ActivityRunCard has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
handleSessionPromote (cyclomatic 20) server/watchkit/watchkit.mjs:565— handleSessionPromote has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
ChatSession.catchUpActive (cyclomatic 19) app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:1088— ChatSession.catchUpActive has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SessionsScreenKt.SessionsScreen (cyclomatic 19) app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:51— SessionsScreenKt.SessionsScreen has cyclomatic complexity 19 (threshold 15). 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.
voiceout.synthesize (cyclomatic 19) hermes-plugin/voiceout.py:638— voiceout.synthesize has cyclomatic complexity 19 (threshold 15). 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.
handleSessions (cyclomatic 19) server/watchkit/watchkit.mjs:1221— handleSessions has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
hermes-plugin._cron_title (cyclomatic 18) REDACTED:746— hermes-plugin._cron_title has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
align_parakeet._fit_to_script (cyclomatic 18) hermes-plugin/align_parakeet.py:224— align_parakeet._fit_to_script has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
voRecConfirm (cyclomatic 18) hermes-plugin/desktop/plugin.js:378— voRecConfirm has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 2 function literals 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.
ChatSession.handleEvent (cyclomatic 17) app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:598— ChatSession.handleEvent has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
stt_stream_ws.sttProbe (cyclomatic 17) server/watchkit/stt_stream_ws.mjs:57— stt_stream_ws.sttProbe has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 2 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 81, finish, runNext, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
voRecStart (cyclomatic 17) hermes-plugin/desktop/plugin.js:293— voRecStart has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (_recEnd, tick, onaudioprocess, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
VoskInstaller.transfer (cyclomatic 16) app/src/main/java/dev/hermes/wearos/voice/VoskInstaller.kt:95— VoskInstaller.transfer has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TailnetClient.funnel_attr_present (cyclomatic 16) REDACTED:179— TailnetClient.funnel_attr_present has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
stt_stream.run_parakeet (cyclomatic 16) server/watchkit/stt_stream.py:83— stt_stream.run_parakeet has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
decodeFrames (cyclomatic 16) server/watchkit/stt_stream_ws.mjs:166— decodeFrames has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Repeated repair: app/src/main/java/dev/hermes/wearos/domain/SplashIntro.kt app/src/main/java/dev/hermes/wearos/domain/SplashIntro.kt:50— app/src/main/java/dev/hermes/wearos/domain/SplashIntro.kt changed 7 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is SplashIntro.decide at line 50), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(splash): cold start reveals on a MOVING film frame — no still-orb, no curtain (#30)”; “fix(splash): the system splash IS the curtain — icon holds until the media paints, 140 ms fade (#23)”; “fix(splash): the film answers the REAL launcher — batch item 12”; “fix(karaoke+splash): the spoken line FOLLOWS — and the film waits long enough to play”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-14..2026-11-12, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-14 10:58:46 -05:00' --until='2026-11-12 10:58:46 -05:00' --full-history --no-merges -- app/src/main/java/dev/hermes/wearos/domain/SplashIntro.kt`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
SettingsScreenKt.SettingsScreen (cognitive 363) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:107— SettingsScreenKt.SettingsScreen has cognitive complexity 363 (threshold 15). Drivers by points: if/else 195 (323 pts), error handling 8 (15 pts), boolean chains 14, match/switch 6 (11 pts) (nesting depth added 140). 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.
plugin.WearKitPane (cognitive 274) hermes-plugin/desktop/plugin.js:578— plugin.WearKitPane has cognitive complexity 274 (threshold 15). Drivers by points: ternaries 72 (169 pts), boolean chains 92, if/else 5 (12 pts), loops 1 (nesting depth added 104). Of this number, 202 points are the body's own statements and 72 belong to 18 function literals inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MainActivity.onCreate (cognitive 165) app/src/main/java/dev/hermes/wearos/MainActivity.kt:211— MainActivity.onCreate has cognitive complexity 165 (threshold 15). Drivers by points: if/else 91 (120 pts), match/switch 15 (21 pts), boolean chains 20, loops 2 (4 pts) (nesting depth added 37). 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.
ChatScreenKt.ChatScreen (cognitive 94) app/src/main/java/dev/hermes/wearos/ui/ChatScreen.kt:70— ChatScreenKt.ChatScreen has cognitive complexity 94 (threshold 15). Drivers by points: if/else 47 (70 pts), boolean chains 17, loops 4 (7 pts) (nesting depth added 26). 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.
WatchMarkdown.parseInline (cognitive 84) app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt:340— WatchMarkdown.parseInline has cognitive complexity 84 (threshold 15). Drivers by points: if/else 25 (62 pts), boolean chains 16, loops 3 (6 pts) (nesting depth added 40). 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.
WatchMarkdown.parse (cognitive 80) app/src/main/java/dev/hermes/wearos/ui/md/WatchMarkdown.kt:152— WatchMarkdown.parse has cognitive complexity 80 (threshold 15). Drivers by points: if/else 28 (59 pts), loops 4 (10 pts), boolean chains 8, match/switch 1 (3 pts) (nesting depth added 39). 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.
(anonymous) (cognitive 80) server/watchkit/watchkit.mjs:1464— (anonymous) has cognitive complexity 80 (threshold 15). Drivers by points: if/else 26 (33 pts), boolean chains 32, ternaries 3 (8 pts), error handling 4 (7 pts) (nesting depth added 15). 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.
DevAskReceiver.onReceive (cognitive 79) app/src/debug/java/dev/hermes/wearos/DevAskReceiver.kt:46— DevAskReceiver.onReceive has cognitive complexity 79 (threshold 15). Drivers by points: if/else 62 (66 pts), boolean chains 9, error handling 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 6). 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.
watchkit.server (cognitive 79) server/watchkit/watchkit.mjs:1464— watchkit.server has cognitive complexity 79 (threshold 15). Drivers by points: if/else 26 (33 pts), boolean chains 31, ternaries 3 (8 pts), error handling 4 (7 pts) (nesting depth added 15). 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.
pipeSession (cognitive 72) server/watchkit/stt_stream_ws.mjs:217— pipeSession has cognitive complexity 72 (threshold 15). Drivers by points: if/else 25 (50 pts), boolean chains 10, error handling 6 (8 pts), loops 2, ternaries 2 (nesting depth added 27). Most of this is not in the body itself: 3 of the 72 points are its own statements and the rest belongs to 15 function items inside it that branch (a function literal at line 295, cleanup, a function literal at line 251, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
hermes-plugin._lane_voice (cognitive 59) REDACTED:581— hermes-plugin._lane_voice has cognitive complexity 59 (threshold 15). Drivers by points: if/else 20 (32 pts), boolean chains 22, error handling 2 (3 pts), ternaries 1 (2 pts) (nesting depth added 14). 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.
MainActivityKt.ChatBody (cognitive 57) app/src/main/java/dev/hermes/wearos/MainActivity.kt:1373— MainActivityKt.ChatBody has cognitive complexity 57 (threshold 15). Drivers by points: if/else 31 (49 pts), boolean chains 4, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 20). 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.
plugin_api.voice_post (cognitive 49) hermes-plugin/dashboard/plugin_api.py:270— plugin_api.voice_post has cognitive complexity 49 (threshold 15). Drivers by points: if/else 19 (24 pts), boolean chains 21, error handling 2 (4 pts) (nesting depth added 7). 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.
MediaViewerKt.ZoomableMediaViewer (cognitive 46) app/src/main/java/dev/hermes/wearos/ui/md/MediaViewer.kt:91— MediaViewerKt.ZoomableMediaViewer has cognitive complexity 46 (threshold 15). Drivers by points: if/else 20 (40 pts), boolean chains 5, loops 1 (nesting depth added 20). 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.
VoiceEnrollKt.VoiceEnroll (cognitive 45) app/src/main/java/dev/hermes/wearos/ui/VoiceEnroll.kt:89— VoiceEnrollKt.VoiceEnroll has cognitive complexity 45 (threshold 15). Drivers by points: if/else 14 (25 pts), error handling 4 (10 pts), loops 2 (6 pts), boolean chains 3, match/switch 1 (nesting depth added 21). 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.
GatewayStt.start (cognitive 44) app/src/main/java/dev/hermes/wearos/voice/GatewayStt.kt:93— GatewayStt.start has cognitive complexity 44 (threshold 15). Drivers by points: if/else 17 (23 pts), loops 6 (13 pts), boolean chains 7, error handling 1 (nesting depth added 13). 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.
handleImg (cognitive 40) server/watchkit/watchkit.mjs:857— handleImg has cognitive complexity 40 (threshold 15). Drivers by points: ternaries 9 (15 pts), if/else 13 (14 pts), error handling 3 (6 pts), boolean chains 4, other 1 (nesting depth added 10). 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.
MdTextKt.ActivityRunCard (cognitive 39) app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:190— MdTextKt.ActivityRunCard has cognitive complexity 39 (threshold 15). Drivers by points: if/else 24 (34 pts), match/switch 3 (5 pts) (nesting depth added 12). 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.
VoskInstaller.transfer (cognitive 35) app/src/main/java/dev/hermes/wearos/voice/VoskInstaller.kt:95— VoskInstaller.transfer has cognitive complexity 35 (threshold 15). Drivers by points: if/else 17 (31 pts), loops 1 (2 pts), boolean chains 1, match/switch 1 (nesting depth added 15). 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.
align_parakeet._fit_to_script (cognitive 35) hermes-plugin/align_parakeet.py:224— align_parakeet._fit_to_script has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 3 (7 pts), loops 4 (6 pts), error handling 1 (3 pts), boolean chains 1 (nesting depth added 16). 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.
watchkit.handleSessionFork (cognitive 35) server/watchkit/watchkit.mjs:452— watchkit.handleSessionFork has cognitive complexity 35 (threshold 15). Drivers by points: boolean chains 12, if/else 10 (11 pts), error handling 4 (5 pts), ternaries 2 (4 pts), loops 2 (3 pts) (nesting depth added 5). Of this number, 28 points are the body's own statements and 7 belong to 3 function literals inside it that branch. 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.
watchkit.mediaDerivative (cognitive 35) server/watchkit/watchkit.mjs:1000— watchkit.mediaDerivative has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 12 (21 pts), if/else 8 (9 pts), boolean chains 5 (nesting depth added 10). Of this number, 19 points are the body's own statements and 16 belong to one function literal inside it that branches. 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.
toolResult (cognitive 35) server/watchkit/watchkit.mjs:654— toolResult has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 7 (12 pts), boolean chains 10, if/else 6 (9 pts), other 3, match/switch 1 (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.
IntroVideoKt.IntroVideo (cognitive 34) app/src/main/java/dev/hermes/wearos/ui/IntroVideo.kt:96— IntroVideoKt.IntroVideo has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (24 pts), boolean chains 8, loops 1, match/switch 1 (nesting depth added 4). 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.
weight_cache.fetch (cognitive 33) hermes-plugin/weight_cache.py:91— weight_cache.fetch has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 9, error handling 3 (4 pts), loops 1, ternaries 1 (nesting depth added 6). 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.
MainActivityKt.OrbCluster (cognitive 31) app/src/main/java/dev/hermes/wearos/MainActivity.kt:1753— MainActivityKt.OrbCluster has cognitive complexity 31 (threshold 15). Drivers by points: if/else 21 (27 pts), boolean chains 4 (nesting depth added 6). 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.
MdTextKt.ImageBlock (cognitive 31) app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:506— MdTextKt.ImageBlock has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (25 pts), error handling 2 (5 pts), boolean chains 1 (nesting depth added 12). 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.
TalkOrbKt.TalkOrb (cognitive 31) app/src/main/java/dev/hermes/wearos/voice/TalkOrb.kt:70— TalkOrbKt.TalkOrb has cognitive complexity 31 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 5, match/switch 4, loops 2 (nesting depth added 6). 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.
handleSearch (cognitive 31) server/watchkit/watchkit.mjs:309— handleSearch has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 8, other 7, ternaries 2 (3 pts), error handling 2, loops 2 (nesting depth added 4). Of this number, 30 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. 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.
watchkit.handleApprovalsWaiting (cognitive 30) server/watchkit/watchkit.mjs:1325— watchkit.handleApprovalsWaiting has cognitive complexity 30 (threshold 15). Drivers by points: boolean chains 10, error handling 4 (8 pts), loops 3 (5 pts), if/else 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 10). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. 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.
hermes-plugin.delegate_enablement (cognitive 29) REDACTED:1113— hermes-plugin.delegate_enablement has cognitive complexity 29 (threshold 15). Drivers by points: boolean chains 10, if/else 6 (9 pts), ternaries 5 (9 pts), error handling 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.
tts_air._worker_request (cognitive 29) hermes-plugin/tts_air.py:1265— tts_air._worker_request has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (20 pts), error handling 2 (6 pts), loops 2, boolean chains 1 (nesting depth added 15). 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.
hermes-plugin._cli_devices (cognitive 27) REDACTED:1599— hermes-plugin._cli_devices has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 2 (6 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 13). 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.
handleMedia (cognitive 27) server/watchkit/watchkit.mjs:1069— handleMedia has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 5 (6 pts), other 3, error handling 2 (nesting depth added 2). 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.
Graph.outboxSweep (cognitive 26) app/src/main/java/dev/hermes/wearos/WearApp.kt:840— Graph.outboxSweep has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (18 pts), match/switch 2 (5 pts), loops 1 (3 pts) (nesting depth added 12). 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.
Graph.init (cognitive 25) app/src/main/java/dev/hermes/wearos/WearApp.kt:297— Graph.init has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 5, loops 1 (2 pts) (nesting depth added 9). 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.
SessionsScreenKt.SessionsScreen (cognitive 25) app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:51— SessionsScreenKt.SessionsScreen has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (20 pts), match/switch 3 (5 pts) (nesting depth added 6). 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.
hermes-plugin.local_checks (cognitive 25) REDACTED:823— hermes-plugin.local_checks has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 12, ternaries 6 (8 pts), error handling 2, if/else 1 (2 pts), loops 1 (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
decodeFrames (cognitive 25) server/watchkit/stt_stream_ws.mjs:166— decodeFrames has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 2 (3 pts), boolean chains 1, other 1 (nesting depth added 11). 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.
OrbDialOverlayKt.OrbDialOverlay (cognitive 24) app/src/main/java/dev/hermes/wearos/ui/OrbDialOverlay.kt:48— OrbDialOverlayKt.OrbDialOverlay has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (20 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). 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.
hermes-plugin._fix_serve (cognitive 24) REDACTED:1339— hermes-plugin._fix_serve has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 8, error handling 5 (nesting depth added 3). 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.
plugin.voSoundTest (cognitive 24) hermes-plugin/desktop/plugin.js:159— plugin.voSoundTest has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, ternaries 3 (5 pts), error handling 2, if/else 2, loops 1 (2 pts) (nesting depth added 3). None of this is in the body itself: all 24 points belong to 2 function literals inside it that branch (lines 177, 166). 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.
ChatSession.catchUpActive (cognitive 23) app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:1088— ChatSession.catchUpActive has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (nesting depth added 5). 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.
DialSpin.move (cognitive 23) app/src/main/java/dev/hermes/wearos/domain/DialSpin.kt:63— DialSpin.move has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (21 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.
hermes-plugin._cron_title (cognitive 23) REDACTED:746— hermes-plugin._cron_title has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 6, error handling 2 (3 pts), ternaries 2 (3 pts), loops 1 (2 pts) (nesting depth added 6). 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.
VoiceOrTypeFieldKt.VoiceOrTypeField (cognitive 22) app/src/main/java/dev/hermes/wearos/ui/VoiceOrTypeField.kt:56— VoiceOrTypeFieldKt.VoiceOrTypeField has cognitive complexity 22 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 1, error handling 1 (nesting depth added 5). 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.
stt_stream.run_parakeet (cognitive 22) server/watchkit/stt_stream.py:83— stt_stream.run_parakeet has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4, ternaries 2 (3 pts), loops 1 (nesting depth added 6). 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.
voiceout._voiced_seconds (cognitive 21) hermes-plugin/voiceout.py:303— voiceout._voiced_seconds has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, loops 3 (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.
voiceout.synthesize (cognitive 21) hermes-plugin/voiceout.py:638— voiceout.synthesize has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 10, if/else 9 (10 pts), ternaries 1 (nesting depth added 1). 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.
BodyTools.probe (cognitive 20) app/src/main/java/dev/hermes/wearos/health/BodyTools.kt:81— BodyTools.probe has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), error handling 5 (7 pts), match/switch 2 (nesting depth added 3). 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.
VoskStt.start (cognitive 20) app/src/main/java/dev/hermes/wearos/voice/VoskStt.kt:76— VoskStt.start has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 2, boolean chains 1, loops 1 (nesting depth added 6). 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.
hermes-plugin._cli_pair (cognitive 20) REDACTED:1556— hermes-plugin._cli_pair has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 2 (3 pts), error handling 1 (2 pts) (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.
ClaimHandler.do_GET (cognitive 20) hermes-plugin/claim_server.py:181— ClaimHandler.do_GET has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 2 (4 pts), loops 1 (3 pts), boolean chains 2, error handling 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.
TailnetClient.funnel_attr_present (cognitive 20) REDACTED:179— TailnetClient.funnel_attr_present has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, error handling 2, ternaries 2, loops 1 (nesting depth added 5). 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.
stt_stream_ws.sttProbe (cognitive 20) server/watchkit/stt_stream_ws.mjs:57— stt_stream_ws.sttProbe has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 5, error handling 2, loops 2, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 20 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 81, finish, runNext, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
handleSessionPromote (cognitive 20) server/watchkit/watchkit.mjs:565— handleSessionPromote has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 6, error handling 2, other 1, ternaries 1 (nesting depth added 1). Of this number, 19 points are the body's own statements and 1 belongs to one function item inside it that branches. 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.
tts_air._run (cognitive 19) hermes-plugin/tts_air.py:461— tts_air._run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 1 (4 pts), loops 1 (3 pts), boolean chains 1, error handling 1 (nesting depth added 9). 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.
ChatSession.refreshGatewaySessions (cognitive 18) app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:1374— ChatSession.refreshGatewaySessions has cognitive complexity 18 (threshold 15). Drivers by points: error handling 7 (12 pts), if/else 4 (6 pts) (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.
TailnetEngine.run (cognitive 18) app/src/main/java/dev/hermes/wearos/net/TailnetEngine.kt:78— TailnetEngine.run has cognitive complexity 18 (threshold 15). Drivers by points: error handling 3 (7 pts), if/else 3 (7 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). 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.
tts_air._reap_stray_workers (cognitive 18) hermes-plugin/tts_air.py:1063— tts_air._reap_stray_workers has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, error handling 2 (3 pts), loops 1 (nesting depth added 5). 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.
voiceout.transcribe_pending (cognitive 18) hermes-plugin/voiceout.py:476— voiceout.transcribe_pending has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 4, error handling 1 (2 pts), loops 2 (nesting depth added 5). 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.
voRecConfirm (cognitive 18) hermes-plugin/desktop/plugin.js:378— voRecConfirm has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 7, if/else 6, ternaries 3 (4 pts), error handling 1 (nesting depth added 1). Most of this is not in the body itself: 8 of the 18 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 393, 407). 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.
handleSessions (cognitive 18) server/watchkit/watchkit.mjs:1221— handleSessions has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, other 4, if/else 3, ternaries 3, error handling 2. Of this number, 14 points are the body's own statements and 4 belong to 2 function literals inside it that branch. 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.
MainActivityKt.SwipeForward (cognitive 17) app/src/main/java/dev/hermes/wearos/MainActivity.kt:1329— MainActivityKt.SwipeForward has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 6, loops 1 (nesting depth added 5). 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.
ChatSession.ask (cognitive 17) app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:490— ChatSession.ask has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 4 (5 pts), boolean chains 3 (nesting depth added 4). 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.
BodySnapshot.buildJson (cognitive 17) app/src/main/java/dev/hermes/wearos/health/BodySnapshot.kt:71— BodySnapshot.buildJson has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 6 (nesting depth added 3). 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.
SettingsScreenKt.GatewayRow (cognitive 17) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1558— SettingsScreenKt.GatewayRow has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, boolean chains 3, match/switch 1. 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.
MdTextKt.MediaBlock (cognitive 17) app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:445— MdTextKt.MediaBlock has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (14 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 2). 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.
ClaimHandler.do_POST (cognitive 17) hermes-plugin/claim_server.py:128— ClaimHandler.do_POST has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), error handling 4 (6 pts), boolean chains 3 (nesting depth added 3). 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.
PairingEngine._prune (cognitive 17) hermes-plugin/pairing.py:213— PairingEngine._prune has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), error handling 1 (4 pts), loops 1 (nesting depth added 9). 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.
watchkit.extractMultipartFile (cognitive 17) server/watchkit/watchkit.mjs:749— watchkit.extractMultipartFile has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 6, ternaries 1 (3 pts), loops 1 (nesting depth added 5). 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.
voRecStart (cognitive 17) hermes-plugin/desktop/plugin.js:293— voRecStart has cognitive complexity 17 (threshold 15). Drivers by points: error handling 5 (6 pts), boolean chains 5, if/else 4, loops 2 (nesting depth added 1). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 7 function items inside it that branch (_recEnd, tick, onaudioprocess, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
CommandsOverlayKt.CommandsOverlay (cognitive 16) app/src/main/java/dev/hermes/wearos/ui/CommandsOverlay.kt:56— CommandsOverlayKt.CommandsOverlay has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 5 (nesting depth added 1). 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.
hermes-plugin._inventory_row (cognitive 16) REDACTED:942— hermes-plugin._inventory_row has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 3 (6 pts), if/else 2 (4 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (2 pts) (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.
hermes-plugin.tailnet_gateway_url (cognitive 16) REDACTED:1050— hermes-plugin.tailnet_gateway_url has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (6 pts), boolean chains 4, ternaries 2 (4 pts), error handling 1 (2 pts) (nesting depth added 4). 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.
watchkit.handleRender (cognitive 16) server/watchkit/watchkit.mjs:784— watchkit.handleRender has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (7 pts), boolean chains 5, if/else 3, error handling 1 (nesting depth added 3). 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.
FunctionTooLong: plugin.WearKitPane hermes-plugin/desktop/plugin.js:578— FunctionTooLong — WearKitPane runs 593 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 493 over it, 5.93× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
Change coupling: Watchkit.kt ↔ watchkit.mjs app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:1— `app/src/main/java/dev/hermes/wearos/net/Watchkit.kt` and `server/watchkit/watchkit.mjs` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) and are written in DIFFERENT LANGUAGES, so no import can join them and they cannot be co-located into one unit — they compile and ship as separate artifacts. What binds them is a CONTRACT across that boundary — an event or message name, a route, a serialised shape — that each side currently spells out on its own, which is exactly why a change to one drags the other. Declare that contract once where both sides read it (a shared schema, a generated constants file, an interface-definition file) so a change on one side fails the other's build instead of drifting silently; where the surface is too small to be worth that, name the counterpart in a comment on both sides so the next reader finds it. There is nothing here to merge. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `245c583b` voice: in-app Vosk model install (gateway-cached zip, Range resume, m…; `8eef8632` docs: renumber the batch-3 SPEC sections (tool-activity §12.12, hand-…; `d818780c` feat(notify): DESKTOP WATCH — approvals and finished answers from des… — run `git show` on any of them.
D4 · Code Duplication· Edited copies of one member (3 members, 53+ corresponding lines) · ×1
Edited copies of one member (3 members, 53+ corresponding lines) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1830— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1830-1890 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1900-1952 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1961-2017 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 53 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (44 corresponding lines) · ×1
Edited copy of a member (44 corresponding lines) app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:197— app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:197-240 | app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:357-414 — These two members are one piece of code written twice and then edited apart: 44 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:254— app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:254-294 | app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:303-339 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) app/src/main/java/dev/hermes/wearos/domain/SessionHistory.kt:42— app/src/main/java/dev/hermes/wearos/domain/SessionHistory.kt:42-60 | app/src/main/java/dev/hermes/wearos/domain/SessionHistory.kt:70-88 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) hermes-plugin/align_parakeet.py:160— hermes-plugin/align_parakeet.py:160-185 | hermes-plugin/align_parakeet.py:189-211 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×1
Edited copy of a member (13 corresponding lines) app/src/main/java/dev/hermes/wearos/voice/GatewayTts.kt:72— app/src/main/java/dev/hermes/wearos/voice/GatewayTts.kt:72-88 | app/src/main/java/dev/hermes/wearos/voice/GatewayTts.kt:96-108 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) hermes-plugin/stt_install.py:355— hermes-plugin/stt_install.py:355-364 | hermes-plugin/tts_air.py:796-811 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) hermes-plugin/stt_install.py:301— hermes-plugin/stt_install.py:301-314 | hermes-plugin/tts_air.py:516-526 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×1
Edited copy of a member (4 corresponding lines) hermes-plugin/align_parakeet.py:215— hermes-plugin/align_parakeet.py:215-218 | hermes-plugin/tts_air.py:1486-1489 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:130— app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:130-136 | app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:180-187 | app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:215-221 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 2+ corresponding lines) · ×1
Edited copies of one member (3 members, 2+ corresponding lines) app/src/main/java/dev/hermes/wearos/net/GatewaySessions.kt:98— app/src/main/java/dev/hermes/wearos/net/GatewaySessions.kt:98-99 | app/src/main/java/dev/hermes/wearos/net/HermesApi.kt:73-74 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:147-148 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 2 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (12–15 lines × 2) app/src/main/java/dev/hermes/wearos/ui/AgentPickerDialog.kt:71— app/src/main/java/dev/hermes/wearos/ui/AgentPickerDialog.kt:71-85 | app/src/main/java/dev/hermes/wearos/ui/ApprovalModeDialog.kt:60-71 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/AgentPickerDialog.kt:71` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1932— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1932-1946 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1997-2011 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1932` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1996` calls `commit` and `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1931` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11–14 lines × 2) app/src/main/java/dev/hermes/wearos/ui/AgentPickerDialog.kt:126— app/src/main/java/dev/hermes/wearos/ui/AgentPickerDialog.kt:126-139 | app/src/main/java/dev/hermes/wearos/ui/ModelPickerDialog.kt:145-155 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/AgentPickerDialog.kt:126` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14 lines × 2) app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:420— app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:420-433 | app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:620-633 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:420` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) app/src/main/java/dev/hermes/wearos/voice/VoskStt.kt:105— app/src/main/java/dev/hermes/wearos/voice/VoskStt.kt:105-117 | app/src/main/java/dev/hermes/wearos/voice/VoskStt.kt:156-167 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/voice/VoskStt.kt:105` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:585— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:585-596 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:711-722 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:987-998 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:585` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:398— app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:398-409 | app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:596-607 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:398` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 3) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1845— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1845-1855 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1910-1920 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1972-1982 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1845` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 4) app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:204— app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:204-213 | app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:300-309 | app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:403-412 | app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:601-610 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/md/MdText.kt:204` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) app/src/main/java/dev/hermes/wearos/ui/AgentPickerDialog.kt:129— app/src/main/java/dev/hermes/wearos/ui/AgentPickerDialog.kt:129-138 | app/src/main/java/dev/hermes/wearos/ui/ModelPickerDialog.kt:145-154 | app/src/main/java/dev/hermes/wearos/ui/PromptEditor.kt:231-240 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/AgentPickerDialog.kt:129` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1178— app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1178-1184 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1211-1217 | app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1254-1260 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1178` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1177` calls `availableEngines` and `app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:1210` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (3–6 lines × 4) app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:361— app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:361-363 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:386-388 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:500-505 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:524-529 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:361` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:358` calls `addQueryParameter` and `app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:384` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 4) app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:407— app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:407-411 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:432-436 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:454-458 | app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:469-473 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:407` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:413` calls `parse` and `app/src/main/java/dev/hermes/wearos/net/Watchkit.kt:460` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:406— app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:406-414 | app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:462-470 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `app/src/main/java/dev/hermes/wearos/ui/SessionsScreen.kt:406` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 3) hermes-plugin/stt_install.py:106— hermes-plugin/stt_install.py:106-111 | hermes-plugin/tts_air.py:163-168 | hermes-plugin/voiceout.py:51-56 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
X3 · Exception handling· Discarded error (an error-returning call as a bare statement) · ×1
Discarded error (an error-returning call as a bare statement) tailnet/go/cmd/smoketest/main.go:107— `tailnet.Stop()` returns an error, and the statement drops it: when `tailnet.Stop` fails nothing records it and the code after it runs as if it had succeeded. Check it (`if err := tailnet.Stop(); err != nil { … }`) and return or log it with what was being done, or assign it to `_` with a comment saying why the failure cannot matter.
Silent fallback default in catch app/src/main/java/dev/hermes/wearos/domain/GatewayModel.kt:147— `decode` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/dev/hermes/wearos/location/LocationTool.kt:49— `availableProviders` swallows every exception into `emptyList()` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:257— `SettingsScreen` swallows every exception into `"?"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/dev/hermes/wearos/ui/SettingsScreen.kt:281— `settingsGwHost` (in `SettingsScreen`) swallows every exception into `""` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch app/src/main/java/dev/hermes/wearos/voice/VoskStt.kt:63— `field` swallows every exception into `""` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
Silent fallback default in catch REDACTED:274— `_tailscale_self` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:328— `_self_node_id` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch REDACTED:443— `_read_profile_key` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch hermes-plugin/dashboard/plugin_api.py:254— `_installed_revision` swallows every exception into `return ''` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch hermes-plugin/tts_provider.py:118— `list_voices` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch server/watchkit/watchkit.mjs:849— `MOUNT_PARENTS` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch server/watchkit/watchkit.mjs:1322— `parseToolCallNames` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Duplicated predicate hermes-plugin/stt_install.py:246— `_proc is not None and _proc.poll() is None` appears character-identically in 2 files — hermes-plugin/stt_install.py, hermes-plugin/tts_air.py. 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 hermes-plugin/stt_install.py:347— `_proc.communicate(timeout=BUILD_TIMEOUT)[0] or ""` appears character-identically in 2 files — hermes-plugin/stt_install.py, hermes-plugin/tts_air.py. 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 hermes-plugin/stt_install.py:126— `shutil.which("cmake") and shutil.which("g++") and shutil.which("git")` appears character-identically in 2 files — hermes-plugin/stt_install.py, hermes-plugin/tts_air.py. 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 hermes-plugin/claim_server.py:264— `thread is not None and thread.is_alive()` appears character-identically in 2 files — hermes-plugin/claim_server.py, REDACTED. 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.
Silent fallback default on parse failure REDACTED:1109— `_profile_pin` returns `''` when `(OSError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure hermes-plugin/tts_air.py:718— `get_device` returns `'cpu'` when `(OSError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default on parse failure hermes-plugin/weight_cache.py:41— `load_index` returns `{}` when `(OSError, ValueError)` is raised, with no log or raise — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Hand-rolled JSON/XML parsing via regex server/watchkit/stt_stream_ws.mjs:257— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
Hand-rolled JSON/XML parsing via regex server/watchkit/stt_stream_ws.mjs:317— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JavaScript/TypeScript code already uses a real parser in the same package; use it here too.
No ADRs found tailnet/go/cmd/smoketest/main.go:10— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `tailnet/go/cmd/smoketest/main.go` makes this repository a deployable product (line 10).
D21 · Naming Consistency· `authURL` spells `URL` where 29 names in the project spell it `Url` · ×1
`authURL` spells `URL` where 29 names in the project spell it `Url` app/src/main/java/dev/hermes/wearos/domain/TailnetState.kt:42— 29 of 30 names in project app spell the token `Url` (29 of 30; unit: names in project app containing `Url`). Peers: AppSettings.baseUrl (app/src/main/java/dev/hermes/wearos/data/AppSettings.kt:138); AppSettings.setBaseUrl (app/src/main/java/dev/hermes/wearos/data/AppSettings.kt:164); AppSettings.mermaidBaseUrl (app/src/main/java/dev/hermes/wearos/data/AppSettings.kt:599); AppSettings.setMermaidBaseUrl (app/src/main/java/dev/hermes/wearos/data/AppSettings.kt:637); ChatSession.apiTo(baseUrl) (app/src/main/java/dev/hermes/wearos/domain/ChatSession.kt:149). Rename to `authUrl`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion app/build.gradle.kts:1— `app` (22992 LoC, 390 module-visible types across 13 directories) overshoots its size bounds. 1 of 2 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 0.0/10. 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
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.
Logging is not universal — Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`, `tailnet/go`.
No SAST REDACTED:4— No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 5 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.
No dependency-update automation REDACTED:5— `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X2 · Cancellation propagation· Not all functions that make a request accept an AbortSignal or the coroutine's cancellation · ×1
Not all functions that make a request accept an AbortSignal or the coroutine's cancellation — Only 1/6 functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http; Ktor, OkHttp newCall, URL streams) accept an AbortSignal or the coroutine's cancellation or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, a cancelled request, a shutdown, an expired deadline. Take a `signal` () and hand it to the request; in a Kotlin suspend function, make the request with a call that suspends — Ktor, OkHttp's `executeAsync()`, or a `suspendCancellableCoroutine` that cancels the `Call` — not a blocking `execute()`: `withContext(Dispatchers.IO)` moves the call off the caller's thread but does not make it cancellable; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Outdated: tailscale.com — `tailscale.com` is required at v1.104.4 in REDACTED, but v1.104.7 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get tailscale.com@v1.104.7 && go mod tidy` and commit the updated REDACTED and go.sum.
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.
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. semgrep could not parse 13 file(s) — `app/src/main/java/dev/hermes/wearos/MainActivity.kt`, `app/src/main/java/dev/hermes/wearos/WearApp.kt`, `app/src/main/java/dev/hermes/wearos/data/AppSettings.kt`, `app/src/main/java/dev/hermes/wearos/domain/SttProviders.kt`, `app/src/main/java/dev/hermes/wearos/domain/TailnetState.kt`, … (+8 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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.
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.
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.
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.
Run 01a1e89b-ded4-7a4c-b0fb-24044c6cd2f3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 49 · Warnings: 320 · Recommendations: 37 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 08:24 UTC.
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.