Public report of openclaw/clawhub, 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, 18:54 UTC · Survey ID cd_bf6300f42b024661bc7c2ea4f9fbf58c
openclaw/clawhub
Measured 16 November 2026, 18:50 UTC, at code version 784f761
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 large codebase: 252,578 lines of product code in 4 projects, tests not counted · Estimated rebuild effort: about 3.8 person-years · Weakest lens: Production Readiness, 50.6
Findings by how serious they are
163 critical1396 serious279 minor
3 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, 18:50 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 ▸
79of 79 dimensions measured by tools.
1811of 1838 findings point to an exact file and line, so you can open each one in the code. The other 27 concern the repository as a whole, such as missing documentation.
79dimensions across 7 lenses, read from 252,578 lines of product code in 4 projects.
openclaw/clawhub is rated At risk because critical security findings are open, most of them in the build pipeline. Its score is held back in part because it has packages under a licence on your banned list. It scores 54.2 out of 100, which the At risk rating leaves unchanged. We judged it as a preview release, against a lower bar.
Production Readiness, at 50.6, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step for the work it takes is fixing the password or key in the code, worth about 3.2 points. Replacing the 14 packages under a banned licence would lift Production Readiness itself, worth about 3.6 points.
119 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen packages carry licence risk, and eight sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning each tool to an exact version, replacing or clearing the banned-licence packages and making the hidden dependencies explicit would close these risks. Passing outside input through environment variables would fix the four pipeline steps that put outside input straight into a shell command, and updating the vulnerable packages would deal with the two packages with a known security hole. The six form fields without a label need a label.
The product code is 252,578 lines, about €550,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.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Product code 45%Tests 55%
Rebuild cost: about €550,000 · Estimate
Cost to rebuild
€180,000 to €920,000, for 3,038 to 9,638 hours of work, about 3.8 person-years for 2 to 8 engineers
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.8 at a score of 54. 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
Large: 252,578 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
Raises the score by about 3.2 points · Low effort · Secret Scanning
2
Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14).
Raises the score by about 3.6 points · Medium effort · License Compliance
3
Resolve the 81 Low coverage finding(s) in Code Coverage — start with catalogFeed.ts, catalogMetadata.ts, experimentalTemplateFeed.ts.
Raises the score by about 2.0 points · Medium effort · Code Coverage
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.
Files that change often carry extra risk · Combined risk
5 files are changed often and are hard to read, which makes them the likeliest places for a mistake. They also have under half their code tested, or were written almost entirely by one person, so a mistake there is less likely to be caught, or only one person knows the code well enough to avoid it. A change to these files therefore carries more risk than the overall score suggests.
Based on: Churn × Complexity Hotspots (86 files) · Code Coverage (81 files under half tested) · Bus Factor (0 files written almost entirely by one person) · The files: templatePackage.ts, useUnifiedSearch.ts and homeListingData.ts
What to do: Add tests to these files and have a second person review every change to them, starting with templatePackage.ts, useUnifiedSearch.ts and homeListingData.ts.
Where the investment is most exposed · Value at risk
This code would cost about €550,000 to build again, about 3.8 person-years of work. Its weakest lens is Production Readiness, at 50.6 (Adequate). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 3.2 points for low effort, because it clears the 1 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 4.7 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 8% to 19% on every change. The history of the code shows how much it changes: about 327,442 lines over the last 90 days, which is about 1,327,959 lines a year. At that pace, the extra work comes to an estimated 276.7 to 1659.9 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 · 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.
242 modules, with 109 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; 202 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.
convex uses convex.agentSkillsHttp, so a change to convex.agentSkillsHttp can break convex, while a change to convex can't break convex.agentSkillsHttp.
Position
Below the diagonal: convex uses a module listed above it, which is the healthy direction.
convex uses convex.catalogClassification, so a change to convex.catalogClassification can break convex, while a change to convex can't break convex.catalogClassification.
Position
Below the diagonal: convex uses a module listed above it, which is the healthy direction.
convex uses convex.featuredSelections, so a change to convex.featuredSelections can break convex, while a change to convex can't break convex.featuredSelections.
Position
Below the diagonal: convex uses a module listed above it, which is the healthy direction.
convex uses convex.lib.githubSkillSync, so a change to convex.lib.githubSkillSync can break convex, while a change to convex can't break convex.lib.githubSkillSync.
Position
Below the diagonal: convex uses a module listed above it, which is the healthy direction.
convex uses convex.lib.packageCatalogRead, so a change to convex.lib.packageCatalogRead can break convex, while a change to convex can't break convex.lib.packageCatalogRead.
Position
Below the diagonal: convex uses a module listed above it, which is the healthy direction.
convex uses convex.lib.publisherAbuseScoring, so a change to convex.lib.publisherAbuseScoring can break convex, while a change to convex can't break convex.lib.publisherAbuseScoring.
Position
Below the diagonal: convex uses a module listed above it, which is the healthy direction.
convex.httpApiV1 uses convex.httpApiV1.packagesV1, so a change to convex.httpApiV1.packagesV1 can break convex.httpApiV1, while a change to convex.httpApiV1 can't break convex.httpApiV1.packagesV1.
Position
Below the diagonal: convex.httpApiV1 uses a module listed above it, which is the healthy direction.
convex.httpApiV1 uses convex.httpApiV1.skillsV1, so a change to convex.httpApiV1.skillsV1 can break convex.httpApiV1, while a change to convex.httpApiV1 can't break convex.httpApiV1.skillsV1.
Position
Below the diagonal: convex.httpApiV1 uses a module listed above it, which is the healthy direction.
convex.httpApiV1 uses convex.lib.installResolver, so a change to convex.lib.installResolver can break convex.httpApiV1, while a change to convex.httpApiV1 can't break convex.lib.installResolver.
Position
Below the diagonal: convex.httpApiV1 uses a module listed above it, which is the healthy direction.
convex.httpApiV1 uses convex.lib.skills.publicVersions, so a change to convex.lib.skills.publicVersions can break convex.httpApiV1, while a change to convex.httpApiV1 can't break convex.lib.skills.publicVersions.
Position
Below the diagonal: convex.httpApiV1 uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.artifactModeration, so a change to convex.lib.artifactModeration can break convex.lib, while a change to convex.lib can't break convex.lib.artifactModeration.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.canonicalTrending, so a change to convex.lib.canonicalTrending can break convex.lib, while a change to convex.lib can't break convex.lib.canonicalTrending.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.clawhubVercelOidc, so a change to convex.lib.clawhubVercelOidc can break convex.lib, while a change to convex.lib can't break convex.lib.clawhubVercelOidc.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.embeddingVisibility, so a change to convex.lib.embeddingVisibility can break convex.lib, while a change to convex.lib can't break convex.lib.embeddingVisibility.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.githubHandoff, so a change to convex.lib.githubHandoff can break convex.lib, while a change to convex.lib can't break convex.lib.githubHandoff.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.githubSkillSync, so a change to convex.lib.githubSkillSync can break convex.lib, while a change to convex.lib can't break convex.lib.githubSkillSync.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.httpRateLimit, so a change to convex.lib.httpRateLimit can break convex.lib, while a change to convex.lib can't break convex.lib.httpRateLimit.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.httpRouteRateLimit, so a change to convex.lib.httpRouteRateLimit can break convex.lib, while a change to convex.lib can't break convex.lib.httpRouteRateLimit.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.installResolver, so a change to convex.lib.installResolver can break convex.lib, while a change to convex.lib can't break convex.lib.installResolver.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.moderationReasonCodes, so a change to convex.lib.moderationReasonCodes can break convex.lib, while a change to convex.lib can't break convex.lib.moderationReasonCodes.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.packageCatalogRead, so a change to convex.lib.packageCatalogRead can break convex.lib, while a change to convex.lib can't break convex.lib.packageCatalogRead.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.publicBrowse, so a change to convex.lib.publicBrowse can break convex.lib, while a change to convex.lib can't break convex.lib.publicBrowse.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.publisherAbuseScoring, so a change to convex.lib.publisherAbuseScoring can break convex.lib, while a change to convex.lib can't break convex.lib.publisherAbuseScoring.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.publishers, so a change to convex.lib.publishers can break convex.lib, while a change to convex.lib can't break convex.lib.publishers.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
convex.lib uses convex.lib.skillPublish, so a change to convex.lib.skillPublish can break convex.lib, while a change to convex.lib can't break convex.lib.skillPublish.
Position
Below the diagonal: convex.lib uses a module listed above it, which is the healthy direction.
packages.clawhub.src.cli.commands uses convex.lib.packageCatalogRead, so a change to convex.lib.packageCatalogRead can break packages.clawhub.src.cli.commands, while a change to packages.clawhub.src.cli.commands can't break convex.lib.packageCatalogRead.
Position
Below the diagonal: packages.clawhub.src.cli.commands uses a module listed above it, which is the healthy direction.
packages.clawhub.src.cli.commands uses convex.lib.skillPublish, so a change to convex.lib.skillPublish can break packages.clawhub.src.cli.commands, while a change to packages.clawhub.src.cli.commands can't break convex.lib.skillPublish.
Position
Below the diagonal: packages.clawhub.src.cli.commands uses a module listed above it, which is the healthy direction.
server uses convex.lib.archiveManifest, so a change to convex.lib.archiveManifest can break server, while a change to server can't break convex.lib.archiveManifest.
Position
Below the diagonal: server uses a module listed above it, which is the healthy direction.
src.lib uses convex.lib.packageCatalogRead, so a change to convex.lib.packageCatalogRead can break src.lib, while a change to src.lib can't break convex.lib.packageCatalogRead.
Position
Below the diagonal: src.lib uses a module listed above it, which is the healthy direction.
src.lib uses src.lib.detectRelativeReadmeAssets, so a change to src.lib.detectRelativeReadmeAssets can break src.lib, while a change to src.lib can't break src.lib.detectRelativeReadmeAssets.
Position
Below the diagonal: src.lib uses a module listed above it, which is the healthy direction.
src.lib uses src.lib.useUnifiedSearch, so a change to src.lib.useUnifiedSearch can break src.lib, while a change to src.lib can't break src.lib.useUnifiedSearch.
Position
Below the diagonal: src.lib uses a module listed above it, which is the healthy direction.
src.routes uses src.lib.useUnifiedSearch, so a change to src.lib.useUnifiedSearch can break src.routes, while a change to src.routes can't break src.lib.useUnifiedSearch.
Position
Below the diagonal: src.routes uses a module listed above it, which is the healthy direction.
src.routes uses src.routes.-management.managementShared, so a change to src.routes.-management.managementShared can break src.routes, while a change to src.routes can't break src.routes.-management.managementShared.
Position
Below the diagonal: src.routes uses a module listed above it, which is the healthy direction.
src.routes.plugins uses src.lib.detectRelativeReadmeAssets, so a change to src.lib.detectRelativeReadmeAssets can break src.routes.plugins, while a change to src.routes.plugins can't break src.lib.detectRelativeReadmeAssets.
Position
Below the diagonal: src.routes.plugins uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 54.6 · Adequate · gated by D1, D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
134
High / Critical
A03:2025 — Software Supply Chain Failures
12
High / Critical
A02:2025 — Security Misconfiguration
2
High / Critical
A07:2025 — Authentication Failures
1
High / Critical
Roadmap
Top priorities: Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14); Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED; Adopt pino (or winston) and log at meaningful points in the services you run.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED.
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.
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 — 163
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 — 1396
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 — 279
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 3
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 79 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 — 79 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, 1811 of 1838 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.
D11 Test Reliability — 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. Test reliability for the vitest suite in packages/clawhub-admin/ was NOT MEASURED: the install for packages/clawhub-admin/ left no `vitest` binary under node_modules, so the suite could not be launched. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (packages/clawhub/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D27 Navigability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Tracing effort is measured over resolved call sites, and all 583 sampled here came from .ts files. This repository's .tsx source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `convex/_generated/api.d.ts`, `convex/catalogFeed.ts`, `convex/devSeed.ts`, `convex/featuredIntelligence.ts`, `convex/httpApiV1/packagesV1.ts`, … (+48 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
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. 'convex/react' is imported (src/routes/add.tsx:2), but this repository stands up no server and carries no migration or rules file this check reads, so who may read and write its data could not be decided.
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.
R10 Code Duplication — 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. 1117 further occurrence(s) are not listed individually; the score already reflects all 1157.
R11 Import Boundaries — 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. 85 further occurrence(s) are not listed individually; the score already reflects all 125.
R2 Cyclomatic Complexity — 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. 1055 further occurrence(s) are not listed individually; the score already reflects all 1095.
R3 Large Files — 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. 89 further occurrence(s) are not listed individually; the score already reflects all 129.
X10 Duplicated predicate — 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. 136 further occurrence(s) are not listed individually; the score already reflects all 176.
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. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala, Rust, Go, Swift, Erlang, F# and Visual Basic source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 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.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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.
320 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SkillDetailPage.SkillDetailPage at 198. A further 9 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being packagePublishRecovery.assertRecoveryArtifactEligibility at 30 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/lib/trendingApi.ts (trendingApi.isCanonicalTrendingItem at 22), convex/skillsShMirror.ts (skillsShMirror.validIdentity at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 313 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 33 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with SkillDetailPage.SkillDetailPage (cyclomatic 198), packagesV1.packagesPostRouterV1Handler (cyclomatic 167), settings.Settings (cyclomatic 162). — 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 33 together lifts Cyclomatic Complexity from 2.0 to about 4.3/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: 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.
+ 369 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 46 bodies over 60 down to 60 or less in Cognitive Complexity — start with skillsV1.skillsGetRouterV1Handler (cognitive 276), packagesV1.packagesPostRouterV1Handler (cognitive 258), skillsV1.skillsPostRouterV1Handler (cognitive 221). — 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 46 together lifts Cognitive Complexity from 2.0 to about 3.6/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.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 109 FunctionTooLong finding(s) in God Classes — start with packagesV1.ts (4), githubSkillSync.ts (4), settings.tsx (3). — One of this dimension's main actionable groups (109 warning-level).
Resolve the 66 FileTooLong finding(s) in God Classes — start with packages.ts (3), skills.ts (2), githubSkillSync.ts (2). — One of this dimension's main actionable groups (66 warning-level).
Resolve the 6 ClassTooLong finding(s) in God Classes — start with AbusePage.tsx, SkillDetailPage.tsx, Header.tsx. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
3 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence.
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.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D8 · Code Coverage7.9 / 10Strong✓ Tool-verified
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 42.1% — 81 file(s) below 50%. Measured from the JavaScript/TypeScript suite (vitest + @vitest/coverage-v8 via `npm install --ignore-scripts` (no lockfile) in the repository root, the 3 run(s) test reliability made; vitest in packages/clawhub-admin/: not run). Taken over 3 runs of the suite: a line counts as covered only when every run executed it.
Resolve the 81 Low coverage finding(s) in Code Coverage — start with catalogFeed.ts, catalogMetadata.ts, experimentalTemplateFeed.ts. — One of this dimension's main actionable groups (81 warning-level).
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Stronggated by 26 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
43 skipped (19 with a documented reason), 1 zero-assertion, 1 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 8231 tests.
No assertions: requires the registry argument at the type levelpackages/clawhub/src/cli/authToken.test.ts:68
Fixed-sleep synchronisation: reserves the last request only once when streamed bodies finish togetherscripts/evaluations/openai-capability-broker.test.ts:360
Mock-dominated test: starts a manual publisher abuse scan without exposing force-new · ×125src/routes/-management.test.tsx:1015
Resolve the 24 Skipped test finding(s) in Test Quality — start with upload-auth-smoke.pw.test.ts (2), mobile-skills.pw.test.ts, skills-sh-external.pw.test.ts. — One of this dimension's main actionable groups (24 warning-level).
Resolve the 1 No assertions finding(s) in Test Quality — start with authToken.test.ts. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Fixed-sleep synchronisation finding(s) in Test Quality — start with openai-capability-broker.test.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d10_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.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `npm install --ignore-scripts` (no lockfile) in the repository root (6696 tests); vitest via `npm install --ignore-scripts` (no lockfile) in packages/clawhub-admin/): measured (0 flaky).
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.
14 outdated direct production npm dependency(ies) of 72 graded, 0 pinning defect(s), across 4 package.json (4 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 0 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry 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, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Outdated (npm): @clack/prompts · ×14
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
1 secret(s) detected. 7 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
REDACTED
What to do
Resolve the 1 Leaked secret finding(s) in Secret Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
14 of 652 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 652 package(s) this repository's committed lockfile installs for a consumer — its 72 production, optional and peer dependency(ies), across 4 product package.json manifest(s), and everything those install in turn. Its 41 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. No third-party code was found shipping without a manifest entry (vendored or copied-in directories, licence comments preserved in committed bundles, bundled module paths, compiled wasm modules). This repository publishes itself under MIT / UNLICENSED, which is its own choice and is not judged here.
Resolve the 14 Banned license finding(s) in License Compliance — start with REDACTED (14). — One of this dimension's main actionable groups (14 issue-level).
Detailed fixes: d14_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
Top hotspots: convex/packages.ts (101×138=13938); convex/httpApiV1/packagesV1.ts (50×167=8350); convex/httpApiV1/skillsV1.ts (28×157=4396) Repeated repair below the complexity floor: convex/publishAttempts.ts (16 of 26 changes were fixes); convex/skillEvaluations.ts (9 of 12 changes were fixes); scripts/run-playwright-local-auth.ts (7 of 10 changes were fixes)
Resolve the 83 Hotspot finding(s) in Churn × Complexity Hotspots — start with packages.ts (3), skills.ts (2), publish.tsx (2). — One of this dimension's main actionable groups (83 warning-level).
Resolve the 10 Repeated repair finding(s) in Churn × Complexity Hotspots — start with canonicalTrending.ts (2), publishAttempts.ts, skillEvaluations.ts. — One of this dimension's main actionable groups (10 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 Factor8.6 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
75 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is src/routes/-management/AbusePage.tsx. Counted over 554 of the 928 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×3
Further sole-owners (lower concentration)
What to do
Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
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.
1 deducted task-comment markers across 246172 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
TodoCommentconvex/http.ts:316
What to do
Resolve the 1 TodoComment finding(s) in Explicit Debt — start with http.ts. — One of this dimension's main actionable groups (1 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.
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.
0 of 1 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
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.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
1 of 4 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionpackage.json:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with package.json. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
19 % of calls cross a namespace and 0 % go through an interface, but 53 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated. Measured over the .ts source only — this repository's .tsx was not sampled for call sites, so this score covers part of the tree, not all of it.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: 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).
134 finding(s): 0 critical, 129 high, 5 medium, 0 low. 119 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 88 file(s) — `.agents/skills/axiom-sre/scripts/discover-alerts` (lines 37–77), `.agents/skills/axiom-sre/scripts/discover-axiom` (lines 81–198), `.agents/skills/axiom-sre/scripts/discover-grafana` (lines 35–76), `.agents/skills/axiom-sre/scripts/discover-pyroscope` (lines 35–76), `.agents/skills/axiom-sre/scripts/discover-slack` (lines 35–86), … (+83 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 10 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 5 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 4 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2), REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 119 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 (119 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 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2), REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d30_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.
4 of 554 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is convex/devSeedExtra.ts. Counted over 554 of the 928 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Orphaned file · ×4convex/devSeedExtra.ts:1
Orphaned files with no living knowledge
✓ On the Gold path — maintain.
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.
Resolve the 8 Boundary-crossing change coupling finding(s) in Change Coupling — start with securityDataset.ts (2), publisherAbuse.ts, httpApiV1.ts. — One of this dimension's main actionable groups (8 issue-level).
Resolve the 5 Change coupling finding(s) in Change Coupling — start with httpRateLimit.ts, SkillCard.tsx, crons.ts. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with schema.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (REDACTED or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a REDACTED (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d37_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 65 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels6.9 / 10Strong✓ 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 UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — src/routes/-management/AbusePage.tsx:755
A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one. — src/routes/-management/ManagedMcpTools.tsx:329
This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label. (×5) — src/routes/-management/PluginsPage.tsx:38, src/routes/-management/ReportsPage.tsx:34, src/routes/-management/SkillsPage.tsx:92, …
This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed. — src/routes/-management/UsersPage.tsx:77
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. — src/routes/import.tsx:1062
This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — src/routes/skills/publish.tsx:876
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.
Do you agree with this assessment?
AC3 · Page structure7.5 / 10Strong✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — src/routes/plugins/$name.tsx:1451, src/routes/settings.tsx:983
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".
This <svg> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its only behaviour is bound to mousemove and pointermove, pointer gestures a keyboard cannot produce, and there is no key handler. The tab stop leads nowhere. Bind the same behaviour to a key handler, or provide an equivalent control elsewhere. — src/components/MetricTrendCard.tsx:117
This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. — src/components/dashboard/DashboardNeedsAttention.tsx:198
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.
<input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — src/components/ui/input.tsx:6
<textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2). — src/components/ui/textarea.tsx:8
`.publisher-profile-bio-toggle:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/publisher-profile.css:338
`.publisher-profile-chrome-more-trigger:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/publisher-profile.css:360
`.publisher-profile-members-menu-list [data-slot="dropdown-menu-item"][data-highlighted]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/publisher-profile.css:589
`.catalog-topic-input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:431
`.user-dropdown-content [data-slot="dropdown-menu-item"]:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:1172
`.skillspector-checks-toggle:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:1638
`.detail-inline-tab:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:5750
`.search-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:9972
`.markdown-code-block-action:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:10425
`.pa-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:11310
`.management-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:12179
`.browse-topic-chip.is-active` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:14103
`a.home-v2-apps-see-all:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:17685
`a.home-v2-byos-import:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:18399
`.dashboard-publisher-select-item:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — src/styles.css:20092
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 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 · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`getCatalogClassificationPageInternalHandler` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — convex/catalogClassification.ts:189
`checkDependencyRegistriesHandler` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — convex/depRegistryScan.ts:4
The guard above `return undefined;` also returns `undefined`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — packages/clawhub/src/cli.ts:158
`onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. (×3) — src/routes/plugins/index.tsx:313, src/routes/plugins/index.tsx:320, src/routes/plugins/index.tsx:329
`onClear` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it. — src/routes/plugins/index.tsx:314
The guard above `return false;` also returns `false`, so no input can make it matter. Implement the distinction that was intended, or delete the guard. — src/routes/skills/publish.tsx:575
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×4) — convex/_generated/api.js:1, convex/_generated/server.js:1, src/routeTree.gen.ts:1, …
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×24) — e2e/local-auth/delete-account-resources.pw.test.ts:11, e2e/local-auth/delete-org-resources.pw.test.ts:11, REDACTED:12, …
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether 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.
scripts/security-dataset/huggingface-live/README.md links to `metadata/latest-manifest.json`, but `scripts/security-dataset/huggingface-live/metadata/latest-manifest.json` does not exist. 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. — scripts/security-dataset/huggingface-live/README.md:51
What to do
Reconcile the README with reality: scripts/security-dataset/huggingface-live/README.md links to `metadata/latest-manifest.json`, but `scripts/security-dataset/huggingface-live/metadata/latest-manifest.json` does not exist.
No logging call was found in the 801 JavaScript/TypeScript production file(s) this check read across 4 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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.
`REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
What to do
Dependabot is configured but does not watch `pip` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
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.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`unzipSync` in `buildArchive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — convex/agentSkillsHttp.ts:358
`unzipSync` in `fetchArtifactReceipt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — convex/lib/openClawPublishAuthorization.ts:672
`gzipSync` in `listArtifactExportBatchCompressedForWorker` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — convex/securityDatasetNode.ts:91
`spawnSync` in `buildCliPackage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/clawhub/scripts/shared-schema.mjs:63
`unzipSync` in `fetchGitHubSource` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/clawhub/src/cli/commands/github.ts:112
`unzipSync` in `extractZipToDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/clawhub/src/skills.ts:50
`unzipSync` in `extractGitHubZipPathToDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/clawhub/src/skills.ts:66
`rmSync` in `materializeNvidiaSkillsSnapshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/evaluations/skill-evaluation-runtime.ts:261
`existsSync` in `prepareExtractedPluginRoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/package-inspector-nightly-scan.ts:824
`existsSync` in `writeSyntheticConfigIfNeeded` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/package-inspector-nightly-scan.ts:934, scripts/package-inspector-nightly-scan.ts:935
`existsSync` in `readJsonIfExists` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/package-inspector-nightly-scan.ts:967
`rmSync` in `cleanupOwnedResources` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/run-playwright-local-auth.ts:317
`readFileSync` in `readFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/run-playwright-local-auth.ts:335
`mkdirSync` in `warmLocalAuthExternalNodeDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/run-playwright-local-auth.ts:347
`writeFileSync` in `warmLocalAuthExternalNodeDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/run-playwright-local-auth.ts:348
`rmSync` in `startLocalConvex` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/run-playwright-local-auth.ts:429
`existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/run-playwright-local-auth.ts:532
`writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/run-playwright-local-auth.ts:588
`spawnSync` in `runStep` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — scripts/seed.ts:100, scripts/seed.ts:110
`spawnSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/staging-seed/import-test-snapshot.ts:44
`unzipSync` in `extractSafeTemplateZip` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — scripts/templates-feed-openclaw-e2e.ts:102
`unzipSync` in `expandFilesWithReport` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — src/lib/uploadFiles.ts:14
`gunzipSync` in `expandFilesWithReport` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — src/lib/uploadFiles.ts:23, src/lib/uploadFiles.ts:28
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
63 duplicated blocks under the repository root have copies in at least two of the sibling directories convex, packages, scripts, server, src — 34 of them are reported below, and 29 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 63 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 63 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 63 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — scripts/skills-sh-catalog/capture-frozen-snapshot.ts:33
26 duplicated blocks under packages/ have copies in at least two of the sibling directories clawhub, clawhub-admin, schema — 19 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/clawhub/src/schema/schemas.ts:228
26 duplicated blocks under src/ have copies in at least two of the sibling directories components, lib, routes — 14 of them are reported below, and 12 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/components/SkillDetailPageView.tsx:518
13 duplicated blocks under convex/ have copies in at least two of the sibling directories httpApiV1, lib — 9 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — convex/httpApiV1/managedMcpV1.ts:24
13 duplicated blocks under scripts/ have copies in at least two of the sibling directories canonical-search, canonical-trending, design-audit, evaluations, lib, public-corpus (+6 more sibling(s) not listed) — 10 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — scripts/security/run-codex-scan-worker.ts:346
10 duplicated blocks under src/routes/ have copies in at least two of the sibling directories $owner, -management, official, orgs, p, plugins (+2 more sibling(s) not listed) — 6 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/routes/official/index.tsx:118
convex/httpApiV1/packagesV1.ts:1696 · convex/httpApiV1/skillsV1.ts:3509 — the two spans are one implementation copied and then locally edited — 1811 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/httpApiV1/packagesV1.ts:1696
src/components/PluginVersionsPanel.tsx:44 · src/components/SkillVersionsPanel.tsx:28 — the two spans are one implementation copied and then locally edited — 1133 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/PluginVersionsPanel.tsx:44
convex/securityScanDispatch.ts:26 · convex/skillEvaluationDispatch.ts:15 — the two spans are one implementation copied and then locally edited — 1082 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/securityScanDispatch.ts:26
convex/devSeed.ts:4189 · convex/devSeed.ts:4529 — the two spans are one implementation copied and then locally edited — 697 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/devSeed.ts:4189
src/routes/official/index.tsx:118 · src/routes/plugins/index.tsx:458 — the two spans are one implementation copied and then locally edited — 580 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/routes/official/index.tsx:118
src/components/SkillDetailPageView.tsx:518 · src/routes/plugins/$name.tsx:1670 — the two spans are one implementation copied and then locally edited — 501 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/SkillDetailPageView.tsx:518
convex/lib/packageSearchDigest.ts:8 · convex/lib/skillSearchDigest.ts:16 — the two spans are one implementation copied and then locally edited — 589 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/lib/packageSearchDigest.ts:8
src/components/PackageSourceChooser.tsx:193 · src/routes/skills/publish.tsx:895 — the two spans are one implementation copied and then locally edited — 376 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/PackageSourceChooser.tsx:193
scripts/skills-sh-catalog/capture-frozen-snapshot.ts:33 · server/skillsShCatalogSource.ts:2706 — the two spans are one implementation copied and then locally edited — 671 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — scripts/skills-sh-catalog/capture-frozen-snapshot.ts:33
packages/schema/src/catalogFeed.ts:66 · packages/schema/src/experimentalTemplateFeed.ts:37 — the two spans are one implementation copied and then locally edited — 481 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/schema/src/catalogFeed.ts:66
packages/clawhub/src/schema/schemas.ts:228 · packages/schema/src/schemas.ts:66 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/clawhub/src/schema/schemas.ts:228
convex/leaderboards.ts:74 · convex/packageLeaderboards.ts:78 — the two spans are one implementation copied and then locally edited — 440 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/leaderboards.ts:74
convex/maintenance.ts:3164 · convex/maintenance.ts:3259 — all 2 copies are in the same file, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — convex/maintenance.ts:3164
convex/securityScan.ts:3105 · convex/skillsShCatalog.ts:1376 — the two spans are one implementation copied and then locally edited — 360 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/securityScan.ts:3105
convex/devSeed.ts:3218 · convex/devSeed.ts:3999 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — convex/devSeed.ts:3218
server/routes/og/plugin.png.ts:42 · server/routes/og/skill.png.ts:32 — the two spans are one implementation copied and then locally edited — 310 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — server/routes/og/plugin.png.ts:42
convex/httpApiV1/packagesV1.ts:1357 · convex/httpApiV1/packagesV1.ts:1560 — the two spans are one implementation copied and then locally edited — 220 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/httpApiV1/packagesV1.ts:1357
src/components/SecurityAuditPage.tsx:652 · src/components/SecurityAuditPage.tsx:850 — 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. — src/components/SecurityAuditPage.tsx:652
packages/clawhub/src/cli/commands/packages.ts:1611 · packages/clawhub/src/cli/commands/packages.ts:1663 — 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. — packages/clawhub/src/cli/commands/packages.ts:1611
src/routes/-management/PluginsPage.tsx:35 · src/routes/-management/SkillsPage.tsx:89 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/routes/-management/PluginsPage.tsx:35
convex/securityScan.ts:1012 · convex/securityScan.ts:2508 — 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. — convex/securityScan.ts:1012
packages/clawhub-admin/src/commands/moderation.ts:82 · packages/clawhub-admin/src/commands/moderation.ts:128 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/clawhub-admin/src/commands/moderation.ts:82
convex/canonicalTrending.ts:440 · convex/canonicalTrending.ts:564 — the two spans are one implementation copied and then locally edited — 287 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/canonicalTrending.ts:440
convex/publishAttempts.ts:1183 · convex/publishAttempts.ts:1227 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — convex/publishAttempts.ts:1183
convex/skillTransfers.ts:369 · convex/skillTransfers.ts:414 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — convex/skillTransfers.ts:369
convex/skills.ts:3103 · convex/skills.ts:3192 — the two spans are one implementation copied and then locally edited — 271 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/skills.ts:3103
convex/pluginInspectorDispatch.ts:54 · convex/publishAttemptDispatch.ts:89 — the two spans are one implementation copied and then locally edited — 302 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/pluginInspectorDispatch.ts:54
convex/publishAttempts.ts:779 · convex/publishAttempts.ts:888 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — convex/publishAttempts.ts:779
convex/securityScan.ts:304 · scripts/security/run-codex-scan-worker.ts:1101 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — convex/securityScan.ts:304
convex/securityScan.ts:1941 · convex/securityScan.ts:1995 — 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. — convex/securityScan.ts:1941
convex/skillsShMirror.ts:1432 · convex/skillsShMirror.ts:1730 — the two spans are one implementation copied and then locally edited — 200 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — convex/skillsShMirror.ts:1432
packages/clawhub/src/cli/commands/star.ts:10 · packages/clawhub/src/cli/commands/unstar.ts:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/clawhub/src/cli/commands/star.ts:10
packages/clawhub/src/schema/packages.ts:125 · packages/schema/src/packages.ts:211 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/clawhub/src/schema/packages.ts:125
src/components/ui/dialog.tsx:75 · src/components/ui/sheet.tsx:64 — the two spans are one implementation copied and then locally edited — 245 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/components/ui/dialog.tsx:75
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
convex/httpApiV1/searchReportsV1.ts:3 reaches into another package with a relative path (../../packages/clawhub/src/schema/searchReports) — import the package by name instead. — convex/httpApiV1/searchReportsV1.ts:3
convex/lib/clawpack.ts:3 reaches into another package with a relative path (../../packages/clawhub/src/clawpack) — import the package by name instead. — convex/lib/clawpack.ts:3
convex/searchReports.ts:3 reaches into another package with a relative path (../packages/clawhub/src/schema/searchReports) — import the package by name instead. — convex/searchReports.ts:3
e2e/local-auth/publish-skill-lifecycle.pw.test.ts:9 reaches past another workspace package's public entry into its internals with a relative path (../../packages/schema/src/ark) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — e2e/local-auth/publish-skill-lifecycle.pw.test.ts:9
e2e/local-auth/publish-skill-lifecycle.pw.test.ts:10 reaches past another workspace package's public entry into its internals with a relative path (../../packages/schema/src/schemas) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — e2e/local-auth/publish-skill-lifecycle.pw.test.ts:10
packages/clawhub-admin/scripts/build.mjs:1 reaches into another package with a relative path (../../clawhub/scripts/shared-schema.mjs) — import the package by name instead. — packages/clawhub-admin/scripts/build.mjs:1
packages/clawhub-admin/src/buildInfo.ts:4 reaches into another package with a relative path (../../clawhub/src/cli/buildInfo.js) — import the package by name instead. — packages/clawhub-admin/src/buildInfo.ts:4
packages/clawhub-admin/src/cli.ts:5 reaches into another package with a relative path (../../clawhub/src/cli/commands/auth.js) — import the package by name instead. — packages/clawhub-admin/src/cli.ts:5
packages/clawhub-admin/src/cli.ts:6 reaches into another package with a relative path (../../clawhub/src/cli/commands/delete.js) — import the package by name instead. — packages/clawhub-admin/src/cli.ts:6
packages/clawhub-admin/src/cli.ts:7 reaches into another package with a relative path (../../clawhub/src/cli/commands/packages.js) — import the package by name instead. — packages/clawhub-admin/src/cli.ts:7
packages/clawhub-admin/src/cli.ts:12 reaches into another package with a relative path (../../clawhub/src/cli/commands/skills.js) — import the package by name instead. — packages/clawhub-admin/src/cli.ts:12
packages/clawhub-admin/src/cli.ts:16 reaches into another package with a relative path (../../clawhub/src/cli/globalOpts.js) — import the package by name instead. — packages/clawhub-admin/src/cli.ts:16
packages/clawhub-admin/src/cli.ts:20 reaches into another package with a relative path (../../clawhub/src/cli/helpStyle.js) — import the package by name instead. — packages/clawhub-admin/src/cli.ts:20
packages/clawhub-admin/src/cli.ts:25 reaches into another package with a relative path (../../clawhub/src/cli/types.js) — import the package by name instead. — packages/clawhub-admin/src/cli.ts:25
packages/clawhub-admin/src/cli.ts:26 reaches into another package with a relative path (../../clawhub/src/cli/ui.js) — import the package by name instead. — packages/clawhub-admin/src/cli.ts:26
packages/clawhub-admin/src/commands/contentRights.ts:3 reaches into another package with a relative path (../../../clawhub/src/cli/authToken.js) — import the package by name instead. — packages/clawhub-admin/src/commands/contentRights.ts:3
packages/clawhub-admin/src/commands/contentRights.ts:4 reaches into another package with a relative path (../../../clawhub/src/cli/registry.js) — import the package by name instead. — packages/clawhub-admin/src/commands/contentRights.ts:4
packages/clawhub-admin/src/commands/contentRights.ts:5 reaches into another package with a relative path (../../../clawhub/src/cli/types.js) — import the package by name instead. — packages/clawhub-admin/src/commands/contentRights.ts:5
packages/clawhub-admin/src/commands/contentRights.ts:6 reaches into another package with a relative path (../../../clawhub/src/cli/ui.js) — import the package by name instead. — packages/clawhub-admin/src/commands/contentRights.ts:6
packages/clawhub-admin/src/commands/contentRights.ts:7 reaches into another package with a relative path (../../../clawhub/src/http.js) — import the package by name instead. — packages/clawhub-admin/src/commands/contentRights.ts:7
packages/clawhub-admin/src/commands/contentRights.ts:8 reaches into another package with a relative path (../../../clawhub/src/schema/index.js) — import the package by name instead. — packages/clawhub-admin/src/commands/contentRights.ts:8
packages/clawhub-admin/src/commands/downloads.ts:1 reaches into another package with a relative path (../../../clawhub/src/cli/authToken.js) — import the package by name instead. — packages/clawhub-admin/src/commands/downloads.ts:1
packages/clawhub-admin/src/commands/downloads.ts:2 reaches into another package with a relative path (../../../clawhub/src/cli/registry.js) — import the package by name instead. — packages/clawhub-admin/src/commands/downloads.ts:2
packages/clawhub-admin/src/commands/downloads.ts:3 reaches into another package with a relative path (../../../clawhub/src/cli/types.js) — import the package by name instead. — packages/clawhub-admin/src/commands/downloads.ts:3
packages/clawhub-admin/src/commands/downloads.ts:4 reaches into another package with a relative path (../../../clawhub/src/http.js) — import the package by name instead. — packages/clawhub-admin/src/commands/downloads.ts:4
packages/clawhub-admin/src/commands/downloads.ts:5 reaches into another package with a relative path (../../../schema/src/downloadAnalytics.js) — import the package by name instead. — packages/clawhub-admin/src/commands/downloads.ts:5
packages/clawhub-admin/src/commands/email.ts:2 reaches into another package with a relative path (../../../clawhub/src/cli/authToken.js) — import the package by name instead. — packages/clawhub-admin/src/commands/email.ts:2
packages/clawhub-admin/src/commands/email.ts:3 reaches into another package with a relative path (../../../clawhub/src/cli/loader.js) — import the package by name instead. — packages/clawhub-admin/src/commands/email.ts:3
packages/clawhub-admin/src/commands/email.ts:4 reaches into another package with a relative path (../../../clawhub/src/cli/output.js) — import the package by name instead. — packages/clawhub-admin/src/commands/email.ts:4
packages/clawhub-admin/src/commands/email.ts:5 reaches into another package with a relative path (../../../clawhub/src/cli/registry.js) — import the package by name instead. — packages/clawhub-admin/src/commands/email.ts:5
packages/clawhub-admin/src/commands/email.ts:6 reaches into another package with a relative path (../../../clawhub/src/cli/types.js) — import the package by name instead. — packages/clawhub-admin/src/commands/email.ts:6
packages/clawhub-admin/src/commands/email.ts:7 reaches into another package with a relative path (../../../clawhub/src/cli/ui.js) — import the package by name instead. — packages/clawhub-admin/src/commands/email.ts:7
packages/clawhub-admin/src/commands/email.ts:8 reaches into another package with a relative path (../../../clawhub/src/http.js) — import the package by name instead. — packages/clawhub-admin/src/commands/email.ts:8
packages/clawhub-admin/src/commands/email.ts:9 reaches into another package with a relative path (../../../clawhub/src/schema/index.js) — import the package by name instead. — packages/clawhub-admin/src/commands/email.ts:9
packages/clawhub-admin/src/commands/featured.ts:1 reaches into another package with a relative path (../../../clawhub/src/cli/authToken.js) — import the package by name instead. — packages/clawhub-admin/src/commands/featured.ts:1
packages/clawhub-admin/src/commands/featured.ts:2 reaches into another package with a relative path (../../../clawhub/src/cli/output.js) — import the package by name instead. — packages/clawhub-admin/src/commands/featured.ts:2
packages/clawhub-admin/src/commands/featured.ts:3 reaches into another package with a relative path (../../../clawhub/src/cli/registry.js) — import the package by name instead. — packages/clawhub-admin/src/commands/featured.ts:3
packages/clawhub-admin/src/commands/featured.ts:4 reaches into another package with a relative path (../../../clawhub/src/cli/types.js) — import the package by name instead. — packages/clawhub-admin/src/commands/featured.ts:4
packages/clawhub-admin/src/commands/featured.ts:5 reaches into another package with a relative path (../../../clawhub/src/cli/ui.js) — import the package by name instead. — packages/clawhub-admin/src/commands/featured.ts:5
packages/clawhub-admin/src/commands/featured.ts:6 reaches into another package with a relative path (../../../clawhub/src/http.js) — import the package by name instead. — packages/clawhub-admin/src/commands/featured.ts:6
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
skillsGetRouterV1Handler has cyclomatic complexity 214 and cognitive complexity 321; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/httpApiV1/skillsV1.ts:1761
SkillDetailPage has cyclomatic complexity 175 and cognitive complexity 156; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/SkillDetailPage.tsx:184
packagesPostRouterV1Handler has cyclomatic complexity 166 and cognitive complexity 259; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/httpApiV1/packagesV1.ts:2615
packagesGetRouterV1Handler has cyclomatic complexity 159 and cognitive complexity 239; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/httpApiV1/packagesV1.ts:3777
AbusePage has cyclomatic complexity 154 and cognitive complexity 145; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/-management/AbusePage.tsx:47
skillsPostRouterV1Handler has cyclomatic complexity 152 and cognitive complexity 238; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/httpApiV1/skillsV1.ts:2926
PluginDetailPageContent has cyclomatic complexity 151 and cognitive complexity 133; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/plugins/$name.tsx:1048
publishPackageImpl has cyclomatic complexity 147 and cognitive complexity 190; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/packages.ts:8052
cmdUpdate has cyclomatic complexity 139 and cognitive complexity 195; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/clawhub/src/cli/commands/skills.ts:629
listPackages has cyclomatic complexity 132 and cognitive complexity 155; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/httpApiV1/packagesV1.ts:1159
handler has cyclomatic complexity 123 and cognitive complexity 158; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/skills.ts:10386
handler has cyclomatic complexity 112 and cognitive complexity 107; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/packages.ts:11253
Settings has cyclomatic complexity 111 and cognitive complexity 91; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/settings.tsx:276
SkillDetailPageView has cyclomatic complexity 104 and cognitive complexity 80; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/components/SkillDetailPageView.tsx:193
listPackagePageImpl has cyclomatic complexity 103 and cognitive complexity 173; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/packages.ts:3946
(anonymous) has cyclomatic complexity 99 and cognitive complexity 146; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — server/routes/ops/skills-sh/mirror-test.post.ts:192
Management has cyclomatic complexity 90 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/management.tsx:226
validateTemplateManifest has cyclomatic complexity 88 and cognitive complexity 154; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/schema/src/templates.ts:484
Upload has cyclomatic complexity 86 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/skills/publish.tsx:90
applyGenericGitHubSkillSourceSyncHandler has cyclomatic complexity 81 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/githubSkillSync.ts:1030
PublishPluginRoute has cyclomatic complexity 81 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/plugins/publish.tsx:173
skillsShCatalogTestV1Handler has cyclomatic complexity 80 and cognitive complexity 107; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/httpApiV1/skillsShCatalogV1.ts:619
preparePackagePublishPlan has cyclomatic complexity 76 and cognitive complexity 97; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/clawhub/src/cli/commands/packages.ts:2646
handler has cyclomatic complexity 76 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/packages.ts:10958
publishVersionForUser has cyclomatic complexity 75 and cognitive complexity 74; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/lib/skillPublish.ts:160
cmdSearchInsights has cyclomatic complexity 74 and cognitive complexity 126; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/clawhub-admin/src/commands/searchInsights.ts:17
validateRetainedPublishAttempt has cyclomatic complexity 70 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/lib/publishAttemptOperationalRecovery.ts:34
exportSkillsV1Handler has cyclomatic complexity 67 and cognitive complexity 116; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/httpApiV1/skillsV1.ts:3531
cmdPublish has cyclomatic complexity 65 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/clawhub/src/cli/commands/publish.ts:39
handler has cyclomatic complexity 62 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/securityScan.ts:2822
handler has cyclomatic complexity 61 and cognitive complexity 87; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/publishAttempts.ts:689
handler has cyclomatic complexity 61 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/skills.ts:4712
admitScans has cyclomatic complexity 61 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/skillsShCatalog.ts:1442
ImportGitHub has cyclomatic complexity 61 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/import.tsx:185
exportPluginsV1Handler has cyclomatic complexity 60 and cognitive complexity 83; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/httpApiV1/packagesV1.ts:1738
UnifiedSearchPage has cyclomatic complexity 60 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — src/routes/search.tsx:94
validateDecisionsRun has cyclomatic complexity 60 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/security/clawscan-decisions.ts:281
runPackageInspectorNightlyScan has cyclomatic complexity 59 and cognitive complexity 111; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/package-inspector-nightly-scan.ts:173
setSkillSoftDeletedByActor has cyclomatic complexity 59 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — convex/skills.ts:11462
clawScanExposure has cyclomatic complexity 59 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — scripts/security/clawscan-exposure.ts:60
Do you agree with this assessment?
R3 · Large Files4.4 / 10Weak✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
convex/packages.ts has 11699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/packages.ts:1
convex/skills.ts has 10977 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/skills.ts:1
convex/devSeed.ts has 4947 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/devSeed.ts:1
convex/httpApiV1/packagesV1.ts has 4416 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/httpApiV1/packagesV1.ts:1
convex/publishers.ts has 4125 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/publishers.ts:1
convex/schema.ts has 4108 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/schema.ts:1
convex/securityScan.ts has 3929 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/securityScan.ts:1
convex/httpApiV1/skillsV1.ts has 3866 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/httpApiV1/skillsV1.ts:1
convex/maintenance.ts has 3786 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/maintenance.ts:1
convex/githubSkillSync.ts has 3240 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/githubSkillSync.ts:1
scripts/security/run-codex-scan-worker.ts has 3061 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/security/run-codex-scan-worker.ts:1
convex/publisherAbuse.ts has 3048 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/publisherAbuse.ts:1
convex/skillsShCatalog.ts has 3004 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/skillsShCatalog.ts:1
packages/clawhub/src/cli/commands/packages.ts has 2929 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/clawhub/src/cli/commands/packages.ts:1
src/routes/settings.tsx has 2911 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/settings.tsx:1
server/skillsShCatalogSource.ts has 2888 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — server/skillsShCatalogSource.ts:1
convex/users.ts has 2585 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/users.ts:1
convex/skillsShMirror.ts has 2320 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/skillsShMirror.ts:1
convex/search.ts has 2072 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/search.ts:1
convex/lib/catalogClassifier.mjs has 2023 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/lib/catalogClassifier.mjs:1
src/routes/plugins/$name.tsx has 1808 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/plugins/$name.tsx:1
convex/publishAttempts.ts has 1800 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/publishAttempts.ts:1
convex/migrations.ts has 1726 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/migrations.ts:1
src/routes/-management/AbusePage.tsx has 1719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/-management/AbusePage.tsx:1
packages/clawhub/src/cli/commands/skills.ts has 1659 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/clawhub/src/cli/commands/skills.ts:1
src/routes/import.tsx has 1565 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/import.tsx:1
scripts/security/run-prepublication-worker.ts has 1408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/security/run-prepublication-worker.ts:1
src/routes/skills/publish.tsx has 1377 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/skills/publish.tsx:1
convex/skillStatEvents.ts has 1328 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/skillStatEvents.ts:1
convex/canonicalTrending.ts has 1321 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/canonicalTrending.ts:1
scripts/package-inspector-nightly-scan.ts has 1292 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — scripts/package-inspector-nightly-scan.ts:1
src/routeTree.gen.ts has 1242 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routeTree.gen.ts:1
src/components/Header.tsx has 1235 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/Header.tsx:1
src/components/SecurityAuditPage.tsx has 1221 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/components/SecurityAuditPage.tsx:1
convex/publisherAbuseTemporalScan.ts has 1219 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/publisherAbuseTemporalScan.ts:1
convex/httpApiV1/skillsShCatalogV1.ts has 1206 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/httpApiV1/skillsShCatalogV1.ts:1
src/routes/user/$handle.tsx has 1192 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/user/$handle.tsx:1
src/routes/management.tsx has 1142 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/management.tsx:1
src/routes/plugins/publish.tsx has 1084 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/routes/plugins/publish.tsx:1
convex/skillsShMirrorVisibility.ts has 1081 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — convex/skillsShMirrorVisibility.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage9.7 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×25) — src/routes/audits.tsx:1, src/routes/add.tsx:1, src/routes/$owner/plugins/$slug/security-audit.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.4 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 341 application, 81 tooling and 828 test entry point(s) detected in this repo. Gate removals on `bun run build` — an undetected custom entry would make these reachable.
no import path from any entry point (341 application, 81 tooling, 828 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×3) — server/routes/og/plugin.ts, server/routes/og/profile.ts, server/routes/og/skill.ts
Nothing imports this binding — it is safe to review for removal. (×4) — packages/clawhub/src/schema/license.ts:2, packages/clawhub/src/schema/license.ts:5, scripts/design-audit/report.ts:220, …
Nothing ultimately consumes this binding: its only referrer is the re-export in packages/clawhub/src/schema/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/clawhub/src/schema/index.ts in the same commit, or the barrel will import a name that no longer exists. (×6) — packages/clawhub/src/schema/schemas.ts:46, packages/clawhub/src/schema/schemas.ts:59, packages/clawhub/src/schema/schemas.ts:71, …
Nothing ultimately consumes this binding: its only referrer is the re-export in server/handlers/convexProxy.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in server/handlers/convexProxy.ts in the same commit, or the barrel will import a name that no longer exists. — server/convexProxy.ts:752
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×6) — package.json:164, package.json:167, package.json:184, …
Every import is type-only — move it to devDependencies. — REDACTED:8
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — server/skillsShCatalogSource.ts:1063
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
`truncated` loses its last character (its last element, if it holds an array) on every pass — `truncated = truncated.slice(0, -1)` on line 1056 — and the loop's only exit is the test on line 1055 — which measures `truncated` only through `Buffer.byteLength(…)`, as a TERM of a larger expression, and never compares its length against a bound of its own. So nothing stops the loop at one character: it runs until the test's other terms come under the bound WITHOUT any help from `truncated`, which leaves `truncated` empty — and if they never do, the loop never ends, because JavaScript's `slice`/`substring`/`substr`/`replace` hand back `""` for an empty value instead of throwing, so every later pass shortens nothing and the test never changes. Neither outcome announces itself: an empty value surfaces later, as a path that names no file, a key that matches nothing, or a record written blank — and a hang surfaces as a frozen tab or a request that never returns. Give the loop a floor (`&& truncated.length > 1`), or compute the length once and clamp it (`truncated = truncated.slice(0, Math.max(1, budget))`) — and decide explicitly what should happen when the budget cannot be met, rather than letting an empty value be the answer. — server/skillsShCatalogSource.ts:1055
What to do
Each finding names the loop's exit test and the statement that shortens the value. Confirm from the two that nothing bounds the length below, then give the loop a floor and decide — out loud — what should happen when the budget cannot be met: truncating to nothing is a silent answer to that question.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
`stripUndefinedForStoredPublish` is exported and takes `value: unknown` from its caller, and it calls itself at line 2 (`stripUndefinedForStoredPublish`) with a piece of `value` (and at line 7) — and nowhere in `stripUndefinedForStoredPublish` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `stripUndefinedForStoredPublish` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — convex/lib/publishStorage.ts:2
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 30/38 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`getLocalDevAuthSecret` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/components/DevPersonaFab.tsx:87
`loadPromotions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — src/components/PromotionsBar.tsx:142
`requestDeviceCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/clawhub/src/deviceAuth.ts:49
`sendResendEmail` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — convex/packages.ts:10638
`handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — convex/webhooks.ts:18
`fetchGitHubUserByNumericId` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — convex/lib/githubAccount.ts:26
`generateSkillSummary` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — convex/lib/skillSummary.ts:66
`fetchAuthenticatedGitHubOwners` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — convex/httpApiV1/skillsShCatalogV1.ts:336
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped7.6 / 10Strong✓ Tool-verified
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
`state.svg` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:226
What to do
Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×21) — vitest.setup.ts:101, src/lib/analyticsRelease.ts:9, src/lib/templateDetail.ts:80, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×10) — src/routes/plugins/publish.tsx:490, REDACTED:301, src/components/UserBadge.tsx:187, …
`.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×3) — src/routes/-management/ManagedMcpTools.tsx:53, src/lib/useUnifiedSearch.ts:408, src/lib/useUnifiedSearch.ts:422
`catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included. (×6) — src/lib/publicApiUrl.ts:13, src/components/GoogleAnalytics.tsx:206, src/components/SecurityAuditPage.tsx:990, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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.8 `!` null assertions per 1k TypeScript source lines — 177 assertion(s) across the 226509 source line(s) of the 781 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: convex/httpApiV1/packagesV1.ts (23), server/skillsShCatalogSource.ts (22), convex/skills.ts (10). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
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 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 1 observation(s) recorded · 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'.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 46 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no exported interface declares behaviour
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (the repository): the app needs environment variables or a config file (such as .env or .dev.vars) that the repository does not provide. Last output: "25 ┃ } / 26 ┃ / 27 ┃ export function getRequiredRuntimeEnv(name: string) { / 28 ┃ const value = getRuntimeEnv(name); / 29 ┃ if (value) return value; / ❯ 30 ┃ throw new Error(Missing required environment variable: ${name}); / 31 ┃ } / 32 ┃ / ⁃ at anonymous (src/convex/client.ts:5:19) / [CAUSE] / Error { / message: 'Missing required environment variable: VITE_CONVEX_URL', / stack: 'Missing required environment variable: VITE_CONVEX_URL\n' + / 'at getRequiredRuntimeEnv (./src/lib/runtimeEnv.ts:30:3)\n' + / 'at anonymous (./src/convex/client.ts:5:19)', / line: 0, / column: 0, / }" No runtime evidence was gathered. The cause is in the repository, not in our sandbox: the app needs environment variables or a config file (such as .env or .dev.vars) that the repository does not provide. Nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C2 Access Controls — Not assessed: this is a browser application whose data is served by a hosted backend ('convex/react', src/routes/add.tsx:2). Its access control is that backend's configuration — Supabase row-level security, Firebase security rules, Appwrite permissions — and this repository carries none of it that this check reads (no Supabase migration, no server code). A client-side route guard hides a page; it authorizes nothing. Whether access is authorized by default could not be established, and its absence is not scored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D25 ADR Conformance — None of 0 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D32 Data Compliance (PII/GDPR) — 53 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
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.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage data present for 128 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R5 Dependency Freshness — uses a bun lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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.
Banned license: @img/sharp-libvips-darwin-arm64 REDACTED:356— `@img/sharp-libvips-darwin-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-darwin-x64 REDACTED:358— `@img/sharp-libvips-darwin-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm REDACTED:360— `@img/sharp-libvips-linux-arm` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-arm64 REDACTED:362— `@img/sharp-libvips-linux-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-ppc64 REDACTED:364— `@img/sharp-libvips-linux-ppc64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-riscv64 REDACTED:366— `@img/sharp-libvips-linux-riscv64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-s390x REDACTED:368— `@img/sharp-libvips-linux-s390x` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linux-x64 REDACTED:370— `@img/sharp-libvips-linux-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-arm64 REDACTED:372— `@img/sharp-libvips-linuxmusl-arm64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-libvips-linuxmusl-x64 REDACTED:374— `@img/sharp-libvips-linuxmusl-x64` 1.3.4 is published on registry.npmjs.org under `LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-wasm32 REDACTED:392— `@img/sharp-wasm32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later AND MIT`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-arm64 REDACTED:396— `@img/sharp-win32-arm64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-ia32 REDACTED:398— `@img/sharp-win32-ia32` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Banned license: @img/sharp-win32-x64 REDACTED:400— `@img/sharp-win32-x64` 0.35.5 is published on registry.npmjs.org under `Apache-2.0 AND LGPL-3.0-or-later`, which this policy bans, and it is not declared by this repository but is installed by one of its production, optional or peer dependencies, as its committed lockfile resolves — a transitive dependency ships its licence just the same — so it is installed by everything that depends on this repository, not just by its build toolchain. A package offering SEVERAL licences is a choice and is only charged when every one of them is banned. Replace the package (or the dependency that pulls it in), or record an accepted exception. ★ The licence that makes this row is LGPL-3.0, and unmodified use is often permitted: the LGPL lets your code use an UNMODIFIED copy of the library that stays a separately installed package (its own entry in node_modules, site-packages or the gem path, which a user can replace) without your code coming under the LGPL. What it then asks is that you pass on its licence and notices and let users swap in their own build of it (LGPL-3.0 section 4). Modifying it, copying its code into yours, or merging it into one bundled or statically linked artifact is where the obligations grow, and this policy cannot see which you do — that is why it denies LGPL-3.0 by default. If you use it unmodified and separately installed, allow it in your repository's licence policy rather than replacing it: add `LGPL-3.0-only` / `LGPL-3.0-or-later` to the allow-list of the licence check your CI runs (`license-checker --onlyAllow`, the `allow-licenses` input of GitHub's dependency-review-action, `[licenses] allow` in cargo-deny's deny.toml), record why in the same change, and hide this row on the findings page with that reason. This scan's banned set is not read from that file, so the row stays until it is hidden.
Boundary-crossing change coupling: publisherAbuse.ts ↔ AbusePage.tsx convex/publisherAbuse.ts:1— `convex/publisherAbuse.ts` (context convex) and `src/routes/-management/AbusePage.tsx` (context routes) sit in DIFFERENT parts of the tree yet change together 79% of the time (15 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `d4054705` fix: let staff stop stuck signal scans (#3574); `3c9d4f12` feat: tighten traffic signals and make them read only (#3493); `987ad8bd` feat: add 30-day activity trends to abuse signal drawer (#3216) — run `git show` on any of them.
Boundary-crossing change coupling: httpApiV1.ts ↔ routes.ts convex/httpApiV1.ts:1— `convex/httpApiV1.ts` (context convex) and `packages/schema/src/routes.ts` (context schema) sit in DIFFERENT parts of the tree yet change together 71% of the time (15 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `cbfee734` feat(api): add plugin marketplace overview snapshot (#3664); `6a7c1558` feat(api): expose plugin categories (#3582); `f92495fc` feat: add canonical Trending snapshot API (#3265) — run `git show` on any of them.
Boundary-crossing change coupling: securityDataset.ts ↔ normalize.ts convex/securityDataset.ts:1— `convex/securityDataset.ts` (context convex) and `scripts/security-dataset/normalize.ts` (context scripts) sit in DIFFERENT parts of the tree yet change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `d677ce37` refactor: share security dataset redaction policy (#4268); `9aa3f37e` feat: export skill bundle content for security datasets (#2448); `51967bca` feat: export skillspector issue details (#2430) — run `git show` on any of them.
Boundary-crossing change coupling: publisherAbuseTemporalScan.ts ↔ AbusePage.tsx convex/publisherAbuseTemporalScan.ts:1— `convex/publisherAbuseTemporalScan.ts` (context convex) and `src/routes/-management/AbusePage.tsx` (context routes) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `d4054705` fix: let staff stop stuck signal scans (#3574); `3c9d4f12` feat: tighten traffic signals and make them read only (#3493); `8a8e6927` fix: alert when signal scans stop retrying (#3202) — run `git show` on any of them.
Boundary-crossing change coupling: schema.ts ↔ AbusePage.tsx convex/schema.ts:1— `convex/schema.ts` (context convex) and `src/routes/-management/AbusePage.tsx` (context routes) sit in DIFFERENT parts of the tree yet change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `d4054705` fix: let staff stop stuck signal scans (#3574); `3c9d4f12` feat: tighten traffic signals and make them read only (#3493); `7ef2b15c` Dedupe abuse signal alerts and add bulk review (#3214) — run `git show` on any of them.
Boundary-crossing change coupling: securityDataset.ts ↔ convexExport.ts convex/securityDataset.ts:1— `convex/securityDataset.ts` (context convex) and `scripts/security-dataset/convexExport.ts` (context scripts) sit in DIFFERENT parts of the tree yet change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `03f97349` fix: preserve legacy package ZIP hashes (#2636); `9aa3f37e` feat: export skill bundle content for security datasets (#2448); `05f27f64` feat: export skillspector dataset signals (#2424) — run `git show` on any of them.
Boundary-crossing change coupling: SkillDetailPage.tsx ↔ $handle.tsx src/components/SkillDetailPage.tsx:1— `src/components/SkillDetailPage.tsx` (context components) and `src/routes/u/$handle.tsx` (context routes) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `be4c51ed` fix: improve auth flow and webkit compatibility (#1555); `f4db0ee3` fix: improve auth flow and webkit compatibility (#1555); `15047082` feat: marketplace UI overhaul — HuggingFace/npm-style discovery hub — run `git show` on any of them.
Boundary-crossing change coupling: usersV1.ts ↔ schemas.ts convex/httpApiV1/usersV1.ts:1— `convex/httpApiV1/usersV1.ts` (context convex) and `packages/clawhub/src/schema/schemas.ts` (context clawhub) sit in DIFFERENT parts of the tree yet change together 50% of the time (12 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `6381d789` feat(admin): support org profile updates (#3416); `a7cab2a0` fix(moderation): expose account hold restoration (#3128); `fb7b73b8` feat: reclaim deleted org handles — run `git show` on any of them.
AC2 · Forms & labels· <input> without a programmatic label · ×6
<input> without a programmatic label src/routes/-management/PluginsPage.tsx:38— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/routes/-management/ReportsPage.tsx:34— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/routes/-management/SkillsPage.tsx:92— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/routes/-management/UsersPage.tsx:44— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/routes/search.tsx:243— This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label htmlFor>, a wrapping <label>, or aria-label.
<input> without a programmatic label src/routes/skills/publish.tsx:876— This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· Link with no accessible name · ×1
Link with no accessible name src/routes/import.tsx:1062— 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.
Focusable <svg> isn't keyboard-operable src/components/MetricTrendCard.tsx:117— This <svg> carries tabIndex={0}, so it is in the tab order and a keyboard user will land on it — but its only behaviour is bound to mousemove and pointermove, pointer gestures a keyboard cannot produce, and there is no key handler. The tab stop leads nowhere. Bind the same behaviour to a key handler, or provide an equivalent control elsewhere.
FunctionTooLong: settings.Settings src/routes/settings.tsx:276— FunctionTooLong — Settings runs 1462 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 1362 over it, 14.62× 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: publish.Upload src/routes/skills/publish.tsx:90— FunctionTooLong — Upload runs 1072 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 972 over it, 10.72× 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: publish.PublishPluginRoute src/routes/plugins/publish.tsx:173— FunctionTooLong — PublishPluginRoute runs 798 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 698 over it, 7.98× 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: $name.PluginDetailPageContent src/routes/plugins/$name.tsx:1048— FunctionTooLong — PluginDetailPageContent runs 767 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 667 over it, 7.67× 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: AbusePage.AbusePage src/routes/-management/AbusePage.tsx:47— FunctionTooLong — AbusePage runs 726 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 626 over it, 7.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.
FunctionTooLong: SkillDetailPage.SkillDetailPage src/components/SkillDetailPage.tsx:184— FunctionTooLong — SkillDetailPage runs 723 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 623 over it, 7.23× 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: import.ImportGitHub src/routes/import.tsx:185— FunctionTooLong — ImportGitHub runs 673 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 573 over it, 6.73× 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: devSeed.seedLocalModerationFixturesHandler convex/devSeed.ts:2934— FunctionTooLong — seedLocalModerationFixturesHandler runs 668 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 568 over it, 6.68× 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: management.Management src/routes/management.tsx:226— FunctionTooLong — Management runs 654 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 554 over it, 6.54× 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: skillsV1.skillsGetRouterV1Handler convex/httpApiV1/skillsV1.ts:1761— FunctionTooLong — skillsGetRouterV1Handler runs 627 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 527 over it, 6.27× 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: Header.Header src/components/Header.tsx:132— FunctionTooLong — Header runs 627 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 527 over it, 6.27× 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: SkillDetailPageView.SkillDetailPageView src/components/SkillDetailPageView.tsx:193— FunctionTooLong — SkillDetailPageView runs 525 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 425 over it, 5.25× 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: packagesV1.packagesPostRouterV1Handler convex/httpApiV1/packagesV1.ts:2615— FunctionTooLong — packagesPostRouterV1Handler runs 516 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 416 over it, 5.16× 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: packagesV1.packagesGetRouterV1Handler convex/httpApiV1/packagesV1.ts:3777— FunctionTooLong — packagesGetRouterV1Handler runs 505 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 405 over it, 5.05× 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: SkillDiffCard.SkillDiffCard src/components/SkillDiffCard.tsx:147— FunctionTooLong — SkillDiffCard runs 460 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 360 over it, 4.60× 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: HomeListingSection.HomeListingSection src/components/HomeListingSection.tsx:218— FunctionTooLong — HomeListingSection runs 450 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 350 over it, 4.50× 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: $handle.PublisherProfilePage src/routes/user/$handle.tsx:483— FunctionTooLong — PublisherProfilePage runs 444 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 344 over it, 4.44× 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: skillsShCatalogV1.skillsShCatalogTestV1Handler convex/httpApiV1/skillsShCatalogV1.ts:619— FunctionTooLong — skillsShCatalogTestV1Handler runs 402 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 302 over it, 4.02× 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: -useSkillsBrowseModel.useSkillsBrowseModel src/routes/skills/-useSkillsBrowseModel.ts:105— FunctionTooLong — useSkillsBrowseModel runs 393 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 293 over it, 3.93× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: skillsV1.exportSkillsV1Handler convex/httpApiV1/skillsV1.ts:3531— FunctionTooLong — exportSkillsV1Handler runs 386 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 286 over it, 3.86× 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: skillsV1.skillsPostRouterV1Handler convex/httpApiV1/skillsV1.ts:2926— FunctionTooLong — skillsPostRouterV1Handler runs 359 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 259 over it, 3.59× 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: SearchInsightsPage.SearchInsightsPage src/routes/-management/SearchInsightsPage.tsx:17— FunctionTooLong — SearchInsightsPage runs 358 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 258 over it, 3.58× 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: PluginVersionsPanel.PluginVersionsPanel src/components/PluginVersionsPanel.tsx:55— FunctionTooLong — PluginVersionsPanel runs 320 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 220 over it, 3.20× 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: SkillsPage.SkillsPage src/routes/-management/SkillsPage.tsx:30— FunctionTooLong — SkillsPage runs 316 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 216 over it, 3.16× 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: SkillDetailTabs.SkillDetailTabs src/components/SkillDetailTabs.tsx:74— FunctionTooLong — SkillDetailTabs runs 307 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 207 over it, 3.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Hotspot: convex/packages.ts convex/packages.ts:8052— convex/packages.ts changed 101 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 138 in packages.publishPackageImpl at line 8052. 46 of those changes were fix/bug commits, and the other 55 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/packages.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: convex/httpApiV1/packagesV1.ts convex/httpApiV1/packagesV1.ts:2615— convex/httpApiV1/packagesV1.ts changed 50 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 167 in packagesV1.packagesPostRouterV1Handler at line 2615. 22 of those changes were fix/bug commits, and the other 28 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/httpApiV1/packagesV1.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: convex/httpApiV1/skillsV1.ts convex/httpApiV1/skillsV1.ts:1761— convex/httpApiV1/skillsV1.ts changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 157 in skillsV1.skillsGetRouterV1Handler at line 1761. 15 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/httpApiV1/skillsV1.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/SkillDetailPage.tsx src/components/SkillDetailPage.tsx:184— src/components/SkillDetailPage.tsx changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 198 in SkillDetailPage.SkillDetailPage at line 184. 9 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/components/SkillDetailPage.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: convex/skills.ts convex/skills.ts:11462— convex/skills.ts changed 53 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in skills.setSkillSoftDeletedByActor at line 11462. 19 of those changes were fix/bug commits, and the other 34 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/skills.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/routes/plugins/$name.tsx src/routes/plugins/$name.tsx:1048— src/routes/plugins/$name.tsx changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 133 in $name.PluginDetailPageContent at line 1048. 7 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/routes/plugins/$name.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/security/run-codex-scan-worker.ts scripts/security/run-codex-scan-worker.ts:2135— scripts/security/run-codex-scan-worker.ts changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 48 in run-codex-scan-worker.validateClawScanArtifactForClawHubProfile at line 2135. 15 of those changes were fix/bug commits, and the other 16 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- scripts/security/run-codex-scan-worker.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/HomeListingSection.tsx src/components/HomeListingSection.tsx:218— src/components/HomeListingSection.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 116 in HomeListingSection.HomeListingSection at line 218. 4 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/components/HomeListingSection.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/clawhub/src/cli/commands/packages.ts packages/clawhub/src/cli/commands/packages.ts:2646— packages/clawhub/src/cli/commands/packages.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 70 in packages.preparePackagePublishPlan at line 2646. 7 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- packages/clawhub/src/cli/commands/packages.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/Header.tsx src/components/Header.tsx:132— src/components/Header.tsx changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 93 in Header.Header at line 132. 5 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/components/Header.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/clawhub/src/cli/commands/skills.ts packages/clawhub/src/cli/commands/skills.ts:629— packages/clawhub/src/cli/commands/skills.ts changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 124 in skills.cmdUpdate at line 629. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- packages/clawhub/src/cli/commands/skills.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/routes/skills/publish.tsx src/routes/skills/publish.tsx:90— src/routes/skills/publish.tsx changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 214 in publish.Upload at line 90. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/routes/skills/publish.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/security/run-prepublication-worker.ts scripts/security/run-prepublication-worker.ts:653— scripts/security/run-prepublication-worker.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in run-prepublication-worker.runNativeClawScan at line 653. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- scripts/security/run-prepublication-worker.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: convex/lib/skillPublish.ts convex/lib/skillPublish.ts:160— convex/lib/skillPublish.ts changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 66 in skillPublish.publishVersionForUser at line 160. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/lib/skillPublish.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/components/SkillDetailPageView.tsx src/components/SkillDetailPageView.tsx:193— src/components/SkillDetailPageView.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 93 in SkillDetailPageView.SkillDetailPageView at line 193. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/components/SkillDetailPageView.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/routes/user/$handle.tsx src/routes/user/$handle.tsx:483— src/routes/user/$handle.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 74 in $handle.PublisherProfilePage at line 483. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/routes/user/$handle.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/lib/packageApi.ts src/lib/packageApi.ts:370— src/lib/packageApi.ts changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in packageApi.fetchPluginCatalog at line 370. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/lib/packageApi.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/schema/src/templates.ts packages/schema/src/templates.ts:484— packages/schema/src/templates.ts changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 79 in templates.validateTemplateManifest at line 484. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- packages/schema/src/templates.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: convex/devSeed.ts convex/devSeed.ts:2934— convex/devSeed.ts changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in devSeed.seedLocalModerationFixturesHandler at line 2934. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/devSeed.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/routes/management.tsx src/routes/management.tsx:226— src/routes/management.tsx changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 102 in management.Management at line 226. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/routes/management.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/routes/plugins/publish.tsx src/routes/plugins/publish.tsx:173— src/routes/plugins/publish.tsx changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 151 in publish.PublishPluginRoute at line 173. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/routes/plugins/publish.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: convex/githubSkillSync.ts convex/githubSkillSync.ts:2209— convex/githubSkillSync.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in githubSkillSync.applyGitHubSkillVerificationResultHandler at line 2209. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/githubSkillSync.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: src/routes/plugins/index.tsx src/routes/plugins/index.tsx:340— src/routes/plugins/index.tsx changed 10 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in index.PluginsIndex at line 340. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/routes/plugins/index.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: packages/clawhub-admin/src/commands/searchInsights.ts packages/clawhub-admin/src/commands/searchInsights.ts:17— packages/clawhub-admin/src/commands/searchInsights.ts changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 69 in searchInsights.cmdSearchInsights at line 17. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- packages/clawhub-admin/src/commands/searchInsights.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: scripts/security/run-clawscan-diagnostic.ts scripts/security/run-clawscan-diagnostic.ts:334— scripts/security/run-clawscan-diagnostic.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in run-clawscan-diagnostic.main at line 334. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- scripts/security/run-clawscan-diagnostic.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FileTooLong: convex/packages.ts convex/packages.ts— FileTooLong — 9553 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 9053 over it, 19.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/skills.ts convex/skills.ts— FileTooLong — 8792 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 8292 over it, 17.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/devSeed.ts convex/devSeed.ts— FileTooLong — 4221 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3721 over it, 8.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: httpApiV1/packagesV1.ts convex/httpApiV1/packagesV1.ts— FileTooLong — 3593 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 3093 over it, 7.19× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/publishers.ts convex/publishers.ts— FileTooLong — 3320 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2820 over it, 6.64× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: httpApiV1/skillsV1.ts convex/httpApiV1/skillsV1.ts— FileTooLong — 3205 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2705 over it, 6.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/securityScan.ts convex/securityScan.ts— FileTooLong — 3170 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2670 over it, 6.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/maintenance.ts convex/maintenance.ts— FileTooLong — 3044 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2544 over it, 6.09× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/githubSkillSync.ts convex/githubSkillSync.ts— FileTooLong — 2685 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2185 over it, 5.37× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: routes/settings.tsx src/routes/settings.tsx— FileTooLong — 2669 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2169 over it, 5.34× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/publisherAbuse.ts convex/publisherAbuse.ts— FileTooLong — 2481 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1981 over it, 4.96× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/skillsShCatalog.ts convex/skillsShCatalog.ts— FileTooLong — 2452 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1952 over it, 4.90× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: commands/packages.ts packages/clawhub/src/cli/commands/packages.ts— FileTooLong — 2360 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1860 over it, 4.72× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: server/skillsShCatalogSource.ts server/skillsShCatalogSource.ts— FileTooLong — 2311 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1811 over it, 4.62× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/users.ts convex/users.ts— FileTooLong — 2072 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1572 over it, 4.14× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/skillsShMirror.ts convex/skillsShMirror.ts— FileTooLong — 1915 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1415 over it, 3.83× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: lib/catalogClassifier.mjs convex/lib/catalogClassifier.mjs— FileTooLong — 1794 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 1294 over it, 3.59× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/search.ts convex/search.ts— FileTooLong — 1692 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1192 over it, 3.38× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: plugins/$name.tsx src/routes/plugins/$name.tsx— FileTooLong — 1632 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1132 over it, 3.26× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: -management/AbusePage.tsx src/routes/-management/AbusePage.tsx— FileTooLong — 1587 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1087 over it, 3.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/publishAttempts.ts convex/publishAttempts.ts— FileTooLong — 1452 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 952 over it, 2.90× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: convex/migrations.ts convex/migrations.ts— FileTooLong — 1418 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 918 over it, 2.84× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: routes/import.tsx src/routes/import.tsx— FileTooLong — 1409 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 909 over it, 2.82× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: commands/skills.ts packages/clawhub/src/cli/commands/skills.ts— FileTooLong — 1352 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 852 over it, 2.70× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: skills/publish.tsx src/routes/skills/publish.tsx— FileTooLong — 1205 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: Upload (90-1368). The bar is 500 significant lines; this is 705 over it, 2.41× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Boundary violation [package:relative-cross-package] convex/httpApiV1/searchReportsV1.ts:3— convex/httpApiV1/searchReportsV1.ts:3 reaches into another package with a relative path (../../packages/clawhub/src/schema/searchReports) — import the package by name instead.
Boundary violation [package:relative-cross-package] convex/lib/clawpack.ts:3— convex/lib/clawpack.ts:3 reaches into another package with a relative path (../../packages/clawhub/src/clawpack) — import the package by name instead.
Boundary violation [package:relative-cross-package] convex/searchReports.ts:3— convex/searchReports.ts:3 reaches into another package with a relative path (../packages/clawhub/src/schema/searchReports) — import the package by name instead.
Boundary violation [package:test-cross-package-internals] e2e/local-auth/publish-skill-lifecycle.pw.test.ts:9— e2e/local-auth/publish-skill-lifecycle.pw.test.ts:9 reaches past another workspace package's public entry into its internals with a relative path (../../packages/schema/src/ark) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:test-cross-package-internals] e2e/local-auth/publish-skill-lifecycle.pw.test.ts:10— e2e/local-auth/publish-skill-lifecycle.pw.test.ts:10 reaches past another workspace package's public entry into its internals with a relative path (../../packages/schema/src/schemas) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/scripts/build.mjs:1— packages/clawhub-admin/scripts/build.mjs:1 reaches into another package with a relative path (../../clawhub/scripts/shared-schema.mjs) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/buildInfo.ts:4— packages/clawhub-admin/src/buildInfo.ts:4 reaches into another package with a relative path (../../clawhub/src/cli/buildInfo.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/cli.ts:5— packages/clawhub-admin/src/cli.ts:5 reaches into another package with a relative path (../../clawhub/src/cli/commands/auth.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/cli.ts:6— packages/clawhub-admin/src/cli.ts:6 reaches into another package with a relative path (../../clawhub/src/cli/commands/delete.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/cli.ts:7— packages/clawhub-admin/src/cli.ts:7 reaches into another package with a relative path (../../clawhub/src/cli/commands/packages.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/cli.ts:12— packages/clawhub-admin/src/cli.ts:12 reaches into another package with a relative path (../../clawhub/src/cli/commands/skills.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/cli.ts:16— packages/clawhub-admin/src/cli.ts:16 reaches into another package with a relative path (../../clawhub/src/cli/globalOpts.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/cli.ts:20— packages/clawhub-admin/src/cli.ts:20 reaches into another package with a relative path (../../clawhub/src/cli/helpStyle.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/cli.ts:25— packages/clawhub-admin/src/cli.ts:25 reaches into another package with a relative path (../../clawhub/src/cli/types.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/cli.ts:26— packages/clawhub-admin/src/cli.ts:26 reaches into another package with a relative path (../../clawhub/src/cli/ui.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/contentRights.ts:3— packages/clawhub-admin/src/commands/contentRights.ts:3 reaches into another package with a relative path (../../../clawhub/src/cli/authToken.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/contentRights.ts:4— packages/clawhub-admin/src/commands/contentRights.ts:4 reaches into another package with a relative path (../../../clawhub/src/cli/registry.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/contentRights.ts:5— packages/clawhub-admin/src/commands/contentRights.ts:5 reaches into another package with a relative path (../../../clawhub/src/cli/types.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/contentRights.ts:6— packages/clawhub-admin/src/commands/contentRights.ts:6 reaches into another package with a relative path (../../../clawhub/src/cli/ui.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/contentRights.ts:7— packages/clawhub-admin/src/commands/contentRights.ts:7 reaches into another package with a relative path (../../../clawhub/src/http.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/contentRights.ts:8— packages/clawhub-admin/src/commands/contentRights.ts:8 reaches into another package with a relative path (../../../clawhub/src/schema/index.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/downloads.ts:1— packages/clawhub-admin/src/commands/downloads.ts:1 reaches into another package with a relative path (../../../clawhub/src/cli/authToken.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/downloads.ts:2— packages/clawhub-admin/src/commands/downloads.ts:2 reaches into another package with a relative path (../../../clawhub/src/cli/registry.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/downloads.ts:3— packages/clawhub-admin/src/commands/downloads.ts:3 reaches into another package with a relative path (../../../clawhub/src/cli/types.js) — import the package by name instead.
Boundary violation [package:relative-cross-package] packages/clawhub-admin/src/commands/downloads.ts:4— packages/clawhub-admin/src/commands/downloads.ts:4 reaches into another package with a relative path (../../../clawhub/src/http.js) — import the package by name instead.
Swallowed exception (empty catch) vitest.setup.ts:101— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/routes/plugins/publish.tsx:490— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) src/routes/-management/ManagedMcpTools.tsx:53— `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) src/lib/analyticsRelease.ts:9— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/lib/templateDetail.ts:80— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/lib/theme.ts:83— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/lib/theme.ts:164— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/lib/theme.ts:183— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/lib/useUnifiedSearch.ts:408— `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) src/lib/useUnifiedSearch.ts:422— `.then(…, () => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) src/components/skillDetailUtils.ts:23— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:301— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) src/components/PluginVersionsPanel.tsx:180— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/components/PluginVersionsPanel.tsx:215— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/components/PromotionsBar.tsx:122— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) src/components/UserBadge.tsx:187— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) src/components/UserBootstrap.tsx:14— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) server/convexProxy.ts:279— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) server/skillsShCatalogSource.ts:711— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) server/skillsShCatalogSource.ts:1770— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) server/og/ogAssets.ts:43— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/clawhub-admin/src/buildInfo.ts:28— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/clawhub/src/http.ts:379— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/clawhub/src/publishFiles.ts:18— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/clawhub/src/skills.ts:165— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Sync-over-async blocking convex/agentSkillsHttp.ts:358— `unzipSync` in `buildArchive` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking convex/lib/openClawPublishAuthorization.ts:672— `unzipSync` in `fetchArtifactReceipt` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking convex/securityDatasetNode.ts:91— `gzipSync` in `listArtifactExportBatchCompressedForWorker` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/clawhub/scripts/shared-schema.mjs:63— `spawnSync` in `buildCliPackage` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/clawhub/src/cli/commands/github.ts:112— `unzipSync` in `fetchGitHubSource` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/clawhub/src/skills.ts:50— `unzipSync` in `extractZipToDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/clawhub/src/skills.ts:66— `unzipSync` in `extractGitHubZipPathToDir` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/evaluations/skill-evaluation-runtime.ts:261— `rmSync` in `materializeNvidiaSkillsSnapshot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/package-inspector-nightly-scan.ts:824— `existsSync` in `prepareExtractedPluginRoot` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/package-inspector-nightly-scan.ts:934— `existsSync` in `writeSyntheticConfigIfNeeded` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/package-inspector-nightly-scan.ts:935— `existsSync` in `writeSyntheticConfigIfNeeded` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/package-inspector-nightly-scan.ts:967— `existsSync` in `readJsonIfExists` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/run-playwright-local-auth.ts:317— `rmSync` in `cleanupOwnedResources` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/run-playwright-local-auth.ts:335— `readFileSync` in `readFile` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/run-playwright-local-auth.ts:347— `mkdirSync` in `warmLocalAuthExternalNodeDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/run-playwright-local-auth.ts:348— `writeFileSync` in `warmLocalAuthExternalNodeDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/run-playwright-local-auth.ts:429— `rmSync` in `startLocalConvex` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/run-playwright-local-auth.ts:532— `existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/run-playwright-local-auth.ts:588— `writeFileSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/seed.ts:100— `spawnSync` in `runStep` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/seed.ts:110— `spawnSync` in `runStep` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/staging-seed/import-test-snapshot.ts:44— `spawnSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking scripts/templates-feed-openclaw-e2e.ts:102— `unzipSync` in `extractSafeTemplateZip` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/lib/uploadFiles.ts:14— `unzipSync` in `expandFilesWithReport` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking src/lib/uploadFiles.ts:23— `gunzipSync` in `expandFilesWithReport` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
+ 1 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×25
No test reaches this file src/routes/audits.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/add.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/$owner/plugins/$slug/security-audit.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/clawhub/scripts/shared-schema.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/$owner/plugins/$slug.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/server.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/$owner/$slug/settings.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/plugins/$scope/$name/security-audit.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/$owner/skills/$slug/settings.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/router.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/packages/new.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/$owner/plugins/$slug/security/$scanner.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/clawhub-admin/scripts/typecheck.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/$owner/$slug/security/$scanner.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/$owner/skills/$slug/security/$scanner.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/admin.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/plugins/$name/security/$scanner.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/packages/$name.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/packages/index.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/plugins/new.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/publish-plugin.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/publish-skill.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file src/routes/upload.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/clawhub-admin/scripts/build.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/clawhub/scripts/build.mjs:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
Skipped test: (unnamed test) e2e/mobile-skills.pw.test.ts:13— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/skills-sh-external.pw.test.ts:6— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/upload-auth-smoke.pw.test.ts:22— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/upload-auth-smoke.pw.test.ts:44— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/delete-account-resources.pw.test.ts:11— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/delete-org-resources.pw.test.ts:11— Skipped — switched off by test.skip
Skipped test: (unnamed test) REDACTED:12— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/featured-lineup.pw.test.ts:7— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/header-profile-link.pw.test.ts:6— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/malicious-skill-ban-flow.pw.test.ts:16— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/manage-context-proof.pw.test.ts:13— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/old-cli-publish-compat.pw.test.ts:14— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/package-ssr-identity.pw.test.ts:7— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/plugin-api-retirements.pw.test.ts:8— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/plugin-catalog-api.pw.test.ts:9— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/plugin-inspector-findings.pw.test.ts:22— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/publish-skill-lifecycle.pw.test.ts:32— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/publisher-create-owner.pw.test.ts:9— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/publisher-github-profile.pw.test.ts:5— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/skill-hero-metadata.pw.test.ts:7— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/skill-presentation-metadata.pw.test.ts:7— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/skill-star-sync.pw.test.ts:17— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/template-official-boundary.pw.test.ts:9— Skipped — switched off by test.skip
Skipped test: (unnamed test) e2e/local-auth/version-delete.pw.test.ts:14— Skipped — switched off by test.skip
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×15
Focus outline removed in CSS without a :focus replacement src/publisher-profile.css:338— `.publisher-profile-bio-toggle:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/publisher-profile.css:360— `.publisher-profile-chrome-more-trigger:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/publisher-profile.css:589— `.publisher-profile-members-menu-list [data-slot="dropdown-menu-item"][data-highlighted]` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:431— `.catalog-topic-input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:1172— `.user-dropdown-content [data-slot="dropdown-menu-item"]:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:1638— `.skillspector-checks-toggle:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:5750— `.detail-inline-tab:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:9972— `.search-input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:10425— `.markdown-code-block-action:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:11310— `.pa-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:12179— `.management-search input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:14103— `.browse-topic-chip.is-active` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:17685— `a.home-v2-apps-see-all:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:18399— `a.home-v2-byos-import:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement src/styles.css:20092— `.dashboard-publisher-select-item:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Repeated repair: convex/publishAttempts.ts convex/publishAttempts.ts:135— convex/publishAttempts.ts changed 26 times in last 90 days and 16 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 12 (its worst body is publishAttempts.isTerminalFinalizationConflict at line 135), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: retry publication promptly after finalization failure”; “fix: resume targeted expired publication finalization (#4468)”; “fix: bind operational retries to reviewed scanner source (#4239)”; “fix: bound storage lookups during scan handoff (#4231)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/publishAttempts.ts`: 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.
Repeated repair: convex/skillEvaluations.ts convex/skillEvaluations.ts:115— convex/skillEvaluations.ts changed 12 times in last 90 days and 9 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is skillEvaluations.resolveEvaluationSkill at line 115), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: show latest completed skill evaluation across recipes (#4093)”; “fix: restore NVIDIA evaluations and upgrade SkillEvaluator (#3956)”; “fix: unauthenticated mutation can requeue NVIDIA skill evaluations (#3762)”; “fix(workers): terminalize skill evaluation outcomes (#3509)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/skillEvaluations.ts`: 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.
Repeated repair: scripts/run-playwright-local-auth.ts scripts/run-playwright-local-auth.ts:528— scripts/run-playwright-local-auth.ts changed 10 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is run-playwright-local-auth.main at line 528), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ci): stabilize local-auth backend downloads (#4489)”; “fix: large plugin publishes run out of memory in the Plugin Inspector gate (#3990)”; “fix(security): require pre-publication checks for every publish (#3947)”; “fix(workers): preserve explicit scanner model settings (#3802)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- scripts/run-playwright-local-auth.ts`: 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.
Repeated repair: src/components/PluginListItem.tsx src/components/PluginListItem.tsx:49— src/components/PluginListItem.tsx changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is PluginListItem.PluginListItem at line 49), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(profile): templates appear in the Plugins tab on publisher profiles (#4792)”; “fix: render inline Markdown in headers and plugin previews (#3832)”; “fix: use publisher avatars for plugins without bundled icons (#3705)”; “fix(plugins): show official publisher badges in catalog results (#3654)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/components/PluginListItem.tsx`: 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.
Repeated repair: scripts/playwright-local-auth-config.ts scripts/playwright-local-auth-config.ts:143— scripts/playwright-local-auth-config.ts changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is playwright-local-auth-config.createLocalAuthTempDir at line 143), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(ci): stabilize local-auth backend downloads (#4489)”; “fix(packages): reclaim unadopted multipart uploads”; “fix: local browser tests fail with deeply nested TMPDIR (#3739)”; “fix(ci): stop local-auth lanes racing the Convex external-deps build (#3598)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- scripts/playwright-local-auth-config.ts`: 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.
Repeated repair: src/routes/skills/index.tsx src/routes/skills/index.tsx:188— src/routes/skills/index.tsx changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is index.SkillsIndex at line 188), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(catalog): isolate optional count failures (#4312)”; “fix(search): preserve navigation cancellation (#4300)”; “fix: simplify skill and plugin catalogs to searchable lists (#3843)”; “fix: align catalog tabs and featured skill rows (#3829)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/routes/skills/index.tsx`: 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.
Repeated repair: REDACTED REDACTED:179— REDACTED changed 7 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is run-skill-evaluation-worker.processClaimedEvaluation at line 179), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(evaluations): expose redacted failure reasons in worker logs (#3987)”; “fix: size evaluation request budgets for paired workloads (#3985)”; “fix: keep sixteen evaluation workers draining the backlog (#3976)”; “fix: restore NVIDIA evaluations and upgrade SkillEvaluator (#3956)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: src/routes/skills/-SkillsResults.tsx src/routes/skills/-SkillsResults.tsx:125— src/routes/skills/-SkillsResults.tsx changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is -SkillsResults.SkillsResults at line 125), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: simplify skill and plugin catalogs to searchable lists (#3843)”; “fix: align catalog tabs and featured skill rows (#3829)”; “fix: surface a retryable error when the skills catalog fails to load (#3512)”; “fix: simplify plugin list columns (#3572)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- src/routes/skills/-SkillsResults.tsx`: 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.
Repeated repair: convex/canonicalTrending.ts convex/canonicalTrending.ts:75— convex/canonicalTrending.ts changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is canonicalTrending.pruneExpiredRows at line 75), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: skills.sh entries missing from Trending because the sync rejects the 93k-row feed (#3952)”; “fix: exclude non-Latin skill titles from Trending (#3715)”; “fix: show only English skill listings in Trending (#3713)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/canonicalTrending.ts`: 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.
Repeated repair: convex/lib/canonicalTrending.ts convex/lib/canonicalTrending.ts:414— convex/lib/canonicalTrending.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 15 (its worst body is canonicalTrending.blendCanonicalTrendingPools at line 414), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: skills.sh entries missing from Trending because the sync rejects the 93k-row feed (#3952)”; “fix: exclude non-Latin skill titles from Trending (#3715)”; “fix: show only English skill listings in Trending (#3713)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 17:29:26 +08:00' --until='2026-11-16 17:29:26 +08:00' --full-history --no-merges -- convex/lib/canonicalTrending.ts`: 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×8
Async function without AbortSignal: getLocalDevAuthSecret src/components/DevPersonaFab.tsx:87— `getLocalDevAuthSecret` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: loadPromotions src/components/PromotionsBar.tsx:142— `loadPromotions` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: requestDeviceCode packages/clawhub/src/deviceAuth.ts:49— `requestDeviceCode` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: sendResendEmail convex/packages.ts:10638— `sendResendEmail` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler convex/webhooks.ts:18— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchGitHubUserByNumericId convex/lib/githubAccount.ts:26— `fetchGitHubUserByNumericId` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: generateSkillSummary convex/lib/skillSummary.ts:66— `generateSkillSummary` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: fetchAuthenticatedGitHubOwners convex/httpApiV1/skillsShCatalogV1.ts:336— `fetchAuthenticatedGitHubOwners` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
ClassTooLong: AbusePage src/routes/-management/AbusePage.tsx:1— ClassTooLong — 726 significant lines (blank, comment-only and punctuation-only lines excluded), 35 methods. The bar is 400 significant lines; this is 326 over it, 1.82× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SkillDetailPage src/components/SkillDetailPage.tsx:1— ClassTooLong — 723 significant lines (blank, comment-only and punctuation-only lines excluded), 4 methods. The bar is 400 significant lines; this is 323 over it, 1.81× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Header src/components/Header.tsx:1— ClassTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded), 12 methods. The bar is 400 significant lines; this is 227 over it, 1.57× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SkillDetailPageView src/components/SkillDetailPageView.tsx:1— ClassTooLong — 525 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 125 over it, 1.31× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SkillDiffCard src/components/SkillDiffCard.tsx:1— ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 60 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HomeListingSection src/components/HomeListingSection.tsx:1— ClassTooLong — 450 significant lines (blank, comment-only and punctuation-only lines excluded), 5 methods. The bar is 400 significant lines; this is 50 over it, 1.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Swallowed exception (caught, then discarded) src/lib/publicApiUrl.ts:13— `catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) src/components/GoogleAnalytics.tsx:206— `catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) src/components/SecurityAuditPage.tsx:990— `catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/schema/src/catalogMetadata.ts:590— `catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) packages/clawhub/src/cli/commands/skills.ts:190— `catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Swallowed exception (caught, then discarded) convex/devSeed.ts:2016— `catch` 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, or keep only the failure you expect and rethrow the rest (`catch (e) { if (!(e instanceof SyntaxError)) throw e; … }`, or test `e.name`), because a JavaScript catch takes every exception, programming errors included.
Change coupling: httpRateLimit.ts ↔ rateLimits.ts convex/lib/httpRateLimit.ts:1— `convex/lib/httpRateLimit.ts` and `convex/rateLimits.ts` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `67f1334c` feat: add an off switch for rate-limiter storage (#4207); `5aba188c` fix: batch high-volume HTTP quota writes (#4198); `d3a009db` perf: add guarded rate-limit RPC comparison (#4160) — run `git show` on any of them.
Change coupling: SkillCard.tsx ↔ SkillListItem.tsx src/components/SkillCard.tsx:1— `src/components/SkillCard.tsx` and `src/components/SkillListItem.tsx` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `2f428b4e` fix: align discovery icons by content type and viewport (#3427); `eb3050fd` fix(ui): restore official terminology; `29b887ce` fix(web): preserve long catalog names (#2962) — run `git show` on any of them.
Change coupling: crons.ts ↔ telemetry.ts convex/crons.ts:1— `convex/crons.ts` and `convex/telemetry.ts` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `b1b3c5e1` feat: enforce Convex retention policy; `2c1b331b` Rank skills by installs and harden install telemetry; `e8a75de2` refactor: remove root install telemetry (#2673) — run `git show` on any of them.
Change coupling: publishers.ts ↔ publicUser.ts convex/publishers.ts:1— `convex/publishers.ts` and `src/lib/publicUser.ts` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `a6b209b5` fix(profile): templates appear in the Plugins tab on publisher profil…; `38566969` fix: show bundled plugin icons in the catalog (#3660); `af3d01c6` feat: verify organization GitHub profiles (#3169) — run `git show` on any of them.
Change coupling: SkillDetailPage.tsx ↔ UserBadge.tsx src/components/SkillDetailPage.tsx:1— `src/components/SkillDetailPage.tsx` and `src/components/UserBadge.tsx` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `0fb07e5b` feat: align skills.sh catalog presentation (#3370); `be4c51ed` fix: improve auth flow and webkit compatibility (#1555); `f4db0ee3` fix: improve auth flow and webkit compatibility (#1555) — run `git show` on any of them.
Duplicated block (36 lines × 2 locations) convex/publishAttempts.ts:779— convex/publishAttempts.ts:779 · convex/publishAttempts.ts:888 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (36 lines × 2 locations) convex/securityScan.ts:304— convex/securityScan.ts:304 · scripts/security/run-codex-scan-worker.ts:1101 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (36 lines × 2 locations) convex/securityScan.ts:1941— convex/securityScan.ts:1941 · convex/securityScan.ts:1995 — 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 (36 lines × 2 locations) packages/clawhub/src/cli/commands/star.ts:10— packages/clawhub/src/cli/commands/star.ts:10 · packages/clawhub/src/cli/commands/unstar.ts:10 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
Duplicated block (36 lines × 2 locations) packages/clawhub/src/schema/packages.ts:125— packages/clawhub/src/schema/packages.ts:125 · packages/schema/src/packages.ts:211 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×4
Markup wires an event to an empty handler src/routes/plugins/index.tsx:313— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/routes/plugins/index.tsx:314— `onClear` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/routes/plugins/index.tsx:320— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler src/routes/plugins/index.tsx:329— `onChange` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
R10 · Code Duplication· Duplicated block with local edits (36 matched lines × 2 locations) · ×3
Duplicated block with local edits (36 matched lines × 2 locations) convex/pluginInspectorDispatch.ts:54— convex/pluginInspectorDispatch.ts:54 · convex/publishAttemptDispatch.ts:89 — the two spans are one implementation copied and then locally edited — 302 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (36 matched lines × 2 locations) convex/skillsShMirror.ts:1432— convex/skillsShMirror.ts:1432 · convex/skillsShMirror.ts:1730 — the two spans are one implementation copied and then locally edited — 200 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (36 matched lines × 2 locations) src/components/ui/dialog.tsx:75— src/components/ui/dialog.tsx:75 · src/components/ui/sheet.tsx:64 — the two spans are one implementation copied and then locally edited — 245 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Dead file (~1 LoC) server/routes/og/plugin.ts— no import path from any entry point (341 application, 81 tooling, 828 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~1 LoC) server/routes/og/profile.ts— no import path from any entry point (341 application, 81 tooling, 828 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~1 LoC) server/routes/og/skill.ts— no import path from any entry point (341 application, 81 tooling, 828 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Focus outline removed inline src/components/ui/input.tsx:6— <input> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
Focus outline removed inline src/components/ui/textarea.tsx:8— <textarea> takes keyboard focus, and its outline-none utility removes the focus ring with no focus-state ring, shadow, border or outline utility in its place. Add one (e.g. focus-visible:ring-2).
IC1 · Incompleteness & stubs· Guard cannot change the result · ×2
Guard cannot change the result — returns what the code already falls through to packages/clawhub/src/cli.ts:158— The guard above `return undefined;` also returns `undefined`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Guard cannot change the result — returns what the code already falls through to src/routes/skills/publish.tsx:575— The guard above `return false;` also returns `false`, so no input can make it matter. Implement the distinction that was intended, or delete the guard.
Duplication concentrated across 3 sibling directories (26 clone groups) packages/clawhub/src/schema/schemas.ts:228— 26 duplicated blocks under packages/ have copies in at least two of the sibling directories clawhub, clawhub-admin, schema — 19 of them are reported below, and 7 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (26 clone groups) src/components/SkillDetailPageView.tsx:518— 26 duplicated blocks under src/ have copies in at least two of the sibling directories components, lib, routes — 14 of them are reported below, and 12 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 26 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 26 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 26 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplicated block (39 lines × 2 locations) convex/publishAttempts.ts:1183— convex/publishAttempts.ts:1183 · convex/publishAttempts.ts:1227 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (39 lines × 2 locations) convex/skillTransfers.ts:369— convex/skillTransfers.ts:369 · convex/skillTransfers.ts:414 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
AC2 · Forms & labels· <Textarea> field component without a label · ×1
<Textarea> field component without a label src/routes/-management/AbusePage.tsx:755— This UI-library field component is named only by a placeholder — a placeholder is not a label (it vanishes as soon as the user types, and many assistive technologies ignore it). Give it a real name whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC2 · Forms & labels· <fieldset> without a <legend> · ×1
<fieldset> without a <legend> src/routes/-management/ManagedMcpTools.tsx:329— A fieldset groups related controls but has no <legend> to name the group. Add a <legend> as its first child — or, if the group already has a visible caption beside it (or the fieldset is there only to disable its subtree and carries no group box), point aria-labelledby at that caption's id instead, which names the group without rendering a second one.
AC2 · Forms & labels· <Select> field component without a label · ×1
<Select> field component without a label src/routes/-management/UsersPage.tsx:77— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Heading level jumps from h2 to h4 · ×1
Heading level jumps from h2 to h4 src/routes/plugins/$name.tsx:1451— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC3 · Page structure· Heading level jumps from h1 to h3 · ×1
Heading level jumps from h1 to h3 src/routes/settings.tsx:983— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×1
Modal dialog does not manage focus src/components/dashboard/DashboardNeedsAttention.tsx:198— This <aside role="dialog"> is a modal dialog, but nothing moves focus into it when it opens and nothing keeps focus inside it while it is open, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
SkillDetailPage.SkillDetailPage (cyclomatic 198) src/components/SkillDetailPage.tsx:184— SkillDetailPage.SkillDetailPage has cyclomatic complexity 198 (threshold 15). Of this number, 131 points are the body's own statements and 67 belong to 28 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
packagesV1.packagesPostRouterV1Handler (cyclomatic 167) convex/httpApiV1/packagesV1.ts:2615— packagesV1.packagesPostRouterV1Handler has cyclomatic complexity 167 (threshold 15). Of this number, 166 points are the body's own statements and 1 belongs 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.
settings.Settings (cyclomatic 162) src/routes/settings.tsx:276— settings.Settings has cyclomatic complexity 162 (threshold 15). Of this number, 89 points are the body's own statements and 73 belong to 32 function items 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.
skillsV1.skillsGetRouterV1Handler (cyclomatic 157) convex/httpApiV1/skillsV1.ts:1761— skillsV1.skillsGetRouterV1Handler has cyclomatic complexity 157 (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.
publish.PublishPluginRoute (cyclomatic 151) src/routes/plugins/publish.tsx:173— publish.PublishPluginRoute has cyclomatic complexity 151 (threshold 15). Of this number, 75 points are the body's own statements and 76 belong to 14 function items 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.
AbusePage.AbusePage (cyclomatic 142) src/routes/-management/AbusePage.tsx:47— AbusePage.AbusePage has cyclomatic complexity 142 (threshold 15). Of this number, 129 points are the body's own statements and 13 belong to 5 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.
skillsV1.skillsPostRouterV1Handler (cyclomatic 141) convex/httpApiV1/skillsV1.ts:2926— skillsV1.skillsPostRouterV1Handler has cyclomatic complexity 141 (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.
packages.publishPackageImpl (cyclomatic 138) convex/packages.ts:8052— packages.publishPackageImpl has cyclomatic complexity 138 (threshold 15). Of this number, 126 points are the body's own statements and 12 belong to 5 function items 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.
$name.PluginDetailPageContent (cyclomatic 133) src/routes/plugins/$name.tsx:1048— $name.PluginDetailPageContent has cyclomatic complexity 133 (threshold 15). Of this number, 122 points are the body's own statements and 11 belong to 8 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.
packagesV1.packagesGetRouterV1Handler (cyclomatic 132) convex/httpApiV1/packagesV1.ts:3777— packagesV1.packagesGetRouterV1Handler has cyclomatic complexity 132 (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.
packagesV1.listPackages (cyclomatic 125) convex/httpApiV1/packagesV1.ts:1159— packagesV1.listPackages has cyclomatic complexity 125 (threshold 15). Of this number, 121 points are the body's own statements and 4 belong to 4 function items 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.
skills.cmdUpdate (cyclomatic 124) packages/clawhub/src/cli/commands/skills.ts:629— skills.cmdUpdate has cyclomatic complexity 124 (threshold 15). Of this number, 118 points are the body's own statements and 6 belong to 4 function items 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.
HomeListingSection.HomeListingSection (cyclomatic 116) src/components/HomeListingSection.tsx:218— HomeListingSection.HomeListingSection has cyclomatic complexity 116 (threshold 15). Of this number, 49 points are the body's own statements and 67 belong to 23 function items 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.
import.ImportGitHub (cyclomatic 114) src/routes/import.tsx:185— import.ImportGitHub has cyclomatic complexity 114 (threshold 15). Of this number, 53 points are the body's own statements and 61 belong to 20 function items 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.
packages.listPackagePageImpl (cyclomatic 109) convex/packages.ts:3946— packages.listPackagePageImpl has cyclomatic complexity 109 (threshold 15). Of this number, 98 points are the body's own statements and 11 belong to 2 function items 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.
management.Management (cyclomatic 102) src/routes/management.tsx:226— management.Management has cyclomatic complexity 102 (threshold 15). Of this number, 70 points are the body's own statements and 32 belong to 21 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Header.Header (cyclomatic 93) src/components/Header.tsx:132— Header.Header has cyclomatic complexity 93 (threshold 15). Of this number, 38 points are the body's own statements and 55 belong to 18 function items 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.
SkillDetailPageView.SkillDetailPageView (cyclomatic 93) src/components/SkillDetailPageView.tsx:193— SkillDetailPageView.SkillDetailPageView has cyclomatic complexity 93 (threshold 15). Of this number, 84 points are the body's own statements and 9 belong to 2 function items 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.
SkillDiffCard.SkillDiffCard (cyclomatic 83) src/components/SkillDiffCard.tsx:147— SkillDiffCard.SkillDiffCard has cyclomatic complexity 83 (threshold 15). Of this number, 34 points are the body's own statements and 49 belong to 14 function items 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.
publish.Upload (cyclomatic 83) src/routes/skills/publish.tsx:90— publish.Upload has cyclomatic complexity 83 (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. This shape REPEATS in the file: one other method here (publish.Upload::handleSubmit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
templates.validateTemplateManifest (cyclomatic 79) packages/schema/src/templates.ts:484— templates.validateTemplateManifest has cyclomatic complexity 79 (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.
skillsShCatalogV1.skillsShCatalogTestV1Handler (cyclomatic 78) convex/httpApiV1/skillsShCatalogV1.ts:619— skillsShCatalogV1.skillsShCatalogTestV1Handler has cyclomatic complexity 78 (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.
publishAttemptOperationalRecovery.validateRetainedPublishAttempt (cyclomatic 76) convex/lib/publishAttemptOperationalRecovery.ts:34— publishAttemptOperationalRecovery.validateRetainedPublishAttempt has cyclomatic complexity 76 (threshold 15). Of this number, 70 points are the body's own statements and 6 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GoogleAnalytics.GoogleAnalytics (cyclomatic 76) src/components/GoogleAnalytics.tsx:28— GoogleAnalytics.GoogleAnalytics has cyclomatic complexity 76 (threshold 15). Most of this is not in the body itself: 1 of the 76 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 75, 199, 57, …). 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.
$handle.PublisherProfilePage (cyclomatic 74) src/routes/user/$handle.tsx:483— $handle.PublisherProfilePage has cyclomatic complexity 74 (threshold 15). Of this number, 51 points are the body's own statements and 23 belong to 11 function items 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.
githubSkillSync.applyGenericGitHubSkillSourceSyncHandler (cyclomatic 71) convex/githubSkillSync.ts:1030— githubSkillSync.applyGenericGitHubSkillSourceSyncHandler has cyclomatic complexity 71 (threshold 15). Of this number, 70 points are the body's own statements and 1 belongs 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.
packages.preparePackagePublishPlan (cyclomatic 70) packages/clawhub/src/cli/commands/packages.ts:2646— packages.preparePackagePublishPlan has cyclomatic complexity 70 (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.
search.UnifiedSearchPage (cyclomatic 70) src/routes/search.tsx:94— search.UnifiedSearchPage has cyclomatic complexity 70 (threshold 15). Of this number, 57 points are the body's own statements and 13 belong to 5 function items 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.
searchInsights.cmdSearchInsights (cyclomatic 69) packages/clawhub-admin/src/commands/searchInsights.ts:17— searchInsights.cmdSearchInsights has cyclomatic complexity 69 (threshold 15). Of this number, 68 points are the body's own statements and 1 belongs to one function item 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.
useUnifiedSearch.useUnifiedSearch (cyclomatic 68) src/lib/useUnifiedSearch.ts:142— useUnifiedSearch.useUnifiedSearch has cyclomatic complexity 68 (threshold 15). Of this number, 22 points are the body's own statements and 46 belong to 9 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skillPublish.publishVersionForUser (cyclomatic 66) convex/lib/skillPublish.ts:160— skillPublish.publishVersionForUser has cyclomatic complexity 66 (threshold 15). Of this number, 62 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skillsV1.exportSkillsV1Handler (cyclomatic 61) convex/httpApiV1/skillsV1.ts:3531— skillsV1.exportSkillsV1Handler has cyclomatic complexity 61 (threshold 15). Of this number, 57 points are the body's own statements and 4 belong to 4 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.
skillsShCatalog.admitScans (cyclomatic 61) convex/skillsShCatalog.ts:1442— skillsShCatalog.admitScans has cyclomatic complexity 61 (threshold 15). Of this number, 60 points are the body's own statements and 1 belongs 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.
skills.setSkillSoftDeletedByActor (cyclomatic 57) convex/skills.ts:11462— skills.setSkillSoftDeletedByActor has cyclomatic complexity 57 (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.
publish.cmdPublish (cyclomatic 56) packages/clawhub/src/cli/commands/publish.ts:39— publish.cmdPublish has cyclomatic complexity 56 (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.
PluginVersionsPanel.PluginVersionsPanel (cyclomatic 56) src/components/PluginVersionsPanel.tsx:55— PluginVersionsPanel.PluginVersionsPanel has cyclomatic complexity 56 (threshold 15). Most of this is not in the body itself: 15 of the 56 points are its own statements and the rest belongs to 8 function items inside it that branch (a function literal at line 273, loadMore, handleRestore, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
packages.searchPackagesImpl (cyclomatic 54) convex/packages.ts:4581— packages.searchPackagesImpl has cyclomatic complexity 54 (threshold 15). Of this number, 39 points are the body's own statements and 15 belong to 7 function items 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.
githubSkillSync.applyGitHubSkillVerificationResultHandler (cyclomatic 54) convex/githubSkillSync.ts:2209— githubSkillSync.applyGitHubSkillVerificationResultHandler has cyclomatic complexity 54 (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.
usersV1.handleAdminStaffEmail (cyclomatic 54) convex/httpApiV1/usersV1.ts:320— usersV1.handleAdminStaffEmail has cyclomatic complexity 54 (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.
searchInsights.readReport (cyclomatic 53) convex/searchInsights.ts:67— searchInsights.readReport has cyclomatic complexity 53 (threshold 15). Of this number, 41 points are the body's own statements and 12 belong to 4 function items 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.
SearchInsightsPage.SearchInsightsPage (cyclomatic 53) src/routes/-management/SearchInsightsPage.tsx:17— SearchInsightsPage.SearchInsightsPage has cyclomatic complexity 53 (threshold 15). Of this number, 28 points are the body's own statements and 25 belong to 11 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.
index.PluginsIndex (cyclomatic 53) src/routes/plugins/index.tsx:340— index.PluginsIndex has cyclomatic complexity 53 (threshold 15). Of this number, 32 points are the body's own statements and 21 belong to 11 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skills.mergeOwnedSkillIntoCanonicalByActor (cyclomatic 51) convex/skills.ts:9310— skills.mergeOwnedSkillIntoCanonicalByActor has cyclomatic complexity 51 (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.
templateBundled.validateTemplateBundledSources (cyclomatic 51) packages/schema/src/templateBundled.ts:34— templateBundled.validateTemplateBundledSources has cyclomatic complexity 51 (threshold 15). Of this number, 45 points are the body's own statements and 6 belong to 3 function items 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.
packagesV1.searchPackages (cyclomatic 50) convex/httpApiV1/packagesV1.ts:3590— packagesV1.searchPackages has cyclomatic complexity 50 (threshold 15). Of this number, 47 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
usersV1.usersPostRouterV1Handler (cyclomatic 48) convex/httpApiV1/usersV1.ts:91— usersV1.usersPostRouterV1Handler has cyclomatic complexity 48 (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.
skillsShCatalogSource.measureSkillsShMirrorProofSource (cyclomatic 48) server/skillsShCatalogSource.ts:1866— skillsShCatalogSource.measureSkillsShMirrorProofSource has cyclomatic complexity 48 (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.
inspect.cmdInspect (cyclomatic 47) packages/clawhub/src/cli/commands/inspect.ts:72— inspect.cmdInspect has cyclomatic complexity 47 (threshold 15). Most of this is not in the body itself: 4 of the 47 points are its own statements and the rest belongs to one function literal inside it that branches (line 81). 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.
search.lexicalFallbackSkillsImpl (cyclomatic 46) convex/search.ts:1916— search.lexicalFallbackSkillsImpl has cyclomatic complexity 46 (threshold 15). Of this number, 22 points are the body's own statements and 24 belong to 7 function items 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.
dashboard.Dashboard (cyclomatic 46) src/routes/dashboard.tsx:61— dashboard.Dashboard has cyclomatic complexity 46 (threshold 15). Of this number, 36 points are the body's own statements and 10 belong to 5 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
-useSkillsBrowseModel.useSkillsBrowseModel (cyclomatic 46) src/routes/skills/-useSkillsBrowseModel.ts:105— -useSkillsBrowseModel.useSkillsBrowseModel has cyclomatic complexity 46 (threshold 15). Of this number, 21 points are the body's own statements and 25 belong to 11 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
device.CliDeviceAuth (cyclomatic 45) src/routes/cli/device.tsx:56— device.CliDeviceAuth has cyclomatic complexity 45 (threshold 15). Of this number, 26 points are the body's own statements and 19 belong to 3 function items 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.
sync.cmdSync (cyclomatic 44) packages/clawhub/src/cli/commands/sync.ts:30— sync.cmdSync has cyclomatic complexity 44 (threshold 15). Of this number, 42 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
templateAgent.validateNativeAgentSettings (cyclomatic 44) packages/schema/src/templateAgent.ts:354— templateAgent.validateNativeAgentSettings has cyclomatic complexity 44 (threshold 15). Of this number, 40 points are the body's own statements and 4 belong to one function item 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.
index.parseClawdisMetadata (cyclomatic 43) convex/lib/skills/index.ts:19— index.parseClawdisMetadata has cyclomatic complexity 43 (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.
packagesV1.exportPluginsV1Handler (cyclomatic 43) convex/httpApiV1/packagesV1.ts:1738— packagesV1.exportPluginsV1Handler has cyclomatic complexity 43 (threshold 15). Of this number, 41 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
$name.PluginDetailTabs (cyclomatic 43) src/routes/plugins/$name.tsx:322— $name.PluginDetailTabs has cyclomatic complexity 43 (threshold 15). Of this number, 37 points are the body's own statements and 6 belong to 3 function items 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.
UserBadge.UserBadge (cyclomatic 42) src/components/UserBadge.tsx:39— UserBadge.UserBadge has cyclomatic complexity 42 (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.
SkillDetailTabs.SkillDetailTabs (cyclomatic 42) src/components/SkillDetailTabs.tsx:74— SkillDetailTabs.SkillDetailTabs has cyclomatic complexity 42 (threshold 15). Of this number, 34 points are the body's own statements and 8 belong to 5 function items 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.
templatePackage.validateTemplatePackageContents (cyclomatic 41) packages/schema/src/templatePackage.ts:161— templatePackage.validateTemplatePackageContents has cyclomatic complexity 41 (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.
catalogFeed.buildSkillEntry (cyclomatic 40) convex/catalogFeed.ts:280— catalogFeed.buildSkillEntry has cyclomatic complexity 40 (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.
publishAttemptOperationalRecovery.assertRetryFinalization (cyclomatic 40) convex/lib/publishAttemptOperationalRecovery.ts:366— publishAttemptOperationalRecovery.assertRetryFinalization has cyclomatic complexity 40 (threshold 15). Of this number, 38 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TemplateDetailPage.TemplateDetailPage (cyclomatic 40) src/components/TemplateDetailPage.tsx:39— TemplateDetailPage.TemplateDetailPage has cyclomatic complexity 40 (threshold 15). Of this number, 22 points are the body's own statements and 18 belong to 4 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.
skills.hardDeleteSkillStep (cyclomatic 39) convex/skills.ts:1448— skills.hardDeleteSkillStep has cyclomatic complexity 39 (threshold 15). Of this number, 37 points are the body's own statements and 2 belong to one function item 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.
featuredSelections.publishForActor (cyclomatic 39) convex/featuredSelections.ts:168— featuredSelections.publishForActor has cyclomatic complexity 39 (threshold 15). Of this number, 35 points are the body's own statements and 4 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.
skills.searchPackageCatalogImpl (cyclomatic 38) convex/skills.ts:5949— skills.searchPackageCatalogImpl has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
searchInsightsV1.searchInsightsV1Handler (cyclomatic 37) convex/httpApiV1/searchInsightsV1.ts:6— searchInsightsV1.searchInsightsV1Handler has cyclomatic complexity 37 (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.
prepublicationReports.retainHttp (cyclomatic 37) convex/prepublicationReports.ts:157— prepublicationReports.retainHttp has cyclomatic complexity 37 (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.
searchEvidenceDigest.buildSearchEvidenceDigest (cyclomatic 37) convex/lib/searchEvidenceDigest.ts:44— searchEvidenceDigest.buildSearchEvidenceDigest has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 4 of the 37 points are its own statements and the rest belongs to 14 function items inside it that branch (project, a function literal at line 203, project::tie, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
packages.cmdInspectPackage (cyclomatic 37) packages/clawhub/src/cli/commands/packages.ts:385— packages.cmdInspectPackage has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to one function literal inside it that branches (line 396). 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.
downloads.downloadZipHandler (cyclomatic 36) convex/downloads.ts:67— downloads.downloadZipHandler has cyclomatic complexity 36 (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.
featuredIntelligence.recommendFeatured (cyclomatic 36) convex/lib/featuredIntelligence.ts:99— featuredIntelligence.recommendFeatured has cyclomatic complexity 36 (threshold 15). Of this number, 17 points are the body's own statements and 19 belong to 7 function items 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.
packages.settleExistingStagedPackagePublication (cyclomatic 36) convex/packages.ts:8770— packages.settleExistingStagedPackagePublication has cyclomatic complexity 36 (threshold 15). Of this number, 34 points are the body's own statements and 2 belong to one function item 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.
featuredIntelligence.readMonthlyAdoption (cyclomatic 36) convex/featuredIntelligence.ts:193— featuredIntelligence.readMonthlyAdoption has cyclomatic complexity 36 (threshold 15). Of this number, 16 points are the body's own statements and 20 belong to 4 function items 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.
skills.listCuratedSkillPage (cyclomatic 36) convex/skills.ts:6305— skills.listCuratedSkillPage has cyclomatic complexity 36 (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.
SkillFilesPanel.SkillFilesPanel (cyclomatic 36) src/components/SkillFilesPanel.tsx:117— SkillFilesPanel.SkillFilesPanel has cyclomatic complexity 36 (threshold 15). Of this number, 20 points are the body's own statements and 16 belong to 5 function items 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.
FeaturedEditorial.FeaturedEditorial (cyclomatic 36) src/routes/-management/FeaturedEditorial.tsx:11— FeaturedEditorial.FeaturedEditorial has cyclomatic complexity 36 (threshold 15). Of this number, 21 points are the body's own statements and 15 belong to 8 function items 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.
agentSkillsHttp.resolveSkill (cyclomatic 35) convex/agentSkillsHttp.ts:129— agentSkillsHttp.resolveSkill 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.
devSeed.seedLocalModerationFixturesHandler (cyclomatic 35) convex/devSeed.ts:2934— devSeed.seedLocalModerationFixturesHandler 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.
pluginDiscoveryQueries.listCuratedPluginCategoryPage (cyclomatic 35) convex/lib/pluginDiscoveryQueries.ts:39— pluginDiscoveryQueries.listCuratedPluginCategoryPage has cyclomatic complexity 35 (threshold 15). Of this number, 28 points are the body's own statements and 7 belong to 3 function items 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.
githubSkillSync.applyGitHubSkillSourceSyncHandler (cyclomatic 35) convex/githubSkillSync.ts:729— githubSkillSync.applyGitHubSkillSourceSyncHandler has cyclomatic complexity 35 (threshold 15). Of this number, 32 points are the body's own statements and 3 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.
maintenance.inspectSkillLineageCycleInternalHandler (cyclomatic 35) convex/maintenance.ts:3401— maintenance.inspectSkillLineageCycleInternalHandler has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
textFiles.decodeUtf8Text (cyclomatic 35) packages/schema/src/textFiles.ts:6— textFiles.decodeUtf8Text has cyclomatic complexity 35 (threshold 15). Of this number, 33 points are the body's own statements and 2 belong to one function item 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.
rolloutCapabilities.getClawHubRuntimeEnvironment (cyclomatic 34) packages/schema/src/rolloutCapabilities.ts:75— rolloutCapabilities.getClawHubRuntimeEnvironment has cyclomatic complexity 34 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skillsShCatalogV1.skillsShCatalogPublicV1Handler (cyclomatic 33) convex/httpApiV1/skillsShCatalogV1.ts:1147— skillsShCatalogV1.skillsShCatalogPublicV1Handler has cyclomatic complexity 33 (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.
skills.cmdInstall (cyclomatic 33) packages/clawhub/src/cli/commands/skills.ts:400— skills.cmdInstall has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 11 of the 33 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 448, 581). 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.
packageApi.fetchPluginCatalog (cyclomatic 33) src/lib/packageApi.ts:370— packageApi.fetchPluginCatalog has cyclomatic complexity 33 (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.
SkillVersionsPanel.SkillVersionsPanel (cyclomatic 33) src/components/SkillVersionsPanel.tsx:51— SkillVersionsPanel.SkillVersionsPanel has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 5 of the 33 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 177, handleDelete, handleRestore, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
ManagedMcpTools.ManagedMcpForm (cyclomatic 33) src/routes/-management/ManagedMcpTools.tsx:204— ManagedMcpTools.ManagedMcpForm has cyclomatic complexity 33 (threshold 15). Most of this is not in the body itself: 15 of the 33 points are its own statements and the rest belongs to 5 function items inside it that branch (submit, selectIcon, a function literal at line 253, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
publish.Upload::handleSubmit (cyclomatic 33) src/routes/skills/publish.tsx:669— publish.Upload::handleSubmit has cyclomatic complexity 33 (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. This shape REPEATS in the file: one other method here (publish.Upload) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
aigAnalysis.reusableAigAnalysis (cyclomatic 32) convex/lib/aigAnalysis.ts:11— aigAnalysis.reusableAigAnalysis has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
skillPageRead.readSkillPageBySlug (cyclomatic 32) convex/lib/skillPageRead.ts:243— skillPageRead.readSkillPageBySlug has cyclomatic complexity 32 (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.
githubSkillSync.upsertGitHubSkillCandidate (cyclomatic 32) convex/githubSkillSync.ts:1501— githubSkillSync.upsertGitHubSkillCandidate has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
publishers.ensurePersonalPublisherForUser (cyclomatic 31) convex/lib/publishers.ts:235— publishers.ensurePersonalPublisherForUser has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
packagePublishRecovery.assertPackageRecoveryEligibility (cyclomatic 31) convex/lib/packagePublishRecovery.ts:196— packagePublishRecovery.assertPackageRecoveryEligibility has cyclomatic complexity 31 (threshold 15). Of this number, 29 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
promotions.normalizePromotionInput (cyclomatic 31) convex/promotions.ts:104— promotions.normalizePromotionInput has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
usersV1.handleAdminUpdatePublisherProfile (cyclomatic 31) convex/httpApiV1/usersV1.ts:848— usersV1.handleAdminUpdatePublisherProfile has cyclomatic complexity 31 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
publisherAbuseTemporalScan.runScheduledTemporalPublisherAbuseScanStep (cyclomatic 31) convex/publisherAbuseTemporalScan.ts:837— publisherAbuseTemporalScan.runScheduledTemporalPublisherAbuseScanStep has cyclomatic complexity 31 (threshold 15). Of this number, 26 points are the body's own statements and 5 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.
packagesV1.mintPublishTokenV1Handler (cyclomatic 30) convex/httpApiV1/packagesV1.ts:2420— packagesV1.mintPublishTokenV1Handler has cyclomatic complexity 30 (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.
skillsShCatalogSource.buildSkillsShMirrorObservation (cyclomatic 30) server/skillsShCatalogSource.ts:747— skillsShCatalogSource.buildSkillsShMirrorObservation has cyclomatic complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skillsShCatalogSource.measureSkillsShTrendingSource (cyclomatic 30) server/skillsShCatalogSource.ts:1461— skillsShCatalogSource.measureSkillsShTrendingSource 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.
homeListingData.fetchHomeSkillListing (cyclomatic 30) src/lib/homeListingData.ts:243— homeListingData.fetchHomeSkillListing has cyclomatic complexity 30 (threshold 15). Of this number, 16 points are the body's own statements and 14 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.
SkillInstallSurface.InstallCommandCard (cyclomatic 30) src/components/SkillInstallSurface.tsx:92— SkillInstallSurface.InstallCommandCard has cyclomatic complexity 30 (threshold 15). Of this number, 28 points are the body's own statements and 2 belong to one function item 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.
SkillsPage.SkillsPage (cyclomatic 30) src/routes/-management/SkillsPage.tsx:30— SkillsPage.SkillsPage has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 5 of the 30 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 134, 183, 333, …). 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.
-useSkillsBrowseModel.useSkillsBrowseModel.sorted (cyclomatic 30) src/routes/skills/-useSkillsBrowseModel.ts:359— -useSkillsBrowseModel.useSkillsBrowseModel.sorted has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 6 of the 30 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 385, 362, 370, …). 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.
githubActionsOidc.verifyGitHubActionsWorkflowJwt (cyclomatic 29) convex/lib/githubActionsOidc.ts:135— githubActionsOidc.verifyGitHubActionsWorkflowJwt has cyclomatic complexity 29 (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.
packages.listPackageInspectorScanBatch (cyclomatic 29) convex/packages.ts:10277— packages.listPackageInspectorScanBatch has cyclomatic complexity 29 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
pluginCategories.inferPluginCategoriesFromManifest (cyclomatic 29) packages/schema/src/pluginCategories.ts:73— pluginCategories.inferPluginCategoriesFromManifest has cyclomatic complexity 29 (threshold 15). Of this number, 28 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
pluginAutoCandidates (cyclomatic 29) convex/lib/catalogClassifier.mjs:1411— pluginAutoCandidates has cyclomatic complexity 29 (threshold 15). Of this number, 23 points are the body's own statements and 6 belong to 2 function items 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.
githubSkillSync.buildGitHubSkillSourceSnapshot (cyclomatic 28) convex/lib/githubSkillSync.ts:181— githubSkillSync.buildGitHubSkillSourceSnapshot 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.
githubSkillSync.scheduleGitHubSkillVerification (cyclomatic 28) convex/githubSkillSync.ts:1958— githubSkillSync.scheduleGitHubSkillVerification 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.
securityPrompt.parseLlmEvalResponse (cyclomatic 28) convex/lib/securityPrompt.ts:666— securityPrompt.parseLlmEvalResponse has cyclomatic complexity 28 (threshold 15). Of this number, 26 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.
publisherAbuse.autoBanPublisherAbuseCandidatesPageInternalHandler (cyclomatic 28) convex/publisherAbuse.ts:932— publisherAbuse.autoBanPublisherAbuseCandidatesPageInternalHandler 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.
packages.cmdPublishPackage (cyclomatic 28) packages/clawhub/src/cli/commands/packages.ts:941— packages.cmdPublishPackage 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.
managedMcp.parseManagedMcpDefinition (cyclomatic 28) packages/schema/src/managedMcp.ts:37— managedMcp.parseManagedMcpDefinition has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MarketplaceIcon.MarketplaceIcon (cyclomatic 28) src/components/MarketplaceIcon.tsx:45— MarketplaceIcon.MarketplaceIcon has cyclomatic complexity 28 (threshold 15). Of this number, 22 points are the body's own statements and 6 belong to 4 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
import.ReviewSkillCard (cyclomatic 28) src/routes/import.tsx:1225— import.ReviewSkillCard has cyclomatic complexity 28 (threshold 15). Of this number, 24 points are the body's own statements and 4 belong to 3 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.
managementShared.formatAuditMetadataSummary (cyclomatic 28) src/routes/-management/managementShared.ts:168— managementShared.formatAuditMetadataSummary 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.
githubImport.importGitHubSkillForUser (cyclomatic 27) convex/githubImport.ts:250— githubImport.importGitHubSkillForUser has cyclomatic complexity 27 (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.
templatePackageHttpRead.readTemplatePackageHttp (cyclomatic 27) convex/lib/templatePackageHttpRead.ts:36— templatePackageHttpRead.readTemplatePackageHttp has cyclomatic complexity 27 (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.
mcpPublicInspection.discoverOAuth (cyclomatic 27) convex/lib/mcpPublicInspection.ts:77— mcpPublicInspection.discoverOAuth has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
publishers.migrateLegacyPublisherHandleToOrgWithActor (cyclomatic 27) convex/publishers.ts:1192— publishers.migrateLegacyPublisherHandleToOrgWithActor has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
skill.png.default (cyclomatic 27) server/routes/og/skill.png.ts:32— skill.png.default has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Header.SearchTypeahead (cyclomatic 27) src/components/Header.tsx:893— Header.SearchTypeahead has cyclomatic complexity 27 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
homeListingData.fetchHomePluginListing (cyclomatic 27) src/lib/homeListingData.ts:356— homeListingData.fetchHomePluginListing has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 9 of the 27 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 380, 427, 467, …). 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.
add.AddPage (cyclomatic 27) src/routes/add.tsx:52— add.AddPage has cyclomatic complexity 27 (threshold 15). Of this number, 23 points are the body's own statements and 4 belong to 3 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.
packageRegistry.extractMcpServerSummaries (cyclomatic 26) convex/lib/packageRegistry.ts:273— packageRegistry.extractMcpServerSummaries has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to one function literal inside it that branches (line 275). 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.
publishAttemptOperationalRecovery.retryFailedPublishAttemptChecks (cyclomatic 26) convex/lib/publishAttemptOperationalRecovery.ts:255— publishAttemptOperationalRecovery.retryFailedPublishAttemptChecks has cyclomatic complexity 26 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
mcpPublicInspection.inspectPublicMcp (cyclomatic 26) convex/lib/mcpPublicInspection.ts:181— mcpPublicInspection.inspectPublicMcp has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs to one function item 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.
convexProxy.parseSkillArchiveManifest (cyclomatic 26) server/convexProxy.ts:521— convexProxy.parseSkillArchiveManifest 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.
publisherOgSvg.buildPublisherOgSvg (cyclomatic 26) server/og/publisherOgSvg.ts:268— publisherOgSvg.buildPublisherOgSvg has cyclomatic complexity 26 (threshold 15). Of this number, 25 points are the body's own statements and 1 belongs 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.
analyticsEngagement.observeAnalyticsEngagement (cyclomatic 26) src/lib/analyticsEngagement.ts:12— analyticsEngagement.observeAnalyticsEngagement has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 2 of the 26 points are its own statements and the rest belongs to 5 function items inside it that branch (scroll, a function literal at line 32, a function literal at line 50, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
googleAnalytics.getGoogleAnalyticsPage (cyclomatic 26) src/lib/googleAnalytics.ts:61— googleAnalytics.getGoogleAnalyticsPage 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.
packageApi.fetchPackages (cyclomatic 26) src/lib/packageApi.ts:300— packageApi.fetchPackages 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.
ManagedMcpTools.ManagedMcpTools (cyclomatic 26) src/routes/-management/ManagedMcpTools.tsx:36— ManagedMcpTools.ManagedMcpTools has cyclomatic complexity 26 (threshold 15). Of this number, 14 points are the body's own statements and 12 belong to 6 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
managedMcpV1.managedMcpV1Handler (cyclomatic 25) convex/httpApiV1/managedMcpV1.ts:13— managedMcpV1.managedMcpV1Handler 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.
searchIntentClassifier.classifySearchIntent (cyclomatic 25) convex/lib/searchIntentClassifier.ts:36— searchIntentClassifier.classifySearchIntent has cyclomatic complexity 25 (threshold 15). Of this number, 20 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
templates.packageManagerArtifacts (cyclomatic 25) packages/schema/src/templates.ts:362— templates.packageManagerArtifacts 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.
CatalogMetadataFields.CatalogMetadataFields (cyclomatic 25) src/components/CatalogMetadataFields.tsx:35— CatalogMetadataFields.CatalogMetadataFields has cyclomatic complexity 25 (threshold 15). Of this number, 16 points are the body's own statements and 9 belong to 3 function items 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.
catalogFeed.buildEntry (cyclomatic 24) convex/catalogFeed.ts:162— catalogFeed.buildEntry has cyclomatic complexity 24 (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.
catalogTextMatch.matchCatalogText (cyclomatic 24) convex/lib/catalogTextMatch.ts:25— catalogTextMatch.matchCatalogText has cyclomatic complexity 24 (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.
githubSkillSync.getArchiveScanBySkillAndContentHashHandler (cyclomatic 24) convex/githubSkillSync.ts:226— githubSkillSync.getArchiveScanBySkillAndContentHashHandler has cyclomatic complexity 24 (threshold 15). Of this number, 18 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
usersV1.handleAdminRecoverPersonalPublisher (cyclomatic 24) convex/httpApiV1/usersV1.ts:730— usersV1.handleAdminRecoverPersonalPublisher has cyclomatic complexity 24 (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.
skillsShClaims.beginSkillsShClaimHandler (cyclomatic 24) convex/skillsShClaims.ts:138— skillsShClaims.beginSkillsShClaimHandler has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
profile.png.default (cyclomatic 24) server/routes/og/profile.png.ts:56— profile.png.default has cyclomatic complexity 24 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
classifyPluginTopics (cyclomatic 24) convex/lib/catalogClassifier.mjs:1886— classifyPluginTopics 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.
openClawPublishAuthorization.validateParentState (cyclomatic 23) convex/lib/openClawPublishAuthorization.ts:543— openClawPublishAuthorization.validateParentState has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
packages.listStablePackageDiscoveryPage (cyclomatic 23) convex/packages.ts:3818— packages.listStablePackageDiscoveryPage has cyclomatic complexity 23 (threshold 15). Of this number, 14 points are the body's own statements and 9 belong to 2 function items 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.
packages.transferPackageOwnerForUser (cyclomatic 23) convex/packages.ts:9548— packages.transferPackageOwnerForUser has cyclomatic complexity 23 (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.
skillPublish.prepareSkillInsertArgsForFinalization (cyclomatic 23) convex/lib/skillPublish.ts:636— skillPublish.prepareSkillInsertArgsForFinalization has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 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.
skills.renameOwnedSkillByActor (cyclomatic 23) convex/skills.ts:9195— skills.renameOwnedSkillByActor has cyclomatic complexity 23 (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.
featuredV1.featuredV1Handler (cyclomatic 23) convex/httpApiV1/featuredV1.ts:20— featuredV1.featuredV1Handler has cyclomatic complexity 23 (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.
securityPrompt.assembleEvalUserMessage (cyclomatic 23) convex/lib/securityPrompt.ts:355— securityPrompt.assembleEvalUserMessage has cyclomatic complexity 23 (threshold 15). Of this number, 16 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.
email.cmdSendStaffEmail (cyclomatic 23) packages/clawhub-admin/src/commands/email.ts:120— email.cmdSendStaffEmail has cyclomatic complexity 23 (threshold 15). Of this number, 17 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.
moderation.cmdRescanAllSkills (cyclomatic 23) packages/clawhub-admin/src/commands/moderation.ts:434— moderation.cmdRescanAllSkills 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.
skillsShCatalogSource.parseSkillsShMirrorProofSnapshotId (cyclomatic 23) server/skillsShCatalogSource.ts:159— skillsShCatalogSource.parseSkillsShMirrorProofSnapshotId has cyclomatic complexity 23 (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.
skillsShCatalogSource.selectSkillsShCatalogTestRows (cyclomatic 23) server/skillsShCatalogSource.ts:2789— skillsShCatalogSource.selectSkillsShCatalogTestRows 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.
downloads.parseArchiveMetricPayload (cyclomatic 22) convex/downloads.ts:446— downloads.parseArchiveMetricPayload has cyclomatic complexity 22 (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.
skillPresentation.isStructurallyValidJpeg (cyclomatic 22) convex/lib/skillPresentation.ts:238— skillPresentation.isStructurallyValidJpeg 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.
packageSdkUsage.replacePackageSdkUsage (cyclomatic 22) convex/lib/packageSdkUsage.ts:182— packageSdkUsage.replacePackageSdkUsage has cyclomatic complexity 22 (threshold 15). Of this number, 21 points are the body's own statements and 1 belongs 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.
packages.resolveDirectPackageSearchDigests (cyclomatic 22) convex/packages.ts:1475— packages.resolveDirectPackageSearchDigests has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to 4 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.
packages.buildPackagePluginCategoryDigestQuery (cyclomatic 22) convex/packages.ts:1690— packages.buildPackagePluginCategoryDigestQuery has cyclomatic complexity 22 (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.
packages.latestCompletedFindingsScans (cyclomatic 22) convex/packages.ts:3529— packages.latestCompletedFindingsScans 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.
packages.restorePackageDoc (cyclomatic 22) convex/packages.ts:5680— packages.restorePackageDoc 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.
packages.insertPackageInspectorFindings (cyclomatic 22) convex/packages.ts:9950— packages.insertPackageInspectorFindings has cyclomatic complexity 22 (threshold 15). Of this number, 20 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.
skillPublicationProgress.readSkillVersionPublicationProgress (cyclomatic 22) convex/lib/skillPublicationProgress.ts:36— skillPublicationProgress.readSkillVersionPublicationProgress has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skillsV1.listSkillsV1Handler (cyclomatic 22) convex/httpApiV1/skillsV1.ts:1447— skillsV1.listSkillsV1Handler has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong 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.
packageInspectorHttp.packageInspectorResultsHttp (cyclomatic 22) convex/packageInspectorHttp.ts:199— packageInspectorHttp.packageInspectorResultsHttp has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
publisherAbuse.runPublisherAbuseScoreRunInternalHandler (cyclomatic 22) convex/publisherAbuse.ts:1559— publisherAbuse.runPublisherAbuseScoreRunInternalHandler 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.
skillsShClaims.applySkillsShTestClaimVerdictHandler (cyclomatic 22) convex/skillsShClaims.ts:294— skillsShClaims.applySkillsShTestClaimVerdictHandler has cyclomatic complexity 22 (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.
skillsShCatalogSource.fetchSkillsShIdentityPage (cyclomatic 22) server/skillsShCatalogSource.ts:856— skillsShCatalogSource.fetchSkillsShIdentityPage 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.
convexProxy.parseSkillExportArchiveManifest (cyclomatic 22) server/convexProxy.ts:572— convexProxy.parseSkillExportArchiveManifest 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.
SkillSecurityScanResults.SkillSpectorContent (cyclomatic 22) src/components/SkillSecurityScanResults.tsx:276— SkillSecurityScanResults.SkillSpectorContent has cyclomatic complexity 22 (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.
PackageSourceChooser.PackageSourceChooser (cyclomatic 22) src/components/PackageSourceChooser.tsx:109— PackageSourceChooser.PackageSourceChooser has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to 4 function items 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.
skillDetailUtils.formatConfigSnippet (cyclomatic 22) src/components/skillDetailUtils.ts:17— skillDetailUtils.formatConfigSnippet 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.
SkillDetailPage.buildStaffVisibilityAlert (cyclomatic 22) src/components/SkillDetailPage.tsx:121— SkillDetailPage.buildStaffVisibilityAlert has cyclomatic complexity 22 (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.
DownloadsPage.DownloadsPage (cyclomatic 22) src/routes/-management/DownloadsPage.tsx:27— DownloadsPage.DownloadsPage has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
index.parseFrontmatterLevelDeclarations (cyclomatic 21) convex/lib/skills/index.ts:261— index.parseFrontmatterLevelDeclarations 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.
githubSkillSync.parseSkillsShDisplayManifest (cyclomatic 21) convex/lib/githubSkillSync.ts:125— githubSkillSync.parseSkillsShDisplayManifest has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong 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.
githubSkillSync.buildGitHubSkillSyncPlan (cyclomatic 21) convex/lib/githubSkillSync.ts:334— githubSkillSync.buildGitHubSkillSyncPlan 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.
skills.isOwnerInitiatedSkillHideForAdminTransfer (cyclomatic 21) convex/skills.ts:11385— skills.isOwnerInitiatedSkillHideForAdminTransfer has cyclomatic complexity 21 (threshold 15). Of this number, 13 points are the body's own statements and 8 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.
githubSkillSync.rollbackGitHubSkillCandidateHandler (cyclomatic 21) convex/githubSkillSync.ts:2069— githubSkillSync.rollbackGitHubSkillCandidateHandler has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
packageInspectorHttp.packageInspectorClaimHttp (cyclomatic 21) convex/packageInspectorHttp.ts:52— packageInspectorHttp.packageInspectorClaimHttp has cyclomatic complexity 21 (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.
skillCardClaims.admitSkillCardClaims (cyclomatic 21) convex/lib/skillCardClaims.ts:70— skillCardClaims.admitSkillCardClaims 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.
skills.readSkillOrigin (cyclomatic 21) packages/clawhub/src/skills.ts:178— skills.readSkillOrigin 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.
skillsShCatalogSource.resolveSkillsShMirrorGitHubLocators (cyclomatic 21) server/skillsShCatalogSource.ts:1177— skillsShCatalogSource.resolveSkillsShMirrorGitHubLocators has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 1197, 1218, 1244, …). 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.
skillsShCatalogSource.fetchSkillsShMirrorBatch (cyclomatic 21) server/skillsShCatalogSource.ts:2193— skillsShCatalogSource.fetchSkillsShMirrorBatch has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 9 of the 21 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 2262, monitoredFetch). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SkillListingRow.SkillListingRow (cyclomatic 21) src/components/SkillListingRow.tsx:34— SkillListingRow.SkillListingRow 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.
HomePopularPublishersSection.HomePopularPublishersSection (cyclomatic 21) src/components/HomePopularPublishersSection.tsx:45— HomePopularPublishersSection.HomePopularPublishersSection has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 61, handlePointerMove, handlePointerDown, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SkillOwnershipPanel.SkillOwnershipPanel (cyclomatic 21) src/components/SkillOwnershipPanel.tsx:105— SkillOwnershipPanel.SkillOwnershipPanel has cyclomatic complexity 21 (threshold 15). Of this number, 12 points are the body's own statements and 9 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PromotionsPage.parseForm (cyclomatic 21) src/routes/-management/PromotionsPage.tsx:110— PromotionsPage.parseForm 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.
index.loadPluginsPageData (cyclomatic 21) src/routes/plugins/index.tsx:136— index.loadPluginsPageData has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
security-audit.SkillSecurityAuditRoutePage (cyclomatic 21) src/routes/$owner/$slug/security-audit.tsx:48— security-audit.SkillSecurityAuditRoutePage has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
shared.parseMultipartPublish (cyclomatic 20) convex/httpApiV1/shared.ts:395— shared.parseMultipartPublish 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.
packageCatalogRead.packageMatchesListFilters (cyclomatic 20) convex/lib/packageCatalogRead.ts:275— packageCatalogRead.packageMatchesListFilters 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.
packagesV1.buildPackageReadiness (cyclomatic 20) convex/httpApiV1/packagesV1.ts:4598— packagesV1.buildPackageReadiness 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.
skillsShCatalogV1.verifyControlledCanaryGitHubSource (cyclomatic 20) convex/httpApiV1/skillsShCatalogV1.ts:396— skillsShCatalogV1.verifyControlledCanaryGitHubSource has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skillsV1.parseSecurityVerdictItems (cyclomatic 20) convex/httpApiV1/skillsV1.ts:860— skillsV1.parseSecurityVerdictItems 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.
skillsV1.parseListSort (cyclomatic 20) convex/httpApiV1/skillsV1.ts:1401— skillsV1.parseListSort has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
publisherAbuseScoring.classifySkillTemporalAbuseScore (cyclomatic 20) convex/lib/publisherAbuseScoring.ts:290— publisherAbuseScoring.classifySkillTemporalAbuseScore 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.
maintenance.backfillSkillSummariesInternalHandler (cyclomatic 20) convex/maintenance.ts:1057— maintenance.backfillSkillSummariesInternalHandler 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.
migrations.classifySuspiciousPublishAttemptPublicState (cyclomatic 20) convex/migrations.ts:446— migrations.classifySuspiciousPublishAttemptPublicState has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs 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.
migrations.buildCanonicalCatalogMetadataPatch (cyclomatic 20) convex/migrations.ts:665— migrations.buildCanonicalCatalogMetadataPatch has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skillsShCatalog.cancelAttempt (cyclomatic 20) convex/skillsShCatalog.ts:2952— skillsShCatalog.cancelAttempt 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.
users.computeEnsureUpdates (cyclomatic 20) convex/users.ts:957— users.computeEnsureUpdates 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.
users.getSelfDeletedAccountEligibility (cyclomatic 20) convex/users.ts:1200— users.getSelfDeletedAccountEligibility has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SkillCard.SkillCard (cyclomatic 20) src/components/SkillCard.tsx:27— SkillCard.SkillCard has cyclomatic complexity 20 (threshold 15). Of this number, 19 points are the body's own statements and 1 belongs 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.
SkillCardPreview.SkillCardPreview (cyclomatic 20) src/components/SkillCardPreview.tsx:130— SkillCardPreview.SkillCardPreview has cyclomatic complexity 20 (threshold 15). Of this number, 14 points are the body's own statements and 6 belong to 4 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.
SkillInstallCard.buildSkillInstallTabs (cyclomatic 20) src/components/SkillInstallCard.tsx:327— SkillInstallCard.buildSkillInstallTabs has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
PromotionsPage.PromotionsPage (cyclomatic 20) src/routes/-management/PromotionsPage.tsx:171— PromotionsPage.PromotionsPage has cyclomatic complexity 20 (threshold 15). Of this number, 12 points are the body's own statements and 8 belong to 4 function items 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.
verifiedClientIp.getVerifiedClientIp (cyclomatic 19) convex/lib/verifiedClientIp.ts:10— verifiedClientIp.getVerifiedClientIp has cyclomatic complexity 19 (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.
githubImport.parseGitHubImportUrl (cyclomatic 19) convex/lib/githubImport.ts:43— githubImport.parseGitHubImportUrl has cyclomatic complexity 19 (threshold 15). Of this number, 18 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.
packageSdkUsage.recordPackageInspectorScan (cyclomatic 19) convex/lib/packageSdkUsage.ts:101— packageSdkUsage.recordPackageInspectorScan 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.
packages.buildPackageTopicDigestQuery (cyclomatic 19) convex/packages.ts:1793— packages.buildPackageTopicDigestQuery 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.
skillQuality.evaluateQuality (cyclomatic 19) convex/lib/skillQuality.ts:157— skillQuality.evaluateQuality 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.
skills.listSkillTopicFilteredPage (cyclomatic 19) convex/skills.ts:5019— skills.listSkillTopicFilteredPage has cyclomatic complexity 19 (threshold 15). Of this number, 17 points are the body's own statements and 2 belong to 2 function items 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.
githubSkillSync.fetchPublicGitHubRepoMetadata (cyclomatic 19) convex/githubSkillSync.ts:3130— githubSkillSync.fetchPublicGitHubRepoMetadata 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.
skillsShCatalogV1.storeArtifactFiles (cyclomatic 19) convex/httpApiV1/skillsShCatalogV1.ts:533— skillsShCatalogV1.storeArtifactFiles 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.
skillsV1.handleTransferRequest (cyclomatic 19) convex/httpApiV1/skillsV1.ts:2736— skillsV1.handleTransferRequest 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.
publisherAbuseTemporalScan.getOrStartScheduledTemporalScanInternalHandler (cyclomatic 19) convex/publisherAbuseTemporalScan.ts:74— publisherAbuseTemporalScan.getOrStartScheduledTemporalScanInternalHandler 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.
securityScan.requestSkillRescanForActor (cyclomatic 19) convex/securityScan.ts:903— securityScan.requestSkillRescanForActor 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.
securityScan.enqueuePackageReleaseScan (cyclomatic 19) convex/securityScan.ts:2654— securityScan.enqueuePackageReleaseScan has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
securityScan.prepareCatalogRetry (cyclomatic 19) convex/securityScan.ts:3182— securityScan.prepareCatalogRetry has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skills.cmdSearch (cyclomatic 19) packages/clawhub/src/cli/commands/skills.ts:296— skills.cmdSearch has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 313, 347). 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.
skills.resolveExploreSort (cyclomatic 19) packages/clawhub/src/cli/commands/skills.ts:1391— skills.resolveExploreSort has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
inspect.cmdVerifySkill (cyclomatic 19) packages/clawhub/src/cli/commands/inspect.ts:293— inspect.cmdVerifySkill has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 310). 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.
cli.findFirstTopLevelOperand (cyclomatic 19) packages/clawhub/src/cli.ts:135— cli.findFirstTopLevelOperand 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.
skillsShCatalogSource.validateSkillsShCatalogGitHubOwnerProof (cyclomatic 19) server/skillsShCatalogSource.ts:2616— skillsShCatalogSource.validateSkillsShCatalogGitHubOwnerProof has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
registryOgSvg.wrapText (cyclomatic 19) server/og/registryOgSvg.ts:102— registryOgSvg.wrapText has cyclomatic complexity 19 (threshold 15). Of this number, 13 points are the body's own statements and 6 belong to 2 function items 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.
CatalogTopicInput.CatalogTopicInput (cyclomatic 19) src/components/CatalogTopicInput.tsx:55— CatalogTopicInput.CatalogTopicInput has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 148, commitDraft, a function literal at line 98, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SkillDiffCard.applyMonacoTheme (cyclomatic 19) src/components/SkillDiffCard.tsx:745— SkillDiffCard.applyMonacoTheme 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.
DashboardDownloadsInsights.DashboardDownloadsInsights (cyclomatic 19) src/components/dashboard/DashboardDownloadsInsights.tsx:36— DashboardDownloadsInsights.DashboardDownloadsInsights has cyclomatic complexity 19 (threshold 15). Of this number, 14 points are the body's own statements and 5 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.
DashboardNeedsAttention.DashboardNeedsAttention (cyclomatic 19) src/components/dashboard/DashboardNeedsAttention.tsx:73— DashboardNeedsAttention.DashboardNeedsAttention has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 7 of the 19 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 145, 83, 105, …). 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.
AbusePage.PublisherTemporalEvidence (cyclomatic 19) src/routes/-management/AbusePage.tsx:1366— AbusePage.PublisherTemporalEvidence has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 5 of the 19 points are its own statements and the rest belongs to one function literal inside it that branches (line 1393). 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.
packageSecurity.resolvePackageReleaseScanStatus (cyclomatic 18) convex/lib/packageSecurity.ts:19— packageSecurity.resolvePackageReleaseScanStatus has cyclomatic complexity 18 (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.
clawpack.parseTarEntries (cyclomatic 18) packages/clawhub/src/clawpack.ts:99— clawpack.parseTarEntries 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.
packageCatalogRead.digestMatchesFilters (cyclomatic 18) convex/lib/packageCatalogRead.ts:148— packageCatalogRead.digestMatchesFilters 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.
packages.toPublicPackage (cyclomatic 18) convex/packages.ts:939— packages.toPublicPackage has cyclomatic complexity 18 (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.
featuredArtifacts.readSkill (cyclomatic 18) convex/featuredArtifacts.ts:95— featuredArtifacts.readSkill has cyclomatic complexity 18 (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.
skills.updateSkillTagsForActor (cyclomatic 18) convex/skills.ts:8526— skills.updateSkillTagsForActor 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.
githubSkillSync.ensureRetainedCurrentGitHubSkillCandidate (cyclomatic 18) convex/githubSkillSync.ts:1664— githubSkillSync.ensureRetainedCurrentGitHubSkillCandidate has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
canonicalSkillSearchResponse.serializeCanonicalSkillSearchResults (cyclomatic 18) convex/lib/canonicalSkillSearchResponse.ts:37— canonicalSkillSearchResponse.serializeCanonicalSkillSearchResults has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 38). 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.
packagePublishRecoveryV1.recoverPackagePublishAttemptV1Handler (cyclomatic 18) convex/httpApiV1/packagePublishRecoveryV1.ts:29— packagePublishRecoveryV1.recoverPackagePublishAttemptV1Handler 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.
packagesV1.packagesDeleteRouterV1Handler (cyclomatic 18) convex/httpApiV1/packagesV1.ts:3321— packagesV1.packagesDeleteRouterV1Handler 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.
securityPrompt.parseAgenticRiskFindings (cyclomatic 18) convex/lib/securityPrompt.ts:559— securityPrompt.parseAgenticRiskFindings 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.
usersV1.handleAdminReserve (cyclomatic 18) convex/httpApiV1/usersV1.ts:615— usersV1.handleAdminReserve 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.
skillBackfill.deepEqual (cyclomatic 18) convex/lib/skillBackfill.ts:49— skillBackfill.deepEqual 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.
userSearch.scoreUser (cyclomatic 18) convex/lib/userSearch.ts:21— userSearch.scoreUser has cyclomatic complexity 18 (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.
publisherAbuseDevSeed.clearDemoRows (cyclomatic 18) convex/publisherAbuseDevSeed.ts:732— publisherAbuseDevSeed.clearDemoRows 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.
moderation.cmdReclassifyBan (cyclomatic 18) packages/clawhub-admin/src/commands/moderation.ts:640— moderation.cmdReclassifyBan has cyclomatic complexity 18 (threshold 15). Of this number, 13 points are the body's own statements and 5 belong 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.
skillsShCatalogSource.buildSkillsShMirrorUpstreamScanners (cyclomatic 18) server/skillsShCatalogSource.ts:425— skillsShCatalogSource.buildSkillsShMirrorUpstreamScanners 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.
convexProxy.proxyConvexRequest (cyclomatic 18) server/convexProxy.ts:126— convexProxy.proxyConvexRequest 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. This is NOT this file's highest cyclomatic complexity: convexProxy.isMergedExportManifestEntry (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
BrowseControls.BrowseCategorySelect (cyclomatic 18) src/components/BrowseControls.tsx:399— BrowseControls.BrowseCategorySelect has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 7 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.
googleAnalytics.createGoogleAnalytics.update (cyclomatic 18) src/lib/googleAnalytics.ts:327— googleAnalytics.createGoogleAnalytics.update has cyclomatic complexity 18 (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.
AbusePage.PublisherAbuseSignalInspector (cyclomatic 18) src/routes/-management/AbusePage.tsx:993— AbusePage.PublisherAbuseSignalInspector 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.
functions.repointPackageLatestRelease (cyclomatic 17) convex/functions.ts:332— functions.repointPackageLatestRelease has cyclomatic complexity 17 (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.
skillZip.buildOrderedZipStream::advance (cyclomatic 17) convex/lib/skillZip.ts:156— skillZip.buildOrderedZipStream::advance 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.
packagePageCursor.decodePublicPageCursor (cyclomatic 17) convex/lib/packagePageCursor.ts:17— packagePageCursor.decodePublicPageCursor has cyclomatic complexity 17 (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.
pluginCategoryClassification.classifyPluginCategories (cyclomatic 17) convex/lib/pluginCategoryClassification.ts:108— pluginCategoryClassification.classifyPluginCategories has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skills.resolveDigestLatestVersionForSkill (cyclomatic 17) convex/skills.ts:5354— skills.resolveDigestLatestVersionForSkill has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skills.revokeSkillVersionForUser (cyclomatic 17) convex/skills.ts:8022— skills.revokeSkillVersionForUser has cyclomatic complexity 17 (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.
httpRouteRateLimit.resolveDefaultRouteRateLimit (cyclomatic 17) convex/lib/httpRouteRateLimit.ts:63— httpRouteRateLimit.resolveDefaultRouteRateLimit has cyclomatic complexity 17 (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.
promotionsV1.promotionsPostRouterV1Handler (cyclomatic 17) convex/httpApiV1/promotionsV1.ts:224— promotionsV1.promotionsPostRouterV1Handler has cyclomatic complexity 17 (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.
skillsV1.skillScanGetRouterV1Handler (cyclomatic 17) convex/httpApiV1/skillsV1.ts:1200— skillsV1.skillScanGetRouterV1Handler 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.
maintenance.cleanupEmptySkillsInternalHandler (cyclomatic 17) convex/maintenance.ts:2590— maintenance.cleanupEmptySkillsInternalHandler 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, 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.
publisherAbuseOwnerSynchrony.getPublisherAbuseOwnerSynchronyCandidateInternalHandler (cyclomatic 17) convex/publisherAbuseOwnerSynchrony.ts:229— publisherAbuseOwnerSynchrony.getPublisherAbuseOwnerSynchronyCandidateInternalHandler 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.
publishers.ensureOrgPublisherHandleWithActor (cyclomatic 17) convex/publishers.ts:1349— publishers.ensureOrgPublisherHandleWithActor 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.
packages.waitForPackagePublication (cyclomatic 17) packages/clawhub/src/cli/commands/packages.ts:1248— packages.waitForPackagePublication 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.
packages.buildSource (cyclomatic 17) packages/clawhub/src/cli/commands/packages.ts:3057— packages.buildSource has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
skills.readSkillsShResolverMetadata (cyclomatic 17) packages/clawhub/src/cli/commands/skills.ts:1527— skills.readSkillsShResolverMetadata has cyclomatic complexity 17 (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.
moderation.cmdRecoverPersonalPublisher (cyclomatic 17) packages/clawhub-admin/src/commands/moderation.ts:282— moderation.cmdRecoverPersonalPublisher has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong 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.
SecurityAuditPage.AigFindingCard (cyclomatic 17) src/components/SecurityAuditPage.tsx:698— SecurityAuditPage.AigFindingCard has cyclomatic complexity 17 (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.
SecurityAuditPage.SecurityAuditPage (cyclomatic 17) src/components/SecurityAuditPage.tsx:1114— SecurityAuditPage.SecurityAuditPage 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.
SkillDiffCard.cssColor4ToHex (cyclomatic 17) src/components/SkillDiffCard.tsx:894— SkillDiffCard.cssColor4ToHex 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.
artifactStatus.skillArtifactStatus (cyclomatic 17) src/components/artifacts/artifactStatus.ts:37— artifactStatus.skillArtifactStatus has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DashboardDownloadsInsights.Sparkline (cyclomatic 17) src/components/dashboard/DashboardDownloadsInsights.tsx:239— DashboardDownloadsInsights.Sparkline has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong 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.
stars.Stars (cyclomatic 17) src/routes/stars.tsx:45— stars.Stars has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
$name.PluginValidationFindingCard (cyclomatic 17) src/routes/plugins/$name.tsx:876— $name.PluginValidationFindingCard has cyclomatic complexity 17 (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.
index.parseInstallSpec (cyclomatic 16) convex/lib/skills/index.ts:119— index.parseInstallSpec 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.
clawpack.parseClawPack (cyclomatic 16) packages/clawhub/src/clawpack.ts:157— clawpack.parseClawPack 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.
openaiResponse.extractResponseText (cyclomatic 16) convex/lib/openaiResponse.ts:1— openaiResponse.extractResponseText 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.
packagePublishRecovery.assertManualPackagePublisher (cyclomatic 16) convex/lib/packagePublishRecovery.ts:57— packagePublishRecovery.assertManualPackagePublisher has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: packagePublishRecovery.assertRecoveryArtifactEligibility (cyclomatic 30) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
packageSdkUsageContract.normalizeSdkUsageReport (cyclomatic 16) convex/lib/packageSdkUsageContract.ts:115— packageSdkUsageContract.normalizeSdkUsageReport has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
packages.takeVisiblePackageCategoryDigestPage (cyclomatic 16) convex/packages.ts:1925— packages.takeVisiblePackageCategoryDigestPage 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. This is NOT this file's highest cyclomatic complexity: packages.reverifyOpenClawAuthorizationEvidence (cyclomatic 17) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
skillFileReadAccess.canReadSkillVersionFiles (cyclomatic 16) convex/lib/skillFileReadAccess.ts:8— skillFileReadAccess.canReadSkillVersionFiles 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.
skills.collectSkillPackageCatalogPage (cyclomatic 16) convex/skills.ts:5676— skills.collectSkillPackageCatalogPage 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.
githubImport.toOwnedPublicRepoListItem (cyclomatic 16) convex/githubImport.ts:578— githubImport.toOwnedPublicRepoListItem 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.
httpApi.cliPublishHandler (cyclomatic 16) convex/httpApi.ts:204— httpApi.cliPublishHandler 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.
publishersV1.createPublisherV1Handler (cyclomatic 16) convex/httpApiV1/publishersV1.ts:12— publishersV1.createPublisherV1Handler 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.
searchReportsV1.searchReportsV1Handler (cyclomatic 16) convex/httpApiV1/searchReportsV1.ts:12— searchReportsV1.searchReportsV1Handler 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.
usersV1.handleAdminReclassifyBan (cyclomatic 16) convex/httpApiV1/usersV1.ts:483— usersV1.handleAdminReclassifyBan 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.
usersV1.handleAdminEnsurePublisher (cyclomatic 16) convex/httpApiV1/usersV1.ts:806— usersV1.handleAdminEnsurePublisher 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.
managedMcpBundle.buildManagedMcpBundle (cyclomatic 16) convex/lib/managedMcpBundle.ts:29— managedMcpBundle.buildManagedMcpBundle 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.
maintenance.backfillSkillFingerprintsInternalHandler (cyclomatic 16) convex/maintenance.ts:1952— maintenance.backfillSkillFingerprintsInternalHandler has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs 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.
maintenance.repairSkillLineageCyclesInternalHandler (cyclomatic 16) convex/maintenance.ts:3613— maintenance.repairSkillLineageCyclesInternalHandler 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.
publisherAbuse.publisherSkillMetricsForScoring (cyclomatic 16) convex/publisherAbuse.ts:2398— publisherAbuse.publisherSkillMetricsForScoring 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.
publisherAbuseTemporalScan.runScheduledTemporalPublisherAbuseScanInternalHandler (cyclomatic 16) convex/publisherAbuseTemporalScan.ts:1061— publisherAbuseTemporalScan.runScheduledTemporalPublisherAbuseScanInternalHandler 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.
publishers.toPublisherListItem (cyclomatic 16) convex/publishers.ts:738— publishers.toPublisherListItem has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skillsShCatalog.reconcileNativeSkill (cyclomatic 16) convex/skillsShCatalog.ts:125— skillsShCatalog.reconcileNativeSkill 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. This is NOT this file's highest cyclomatic complexity: skillsShCatalog.sameFixtureObservation (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
skillsShCatalog.validateRealScanArtifacts (cyclomatic 16) convex/skillsShCatalog.ts:2852— skillsShCatalog.validateRealScanArtifacts 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. This is NOT this file's highest cyclomatic complexity: skillsShCatalog.sameFixtureObservation (cyclomatic 19) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
users.ensurePublisherHandleWithActor (cyclomatic 16) convex/users.ts:2243— users.ensurePublisherHandleWithActor 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.
deviceAuth.pollForDeviceToken (cyclomatic 16) packages/clawhub/src/deviceAuth.ts:92— deviceAuth.pollForDeviceToken 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.
http.normalizeHttpErrorBody (cyclomatic 16) packages/clawhub/src/http.ts:638— http.normalizeHttpErrorBody 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.
http.formatStructuredHttpError (cyclomatic 16) packages/clawhub/src/http.ts:670— http.formatStructuredHttpError 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.
packages.cmdExplorePackages (cyclomatic 16) packages/clawhub/src/cli/commands/packages.ts:316— packages.cmdExplorePackages has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 2 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 325). 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.
packages.cmdValidatePackage (cyclomatic 16) packages/clawhub/src/cli/commands/packages.ts:670— packages.cmdValidatePackage 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.
packages.cmdVerifyPackage (cyclomatic 16) packages/clawhub/src/cli/commands/packages.ts:1540— packages.cmdVerifyPackage has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 1552). 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.
featured.parseSkillRefOrFail (cyclomatic 16) packages/clawhub-admin/src/commands/featured.ts:41— featured.parseSkillRefOrFail 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.
packages.cmdPackageModerationQueue (cyclomatic 16) packages/clawhub-admin/src/commands/packages.ts:417— packages.cmdPackageModerationQueue 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.
packages.cmdUpsertPackageMigration (cyclomatic 16) packages/clawhub-admin/src/commands/packages.ts:627— packages.cmdUpsertPackageMigration has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 641). 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.
skillsShCatalogSource.fetchGitHubRepoTreeSnapshot (cyclomatic 16) server/skillsShCatalogSource.ts:1099— skillsShCatalogSource.fetchGitHubRepoTreeSnapshot 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.
plugin.png.default (cyclomatic 16) server/routes/og/plugin.png.ts:42— plugin.png.default has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
analyticsEvents.analyticsEventParameters (cyclomatic 16) src/lib/analyticsEvents.ts:225— analyticsEvents.analyticsEventParameters 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.
googleAnalytics.deferredWorkflow (cyclomatic 16) src/lib/googleAnalytics.ts:156— googleAnalytics.deferredWorkflow 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.
SecurityAuditPage.inferSkillSpectorPatternCategory (cyclomatic 16) src/components/SecurityAuditPage.tsx:243— SecurityAuditPage.inferSkillSpectorPatternCategory 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.
docs.DocsAuth (cyclomatic 16) src/routes/auth/docs.tsx:23— docs.DocsAuth has cyclomatic complexity 16 (threshold 15). Of this number, 12 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
-useSkillsBrowseModel.useSkillsBrowseModel.fetchPage (cyclomatic 16) src/routes/skills/-useSkillsBrowseModel.ts:181— -useSkillsBrowseModel.useSkillsBrowseModel.fetchPage has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs 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.
classifySkill (cyclomatic 16) convex/lib/catalogClassifier.mjs:2018— classifySkill has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 8 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
No assertions: requires the registry argument at the type level packages/clawhub/src/cli/authToken.test.ts:68— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D10 · Test Quality· Fixed-sleep synchronisation · ×1
Fixed-sleep synchronisation: reserves the last request only once when streamed bodies finish together scripts/evaluations/openai-capability-broker.test.ts:360— This test starts work it did not wait for (`pending`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 50))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
TodoComment convex/http.ts:316— // TODO: remove legacy /api routes after deprecation window. — 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.
skillsV1.skillsGetRouterV1Handler (cognitive 276) convex/httpApiV1/skillsV1.ts:1761— skillsV1.skillsGetRouterV1Handler has cognitive complexity 276 (threshold 15). Drivers by points: if/else 75 (154 pts), ternaries 38 (88 pts), boolean chains 34 (nesting depth added 129). 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.
packagesV1.packagesPostRouterV1Handler (cognitive 258) convex/httpApiV1/packagesV1.ts:2615— packagesV1.packagesPostRouterV1Handler has cognitive complexity 258 (threshold 15). Drivers by points: if/else 83 (153 pts), boolean chains 38, ternaries 16 (36 pts), error handling 16 (31 pts) (nesting depth added 105). 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.
skillsV1.skillsPostRouterV1Handler (cognitive 221) convex/httpApiV1/skillsV1.ts:2926— skillsV1.skillsPostRouterV1Handler has cognitive complexity 221 (threshold 15). Drivers by points: if/else 62 (116 pts), ternaries 27 (60 pts), error handling 13 (26 pts), boolean chains 19 (nesting depth added 100). 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.
packagesV1.packagesGetRouterV1Handler (cognitive 212) convex/httpApiV1/packagesV1.ts:3777— packagesV1.packagesGetRouterV1Handler has cognitive complexity 212 (threshold 15). Drivers by points: if/else 84 (159 pts), boolean chains 26, ternaries 9 (17 pts), error handling 3 (7 pts), loops 1 (3 pts) (nesting depth added 89). 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.
AbusePage.AbusePage (cognitive 201) src/routes/-management/AbusePage.tsx:47— AbusePage.AbusePage has cognitive complexity 201 (threshold 15). Drivers by points: ternaries 93 (156 pts), boolean chains 35, if/else 7 (10 pts) (nesting depth added 66). Of this number, 170 points are the body's own statements and 31 belong to 5 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.
SkillDetailPage.SkillDetailPage (cognitive 198) src/components/SkillDetailPage.tsx:184— SkillDetailPage.SkillDetailPage has cognitive complexity 198 (threshold 15). Drivers by points: ternaries 74 (96 pts), boolean chains 63, if/else 34 (36 pts), error handling 3 (nesting depth added 24). Of this number, 127 points are the body's own statements and 71 belong to 28 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
publish.PublishPluginRoute (cognitive 196) src/routes/plugins/publish.tsx:173— publish.PublishPluginRoute has cognitive complexity 196 (threshold 15). Drivers by points: ternaries 47 (95 pts), if/else 55 (66 pts), boolean chains 33, error handling 1 (2 pts) (nesting depth added 60). Of this number, 101 points are the body's own statements and 95 belong to 14 function items 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.
HomeListingSection.HomeListingSection (cognitive 195) src/components/HomeListingSection.tsx:218— HomeListingSection.HomeListingSection has cognitive complexity 195 (threshold 15). Drivers by points: ternaries 56 (117 pts), if/else 35 (56 pts), boolean chains 22 (nesting depth added 82). Of this number, 67 points are the body's own statements and 128 belong to 23 function items 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.
packages.listPackagePageImpl (cognitive 193) convex/packages.ts:3946— packages.listPackagePageImpl has cognitive complexity 193 (threshold 15). Drivers by points: if/else 36 (90 pts), ternaries 26 (62 pts), boolean chains 33, loops 3 (8 pts) (nesting depth added 95). Of this number, 174 points are the body's own statements and 19 belong to 2 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
settings.Settings (cognitive 191) src/routes/settings.tsx:276— settings.Settings has cognitive complexity 191 (threshold 15). Drivers by points: ternaries 52 (96 pts), if/else 42 (45 pts), boolean chains 41, error handling 9 (nesting depth added 47). Of this number, 101 points are the body's own statements and 90 belong to 32 function items 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.
packages.publishPackageImpl (cognitive 186) convex/packages.ts:8052— packages.publishPackageImpl has cognitive complexity 186 (threshold 15). Drivers by points: if/else 56 (102 pts), ternaries 36 (45 pts), boolean chains 32, error handling 4 (5 pts), loops 1 (2 pts) (nesting depth added 57). Of this number, 172 points are the body's own statements and 14 belong to 5 function items 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.
skills.cmdUpdate (cognitive 180) packages/clawhub/src/cli/commands/skills.ts:629— skills.cmdUpdate has cognitive complexity 180 (threshold 15). Drivers by points: if/else 45 (104 pts), ternaries 18 (41 pts), boolean chains 32, error handling 1 (2 pts), loops 1 (nesting depth added 83). Of this number, 169 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
$name.PluginDetailPageContent (cognitive 165) src/routes/plugins/$name.tsx:1048— $name.PluginDetailPageContent has cognitive complexity 165 (threshold 15). Drivers by points: ternaries 78 (121 pts), boolean chains 37, if/else 7 (nesting depth added 43). Of this number, 154 points are the body's own statements and 11 belong to 8 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.
import.ImportGitHub (cognitive 151) src/routes/import.tsx:185— import.ImportGitHub has cognitive complexity 151 (threshold 15). Drivers by points: ternaries 38 (75 pts), if/else 27 (36 pts), boolean chains 24, loops 10 (11 pts), error handling 4 (5 pts) (nesting depth added 48). Of this number, 80 points are the body's own statements and 71 belong to 20 function items 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.
templates.validateTemplateManifest (cognitive 144) packages/schema/src/templates.ts:484— templates.validateTemplateManifest has cognitive complexity 144 (threshold 15). Drivers by points: if/else 42 (100 pts), loops 13 (21 pts), boolean chains 17, error handling 2 (5 pts), ternaries 1 (nesting depth added 69). 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.
packagesV1.listPackages (cognitive 142) convex/httpApiV1/packagesV1.ts:1159— packagesV1.listPackages has cognitive complexity 142 (threshold 15). Drivers by points: ternaries 27 (56 pts), boolean chains 45, if/else 27 (37 pts), loops 2 (4 pts) (nesting depth added 41). Of this number, 136 points are the body's own statements and 6 belong to 4 function items 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.
SkillDiffCard.SkillDiffCard (cognitive 130) src/components/SkillDiffCard.tsx:147— SkillDiffCard.SkillDiffCard has cognitive complexity 130 (threshold 15). Drivers by points: ternaries 38 (87 pts), if/else 23 (25 pts), boolean chains 14, loops 3, error handling 1 (nesting depth added 51). Of this number, 73 points are the body's own statements and 57 belong to 14 function items 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.
searchInsights.cmdSearchInsights (cognitive 124) packages/clawhub-admin/src/commands/searchInsights.ts:17— searchInsights.cmdSearchInsights has cognitive complexity 124 (threshold 15). Drivers by points: if/else 38 (66 pts), ternaries 12 (26 pts), loops 7 (21 pts), boolean chains 11 (nesting depth added 56). Of this number, 121 points are the body's own statements and 3 belong to one function item 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.
$handle.PublisherProfilePage (cognitive 121) src/routes/user/$handle.tsx:483— $handle.PublisherProfilePage has cognitive complexity 121 (threshold 15). Drivers by points: ternaries 38 (90 pts), boolean chains 19, if/else 11, error handling 1 (nesting depth added 52). Of this number, 101 points are the body's own statements and 20 belong to 11 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SkillDetailPageView.SkillDetailPageView (cognitive 116) src/components/SkillDetailPageView.tsx:193— SkillDetailPageView.SkillDetailPageView has cognitive complexity 116 (threshold 15). Drivers by points: ternaries 54 (94 pts), boolean chains 21, if/else 1 (nesting depth added 40). Of this number, 107 points are the body's own statements and 9 belong to 2 function items 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.
search.UnifiedSearchPage (cognitive 113) src/routes/search.tsx:94— search.UnifiedSearchPage has cognitive complexity 113 (threshold 15). Drivers by points: ternaries 34 (87 pts), boolean chains 23, if/else 3 (nesting depth added 53). Of this number, 90 points are the body's own statements and 23 belong to 5 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
skillsV1.exportSkillsV1Handler (cognitive 109) convex/httpApiV1/skillsV1.ts:3531— skillsV1.exportSkillsV1Handler has cognitive complexity 109 (threshold 15). Drivers by points: if/else 35 (74 pts), ternaries 8 (15 pts), error handling 5 (7 pts), loops 5 (7 pts), boolean chains 6 (nesting depth added 50). Of this number, 105 points are the body's own statements and 4 belong to 4 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.
templateBundled.validateTemplateBundledSources (cognitive 109) packages/schema/src/templateBundled.ts:34— templateBundled.validateTemplateBundledSources has cognitive complexity 109 (threshold 15). Drivers by points: if/else 19 (68 pts), ternaries 4 (16 pts), boolean chains 15, loops 4 (10 pts) (nesting depth added 67). Of this number, 99 points are the body's own statements and 10 belong to 3 function items 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.
Header.Header (cognitive 109) src/components/Header.tsx:132— Header.Header has cognitive complexity 109 (threshold 15). Drivers by points: ternaries 29 (44 pts), if/else 35 (42 pts), boolean chains 20, loops 3 (nesting depth added 22). Of this number, 46 points are the body's own statements and 63 belong to 18 function items 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.
management.Management (cognitive 108) src/routes/management.tsx:226— management.Management has cognitive complexity 108 (threshold 15). Drivers by points: ternaries 56 (62 pts), boolean chains 24, if/else 19 (22 pts) (nesting depth added 9). Of this number, 70 points are the body's own statements and 38 belong to 21 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
skillsShCatalogV1.skillsShCatalogTestV1Handler (cognitive 106) convex/httpApiV1/skillsShCatalogV1.ts:619— skillsShCatalogV1.skillsShCatalogTestV1Handler has cognitive complexity 106 (threshold 15). Drivers by points: if/else 56 (69 pts), ternaries 15 (28 pts), error handling 3 (5 pts), boolean chains 4 (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.
PluginVersionsPanel.PluginVersionsPanel (cognitive 89) src/components/PluginVersionsPanel.tsx:55— PluginVersionsPanel.PluginVersionsPanel has cognitive complexity 89 (threshold 15). Drivers by points: ternaries 15 (48 pts), if/else 18 (22 pts), boolean chains 14, error handling 5 (nesting depth added 37). Of this number, 22 points are the body's own statements and 67 belong to 8 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SkillsPage.SkillsPage (cognitive 87) src/routes/-management/SkillsPage.tsx:30— SkillsPage.SkillsPage has cognitive complexity 87 (threshold 15). Drivers by points: ternaries 18 (67 pts), if/else 4 (16 pts), boolean chains 4 (nesting depth added 61). Most of this is not in the body itself: 7 of the 87 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 134, 183, 333, …). 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.
publish.Upload (cognitive 84) src/routes/skills/publish.tsx:90— publish.Upload has cognitive complexity 84 (threshold 15). Drivers by points: ternaries 65 (82 pts), if/else 77 (80 pts), boolean chains 49, error handling 1, loops 1 (nesting depth added 20). 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. This shape REPEATS in the file: one other method here (publish.Upload::handleSubmit) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
SearchInsightsPage.SearchInsightsPage (cognitive 82) src/routes/-management/SearchInsightsPage.tsx:17— SearchInsightsPage.SearchInsightsPage has cognitive complexity 82 (threshold 15). Drivers by points: ternaries 33 (65 pts), if/else 9, boolean chains 8 (nesting depth added 32). Of this number, 39 points are the body's own statements and 43 belong to 11 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.
packages.preparePackagePublishPlan (cognitive 80) packages/clawhub/src/cli/commands/packages.ts:2646— packages.preparePackagePublishPlan has cognitive complexity 80 (threshold 15). Drivers by points: if/else 28 (43 pts), ternaries 18 (21 pts), boolean chains 11, error handling 3 (5 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.
githubSkillSync.applyGenericGitHubSkillSourceSyncHandler (cognitive 79) convex/githubSkillSync.ts:1030— githubSkillSync.applyGenericGitHubSkillSourceSyncHandler has cognitive complexity 79 (threshold 15). Drivers by points: if/else 27 (48 pts), boolean chains 20, ternaries 4 (6 pts), loops 3, error handling 1 (2 pts) (nesting depth added 24). Of this number, 78 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
skills.searchPackageCatalogImpl (cognitive 76) convex/skills.ts:5949— skills.searchPackageCatalogImpl has cognitive complexity 76 (threshold 15). Drivers by points: if/else 23 (55 pts), loops 4 (9 pts), boolean chains 8, ternaries 2 (4 pts) (nesting depth added 39). 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.
packages.searchPackagesImpl (cognitive 71) convex/packages.ts:4581— packages.searchPackagesImpl has cognitive complexity 71 (threshold 15). Drivers by points: if/else 18 (32 pts), ternaries 11 (19 pts), boolean chains 15, loops 3 (5 pts) (nesting depth added 24). Of this number, 43 points are the body's own statements and 28 belong to 7 function items 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.
skillsShCatalog.admitScans (cognitive 71) convex/skillsShCatalog.ts:1442— skillsShCatalog.admitScans has cognitive complexity 71 (threshold 15). Drivers by points: if/else 24 (44 pts), boolean chains 18, ternaries 5 (8 pts), loops 1 (nesting depth added 23). Of this number, 69 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.
packagesV1.exportPluginsV1Handler (cognitive 70) convex/httpApiV1/packagesV1.ts:1738— packagesV1.exportPluginsV1Handler has cognitive complexity 70 (threshold 15). Drivers by points: if/else 23 (45 pts), loops 6 (8 pts), boolean chains 6, ternaries 3 (6 pts), error handling 4 (5 pts) (nesting depth added 28). Of this number, 66 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SkillDetailTabs.SkillDetailTabs (cognitive 68) src/components/SkillDetailTabs.tsx:74— SkillDetailTabs.SkillDetailTabs has cognitive complexity 68 (threshold 15). Drivers by points: ternaries 33 (60 pts), boolean chains 6, if/else 2 (nesting depth added 27). Of this number, 55 points are the body's own statements and 13 belong to 5 function items 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.
$name.PluginDetailTabs (cognitive 68) src/routes/plugins/$name.tsx:322— $name.PluginDetailTabs has cognitive complexity 68 (threshold 15). Drivers by points: ternaries 29 (55 pts), boolean chains 10, if/else 3 (nesting depth added 26). Of this number, 61 points are the body's own statements and 7 belong to 3 function items 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.
skillPublish.publishVersionForUser (cognitive 66) convex/lib/skillPublish.ts:160— skillPublish.publishVersionForUser has cognitive complexity 66 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 21, ternaries 14 (15 pts), loops 1 (2 pts), error handling 1 (nesting depth added 10). Of this number, 63 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
GoogleAnalytics.GoogleAnalytics (cognitive 66) src/components/GoogleAnalytics.tsx:28— GoogleAnalytics.GoogleAnalytics has cognitive complexity 66 (threshold 15). Drivers by points: if/else 30 (35 pts), boolean chains 23, ternaries 4 (7 pts), error handling 1 (nesting depth added 8). None of this is in the body itself: all 66 points belong to 13 function literals inside it that branch (lines 75, 199, 57, …). 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.
inspect.cmdInspect (cognitive 65) packages/clawhub/src/cli/commands/inspect.ts:72— inspect.cmdInspect has cognitive complexity 65 (threshold 15). Drivers by points: if/else 30 (45 pts), boolean chains 8, loops 2 (7 pts), error handling 2 (3 pts), ternaries 2 (nesting depth added 21). Most of this is not in the body itself: 3 of the 65 points are its own statements and the rest belongs to one function literal inside it that branches (line 81). 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.
devSeed.seedLocalModerationFixturesHandler (cognitive 64) convex/devSeed.ts:2934— devSeed.seedLocalModerationFixturesHandler has cognitive complexity 64 (threshold 15). Drivers by points: if/else 20 (44 pts), loops 4 (9 pts), ternaries 5 (7 pts), boolean chains 4 (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.
skills.mergeOwnedSkillIntoCanonicalByActor (cognitive 63) convex/skills.ts:9310— skills.mergeOwnedSkillIntoCanonicalByActor has cognitive complexity 63 (threshold 15). Drivers by points: if/else 27 (41 pts), boolean chains 16, loops 3 (4 pts), ternaries 2 (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.
githubSkillSync.applyGitHubSkillVerificationResultHandler (cognitive 63) convex/githubSkillSync.ts:2209— githubSkillSync.applyGitHubSkillVerificationResultHandler has cognitive complexity 63 (threshold 15). Drivers by points: if/else 16 (27 pts), boolean chains 19, ternaries 8 (17 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.
publish.cmdPublish (cognitive 63) packages/clawhub/src/cli/commands/publish.ts:39— publish.cmdPublish has cognitive complexity 63 (threshold 15). Drivers by points: if/else 18 (23 pts), ternaries 16 (23 pts), boolean chains 15, error handling 1, 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.
usersV1.usersPostRouterV1Handler (cognitive 61) convex/httpApiV1/usersV1.ts:91— usersV1.usersPostRouterV1Handler has cognitive complexity 61 (threshold 15). Drivers by points: if/else 26 (35 pts), ternaries 9 (12 pts), boolean chains 7, error handling 4 (7 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
skillsShCatalogSource.fetchSkillsShIdentityPage (cognitive 60) server/skillsShCatalogSource.ts:856— skillsShCatalogSource.fetchSkillsShIdentityPage has cognitive complexity 60 (threshold 15). Drivers by points: if/else 14 (47 pts), error handling 3 (8 pts), loops 2 (3 pts), boolean chains 2 (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.
sync.cmdSync (cognitive 59) packages/clawhub/src/cli/commands/sync.ts:30— sync.cmdSync has cognitive complexity 59 (threshold 15). Drivers by points: if/else 26 (35 pts), ternaries 7 (12 pts), boolean chains 7, error handling 3 (4 pts), loops 1 (nesting depth added 15). Of this number, 57 points are the body's own statements and 2 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.
TemplateDetailPage.TemplateDetailPage (cognitive 59) src/components/TemplateDetailPage.tsx:39— TemplateDetailPage.TemplateDetailPage has cognitive complexity 59 (threshold 15). Drivers by points: ternaries 23 (46 pts), boolean chains 8, if/else 5 (nesting depth added 23). Of this number, 23 points are the body's own statements and 36 belong to 4 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.
searchInsights.readReport (cognitive 58) convex/searchInsights.ts:67— searchInsights.readReport has cognitive complexity 58 (threshold 15). Drivers by points: if/else 11 (18 pts), ternaries 9 (16 pts), boolean chains 13, loops 6 (9 pts), error handling 1 (2 pts) (nesting depth added 18). Of this number, 46 points are the body's own statements and 12 belong to 4 function items 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.
usersV1.handleAdminStaffEmail (cognitive 58) convex/httpApiV1/usersV1.ts:320— usersV1.handleAdminStaffEmail has cognitive complexity 58 (threshold 15). Drivers by points: if/else 21 (24 pts), ternaries 17 (18 pts), boolean chains 14, error handling 1 (2 pts) (nesting depth added 5). 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.
useUnifiedSearch.useUnifiedSearch (cognitive 58) src/lib/useUnifiedSearch.ts:142— useUnifiedSearch.useUnifiedSearch has cognitive complexity 58 (threshold 15). Drivers by points: boolean chains 23, if/else 17 (20 pts), ternaries 13, error handling 2 (nesting depth added 3). Of this number, 16 points are the body's own statements and 42 belong to 9 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
skills.setSkillSoftDeletedByActor (cognitive 56) convex/skills.ts:11462— skills.setSkillSoftDeletedByActor has cognitive complexity 56 (threshold 15). Drivers by points: if/else 17 (23 pts), boolean chains 20, ternaries 12, error handling 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
publishAttemptOperationalRecovery.validateRetainedPublishAttempt (cognitive 54) convex/lib/publishAttemptOperationalRecovery.ts:34— publishAttemptOperationalRecovery.validateRetainedPublishAttempt has cognitive complexity 54 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 15, ternaries 8 (15 pts), loops 2, error handling 1 (nesting depth added 14). Of this number, 50 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
templateAgent.validateNativeAgentSettings (cognitive 54) packages/schema/src/templateAgent.ts:354— templateAgent.validateNativeAgentSettings has cognitive complexity 54 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 18, loops 5 (7 pts), error handling 1 (2 pts) (nesting depth added 11). Of this number, 49 points are the body's own statements and 5 belong to one function item 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.
skillsShCatalogSource.measureSkillsShMirrorProofSource (cognitive 54) server/skillsShCatalogSource.ts:1866— skillsShCatalogSource.measureSkillsShMirrorProofSource has cognitive complexity 54 (threshold 15). Drivers by points: if/else 16 (29 pts), boolean chains 10, loops 4 (9 pts), ternaries 3 (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.
SkillFilesPanel.SkillFilesPanel (cognitive 54) src/components/SkillFilesPanel.tsx:117— SkillFilesPanel.SkillFilesPanel has cognitive complexity 54 (threshold 15). Drivers by points: ternaries 20 (40 pts), if/else 10, boolean chains 4 (nesting depth added 20). Of this number, 38 points are the body's own statements and 16 belong to 5 function items 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.
index.PluginsIndex (cognitive 52) src/routes/plugins/index.tsx:340— index.PluginsIndex has cognitive complexity 52 (threshold 15). Drivers by points: ternaries 16 (24 pts), boolean chains 15, if/else 11 (12 pts), error handling 1 (nesting depth added 9). Of this number, 30 points are the body's own statements and 22 belong to 11 function items 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.
githubSkillSync.applyGitHubSkillSourceSyncHandler (cognitive 50) convex/githubSkillSync.ts:729— githubSkillSync.applyGitHubSkillSourceSyncHandler has cognitive complexity 50 (threshold 15). Drivers by points: if/else 13 (28 pts), ternaries 8 (12 pts), boolean chains 5, error handling 2 (3 pts), loops 2 (nesting depth added 20). Of this number, 48 points are the body's own statements and 2 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.
publisherAbuse.autoBanPublisherAbuseCandidatesPageInternalHandler (cognitive 50) convex/publisherAbuse.ts:932— publisherAbuse.autoBanPublisherAbuseCandidatesPageInternalHandler has cognitive complexity 50 (threshold 15). Drivers by points: if/else 17 (36 pts), boolean chains 7, ternaries 3 (6 pts), loops 1 (nesting depth added 22). 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.
device.CliDeviceAuth (cognitive 49) src/routes/cli/device.tsx:56— device.CliDeviceAuth has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 13 (22 pts), boolean chains 13, if/else 9 (12 pts), error handling 2 (nesting depth added 12). Of this number, 32 points are the body's own statements and 17 belong to 3 function items 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.
-useSkillsBrowseModel.useSkillsBrowseModel (cognitive 49) src/routes/skills/-useSkillsBrowseModel.ts:105— -useSkillsBrowseModel.useSkillsBrowseModel has cognitive complexity 49 (threshold 15). Drivers by points: ternaries 16 (20 pts), if/else 14 (16 pts), boolean chains 12, error handling 1 (nesting depth added 6). Of this number, 19 points are the body's own statements and 30 belong to 11 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
packageApi.fetchPluginCatalog (cognitive 48) src/lib/packageApi.ts:370— packageApi.fetchPluginCatalog has cognitive complexity 48 (threshold 15). Drivers by points: if/else 25 (38 pts), error handling 2 (4 pts), boolean chains 3, ternaries 2 (3 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.
index.parseClawdisMetadata (cognitive 47) convex/lib/skills/index.ts:19— index.parseClawdisMetadata has cognitive complexity 47 (threshold 15). Drivers by points: if/else 21 (30 pts), ternaries 6 (9 pts), boolean chains 7, error handling 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.
publisherAbuseTemporalScan.runScheduledTemporalPublisherAbuseScanStep (cognitive 47) convex/publisherAbuseTemporalScan.ts:837— publisherAbuseTemporalScan.runScheduledTemporalPublisherAbuseScanStep has cognitive complexity 47 (threshold 15). Drivers by points: ternaries 11 (25 pts), if/else 12 (18 pts), boolean chains 4 (nesting depth added 20). Of this number, 43 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
githubSkillSync.buildGitHubSkillSourceSnapshot (cognitive 46) convex/lib/githubSkillSync.ts:181— githubSkillSync.buildGitHubSkillSourceSnapshot has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 14 (25 pts), if/else 5 (11 pts), boolean chains 4, error handling 1 (3 pts), loops 2 (3 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.
searchInsightsV1.searchInsightsV1Handler (cognitive 46) convex/httpApiV1/searchInsightsV1.ts:6— searchInsightsV1.searchInsightsV1Handler has cognitive complexity 46 (threshold 15). Drivers by points: if/else 22 (33 pts), boolean chains 12, 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.
FeaturedEditorial.FeaturedEditorial (cognitive 46) src/routes/-management/FeaturedEditorial.tsx:11— FeaturedEditorial.FeaturedEditorial has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 19 (33 pts), boolean chains 9, if/else 3, error handling 1 (nesting depth added 14). Of this number, 24 points are the body's own statements and 22 belong to 8 function items 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.
downloads.downloadZipHandler (cognitive 45) convex/downloads.ts:67— downloads.downloadZipHandler has cognitive complexity 45 (threshold 15). Drivers by points: if/else 16 (26 pts), ternaries 6 (10 pts), boolean chains 4, loops 2 (3 pts), error handling 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.
templatePackage.validateTemplatePackageContents (cognitive 45) packages/schema/src/templatePackage.ts:161— templatePackage.validateTemplatePackageContents has cognitive complexity 45 (threshold 15). Drivers by points: if/else 24 (29 pts), boolean chains 6, ternaries 5 (6 pts), loops 3, error handling 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
dashboard.Dashboard (cognitive 45) src/routes/dashboard.tsx:61— dashboard.Dashboard has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 16 (19 pts), boolean chains 16, if/else 9 (10 pts) (nesting depth added 4). Of this number, 35 points are the body's own statements and 10 belong to 5 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
skills.listCuratedSkillPage (cognitive 44) convex/skills.ts:6305— skills.listCuratedSkillPage has cognitive complexity 44 (threshold 15). Drivers by points: if/else 9 (28 pts), boolean chains 10, loops 2 (3 pts), ternaries 3 (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.
search.lexicalFallbackSkillsImpl (cognitive 44) convex/search.ts:1916— search.lexicalFallbackSkillsImpl has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (24 pts), boolean chains 13, ternaries 4, loops 2 (3 pts) (nesting depth added 9). Of this number, 18 points are the body's own statements and 26 belong to 7 function items 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.
packagesV1.searchPackages (cognitive 44) convex/httpApiV1/packagesV1.ts:3590— packagesV1.searchPackages has cognitive complexity 44 (threshold 15). Drivers by points: boolean chains 22, if/else 18 (19 pts), ternaries 2 (3 pts) (nesting depth added 2). Of this number, 43 points are the body's own statements and 1 belongs to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
packages.cmdInspectPackage (cognitive 44) packages/clawhub/src/cli/commands/packages.ts:385— packages.cmdInspectPackage has cognitive complexity 44 (threshold 15). Drivers by points: if/else 23 (29 pts), boolean chains 7, loops 2 (6 pts), ternaries 2 (nesting depth added 10). Most of this is not in the body itself: 2 of the 44 points are its own statements and the rest belongs to one function literal inside it that branches (line 396). 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.
homeListingData.fetchHomeSkillListing (cognitive 44) src/lib/homeListingData.ts:243— homeListingData.fetchHomeSkillListing has cognitive complexity 44 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 7 (12 pts), boolean chains 8, error handling 2 (4 pts), loops 2 (3 pts) (nesting depth added 17). Of this number, 27 points are the body's own statements and 17 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.
SkillInstallSurface.InstallCommandCard (cognitive 44) src/components/SkillInstallSurface.tsx:92— SkillInstallSurface.InstallCommandCard has cognitive complexity 44 (threshold 15). Drivers by points: ternaries 21 (36 pts), boolean chains 7, if/else 1 (nesting depth added 15). Of this number, 42 points are the body's own statements and 2 belong to one function item 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.
packages.cmdPublishPackage (cognitive 43) packages/clawhub/src/cli/commands/packages.ts:941— packages.cmdPublishPackage has cognitive complexity 43 (threshold 15). Drivers by points: if/else 22 (31 pts), ternaries 5 (6 pts), boolean chains 3, loops 1 (2 pts), error handling 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.
skills.cmdInstall (cognitive 43) packages/clawhub/src/cli/commands/skills.ts:400— skills.cmdInstall has cognitive complexity 43 (threshold 15). Drivers by points: if/else 19 (25 pts), ternaries 8 (10 pts), boolean chains 8 (nesting depth added 8). Most of this is not in the body itself: 10 of the 43 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 448, 581). 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.
pluginDiscoveryQueries.listCuratedPluginCategoryPage (cognitive 42) convex/lib/pluginDiscoveryQueries.ts:39— pluginDiscoveryQueries.listCuratedPluginCategoryPage has cognitive complexity 42 (threshold 15). Drivers by points: if/else 10 (21 pts), boolean chains 11, loops 3 (4 pts), ternaries 2 (4 pts), error handling 1 (2 pts) (nesting depth added 15). Of this number, 35 points are the body's own statements and 7 belong to 3 function items 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.
maintenance.backfillSkillSummariesInternalHandler (cognitive 42) convex/maintenance.ts:1057— maintenance.backfillSkillSummariesInternalHandler has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (33 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 25). 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.
publishers.ensurePersonalPublisherForUser (cognitive 41) convex/lib/publishers.ts:235— publishers.ensurePersonalPublisherForUser has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 8, error handling 3 (4 pts), ternaries 2 (4 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.
agentSkillsHttp.resolveSkill (cognitive 41) convex/agentSkillsHttp.ts:129— agentSkillsHttp.resolveSkill has cognitive complexity 41 (threshold 15). Drivers by points: if/else 16 (30 pts), boolean chains 9, ternaries 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
packages.settleExistingStagedPackagePublication (cognitive 41) convex/packages.ts:8770— packages.settleExistingStagedPackagePublication has cognitive complexity 41 (threshold 15). Drivers by points: if/else 10 (19 pts), ternaries 5 (13 pts), boolean chains 9 (nesting depth added 17). Of this number, 38 points are the body's own statements and 3 belong to one function item 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.
skills.hardDeleteSkillStep (cognitive 41) convex/skills.ts:1448— skills.hardDeleteSkillStep has cognitive complexity 41 (threshold 15). Drivers by points: if/else 14 (24 pts), loops 7 (14 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 18). Of this number, 39 points are the body's own statements and 2 belong to one function item 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.
maintenance.repairSkillLineageCyclesInternalHandler (cognitive 41) convex/maintenance.ts:3613— maintenance.repairSkillLineageCyclesInternalHandler has cognitive complexity 41 (threshold 15). Drivers by points: if/else 12 (36 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 25). 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.
textFiles.decodeUtf8Text (cognitive 41) packages/schema/src/textFiles.ts:6— textFiles.decodeUtf8Text has cognitive complexity 41 (threshold 15). Drivers by points: if/else 11 (21 pts), ternaries 5 (13 pts), boolean chains 6, loops 1 (nesting depth added 18). Of this number, 38 points are the body's own statements and 3 belong to one function item 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.
managementShared.formatAuditMetadataSummary (cognitive 41) src/routes/-management/managementShared.ts:168— managementShared.formatAuditMetadataSummary has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 11 (22 pts), if/else 13 (16 pts), boolean chains 3 (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.
PluginsPage.PluginsPage (cognitive 41) src/routes/-management/PluginsPage.tsx:11— PluginsPage.PluginsPage has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 13 (40 pts), if/else 1 (nesting depth added 27). Most of this is not in the body itself: 8 of the 41 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 78, 43, 127). 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.
featuredSelections.publishForActor (cognitive 40) convex/featuredSelections.ts:168— featuredSelections.publishForActor has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (24 pts), boolean chains 7, ternaries 3 (7 pts), loops 2 (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.
maintenance.cleanupEmptySkillsInternalHandler (cognitive 40) convex/maintenance.ts:2590— maintenance.cleanupEmptySkillsInternalHandler has cognitive complexity 40 (threshold 15). Drivers by points: if/else 12 (35 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 24). Of this number, 39 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
classifyPluginTopics (cognitive 40) convex/lib/catalogClassifier.mjs:1886— classifyPluginTopics has cognitive complexity 40 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 5 (12 pts), loops 6 (10 pts), other 4, boolean chains 2 (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.
featuredIntelligence.recommendFeatured (cognitive 39) convex/lib/featuredIntelligence.ts:99— featuredIntelligence.recommendFeatured has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 15 (24 pts), loops 6 (7 pts), if/else 3 (5 pts), boolean chains 3 (nesting depth added 12). Of this number, 26 points are the body's own statements and 13 belong to 7 function items 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.
searchEvidenceDigest.buildSearchEvidenceDigest (cognitive 39) convex/lib/searchEvidenceDigest.ts:44— searchEvidenceDigest.buildSearchEvidenceDigest has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 11 (18 pts), boolean chains 14, if/else 4 (6 pts), loops 1 (nesting depth added 9). Most of this is not in the body itself: 5 of the 39 points are its own statements and the rest belongs to 14 function items inside it that branch (project::tie, a function literal at line 203, project, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
pluginAutoCandidates (cognitive 39) convex/lib/catalogClassifier.mjs:1411— pluginAutoCandidates has cognitive complexity 39 (threshold 15). Drivers by points: if/else 15 (22 pts), loops 4 (6 pts), boolean chains 4, ternaries 3 (4 pts), other 3 (nesting depth added 10). Of this number, 34 points are the body's own statements and 5 belong to 2 function items 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.
skillsShCatalogSource.selectSkillsShCatalogTestRows (cognitive 38) server/skillsShCatalogSource.ts:2789— skillsShCatalogSource.selectSkillsShCatalogTestRows has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 6 (8 pts), boolean chains 6 (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.
analyticsEngagement.observeAnalyticsEngagement (cognitive 38) src/lib/analyticsEngagement.ts:12— analyticsEngagement.observeAnalyticsEngagement has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (23 pts), boolean chains 7, loops 5 (7 pts), ternaries 1 (nesting depth added 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 5 function items inside it that branch (a function literal at line 50, scroll, a function literal at line 32, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
UserBadge.UserBadge (cognitive 38) src/components/UserBadge.tsx:39— UserBadge.UserBadge has cognitive complexity 38 (threshold 15). Drivers by points: ternaries 19 (25 pts), boolean chains 12, if/else 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
skillsShCatalogV1.skillsShCatalogPublicV1Handler (cognitive 37) convex/httpApiV1/skillsShCatalogV1.ts:1147— skillsShCatalogV1.skillsShCatalogPublicV1Handler has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 7, error handling 3 (5 pts), ternaries 4 (5 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.
PackageSourceChooser.PackageSourceChooser (cognitive 37) src/components/PackageSourceChooser.tsx:109— PackageSourceChooser.PackageSourceChooser has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 16 (31 pts), boolean chains 3, if/else 2 (3 pts) (nesting depth added 16). Of this number, 31 points are the body's own statements and 6 belong to 4 function items 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.
ManagedMcpTools.ManagedMcpForm (cognitive 37) src/routes/-management/ManagedMcpTools.tsx:204— ManagedMcpTools.ManagedMcpForm has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 21 (27 pts), if/else 5, boolean chains 4, error handling 1 (nesting depth added 6). Of this number, 16 points are the body's own statements and 21 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
managedMcpV1.managedMcpV1Handler (cognitive 36) convex/httpApiV1/managedMcpV1.ts:13— managedMcpV1.managedMcpV1Handler has cognitive complexity 36 (threshold 15). Drivers by points: if/else 10 (15 pts), ternaries 4 (8 pts), error handling 3 (5 pts), boolean chains 4, loops 2 (4 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.
SecurityAuditPage.SecurityAuditPage (cognitive 36) src/components/SecurityAuditPage.tsx:1114— SecurityAuditPage.SecurityAuditPage has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 14 (34 pts), boolean chains 2 (nesting depth added 20). 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.
publisherAbuse.runPublisherAbuseScoreRunInternalHandler (cognitive 35) convex/publisherAbuse.ts:1559— publisherAbuse.runPublisherAbuseScoreRunInternalHandler has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (29 pts), boolean chains 3, error handling 2, loops 1 (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.
templates.packageManagerArtifacts (cognitive 35) packages/schema/src/templates.ts:362— templates.packageManagerArtifacts has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (27 pts), boolean chains 6, loops 1, ternaries 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.
skillsShCatalogSource.measureSkillsShTrendingSource (cognitive 35) server/skillsShCatalogSource.ts:1461— skillsShCatalogSource.measureSkillsShTrendingSource has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (25 pts), boolean chains 7, loops 2 (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.
packageApi.fetchPackages (cognitive 35) src/lib/packageApi.ts:300— packageApi.fetchPackages has cognitive complexity 35 (threshold 15). Drivers by points: if/else 21 (30 pts), ternaries 2 (3 pts), boolean chains 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.
add.AddPage (cognitive 35) src/routes/add.tsx:52— add.AddPage has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 13 (22 pts), boolean chains 9, if/else 4 (nesting depth added 9). Of this number, 31 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AbusePage.PublisherTemporalEvidence (cognitive 35) src/routes/-management/AbusePage.tsx:1366— AbusePage.PublisherTemporalEvidence has cognitive complexity 35 (threshold 15). Drivers by points: ternaries 17 (34 pts), if/else 1 (nesting depth added 17). Most of this is not in the body itself: 6 of the 35 points are its own statements and the rest belongs to one function literal inside it that branches (line 1393). 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.
securityPrompt.assembleEvalUserMessage (cognitive 34) convex/lib/securityPrompt.ts:355— securityPrompt.assembleEvalUserMessage has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (24 pts), ternaries 7, loops 1 (2 pts), boolean chains 1 (nesting depth added 10). Of this number, 20 points are the body's own statements and 14 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.
prepublicationReports.retainHttp (cognitive 34) convex/prepublicationReports.ts:157— prepublicationReports.retainHttp has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (18 pts), error handling 6 (7 pts), boolean chains 5, ternaries 2 (4 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
mcpPublicInspection.discoverOAuth (cognitive 34) convex/lib/mcpPublicInspection.ts:77— mcpPublicInspection.discoverOAuth has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 5, error handling 2 (4 pts), loops 3 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
skills.readSkillOrigin (cognitive 34) packages/clawhub/src/skills.ts:178— skills.readSkillOrigin has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 11 (22 pts), if/else 3 (6 pts), boolean chains 3, error handling 1 (2 pts), loops 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.
homeListingData.fetchHomePluginListing (cognitive 34) src/lib/homeListingData.ts:356— homeListingData.fetchHomePluginListing has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 11, loops 3 (6 pts), ternaries 2 (3 pts) (nesting depth added 11). Most of this is not in the body itself: 9 of the 34 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 380, 467, 427, …). 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.
SkillVersionsPanel.SkillVersionsPanel (cognitive 34) src/components/SkillVersionsPanel.tsx:51— SkillVersionsPanel.SkillVersionsPanel has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 10, ternaries 9 (10 pts), error handling 2 (nesting depth added 3). Most of this is not in the body itself: 4 of the 34 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 177, handleDelete, handleRestore, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
githubImport.importGitHubSkillForUser (cognitive 33) convex/githubImport.ts:250— githubImport.importGitHubSkillForUser has cognitive complexity 33 (threshold 15). Drivers by points: if/else 17 (22 pts), error handling 3 (4 pts), boolean chains 3, ternaries 2 (3 pts), loops 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
githubSkillSync.upsertGitHubSkillCandidate (cognitive 33) convex/githubSkillSync.ts:1501— githubSkillSync.upsertGitHubSkillCandidate has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 6 (10 pts), boolean chains 9 (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.
securityPrompt.parseLlmEvalResponse (cognitive 33) convex/lib/securityPrompt.ts:666— securityPrompt.parseLlmEvalResponse has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 6 (10 pts), boolean chains 7, loops 1 (2 pts), error handling 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.
moderation.cmdRescanAllSkills (cognitive 33) packages/clawhub-admin/src/commands/moderation.ts:434— moderation.cmdRescanAllSkills has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 7 (11 pts), boolean chains 6, 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.
publisherOgSvg.buildPublisherOgSvg (cognitive 33) server/og/publisherOgSvg.ts:268— publisherOgSvg.buildPublisherOgSvg has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 22 (30 pts), boolean chains 3 (nesting depth added 8). Of this number, 32 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
googleAnalytics.getGoogleAnalyticsPage (cognitive 33) src/lib/googleAnalytics.ts:61— googleAnalytics.getGoogleAnalyticsPage has cognitive complexity 33 (threshold 15). Drivers by points: if/else 15 (23 pts), boolean chains 6, ternaries 2 (3 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.
catalogFeed.buildSkillEntry (cognitive 32) convex/catalogFeed.ts:280— catalogFeed.buildSkillEntry has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 10, ternaries 6 (9 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.
aigAnalysis.reusableAigAnalysis (cognitive 32) convex/lib/aigAnalysis.ts:11— aigAnalysis.reusableAigAnalysis has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 10 (16 pts), boolean chains 8, if/else 6 (7 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
usersV1.handleAdminUpdatePublisherProfile (cognitive 32) convex/httpApiV1/usersV1.ts:848— usersV1.handleAdminUpdatePublisherProfile has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (17 pts), ternaries 6 (7 pts), boolean chains 5, error handling 3 (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.
skillCardClaims.admitSkillCardClaims (cognitive 32) convex/lib/skillCardClaims.ts:70— skillCardClaims.admitSkillCardClaims has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 5 (9 pts), boolean chains 4 (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.
HomeListingSection.HomeListingEmptyPanel (cognitive 32) src/components/HomeListingSection.tsx:51— HomeListingSection.HomeListingEmptyPanel has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 13 (31 pts), boolean chains 1 (nesting depth added 18). 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.
clawpack.parseTarEntries (cognitive 31) packages/clawhub/src/clawpack.ts:99— clawpack.parseTarEntries has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (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.
packages.latestCompletedFindingsScans (cognitive 31) convex/packages.ts:3529— packages.latestCompletedFindingsScans has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 7, loops 3 (4 pts), ternaries 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.
packages.listStablePackageDiscoveryPage (cognitive 31) convex/packages.ts:3818— packages.listStablePackageDiscoveryPage has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 7 (11 pts), boolean chains 4, loops 3 (nesting depth added 9). Of this number, 18 points are the body's own statements and 13 belong to 2 function items 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.
packagesV1.mintPublishTokenV1Handler (cognitive 31) convex/httpApiV1/packagesV1.ts:2420— packagesV1.mintPublishTokenV1Handler has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 13 (14 pts), if/else 8 (11 pts), boolean chains 3, error handling 3 (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.
promotions.normalizePromotionInput (cognitive 31) convex/promotions.ts:104— promotions.normalizePromotionInput has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (17 pts), ternaries 7, boolean chains 5, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skillsShCatalogV1.storeArtifactFiles (cognitive 31) convex/httpApiV1/skillsShCatalogV1.ts:533— skillsShCatalogV1.storeArtifactFiles has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 2 (6 pts), boolean chains 3, loops 2 (3 pts), error handling 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.
skillsShCatalog.cancelAttempt (cognitive 31) convex/skillsShCatalog.ts:2952— skillsShCatalog.cancelAttempt has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 2 (8 pts), boolean chains 6 (nesting depth added 15). 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.
email.cmdSendStaffEmail (cognitive 31) packages/clawhub-admin/src/commands/email.ts:120— email.cmdSendStaffEmail has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (17 pts), ternaries 10 (11 pts), boolean chains 3 (nesting depth added 8). Of this number, 25 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.
skillDetailUtils.formatConfigSnippet (cognitive 31) src/components/skillDetailUtils.ts:17— skillDetailUtils.formatConfigSnippet has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (23 pts), boolean chains 6, error handling 1, 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.
PromotionsPage.PromotionsPage (cognitive 31) src/routes/-management/PromotionsPage.tsx:171— PromotionsPage.PromotionsPage has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 15 (27 pts), boolean chains 2, if/else 2 (nesting depth added 12). Most of this is not in the body itself: 13 of the 31 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 232, submit, a function literal at line 212, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
-SkillsResults.SkillsResults (cognitive 31) src/routes/skills/-SkillsResults.tsx:125— -SkillsResults.SkillsResults has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 9 (21 pts), if/else 2 (8 pts), boolean chains 2 (nesting depth added 18). Of this number, 23 points are the body's own statements and 8 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.
publish.Upload::handleSubmit (cognitive 31) src/routes/skills/publish.tsx:669— publish.Upload::handleSubmit has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 10, ternaries 6 (7 pts), error handling 1, loops 1 (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. This shape REPEATS in the file: one other method here (publish.Upload) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
skillZip.buildOrderedZipStream::advance (cognitive 30) convex/lib/skillZip.ts:156— skillZip.buildOrderedZipStream::advance has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 2 (3 pts), boolean chains 2 (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.
githubActionsOidc.verifyGitHubActionsWorkflowJwt (cognitive 30) convex/lib/githubActionsOidc.ts:135— githubActionsOidc.verifyGitHubActionsWorkflowJwt has cognitive complexity 30 (threshold 15). Drivers by points: if/else 18 (20 pts), ternaries 6, boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
packages.resolveDirectPackageSearchDigests (cognitive 30) convex/packages.ts:1475— packages.resolveDirectPackageSearchDigests has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 19 (28 pts), boolean chains 2 (nesting depth added 9). Of this number, 23 points are the body's own statements and 7 belong to 4 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.
publisherAbuseDevSeed.clearDemoRows (cognitive 30) convex/publisherAbuseDevSeed.ts:732— publisherAbuseDevSeed.clearDemoRows has cognitive complexity 30 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 9 (13 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.
publishers.migrateLegacyPublisherHandleToOrgWithActor (cognitive 30) convex/publishers.ts:1192— publishers.migrateLegacyPublisherHandleToOrgWithActor has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 8, ternaries 3 (4 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
managedMcp.parseManagedMcpDefinition (cognitive 30) packages/schema/src/managedMcp.ts:37— managedMcp.parseManagedMcpDefinition has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 9, error handling 1 (2 pts), loops 2 (nesting depth added 5). 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.
convexProxy.parseSkillArchiveManifest (cognitive 30) server/convexProxy.ts:521— convexProxy.parseSkillArchiveManifest has cognitive complexity 30 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 9, error handling 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
packageRegistry.extractMcpServerSummaries (cognitive 29) convex/lib/packageRegistry.ts:273— packageRegistry.extractMcpServerSummaries has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 13 (17 pts), boolean chains 8, error handling 1 (2 pts), if/else 2 (nesting depth added 5). None of this is in the body itself: all 29 points belong to one function literal inside it that branches (line 275). 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.
skillPageRead.readSkillPageBySlug (cognitive 29) convex/lib/skillPageRead.ts:243— skillPageRead.readSkillPageBySlug has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 13 (14 pts), boolean chains 9, if/else 6 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
githubSkillSync.scheduleGitHubSkillVerification (cognitive 29) convex/githubSkillSync.ts:1958— githubSkillSync.scheduleGitHubSkillVerification has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 7, ternaries 4 (6 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
mcpPublicInspection.inspectPublicMcp (cognitive 29) convex/lib/mcpPublicInspection.ts:181— mcpPublicInspection.inspectPublicMcp has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 4 (9 pts), boolean chains 6, error handling 1 (nesting depth added 9). Of this number, 26 points are the body's own statements and 3 belong to one function item 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.
packages.cmdPackageModerationQueue (cognitive 29) packages/clawhub-admin/src/commands/packages.ts:417— packages.cmdPackageModerationQueue has cognitive complexity 29 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 3 (9 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
rolloutCapabilities.getClawHubRuntimeEnvironment (cognitive 29) packages/schema/src/rolloutCapabilities.ts:75— rolloutCapabilities.getClawHubRuntimeEnvironment has cognitive complexity 29 (threshold 15). Drivers by points: if/else 16, boolean chains 13. 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.
CatalogMetadataFields.CatalogMetadataFields (cognitive 29) src/components/CatalogMetadataFields.tsx:35— CatalogMetadataFields.CatalogMetadataFields has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 17 (24 pts), if/else 3, boolean chains 2 (nesting depth added 7). Of this number, 20 points are the body's own statements and 9 belong to 3 function items 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.
SkillCardPreview.SkillCardPreview (cognitive 29) src/components/SkillCardPreview.tsx:130— SkillCardPreview.SkillCardPreview has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 17 (27 pts), boolean chains 1, if/else 1 (nesting depth added 10). Of this number, 19 points are the body's own statements and 10 belong to 4 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.
ManagedMcpTools.ManagedMcpTools (cognitive 29) src/routes/-management/ManagedMcpTools.tsx:36— ManagedMcpTools.ManagedMcpTools has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 12 (15 pts), if/else 6 (7 pts), boolean chains 5, error handling 2 (nesting depth added 4). Of this number, 15 points are the body's own statements and 14 belong to 6 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
skillBackfill.deepEqual (cognitive 28) convex/lib/skillBackfill.ts:49— skillBackfill.deepEqual has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 4, loops 2 (4 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.
maintenance.backfillSkillFingerprintsInternalHandler (cognitive 28) convex/maintenance.ts:1952— maintenance.backfillSkillFingerprintsInternalHandler has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 14). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
maintenance.backfillSkillBadgeTableInternalHandler (cognitive 28) convex/maintenance.ts:2293— maintenance.backfillSkillBadgeTableInternalHandler has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 3 (6 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.
packages.waitForPackagePublication (cognitive 28) packages/clawhub/src/cli/commands/packages.ts:1248— packages.waitForPackagePublication has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (20 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts), loops 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.
cli.findFirstTopLevelOperand (cognitive 28) packages/clawhub/src/cli.ts:135— cli.findFirstTopLevelOperand has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 4, loops 1 (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.
MarketplaceIcon.MarketplaceIcon (cognitive 28) src/components/MarketplaceIcon.tsx:45— MarketplaceIcon.MarketplaceIcon has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 14 (18 pts), boolean chains 9, if/else 1 (nesting depth added 4). Of this number, 21 points are the body's own statements and 7 belong to 4 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
packages.restorePackageDoc (cognitive 27) convex/packages.ts:5680— packages.restorePackageDoc has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 7, ternaries 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
usersV1.handleAdminRecoverPersonalPublisher (cognitive 27) convex/httpApiV1/usersV1.ts:730— usersV1.handleAdminRecoverPersonalPublisher has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 9 (10 pts), boolean chains 1, error handling 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
skillsShCatalog.validateRealScanArtifacts (cognitive 27) convex/skillsShCatalog.ts:2852— skillsShCatalog.validateRealScanArtifacts has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 3, loops 2 (3 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.
searchInsights.waitForReport (cognitive 27) packages/clawhub-admin/src/commands/searchInsights.ts:244— searchInsights.waitForReport has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 3 (9 pts), boolean chains 3, error handling 1 (2 pts), 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.
skillsShCatalogSource.fetchSkillsShProofText (cognitive 27) server/skillsShCatalogSource.ts:1805— skillsShCatalogSource.fetchSkillsShProofText has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 2 (3 pts), ternaries 1 (3 pts), boolean chains 2 (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.
index.parseFrontmatterLevelDeclarations (cognitive 26) convex/lib/skills/index.ts:261— index.parseFrontmatterLevelDeclarations has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (21 pts), boolean chains 3, ternaries 2 (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.
skillPresentation.isStructurallyValidJpeg (cognitive 26) convex/lib/skillPresentation.ts:238— skillPresentation.isStructurallyValidJpeg has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 6, loops 2 (3 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.
githubSkillSync.buildGitHubSkillSyncPlan (cognitive 26) convex/lib/githubSkillSync.ts:334— githubSkillSync.buildGitHubSkillSyncPlan has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 4 (7 pts), boolean chains 3, 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.
packagePublishRecovery.assertPackageRecoveryEligibility (cognitive 26) convex/lib/packagePublishRecovery.ts:196— packagePublishRecovery.assertPackageRecoveryEligibility has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 10, loops 1 (2 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skillPublish.prepareSkillInsertArgsForFinalization (cognitive 26) convex/lib/skillPublish.ts:636— skillPublish.prepareSkillInsertArgsForFinalization has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 7 (8 pts), boolean chains 6, loops 1 (nesting depth added 5). Of this number, 23 points are the body's own statements and 3 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.
skills.listSkillTopicFilteredPage (cognitive 26) convex/skills.ts:5019— skills.listSkillTopicFilteredPage has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (16 pts), ternaries 4, boolean chains 3, loops 2 (3 pts) (nesting depth added 11). Of this number, 25 points are the body's own statements and 1 belongs to 2 function items 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.
skills.collectSkillPackageCatalogPage (cognitive 26) convex/skills.ts:5676— skills.collectSkillPackageCatalogPage has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 5, loops 2 (3 pts), ternaries 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.
skillsV1.parseSecurityVerdictItems (cognitive 26) convex/httpApiV1/skillsV1.ts:860— skillsV1.parseSecurityVerdictItems has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 5, ternaries 2 (4 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
registryOgSvg.wrapText (cognitive 26) server/og/registryOgSvg.ts:102— registryOgSvg.wrapText has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (17 pts), ternaries 2 (4 pts), boolean chains 3, loops 2 (nesting depth added 8). Of this number, 19 points are the body's own statements and 7 belong to 2 function items 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.
import.ReviewSkillCard (cognitive 26) src/routes/import.tsx:1225— import.ReviewSkillCard has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 13 (19 pts), boolean chains 7 (nesting depth added 6). Of this number, 21 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PromotionsPage.parseForm (cognitive 26) src/routes/-management/PromotionsPage.tsx:110— PromotionsPage.parseForm has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 11 (13 pts), if/else 6 (10 pts), boolean chains 2, 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.
devSeed.retireLegacyLocalOwnerPublishers (cognitive 25) convex/devSeed.ts:642— devSeed.retireLegacyLocalOwnerPublishers has cognitive complexity 25 (threshold 15). Drivers by points: loops 8 (18 pts), if/else 3 (7 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.
openaiResponse.extractResponseText (cognitive 25) convex/lib/openaiResponse.ts:1— openaiResponse.extractResponseText has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 5, loops 2 (3 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.
packages.listPackageInspectorScanBatch (cognitive 25) convex/packages.ts:10277— packages.listPackageInspectorScanBatch has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 9, ternaries 2 (5 pts), 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.
skillPageRead.resolveSkillBySlugOrAliasForOwner (cognitive 25) convex/lib/skillPageRead.ts:164— skillPageRead.resolveSkillBySlugOrAliasForOwner has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (21 pts), boolean chains 4 (nesting depth added 12). 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.
packagesV1.packagesDeleteRouterV1Handler (cognitive 25) convex/httpApiV1/packagesV1.ts:3321— packagesV1.packagesDeleteRouterV1Handler has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 3 (5 pts), boolean chains 2, ternaries 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.
maintenance.nominateEmptySkillSpammersInternalHandler (cognitive 25) convex/maintenance.ts:2804— maintenance.nominateEmptySkillSpammersInternalHandler has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (5 pts), boolean chains 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.
publisherAbuseOwnerSynchrony.getPublisherAbuseOwnerSynchronyCandidateInternalHandler (cognitive 25) convex/publisherAbuseOwnerSynchrony.ts:229— publisherAbuseOwnerSynchrony.getPublisherAbuseOwnerSynchronyCandidateInternalHandler has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 2 (3 pts), boolean chains 2, ternaries 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.
publisherAbuseTemporalScan.runScheduledTemporalPublisherAbuseScanInternalHandler (cognitive 25) convex/publisherAbuseTemporalScan.ts:1061— publisherAbuseTemporalScan.runScheduledTemporalPublisherAbuseScanInternalHandler has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 5 (9 pts), error handling 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.
orgs.cmdRepairScopedPackages (cognitive 25) packages/clawhub-admin/src/commands/orgs.ts:453— orgs.cmdRepairScopedPackages has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 6 (12 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (3 pts), if/else 3 (nesting depth added 10). Most of this is not in the body itself: 5 of the 25 points are its own statements and the rest belongs to one function literal inside it that branches (line 471). 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.
skillsShCatalogSource.resolveSkillsShMirrorGitHubLocators (cognitive 25) server/skillsShCatalogSource.ts:1177— skillsShCatalogSource.resolveSkillsShMirrorGitHubLocators has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 5, loops 2 (3 pts) (nesting depth added 11). None of this is in the body itself: all 25 points belong to 4 function literals inside it that branch (lines 1218, 1197, 1244, …). 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.
srcset.parseSrcset (cognitive 25) src/lib/srcset.ts:10— srcset.parseSrcset has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 5 (10 pts), boolean chains 4 (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.
SkillListingRow.SkillListingRow (cognitive 25) src/components/SkillListingRow.tsx:34— SkillListingRow.SkillListingRow has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 15 (21 pts), boolean chains 4 (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.
embeddings.generateEmbeddings (cognitive 24) convex/lib/embeddings.ts:71— embeddings.generateEmbeddings has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), error handling 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.
skills.listCommunitySkillCategoryPage (cognitive 24) convex/skills.ts:6420— skills.listCommunitySkillCategoryPage has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (17 pts), loops 2 (3 pts), boolean chains 2, ternaries 2 (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.
skills.renameOwnedSkillByActor (cognitive 24) convex/skills.ts:9195— skills.renameOwnedSkillByActor has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (13 pts), boolean chains 7, ternaries 2 (4 pts) (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.
securityPrompt.parseAgenticRiskFindings (cognitive 24) convex/lib/securityPrompt.ts:559— securityPrompt.parseAgenticRiskFindings has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 7, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
templatePackageHttpRead.readTemplatePackageHttp (cognitive 24) convex/lib/templatePackageHttpRead.ts:36— templatePackageHttpRead.readTemplatePackageHttp has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (17 pts), boolean chains 5, error handling 1, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
mcpPublicInspection.readJson (cognitive 24) convex/lib/mcpPublicInspection.ts:20— mcpPublicInspection.readJson has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (4 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.
pluginCategories.inferPluginCategoriesFromManifest (cognitive 24) packages/schema/src/pluginCategories.ts:73— pluginCategories.inferPluginCategoriesFromManifest has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13, boolean chains 9, ternaries 2. Of this number, 23 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skillsShCatalogSource.fetchSkillsShMirrorBatch (cognitive 24) server/skillsShCatalogSource.ts:2193— skillsShCatalogSource.fetchSkillsShMirrorBatch has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), error handling 2 (4 pts), boolean chains 3, ternaries 3, loops 1 (nesting depth added 8). Most of this is not in the body itself: 6 of the 24 points are its own statements and the rest belongs to 2 function items inside it that branch (a function literal at line 2262, monitoredFetch). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
BrowseControls.BrowseCategorySelect (cognitive 24) src/components/BrowseControls.tsx:399— BrowseControls.BrowseCategorySelect has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 10 (18 pts), if/else 5, boolean chains 1 (nesting depth added 8). Of this number, 14 points are the body's own statements and 10 belong to 7 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.
BrowseResultsSkeleton.BrowseResultsSkeleton (cognitive 24) src/components/skeletons/BrowseResultsSkeleton.tsx:12— BrowseResultsSkeleton.BrowseResultsSkeleton has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 13 (23 pts), if/else 1 (nesting depth added 10). Of this number, 14 points are the body's own statements and 10 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.
SkillCard.SkillCard (cognitive 24) src/components/SkillCard.tsx:27— SkillCard.SkillCard has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 13 (20 pts), boolean chains 4 (nesting depth added 7). Of this number, 22 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.
AbusePage.PublisherAbuseSignalInspector (cognitive 24) src/routes/-management/AbusePage.tsx:993— AbusePage.PublisherAbuseSignalInspector has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 17 (24 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
-useSkillsBrowseModel.useSkillsBrowseModel.fetchPage (cognitive 24) src/routes/skills/-useSkillsBrowseModel.ts:181— -useSkillsBrowseModel.useSkillsBrowseModel.fetchPage has cognitive complexity 24 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 4 (8 pts), boolean chains 3, error handling 1, loops 1 (nesting depth added 10). Of this number, 22 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.
canonicalTrending.blendCanonicalTrendingPools (cognitive 23) convex/lib/canonicalTrending.ts:414— canonicalTrending.blendCanonicalTrendingPools has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 4 (5 pts), boolean chains 3 (nesting depth added 9). Of this number, 15 points are the body's own statements and 8 belong to 2 function items 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.
catalogClassifier.scoreTextCategory (cognitive 23) convex/lib/catalogClassifier.mjs:1601— catalogClassifier.scoreTextCategory has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 4, 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.
catalogTextMatch.matchCatalogText (cognitive 23) convex/lib/catalogTextMatch.ts:25— catalogTextMatch.matchCatalogText has cognitive complexity 23 (threshold 15). Drivers by points: if/else 19, boolean chains 4. 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.
openClawPublishAuthorization.validateParentState (cognitive 23) convex/lib/openClawPublishAuthorization.ts:543— openClawPublishAuthorization.validateParentState has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 16, if/else 5 (7 pts) (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
packages.buildPackagePluginCategoryDigestQuery (cognitive 23) convex/packages.ts:1690— packages.buildPackagePluginCategoryDigestQuery has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 6, ternaries 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.
packages.insertPackageInspectorFindings (cognitive 23) convex/packages.ts:9950— packages.insertPackageInspectorFindings has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 7, ternaries 3 (4 pts), loops 2 (3 pts) (nesting depth added 6). 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.
featuredIntelligence.readMonthlyAdoption (cognitive 23) convex/featuredIntelligence.ts:193— featuredIntelligence.readMonthlyAdoption has cognitive complexity 23 (threshold 15). Drivers by points: if/else 17 (38 pts), loops 7 (11 pts), boolean chains 5, ternaries 1 (3 pts), error handling 1 (nesting depth added 27). 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. This shape REPEATS in the file: one other method here (featuredIntelligence.readMonthlyAdoption::readPage) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
searchReportsV1.searchReportsV1Handler (cognitive 23) convex/httpApiV1/searchReportsV1.ts:12— searchReportsV1.searchReportsV1Handler has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (12 pts), error handling 4 (7 pts), boolean chains 4 (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.
migrations.classifySuspiciousPublishAttemptPublicState (cognitive 23) convex/migrations.ts:446— migrations.classifySuspiciousPublishAttemptPublicState has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5, ternaries 3 (4 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.
securityScan.requestSkillRescanForActor (cognitive 23) convex/securityScan.ts:903— securityScan.requestSkillRescanForActor has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 3 (5 pts), boolean chains 4 (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.
skillsShClaims.applySkillsShTestClaimVerdictHandler (cognitive 23) convex/skillsShClaims.ts:294— skillsShClaims.applySkillsShTestClaimVerdictHandler has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 5, boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
skills.cmdSearch (cognitive 23) packages/clawhub/src/cli/commands/skills.ts:296— skills.cmdSearch has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 4 (5 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 5). Most of this is not in the body itself: 6 of the 23 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 313, 347). 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.
packages.cmdExportPackageValidationReport (cognitive 23) packages/clawhub-admin/src/commands/packages.ts:132— packages.cmdExportPackageValidationReport has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 4 (6 pts), ternaries 2 (4 pts), boolean chains 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.
experimentalTemplateFeed.parseExperimentalTemplateFeed (cognitive 23) packages/schema/src/experimentalTemplateFeed.ts:52— experimentalTemplateFeed.parseExperimentalTemplateFeed has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 2 (3 pts), boolean chains 2 (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.
skillsShCatalogSource.buildSkillsShMirrorObservation (cognitive 23) server/skillsShCatalogSource.ts:747— skillsShCatalogSource.buildSkillsShMirrorObservation has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 7, ternaries 6, error handling 1 (2 pts) (nesting depth added 4). Of this number, 22 points are the body's own statements and 1 belongs to one function item 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.
SkillDiffCard.cssColor4ToHex (cognitive 23) src/components/SkillDiffCard.tsx:894— SkillDiffCard.cssColor4ToHex has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 6 (9 pts), boolean chains 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.
catalogClassificationNode.classifyCatalogInternalHandler (cognitive 22) convex/catalogClassificationNode.ts:131— catalogClassificationNode.classifyCatalogInternalHandler has cognitive complexity 22 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (7 pts), error handling 1 (3 pts), loops 2 (3 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.
catalogFeed.buildEntry (cognitive 22) convex/catalogFeed.ts:162— catalogFeed.buildEntry has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 6, ternaries 4 (5 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
packageCatalogRead.digestMatchesFilters (cognitive 22) convex/lib/packageCatalogRead.ts:148— packageCatalogRead.digestMatchesFilters has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 5 (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.
packageSdkUsage.recordPackageInspectorScan (cognitive 22) convex/lib/packageSdkUsage.ts:101— packageSdkUsage.recordPackageInspectorScan has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 9 (13 pts), boolean chains 6, if/else 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
packages.takeVisiblePackageCategoryDigestPage (cognitive 22) convex/packages.ts:1925— packages.takeVisiblePackageCategoryDigestPage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4, ternaries 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
canonicalSkillSearchResponse.serializeCanonicalSkillSearchResults (cognitive 22) convex/lib/canonicalSkillSearchResponse.ts:37— canonicalSkillSearchResponse.serializeCanonicalSkillSearchResults has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 14 (18 pts), if/else 2 (3 pts), boolean chains 1 (nesting depth added 5). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 38). 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.
featuredV1.featuredV1Handler (cognitive 22) convex/httpApiV1/featuredV1.ts:20— featuredV1.featuredV1Handler has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 3 (4 pts), error handling 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
skillsV1.skillScanGetRouterV1Handler (cognitive 22) convex/httpApiV1/skillsV1.ts:1200— skillsV1.skillScanGetRouterV1Handler has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (6 pts), boolean chains 3, error handling 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.
skillsV1.listSkillsV1Handler (cognitive 22) convex/httpApiV1/skillsV1.ts:1447— skillsV1.listSkillsV1Handler has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 8, ternaries 7 (8 pts), if/else 6 (nesting depth added 1). Of this number, 20 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
usersV1.handleAdminReserve (cognitive 22) convex/httpApiV1/usersV1.ts:615— usersV1.handleAdminReserve has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 7 (11 pts), error handling 2 (4 pts), if/else 4, loops 2, boolean chains 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.
skillsShCatalogSource.fetchSkillsShMirrorControlledBatch (cognitive 22) server/skillsShCatalogSource.ts:2352— skillsShCatalogSource.fetchSkillsShMirrorControlledBatch has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 8). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 2382). 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.
SkillSecurityScanResults.SkillSpectorContent (cognitive 22) src/components/SkillSecurityScanResults.tsx:276— SkillSecurityScanResults.SkillSpectorContent has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 13 (15 pts), boolean chains 6, if/else 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
HomePopularPublishersSection.HomePopularPublishersSection (cognitive 22) src/components/HomePopularPublishersSection.tsx:45— HomePopularPublishersSection.HomePopularPublishersSection has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 4, ternaries 2, error handling 1 (nesting depth added 2). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 61, handlePointerMove, handlePointerDown, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
DashboardDownloadsInsights.DashboardDownloadsInsights (cognitive 22) src/components/dashboard/DashboardDownloadsInsights.tsx:36— DashboardDownloadsInsights.DashboardDownloadsInsights has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 13 (18 pts), boolean chains 3, if/else 1 (nesting depth added 5). Of this number, 17 points are the body's own statements and 5 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.
DashboardNeedsAttention.DashboardNeedsAttention (cognitive 22) src/components/dashboard/DashboardNeedsAttention.tsx:73— DashboardNeedsAttention.DashboardNeedsAttention has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 6 (7 pts), boolean chains 2 (nesting depth added 4). Most of this is not in the body itself: 9 of the 22 points are its own statements and the rest belongs to 7 function literals inside it that branch (lines 145, 83, 105, …). 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.
ReportsPage.ReportsPage (cognitive 22) src/routes/-management/ReportsPage.tsx:6— ReportsPage.ReportsPage has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 8 (22 pts) (nesting depth added 14). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 49, 70). 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.
-useSkillsBrowseModel.useSkillsBrowseModel.sorted (cognitive 22) src/routes/skills/-useSkillsBrowseModel.ts:359— -useSkillsBrowseModel.useSkillsBrowseModel.sorted has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 9, ternaries 9, if/else 3, match/switch 1. Most of this is not in the body itself: 5 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 385, 362, 370, …). 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.
downloads.parseArchiveMetricPayload (cognitive 21) convex/downloads.ts:446— downloads.parseArchiveMetricPayload has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11, boolean chains 10. 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.
githubImport.parseGitHubImportUrl (cognitive 21) convex/lib/githubImport.ts:43— githubImport.parseGitHubImportUrl has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 5, error handling 2 (nesting depth added 3). 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.
skillPresentation.resolveSkillPresentation (cognitive 21) convex/lib/skillPresentation.ts:72— skillPresentation.resolveSkillPresentation has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 9 (18 pts), boolean chains 3 (nesting depth added 9). 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 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.
packageSdkUsage.replacePackageSdkUsage (cognitive 21) convex/lib/packageSdkUsage.ts:182— packageSdkUsage.replacePackageSdkUsage has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (10 pts), boolean chains 4, if/else 4, loops 3 (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 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.
packages.listOfficialFirstPackageCategoryPage (cognitive 21) convex/packages.ts:4356— packages.listOfficialFirstPackageCategoryPage has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 3 (5 pts), boolean chains 2 (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.
skills.updateSkillTagsForActor (cognitive 21) convex/skills.ts:8526— skills.updateSkillTagsForActor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 3, loops 3, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
packagesV1.parseMultipartPackagePublish (cognitive 21) convex/httpApiV1/packagesV1.ts:1060— packagesV1.parseMultipartPackagePublish has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 2 (4 pts), boolean chains 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.
publisherCatalogDisplay.buildGitHubSkillCatalogDisplay (cognitive 21) convex/lib/publisherCatalogDisplay.ts:91— publisherCatalogDisplay.buildGitHubSkillCatalogDisplay has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 3 (6 pts), ternaries 4 (5 pts), boolean chains 3 (nesting depth added 7). Of this number, 19 points are the body's own statements and 2 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.
maintenance.backfillUserStatsInternalHandler (cognitive 21) convex/maintenance.ts:1152— maintenance.backfillUserStatsInternalHandler has cognitive complexity 21 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 4 (10 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.
publisherAbuse.hasStaffPublisherManager (cognitive 21) convex/publisherAbuse.ts:2287— publisherAbuse.hasStaffPublisherManager has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (17 pts), loops 2 (3 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.
deviceAuth.pollForDeviceToken (cognitive 21) packages/clawhub/src/deviceAuth.ts:92— deviceAuth.pollForDeviceToken has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 1 (2 pts), match/switch 1 (2 pts), boolean chains 1, loops 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.
packages.cmdExplorePackages (cognitive 21) packages/clawhub/src/cli/commands/packages.ts:316— packages.cmdExplorePackages has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 3 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 1 of the 21 points is its own statement and the rest belongs to one function literal inside it that branches (line 325). 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.
moderation.cmdRecoverPersonalPublisher (cognitive 21) packages/clawhub-admin/src/commands/moderation.ts:282— moderation.cmdRecoverPersonalPublisher has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 5 (6 pts), boolean chains 3 (nesting depth added 4). Of this number, 15 points are the body's own statements and 6 belong 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.
skillsShCatalogSource.buildSkillsShMirrorUpstreamScanners (cognitive 21) server/skillsShCatalogSource.ts:425— skillsShCatalogSource.buildSkillsShMirrorUpstreamScanners has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
convexProxy.parseSkillExportArchiveManifest (cognitive 21) server/convexProxy.ts:572— convexProxy.parseSkillExportArchiveManifest has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Header.SearchTypeahead (cognitive 21) src/components/Header.tsx:893— Header.SearchTypeahead has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 11 (14 pts), boolean chains 7 (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.
SkillDetailPage.buildStaffVisibilityAlert (cognitive 21) src/components/SkillDetailPage.tsx:121— SkillDetailPage.buildStaffVisibilityAlert has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16, boolean chains 5. 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.
DownloadsPage.DownloadsPage (cognitive 21) src/routes/-management/DownloadsPage.tsx:27— DownloadsPage.DownloadsPage has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 13, boolean chains 5, if/else 2, error handling 1. Of this number, 16 points are the body's own statements and 5 belong to 4 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
addTopicTextEvidence (cognitive 21) convex/lib/catalogClassifier.mjs:1834— addTopicTextEvidence has cognitive complexity 21 (threshold 15). Drivers by points: if/else 2 (6 pts), ternaries 2 (6 pts), loops 3 (5 pts), other 4 (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.
skillMarkdown.toJsonValue (cognitive 20) convex/lib/skills/skillMarkdown.ts:175— skillMarkdown.toJsonValue has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 3 (6 pts), loops 1 (2 pts) (nesting depth added 6). Of this number, 18 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.
packageCatalogRead.packageMatchesListFilters (cognitive 20) convex/lib/packageCatalogRead.ts:275— packageCatalogRead.packageMatchesListFilters has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 8 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
publishAttemptOperationalRecovery.retryFailedPublishAttemptChecks (cognitive 20) convex/lib/publishAttemptOperationalRecovery.ts:255— publishAttemptOperationalRecovery.retryFailedPublishAttemptChecks has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9, boolean chains 8, ternaries 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
skills.isOwnerInitiatedSkillHideForAdminTransfer (cognitive 20) convex/skills.ts:11385— skills.isOwnerInitiatedSkillHideForAdminTransfer has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 7, ternaries 3 (4 pts), error handling 1 (nesting depth added 3). Of this number, 13 points are the body's own statements and 7 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.
packagesV1.buildPackageReadiness (cognitive 20) convex/httpApiV1/packagesV1.ts:4598— packagesV1.buildPackageReadiness has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 14 (15 pts), boolean chains 5 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
packageInspectorHttp.packageInspectorArtifactHttp (cognitive 20) convex/packageInspectorHttp.ts:138— packageInspectorHttp.packageInspectorArtifactHttp has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 2 (3 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
managedMcpBundle.buildManagedMcpBundle (cognitive 20) convex/lib/managedMcpBundle.ts:29— managedMcpBundle.buildManagedMcpBundle has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 14 (19 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
userSearch.scoreUser (cognitive 20) convex/lib/userSearch.ts:21— userSearch.scoreUser has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (16 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.
publishers.getUserPublisherOgAffiliations (cognitive 20) convex/publishers.ts:1002— publishers.getUserPublisherOgAffiliations has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 3, loops 2 (3 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.
moderation.cmdReclassifyBan (cognitive 20) packages/clawhub-admin/src/commands/moderation.ts:640— moderation.cmdReclassifyBan has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 5 (6 pts), boolean chains 2 (nesting depth added 3). Of this number, 15 points are the body's own statements and 5 belong 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.
packages.cmdListPackageMigrations (cognitive 20) packages/clawhub-admin/src/commands/packages.ts:566— packages.cmdListPackageMigrations has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
inspect.cmdVerifySkill (cognitive 20) packages/clawhub/src/cli/commands/inspect.ts:293— inspect.cmdVerifySkill has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 3, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 7 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 310). 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.
skillsShCatalogSource.parseSkillsShMirrorProofSnapshotId (cognitive 20) server/skillsShCatalogSource.ts:159— skillsShCatalogSource.parseSkillsShMirrorProofSnapshotId has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 4, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CatalogTopicInput.CatalogTopicInput (cognitive 20) src/components/CatalogTopicInput.tsx:55— CatalogTopicInput.CatalogTopicInput has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 5 (7 pts), boolean chains 4 (nesting depth added 3). Most of this is not in the body itself: 8 of the 20 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 148, commitDraft, a function literal at line 98, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
SkillOwnershipPanel.SkillOwnershipPanel (cognitive 20) src/components/SkillOwnershipPanel.tsx:105— SkillOwnershipPanel.SkillOwnershipPanel has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8, boolean chains 7, error handling 3, if/else 2. Of this number, 11 points are the body's own statements and 9 belong to 4 function items inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
$name.buildValidationAgentFixPrompt::appendFindings (cognitive 20) src/routes/plugins/$name.tsx:772— $name.buildValidationAgentFixPrompt::appendFindings has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 3 (6 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
$name.PluginValidationFindingCard (cognitive 20) src/routes/plugins/$name.tsx:876— $name.PluginValidationFindingCard has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 13 (17 pts), boolean chains 2, if/else 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
httpRateLimit.applyRateLimit (cognitive 19) convex/lib/httpRateLimit.ts:91— httpRateLimit.applyRateLimit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 3 (6 pts), boolean chains 3 (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.
shared.parseMultipartPublish (cognitive 19) convex/httpApiV1/shared.ts:395— shared.parseMultipartPublish has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 11, boolean chains 3, error handling 2, if/else 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.
packages.transferPackageOwnerForUser (cognitive 19) convex/packages.ts:9548— packages.transferPackageOwnerForUser has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 9 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
featuredIntelligence.readMonthlyAdoption::readPage (cognitive 19) convex/featuredIntelligence.ts:212— featuredIntelligence.readMonthlyAdoption::readPage has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (2 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. This shape REPEATS in the file: one other method here (featuredIntelligence.readMonthlyAdoption) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
skillQuality.evaluateQuality (cognitive 19) convex/lib/skillQuality.ts:157— skillQuality.evaluateQuality has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (12 pts), boolean chains 4, if/else 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
skills.revokeSkillVersionForUser (cognitive 19) convex/skills.ts:8022— skills.revokeSkillVersionForUser has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 3 (5 pts), boolean chains 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, 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.
githubSkillSync.fetchPublicGitHubRepoMetadata (cognitive 19) convex/githubSkillSync.ts:3130— githubSkillSync.fetchPublicGitHubRepoMetadata has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (6 pts), ternaries 6 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
httpRouteRateLimit.resolveDefaultRouteRateLimit (cognitive 19) convex/lib/httpRouteRateLimit.ts:63— httpRouteRateLimit.resolveDefaultRouteRateLimit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 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.
skillsV1.handleTransferRequest (cognitive 19) convex/httpApiV1/skillsV1.ts:2736— skillsV1.handleTransferRequest has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 6 (9 pts), if/else 5, boolean chains 4, error handling 1 (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.
packageInspectorHttp.packageInspectorClaimHttp (cognitive 19) convex/packageInspectorHttp.ts:52— packageInspectorHttp.packageInspectorClaimHttp has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 8, ternaries 8, if/else 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
maintenance.repairLegacyPluginSkillSpectorBatchInternalHandler (cognitive 19) convex/maintenance.ts:1448— maintenance.repairLegacyPluginSkillSpectorBatchInternalHandler has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
migrations.processPluginManifestSummaryBackfillCandidates (cognitive 19) convex/migrations.ts:1315— migrations.processPluginManifestSummaryBackfillCandidates has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 1 (2 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.
publisherAbuseTemporalScan.advanceScheduledTemporalPercentileInternalHandler (cognitive 19) convex/publisherAbuseTemporalScan.ts:344— publisherAbuseTemporalScan.advanceScheduledTemporalPercentileInternalHandler has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 9 (14 pts), if/else 4, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
publishers.ensureOrgPublisherHandleWithActor (cognitive 19) convex/publishers.ts:1349— publishers.ensureOrgPublisherHandleWithActor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 6, ternaries 3 (5 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
users.computeEnsureUpdates (cognitive 19) convex/users.ts:957— users.computeEnsureUpdates has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 7, if/else 6, ternaries 4 (6 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
github.fetchGitHub (cognitive 19) packages/clawhub/src/cli/commands/github.ts:384— github.fetchGitHub has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), error handling 1 (2 pts), loops 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.
packages.cmdListPackageReports (cognitive 19) packages/clawhub-admin/src/commands/packages.ts:316— packages.cmdListPackageReports has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
promotions.cmdListPromotions (cognitive 19) packages/clawhub-admin/src/commands/promotions.ts:51— promotions.cmdListPromotions has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 4 (6 pts), loops 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
publisherOgSvg.wrapTextWithoutEllipsis (cognitive 19) server/og/publisherOgSvg.ts:105— publisherOgSvg.wrapTextWithoutEllipsis has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 3 (5 pts), boolean chains 3, loops 2 (nesting depth added 5). Of this number, 12 points are the body's own statements and 7 belong to 2 function items 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.
profile.png.default (cognitive 19) server/routes/og/profile.png.ts:56— profile.png.default has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, ternaries 7, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
googleAnalytics.createGoogleAnalytics.update (cognitive 19) src/lib/googleAnalytics.ts:327— googleAnalytics.createGoogleAnalytics.update has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 4, ternaries 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
browseTopicSearch.parseBrowseTopicFromSearchInput (cognitive 19) src/lib/browseTopicSearch.ts:22— browseTopicSearch.parseBrowseTopicFromSearchInput has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
stars.Stars (cognitive 19) src/routes/stars.tsx:45— stars.Stars has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 7 (10 pts), if/else 7, boolean chains 2 (nesting depth added 3). Of this number, 15 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, 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.
security-audit.SkillSecurityAuditRoutePage (cognitive 19) src/routes/$owner/$slug/security-audit.tsx:48— security-audit.SkillSecurityAuditRoutePage has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (9 pts), boolean chains 8, if/else 2 (nesting depth added 1). Of this number, 16 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
verifiedClientIp.getVerifiedClientIp (cognitive 18) convex/lib/verifiedClientIp.ts:10— verifiedClientIp.getVerifiedClientIp has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 6, error handling 2 (3 pts) (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.
publishers.assertCanManageOwnedResource (cognitive 18) convex/lib/publishers.ts:130— publishers.assertCanManageOwnedResource has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 4 (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.
githubSkillSync.parseSkillsShDisplayManifest (cognitive 18) convex/lib/githubSkillSync.ts:125— githubSkillSync.parseSkillsShDisplayManifest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6, ternaries 6, boolean chains 5, error handling 1. Of this number, 10 points are the body's own statements and 8 belong to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
clawpack.parseClawPack (cognitive 18) packages/clawhub/src/clawpack.ts:157— clawpack.parseClawPack has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), error handling 3 (4 pts), ternaries 3, boolean chains 1 (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.
packages.toPublicPackage (cognitive 18) convex/packages.ts:939— packages.toPublicPackage has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (8 pts), boolean chains 6, if/else 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
packages.buildPackageTopicDigestQuery (cognitive 18) convex/packages.ts:1793— packages.buildPackageTopicDigestQuery has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 5, ternaries 2 (3 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
packages.getReadablePackageByName (cognitive 18) convex/packages.ts:2081— packages.getReadablePackageByName has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 5, ternaries 2 (4 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.
packages.runPackagePublishPostFinalizeFollowups (cognitive 18) convex/packages.ts:9230— packages.runPackagePublishPostFinalizeFollowups has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (7 pts), if/else 5 (6 pts), error handling 1 (3 pts), boolean chains 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.
featuredArtifacts.readSkill (cognitive 18) convex/featuredArtifacts.ts:95— featuredArtifacts.readSkill has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, ternaries 4 (5 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
skills.compactSecurityVerdictVersion (cognitive 18) convex/skills.ts:2742— skills.compactSecurityVerdictVersion has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 10 (18 pts) (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.
githubSkillSync.syncGitHubSkillSourcesHandler (cognitive 18) convex/githubSkillSync.ts:2842— githubSkillSync.syncGitHubSkillSourcesHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, error handling 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
promotionsV1.promotionsPostRouterV1Handler (cognitive 18) convex/httpApiV1/promotionsV1.ts:224— promotionsV1.promotionsPostRouterV1Handler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), error handling 3 (4 pts), boolean chains 3, ternaries 1 (2 pts) (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.
usersV1.handleAdminOfficialPublisherPost (cognitive 18) convex/httpApiV1/usersV1.ts:694— usersV1.handleAdminOfficialPublisherPost has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 5 (6 pts), boolean chains 1, error handling 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.
maintenance.inspectSkillLineageCycleInternalHandler (cognitive 18) convex/maintenance.ts:3401— maintenance.inspectSkillLineageCycleInternalHandler has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8, boolean chains 7, ternaries 3. Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
pluginCategoryRefresh.readRefreshManifests (cognitive 18) convex/pluginCategoryRefresh.ts:285— pluginCategoryRefresh.readRefreshManifests has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (15 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function item 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.
users.hasStaffPublisherManager (cognitive 18) convex/users.ts:253— users.hasStaffPublisherManager has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (11 pts), loops 3 (6 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.
http.normalizeHttpErrorBody (cognitive 18) packages/clawhub/src/http.ts:638— http.normalizeHttpErrorBody has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 5 (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.
openclawContract.validateOpenClawExternalCodePluginPackageContents (cognitive 18) packages/schema/src/openclawContract.ts:215— openclawContract.validateOpenClawExternalCodePluginPackageContents has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts), boolean chains 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.
skill.png.default (cognitive 18) server/routes/og/skill.png.ts:32— skill.png.default has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 9, ternaries 8, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
rehypeProxyImages.rehypeProxyImages.<returned closure> (cognitive 18) src/lib/rehypeProxyImages.ts:182— rehypeProxyImages.rehypeProxyImages.<returned closure> has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 183). 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.
SecurityAuditPage.inferSkillSpectorPatternCategory (cognitive 18) src/components/SecurityAuditPage.tsx:243— SecurityAuditPage.inferSkillSpectorPatternCategory has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), 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.
SkillDiffCard.applyMonacoTheme (cognitive 18) src/components/SkillDiffCard.tsx:745— SkillDiffCard.applyMonacoTheme has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 17, boolean chains 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.
UsersPage.UsersPage (cognitive 18) src/routes/-management/UsersPage.tsx:14— UsersPage.UsersPage has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 5 (10 pts), boolean chains 4, if/else 2 (4 pts) (nesting depth added 7). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 57, 79, 98). 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.
index.loadPluginsPageData (cognitive 18) src/routes/plugins/index.tsx:136— index.loadPluginsPageData has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 6, if/else 4 (6 pts), ternaries 4 (5 pts), error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
$name.loadPluginDetail (cognitive 18) src/routes/plugins/$name.tsx:163— $name.loadPluginDetail has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (3 pts), loops 2, ternaries 2, boolean chains 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.
packageSecurity.resolvePackageReleaseScanStatus (cognitive 17) convex/lib/packageSecurity.ts:19— packageSecurity.resolvePackageReleaseScanStatus has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 6, ternaries 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.
skillPresentation.isStructurallyValidPng (cognitive 17) convex/lib/skillPresentation.ts:212— skillPresentation.isStructurallyValidPng has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 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.
devSeed.ensureLocalSeedUser (cognitive 17) convex/devSeed.ts:2124— devSeed.ensureLocalSeedUser has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 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.
initialPluginFamilyRead.readInitialPluginFamilyPage (cognitive 17) convex/lib/initialPluginFamilyRead.ts:52— initialPluginFamilyRead.readInitialPluginFamilyPage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 3 (7 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
packageIcons.resolvePackageIcon (cognitive 17) convex/lib/packageIcons.ts:33— packageIcons.resolvePackageIcon has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 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.
packageRuntimeIdentity.assertPackageRuntimeIdAvailable (cognitive 17) convex/lib/packageRuntimeIdentity.ts:6— packageRuntimeIdentity.assertPackageRuntimeIdAvailable has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (8 pts), if/else 4 (6 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.
packages.mayHaveVisiblePackageCategoryDigest (cognitive 17) convex/packages.ts:1877— packages.mayHaveVisiblePackageCategoryDigest has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
skillFileReadAccess.canReadSkillVersionFiles (cognitive 17) convex/lib/skillFileReadAccess.ts:8— skillFileReadAccess.canReadSkillVersionFiles has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 5 (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.
githubImport.toOwnedPublicRepoListItem (cognitive 17) convex/githubImport.ts:578— githubImport.toOwnedPublicRepoListItem has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 11 (14 pts), boolean chains 1, error handling 1, if/else 1 (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.
githubImport.unzipToEntries (cognitive 17) convex/githubImport.ts:877— githubImport.unzipToEntries has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1, loops 1 (nesting depth added 5). 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.
skillsShCatalogEnvironment.getSkillsShFixtureEnvironmentPolicy (cognitive 17) convex/lib/skillsShCatalogEnvironment.ts:55— skillsShCatalogEnvironment.getSkillsShFixtureEnvironmentPolicy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
publishersV1.createPublisherV1Handler (cognitive 17) convex/httpApiV1/publishersV1.ts:12— publishersV1.createPublisherV1Handler has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 4 (5 pts), boolean chains 2, error handling 1 (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.
skillsV1.publishSkillV1Handler (cognitive 17) convex/httpApiV1/skillsV1.ts:2562— skillsV1.publishSkillV1Handler has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 1 (2 pts), error handling 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.
publisherAbuseScoring.classifySkillTemporalAbuseScore (cognitive 17) convex/lib/publisherAbuseScoring.ts:290— publisherAbuseScoring.classifySkillTemporalAbuseScore has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10, if/else 4, boolean chains 3. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
searchIntentClassifier.classifySearchIntent (cognitive 17) convex/lib/searchIntentClassifier.ts:36— searchIntentClassifier.classifySearchIntent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 6, error handling 1, ternaries 1. Of this number, 16 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
maintenance.repairLegacyPublisherOwnershipForUserHandler (cognitive 17) convex/maintenance.ts:4044— maintenance.repairLegacyPublisherOwnershipForUserHandler has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (5 pts), boolean chains 2, 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.
publishers.toPublisherListItem (cognitive 17) convex/publishers.ts:738— publishers.toPublisherListItem has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10 (12 pts), boolean chains 3, if/else 2 (nesting depth added 2). Of this number, 16 points are the body's own statements and 1 belongs to one function item 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.
buildInfo.findGitDir (cognitive 17) packages/clawhub/src/cli/buildInfo.ts:97— buildInfo.findGitDir has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (10 pts), error handling 2 (6 pts), loops 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.
packages.printPackagePublication (cognitive 17) packages/clawhub/src/cli/commands/packages.ts:1891— packages.printPackagePublication has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), ternaries 2 (5 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
skills.resolveSkillsShCatalogInstall (cognitive 17) packages/clawhub/src/cli/commands/skills.ts:1480— skills.resolveSkillsShCatalogInstall has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 5 (8 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
skills.readSkillsShResolverMetadata (cognitive 17) packages/clawhub/src/cli/commands/skills.ts:1527— skills.readSkillsShResolverMetadata has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (7 pts), boolean chains 5, if/else 5 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
orgs.parseCsvRecords (cognitive 17) packages/clawhub-admin/src/commands/orgs.ts:646— orgs.parseCsvRecords has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 6, 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.
packages.cmdHardDeletePackage (cognitive 17) packages/clawhub-admin/src/commands/packages.ts:203— packages.cmdHardDeletePackage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 5 (6 pts), boolean chains 3 (nesting depth added 3). Of this number, 14 points are the body's own statements and 3 belong 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.
inspect.validateSkillsShVerification (cognitive 17) packages/clawhub/src/cli/commands/inspect.ts:353— inspect.validateSkillsShVerification has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, ternaries 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
scan.formatQueueProgress (cognitive 17) packages/clawhub/src/cli/commands/scan.ts:179— scan.formatQueueProgress has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (13 pts), if/else 3, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
convexError.getUserFacingConvexError (cognitive 17) src/lib/convexError.ts:38— convexError.getUserFacingConvexError has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DevPersonaFab.DevPersonaFab (cognitive 17) src/components/DevPersonaFab.tsx:105— DevPersonaFab.DevPersonaFab has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 7 (9 pts), if/else 4 (5 pts), error handling 2, boolean chains 1 (nesting depth added 3). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 3 function items inside it that branch (usePersona, endSession, a function literal at line 184). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
analyticsEvents.analyticsEventParameters (cognitive 17) src/lib/analyticsEvents.ts:225— analyticsEvents.analyticsEventParameters has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
homeListingData.searchHomeTrendingSkillListing (cognitive 17) src/lib/homeListingData.ts:168— homeListingData.searchHomeTrendingSkillListing has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 2 (4 pts), boolean chains 3, error handling 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SecurityAuditPage.AigFindingCard (cognitive 17) src/components/SecurityAuditPage.tsx:698— SecurityAuditPage.AigFindingCard has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 10 (13 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.
SkillCardPreview.parseOutputFields (cognitive 17) src/components/SkillCardPreview.tsx:102— SkillCardPreview.parseOutputFields has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (14 pts), if/else 1 (2 pts), loops 1 (nesting depth added 11). 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.
DashboardDownloadsInsights.Sparkline (cognitive 17) src/components/dashboard/DashboardDownloadsInsights.tsx:239— DashboardDownloadsInsights.Sparkline has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 13 (15 pts), boolean chains 2 (nesting depth added 2). Of this number, 15 points are the body's own statements and 2 belong 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.
dashboardCatalog.defaultDashboardPriority (cognitive 17) src/components/dashboard/dashboardCatalog.ts:120— dashboardCatalog.defaultDashboardPriority has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
functions.repointPackageLatestRelease (cognitive 16) convex/functions.ts:332— functions.repointPackageLatestRelease has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 6, ternaries 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
githubImport.fetchGitHubZipBytes (cognitive 16) convex/lib/githubImport.ts:192— githubImport.fetchGitHubZipBytes has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
catalogClassifier.structuredTopicValues (cognitive 16) convex/lib/catalogClassifier.mjs:1871— catalogClassifier.structuredTopicValues has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (5 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.
skillPublicationProgress.readSkillVersionPublicationProgress (cognitive 16) convex/lib/skillPublicationProgress.ts:36— skillPublicationProgress.readSkillVersionPublicationProgress has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 6 (7 pts), ternaries 1 (nesting depth added 1). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
httpApi.cliPublishHandler (cognitive 16) convex/httpApi.ts:204— httpApi.cliPublishHandler has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (7 pts), if/else 3 (5 pts), boolean chains 2, error handling 2 (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.
httpApi.cliTelemetryInstallHandler (cognitive 16) convex/httpApi.ts:308— httpApi.cliTelemetryInstallHandler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 2 (5 pts), error handling 2, ternaries 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.
packagePublishRecoveryV1.recoverPackagePublishAttemptV1Handler (cognitive 16) convex/httpApiV1/packagePublishRecoveryV1.ts:29— packagePublishRecoveryV1.recoverPackagePublishAttemptV1Handler has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 3, ternaries 2 (3 pts), error handling 2 (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.
usersV1.handleAdminReclassifyBan (cognitive 16) convex/httpApiV1/usersV1.ts:483— usersV1.handleAdminReclassifyBan has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 5, boolean chains 3, error handling 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
packageInspectorHttp.packageInspectorResultsHttp (cognitive 16) convex/packageInspectorHttp.ts:199— packageInspectorHttp.packageInspectorResultsHttp has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 5, if/else 5, ternaries 4, error handling 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
publisherAbuse.publisherSkillMetricsForScoring (cognitive 16) convex/publisherAbuse.ts:2398— publisherAbuse.publisherSkillMetricsForScoring has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 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.
publisherAbuse.upsertPublisherAbuseReviewNomination (cognitive 16) convex/publisherAbuse.ts:2462— publisherAbuse.upsertPublisherAbuseReviewNomination has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (10 pts), boolean chains 5, if/else 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
searchReports.envelope (cognitive 16) convex/searchReports.ts:74— searchReports.envelope has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (15 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
publishFiles.forEachPublishFile (cognitive 16) packages/clawhub/src/publishFiles.ts:5— publishFiles.forEachPublishFile has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 3, error handling 1 (2 pts), loops 2 (nesting depth added 5). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (walk). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
packages.cmdValidatePackage (cognitive 16) packages/clawhub/src/cli/commands/packages.ts:670— packages.cmdValidatePackage has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 3 (4 pts), boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
packages.printPackageInspectorFindings (cognitive 16) packages/clawhub/src/cli/commands/packages.ts:1337— packages.printPackageInspectorFindings has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (8 pts), if/else 4 (7 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
skills.cmdListSkillReports (cognitive 16) packages/clawhub/src/cli/commands/skills.ts:1282— skills.cmdListSkillReports has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 2, loops 1 (2 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.
skills.cmdHardDeleteSkill (cognitive 16) packages/clawhub-admin/src/commands/skills.ts:31— skills.cmdHardDeleteSkill has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 5 (6 pts), boolean chains 3 (nesting depth added 3). Of this number, 13 points are the body's own statements and 3 belong 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.
skillsShCatalogSource.repositoryIdentityFromHtml (cognitive 16) server/skillsShCatalogSource.ts:643— skillsShCatalogSource.repositoryIdentityFromHtml has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 5). Of this number, 13 points are the body's own statements and 3 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.
convexProxy.proxyConvexRequest (cognitive 16) server/convexProxy.ts:126— convexProxy.proxyConvexRequest has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 5, ternaries 3, error handling 1 (2 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Header.getTypeaheadRowBody (cognitive 16) src/components/Header.tsx:1174— Header.getTypeaheadRowBody has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 4 (5 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SecurityAuditPage.AigSection (cognitive 16) src/components/SecurityAuditPage.tsx:577— SecurityAuditPage.AigSection has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 8 (12 pts), boolean chains 3, if/else 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.
detectRelativeReadmeAssets.detectRelativeReadmeAssets (cognitive 16) src/lib/detectRelativeReadmeAssets.ts:72— detectRelativeReadmeAssets.detectRelativeReadmeAssets has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (11 pts), loops 4, boolean chains 1 (nesting depth added 2). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (record, recordSrcset). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Change-coupling hub: schema.ts → crons.ts, packageSearchDigest.ts, publisherAbuseScoring.ts, retentionPolicy.ts, skillSearchDigest.ts, publisherAbuseTemporalScan.ts, skillStatEvents.ts convex/schema.ts— `convex/schema.ts` changes together with 7 other files — `convex/crons.ts`, `convex/lib/packageSearchDigest.ts`, `convex/lib/publisherAbuseScoring.ts`, `convex/lib/retentionPolicy.ts`, `convex/lib/skillSearchDigest.ts`, `convex/publisherAbuseTemporalScan.ts`, `convex/skillStatEvents.ts` — none of which declares a dependency on it: one file is the hub of 7 separate couplings, not 7 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 7.
Fake-async — async method never awaits convex/catalogClassification.ts:189— `getCatalogClassificationPageInternalHandler` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Hollow method — returns a constant without doing the work convex/depRegistryScan.ts:4— `checkDependencyRegistriesHandler` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
P12 · CI test-gate honesty· Tests run only outside the merge gate · ×1
Tests run only outside the merge gate REDACTED:399— `bunx playwright test --workers=1 e2e/menu-smoke.pw.test.ts e2e/publish-entry-workflows.pw.test.ts e2e/upload-auth-smoke.pw.test.ts` is the only CI command that runs 6 test(s) in 3 file(s) (e.g. `e2e/menu-smoke.pw.test.ts`, `e2e/publish-entry-workflows.pw.test.ts`), and the workflow runs only on workflow_dispatch — a failure there is found after the change merged, when the only remedy is a revert. Run them on pull requests (or in the merge queue).
No structured logging — No logging call was found in the 801 JavaScript/TypeScript production file(s) this check read across 4 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Duplication concentrated across 5 sibling directories (63 clone groups) scripts/skills-sh-catalog/capture-frozen-snapshot.ts:33— 63 duplicated blocks under the repository root have copies in at least two of the sibling directories convex, packages, scripts, server, src — 34 of them are reported below, and 29 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 63 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 63 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 63 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (13 clone groups) convex/httpApiV1/managedMcpV1.ts:24— 13 duplicated blocks under convex/ have copies in at least two of the sibling directories httpApiV1, lib — 9 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 12 sibling directories (13 clone groups) scripts/security/run-codex-scan-worker.ts:346— 13 duplicated blocks under scripts/ have copies in at least two of the sibling directories canonical-search, canonical-trending, design-audit, evaluations, lib, public-corpus (+6 more sibling(s) not listed) — 10 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 8 sibling directories (10 clone groups) src/routes/official/index.tsx:118— 10 duplicated blocks under src/routes/ have copies in at least two of the sibling directories $owner, -management, official, orgs, p, plugins (+2 more sibling(s) not listed) — 6 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (306 matched lines × 2 locations) · ×1
Duplicated block with local edits (306 matched lines × 2 locations) convex/httpApiV1/packagesV1.ts:1696— convex/httpApiV1/packagesV1.ts:1696 · convex/httpApiV1/skillsV1.ts:3509 — the two spans are one implementation copied and then locally edited — 1811 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (207 matched lines × 2 locations) · ×1
Duplicated block with local edits (207 matched lines × 2 locations) src/components/PluginVersionsPanel.tsx:44— src/components/PluginVersionsPanel.tsx:44 · src/components/SkillVersionsPanel.tsx:28 — the two spans are one implementation copied and then locally edited — 1133 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (167 matched lines × 2 locations) · ×1
Duplicated block with local edits (167 matched lines × 2 locations) convex/securityScanDispatch.ts:26— convex/securityScanDispatch.ts:26 · convex/skillEvaluationDispatch.ts:15 — the two spans are one implementation copied and then locally edited — 1082 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (139 matched lines × 2 locations) · ×1
Duplicated block with local edits (139 matched lines × 2 locations) convex/devSeed.ts:4189— convex/devSeed.ts:4189 · convex/devSeed.ts:4529 — the two spans are one implementation copied and then locally edited — 697 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (106 matched lines × 2 locations) · ×1
Duplicated block with local edits (106 matched lines × 2 locations) src/routes/official/index.tsx:118— src/routes/official/index.tsx:118 · src/routes/plugins/index.tsx:458 — the two spans are one implementation copied and then locally edited — 580 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (101 matched lines × 2 locations) · ×1
Duplicated block with local edits (101 matched lines × 2 locations) src/components/SkillDetailPageView.tsx:518— src/components/SkillDetailPageView.tsx:518 · src/routes/plugins/$name.tsx:1670 — the two spans are one implementation copied and then locally edited — 501 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (91 matched lines × 2 locations) · ×1
Duplicated block with local edits (91 matched lines × 2 locations) convex/lib/packageSearchDigest.ts:8— convex/lib/packageSearchDigest.ts:8 · convex/lib/skillSearchDigest.ts:16 — the two spans are one implementation copied and then locally edited — 589 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (90 matched lines × 2 locations) · ×1
Duplicated block with local edits (90 matched lines × 2 locations) src/components/PackageSourceChooser.tsx:193— src/components/PackageSourceChooser.tsx:193 · src/routes/skills/publish.tsx:895 — the two spans are one implementation copied and then locally edited — 376 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (87 matched lines × 2 locations) · ×1
Duplicated block with local edits (87 matched lines × 2 locations) scripts/skills-sh-catalog/capture-frozen-snapshot.ts:33— scripts/skills-sh-catalog/capture-frozen-snapshot.ts:33 · server/skillsShCatalogSource.ts:2706 — the two spans are one implementation copied and then locally edited — 671 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (63 matched lines × 2 locations) · ×1
Duplicated block with local edits (63 matched lines × 2 locations) packages/schema/src/catalogFeed.ts:66— packages/schema/src/catalogFeed.ts:66 · packages/schema/src/experimentalTemplateFeed.ts:37 — the two spans are one implementation copied and then locally edited — 481 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (60 lines × 2 locations) packages/clawhub/src/schema/schemas.ts:228— packages/clawhub/src/schema/schemas.ts:228 · packages/schema/src/schemas.ts:66 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
R10 · Code Duplication· Duplicated block with local edits (57 matched lines × 2 locations) · ×1
Duplicated block with local edits (57 matched lines × 2 locations) convex/leaderboards.ts:74— convex/leaderboards.ts:74 · convex/packageLeaderboards.ts:78 — the two spans are one implementation copied and then locally edited — 440 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (57 lines × 2 locations) convex/maintenance.ts:3164— convex/maintenance.ts:3164 · convex/maintenance.ts:3259 — all 2 copies are in the same file, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (53 matched lines × 2 locations) · ×1
Duplicated block with local edits (53 matched lines × 2 locations) convex/securityScan.ts:3105— convex/securityScan.ts:3105 · convex/skillsShCatalog.ts:1376 — the two spans are one implementation copied and then locally edited — 360 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (49 lines × 2 locations) convex/devSeed.ts:3218— convex/devSeed.ts:3218 · convex/devSeed.ts:3999 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (49 matched lines × 2 locations) · ×1
Duplicated block with local edits (49 matched lines × 2 locations) server/routes/og/plugin.png.ts:42— server/routes/og/plugin.png.ts:42 · server/routes/og/skill.png.ts:32 — the two spans are one implementation copied and then locally edited — 310 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (47 matched lines × 2 locations) · ×1
Duplicated block with local edits (47 matched lines × 2 locations) convex/httpApiV1/packagesV1.ts:1357— convex/httpApiV1/packagesV1.ts:1357 · convex/httpApiV1/packagesV1.ts:1560 — the two spans are one implementation copied and then locally edited — 220 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (45 lines × 2 locations) src/components/SecurityAuditPage.tsx:652— src/components/SecurityAuditPage.tsx:652 · src/components/SecurityAuditPage.tsx:850 — 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 (44 lines × 2 locations) packages/clawhub/src/cli/commands/packages.ts:1611— packages/clawhub/src/cli/commands/packages.ts:1611 · packages/clawhub/src/cli/commands/packages.ts:1663 — 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 (43 lines × 2 locations) src/routes/-management/PluginsPage.tsx:35— src/routes/-management/PluginsPage.tsx:35 · src/routes/-management/SkillsPage.tsx:89 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (42 lines × 2 locations) convex/securityScan.ts:1012— convex/securityScan.ts:1012 · convex/securityScan.ts:2508 — 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 (41 lines × 2 locations) packages/clawhub-admin/src/commands/moderation.ts:82— packages/clawhub-admin/src/commands/moderation.ts:82 · packages/clawhub-admin/src/commands/moderation.ts:128 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (40 matched lines × 2 locations) · ×1
Duplicated block with local edits (40 matched lines × 2 locations) convex/canonicalTrending.ts:440— convex/canonicalTrending.ts:440 · convex/canonicalTrending.ts:564 — the two spans are one implementation copied and then locally edited — 287 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (39 matched lines × 2 locations) · ×1
Duplicated block with local edits (39 matched lines × 2 locations) convex/skills.ts:3103— convex/skills.ts:3103 · convex/skills.ts:3192 — the two spans are one implementation copied and then locally edited — 271 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Complex function skillsGetRouterV1Handler (cyclomatic 214, cognitive 321) convex/httpApiV1/skillsV1.ts:1761— skillsGetRouterV1Handler has cyclomatic complexity 214 and cognitive complexity 321; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function SkillDetailPage (cyclomatic 175, cognitive 156) src/components/SkillDetailPage.tsx:184— SkillDetailPage has cyclomatic complexity 175 and cognitive complexity 156; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function packagesPostRouterV1Handler (cyclomatic 166, cognitive 259) convex/httpApiV1/packagesV1.ts:2615— packagesPostRouterV1Handler has cyclomatic complexity 166 and cognitive complexity 259; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function packagesGetRouterV1Handler (cyclomatic 159, cognitive 239) convex/httpApiV1/packagesV1.ts:3777— packagesGetRouterV1Handler has cyclomatic complexity 159 and cognitive complexity 239; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function AbusePage (cyclomatic 154, cognitive 145) src/routes/-management/AbusePage.tsx:47— AbusePage has cyclomatic complexity 154 and cognitive complexity 145; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function skillsPostRouterV1Handler (cyclomatic 152, cognitive 238) convex/httpApiV1/skillsV1.ts:2926— skillsPostRouterV1Handler has cyclomatic complexity 152 and cognitive complexity 238; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function PluginDetailPageContent (cyclomatic 151, cognitive 133) src/routes/plugins/$name.tsx:1048— PluginDetailPageContent has cyclomatic complexity 151 and cognitive complexity 133; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function publishPackageImpl (cyclomatic 147, cognitive 190) convex/packages.ts:8052— publishPackageImpl has cyclomatic complexity 147 and cognitive complexity 190; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function cmdUpdate (cyclomatic 139, cognitive 195) packages/clawhub/src/cli/commands/skills.ts:629— cmdUpdate has cyclomatic complexity 139 and cognitive complexity 195; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function listPackages (cyclomatic 132, cognitive 155) convex/httpApiV1/packagesV1.ts:1159— listPackages has cyclomatic complexity 132 and cognitive complexity 155; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handler (cyclomatic 123, cognitive 158) convex/skills.ts:10386— handler has cyclomatic complexity 123 and cognitive complexity 158; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handler (cyclomatic 112, cognitive 107) convex/packages.ts:11253— handler has cyclomatic complexity 112 and cognitive complexity 107; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Settings (cyclomatic 111, cognitive 91) src/routes/settings.tsx:276— Settings has cyclomatic complexity 111 and cognitive complexity 91; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function SkillDetailPageView (cyclomatic 104, cognitive 80) src/components/SkillDetailPageView.tsx:193— SkillDetailPageView has cyclomatic complexity 104 and cognitive complexity 80; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function listPackagePageImpl (cyclomatic 103, cognitive 173) convex/packages.ts:3946— listPackagePageImpl has cyclomatic complexity 103 and cognitive complexity 173; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 99, cognitive 146) server/routes/ops/skills-sh/mirror-test.post.ts:192— (anonymous) has cyclomatic complexity 99 and cognitive complexity 146; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Management (cyclomatic 90, cognitive 85) src/routes/management.tsx:226— Management has cyclomatic complexity 90 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateTemplateManifest (cyclomatic 88, cognitive 154) packages/schema/src/templates.ts:484— validateTemplateManifest has cyclomatic complexity 88 and cognitive complexity 154; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Upload (cyclomatic 86, cognitive 75) src/routes/skills/publish.tsx:90— Upload has cyclomatic complexity 86 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function applyGenericGitHubSkillSourceSyncHandler (cyclomatic 81, cognitive 92) convex/githubSkillSync.ts:1030— applyGenericGitHubSkillSourceSyncHandler has cyclomatic complexity 81 and cognitive complexity 92; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function PublishPluginRoute (cyclomatic 81, cognitive 65) src/routes/plugins/publish.tsx:173— PublishPluginRoute has cyclomatic complexity 81 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function skillsShCatalogTestV1Handler (cyclomatic 80, cognitive 107) convex/httpApiV1/skillsShCatalogV1.ts:619— skillsShCatalogTestV1Handler has cyclomatic complexity 80 and cognitive complexity 107; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function preparePackagePublishPlan (cyclomatic 76, cognitive 97) packages/clawhub/src/cli/commands/packages.ts:2646— preparePackagePublishPlan has cyclomatic complexity 76 and cognitive complexity 97; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handler (cyclomatic 76, cognitive 68) convex/packages.ts:10958— handler has cyclomatic complexity 76 and cognitive complexity 68; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function publishVersionForUser (cyclomatic 75, cognitive 74) convex/lib/skillPublish.ts:160— publishVersionForUser has cyclomatic complexity 75 and cognitive complexity 74; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function cmdSearchInsights (cyclomatic 74, cognitive 126) packages/clawhub-admin/src/commands/searchInsights.ts:17— cmdSearchInsights has cyclomatic complexity 74 and cognitive complexity 126; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateRetainedPublishAttempt (cyclomatic 70, cognitive 57) convex/lib/publishAttemptOperationalRecovery.ts:34— validateRetainedPublishAttempt has cyclomatic complexity 70 and cognitive complexity 57; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function exportSkillsV1Handler (cyclomatic 67, cognitive 116) convex/httpApiV1/skillsV1.ts:3531— exportSkillsV1Handler has cyclomatic complexity 67 and cognitive complexity 116; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function cmdPublish (cyclomatic 65, cognitive 76) packages/clawhub/src/cli/commands/publish.ts:39— cmdPublish has cyclomatic complexity 65 and cognitive complexity 76; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handler (cyclomatic 62, cognitive 73) convex/securityScan.ts:2822— handler has cyclomatic complexity 62 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handler (cyclomatic 61, cognitive 87) convex/publishAttempts.ts:689— handler has cyclomatic complexity 61 and cognitive complexity 87; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handler (cyclomatic 61, cognitive 78) convex/skills.ts:4712— handler has cyclomatic complexity 61 and cognitive complexity 78; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function admitScans (cyclomatic 61, cognitive 73) convex/skillsShCatalog.ts:1442— admitScans has cyclomatic complexity 61 and cognitive complexity 73; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ImportGitHub (cyclomatic 61, cognitive 49) src/routes/import.tsx:185— ImportGitHub has cyclomatic complexity 61 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function exportPluginsV1Handler (cyclomatic 60, cognitive 83) convex/httpApiV1/packagesV1.ts:1738— exportPluginsV1Handler has cyclomatic complexity 60 and cognitive complexity 83; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function UnifiedSearchPage (cyclomatic 60, cognitive 52) src/routes/search.tsx:94— UnifiedSearchPage has cyclomatic complexity 60 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function validateDecisionsRun (cyclomatic 60, cognitive 49) scripts/security/clawscan-decisions.ts:281— validateDecisionsRun has cyclomatic complexity 60 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function runPackageInspectorNightlyScan (cyclomatic 59, cognitive 111) scripts/package-inspector-nightly-scan.ts:173— runPackageInspectorNightlyScan has cyclomatic complexity 59 and cognitive complexity 111; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function setSkillSoftDeletedByActor (cyclomatic 59, cognitive 62) convex/skills.ts:11462— setSkillSoftDeletedByActor has cyclomatic complexity 59 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function clawScanExposure (cyclomatic 59, cognitive 44) scripts/security/clawscan-exposure.ts:60— clawScanExposure has cyclomatic complexity 59 and cognitive complexity 44; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
convex/packages.ts: 11699 lines of code convex/packages.ts:1— convex/packages.ts has 11699 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/skills.ts: 10977 lines of code convex/skills.ts:1— convex/skills.ts has 10977 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/devSeed.ts: 4947 lines of code convex/devSeed.ts:1— convex/devSeed.ts has 4947 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· convex/httpApiV1/packagesV1.ts · ×1
convex/httpApiV1/packagesV1.ts: 4416 lines of code convex/httpApiV1/packagesV1.ts:1— convex/httpApiV1/packagesV1.ts has 4416 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/publishers.ts: 4125 lines of code convex/publishers.ts:1— convex/publishers.ts has 4125 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/schema.ts: 4108 lines of code convex/schema.ts:1— convex/schema.ts has 4108 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/securityScan.ts: 3929 lines of code convex/securityScan.ts:1— convex/securityScan.ts has 3929 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· convex/httpApiV1/skillsV1.ts · ×1
convex/httpApiV1/skillsV1.ts: 3866 lines of code convex/httpApiV1/skillsV1.ts:1— convex/httpApiV1/skillsV1.ts has 3866 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/maintenance.ts: 3786 lines of code convex/maintenance.ts:1— convex/maintenance.ts has 3786 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/githubSkillSync.ts: 3240 lines of code convex/githubSkillSync.ts:1— convex/githubSkillSync.ts has 3240 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· scripts/security/run-codex-scan-worker.ts · ×1
scripts/security/run-codex-scan-worker.ts: 3061 lines of code scripts/security/run-codex-scan-worker.ts:1— scripts/security/run-codex-scan-worker.ts has 3061 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/publisherAbuse.ts: 3048 lines of code convex/publisherAbuse.ts:1— convex/publisherAbuse.ts has 3048 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/skillsShCatalog.ts: 3004 lines of code convex/skillsShCatalog.ts:1— convex/skillsShCatalog.ts has 3004 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/clawhub/src/cli/commands/packages.ts · ×1
packages/clawhub/src/cli/commands/packages.ts: 2929 lines of code packages/clawhub/src/cli/commands/packages.ts:1— packages/clawhub/src/cli/commands/packages.ts has 2929 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/routes/settings.tsx: 2911 lines of code src/routes/settings.tsx:1— src/routes/settings.tsx has 2911 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· server/skillsShCatalogSource.ts · ×1
server/skillsShCatalogSource.ts: 2888 lines of code server/skillsShCatalogSource.ts:1— server/skillsShCatalogSource.ts has 2888 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/users.ts: 2585 lines of code convex/users.ts:1— convex/users.ts has 2585 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/skillsShMirror.ts: 2320 lines of code convex/skillsShMirror.ts:1— convex/skillsShMirror.ts has 2320 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/search.ts: 2072 lines of code convex/search.ts:1— convex/search.ts has 2072 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· convex/lib/catalogClassifier.mjs · ×1
convex/lib/catalogClassifier.mjs: 2023 lines of code convex/lib/catalogClassifier.mjs:1— convex/lib/catalogClassifier.mjs has 2023 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/routes/plugins/$name.tsx · ×1
src/routes/plugins/$name.tsx: 1808 lines of code src/routes/plugins/$name.tsx:1— src/routes/plugins/$name.tsx has 1808 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/publishAttempts.ts: 1800 lines of code convex/publishAttempts.ts:1— convex/publishAttempts.ts has 1800 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/migrations.ts: 1726 lines of code convex/migrations.ts:1— convex/migrations.ts has 1726 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/routes/-management/AbusePage.tsx · ×1
src/routes/-management/AbusePage.tsx: 1719 lines of code src/routes/-management/AbusePage.tsx:1— src/routes/-management/AbusePage.tsx has 1719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/clawhub/src/cli/commands/skills.ts · ×1
packages/clawhub/src/cli/commands/skills.ts: 1659 lines of code packages/clawhub/src/cli/commands/skills.ts:1— packages/clawhub/src/cli/commands/skills.ts has 1659 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/routes/import.tsx: 1565 lines of code src/routes/import.tsx:1— src/routes/import.tsx has 1565 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· scripts/security/run-prepublication-worker.ts · ×1
scripts/security/run-prepublication-worker.ts: 1408 lines of code scripts/security/run-prepublication-worker.ts:1— scripts/security/run-prepublication-worker.ts has 1408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/routes/skills/publish.tsx · ×1
src/routes/skills/publish.tsx: 1377 lines of code src/routes/skills/publish.tsx:1— src/routes/skills/publish.tsx has 1377 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
convex/skillStatEvents.ts: 1328 lines of code convex/skillStatEvents.ts:1— convex/skillStatEvents.ts has 1328 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· convex/canonicalTrending.ts · ×1
convex/canonicalTrending.ts: 1321 lines of code convex/canonicalTrending.ts:1— convex/canonicalTrending.ts has 1321 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· scripts/package-inspector-nightly-scan.ts · ×1
scripts/package-inspector-nightly-scan.ts: 1292 lines of code scripts/package-inspector-nightly-scan.ts:1— scripts/package-inspector-nightly-scan.ts has 1292 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/routeTree.gen.ts: 1242 lines of code src/routeTree.gen.ts:1— src/routeTree.gen.ts has 1242 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/components/Header.tsx: 1235 lines of code src/components/Header.tsx:1— src/components/Header.tsx has 1235 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/components/SecurityAuditPage.tsx · ×1
src/components/SecurityAuditPage.tsx: 1221 lines of code src/components/SecurityAuditPage.tsx:1— src/components/SecurityAuditPage.tsx has 1221 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· convex/publisherAbuseTemporalScan.ts · ×1
convex/publisherAbuseTemporalScan.ts: 1219 lines of code convex/publisherAbuseTemporalScan.ts:1— convex/publisherAbuseTemporalScan.ts has 1219 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· convex/httpApiV1/skillsShCatalogV1.ts · ×1
convex/httpApiV1/skillsShCatalogV1.ts: 1206 lines of code convex/httpApiV1/skillsShCatalogV1.ts:1— convex/httpApiV1/skillsShCatalogV1.ts has 1206 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/routes/user/$handle.tsx · ×1
src/routes/user/$handle.tsx: 1192 lines of code src/routes/user/$handle.tsx:1— src/routes/user/$handle.tsx has 1192 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
src/routes/management.tsx: 1142 lines of code src/routes/management.tsx:1— src/routes/management.tsx has 1142 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· src/routes/plugins/publish.tsx · ×1
src/routes/plugins/publish.tsx: 1084 lines of code src/routes/plugins/publish.tsx:1— src/routes/plugins/publish.tsx has 1084 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· convex/skillsShMirrorVisibility.ts · ×1
convex/skillsShMirrorVisibility.ts: 1081 lines of code convex/skillsShMirrorVisibility.ts:1— convex/skillsShMirrorVisibility.ts has 1081 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Unused dependency '@edge-runtime/vm' package.json:164— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@react-email/ui' package.json:167— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'only-allow' package.json:184— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'oxlint-tsgolint' package.json:187— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'react-email' package.json:189— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'tsrs' package.json:191— Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Weak hash algorithm server/skillsShCatalogSource.ts:1063— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
X16 · Unfloored truncation loop· Truncation loop has no floor · ×1
Truncation loop has no floor — the value can be consumed entirely server/skillsShCatalogSource.ts:1055— `truncated` loses its last character (its last element, if it holds an array) on every pass — `truncated = truncated.slice(0, -1)` on line 1056 — and the loop's only exit is the test on line 1055 — which measures `truncated` only through `Buffer.byteLength(…)`, as a TERM of a larger expression, and never compares its length against a bound of its own. So nothing stops the loop at one character: it runs until the test's other terms come under the bound WITHOUT any help from `truncated`, which leaves `truncated` empty — and if they never do, the loop never ends, because JavaScript's `slice`/`substring`/`substr`/`replace` hand back `""` for an empty value instead of throwing, so every later pass shortens nothing and the test never changes. Neither outcome announces itself: an empty value surfaces later, as a path that names no file, a key that matches nothing, or a record written blank — and a hang surfaces as a frozen tab or a request that never returns. Give the loop a floor (`&& truncated.length > 1`), or compute the length once and clamp it (`truncated = truncated.slice(0, Math.max(1, budget))`) — and decide explicitly what should happen when the budget cannot be met, rather than letting an empty value be the answer.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×1
Recursive walk over a caller-supplied document has no depth cap convex/lib/publishStorage.ts:2— `stripUndefinedForStoredPublish` is exported and takes `value: unknown` from its caller, and it calls itself at line 2 (`stripUndefinedForStoredPublish`) with a piece of `value` (and at line 7) — and nowhere in `stripUndefinedForStoredPublish` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `stripUndefinedForStoredPublish` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
X24 · Document value interpolated into markup unescaped· Untrusted text written into markup unescaped · ×1
Untrusted text written into markup unescaped REDACTED:226— `state.svg` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Mock-dominated test: starts a manual publisher abuse scan without exposing force-new src/routes/-management.test.tsx:1015— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: runs every signal check from the Signals tab rescan control src/routes/-management.test.tsx:1038— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: connects GitHub from organization settings when memberships are unavailable src/routes/-settings.test.tsx:361— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: selects a verified GitHub organization and saves its immutable id src/routes/-settings.test.tsx:378— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: refreshes a linked GitHub organization handle after a rename src/routes/-settings.test.tsx:417— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: saves unrelated profile changes when the linked GitHub organization is unavailable src/routes/-settings.test.tsx:464— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: allows removing a GitHub organization after membership verification expires src/routes/-settings.test.tsx:505— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: clears auth state and leaves settings after account deletion succeeds src/routes/-settings.test.tsx:634— This test sets up 6 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: creates a member invite from the Members block invite dialog src/routes/-settings.test.tsx:965— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: updates an existing member role from the Members block dialog src/routes/-settings.test.tsx:1004— This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: updates an existing member role by personal publisher handle when user handle is missing src/routes/-settings.test.tsx:1034— This test sets up 5 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: loads additional permanent history pages src/routes/-management/PromotionsPage.test.tsx:85— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: accumulates only visible allowed seconds and requires meaningful scrolling src/lib/analyticsEngagement.test.ts:135— This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: cancels short section appearances and denies pending/hidden dwell src/lib/analyticsEngagement.test.ts:158— This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: signs out before switching between local personas src/components/DevPersonaFab.test.tsx:176— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: starts GitHub sign-in with the current relative URL by default src/components/SignInButton.test.tsx:49— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: surfaces user-facing auth errors when sign-in rejects src/components/SignInButton.test.tsx:93— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: routes banned-account sign-in rejections to the banned account page src/components/SignInButton.test.tsx:110— This test sets up 5 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: shows manager pagination when a filtered plugin page has no visible releases src/__tests__/version-delete-ui.test.tsx:614— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: renders unknown audit state when metadata is not fetched server/og/pluginRoute.test.ts:163— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: uses explicit downloads over legacy installs query params server/og/pluginRoute.test.ts:186— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: verifies trust indicators before rendering query-requested official state server/og/profileRoute.test.ts:148— This test sets up 6 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: verifies non-zero organization state even when affiliations have no images server/og/profileRoute.test.ts:189— This test sets up 6 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: uses verified metadata for official cards requested by query params server/og/profileRoute.test.ts:242— This test sets up 5 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: uses verified metadata when fetched metadata adds trust indicators server/og/profileRoute.test.ts:295— This test sets up 5 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Duplicated predicate convex/featuredSkills.ts:93— `!/^[a-z0-9][a-z0-9._-]*$/.test(part) || part.includes("..")` appears character-identically in 2 files — convex/featuredSkills.ts, packages/clawhub-admin/src/commands/featured.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/clawhub/src/cli/commands/scan.ts:251— `!Array.isArray(value) || value.length === 0` appears character-identically in 2 files — packages/clawhub/src/cli/commands/scan.ts, scripts/security/run-codex-scan-worker.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate .github/scripts/verify-trusted-tooling-identity.cjs:265— `!Array.isArray(value) || value.length === 0 || value.length > 512` appears character-identically in 2 files — .github/scripts/verify-trusted-tooling-identity.cjs, convex/lib/openClawPublishAuthorization.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/schema/src/catalogFeed.ts:103— `!Number.isFinite(Date.parse(feed.generatedAt)) || !Number.isFinite(Date.parse(feed.expiresAt))` appears character-identically in 3 files — packages/schema/src/catalogFeed.ts, packages/schema/src/experimentalTemplateFeed.ts, packages/schema/src/promotionsFeed.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/featuredIntelligence.ts:76— `!Number.isInteger(limit) || limit < 1 || limit > 100` appears character-identically in 3 files — convex/featuredIntelligence.ts, convex/lib/searchReportContract.ts, convex/searchInsights.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/skillsShCatalog.ts:305— `!Number.isInteger(value) || value < min || value > max` appears character-identically in 3 files — convex/skillsShCatalog.ts, convex/skillsShMirror.ts, server/skillsShCatalogSource.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/httpApiV1/skillsShCatalogV1.ts:363— `!Number.isSafeInteger(id) || id <= 0 || login !== owner` appears character-identically in 2 files — convex/httpApiV1/skillsShCatalogV1.ts, scripts/skills-sh-catalog/github-owner-resolution.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/security/run-clawscan-diagnostic.ts:137— `!Number.isSafeInteger(timeoutMs) || timeoutMs < 1 || timeoutMs > DIAGNOSTIC_PROCESS_BUDGET_MS` appears character-identically in 2 files — scripts/security/run-clawscan-diagnostic.ts, scripts/security/run-clawscan-original-diagnostic.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/featuredSelections.ts:39— `!actor || actor.deletedAt || actor.deactivatedAt` appears character-identically in 6 files — convex/featuredSelections.ts, convex/featuredSkills.ts, convex/promotions.ts, convex/securityScan.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/securityScanDispatch.ts:280— `!begin.shouldDispatch || !begin.leaseToken` appears character-identically in 2 files — convex/securityScanDispatch.ts, convex/skillEvaluationDispatch.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/routes/official/index.tsx:190— `!canLoadMore || typeof IntersectionObserver === "undefined"` appears character-identically in 2 files — src/routes/official/index.tsx, src/routes/plugins/index.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate .github/scripts/verify-trusted-tooling-identity.cjs:269— `!entry || typeof entry !== "object" || Array.isArray(entry)` appears character-identically in 3 files — .github/scripts/verify-trusted-tooling-identity.cjs, convex/httpApiV1/promotionsV1.ts, convex/lib/catalogClassifier.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/lib/skills/index.ts:242— `!input || typeof input !== "object" || Array.isArray(input)` appears character-identically in 2 files — convex/lib/skills/index.ts, packages/clawhub-admin/src/commands/managedMcp.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/clawhub-admin/src/commands/moderation.ts:319— `!isInteractive() || inputAllowed === false` appears character-identically in 3 files — packages/clawhub-admin/src/commands/moderation.ts, packages/clawhub-admin/src/commands/orgs.ts, packages/clawhub/src/cli/commands/packages.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/components/dashboard/DashboardNeedsAttention.tsx:567— `!issueClass || issueClass === "inspector-gap"` appears character-identically in 2 files — src/components/dashboard/DashboardNeedsAttention.tsx, src/routes/plugins/$name.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/devSeed.ts:2090— `!linkedUser || linkedUser.deletedAt || linkedUser.deactivatedAt` appears character-identically in 2 files — convex/devSeed.ts, convex/publishers.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/httpApi.ts:438— `!message || /^unauthorized$/i.test(message)` appears character-identically in 2 files — convex/httpApi.ts, convex/httpApiV1/shared.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate scripts/local-clawscan-dry-run.ts:418— `!metadata || typeof metadata !== "object" || Array.isArray(metadata)` appears character-identically in 2 files — scripts/local-clawscan-dry-run.ts, src/routes/-management/managementShared.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate src/routes/official/index.tsx:173— `!nextCursor || loadMoreInFlightRef.current` appears character-identically in 2 files — src/routes/official/index.tsx, src/routes/plugins/index.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/lib/skillsShMirrorPublic.ts:65— `!normalized || normalized.includes("/") || normalized.includes("\\") || normalized.includes(":") || normalized.includes("..")` appears character-identically in 2 files — convex/lib/skillsShMirrorPublic.ts, convex/skillsShMirrorPublic.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/clawhub/src/cli/commands/inspect.ts:243— `!options.file || options.files || options.versions || options.version` appears character-identically in 2 files — packages/clawhub/src/cli/commands/inspect.ts, packages/clawhub/src/cli/commands/packages.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/clawhub-admin/src/commands/featured.ts:69— `!ownerHandle || !slug || ownerHandle.includes("\\") || ownerHandle.includes("..") || slug.includes("\\") || slug.includes("..")` appears character-identically in 2 files — packages/clawhub-admin/src/commands/featured.ts, packages/clawhub-admin/src/commands/skills.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/httpApiV1/usersV1.ts:865— `!parsed || typeof parsed !== "object" || Array.isArray(parsed)` appears character-identically in 5 files — convex/httpApiV1/usersV1.ts, convex/lib/githubSkillSync.ts, convex/lib/skills/skillMarkdown.ts, scripts/generate-llms-txt.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/httpApiV1/publishersV1.ts:19— `!payload || typeof payload !== "object" || Array.isArray(payload)` appears character-identically in 4 files — convex/httpApiV1/publishersV1.ts, convex/httpApiV1/skillsV1.ts, convex/packageInspectorHttp.ts, server/skillsShCatalogSource.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate convex/githubSkillSync.ts:1124— `!publisher || publisher.deletedAt || publisher.deactivatedAt` appears character-identically in 7 files — convex/githubSkillSync.ts, convex/lib/officialPublishers.ts, convex/lib/public.ts, convex/publisherAbuse.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Disabled test e2e/local-auth/delete-account-resources.pw.test.ts:11— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/delete-org-resources.pw.test.ts:11— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test REDACTED:12— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/featured-lineup.pw.test.ts:7— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/header-profile-link.pw.test.ts:6— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/malicious-skill-ban-flow.pw.test.ts:16— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/manage-context-proof.pw.test.ts:13— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/old-cli-publish-compat.pw.test.ts:14— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/package-ssr-identity.pw.test.ts:7— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/plugin-api-retirements.pw.test.ts:8— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/plugin-catalog-api.pw.test.ts:9— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/plugin-inspector-findings.pw.test.ts:22— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/publish-skill-lifecycle.pw.test.ts:32— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/publisher-create-owner.pw.test.ts:9— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/publisher-github-profile.pw.test.ts:5— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/skill-hero-metadata.pw.test.ts:7— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/skill-presentation-metadata.pw.test.ts:7— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/skill-star-sync.pw.test.ts:17— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/template-official-boundary.pw.test.ts:9— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/local-auth/version-delete.pw.test.ts:14— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/mobile-skills.pw.test.ts:13— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/skills-sh-external.pw.test.ts:6— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/upload-auth-smoke.pw.test.ts:22— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test e2e/upload-auth-smoke.pw.test.ts:44— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Silent fallback default in catch convex/lib/changelog.ts:178— `generateChangelogForPublish` swallows every exception into `return "- Updated skill."` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch convex/lib/changelog.ts:224— `generatePackageChangelogPreview` swallows every exception into `return "- Updated package."` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch convex/lib/changelog.ts:263— `generateChangelogPreview` swallows every exception into `return "- Updated skill."` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch convex/migrations.ts:660— `normalizeInferredCategories` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch convex/skillsShMirror.ts:534— `validTopicInferenceTerms` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch e2e/helpers/convexSeed.ts:35— `pollableDevSeedState` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/clawhub-admin/src/buildInfo.ts:15— `readPackageVersion` swallows every exception into `return "0.0.0"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/schema/src/catalogMetadata.ts:568— `normalizeInferredCatalogTopics` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch packages/schema/src/templatePackage.ts:153— `templateBundledMetadataPaths` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch scripts/evaluations/skill-evaluation-runtime.ts:73— `configuredTaskSource` swallows every exception into `return "auto"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch scripts/playwright-local-auth-config.ts:54— `resolveLocalAuthExternalNodeDependencies` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch scripts/security/run-codex-scan-worker.ts:577— `clawScanScannerOutputReferences` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch server/skillsShCatalogSource.ts:1741— `parseSkillsShPageFieldEvidence.jsonLdValues` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch scripts/skills-sh-catalog/prove-500.ts:71— `readNumber` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch scripts/ui-proof.mjs:345— `readLaneManifest` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/lib/themeCookie.ts:24— `getThemeModeFromCookieHeader` swallows every exception into `return "system"` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/lib/analyticsEvents.ts:163— `normalizeNonfunctionalSearchKeys` swallows every exception into `return true` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Silent fallback default in catch src/lib/analyticsEvents.ts:374— `safeReferralOrigin` swallows every exception into `return ""` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Orphaned file convex/devSeedExtra.ts: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 src/lib/readmeAssetBaseUrl.ts: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 src/components/ui/sheet.tsx: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 convex/lib/userSkillStats.ts: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.
Blanket warning suppression convex/_generated/api.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression convex/_generated/server.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/routeTree.gen.ts:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression src/routeTree.gen.ts:3— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 62 significant file(s) lose their only recent owner: convex/canonicalTrending.ts, scripts/package-inspector-nightly-scan.ts, convex/skillsShMirrorVisibility.ts, scripts/plugin-category-operator.ts, convex/pluginCategoryRefresh.ts, convex/canonicalTrendingTestFixtures.ts, convex/searchInsights.ts, convex/searchWeeklyDigest.ts (+54 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 4 significant file(s) lose their only recent owner: convex/lib/skillCardClaims.ts, packages/clawhub/src/cli/buildInfo.ts, packages/clawhub/src/cli/clawdbotConfig.ts, src/lib/useDeferredActivityTrend.ts. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 3 significant file(s) lose their only recent owner: scripts/lib/previewAnalyticsProof.ts, src/lib/analyticsEvents.ts, src/components/GoogleAnalytics.tsx. Pair on, review, or document these before any departure.
redundant comment convex/lib/securityPrompt.ts:480— "SKILL.md content" repeats the code it sits on: 3 of its 3 words (skill, md, content) are already in `sections.push(`### SKILL.md content (quoted artifact data)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment convex/lib/skills/index.ts:90— "Parse dependency declarations" repeats the code it sits on: 3 of its 3 words (parse, dependency, declarations) are already in `const dependencies = parseDependencyDeclarations(clawdisObj.dependencies);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment convex/packages.public.test.ts:20143— "The release was soft-deleted together with the package." repeats the code it sits on: 4 of its 5 words (release, soft, deleted, package) are already in `const restoredRelease = makeReleaseDoc({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 3 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (75 single-owned of 554 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 554 of the 928 production source files in this repository met that bar). They are anonymized user #4 (2 file(s)), anonymized user #5 (2 file(s)), anonymized user #6 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: src/routes/-management/AbusePage.tsx, scripts/security/run-endor-plugin-scan.ts, server/og/registryOgSvg.ts, src/components/SkillShortSummaryField.tsx, convex/githubAccountAgeBackfill.ts, scripts/verify-convex-contract.ts.
D21 · Naming Consistency· `baseURL` spells `URL` where 146 names in the project spell it `Url` · ×1
`baseURL` spells `URL` where 146 names in the project spell it `Url` e2e/helpers/productionSmoke.ts:5— 146 of 147 names in project clawhub spell the token `Url` (146 of 147; unit: names in project clawhub containing `Url`). Peers: catalogFeed.catalogFeedIconUrl (convex/catalogFeed.ts:408); cliDeviceAuth.getVerificationUrl (convex/cliDeviceAuth.ts:237); cliDeviceAuth.getVerificationUrl(siteUrlValue) (convex/cliDeviceAuth.ts:237); http.cliUploadUrlHttp (convex/http.ts:32); httpApi.cliUploadUrlHandler (convex/httpApi.ts:182). Rename to `baseUrl`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion package.json:1— `(repository root)` (228445 LoC, 853 module-visible types across 61 directories) overshoots its size bounds. 1 of 4 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 5.0/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 4 of 554 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 554 of the 928 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: convex/devSeedExtra.ts, src/lib/readmeAssetBaseUrl.ts, src/components/ui/sheet.tsx, convex/lib/userSkillStats.ts. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
README/code drift scripts/security-dataset/huggingface-live/README.md:51— scripts/security-dataset/huggingface-live/README.md links to `metadata/latest-manifest.json`, but `scripts/security-dataset/huggingface-live/metadata/latest-manifest.json` does not exist. 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.
P3 · Security & performance tooling· Dependabot does not watch pip · ×1
Dependabot does not watch pip REDACTED:2— `REDACTED` schedules updates, but no `package-ecosystem` entry covers `pip`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
R7 · Dead Code· Unused export 'PLATFORM_SKILL_LICENSE_NAME' · ×1
Unused export 'PLATFORM_SKILL_LICENSE_NAME' packages/clawhub/src/schema/license.ts:2— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'PLATFORM_SKILL_LICENSE_URL' · ×1
Unused export 'PLATFORM_SKILL_LICENSE_URL' packages/clawhub/src/schema/license.ts:5— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'ApiV1PublisherEnsureResponse' · ×1
Unused export 'ApiV1PublisherEnsureResponse' packages/clawhub/src/schema/schemas.ts:46— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/clawhub/src/schema/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/clawhub/src/schema/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'ApiV1PublisherRemoveMemberResponse' · ×1
Unused export 'ApiV1PublisherRemoveMemberResponse' packages/clawhub/src/schema/schemas.ts:59— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/clawhub/src/schema/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/clawhub/src/schema/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'ApiV1PublisherProfileUpdateResponse' · ×1
Unused export 'ApiV1PublisherProfileUpdateResponse' packages/clawhub/src/schema/schemas.ts:71— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/clawhub/src/schema/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/clawhub/src/schema/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'ApiV1PublisherRecoveryResponse' · ×1
Unused export 'ApiV1PublisherRecoveryResponse' packages/clawhub/src/schema/schemas.ts:113— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/clawhub/src/schema/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/clawhub/src/schema/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'ApiV1OfficialPublisherListResponse' · ×1
Unused export 'ApiV1OfficialPublisherListResponse' packages/clawhub/src/schema/schemas.ts:132— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/clawhub/src/schema/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/clawhub/src/schema/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused export 'ApiV1OfficialPublisherUpdateResponse' · ×1
Unused export 'ApiV1OfficialPublisherUpdateResponse' packages/clawhub/src/schema/schemas.ts:143— Nothing ultimately consumes this binding: its only referrer is the re-export in packages/clawhub/src/schema/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/clawhub/src/schema/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'default' server/convexProxy.ts:752— Nothing ultimately consumes this binding: its only referrer is the re-export in server/handlers/convexProxy.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in server/handlers/convexProxy.ts in the same commit, or the barrel will import a name that no longer exists.
R8 · Dependency Hygiene· Type-only dependency 'unified' in production deps · ×1
Type-only dependency 'unified' in production deps REDACTED:8— Every import is type-only — move it to devDependencies.
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 30/38 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
Null assertions (`!`) override strict null checking — ~0.8 `!` null assertions per 1k TypeScript source lines — 177 assertion(s) across the 226509 source line(s) of the 781 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: convex/httpApiV1/packagesV1.ts (23), server/skillsShCatalogSource.ts (22), convex/skills.ts (10). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
Skipped (documented): (unnamed test) scripts/playwright-local-auth-config.test.ts:32— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/playwright-local-convex.test.ts:29— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/templates-feed-openclaw-e2e.test.ts:443— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/templates-feed-openclaw-e2e.test.ts:472— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/templates-feed-openclaw-e2e.test.ts:490— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/templates-feed-openclaw-e2e.test.ts:497— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/security/qualify-test-template.test.ts:322— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/security/template-qualification-workspace.test.ts:184— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/lib/runWorkerCommand.cleanup-timers.test.ts:34— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/lib/runWorkerCommand.cleanup-timers.test.ts:71— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/lib/runWorkerCommand.cleanup-timers.test.ts:113— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/lib/runWorkerCommand.cleanup-timers.test.ts:173— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/lib/runWorkerCommand.cleanup-timers.test.ts:202— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/lib/runWorkerCommand.cleanup-timers.test.ts:238— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) scripts/lib/runWorkerCommand.cleanup.test.ts:10— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/clawhub/test-artifact/cli.artifact.test.ts:765— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/clawhub/test-artifact/cli.artifact.test.ts:801— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/clawhub/test-artifact/cli.artifact.test.ts:869— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Skipped (documented): (unnamed test) packages/clawhub/test-artifact/cli.artifact.test.ts:889— Skipped with a documented reason — a deferral, not lazy debt: switched off by it.skipIf
Outdated (npm): @clack/prompts — @clack/prompts is pinned at 1.8.1; registry.npmjs.org publishes 1.9.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @convex-dev/auth — @convex-dev/auth is pinned at 0.0.96; registry.npmjs.org publishes 2.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @convex-dev/migrations — @convex-dev/migrations is pinned at 0.3.7; registry.npmjs.org publishes 0.3.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @convex-dev/workpool — @convex-dev/workpool is pinned at 0.4.15; registry.npmjs.org publishes 0.4.16 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @react-email/render — @react-email/render is pinned at 2.2.0; registry.npmjs.org publishes 2.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @vercel/oidc — @vercel/oidc is pinned at 4.0.7; registry.npmjs.org publishes 4.0.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): convex — convex is pinned at 1.49.0; registry.npmjs.org publishes 1.50.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): convex-helpers — convex-helpers is pinned at 0.1.134; registry.npmjs.org publishes 0.1.135 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): croner — croner is pinned at 11.0.0; registry.npmjs.org publishes 11.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): jose — jose is pinned at 6.2.16; registry.npmjs.org publishes 6.2.17 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): lucide-react — lucide-react is pinned at 1.70.0; registry.npmjs.org publishes 1.73.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): mermaid — mermaid is pinned at 11.17.2; registry.npmjs.org publishes 12.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): resend — resend is pinned at 6.37.0; registry.npmjs.org publishes 6.38.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): undici — undici is pinned at 7.30.2; registry.npmjs.org publishes 8.12.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
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 53 file(s) — `convex/_generated/api.d.ts`, `convex/catalogFeed.ts`, `convex/devSeed.ts`, `convex/featuredIntelligence.ts`, `convex/httpApiV1/packagesV1.ts`, … (+48 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
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 01a1e5b2-0c59-7ad0-8d92-238c3ce1e1b9 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 163 · Warnings: 1396 · Recommendations: 246 · Info: 33 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 18:50 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.