Public report of tmpim/casket, published 16 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, 16 November 2026, 19:32 UTC · Survey ID cd_b614617b96204c6fac00348a2eb768e5
tmpim/casket
Measured 16 November 2026, 19:32 UTC, at code version 3be7e97
First survey, so nothing to compare with yet
CAI scoreAt risk
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: 28,010 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Accessibility, 40.9
Findings by how serious they are
40 critical401 serious140 minor
13 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
16 November 2026, 19:32 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
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 ▸
56of 56 dimensions measured by tools.
534of 581 findings point to an exact file and line, so you can open each one in the code. The other 47 concern the repository as a whole, such as missing documentation.
56dimensions across 7 lenses, read from 28,010 lines of product code in 1 project.
tmpim/casket is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 49.6 out of 100, which the At risk rating leaves unchanged.
Accessibility, at 40.9, is the weakest lens and counts most in the score. The best first step is making the controls keyboard-usable, worth about 6.5 points. Fixing focus, motion and contrast comes next, worth about 3.9 points. Raising Accessibility to 70 would lift the score to about 56.5.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Eight known security holes in the packages the code depends on can be used by attackers, and four settings leave the servers or containers unsafe. Pinning each tool to an exact version, updating the vulnerable packages and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the three secrets exposed to more of the pipeline than needed, and the connection that skips the certificate check needs the certificate check switched back on. The three buttons or links with no name need a name, even when they only show an icon.
The product code is 28,010 lines, about €47,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 40.9 to 70, the lowest score rated Strong, the score would rise from 49.6 to about 56.5.
Code composition: what the lines of code are
Product code 56%Tests 44%
Rebuild cost: about €47,000 · Estimate
Cost to rebuild
€16,000 to €78,000, for 259 to 820 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 50. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 28,010 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
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Raises the score by about 6.5 points · Medium effort · Keyboard semantics
2
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Raises the score by about 3.3 points · Medium effort · Forms & labels
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 €47,000 to build again, about 0.3 person-years of work. Its weakest lens is Accessibility, at 40.9 (Weak). Accessibility is about whether the interface is built so that everyone can use it, including people who can't see the screen or can't use a mouse. Because the weakest lens counts most in the score, work on Accessibility also moves the score most.
Based on: the rebuild estimate · the Accessibility grade · how much each lens counts
What to do: Start with the Accessibility actions in Top priorities.
If you do one thing first · First action
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href. Of all the actions in this report, it raises the score most for the work it takes: about 6.5 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
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 5.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 6% to 13% on every change. The history of the code shows how much it changes: about 25,907 lines over the last 90 days, which is about 105,067 lines a year. At that pace, the extra work comes to an estimated 14.8 to 88.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.
75 modules, with 100 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 35 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.
com/tmpim/casket uses com/tmpim/casket/casketfile, so a change to com/tmpim/casket/casketfile can break com/tmpim/casket, while a change to com/tmpim/casket can't break com/tmpim/casket/casketfile.
Position
Below the diagonal: com/tmpim/casket uses a module listed above it, which is the healthy direction.
com/tmpim/casket/casket/casketmain uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/casket/casketmain, while a change to com/tmpim/casket/casket/casketmain can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/casket/casketmain uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/bind uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/bind, while a change to com/tmpim/casket/caskethttp/bind can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/bind uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskettls uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskettls, while a change to com/tmpim/casket/caskettls can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskettls uses a module listed above it, which is the healthy direction.
com/tmpim/casket/onevent/hook uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/onevent/hook, while a change to com/tmpim/casket/onevent/hook can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/onevent/hook uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/httpserver uses com/tmpim/casket/casketfile, so a change to com/tmpim/casket/casketfile can break com/tmpim/casket/caskethttp/httpserver, while a change to com/tmpim/casket/caskethttp/httpserver can't break com/tmpim/casket/casketfile.
Position
Below the diagonal: com/tmpim/casket/caskethttp/httpserver uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/httpserver uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/httpserver, while a change to com/tmpim/casket/caskethttp/httpserver can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/httpserver uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/httpserver uses com/tmpim/casket/caskettls, so a change to com/tmpim/casket/caskettls can break com/tmpim/casket/caskethttp/httpserver, while a change to com/tmpim/casket/caskethttp/httpserver can't break com/tmpim/casket/caskettls.
Position
Below the diagonal: com/tmpim/casket/caskethttp/httpserver uses a module listed above it, which is the healthy direction.
com/tmpim/casket/onevent uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/onevent, while a change to com/tmpim/casket/onevent can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/onevent uses a module listed above it, which is the healthy direction.
com/tmpim/casket/onevent uses com/tmpim/casket/onevent/hook, so a change to com/tmpim/casket/onevent/hook can break com/tmpim/casket/onevent, while a change to com/tmpim/casket/onevent can't break com/tmpim/casket/onevent/hook.
Position
Below the diagonal: com/tmpim/casket/onevent uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/basicauth uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/basicauth, while a change to com/tmpim/casket/caskethttp/basicauth can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/basicauth uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/basicauth uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/basicauth, while a change to com/tmpim/casket/caskethttp/basicauth can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/basicauth uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/browse uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/browse, while a change to com/tmpim/casket/caskethttp/browse can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/browse uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/browse uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/browse, while a change to com/tmpim/casket/caskethttp/browse can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/browse uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/chuieauth uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/chuieauth, while a change to com/tmpim/casket/caskethttp/chuieauth can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/chuieauth uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/chuieauth uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/chuieauth, while a change to com/tmpim/casket/caskethttp/chuieauth can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/chuieauth uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/errors uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/errors, while a change to com/tmpim/casket/caskethttp/errors can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/errors uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/errors uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/errors, while a change to com/tmpim/casket/caskethttp/errors can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/errors uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/expvar uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/expvar, while a change to com/tmpim/casket/caskethttp/expvar can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/expvar uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/expvar uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/expvar, while a change to com/tmpim/casket/caskethttp/expvar can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/expvar uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/extensions uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/extensions, while a change to com/tmpim/casket/caskethttp/extensions can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/extensions uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/extensions uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/extensions, while a change to com/tmpim/casket/caskethttp/extensions can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/extensions uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/fastcgi uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/fastcgi, while a change to com/tmpim/casket/caskethttp/fastcgi can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/fastcgi uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/fastcgi uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/fastcgi, while a change to com/tmpim/casket/caskethttp/fastcgi can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/fastcgi uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/forwardproxy uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/forwardproxy, while a change to com/tmpim/casket/caskethttp/forwardproxy can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/forwardproxy uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/forwardproxy uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/forwardproxy, while a change to com/tmpim/casket/caskethttp/forwardproxy can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/forwardproxy uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/geoip uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/geoip, while a change to com/tmpim/casket/caskethttp/geoip can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/geoip uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/geoip uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/geoip, while a change to com/tmpim/casket/caskethttp/geoip can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/geoip uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/gzip uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/gzip, while a change to com/tmpim/casket/caskethttp/gzip can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/gzip uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/gzip uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/gzip, while a change to com/tmpim/casket/caskethttp/gzip can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/gzip uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/header uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/header, while a change to com/tmpim/casket/caskethttp/header can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/header uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/header uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/header, while a change to com/tmpim/casket/caskethttp/header can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/header uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/internalsrv uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/internalsrv, while a change to com/tmpim/casket/caskethttp/internalsrv can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/internalsrv uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/internalsrv uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/internalsrv, while a change to com/tmpim/casket/caskethttp/internalsrv can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/internalsrv uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/limits uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/limits, while a change to com/tmpim/casket/caskethttp/limits can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/limits uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/limits uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/limits, while a change to com/tmpim/casket/caskethttp/limits can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/limits uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/log uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/log, while a change to com/tmpim/casket/caskethttp/log can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/log uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/log uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/log, while a change to com/tmpim/casket/caskethttp/log can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/log uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/markdown uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/markdown, while a change to com/tmpim/casket/caskethttp/markdown can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/markdown uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/markdown uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/markdown, while a change to com/tmpim/casket/caskethttp/markdown can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/markdown uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/mime uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/mime, while a change to com/tmpim/casket/caskethttp/mime can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/mime uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/mime uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/mime, while a change to com/tmpim/casket/caskethttp/mime can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/mime uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/pprof uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/pprof, while a change to com/tmpim/casket/caskethttp/pprof can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/pprof uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/pprof uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/pprof, while a change to com/tmpim/casket/caskethttp/pprof can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/pprof uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/prometheus uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/prometheus, while a change to com/tmpim/casket/caskethttp/prometheus can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/prometheus uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/prometheus uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/prometheus, while a change to com/tmpim/casket/caskethttp/prometheus can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/prometheus uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/proxy uses com/tmpim/casket/casketfile, so a change to com/tmpim/casket/casketfile can break com/tmpim/casket/caskethttp/proxy, while a change to com/tmpim/casket/caskethttp/proxy can't break com/tmpim/casket/casketfile.
Position
Below the diagonal: com/tmpim/casket/caskethttp/proxy uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/proxy uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/proxy, while a change to com/tmpim/casket/caskethttp/proxy can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/proxy uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/proxy uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/proxy, while a change to com/tmpim/casket/caskethttp/proxy can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/proxy uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/push uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/push, while a change to com/tmpim/casket/caskethttp/push can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/push uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/push uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/push, while a change to com/tmpim/casket/caskethttp/push can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/push uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/rate-limit uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/rate-limit, while a change to com/tmpim/casket/caskethttp/rate-limit can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/rate-limit uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/rate-limit uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/rate-limit, while a change to com/tmpim/casket/caskethttp/rate-limit can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/rate-limit uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/realip uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/realip, while a change to com/tmpim/casket/caskethttp/realip can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/realip uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/realip uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/realip, while a change to com/tmpim/casket/caskethttp/realip can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/realip uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/redirect uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/redirect, while a change to com/tmpim/casket/caskethttp/redirect can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/redirect uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/redirect uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/redirect, while a change to com/tmpim/casket/caskethttp/redirect can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/redirect uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/requestid uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/requestid, while a change to com/tmpim/casket/caskethttp/requestid can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/requestid uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/requestid uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/requestid, while a change to com/tmpim/casket/caskethttp/requestid can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/requestid uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/rewrite uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/rewrite, while a change to com/tmpim/casket/caskethttp/rewrite can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/rewrite uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/rewrite uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/rewrite, while a change to com/tmpim/casket/caskethttp/rewrite can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/rewrite uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/status uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/status, while a change to com/tmpim/casket/caskethttp/status can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/status uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/status uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/status, while a change to com/tmpim/casket/caskethttp/status can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/status uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/templates uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/templates, while a change to com/tmpim/casket/caskethttp/templates can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/templates uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/templates uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/templates, while a change to com/tmpim/casket/caskethttp/templates can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/templates uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/tmpauth uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/tmpauth, while a change to com/tmpim/casket/caskethttp/tmpauth can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/tmpauth uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/tmpauth uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/tmpauth, while a change to com/tmpim/casket/caskethttp/tmpauth can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/tmpauth uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/tryfiles uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/tryfiles, while a change to com/tmpim/casket/caskethttp/tryfiles can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/tryfiles uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/tryfiles uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/tryfiles, while a change to com/tmpim/casket/caskethttp/tryfiles can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/tryfiles uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/webdav uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/webdav, while a change to com/tmpim/casket/caskethttp/webdav can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/webdav uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/webdav uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/webdav, while a change to com/tmpim/casket/caskethttp/webdav can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/webdav uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/websocket uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/websocket, while a change to com/tmpim/casket/caskethttp/websocket can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/websocket uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/websocket uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/websocket, while a change to com/tmpim/casket/caskethttp/websocket can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/websocket uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/ipfilter uses com/tmpim/casket, so a change to com/tmpim/casket can break com/tmpim/casket/caskethttp/ipfilter, while a change to com/tmpim/casket/caskethttp/ipfilter can't break com/tmpim/casket.
Position
Below the diagonal: com/tmpim/casket/caskethttp/ipfilter uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/ipfilter uses com/tmpim/casket/caskethttp/httpserver, so a change to com/tmpim/casket/caskethttp/httpserver can break com/tmpim/casket/caskethttp/ipfilter, while a change to com/tmpim/casket/caskethttp/ipfilter can't break com/tmpim/casket/caskethttp/httpserver.
Position
Below the diagonal: com/tmpim/casket/caskethttp/ipfilter uses a module listed above it, which is the healthy direction.
com/tmpim/casket/caskethttp/ipfilter uses com/tmpim/casket/caskethttp/geoip, so a change to com/tmpim/casket/caskethttp/geoip can break com/tmpim/casket/caskethttp/ipfilter, while a change to com/tmpim/casket/caskethttp/ipfilter can't break com/tmpim/casket/caskethttp/geoip.
Position
Below the diagonal: com/tmpim/casket/caskethttp/ipfilter uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 49.4 · Weak · gated by D1, D2, X5 ·
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
53
High / Critical
A03:2025 — Software Supply Chain Failures
23
High / Critical
A02:2025 — Security Misconfiguration
10
High / Critical
A07:2025 — Authentication Failures
1
High / Critical
Roadmap
Top priorities: Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href; Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1; Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
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 — 40
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 — 401
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 — 140
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 56 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 1.0, 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 — 56 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, 534 of 581 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.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its Go module dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — 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.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D26 Project Cohesion — 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. `(repository root)` (27850 LoC, 250 module-visible types across 74 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
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. `docs/src/.vitepress/theme/index.ts` 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.
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.
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, Vue components 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, Vue components 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.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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.
X17 Uncapped recursion over a caller-supplied document — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, 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.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Scala, Ruby and Python source only, and no C# was loaded and no JavaScript/TypeScript, Java, Scala, Ruby or Python was found in this repository, 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.
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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
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.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
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.
D22 Internal API Consistency: API consistency compares the call shapes of members that play the same role on the exposed C# surface: whether the API suits its callers is not measured, and surfaces in other languages are not measured.
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.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
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.
+ 52 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with replacer.getSubstitution (cyclomatic 95), proxy.parseBlock (cyclomatic 77), forwardproxy.setup (cyclomatic 76). — 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 8 together lifts Cyclomatic Complexity from 3.1 to about 6.2/10, projected with the scoring formula itself and assuming each lands exactly at 30; 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.
+ 97 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 12 bodies over 60 down to 60 or less in Cognitive Complexity — start with forwardproxy.setup (cognitive 173), caskettls.setupTLS (cognitive 167), proxy.parseBlock (cognitive 117). — 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 12 together lifts Cognitive Complexity from 2.0 to about 3.2/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 Classes8.7 / 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 3 MethodTooLong finding(s) in God Classes — start with replacer.go, REDACTED, forwardproxy.go. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 FunctionTooLong finding(s) in God Classes — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 TooManyMethods finding(s) in God Classes — start with tplcontext.go, render.go. — One of this dimension's main actionable groups (2 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.
17 duplicated block group(s) detected. 4.0 % of the production lines (1,129 of 28,010) are in a reported copy. A further 18 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (53 corresponding lines)dnsproviders/namedotcom/namedotcom.go:36
Edited copy of a member (61 corresponding lines)caskethttp/httpserver/mitm.go:377
+ 25 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with web.go, REDACTED, auth.go. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Edited copy of a member (14 corresponding lines) finding(s) in Code Duplication — start with REDACTED, handler.go. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Duplicated block (11 lines × 4) finding(s) in Code Duplication — start with cloudflare.go, dnspod.go. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with tplcontext.go, logger.go. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 61.2% — 50 file(s) below 50%. Measured from the Go suite (github.com/tmpim/casket: `go test -coverprofile -coverpkg=./...`, the 3 run(s) test reliability made). Taken over 3 runs of the suite: a line counts as covered only when every run executed it. 19 line(s) in 6 file(s) were executed in some runs and not in others, so they are not counted.
Tests reach code only in some runs: casket.go · ×6casket.go:818
What to do
Resolve the 50 Low coverage finding(s) in Code Coverage — start with REDACTED (3), handler.go (2), run.go. — One of this dimension's main actionable groups (50 warning-level).
Resolve the 6 Tests reach code only in some runs finding(s) in Code Coverage — start with casket.go, reloader.go, mitm.go. — One of this dimension's main actionable groups (6 recommendation-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
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.
31 outdated, 0 author-deprecated direct Go module(s), 6 pinning or checksum defect(s). 54 of 54 direct requirement(s) were graded against proxy.golang.org (0 not served there, 5 publishing no tagged release to be behind). 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.
Dependency pinned to a stale untagged commit: github.com/captncraig/cors · ×6
Outdated: github.com/caddyserver/certmagic · ×31
What to do
Resolve the 6 Dependency pinned to a stale untagged commit finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (6 warning-level).
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 162 required Go module(s) use a banned license. Licences were read per module version from the licence files pkg.go.dev detects (via api.deps.dev), over every module this repository's REDACTED requires, direct and indirect, at the version the build uses. Go records no test-only scope at module level, so modules only this repository's own tests import are included. 2 of them carry no licence file that matches a known SPDX licence; that is missing data, not a violation, and none of them is charged. ★ COVERAGE OF THIS VERDICT: it grades this repository's Go module dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
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 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with ipfilter.go. — 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.
Do you agree with this assessment?
D16 · Bus Factor9.1 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
5 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is REDACTED. Counted over 57 of the 167 production source files in this repository: 63 are under the ~2,400-byte size floor this dimension measures over, and the remaining 47 have no attributable history left to measure.
Off-boarding risk: anonymized user #1
✓ On the Gold path — maintain.
Detailed fixes: d16_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.
57 deducted task-comment markers across 28010 LoC (0.2/KLoC) → score 9.6. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
TodoComment · ×57casket_test.go:28
What to do
Resolve the 57 TodoComment finding(s) in Explicit Debt — start with REDACTED (4), mitm.go (4), server.go (4). — One of this dimension's main actionable groups (57 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
1 of 1 documentation facets pass in full. 77 document(s) read across 2 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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
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 15 declarations measured against a convention their peers follow.
`addIpRanges` spells `Ip` where 14 names in the project spell it `IP`caskethttp/realip/setup.go:68
What to do
Resolve the 1 `addIpRanges` spells `Ip` where 14 names in the project spell it `IP` finding(s) in Naming Consistency — start with REDACTED. — 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.
Do you agree with this assessment?
D22 · Internal API Consistency6.7 / 10Adequate✓ Tool-verified
What it measures: Whether the internal API surface is consistent and coherent.
Method: Call-shape rules (A1-A9) over the structured code model of the intentionally exposed C# surface: members of one type, overloads of one name and the same slot across sibling types are compared, and a member that makes a caller use a different convention for the same kind of operation is flagged. Deterministic, no model. Advisory.
1 API inconsistencies among 30 exposed members measured against a convention their peers follow.
`Context.Markdown` signals absence with `(T, error)` (an error when absent) where its 9 sibling single-key reads use a bare `T` (the zero value when absent)caskethttp/httpserver/tplcontext.go:276
What to do
Resolve the 1 `Context.Markdown` signals absence with `(T, error)` (an error when… finding(s) in Internal API Consistency — start with tplcontext.go. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d22_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.6 / 10Strong✓ Tool-verified
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.
47 % of calls cross a namespace and 10 % go through an interface, but 62 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret 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.
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).
53 finding(s): 0 critical, 21 high, 16 medium, 16 low. 16 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 2 file(s) — `caskethttp/browse/default_template.html` (line 435), `docs/src/.vitepress/theme/index.ts` (lines 7–15) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 9 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 16 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 (16 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 7 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (6). — One of this dimension's main actionable groups (6 issue-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 4 High IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Low IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-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.
70 of 104 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is casket.go. Counted over 104 of the 167 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 67 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (14), handler.go (2), plugin.go. — One of this dimension's main actionable groups (67 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with casket.go, mitm.go, REDACTED. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ 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.
AC2 · Forms & labels5.0 / 10Weak✓ 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 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. — caskethttp/browse/default_template.html:344
A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label. (×3) — caskethttp/browse/default_template.html:367, caskethttp/browse/default_template.html:369, caskethttp/browse/default_template.html:371
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.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — caskethttp/browse/default_template.html:2
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
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". — caskethttp/browse/default_template.html:347
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.
`.dropdown::before` moves (`transition: transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — caskethttp/browse/default_template.html:109
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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.
caskethttp/forwardproxy/README.md names Go 1.12 or later, but REDACTED:3 requires `go 1.25.0`: the code does not build on Go 1.12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — caskethttp/forwardproxy/README.md:145
What to do
Reconcile the README with reality: caskethttp/forwardproxy/README.md names Go 1.12 or later, but REDACTED:3 requires `go 1.25.0`: the code does not build on Go 1.12.
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.
`docs/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — docs/package.json:9
What to do
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 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.
`http.Get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — caskethttp/tmpauth/background.go:77
`http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — caskethttp/tmpauth/setup.go:63
What to do
Give every `http.Client` an explicit `Timeout` (never call `http.Get`/`http.Post` or `http.DefaultClient`, which have none), or build each request with `http.NewRequestWithContext` under a `context.WithTimeout`; add retry with back-off (`hashicorp/go-retryablehttp`) and a breaker (`sony/gobreaker`) around dependencies that fail.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
A Go testing.B suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured. — caskethttp/staticfiles/fileserver_test.go
What to do
Call b.ReportAllocs() in the benchmarks, or run them with `go test -bench . -benchmem`, so allocation regressions are visible, not just time.
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 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 a context.Context (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 2/6 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`updateMinimumIat` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — caskethttp/tmpauth/background.go:68
`socketDial` calls `net.DialTimeout(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:108
`srvDialerFunc` calls `net.DialTimeout(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:114
`healthCheck` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`. — REDACTED:622
What to do
Thread a context.Context through functions that make requests, so the work stops when its caller gives up.
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 enumerated7.7 / 10Strong✓ Tool-verified
Other · Code Health — 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.
`allConfigs` is walked by the `for … range` at line 153, and line 158 appends to `allConfigs`. A range evaluates its slice once and walks the length it had when the loop began, so the elements appended here are never visited by this loop — work queued for it is silently dropped. — caskethttp/httpserver/https.go:153
What to do
Each finding names the two lines that cannot both stand — the `for … range` over the collection, and the change to it in the body. Confirm from those two, then pick one: build the result instead of editing the walked collection (`var kept []T` … `kept = append(kept, v)`, or `kept := s[:0]` and assign `s = kept` after the loop; `slices.DeleteFunc(s, drop)` in one call); for a worklist that must visit what it adds, loop `for len(queue) > 0` or by index (`for i := 0; i < len(s); i++`); walk a copy (`range slices.Clone(s)`, `range slices.Collect(maps.Keys(m))`) and change the original; delete only the CURRENT key (`delete(m, k)`), which the specification allows; or — where only the first match was ever meant — `break` straight after the change.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard7.1 / 10Strong✓ Tool-verified
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.
`fields` holds what `Split` returns, and `fields[3]` takes element 3 of it without checking its length — while this file tests that same result elsewhere before indexing it, because it can be nil or shorter. Here a short result panics with `index out of range`. Test `len(fields)` (or nil) first, as the other call site does. — caskethttp/ipfilter/ipfilter.go:371
What to do
Each finding names the index access that escapes the guard and the line of the correctly bracketed access beside it. Compare the two: they differ only in where one parenthesis sits. Move it so the emptiness test brackets every access to that symbol — and if the value provably cannot be empty at this point, delete the test rather than leave a condition that guards one access and not its neighbour.
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.
`_, ipnet, _ := net.ParseCIDR(privateNetwork)` writes the call's error to `_` and then uses `ipnet` as if the call succeeded. When `net.ParseCIDR` fails, `ipnet` 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 `ipnet` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — casket.go:942
`if err != nil` 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. (×27) — plugins.go:143, caskettls/env/env.go:105, caskettls/env/env.go:138, …
`if err := json.Unmarshal(jsonData, &accounts); err != nil` 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. — dnsproviders/acmedns/acmedns.go:102
`if _, err := stdin.Write(message); err != nil` 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. — REDACTED:274
`if err := conn.WriteMessage(websocket.TextMessage, bytes.TrimSpace(s.Bytes())); err != nil` 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. — REDACTED:299
`if err := conn.WriteMessage(websocket.TextMessage, out[0:len-remainLen]); err != nil` 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. — REDACTED:335
`if err := conn.WriteMessage(websocket.BinaryMessage, out[0:len]); err != nil` 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. — REDACTED:363
`fs, _ := hFile.Stat()` writes the call's error to `_` and then uses `fs` as if the call succeeded. When `hFile.Stat` fails, `fs` 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 `fs` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line. — REDACTED:240
`if _, err := meta.Write(scanner.Bytes()); err != nil` 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. — caskethttp/markdown/metadata/metadata.go:136
`if _, err := meta.WriteRune(' '); err != nil` 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. — caskethttp/markdown/metadata/metadata.go:139
`if _, err := markdown.Write(scanner.Bytes()); err != nil` 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. — caskethttp/markdown/metadata/metadata.go:151
`if _, err := markdown.WriteRune(' '); err != nil` 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. — caskethttp/markdown/metadata/metadata.go:154
`if err := toml.Unmarshal(meta.Bytes(), &m); err != nil` 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. — caskethttp/markdown/metadata/metadata_toml.go:43
`if err := yaml.Unmarshal(meta.Bytes(), &m); err != nil` 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. — caskethttp/markdown/metadata/metadata_yaml.go:43
What to do
Discarded error (assigned to `_`, then its result used)
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 12 of 55 WCAG 2.2 Level A/AA success criteria (22%; ≈24% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 43 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 — 1 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X7 Silent fallback defaults — 2 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 — 56 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.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AX1 Captive dependencies — Not applicable: this repository's Go imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
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) — -------------------- 8 | RUN curl --fail https://getcasket.com | bash -s http.forwardproxy 9 | 10 | >>> COPY gen_casketfile_and_start.sh /bin/ 11 | 12 | VOLUME /root/.casket -------------------- ERROR: failed to solve: failed to compute cache key: failed to calculate checksum of ref a3edd54e-5fb1-4c8a-a857-accf610c15a2::v38jbwj1tblnudqak5ynyvjl4: "/gen_casketfile_and_start.sh": not found; likely cause (the repository): a file the REDACTED copies (`gen_casketfile_and_start.sh`) is not in the repository's build context (it may be produced by a build step outside the REDACTED, or excluded by .dockerignore); runtime evidence skipped The cause is in the repository, not in our sandbox: a file the REDACTED copies (`gen_casketfile_and_start.sh`) is not in the repository's build context (it may be produced by a build step outside the REDACTED, or excluded by .dockerignore). 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 — ~22169 lines of test source are present (.go) 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.
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.
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"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .go source were not judged.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 1 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.
D5 Coupling — Not applicable — this Go build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 1 aggregate root(s) (types guarding their own state behind command methods — this language has no AggregateRoot base to inherit); 1 value object(s)
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 event-sourced shape(s) (event folds / event-recording aggregates))
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 Go aggregate(s) recording domain events (own events-slice append / raise-record))
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 164 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.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: Go and PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
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.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X12 Unreachable branch — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — 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 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
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — 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
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Go was read, and it logs through none: the standard library's `log` takes one finished line, or it makes no log call outside its tests at all, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through log/slog, zap, logrus, zerolog, hclog, go-kit's log or logr would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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· Link with no accessible name · ×3
Link with no accessible name caskethttp/browse/default_template.html:367— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name caskethttp/browse/default_template.html:369— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
Link with no accessible name caskethttp/browse/default_template.html:371— A link with no text, aria-label or labelled child (e.g. an icon-only link) has no accessible name, so assistive tech can't say where it goes. Add visible text or an aria-label.
AC2 · Forms & labels· <input> without a programmatic label · ×1
<input> without a programmatic label caskethttp/browse/default_template.html:344— 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.
<html> without a lang caskethttp/browse/default_template.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×1
Click handler on a non-interactive <div> caskethttp/browse/default_template.html:347— 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".
TodoComment casket_test.go:28— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:221— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:222— // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment commands_test.go:128— // TODO - see how many quotes are displayed if we use "", """, """"""" — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment upgrade.go:47— // TODO: For more information when debugging, see: — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment upgrade.go:210— // at fd 4 (TODO: the reason for this is still unclear - to reproduce, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:73— // TODO: Check how relevant this is with TLS 1.3. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:350— // TODO: remove this once the standard library allows a tls.Config with — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskettls/crypto.go:31— // TODO: See about moving this into CertMagic and using its Storage — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskettls/setup.go:39— // TODO: remove this line when Go1.13 is released. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskettls/tls.go:80— // TODO: Bubble down certificate revocation reasons per RFC 5280. Is this function only ever called by human — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskethttp/caskethttp_test.go:24— // TODO: this test could be improved; the purpose is to — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskethttp/websocket/setup.go:127— // TODO: This isn't used currently — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:79— // TODO: Not used, but parser supports it until we decide on it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:18— // TODO: Should this package be rolled into the httpserver package? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:68— // TODO remove when stdlib http.Dir fixes this. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:238— // TODO: Could these FileInfos be stored instead of their paths, to avoid opening them all the time? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskethttp/rate-limit/setup.go:115— // TODO: check status code is valid — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskethttp/proxy/proxy_test.go:1721— // TODO. (#1782) This test requires configuring hosts
TodoComment caskethttp/proxy/proxy_test.go:1756— // TODO: Use a dynamically-generated, self-signed cert instead — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:666— // TODO ReadAll will be replaced if deemed necessary — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskethttp/markdown/summary/render.go:51— // TODO: This is not desired (we'd rather not write lists as part of summary), — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskethttp/httpserver/https.go:122— // TODO: SubjectQualifiesForPublicCert behavior may be slightly different in mainline certmagic — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskethttp/httpserver/https_test.go:202— // TODO: caskettls.TestQualifiesForManagedTLS and this test share nearly the same config list... — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment caskethttp/httpserver/middleware.go:79— // TODO The long term plan is to get all middleware implement this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Swallowed exception (caught, then discarded) plugins.go:143— `if err != nil` 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) dnsproviders/acmedns/acmedns.go:102— `if err := json.Unmarshal(jsonData, &accounts); err != nil` 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) caskettls/env/env.go:105— `if err != nil` 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) caskettls/env/env.go:138— `if err != nil` 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— `if _, err := stdin.Write(message); err != nil` 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:299— `if err := conn.WriteMessage(websocket.TextMessage, bytes.TrimSpace(s.Bytes())); err != nil` 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:335— `if err := conn.WriteMessage(websocket.TextMessage, out[0:len-remainLen]); err != nil` 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:363— `if err := conn.WriteMessage(websocket.BinaryMessage, out[0:len]); err != nil` 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:144— `if err != nil` 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:196— `if err != nil` 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) caskethttp/rewrite/to.go:91— `if err != nil` 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) caskethttp/rewrite/to.go:97— `if err != nil` 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) caskethttp/push/handler.go:97— `if err != nil` 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:155— `if err != nil` 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:643— `if err != nil` 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:651— `if err != nil` 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:669— `if err != nil` 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:789— `if err != nil` 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:795— `if err != nil` 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) caskethttp/prometheus/handler.go:20— `if err != nil` 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) caskethttp/markdown/markdown.go:154— `if err != nil` 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) caskethttp/markdown/metadata/metadata.go:136— `if _, err := meta.Write(scanner.Bytes()); err != nil` 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) caskethttp/markdown/metadata/metadata.go:139— `if _, err := meta.WriteRune(' '); err != nil` 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) caskethttp/markdown/metadata/metadata.go:151— `if _, err := markdown.Write(scanner.Bytes()); err != nil` 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) caskethttp/markdown/metadata/metadata.go:154— `if _, err := markdown.WriteRune(' '); err != nil` 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.
D12 · Dependency Hygiene· Dependency pinned to a stale untagged commit · ×6
Dependency pinned to a stale untagged commit: github.com/captncraig/cors — Direct dependency `github.com/captncraig/cors` is required at `v0.0.0-20190703115713-e80254a89df1` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2019-07-03, 7.4 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/captncraig/cors` and has not moved this requirement in 7.4 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/captncraig/cors` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/flynn/go-shlex — Direct dependency `github.com/flynn/go-shlex` is required at `v0.0.0-20150515145356-3f9db97f8568` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2015-05-15, 11.5 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/flynn/go-shlex` and has not moved this requirement in 11.5 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/flynn/go-shlex` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/inhies/go-bytesize — Direct dependency `github.com/inhies/go-bytesize` is required at `v0.0.0-20220417184213-4913239db9cf` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2022-04-17, 4.6 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/inhies/go-bytesize` and has not moved this requirement in 4.6 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/inhies/go-bytesize` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/jimstudt/http-authentication — Direct dependency `github.com/jimstudt/http-authentication` is required at `v0.0.0-20140401203705-3eca13d6893a` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2014-04-01, 12.6 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/jimstudt/http-authentication` and has not moved this requirement in 12.6 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/jimstudt/http-authentication` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/libdns/digitalocean — Direct dependency `github.com/libdns/digitalocean` is required at `v0.0.0-20230728223659-4f9064657aea` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2023-07-28, 3.3 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/libdns/digitalocean` and has not moved this requirement in 3.3 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/libdns/digitalocean` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Dependency pinned to a stale untagged commit: github.com/libdns/namecheap — Direct dependency `github.com/libdns/namecheap` is required at `v0.0.0-20211109042440-fc7440785c8e` in REDACTED — a pseudo-version, which pins an UNTAGGED commit from 2021-11-09, 5 years ago. The pin itself is exact, so this is not a reproducibility defect, and it is not a claim that the module is unmaintained. What it says is that this repository tracks no RELEASE of `github.com/libdns/namecheap` and has not moved this requirement in 5 years: every fix the module has published since that commit — including any security fix — is absent from this build, whether the module went quiet or moved on without you. Check whether `github.com/libdns/namecheap` now publishes tagged releases and move the requirement to one; if it publishes none, re-pin to a current commit.
Duplicated block (11 lines × 2) caskethttp/chuieauth/web.go:150— caskethttp/chuieauth/web.go:150-160 | caskethttp/chuieauth/web.go:248-258 — 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 `caskethttp/chuieauth/web.go:150` 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 (11 lines × 2) caskethttp/geoip/setup.go:164— caskethttp/geoip/setup.go:164-174 | caskethttp/ipfilter/ipfilter.go:152-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `caskethttp/geoip/setup.go:164` 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 (11 lines × 2) caskethttp/chuieauth/auth.go:228— caskethttp/chuieauth/auth.go:228-238 | caskethttp/chuieauth/auth.go:253-263 — 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 `caskethttp/chuieauth/auth.go:228` 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 × 2) dnsproviders/namedotcom/namedotcom.go:64— dnsproviders/namedotcom/namedotcom.go:64-74 | dnsproviders/rfc2136/rfc2136.go:65-75 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `dnsproviders/namedotcom/namedotcom.go:64` 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.
X2 · Cancellation propagation· Function without context.Context · ×4
Function without context.Context: updateMinimumIat caskethttp/tmpauth/background.go:68— `updateMinimumIat` calls `http.Get(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: socketDial REDACTED:108— `socketDial` calls `net.DialTimeout(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: srvDialerFunc REDACTED:114— `srvDialerFunc` calls `net.DialTimeout(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
Function without context.Context: healthCheck REDACTED:622— `healthCheck` calls `http.NewRequest(…)` but takes no context.Context and reaches none its caller controls, so its caller cannot cancel the request once it has started. Take `ctx context.Context` as the first parameter and build the request with it: `http.NewRequestWithContext(ctx, …)`, `(&net.Dialer{}).DialContext(ctx, …)`.
MethodTooLong: replacer.getSubstitution caskethttp/httpserver/replacer.go:260— MethodTooLong — getSubstitution runs 226 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× 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: HTTPConnectDialer.DialContext REDACTED:110— MethodTooLong — DialContext runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× 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: ForwardProxy.ServeHTTP caskethttp/forwardproxy/forwardproxy.go:291— MethodTooLong — ServeHTTP runs 101 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1 over it, 1.01× 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.
FunctionTooLong: forwardproxy.setup REDACTED:40— FunctionTooLong — setup 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.
FunctionTooLong: caskettls.setupTLS caskettls/setup.go:53— FunctionTooLong — setupTLS runs 203 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 103 over it, 2.03× 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.
FunctionTooLong: proxy.parseBlock REDACTED:337— FunctionTooLong — parseBlock runs 187 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 87 over it, 1.87× 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.
TooManyMethods: Context caskethttp/httpserver/tplcontext.go:45— 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.
TooManyMethods: renderer caskethttp/markdown/summary/render.go:30— 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.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) caskethttp/push/setup.go:44— caskethttp/push/setup.go:44-57 | caskethttp/rewrite/setup.go:33-50 — These two members are one piece of code written twice and then edited apart: 14 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 (14 corresponding lines) caskethttp/chuieauth/handler.go:74— caskethttp/chuieauth/handler.go:74-88 | caskethttp/status/setup.go:33-46 — These two members are one piece of code written twice and then edited apart: 14 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 (11 lines × 4) dnsproviders/cloudflare/cloudflare.go:45— dnsproviders/cloudflare/cloudflare.go:45-55 | dnsproviders/digitalocean/digitalocean.go:40-50 | dnsproviders/duckdns/duckdns.go:40-50 | dnsproviders/linode/linode.go:40-50 — `dnsproviders/digitalocean/digitalocean.go` and `dnsproviders/duckdns/duckdns.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 56 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (11 lines × 4) dnsproviders/dnspod/dnspod.go:35— dnsproviders/dnspod/dnspod.go:35-45 | dnsproviders/gandi/gandi.go:35-45 | dnsproviders/rfc2136/rfc2136.go:43-53 | dnsproviders/vultr/vultr.go:35-45 — `dnsproviders/dnspod/dnspod.go` and `dnsproviders/vultr/vultr.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 59 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `dnsproviders/dnspod/dnspod.go:35` 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.
Low cohesion: Context (LCOM4 10) caskethttp/httpserver/tplcontext.go:45— Context's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Logger (LCOM4 4) caskethttp/httpserver/logger.go:38— Logger's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Outbound HTTP without resilience caskethttp/tmpauth/background.go:77— `http.Get(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience caskethttp/tmpauth/setup.go:63— `http.Client{` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
X3 · Exception handling· Discarded error (assigned to `_`, then its result used) · ×2
Discarded error (assigned to `_`, then its result used) casket.go:942— `_, ipnet, _ := net.ParseCIDR(privateNetwork)` writes the call's error to `_` and then uses `ipnet` as if the call succeeded. When `net.ParseCIDR` fails, `ipnet` 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 `ipnet` (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:240— `fs, _ := hFile.Stat()` writes the call's error to `_` and then uses `fs` as if the call succeeded. When `hFile.Stat` fails, `fs` 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 `fs` (return it, wrapped with what was being done), or, if the failure genuinely cannot matter, say why in a comment on the line.
AC6 · Visual & motion safety· Animation without a prefers-reduced-motion guard · ×1
Animation without a prefers-reduced-motion guard caskethttp/browse/default_template.html:109— `.dropdown::before` moves (`transition: transform 0.2s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
replacer.getSubstitution (cyclomatic 95) caskethttp/httpserver/replacer.go:260— replacer.getSubstitution has cyclomatic complexity 95 (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.
proxy.parseBlock (cyclomatic 77) REDACTED:337— proxy.parseBlock has cyclomatic complexity 77 (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.
forwardproxy.setup (cyclomatic 76) REDACTED:40— forwardproxy.setup has cyclomatic complexity 76 (threshold 15). Of this number, 71 points are the body's own statements and 5 belong to 2 function literals inside it that branch. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
caskettls.setupTLS (cyclomatic 76) caskettls/setup.go:53— caskettls.setupTLS has cyclomatic complexity 76 (threshold 15). Of this number, 70 points are the body's own statements and 6 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.
ForwardProxy.ServeHTTP (cyclomatic 46) caskethttp/forwardproxy/forwardproxy.go:291— ForwardProxy.ServeHTTP has cyclomatic complexity 46 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
fastcgi.fastcgiParse (cyclomatic 35) caskethttp/fastcgi/setup.go:64— fastcgi.fastcgiParse has cyclomatic complexity 35 (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.
ipfilter.ipfilterParseSingle (cyclomatic 34) caskethttp/ipfilter/ipfilter.go:387— ipfilter.ipfilterParseSingle has cyclomatic complexity 34 (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.
casket.startServers (cyclomatic 31) casket.go:682— casket.startServers has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 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.
Handler.ServeHTTP (cyclomatic 30) caskethttp/fastcgi/fastcgi.go:58— Handler.ServeHTTP has cyclomatic complexity 30 (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.
Proxy.ServeHTTP (cyclomatic 30) caskethttp/proxy/proxy.go:123— Proxy.ServeHTTP has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 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.
FileServer.serveFile (cyclomatic 30) REDACTED:64— FileServer.serveFile has cyclomatic complexity 30 (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.
Tmpauth.ServeHTTP (cyclomatic 30) caskethttp/tmpauth/handler.go:71— Tmpauth.ServeHTTP has cyclomatic complexity 30 (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.
HTTPConnectDialer.DialContext (cyclomatic 28) REDACTED:110— HTTPConnectDialer.DialContext has cyclomatic complexity 28 (threshold 15). Of this number, 23 points are the body's own statements and 5 belong to 2 function literals inside it that branch. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
RateLimit.ServeHTTP (cyclomatic 28) caskethttp/rate-limit/ratelimit.go:44— RateLimit.ServeHTTP has cyclomatic complexity 28 (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.
basicauth.basicAuthParse (cyclomatic 26) caskethttp/basicauth/setup.go:54— basicauth.basicAuthParse has cyclomatic complexity 26 (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.
casket.parseRules (cyclomatic 26) caskethttp/cors/casket/corsPlugin.go:50— casket.parseRules has cyclomatic complexity 26 (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.
metrics.parse (cyclomatic 25) REDACTED:132— metrics.parse 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.
websocket.pumpStdout (cyclomatic 25) REDACTED:282— websocket.pumpStdout 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.
casketmain.Run (cyclomatic 24) casket/casketmain/run.go:77— casketmain.Run 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.
gzip.gzipParse (cyclomatic 24) caskethttp/gzip/setup.go:43— gzip.gzipParse 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.
httpContext.InspectServerBlocks (cyclomatic 24) caskethttp/httpserver/plugin.go:122— httpContext.InspectServerBlocks 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.
httpserver.parseRawClientHello (cyclomatic 23) caskethttp/httpserver/mitm.go:220— httpserver.parseRawClientHello has cyclomatic complexity 23 (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.
httpContext.MakeServers (cyclomatic 22) caskethttp/httpserver/plugin.go:226— httpContext.MakeServers 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.
proxy.NewStaticUpstreams (cyclomatic 22) REDACTED:109— proxy.NewStaticUpstreams 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.
redirect.redirParse (cyclomatic 22) caskethttp/redirect/setup.go:45— redirect.redirParse has cyclomatic complexity 22 (threshold 15). Of this number, 11 points are the body's own statements and 11 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.
timeouts.setupTimeouts (cyclomatic 22) caskethttp/timeouts/timeouts.go:31— timeouts.setupTimeouts 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.
caskettls.loadCertsInDir (cyclomatic 22) caskettls/setup.go:354— caskettls.loadCertsInDir has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to one function literal inside it that branches (line 355). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
casket.startWithListenerFds (cyclomatic 21) casket.go:487— casket.startWithListenerFds has cyclomatic complexity 21 (threshold 15). Of this number, 18 points are the body's own statements and 3 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.
browse.browseParse (cyclomatic 21) caskethttp/browse/setup.go:58— browse.browseParse has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 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.
tmpauth.parseConfig (cyclomatic 21) caskethttp/tmpauth/config.go:31— tmpauth.parseConfig has cyclomatic complexity 21 (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.
main.main (cyclomatic 21) REDACTED:22— main.main has cyclomatic complexity 21 (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.
webdav.parse (cyclomatic 21) caskethttp/webdav/webdav.go:63— webdav.parse has cyclomatic complexity 21 (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.
Instance.Restart (cyclomatic 20) casket.go:183— Instance.Restart has cyclomatic complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 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.
lexer.next (cyclomatic 20) casketfile/lexer.go:74— lexer.next 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.
BasicAuth.ServeHTTP (cyclomatic 20) REDACTED:67— BasicAuth.ServeHTTP 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.
caskettls.assertConfigsCompatible (cyclomatic 20) REDACTED:363— caskettls.assertConfigsCompatible 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.
casket.Upgrade (cyclomatic 19) upgrade.go:50— casket.Upgrade 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.
tlsHandler.ServeHTTP (cyclomatic 19) caskethttp/httpserver/mitm.go:53— tlsHandler.ServeHTTP 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.
Tmpauth.parseAuthJWT (cyclomatic 19) REDACTED:89— Tmpauth.parseAuthJWT 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.
httpserver.makeHTTPServerWithTimeouts (cyclomatic 18) caskethttp/httpserver/server.go:190— httpserver.makeHTTPServerWithTimeouts 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.
Markdown.ServeHTTP (cyclomatic 18) caskethttp/markdown/markdown.go:82— Markdown.ServeHTTP has cyclomatic complexity 18 (threshold 15). 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.
markdown.loadParams (cyclomatic 18) caskethttp/markdown/setup.go:103— markdown.loadParams 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.
parser.doImport (cyclomatic 17) casketfile/parse.go:231— parser.doImport has cyclomatic complexity 17 (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.
errors.errorsParse (cyclomatic 17) caskethttp/errors/setup.go:45— errors.errorsParse has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 57). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
log.logParse (cyclomatic 17) caskethttp/log/setup.go:45— log.logParse has cyclomatic complexity 17 (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.
staticUpstream.healthCheck (cyclomatic 17) REDACTED:622— staticUpstream.healthCheck has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 8 of the 17 points are its own statements and the rest belongs to one function literal inside it that branches (line 639). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
ratelimit.rateLimitParse (cyclomatic 17) caskethttp/rate-limit/setup.go:56— ratelimit.rateLimitParse has cyclomatic complexity 17 (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.
rewrite.rewriteParse (cyclomatic 17) caskethttp/rewrite/setup.go:52— rewrite.rewriteParse has cyclomatic complexity 17 (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.
configBlock.validate (cyclomatic 17) caskethttp/tmpauth/config.go:148— configBlock.validate has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal 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.
websocket.webSocketParse (cyclomatic 17) caskethttp/websocket/setup.go:48— websocket.webSocketParse has cyclomatic complexity 17 (threshold 15). Of this number, 9 points are the body's own statements and 8 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.
Config.buildStandardTLSConfig (cyclomatic 17) REDACTED:190— Config.buildStandardTLSConfig has cyclomatic complexity 17 (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.
httpserver.standardizeAddress (cyclomatic 16) caskethttp/httpserver/plugin.go:476— httpserver.standardizeAddress has cyclomatic complexity 16 (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.
httpserver.ParseRoller (cyclomatic 16) caskethttp/httpserver/roller.go:77— httpserver.ParseRoller has cyclomatic complexity 16 (threshold 15). 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.
push.parsePushRules (cyclomatic 16) caskethttp/push/setup.go:59— push.parsePushRules has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 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.
module.ServeHTTP (cyclomatic 16) caskethttp/realip/module.go:38— module.ServeHTTP 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.
ovh.NewDNSProvider (cyclomatic 16) dnsproviders/ovh/ovh.go:36— ovh.NewDNSProvider 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.
rfc2136.NewDNSProvider (cyclomatic 16) dnsproviders/rfc2136/rfc2136.go:35— rfc2136.NewDNSProvider 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.
Hotspot: caskethttp/ipfilter/ipfilter.go caskethttp/ipfilter/ipfilter.go:387— caskethttp/ipfilter/ipfilter.go changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in ipfilter.ipfilterParseSingle at line 387. 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-06-02..2026-08-31, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-02 16:47:51 +01:00' --until='2026-08-31 16:47:51 +01:00' --full-history --no-merges -- caskethttp/ipfilter/ipfilter.go`: 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.
forwardproxy.setup (cognitive 173) REDACTED:40— forwardproxy.setup has cognitive complexity 173 (threshold 15). Drivers by points: if/else 52 (150 pts), loops 5 (12 pts), match/switch 2 (6 pts), boolean chains 5 (nesting depth added 109). Of this number, 164 points are the body's own statements and 9 belong to 2 function literals inside it that branch. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
caskettls.setupTLS (cognitive 167) caskettls/setup.go:53— caskettls.setupTLS has cognitive complexity 167 (threshold 15). Drivers by points: if/else 41 (132 pts), loops 5 (15 pts), match/switch 5 (13 pts), boolean chains 7 (nesting depth added 109). Of this number, 151 points are the body's own statements and 16 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.
proxy.parseBlock (cognitive 117) REDACTED:337— proxy.parseBlock has cognitive complexity 117 (threshold 15). Drivers by points: if/else 52 (110 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 60). 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.
replacer.getSubstitution (cognitive 102) caskethttp/httpserver/replacer.go:260— replacer.getSubstitution has cognitive complexity 102 (threshold 15). Drivers by points: if/else 47 (95 pts), loops 2 (4 pts), boolean chains 2, match/switch 1 (nesting depth added 50). 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.
casket.startServers (cognitive 99) casket.go:682— casket.startServers has cognitive complexity 99 (threshold 15). Drivers by points: if/else 24 (93 pts), loops 3, match/switch 1 (2 pts), boolean chains 1 (nesting depth added 70). Of this number, 89 points are the body's own statements and 10 belong to one function literal inside it that branches. 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.
basicauth.basicAuthParse (cognitive 95) caskethttp/basicauth/setup.go:54— basicauth.basicAuthParse has cognitive complexity 95 (threshold 15). Drivers by points: if/else 17 (75 pts), match/switch 3 (11 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 71). 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.
ForwardProxy.ServeHTTP (cognitive 82) caskethttp/forwardproxy/forwardproxy.go:291— ForwardProxy.ServeHTTP has cognitive complexity 82 (threshold 15). Drivers by points: if/else 34 (70 pts), boolean chains 8, loops 1 (2 pts), match/switch 1 (2 pts) (nesting depth added 38). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
fastcgi.fastcgiParse (cognitive 79) caskethttp/fastcgi/setup.go:64— fastcgi.fastcgiParse has cognitive complexity 79 (threshold 15). Drivers by points: if/else 22 (72 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 53). 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.
casket.parseRules (cognitive 72) caskethttp/cors/casket/corsPlugin.go:50— casket.parseRules has cognitive complexity 72 (threshold 15). Drivers by points: if/else 20 (60 pts), loops 4 (9 pts), match/switch 1 (3 pts) (nesting depth added 47). 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.
RateLimit.ServeHTTP (cognitive 68) caskethttp/rate-limit/ratelimit.go:44— RateLimit.ServeHTTP has cognitive complexity 68 (threshold 15). Drivers by points: if/else 16 (48 pts), loops 7 (16 pts), boolean chains 4 (nesting depth added 41). 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.
Handler.ServeHTTP (cognitive 67) caskethttp/fastcgi/fastcgi.go:58— Handler.ServeHTTP has cognitive complexity 67 (threshold 15). Drivers by points: if/else 23 (60 pts), boolean chains 3, match/switch 1 (3 pts), loops 1 (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.
ipfilter.ipfilterParseSingle (cognitive 64) caskethttp/ipfilter/ipfilter.go:387— ipfilter.ipfilterParseSingle has cognitive complexity 64 (threshold 15). Drivers by points: if/else 20 (55 pts), loops 2 (4 pts), boolean chains 3, match/switch 1 (2 pts) (nesting depth added 38). 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.
gzip.gzipParse (cognitive 60) caskethttp/gzip/setup.go:43— gzip.gzipParse has cognitive complexity 60 (threshold 15). Drivers by points: if/else 14 (45 pts), loops 4 (11 pts), match/switch 1 (3 pts), boolean chains 1 (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.
metrics.parse (cognitive 60) REDACTED:132— metrics.parse has cognitive complexity 60 (threshold 15). Drivers by points: if/else 11 (44 pts), loops 4 (11 pts), match/switch 2 (5 pts) (nesting depth added 43). 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.
proxy.NewStaticUpstreams (cognitive 57) REDACTED:109— proxy.NewStaticUpstreams has cognitive complexity 57 (threshold 15). Drivers by points: if/else 14 (45 pts), loops 4 (7 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 36). 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.
Tmpauth.ServeHTTP (cognitive 57) caskethttp/tmpauth/handler.go:71— Tmpauth.ServeHTTP has cognitive complexity 57 (threshold 15). Drivers by points: if/else 23 (41 pts), loops 5 (14 pts), match/switch 1 (2 pts) (nesting depth added 28). 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.
websocket.pumpStdout (cognitive 57) REDACTED:282— websocket.pumpStdout has cognitive complexity 57 (threshold 15). Drivers by points: if/else 21 (51 pts), loops 3 (6 pts) (nesting depth added 33). 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.
browse.browseParse (cognitive 56) caskethttp/browse/setup.go:58— browse.browseParse has cognitive complexity 56 (threshold 15). Drivers by points: if/else 18 (45 pts), loops 4 (8 pts), match/switch 1 (3 pts) (nesting depth added 33). Of this number, 53 points are the body's own statements and 3 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.
Proxy.ServeHTTP (cognitive 56) caskethttp/proxy/proxy.go:123— Proxy.ServeHTTP has cognitive complexity 56 (threshold 15). Drivers by points: if/else 25 (51 pts), boolean chains 4, loops 1 (nesting depth added 26). Of this number, 54 points are the body's own statements and 2 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.
caskettls.loadCertsInDir (cognitive 56) caskettls/setup.go:354— caskettls.loadCertsInDir has cognitive complexity 56 (threshold 15). Drivers by points: if/else 19 (52 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 34). None of this is in the body itself: all 56 points belong to one function literal inside it that branches (line 355). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
webdav.parse (cognitive 54) caskethttp/webdav/webdav.go:63— webdav.parse has cognitive complexity 54 (threshold 15). Drivers by points: if/else 14 (45 pts), boolean chains 3, loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 34). 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.
httpContext.InspectServerBlocks (cognitive 52) caskethttp/httpserver/plugin.go:122— httpContext.InspectServerBlocks has cognitive complexity 52 (threshold 15). Drivers by points: if/else 13 (41 pts), boolean chains 7, loops 3 (4 pts) (nesting depth added 29). 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.
lexer.next (cognitive 49) casketfile/lexer.go:74— lexer.next has cognitive complexity 49 (threshold 15). Drivers by points: if/else 18 (48 pts), loops 1 (nesting depth added 30). 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.
FileServer.serveFile (cognitive 49) REDACTED:64— FileServer.serveFile has cognitive complexity 49 (threshold 15). Drivers by points: if/else 22 (36 pts), loops 5 (11 pts), boolean chains 2 (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.
timeouts.setupTimeouts (cognitive 47) caskethttp/timeouts/timeouts.go:31— timeouts.setupTimeouts has cognitive complexity 47 (threshold 15). Drivers by points: if/else 13 (40 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 30). 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.
log.logParse (cognitive 46) caskethttp/log/setup.go:45— log.logParse has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (37 pts), loops 3 (7 pts), match/switch 1 (2 pts) (nesting depth added 29). 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.
IPFilter.ShouldAllow (cognitive 45) caskethttp/ipfilter/ipfilter.go:177— IPFilter.ShouldAllow has cognitive complexity 45 (threshold 15). Drivers by points: if/else 11 (35 pts), loops 3 (9 pts), boolean chains 1 (nesting depth added 30). 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.
errors.errorsParse (cognitive 44) caskethttp/errors/setup.go:45— errors.errorsParse has cognitive complexity 44 (threshold 15). Drivers by points: if/else 15 (39 pts), match/switch 1 (3 pts), loops 2 (nesting depth added 26). Most of this is not in the body itself: 12 of the 44 points are its own statements and the rest belongs to one function literal inside it that branches (line 57). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
HTTPConnectDialer.DialContext (cognitive 44) REDACTED:110— HTTPConnectDialer.DialContext has cognitive complexity 44 (threshold 15). Drivers by points: if/else 20 (38 pts), loops 2 (3 pts), match/switch 2, boolean chains 1 (nesting depth added 19). Of this number, 39 points are the body's own statements and 5 belong to 2 function literals inside it that branch. This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
rewrite.rewriteParse (cognitive 44) caskethttp/rewrite/setup.go:52— rewrite.rewriteParse has cognitive complexity 44 (threshold 15). Drivers by points: if/else 9 (34 pts), match/switch 2 (6 pts), loops 2 (4 pts) (nesting depth added 31). 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.
ratelimit.rateLimitParse (cognitive 43) caskethttp/rate-limit/setup.go:56— ratelimit.rateLimitParse has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (30 pts), loops 3 (8 pts), match/switch 2 (5 pts) (nesting depth added 28). 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.
push.parsePushRules (cognitive 41) caskethttp/push/setup.go:59— push.parsePushRules has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (29 pts), loops 5 (9 pts), match/switch 1 (3 pts) (nesting depth added 25). Of this number, 20 points are the body's own statements and 21 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.
staticUpstream.healthCheck (cognitive 40) REDACTED:622— staticUpstream.healthCheck has cognitive complexity 40 (threshold 15). Drivers by points: if/else 13 (35 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 23). Most of this is not in the body itself: 15 of the 40 points are its own statements and the rest belongs to one function literal inside it that branches (line 639). The decisions are inside the literal, 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 literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
websocket.webSocketParse (cognitive 40) caskethttp/websocket/setup.go:48— websocket.webSocketParse has cognitive complexity 40 (threshold 15). Drivers by points: if/else 15 (36 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 22). Of this number, 18 points are the body's own statements and 22 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.
casket.startWithListenerFds (cognitive 39) casket.go:487— casket.startWithListenerFds has cognitive complexity 39 (threshold 15). Drivers by points: if/else 14 (28 pts), loops 5 (10 pts), boolean chains 1 (nesting depth added 19). Of this number, 33 points are the body's own statements and 6 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.
BasicAuth.ServeHTTP (cognitive 39) REDACTED:67— BasicAuth.ServeHTTP has cognitive complexity 39 (threshold 15). Drivers by points: if/else 12 (29 pts), loops 3 (6 pts), boolean chains 3, jumps 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.
redirect.redirParse (cognitive 38) caskethttp/redirect/setup.go:45— redirect.redirParse has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (31 pts), loops 3 (5 pts), boolean chains 1, match/switch 1 (nesting depth added 18). Of this number, 25 points are the body's own statements and 13 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.
casket.executeDirectives (cognitive 37) casket.go:615— casket.executeDirectives has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (27 pts), loops 4 (10 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.
main.main (cognitive 37) REDACTED:22— main.main has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (31 pts), match/switch 2 (4 pts), loops 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.
status.statusParse (cognitive 35) caskethttp/status/setup.go:49— status.statusParse has cognitive complexity 35 (threshold 15). Drivers by points: if/else 6 (22 pts), loops 4 (11 pts), match/switch 1 (2 pts) (nesting depth added 24). 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.
httpserver.parseRawClientHello (cognitive 34) caskethttp/httpserver/mitm.go:220— httpserver.parseRawClientHello has cognitive complexity 34 (threshold 15). Drivers by points: if/else 14 (24 pts), loops 3 (5 pts), boolean chains 3, match/switch 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.
Instance.Restart (cognitive 33) casket.go:183— Instance.Restart has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (26 pts), loops 4 (5 pts), boolean chains 2 (nesting depth added 14). Of this number, 22 points are the body's own statements and 11 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.
tmpauth.parseConfig (cognitive 33) caskethttp/tmpauth/config.go:31— tmpauth.parseConfig has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (26 pts), loops 2 (3 pts), match/switch 1 (3 pts), boolean chains 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.
casketmain.Run (cognitive 32) casket/casketmain/run.go:77— casketmain.Run has cognitive complexity 32 (threshold 15). Drivers by points: if/else 20 (28 pts), loops 1 (2 pts), boolean chains 1, match/switch 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.
casket.Upgrade (cognitive 31) upgrade.go:50— casket.Upgrade has cognitive complexity 31 (threshold 15). Drivers by points: if/else 16 (27 pts), loops 3 (4 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.
header.headersParse (cognitive 31) caskethttp/header/setup.go:45— header.headersParse has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (23 pts), loops 4 (8 pts) (nesting depth added 17). 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.
templates.templatesParse (cognitive 30) caskethttp/templates/setup.go:61— templates.templatesParse has cognitive complexity 30 (threshold 15). Drivers by points: if/else 4 (18 pts), loops 3 (6 pts), match/switch 2 (6 pts) (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.
route53.NewDNSProvider (cognitive 30) dnsproviders/route53/route53.go:34— route53.NewDNSProvider has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (24 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 21). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
parser.doImport (cognitive 28) casketfile/parse.go:231— parser.doImport has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 10). 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.
httpContext.MakeServers (cognitive 28) caskethttp/httpserver/plugin.go:226— httpContext.MakeServers has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 6, loops 2 (nesting depth added 10). 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.
module.ServeHTTP (cognitive 28) caskethttp/realip/module.go:38— module.ServeHTTP has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (4 pts), boolean chains 3 (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.
acmedns.NewDNSProvider (cognitive 28) dnsproviders/acmedns/acmedns.go:44— acmedns.NewDNSProvider has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (22 pts), match/switch 2 (4 pts), loops 1 (2 pts) (nesting depth added 19). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
Logger.ServeHTTP (cognitive 27) caskethttp/log/log.go:41— Logger.ServeHTTP has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (23 pts), loops 2 (4 pts) (nesting depth added 18). 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.
parser.addresses (cognitive 26) casketfile/parse.go:120— parser.addresses has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 3, loops 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.
Config.buildStandardTLSConfig (cognitive 26) REDACTED:190— Config.buildStandardTLSConfig has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (20 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 10). 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.
caskettls.MakeTLSConfig (cognitive 26) REDACTED:283— caskettls.MakeTLSConfig has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (22 pts), boolean chains 3, loops 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.
Config.HandleRequest (cognitive 25) caskethttp/cors/cors.go:48— Config.HandleRequest has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (23 pts), boolean chains 1, 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.
limits.parseLimits (cognitive 25) caskethttp/limits/setup.go:57— limits.parseLimits has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), match/switch 2 (4 pts), loops 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.
markdown.loadParams (cognitive 25) caskethttp/markdown/setup.go:103— markdown.loadParams has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (4 pts), match/switch 2 (3 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
rfc2136.NewDNSProvider (cognitive 25) dnsproviders/rfc2136/rfc2136.go:35— rfc2136.NewDNSProvider has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 2 (4 pts), loops 1 (2 pts), 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.
mime.mimeParse (cognitive 24) caskethttp/mime/setup.go:46— mime.mimeParse has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (18 pts), loops 2 (4 pts), match/switch 1 (2 pts) (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.
godaddy.NewDNSProvider (cognitive 24) dnsproviders/godaddy/godaddy.go:33— godaddy.NewDNSProvider has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (16 pts), match/switch 2 (4 pts), boolean chains 2, loops 1 (2 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.
ovh.NewDNSProvider (cognitive 24) dnsproviders/ovh/ovh.go:36— ovh.NewDNSProvider has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (17 pts), match/switch 2 (4 pts), loops 1 (2 pts), 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.
proxy.createUpstreamRequest (cognitive 23) caskethttp/proxy/proxy.go:312— proxy.createUpstreamRequest has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 11). Of this number, 21 points are the body's own statements and 2 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.
Templates.ServeHTTP (cognitive 23) caskethttp/templates/templates.go:35— Templates.ServeHTTP has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (18 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 11). Of this number, 12 points are the body's own statements and 11 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.
caskettls.NewConfig (cognitive 23) REDACTED:119— caskettls.NewConfig has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (5 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 13). Most of this is not in the body itself: 4 of the 23 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 128, 148). 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.
DBReloader.watch (cognitive 22) caskethttp/geoip/reloader.go:130— DBReloader.watch has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 1 (2 pts), boolean chains 1, loops 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.
Headers.ServeHTTP (cognitive 22) caskethttp/header/header.go:36— Headers.ServeHTTP has cognitive complexity 22 (threshold 15). Drivers by points: loops 4 (14 pts), if/else 4 (8 pts) (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
replacer.Replace (cognitive 22) caskethttp/httpserver/replacer.go:158— replacer.Replace has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (5 pts), boolean chains 2, jumps 2 (nesting depth added 10). 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.
PrefixFileReloader.watch (cognitive 22) caskethttp/ipfilter/prefix_file.go:117— PrefixFileReloader.watch has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 1 (2 pts), boolean chains 1, loops 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.
proxy.mutateHeadersByRules (cognitive 22) caskethttp/proxy/proxy.go:387— proxy.mutateHeadersByRules has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 4 (7 pts), boolean chains 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.
caskettls.assertConfigsCompatible (cognitive 22) REDACTED:363— caskettls.assertConfigsCompatible has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 4, loops 3 (nesting depth added 3). 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.
browse.directoryListing (cognitive 21) REDACTED:286— browse.directoryListing has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (3 pts), boolean chains 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.
httpserver.makeHTTPServerWithTimeouts (cognitive 21) caskethttp/httpserver/server.go:190— httpserver.makeHTTPServerWithTimeouts has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 8, loops 1 (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.
tlsHandler.ServeHTTP (cognitive 21) caskethttp/httpserver/mitm.go:53— tlsHandler.ServeHTTP has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 5 (nesting depth added 3). 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.
configBlock.validate (cognitive 21) caskethttp/tmpauth/config.go:148— configBlock.validate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 4 (nesting depth added 4). 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, 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.
cloudflare.NewDNSProvider (cognitive 21) dnsproviders/cloudflare/cloudflare.go:29— cloudflare.NewDNSProvider has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (11 pts), match/switch 3 (7 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.
namecheap.NewDNSProvider (cognitive 21) dnsproviders/namecheap/namecheap.go:35— namecheap.NewDNSProvider has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 2 (4 pts), loops 1 (2 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.
namedotcom.NewDNSProvider (cognitive 21) dnsproviders/namedotcom/namedotcom.go:36— namedotcom.NewDNSProvider has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), match/switch 2 (4 pts), loops 1 (2 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.
caskettls.standaloneTLSTicketKeyRotation (cognitive 20) caskettls/crypto.go:55— caskettls.standaloneTLSTicketKeyRotation has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (4 pts), match/switch 1 (2 pts) (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.
pdns.NewDNSProvider (cognitive 20) dnsproviders/pdns/pdns.go:35— pdns.NewDNSProvider has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (13 pts), match/switch 2 (4 pts), loops 1 (2 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.
Browse.ServeListing (cognitive 19) REDACTED:515— Browse.ServeListing has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), match/switch 2 (3 pts), boolean chains 2, 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.
httpserver.activateHTTPS (cognitive 19) caskethttp/httpserver/https.go:29— httpserver.activateHTTPS has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 3, 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.
Middleware.ServeHTTP (cognitive 19) caskethttp/push/handler.go:24— Middleware.ServeHTTP has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (4 pts), jumps 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.
websocket.findIncompleteRuneLength (cognitive 19) REDACTED:435— websocket.findIncompleteRuneLength has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (18 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.
azure.NewDNSProvider (cognitive 19) dnsproviders/azure/azure.go:21— azure.NewDNSProvider has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 pts), loops 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.
casketfile.jsonToText (cognitive 18) casketfile/json.go:135— casketfile.jsonToText has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (8 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
chuieauth.parseRules (cognitive 18) caskethttp/chuieauth/handler.go:90— chuieauth.parseRules has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (6 pts), match/switch 1 (3 pts), boolean chains 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.
forwardproxy.flushingIoCopy (cognitive 18) caskethttp/forwardproxy/forwardproxy.go:499— forwardproxy.flushingIoCopy has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 1 (nesting depth added 10). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
Gzip.ServeHTTP (cognitive 18) caskethttp/gzip/gzip.go:55— Gzip.ServeHTTP has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (3 pts), jumps 1 (nesting depth added 8). Of this number, 16 points are the body's own statements and 2 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.
httpserver.standardizeAddress (cognitive 18) caskethttp/httpserver/plugin.go:476— httpserver.standardizeAddress has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4 (nesting depth added 3). 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.
casket.parseWindowsCommand (cognitive 17) commands.go:75— casket.parseWindowsCommand has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, loops 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.
httpserver.NewServer (cognitive 17) caskethttp/httpserver/server.go:83— httpserver.NewServer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 6). Of this number, 11 points are the body's own statements and 6 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.
rawHelloInfo.looksLikeEdge (cognitive 17) caskethttp/httpserver/mitm.go:504— rawHelloInfo.looksLikeEdge has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 2, loops 2 (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.
Markdown.ServeHTTP (cognitive 17) caskethttp/markdown/markdown.go:82— Markdown.ServeHTTP has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 3 (4 pts), loops 2 (3 pts) (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.
parser.directive (cognitive 16) casketfile/parse.go:343— parser.directive has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 4, loops 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.
httpserver.RegisterDevDirective (cognitive 16) caskethttp/httpserver/plugin.go:553— httpserver.RegisterDevDirective has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 2 (3 pts) (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.
push.parseLinkHeader (cognitive 16) caskethttp/push/link_parser.go:38— push.parseLinkHeader has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 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.
Tmpauth.parseAuthJWT (cognitive 16) REDACTED:89— Tmpauth.parseAuthJWT has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13, match/switch 2, loops 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.
configGroup.getConfig (cognitive 16) caskettls/handshake.go:40— configGroup.getConfig has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, loops 2 (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.
googlecloud.NewDNSProvider (cognitive 16) dnsproviders/googlecloud/googlecloud.go:33— googlecloud.NewDNSProvider has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 2 (4 pts), 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.
transip.NewDNSProvider (cognitive 16) dnsproviders/transip/transip.go:32— transip.NewDNSProvider has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (10 pts), match/switch 2 (4 pts), 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.
D22 · Internal API Consistency· `Context.Markdown` signals absence with `(T, error)` (an error when absent) where its 9 sibling single-key reads use a bare `T` (the zero value when absent) · ×1
`Context.Markdown` signals absence with `(T, error)` (an error when absent) where its 9 sibling single-key reads use a bare `T` (the zero value when absent) caskethttp/httpserver/tplcontext.go:276— 9 of 10 single-key reads of `Context` return a bare `T` (the zero value when absent) (9 of 10). Siblings: Context.Now (caskethttp/httpserver/tplcontext.go:73); Context.Cookie (caskethttp/httpserver/tplcontext.go:84); Context.Header (caskethttp/httpserver/tplcontext.go:95); Context.StripHTML (caskethttp/httpserver/tplcontext.go:218); Context.Ext (caskethttp/httpserver/tplcontext.go:252). Return a bare `T` (the zero value when absent) like its siblings. [rule A5]
FileTooLong: REDACTED REDACTED— FileTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 20 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
D4 · Code Duplication· Edited copy of a member (53 corresponding lines) · ×1
Edited copy of a member (53 corresponding lines) dnsproviders/namedotcom/namedotcom.go:36— dnsproviders/namedotcom/namedotcom.go:36-88 | dnsproviders/rfc2136/rfc2136.go:35-92 — These two members are one piece of code written twice and then edited apart: 53 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 (61 corresponding lines) · ×1
Edited copy of a member (61 corresponding lines) caskethttp/httpserver/mitm.go:377— caskethttp/httpserver/mitm.go:377-442 | caskethttp/httpserver/mitm.go:608-668 — These two members are one piece of code written twice and then edited apart: 61 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 (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) caskethttp/geoip/setup.go:61— caskethttp/geoip/setup.go:61-110 | caskethttp/ipfilter/ipfilter.go:92-149 — These two members are one piece of code written twice and then edited apart: 50 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 (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) caskethttp/geoip/reloader.go:130— caskethttp/geoip/reloader.go:130-177 | caskethttp/ipfilter/prefix_file.go:117-162 — These two members are one piece of code written twice and then edited apart: 46 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 (5 members, 33+ corresponding lines) · ×1
Edited copies of one member (5 members, 33+ corresponding lines) dnsproviders/digitalocean/digitalocean.go:30— dnsproviders/digitalocean/digitalocean.go:30-62 | dnsproviders/dnspod/dnspod.go:30-62 | dnsproviders/duckdns/duckdns.go:30-62 | dnsproviders/linode/linode.go:30-62 | dnsproviders/vultr/vultr.go:30-62 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 33 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) caskethttp/geoip/reloader.go:46— caskethttp/geoip/reloader.go:46-89 | caskethttp/ipfilter/prefix_file.go:37-77 — These two members are one piece of code written twice and then edited apart: 41 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 (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) caskethttp/geoip/setup.go:163— caskethttp/geoip/setup.go:163-191 | caskethttp/ipfilter/ipfilter.go:151-174 — These two members are one piece of code written twice and then edited apart: 24 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 (20 corresponding lines) · ×1
Edited copy of a member (20 corresponding lines) caskethttp/chuieauth/auth.go:226— caskethttp/chuieauth/auth.go:226-249 | caskethttp/chuieauth/auth.go:251-270 — These two members are one piece of code written twice and then edited apart: 20 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) caskethttp/markdown/setup.go:34— caskethttp/markdown/setup.go:34-54 | caskethttp/templates/setup.go:34-59 — These two members are one piece of code written twice and then edited apart: 21 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 (15 corresponding lines) · ×1
Edited copy of a member (15 corresponding lines) caskethttp/markdown/metadata/metadata_toml.go:35— caskethttp/markdown/metadata/metadata_toml.go:35-49 | caskethttp/markdown/metadata/metadata_yaml.go:35-49 — 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 (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) casketfile/dispenser.go:87— casketfile/dispenser.go:87-102 | casketfile/dispenser.go:108-123 — These two members are one piece of code written twice and then edited apart: 16 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) caskethttp/rewrite/rewrite.go:97— caskethttp/rewrite/rewrite.go:97-107 | caskethttp/rewrite/rewrite.go:194-215 — 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 (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) caskethttp/geoip/reloader.go:109— caskethttp/geoip/reloader.go:109-128 | caskethttp/ipfilter/prefix_file.go:83-99 — These two members are one piece of code written twice and then edited apart: 17 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, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) caskethttp/browse/setup.go:39— caskethttp/browse/setup.go:39-56 | caskethttp/expvar/setup.go:34-51 | caskethttp/tryfiles/tryfiles.go:49-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 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 (6 members, 11+ corresponding lines) · ×1
Edited copies of one member (6 members, 11+ corresponding lines) caskethttp/extensions/setup.go:30— caskethttp/extensions/setup.go:30-48 | caskethttp/gzip/setup.go:30-41 | caskethttp/header/setup.go:32-43 | caskethttp/limits/setup.go:45-55 | caskethttp/mime/setup.go:33-44 | caskethttp/redirect/setup.go:32-43 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) caskethttp/cors/casket/corsPlugin.go:145— caskethttp/cors/casket/corsPlugin.go:145-151 | caskethttp/realip/setup.go:99-105 — 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.
Duplicated block (29 lines × 2) caskethttp/httpserver/mitm.go:414— caskethttp/httpserver/mitm.go:414-442 | caskethttp/httpserver/mitm.go:640-668 — 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 `caskethttp/httpserver/mitm.go:414` 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. 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 (22–24 lines × 2) caskethttp/geoip/reloader.go:150— caskethttp/geoip/reloader.go:150-173 | caskethttp/ipfilter/prefix_file.go:137-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `caskethttp/geoip/reloader.go:150` 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 (22 lines × 2) dnsproviders/dnspod/dnspod.go:32— dnsproviders/dnspod/dnspod.go:32-53 | dnsproviders/vultr/vultr.go:32-53 — `dnsproviders/dnspod/dnspod.go` and `dnsproviders/vultr/vultr.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 59 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `dnsproviders/dnspod/dnspod.go:32` 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 (19 lines × 3) dnsproviders/digitalocean/digitalocean.go:35— dnsproviders/digitalocean/digitalocean.go:35-53 | dnsproviders/duckdns/duckdns.go:35-53 | dnsproviders/linode/linode.go:35-53 — `dnsproviders/digitalocean/digitalocean.go` and `dnsproviders/duckdns/duckdns.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 56 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `dnsproviders/digitalocean/digitalocean.go:35` 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 (18 lines × 2) caskethttp/geoip/reloader.go:131— caskethttp/geoip/reloader.go:131-148 | caskethttp/ipfilter/prefix_file.go:118-135 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `caskethttp/geoip/reloader.go:131` 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 (15 lines × 5) dnsproviders/digitalocean/digitalocean.go:43— dnsproviders/digitalocean/digitalocean.go:43-57 | dnsproviders/dnspod/dnspod.go:43-57 | dnsproviders/duckdns/duckdns.go:43-57 | dnsproviders/linode/linode.go:43-57 | dnsproviders/vultr/vultr.go:43-57 — `dnsproviders/digitalocean/digitalocean.go` and `dnsproviders/duckdns/duckdns.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 56 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `dnsproviders/digitalocean/digitalocean.go:43` 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) dnsproviders/namecheap/namecheap.go:42— dnsproviders/namecheap/namecheap.go:42-53 | dnsproviders/namedotcom/namedotcom.go:47-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `dnsproviders/namecheap/namecheap.go:42` 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 (9–10 lines × 2) REDACTED:336— REDACTED:336-344 | REDACTED:364-373 — 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 `REDACTED:336` 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 (9 lines × 2) caskethttp/rate-limit/setup.go:66— caskethttp/rate-limit/setup.go:66-74 | caskethttp/rate-limit/setup.go:79-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 14) dnsproviders/digitalocean/digitalocean.go:35— dnsproviders/digitalocean/digitalocean.go:35-45 | dnsproviders/dnspod/dnspod.go:35-45 | dnsproviders/duckdns/duckdns.go:35-45 | dnsproviders/gandi/gandi.go:35-45 | dnsproviders/googlecloud/googlecloud.go:39-49 | dnsproviders/linode/linode.go:35-45 | dnsproviders/namecheap/namecheap.go:42-52 | dnsproviders/namedotcom/namedotcom.go:47-57 | dnsproviders/ovh/ovh.go:44-54 | dnsproviders/pdns/pdns.go:42-52 | dnsproviders/rfc2136/rfc2136.go:43-53 | dnsproviders/route53/route53.go:43-53 | dnsproviders/transip/transip.go:38-48 | dnsproviders/vultr/vultr.go:35-45 — `dnsproviders/digitalocean/digitalocean.go` and `dnsproviders/duckdns/duckdns.go` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 56 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `dnsproviders/digitalocean/digitalocean.go:35` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `dnsproviders/googlecloud/googlecloud.go:35` calls `GetOrDefaultString` and `dnsproviders/digitalocean/digitalocean.go:31` 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 (7 lines × 2) REDACTED:141— REDACTED:141-147 | REDACTED:152-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:141` 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.
X27 · Collection changed while being enumerated· Collection is structurally changed while it is being enumerated · ×1
Collection is structurally changed while it is being enumerated caskethttp/httpserver/https.go:153— `allConfigs` is walked by the `for … range` at line 153, and line 158 appends to `allConfigs`. A range evaluates its slice once and walks the length it had when the loop began, so the elements appended here are never visited by this loop — work queued for it is silently dropped.
X28 · Index access outside its own emptiness guard· Index access outside its own emptiness guard · ×1
Index access outside its own emptiness guard caskethttp/ipfilter/ipfilter.go:371— `fields` holds what `Split` returns, and `fields[3]` takes element 3 of it without checking its length — while this file tests that same result elsewhere before indexing it, because it can be nil or shorter. Here a short result panics with `index out of range`. Test `len(fields)` (or nil) first, as the other call site does.
Orphaned file caskethttp/httpserver/plugin.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/httpserver/server.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/fastcgi/fastcgi.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/httpserver/replacer.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskettls/setup.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file plugins.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file casket/casketmain/run.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file casketfile/parse.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/proxy/proxy.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/httpserver/tplcontext.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file casketfile/dispenser.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/httpserver/recorder.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/httpserver/https.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/httpserver/middleware.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file upgrade.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/rewrite/rewrite.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskettls/handshake.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/markdown/summary/render.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/limits/setup.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file caskethttp/httpserver/vhosttrie.go:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
D8 · Code Coverage· Tests reach code only in some runs · ×6
Tests reach code only in some runs: casket.go casket.go:818— 1 line(s) (818) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: caskethttp/geoip/reloader.go caskethttp/geoip/reloader.go:171— 3 line(s) (171-173) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: caskethttp/httpserver/mitm.go caskethttp/httpserver/mitm.go:222— 4 line(s) (222-223, 237-238) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: REDACTED REDACTED:74— 4 line(s) (74-77) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: caskettls/crypto.go caskettls/crypto.go:78— 3 line(s) (78-80) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
Tests reach code only in some runs: sigtrap_posix.go sigtrap_posix.go:30— 4 line(s) (30-33) were executed in some of the 3 runs of the suite and not in others. A test that does not take the same path every run only tests the part it always takes, so these lines are not counted as covered. Make the tests that reach them deterministic (a fixed clock, seed or ordering, or waiting on the event instead of on time), or test the paths directly.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file casket.go:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file caskethttp/httpserver/mitm.go:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file REDACTED:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Silent fallback default on error caskethttp/httpserver/mitm.go:144— `getVersion` turns a non-nil `err` into `return -1` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. 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 `if` or in the doc comment, and the row stops firing.
Silent fallback default on error caskethttp/httpserver/tplcontext.go:140— `ServerIP` turns a non-nil `err` into `return ""` — a failure becomes a plausible value and a silent behavior change with no trail. Log the error or return it. 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 `if` or in the doc comment, and the row stops firing.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 5 significant file(s) lose their only recent owner: REDACTED, caskethttp/ipfilter/ipfilter.go, REDACTED, caskethttp/basicauth/setup.go, caskethttp/ipfilter/prefix_file.go. Pair on, review, or document these before any departure.
No ADRs found REDACTED:1— 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 `REDACTED` makes this repository a deployable product (line 1).
D21 · Naming Consistency· `addIpRanges` spells `Ip` where 14 names in the project spell it `IP` · ×1
`addIpRanges` spells `Ip` where 14 names in the project spell it `IP` caskethttp/realip/setup.go:68— 14 of 15 names in project github.com/tmpim/casket spell the token `IP` (14 of 15; unit: names in project github.com/tmpim/casket containing `IP`). Peers: github.com/tmpim/casket/caskethttp/forwardproxy.aclIPRule (caskethttp/forwardproxy/acl.go:21); ForwardProxy.hideIP (caskethttp/forwardproxy/forwardproxy.go:46); github.com/tmpim/casket/caskethttp/geoip.GeoIP (caskethttp/geoip/setup.go:27); github.com/tmpim/casket/caskethttp/geoip.GeoIPRecord (caskethttp/geoip/setup.go:33); geoip.getClientIP (caskethttp/geoip/setup.go:163). Rename to `addIPRanges`. [rule N6]
Concentrated knowledge decay — 70 of 104 significant files have no living knowledge, while the repository is still being changed at a low rate (11 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 70 separate risks. Counted over 104 of the 167 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
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.
README/code drift caskethttp/forwardproxy/README.md:145— caskethttp/forwardproxy/README.md names Go 1.12 or later, but REDACTED:3 requires `go 1.25.0`: the code does not build on Go 1.12. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
No dependency-update automation docs/package.json:9— `docs/package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
Benchmarks don't track allocations caskethttp/staticfiles/fileserver_test.go— A Go testing.B suite exists but nothing turns on its allocation measurement — allocations (the main way hot code pressures a garbage collector or allocator) aren't being measured.
X2 · Cancellation propagation· Not all functions that make a request accept a context.Context · ×1
Not all functions that make a request accept a context.Context — Only 2/6 functions that make a cancellable request (net/http, net.Dial) accept a context.Context or pass one on, so a request keeps running after whatever wanted it has given up — a cancelled request, a shutdown, an expired deadline. Take `ctx context.Context` as the first parameter and build the request with it (`http.NewRequestWithContext`, `DialContext`); where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Outdated: github.com/caddyserver/certmagic — `github.com/caddyserver/certmagic` is required at v0.20.0 in REDACTED, but v0.25.6 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/caddyserver/certmagic@v0.25.6 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/djherbis/buffer — `github.com/djherbis/buffer` is required at v1.2.0 in REDACTED, but v1.2.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/djherbis/buffer@v1.2.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/dustin/go-humanize — `github.com/dustin/go-humanize` is required at v1.0.1 in REDACTED, but v1.1.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/dustin/go-humanize@v1.1.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/fsnotify/fsnotify — `github.com/fsnotify/fsnotify` is required at v1.9.0 in REDACTED, but v1.10.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/fsnotify/fsnotify@v1.10.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/gorilla/sessions — `github.com/gorilla/sessions` is required at v1.2.2 in REDACTED, but v1.4.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/gorilla/sessions@v1.4.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/gorilla/websocket — `github.com/gorilla/websocket` is required at v1.5.1 in REDACTED, but v1.5.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/gorilla/websocket@v1.5.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/hashicorp/go-syslog — `github.com/hashicorp/go-syslog` is required at v1.0.0 in REDACTED, but v1.0.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/hashicorp/go-syslog@v1.0.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/acmedns — `github.com/libdns/acmedns` is required at v0.2.0 in REDACTED, but v0.5.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/acmedns@v0.5.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/azure — `github.com/libdns/azure` is required at v0.4.0 in REDACTED, but v0.5.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/azure@v0.5.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/cloudflare — `github.com/libdns/cloudflare` is required at v0.1.1 in REDACTED, but v0.2.2 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/cloudflare@v0.2.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/duckdns — `github.com/libdns/duckdns` is required at v0.2.0 in REDACTED, but v0.3.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/duckdns@v0.3.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/gandi — `github.com/libdns/gandi` is required at v1.0.3 in REDACTED, but v1.2.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/gandi@v1.2.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/godaddy — `github.com/libdns/godaddy` is required at v1.0.3 in REDACTED, but v1.1.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/godaddy@v1.1.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/googleclouddns — `github.com/libdns/googleclouddns` is required at v1.1.0 in REDACTED, but v1.2.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/googleclouddns@v1.2.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/linode — `github.com/libdns/linode` is required at v0.4.1 in REDACTED, but v0.5.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/linode@v0.5.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/namecheap — `github.com/libdns/namecheap` is required at v0.0.0-20211109042440-fc7440785c8e in REDACTED, but v1.0.0 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/libdns/namecheap@v1.0.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/namedotcom — `github.com/libdns/namedotcom` is required at v0.3.3 in REDACTED, but v0.9.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/namedotcom@v0.9.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/ovh — `github.com/libdns/ovh` is required at v0.0.2 in REDACTED, but v1.1.0 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/libdns/ovh@v1.1.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/powerdns — `github.com/libdns/powerdns` is required at v0.1.2 in REDACTED, but v0.1.4 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/powerdns@v0.1.4 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/rfc2136 — `github.com/libdns/rfc2136` is required at v0.1.0 in REDACTED, but v1.0.1 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/libdns/rfc2136@v1.0.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/route53 — `github.com/libdns/route53` is required at v1.3.3 in REDACTED, but v1.6.3 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/libdns/route53@v1.6.3 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/libdns/transip — `github.com/libdns/transip` is required at v0.0.0-20240123173758-1e040d7f9881 in REDACTED, but v1.1.2 is the module's current release — so this build is missing every fix published since, including any security fix. This crosses a major version — v0 releases carry no compatibility promise, so read the changelog before taking it. Run `go get github.com/libdns/transip@v1.1.2 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/oschwald/maxminddb-golang — `github.com/oschwald/maxminddb-golang` is required at v1.12.0 in REDACTED, but v1.13.1 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/oschwald/maxminddb-golang@v1.13.1 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/prometheus/client_golang — `github.com/prometheus/client_golang` is required at v1.19.0 in REDACTED, but v1.25.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/prometheus/client_golang@v1.25.0 && go mod tidy` and commit the updated REDACTED and go.sum.
Outdated: github.com/quic-go/quic-go — `github.com/quic-go/quic-go` is required at v0.43.0 in REDACTED, but v0.65.0 is the module's current release — so this build is missing every fix published since, including any security fix. Run `go get github.com/quic-go/quic-go@v0.65.0 && go mod tidy` and commit the updated REDACTED and go.sum.
+ 6 more in this group — see findings.md.
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 1 file(s) — `docs/src/.vitepress/theme/index.ts` — 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 01a1e5d8-668f-7377-9edb-b1773f1a7cdc · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 40 · Warnings: 401 · Recommendations: 109 · Info: 31 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 19:32 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.