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

hyperweb-io/create-cosmos-app

Measured 17 November 2026, 22:20 UTC, at code version 70cc6f0

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

Test reliability is not measured: The JS/TS suite's lockfile was refused.

Bus factor is not measured: No living knowledge left to concentrate.

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 33.1out of 100 At risk

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

A medium codebase: 67,118 lines of product code in 7 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 20.6

Findings by how serious they are

658 critical 401 serious 254 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 22:20 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 ▸

60of 60 dimensions measured by tools.
1235of 1313 findings point to an exact file and line, so you can open each one in the code. The other 78 concern the repository as a whole, such as missing documentation.
60dimensions across 7 lenses, read from 67,118 lines of product code in 7 projects.
Chapters

Executive summary

hyperweb-io/create-cosmos-app is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no logging, tracing or health checks in the code and no automated security scanning of the code, its secrets or its dependencies. It scores 33.1 out of 100, which the At risk rating leaves unchanged.

Production Readiness, at 20.6, is the weakest lens and counts most in the score. The best first step is making the four tests that check nothing check their results, worth about 10.5 points. Adopting a logging library would lift Production Readiness itself, worth about 3.8 points. Raising Production Readiness to 70 would lift the score to about 43.9.

632 known security holes in the packages the code depends on can be used by attackers. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three weaknesses in the code could be used by an attacker. Updating the vulnerable packages, pinning each tool to an exact version and fixing the weaknesses the scanner points to would close these risks. Setting a waiting period for automatic updates would fix the two automatic dependency updates that take new releases at once, and the pipeline step that installs packages without pinning their versions needs the packages it installs pinned to exact versions. The nine test suites that won't install need their lockfile updated so they install.

The product code is 67,118 lines, about €57,000 to rebuild.

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

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

If Production Readiness rose from 20.6 to 70, the lowest score rated Strong, the score would rise from 33.1 to about 43.9.

Code composition: what the lines of code are
Product code 100%Tests 0%
Rebuild cost: about €57,000 · Estimate
Cost to rebuild€19,000 to €96,000, for 318 to 1,008 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 33. 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.
SizeMedium: 67,118 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 4 No assertions finding(s) in Test Quality — start with first.test.ts (3), example.test.ts.
Raises the score by about 10.5 points · Low effort · Test Quality
2
Resolve the 4 Test project verifies nothing finding(s) in Test Quality — start with first.test.ts (3), example.test.ts.
Raises the score by about 10.5 points · Low effort · Test Quality
3
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Raises the score by about 5.5 points · Medium effort · Forms & labels

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €57,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 20.6 (Critical). 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 4 No assertions finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 10.5 points for low effort, because it clears the 4 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

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.

67 modules, with 1 dependency 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; 27 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.
uses →1 boilerplates.lerna-module2 boilerplates.lerna-tsx-module.src3 boilerplates.npm-boilerplate.src4 boilerplates.telescope.packages.__MODULENAME__5 boilerplates.telescope.packages.__MODULENAME__.scripts6 boilerplates.ts-codegen-npm-module.scripts7 boilerplates.website8 boilerplates.website.components.common9 boilerplates.website.pages10 packages.create-cosmos-app11 packages.create-cosmos-app.src.utils12 templates.chain-template13 templates.chain-template.components.asset-list14 templates.chain-template.components.asset-list.AssetListSection15 templates.chain-template.components.asset-list.AssetsOverview16 templates.chain-template.components.asset-list.DropdownTransferModal17 templates.chain-template.components.asset-list.RowTransferModal18 templates.chain-template.components.common19 templates.chain-template.components.common.Button20 templates.chain-template.components.common.Header21 templates.chain-template.components.common.Header.Header22 templates.chain-template.components.common.Radio23 templates.chain-template.components.common.Sidebar24 templates.chain-template.components.common.Sidebar.NavItems25 templates.chain-template.components.common.Wallet26 templates.chain-template.components.common.Wallet.RingLoader27 templates.chain-template.components.common.Wallet.RingLoader.RingLoader28 templates.chain-template.components.contract29 templates.chain-template.components.contract.AttachFundsRadio30 templates.chain-template.components.contract.CreateFromUpload31 templates.chain-template.components.contract.JsonInput32 templates.chain-template.components.staking33 templates.chain-template.components.voting34 templates.chain-template.config35 templates.chain-template.config.products36 templates.chain-template.contexts37 templates.chain-template.contexts.chain38 templates.chain-template.hooks.asset-list39 templates.chain-template.hooks.asset-list.useChainAssetsPrices40 packages.create-cosmos-app.src
1 boilerplates.lerna-module
2 boilerplates.lerna-tsx-module.src
3 boilerplates.npm-boilerplate.src
4 boilerplates.telescope.packages.__MODULENAME__
5 boilerplates.telescope.packages.__MODULENAME__.scripts
6 boilerplates.ts-codegen-npm-module.scripts
7 boilerplates.website
8 boilerplates.website.components.common
9 boilerplates.website.pages
10 packages.create-cosmos-app
11 packages.create-cosmos-app.src.utils
12 templates.chain-template
13 templates.chain-template.components.asset-list
14 templates.chain-template.components.asset-list.AssetListSection
15 templates.chain-template.components.asset-list.AssetsOverview
16 templates.chain-template.components.asset-list.DropdownTransferModal
17 templates.chain-template.components.asset-list.RowTransferModal
18 templates.chain-template.components.common
19 templates.chain-template.components.common.Button
20 templates.chain-template.components.common.Header
21 templates.chain-template.components.common.Header.Header
22 templates.chain-template.components.common.Radio
23 templates.chain-template.components.common.Sidebar
24 templates.chain-template.components.common.Sidebar.NavItems
25 templates.chain-template.components.common.Wallet
26 templates.chain-template.components.common.Wallet.RingLoader
27 templates.chain-template.components.common.Wallet.RingLoader.RingLoader
28 templates.chain-template.components.contract
29 templates.chain-template.components.contract.AttachFundsRadio
30 templates.chain-template.components.contract.CreateFromUpload
31 templates.chain-template.components.contract.JsonInput
32 templates.chain-template.components.staking
33 templates.chain-template.components.voting
34 templates.chain-template.config
35 templates.chain-template.config.products
36 templates.chain-template.contexts
37 templates.chain-template.contexts.chain
38 templates.chain-template.hooks.asset-list
39 templates.chain-template.hooks.asset-list.useChainAssetsPrices
40 packages.create-cosmos-app.src1
Uses a module listed above itPart of a loopThe module itself
1 boilerplates.lerna-module2 boilerplates.lerna-tsx-module.src3 boilerplates.npm-boilerplate.src4 boilerplates.telescope.packages.__MODULENAME__5 boilerplates.telescope.packages.__MODULENAME__.scripts6 boilerplates.ts-codegen-npm-module.scripts7 boilerplates.website8 boilerplates.website.components.common9 boilerplates.website.pages10 packages.create-cosmos-app11 packages.create-cosmos-app.src.utils12 templates.chain-template13 templates.chain-template.components.asset-list14 templates.chain-template.components.asset-list.AssetListSection15 templates.chain-template.components.asset-list.AssetsOverview16 templates.chain-template.components.asset-list.DropdownTransferModal17 templates.chain-template.components.asset-list.RowTransferModal18 templates.chain-template.components.common19 templates.chain-template.components.common.Button20 templates.chain-template.components.common.Header21 templates.chain-template.components.common.Header.Header22 templates.chain-template.components.common.Radio23 templates.chain-template.components.common.Sidebar24 templates.chain-template.components.common.Sidebar.NavItems25 templates.chain-template.components.common.Wallet26 templates.chain-template.components.common.Wallet.RingLoader27 templates.chain-template.components.common.Wallet.RingLoader.RingLoader28 templates.chain-template.components.contract29 templates.chain-template.components.contract.AttachFundsRadio30 templates.chain-template.components.contract.CreateFromUpload31 templates.chain-template.components.contract.JsonInput32 templates.chain-template.components.staking33 templates.chain-template.components.voting34 templates.chain-template.config35 templates.chain-template.config.products36 templates.chain-template.contexts37 templates.chain-template.contexts.chain38 templates.chain-template.hooks.asset-list39 templates.chain-template.hooks.asset-list.useChainAssetsPrices40 packages.create-cosmos-app.srcboilerplates.lerna-module1boilerplates.lerna-tsx-module.src2boilerplates.npm-boilerplate.src3boilerplates.telescope.packages.__MODULENAME__4boilerplates.telescope.packages.__MODULENAME__.scripts5boilerplates.ts-codegen-npm-module.scripts6boilerplates.website7boilerplates.website.components.common8boilerplates.website.pages9packages.create-cosmos-app10packages.create-cosmos-app.src.utils11templates.chain-template12templates.chain-template.components.asset-list13templates.chain-template.components.asset-list.AssetListSection14templates.chain-template.components.asset-list.AssetsOverview15templates.chain-template.components.asset-list.DropdownTransferModal16templates.chain-template.components.asset-list.RowTransferModal17templates.chain-template.components.common18templates.chain-template.components.common.Button19templates.chain-template.components.common.Header20templates.chain-template.components.common.Header.Header21templates.chain-template.components.common.Radio22templates.chain-template.components.common.Sidebar23templates.chain-template.components.common.Sidebar.NavItems24templates.chain-template.components.common.Wallet25templates.chain-template.components.common.Wallet.RingLoader26templates.chain-template.components.common.Wallet.RingLoader.RingLoader27templates.chain-template.components.contract28templates.chain-template.components.contract.AttachFundsRadio29templates.chain-template.components.contract.CreateFromUpload30templates.chain-template.components.contract.JsonInput31templates.chain-template.components.staking32templates.chain-template.components.voting33templates.chain-template.config34templates.chain-template.config.products35templates.chain-template.contexts36templates.chain-template.contexts.chain37templates.chain-template.hooks.asset-list38templates.chain-template.hooks.asset-list.useChainAssetsPrices39packages.create-cosmos-app.src401+27 more modules (most-connected shown)

At a glance — Code Health · 56.7 · Adequate · gated by R10 ·

At a glance — Architecture · 59.8 · Adequate · gated by R9 ·

At a glance — Maturity · 46.8 · Weak · gated by D34, M2 ·

At a glance — Readiness · 20.6 · Critical · gated by D10, R4, R8, P2, P3 ·

At a glance — Security · 65.1 · Adequate · gated by D29 ·

At a glance — Accessibility · 32.4 · Weak · gated by AC2 ·

At a glance — Performance · 60.0 · Adequate ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures853High / Critical
A05:2025 — Injection15High / Critical

Roadmap

Top priorities: Resolve the 4 No assertions finding(s) in Test Quality — start with first.test.ts (3), example.test.ts; Resolve the 4 Test project verifies nothing finding(s) in Test Quality — start with first.test.ts (3), example.test.ts; Resolve the 107 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (107).

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

Do thisHelpsEffortDimension
Resolve the 4 No assertions finding(s) in Test Quality — start with first.test.ts (3), example.test.ts.+10.5 ptsLowTest Quality
Resolve the 4 Test project verifies nothing finding(s) in Test Quality — start with first.test.ts (3), example.test.ts.+10.5 ptsLowTest Quality
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.+5.5 ptsMediumForms & labels
Resolve the 107 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (107).+9.1 ptsHighDependency Hygiene
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.+4.3 ptsMediumVisual & motion safety
Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, git-question-template.ts, utils.ts.+2.0 ptsLowKnowledge Freshness
Adopt pino (or winston) and log at meaningful points in the services you run.+3.8 ptsMediumObservability
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.+3.8 ptsMediumSecurity & performance tooling

File quality

Per-file score 0–10 — a quality signature. Of 54 files carrying findings, judged against the Production bar: 31% slop · 36% mixed · 33% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED0.2SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED1.6SlopStatic Analysis (SAST): High: REDACTED
REDACTED2.0SlopStatic Analysis (SAST): High: REDACTED
REDACTED5.7MixedStatic Analysis (SAST): Medium: REDACTED
packages/create-cosmos-app/REDACTED6.8MixedDependency Hygiene: Deprecated: eslint
REDACTED7.2MixedStatic Analysis (SAST): High: REDACTED

How the grades work

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

Critical — 658

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 401

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 254

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

Could not be resolved — 8

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

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

What we checked — 60 dimensions across the health lenses
D1D2D3D5D6D10D12D13D14D15D17D19D20D21D23D24D26D27D28D29D30D34D35D43AC2AC6AX10AX3AX4AX6GD1IC1M1M2M3P1P10P2P3P6PF3R1R10R11R2R3R4R6R7R8R9X1X12X16X2X21X25X29X3X5

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

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1235 of 1313 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1eb98-d926-7fe9-bab5-de638c86bf57.

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

Run transparency — what happened this run

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

  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the jest suite in examples/authz/ was NOT MEASURED: the dependency install for examples/authz/ could not reach the package registry on this run (➤ YN0001: │ RequestError: tunneling socket could not be established, statusCode=403), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 3 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 3 of the 28 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
  • D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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/create-cosmos-app/REDACTED), 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 REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run dev` in boilerplates/website/) kept running but served no page within 2 minutes. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: / https://nextjs.org/telemetry / /bin/sh: 1: yarn: not found / ▲ Next.js 13.5.6 / - Local: http://localhost:3000 / ✓ Ready in 697ms / Browserslist: caniuse-lite is outdated. Please run: / npx browserslist@latest --update-db / Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating / ○ Compiling / ... / ✓ Compiled / in 3.3s (1474 modules)" No runtime evidence was gathered.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev` in boilerplates/website/) kept running but served no page within 2 minutes. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: / https://nextjs.org/telemetry / /bin/sh: 1: yarn: not found / ▲ Next.js 13.5.6 / - Local: http://localhost:3000 / ✓ Ready in 697ms / Browserslist: caniuse-lite is outdated. Please run: / npx browserslist@latest --update-db / Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating / ○ Compiling / ... / ✓ Compiled / in 3.3s (1474 modules)" No runtime evidence was gathered.
  • P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
  • 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. 6 further occurrence(s) are not listed individually; the score already reflects all 46.
  • R4 Test Coverage — 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. 23 further occurrence(s) are not listed individually; the score already reflects all 63.
  • S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 217 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
  • 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: 9 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity9.5 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was git-cca-template.createGitApp.<returned closure> at 22.

git-cca-template.createGitApp.<returned closure> (cyclomatic 22)REDACTED:80

What to do

  1. Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with git-cca-template.createGitApp.<returned closure> (cyclomatic 22). — Refactoring it lifts Cyclomatic Complexity from 9.5 to about 10.0/10.

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

D2 · Cognitive Complexity7.5 / 10Strong✓ Tool-verified

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

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

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

2 method(s) exceeded the cognitive complexity threshold of 15; the worst was git-cca-template.createGitApp.<returned closure> at 39.

git-cca-template.createGitApp.<returned closure> (cognitive 39)REDACTED:80
git-question-template.createQuestionTemplate.<returned closure> (cognitive 17)packages/create-cosmos-app/src/git-question-template.ts:9

What to do

  1. Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with git-cca-template.createGitApp.<returned closure> (cognitive 39), git-question-template.createQuestionTemplate.<returned closure> (cognitive 17). — 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 2 together lifts Cognitive Complexity from 7.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes9.9 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

2 over-large unit(s) detected — types, modules or files that carry too much.

FunctionTooLong: Connect.SVGComponentboilerplates/website/components/common/Connect.tsx:2
FileTooLong: common/Connect.tsxboilerplates/website/components/common/Connect.tsx

What to do

  1. Resolve the 1 FunctionTooLong finding(s) in God Classes — start with Connect.tsx. — One of this dimension's main actionable groups (1 warning-level).
  2. Resolve the 1 FileTooLong finding(s) in God Classes — start with Connect.tsx. — One of this dimension's main actionable groups (1 warning-level).

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

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

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

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

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

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

7 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, with abstractness counted on 4 of the 7 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 44 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D10 · Test Quality2.5 / 10Weak✓ Tool-verified

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

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

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

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

No assertions: it works · ×4boilerplates/ts-codegen-npm-module/__tests__/example.test.ts:1
Test project verifies nothing: boilerplates/lerna-module · ×4boilerplates/lerna-module/__tests__/first.test.ts:1

What to do

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

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

D12 · Dependency Hygiene7.0 / 10Strong✓ Tool-verified

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

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

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

64 outdated direct production npm dependency(ies) of 79 graded, 0 pinning defect(s), across 24 REDACTED (8 of them the product) and 16 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 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.

Deprecated: eslint · ×6boilerplates/lerna-workspace/REDACTED:34
Deprecated: @babel/plugin-proposal-dynamic-import · ×107REDACTED:768
Outdated (npm): framer-motion · ×6boilerplates/website/REDACTED:24
Outdated (npm): @apollo/client · ×58

What to do

  1. Resolve the 107 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (107). — One of this dimension's main actionable groups (107 recommendation-level).
  2. Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
  3. Resolve the 6 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 recommendation-level).

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

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

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

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

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

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

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

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

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

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

0 of 1319 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1319 package(s) this repository's committed lockfile installs for a consumer — its 79 production, optional and peer dependency(ies), across 8 product REDACTED manifest(s), and everything those install in turn. Its 237 `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. 67 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 SEE LICENSE IN LICENSE, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

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

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

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

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

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

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

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

TodoComment · ×9templates/chain-template/utils/asset-list/pool.ts:265
TodoComment repeated across 34 filesexamples/authz/pages/_app.tsx:1

What to do

  1. Resolve the 9 TodoComment finding(s) in Explicit Debt — start with pool.ts (6), _app.tsx (2), WarnBlock.tsx. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 1 TodoComment repeated across 34 files finding(s) in Explicit Debt — start with _app.tsx. — 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.

D19 · Documentation Quality8.3 / 10Strong✓ Tool-verified

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

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

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

1 of 2 documentation facets pass in full; short on: F2 example. 11 document(s) read across 12 unit(s).

Documentation: no build, run or usage example · ×3boilerplates/npm-boilerplate/README.md:1

What to do

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

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

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

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

No architecture decision records were found.

No ADRs foundpackages/create-cosmos-app/REDACTED:10

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).

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

D21 · Naming Consistency10.0 / 10Exemplary✓ Tool-verified

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.

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

6 naming inconsistencies among 11019 declarations measured against a convention their peers follow.

`cosmosSdkVersion` spells `Sdk` where 5787 names in the project spell it `SDK` · ×4examples/authz/src/codegen/cosmos/base/tendermint/v1beta1/query.ts:305
`renderURLSearchParams` spells `URL` where 5226 names in the project spell it `Url`examples/grpc-web-grpc-gateway/codegen_grpc_gateway/grpc-gateway.ts:327
`toDataURL` spells `URL` where 5226 names in the project spell it `Url`examples/telescope-with-contracts/utils/index.ts:49

✓ On the Gold path — maintain.

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

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

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.

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

No domain types leak across context boundaries (16 contexts). Contexts: authz, chain-template, connect-chain, connect-multi-chain, create-cosmos-app, grpc-web-grpc-gateway, ibc-asset-list, nft, provide-liquidity, rollkit, spawn, stake-tokens and 4 more.

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D24 · Comment Value10.0 9.8 / 10Exemplary○ Nothing flagged

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

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

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 98% · ceiling Documented

0 of 32 judged comments only repeat the code they sit on (0.0 %). 1 comment(s) in another language or script were not judged.

doc comments repeat the namespackages/create-cosmos-app/src/utils.ts:138

✓ On the Gold path — maintain.

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

D26 · Project Cohesion10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 of 7 build units (npm) flagged as possibly oversized/incoherent.

✓ On the Gold path — maintain.

Detailed fixes: d26_recommendation.md.

D27 · Navigability9.7 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

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

20 % of calls cross a namespace and 6 % go through an interface, but 99 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

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.

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

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)3.0 / 10Weak✓ Tool-verified

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

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

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

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

15 finding(s): 0 critical, 12 high, 3 medium, 0 low. 6 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. Separately, one or more rules could not re-parse an embedded snippet in 1 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
  2. 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).
  3. No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

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

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

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

853 finding(s): 146 critical, 486 high, 198 medium, 23 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

  1. Resolve the 486 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (486). — One of this dimension's main actionable groups (486 issue-level).
  2. Resolve the 103 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (103). — One of this dimension's main actionable groups (103 issue-level).
  3. Resolve the 43 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (43). — One of this dimension's main actionable groups (43 issue-level).

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

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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.

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

3 of 3 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is REDACTED. Counted over 3 of the 28 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×3REDACTED:1
Orphaned files with no living knowledge

What to do

  1. Resolve the 3 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED, git-question-template.ts, utils.ts. — One of this dimension's main actionable groups (3 recommendation-level).
  2. Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

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

AC2 · Forms & labels1.6 / 10Critical✓ 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 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. (×4) — templates/chain-template/components/common/Header/ChainDropdown.tsx:47, templates/chain-template/components/contract/AttachFundsRadio.tsx:130, templates/chain-template/components/contract/ContractAddressField.tsx:146, …
  • This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — templates/chain-template/components/common/Radio/Radio.tsx:46
  • 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. — templates/chain-template/components/contract/SelectAssetItem.tsx:134
  • This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. 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. — templates/chain-template/components/staking/RedelegateModal.tsx:113

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.
AC6 · Visual & motion safety5.4 / 10Adequate✓ Tool-verified

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

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

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

  • `.radio` 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. (×2) — templates/chain-template/components/common/Radio/Radio.module.css:9, examples/spawn/components/common/Radio/Radio.module.css:9
  • `.ringLoader` moves (`animation: rotate-ring 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. (×2) — templates/chain-template/components/common/Wallet/RingLoader/ring.module.css:3, examples/spawn/components/common/Wallet/RingLoader/ring.module.css:3

What to do

  • Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
AX10 · Code composition9.7 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `IBinaryReader` declares 18 required operations: `tag`, `skip`, `skipType`, `uint32`, `int32`, `sint32`, `fixed32`, `sfixed32`, `int64`, `uint64`, `sint64`, `fixed64`, `sfixed64`, `float`, `double`, `bool`, `bytes`, `string`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — examples/authz/src/codegen/binary.ts:72, examples/telescope/src/codegen/binary.ts:71
  • `IBinaryWriter` declares 20 required operations: `finish`, `fork`, `reset`, `ldelim`, `tag`, `uint32`, `int32`, `sint32`, `int64`, `uint64`, `sint64`, `fixed64`, `sfixed64`, `bool`, `fixed32`, `sfixed32`, `float`, `double`, `bytes`, `string`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×2) — examples/authz/src/codegen/binary.ts:245, examples/telescope/src/codegen/binary.ts:244
  • `Query` declares 17 required operations: `moduleBalance`, `moduleLockedAmount`, `accountUnlockableCoins`, `accountUnlockingCoins`, `accountLockedCoins`, `accountLockedPastTime`, `accountLockedPastTimeNotUnlockingOnly`, `accountUnlockedBeforeTime`, `accountLockedPastTimeDenom`, `lockedDenom`, `lockedByID`, `syntheticLockupsByLockupID`, `accountLockedLongerDuration`, `accountLockedDuration`, `accountLockedLongerDurationNotUnlockingOnly`, `accountLockedLongerDurationDenom`, `params`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. (×3) — examples/authz/src/codegen/osmosis/lockup/query.rpc.Query.ts:12, examples/telescope-with-contracts/src/codegen/osmosis/lockup/query.rpc.Query.ts:6, examples/telescope/src/codegen/osmosis/lockup/query.rpc.Query.ts:9
  • `MarketplaceReadOnlyInterface` declares 23 required operations: `collections`, `ask`, `asks`, `reverseAsks`, `asksSortedByPrice`, `reverseAsksSortedByPrice`, `askCount`, `asksBySeller`, `bid`, `bidsByBidder`, `bidsByBidderSortedByExpiration`, `bids`, `bidsSortedByPrice`, `reverseBidsSortedByPrice`, `collectionBid`, `collectionBidsByBidder`, `collectionBidsByBidderSortedByExpiration`, `collectionBidsSortedByPrice`, `reverseCollectionBidsSortedByPrice`, `askHooks`, `bidHooks`, `saleHooks`, `params`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — examples/telescope-with-contracts/src/codegen/Marketplace.client.ts:10

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

IC1 · Incompleteness & stubs8.3 / 10Strong✓ Tool-verified

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

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

  • `warnIfOutdated` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:69
  • `onClick` 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. — templates/chain-template/components/contract/SelectAssetItem.tsx:98

What to do

  • Remove the dead code that looks live: delete dead if(false) branches, which read as logic that runs, and either do the real async work or drop the async keyword from fake-async functions, which promise work they never wait for.
M1 · Documentation (README)8.6 / 10Strong✓ Tool-verified

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

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

What to do

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

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

P2 · Observability0.0 / 10Critical✓ Tool-verified

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

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

  • No logging call was found in the 176 JavaScript/TypeScript production file(s) this check read across 10 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.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:5
  • `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:21

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

PF3 · Async & latency hygiene6.0 / 10Adequate✓ Tool-verified

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

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

  • `fs.readFileSync` in `warnIfOutdated` 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. — REDACTED:72
  • `fs.lstatSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:132, packages/create-cosmos-app/src/git-question-template.ts:84
  • `fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×5) — REDACTED:138, REDACTED:140, REDACTED:214, …
  • `fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — REDACTED:192, REDACTED:221, packages/create-cosmos-app/src/git-question-template.ts:125
  • `fs.existsSync` in `getQuestionsAndAnswers` 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/create-cosmos-app/src/utils.ts:70
  • `fs.readFileSync` in `getQuestionsAndAnswers` 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/create-cosmos-app/src/utils.ts:71

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.
R1 · Type Safety10.0 / 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.

R10 · Code Duplication2.1 / 10Critical✓ Tool-verified

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

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

  • examples/spawn/ and templates/chain-template/ are near-verbatim copies of each other: 136 files are byte-identical under the same relative paths (~8671 lines; the trees hold 170 and 173 files). That is one structural fact, not 136 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — templates/chain-template/components/contract/InstantiateContract.tsx:1
  • examples/rollkit/ and templates/connect-multi-chain/ are near-verbatim copies of each other: 15 files are byte-identical under the same relative paths (~688 lines; the trees hold 26 and 28 files). That is one structural fact, not 15 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — templates/connect-multi-chain/components/common/Footer.tsx:1
  • 11 of the duplicated blocks reported below have copies in at least two of the sibling directories connect-chain, connect-multi-chain under templates/. That concentration is one structural fact, not 11 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 11 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. — templates/connect-chain/components/common/Footer.tsx:9
  • 6 duplicated blocks under templates/chain-template/ have copies in at least two of the sibling directories components, hooks, pages, utils — 4 of them are reported below, and 2 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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. — templates/chain-template/components/contract/InstantiateContract.tsx:262
  • templates/connect-chain/components/common/Footer.tsx:9 · templates/connect-multi-chain/components/common/Footer.tsx:9 — these 2 files are line-for-line copies of one another — 97 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — templates/connect-chain/components/common/Footer.tsx:9
  • templates/connect-chain/components/wallet/Astronaut.tsx:1 · templates/connect-multi-chain/components/wallet/Astronaut.tsx:1 — these 2 files are line-for-line copies of one another — 81 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — templates/connect-chain/components/wallet/Astronaut.tsx:1
  • templates/chain-template/components/staking/DelegateModal.tsx:77 · templates/chain-template/components/staking/UndelegateModal.tsx:60 — the two spans are one implementation copied and then locally edited — 316 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. — templates/chain-template/components/staking/DelegateModal.tsx:77
  • templates/chain-template/components/staking/RedelegateModal.tsx:52 · templates/chain-template/components/staking/UndelegateModal.tsx:55 — the two spans are one implementation copied and then locally edited — 282 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. — templates/chain-template/components/staking/RedelegateModal.tsx:52
  • templates/chain-template/components/asset-list/DropdownTransferModal.tsx:38 · templates/chain-template/components/asset-list/RowTransferModal.tsx:19 — the two spans are one implementation copied and then locally edited — 265 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. — templates/chain-template/components/asset-list/DropdownTransferModal.tsx:38
  • templates/connect-chain/components/wallet/Wallet.tsx:34 · templates/connect-multi-chain/components/wallet/Wallet.tsx:43 — the two spans are one implementation copied and then locally edited — 304 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. — templates/connect-chain/components/wallet/Wallet.tsx:34
  • templates/chain-template/components/contract/ExecuteTab.tsx:18 · templates/chain-template/components/contract/QueryTab.tsx:13 — the two spans are one implementation copied and then locally edited — 199 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. — templates/chain-template/components/contract/ExecuteTab.tsx:18
  • templates/chain-template/hooks/contract/useExecuteContractTx.tsx:23 · templates/chain-template/hooks/contract/useInstantiateTx.tsx:24 — the two spans are one implementation copied and then locally edited — 190 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. — templates/chain-template/hooks/contract/useExecuteContractTx.tsx:23
  • templates/chain-template/components/staking/AllValidatorsList.tsx:33 · templates/chain-template/components/staking/SelectValidatorModal.tsx:38 — 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. — templates/chain-template/components/staking/AllValidatorsList.tsx:33
  • templates/connect-chain/components/common/Header.tsx:11 · templates/connect-multi-chain/components/common/Header.tsx:14 — 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. — templates/connect-chain/components/common/Header.tsx:11
  • templates/connect-chain/config/projects.ts:1 · templates/connect-multi-chain/config/projects.ts:1 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents. — templates/connect-chain/config/projects.ts:1
  • templates/chain-template/components/asset-list/DropdownTransferModal.tsx:129 · templates/chain-template/components/asset-list/RowTransferModal.tsx:108 · templates/chain-template/components/asset-list/RowTransferModal.tsx:173 — the 3 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. — templates/chain-template/components/asset-list/DropdownTransferModal.tsx:129
  • templates/chain-template/components/staking/AllValidatorsList.tsx:33 · templates/chain-template/components/staking/MyValidatorsList.tsx:32 · templates/chain-template/components/staking/SelectValidatorModal.tsx:38 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — templates/chain-template/components/staking/AllValidatorsList.tsx:33
  • packages/create-cosmos-app/src/git-question-template.ts:49 · packages/create-cosmos-app/src/utils.ts:102 — 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/create-cosmos-app/src/git-question-template.ts:49
  • templates/connect-chain/components/wallet/Connect.tsx:16 · templates/connect-multi-chain/components/wallet/Connect.tsx:16 — 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. — templates/connect-chain/components/wallet/Connect.tsx:16
  • templates/chain-template/components/contract/InstantiateContract.tsx:262 · templates/chain-template/pages/faucet.tsx:114 — 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. — templates/chain-template/components/contract/InstantiateContract.tsx:262
  • templates/chain-template/components/contract/CodeIdField.tsx:32 · templates/chain-template/components/contract/ContractAddressField.tsx:96 — the two spans are one implementation copied and then locally edited — 121 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. — templates/chain-template/components/contract/CodeIdField.tsx:32
  • templates/connect-chain/components/wallet/Warning.tsx:17 · templates/connect-multi-chain/components/wallet/Warning.tsx:17 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — templates/connect-chain/components/wallet/Warning.tsx:17
  • templates/chain-template/components/contract/ExecuteTab.tsx:70 · templates/chain-template/components/contract/UploadContract.tsx:65 — 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. — templates/chain-template/components/contract/ExecuteTab.tsx:70
  • templates/chain-template/components/staking/AllValidators.tsx:30 · templates/chain-template/components/staking/MyValidators.tsx:43 — 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. — templates/chain-template/components/staking/AllValidators.tsx:30
  • templates/connect-chain/components/wallet/User.tsx:10 · templates/connect-multi-chain/components/wallet/User.tsx:10 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — templates/connect-chain/components/wallet/User.tsx:10
  • templates/chain-template/components/asset-list/RowTransferModal.tsx:137 · templates/chain-template/components/asset-list/RowTransferModal.tsx:202 — 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. — templates/chain-template/components/asset-list/RowTransferModal.tsx:137
  • templates/chain-template/hooks/contract/useExecuteContractTx.tsx:67 · templates/chain-template/hooks/contract/useInstantiateTx.tsx:65 · templates/chain-template/hooks/contract/useStoreCodeTx.tsx:64 — the 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — templates/chain-template/hooks/contract/useExecuteContractTx.tsx:67
  • templates/chain-template/hooks/voting/useVotingData.ts:15 · templates/chain-template/utils/voting.ts:57 — 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. — templates/chain-template/hooks/voting/useVotingData.ts:15
  • templates/chain-template/pages/faucet.tsx:83 · templates/chain-template/pages/index.tsx:17 — 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. — templates/chain-template/pages/faucet.tsx:83
  • templates/connect-chain/pages/_app.tsx:15 · templates/connect-multi-chain/pages/_app.tsx:15 — 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. — templates/connect-chain/pages/_app.tsx:15
  • templates/chain-template/hooks/asset-list/useOsmoQueryHooks.ts:5 · templates/chain-template/hooks/voting/useQueryHooks.ts:9 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — templates/chain-template/hooks/asset-list/useOsmoQueryHooks.ts:5
  • templates/chain-template/components/staking/AllValidatorsList.tsx:94 · templates/chain-template/components/staking/SelectValidatorModal.tsx:100 — 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. — templates/chain-template/components/staking/AllValidatorsList.tsx:94
  • templates/chain-template/hooks/asset-list/useAssets.ts:45 · templates/chain-template/hooks/asset-list/useTotalAssets.ts:91 — 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. — templates/chain-template/hooks/asset-list/useAssets.ts:45
  • templates/connect-chain/components/common/Layout.tsx:6 · templates/connect-multi-chain/components/common/Layout.tsx:6 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — templates/connect-chain/components/common/Layout.tsx:6
  • templates/chain-template/hooks/asset-list/useChainAssetsPrices.ts:23 · templates/chain-template/hooks/staking/useAssetsPrices.ts:29 — 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. — templates/chain-template/hooks/asset-list/useChainAssetsPrices.ts:23
  • packages/create-cosmos-app/src/git-question-template.ts:26 · packages/create-cosmos-app/src/utils.ts:71 — 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/create-cosmos-app/src/git-question-template.ts:26
  • templates/chain-template/hooks/asset-list/useAssets.ts:24 · templates/chain-template/hooks/asset-list/useTotalAssets.ts:33 — 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. — templates/chain-template/hooks/asset-list/useAssets.ts:24
  • templates/chain-template/components/contract/ContractAddressField.tsx:18 · templates/chain-template/components/contract/JsonInput.tsx:15 — 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. — templates/chain-template/components/contract/ContractAddressField.tsx:18
  • templates/chain-template/components/staking/DelegateModal.tsx:166 · templates/chain-template/components/staking/UndelegateModal.tsx:93 · templates/chain-template/components/staking/ValidatorInfoModal.tsx:40 — the 3 copies are spread across 3 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. — templates/chain-template/components/staking/DelegateModal.tsx:166
  • templates/chain-template/hooks/voting/useVotingData.ts:45 · templates/chain-template/hooks/voting/useVotingData.ts:76 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — templates/chain-template/hooks/voting/useVotingData.ts:45

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries5.6 / 10Adequate✓ Tool-verified

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

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

  • templates/chain-template/hooks/asset-list/useTotalAssets.ts:9 imports osmo-query/dist/codegen/osmosis/gamm/pool-models/balancer/balancerPool, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/chain-template/hooks/asset-list/useTotalAssets.ts:9
  • templates/chain-template/utils/asset-list/pool.ts:1 imports osmo-query/dist/codegen/osmosis/gamm/pool-models/balancer/balancerPool, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/chain-template/utils/asset-list/pool.ts:1
  • templates/chain-template/utils/asset-list/pool.ts:2 imports osmo-query/dist/codegen/cosmos/base/v1beta1/coin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/chain-template/utils/asset-list/pool.ts:2
  • templates/chain-template/utils/asset-list/types.ts:2 imports osmo-query/dist/codegen/google/protobuf/duration, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/chain-template/utils/asset-list/types.ts:2
  • templates/chain-template/utils/asset-list/types.ts:3 imports osmo-query/dist/codegen/osmosis/incentives/gauge, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/chain-template/utils/asset-list/types.ts:3
  • templates/chain-template/utils/asset-list/types.ts:4 imports osmo-query/dist/codegen/osmosis/superfluid/superfluid, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/chain-template/utils/asset-list/types.ts:4
  • templates/chain-template/utils/asset-list/types.ts:5 imports osmo-query/dist/codegen/cosmos/base/v1beta1/coin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/chain-template/utils/asset-list/types.ts:5
  • templates/chain-template/utils/asset-list/types.ts:6 imports osmo-query/dist/codegen/osmosis/gamm/pool-models/balancer/balancerPool, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/chain-template/utils/asset-list/types.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.
R2 · Cyclomatic Complexity9.9 / 10Exemplary✓ Tool-verified

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

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

  • Proposal has cyclomatic complexity 25 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — templates/chain-template/components/voting/Proposal.tsx:53
  • (anonymous) has cyclomatic complexity 19 and cognitive complexity 38; 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. — REDACTED:80
  • InstantiateContract has cyclomatic complexity 19 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — templates/chain-template/components/contract/InstantiateContract.tsx:45
  • Button has cyclomatic complexity 12 and cognitive complexity 11; 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. — templates/chain-template/components/common/Button.tsx:83
  • getTemplateFolder has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/create-cosmos-app/src/utils.ts:15
  • Drawer has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — templates/chain-template/components/common/Drawer.tsx:12
R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

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

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

R4 · Test Coverage0.1 / 10Critical✓ 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.

  • boilerplates/lerna-module/jest.config.js declares environment "node", and no package here declares a DOM implementation (jsdom / happy-dom), a component testing library or a browser runner — so none of the 96 unreached component module(s) can be tested as written, however the suite is authored: templates/chain-template/components/voting/Proposal.tsx, templates/chain-template/components/contract/InstantiateContract.tsx, templates/chain-template/components/asset-list/DropdownTransferModal.tsx, templates/chain-template/components/asset-list/RowTransferModal.tsx, templates/chain-template/components/staking/DelegateModal.tsx, templates/chain-template/components/voting/Voting.tsx and 90 more. Add a DOM environment and a component testing library (for example jsdom + @testing-library, or the runner's browser mode), then test the components. Reported once because these files share one cause, not one omission each. — boilerplates/lerna-module/jest.config.js: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. (×39) — templates/chain-template/utils/asset-list/pool.ts:1, templates/chain-template/hooks/staking/useStakingData.ts:1, REDACTED:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED 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: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • `examples/provide-liquidity` is TypeScript, but a type error in it cannot fail anything this repository runs: its Next.js config sets `typescript.ignoreBuildErrors: true`, so `next build` — the one step that would run the type checker — passes over type errors, and no script, config or CI step of the package runs `tsc` instead. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles. — examples/provide-liquidity/next.config.js:4
  • The package in `boilerplates/lerna-module` declares the lint script `lint` (`eslint . --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `boilerplates/lerna-module` (or the workspace's task runner). — boilerplates/lerna-module/REDACTED:28
  • The package in `boilerplates/ts-codegen-npm-module` declares the lint script `lint` (`eslint src --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `boilerplates/ts-codegen-npm-module` (or the workspace's task runner). — boilerplates/ts-codegen-npm-module/REDACTED:28
  • The package in `boilerplates/website` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `boilerplates/website` (or the workspace's task runner). — boilerplates/website/REDACTED:9
  • The package in `examples/grpc-web-grpc-gateway` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/grpc-web-grpc-gateway` (or the workspace's task runner). — examples/grpc-web-grpc-gateway/REDACTED:9
  • The package in `examples/ibc-asset-list` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/ibc-asset-list` (or the workspace's task runner). — examples/ibc-asset-list/REDACTED:9
  • The package in `examples/nft` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/nft` (or the workspace's task runner). — REDACTED:9
  • The package in `examples/provide-liquidity` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/provide-liquidity` (or the workspace's task runner). — examples/provide-liquidity/REDACTED:9
  • The package in `examples/rollkit` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/rollkit` (or the workspace's task runner). — examples/rollkit/REDACTED:9
  • The package in `examples/spawn` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/spawn` (or the workspace's task runner). — examples/spawn/REDACTED:9
  • The package in `examples/stake-tokens` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/stake-tokens` (or the workspace's task runner). — examples/stake-tokens/REDACTED:9
  • The package in `examples/swap-tokens` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/swap-tokens` (or the workspace's task runner). — examples/swap-tokens/REDACTED:9
  • The package in `examples/telescope-with-contracts` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/telescope-with-contracts` (or the workspace's task runner). — REDACTED:9
  • The package in `examples/telescope` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/telescope` (or the workspace's task runner). — examples/telescope/REDACTED:9
  • The package in `examples/vote-proposal` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/vote-proposal` (or the workspace's task runner). — examples/vote-proposal/REDACTED:9
  • The package in `packages/create-cosmos-app` declares the lint script `lint` (`eslint .`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/create-cosmos-app` (or the workspace's task runner). — packages/create-cosmos-app/REDACTED:27
  • The package in `templates/chain-template` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `templates/chain-template` (or the workspace's task runner). — templates/chain-template/REDACTED:9
  • The package in `templates/connect-chain` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `templates/connect-chain` (or the workspace's task runner). — templates/connect-chain/REDACTED:9
  • The package in `templates/connect-multi-chain` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `templates/connect-multi-chain` (or the workspace's task runner). — templates/connect-multi-chain/REDACTED:9
  • The package in `boilerplates/telescope/packages/__MODULENAME__` declares the lint script `lint` (`eslint . --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `boilerplates/telescope/packages/__MODULENAME__` (or the workspace's task runner). — boilerplates/telescope/packages/__MODULENAME__/REDACTED:29
R7 · Dead Code8.7 / 10Strong✓ 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.

  • 1 file(s) (~4 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
  • Unreachable from the 25 application, 14 tooling and 5 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (25 application, 14 tooling, 5 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — packages/create-cosmos-app/src/git-question-template.ts, templates/connect-multi-chain/utils/index.ts
  • Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/components/asset-list/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 templates/chain-template/components/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists. — templates/chain-template/components/asset-list/types.tsx:52
  • Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists. (×11) — templates/chain-template/utils/asset-list/base.ts:51, templates/chain-template/utils/asset-list/pool.ts:34, templates/chain-template/utils/asset-list/pool.ts:52, …
  • Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/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 templates/chain-template/utils/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — templates/chain-template/utils/voting.ts:9, templates/chain-template/utils/voting.ts:60
  • Nothing imports this binding — it is safe to review for removal. (×3) — templates/connect-chain/components/wallet/Chain.tsx:9, templates/connect-chain/components/wallet/Warning.tsx:15, templates/connect-multi-chain/components/wallet/Warning.tsx:15

What to do

  • Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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

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

  • Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×3) — templates/chain-template/utils/contract.ts:2, templates/chain-template/components/common/Wallet/Connected.tsx:4, templates/connect-multi-chain/components/wallet/Wallet.tsx:8
  • Declared in boilerplates/lerna-workspace/REDACTED 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. (×2) — boilerplates/lerna-workspace/REDACTED:30, boilerplates/lerna-workspace/REDACTED:39
  • Declared in boilerplates/telescope/REDACTED 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. — boilerplates/telescope/REDACTED:40
  • Declared in packages/create-cosmos-app/REDACTED 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. — packages/create-cosmos-app/REDACTED:51
  • Declared in templates/chain-template/REDACTED 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. — templates/chain-template/REDACTED:59
  • Declared in templates/connect-chain/REDACTED 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. (×3) — templates/connect-chain/REDACTED:25, templates/connect-chain/REDACTED:26, templates/connect-chain/REDACTED:31
  • Declared in templates/connect-multi-chain/REDACTED 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. (×3) — templates/connect-multi-chain/REDACTED:25, templates/connect-multi-chain/REDACTED:26, templates/connect-multi-chain/REDACTED:32

What to do

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

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

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

  • templates/chain-template/components/asset-list/AssetListSection.tsx → templates/chain-template/components/asset-list/AssetsOverview.tsx → templates/chain-template/components/asset-list/DropdownTransferModal.tsx → templates/chain-template/hooks/index.ts → templates/chain-template/hooks/asset-list/index.ts → templates/chain-template/hooks/asset-list/useAssets.ts → templates/chain-template/components/index.ts → templates/chain-template/components/asset-list/index.ts → templates/chain-template/components/asset-list/AssetListSection.tsx (one verified cycle inside a mutually-dependent group of 82 files) — templates/chain-template/components/asset-list/AssetListSection.tsx:3

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

  • Only 0/7 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
  • `creditFromFaucet` 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 })`. — templates/chain-template/utils/faucet.ts:51
  • `isUrlValid` 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 })`. — templates/chain-template/utils/staking/logos.ts:43
  • `getLogoUrls` 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 })`. — templates/chain-template/utils/staking/logos.ts:70
  • `fetchPrices` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×2) — templates/chain-template/hooks/staking/useAssetsPrices.ts:34, templates/chain-template/hooks/asset-list/useChainAssetsPrices.ts:28
  • `fetcher` 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 })`. — templates/chain-template/hooks/common/useStarshipChains.ts:38
  • `fetchTokens` 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 })`. — templates/chain-template/hooks/asset-list/useTopTokens.ts:22

What to do

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

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

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

X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

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.

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

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

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

X3 · Exception handling6.6 / 10Adequate✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — templates/chain-template/components/voting/Voting.tsx:86

What to do

  • Swallowed exception (empty catch)
X5 · Nullable reference types6.8 / 10Adequate✓ Tool-verified

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.

  • 16/24 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
  • ~1.8 `!` null assertions per 1k TypeScript source lines — 28 assertion(s) across the 15482 source line(s) of the 213 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: templates/chain-template/components/voting/Voting.tsx (6), templates/chain-template/components/contract/AttachFundsRadio.tsx (2), templates/chain-template/components/contract/JsonEditor.tsx (2). 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 `?`).

WCAG coverage — what static analysis assessed

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

DimensionWCAG 2.2 A/AA criteriaCoverage
AC2 · Forms & labels1.3.1, 3.3.2, 4.1.2Partial signal
AC6 · Visual & motion safety1.4.3, 2.4.7Partial — literal CSS only

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

Reference — by lens

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

LensScoreRatingImpact
Code Health56.7Adequate — gated by R10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture59.8Adequate — gated by R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity46.8Weak — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness20.6Critical — gated by D10, R4, R8, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security65.1Adequate — gated by D29Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility32.4Weak — gated by AC2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60.0AdequateStrongest area.
Unscored — 5 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.

  • D36 Supply-chain Provenance & Signing — 2 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
  • SC1 Supply-chain hygiene — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 7 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

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

  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 62 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
  • AC3 Page structure — No structural check found in the parsed markup — AC3 not applicable here.
  • AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
  • AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
  • 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 — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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` in boilerplates/website/) kept running but served no page within 2 minutes. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "You can learn more, including how to opt-out if you'd not like to participate in this anonymous program, by visiting the following URL: / https://nextjs.org/telemetry / /bin/sh: 1: yarn: not found / ▲ Next.js 13.5.6 / - Local: http://localhost:3000 / ✓ Ready in 697ms / Browserslist: caniuse-lite is outdated. Please run: / npx browserslist@latest --update-db / Why you should do it regularly: https://github.com/browserslist/browserslist#browsers-data-updating / ○ Compiling / ... / ✓ Compiled / in 3.3s (1474 modules)" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
  • C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
  • D11 Test Reliability — JavaScript/TypeScript suite in examples/authz/ was not re-run
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • 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 — no ADRs to check
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D4 Code Duplication — 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.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
  • DM1 Domain Modelling — not scored — this repository shows 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
  • M4 Documentation accuracy — Not applicable: the 11 current-state document(s) make no claim of a kind M4 checks. 24 claim(s) of kinds M4 does not check were not checked (path 1, command argument 18, install 5); M4 checks only links and versions and artefact counts.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, 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 yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • S1 Web-Security Posture — Not assessed: 217 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. 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.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X20 Mistyped argument guard — 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
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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.
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — 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.

Critical — 658 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×486
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 461 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical CVE · ×103
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 78 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical vulnerability · ×43
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 18 more in this group — see findings.md.
D11 · Test Reliability · Test suite cannot be installed from its own lockfile · ×9
  • Test suite cannot be installed from its own lockfile: the repository root — The jest suite in the repository root was never exercised because its dependency install refused the committed lockfile — the dependency install for the repository root refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
  • Test suite cannot be installed from its own lockfile: boilerplates/lerna-module/ — The jest suite in boilerplates/lerna-module/ was never exercised because its dependency install refused the committed lockfile — the dependency install for boilerplates/lerna-module/ refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
  • Test suite cannot be installed from its own lockfile: boilerplates/lerna-tsx-module/ — The jest suite in boilerplates/lerna-tsx-module/ was never exercised because its dependency install refused the committed lockfile — the dependency install for boilerplates/lerna-tsx-module/ refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
  • Test suite cannot be installed from its own lockfile: boilerplates/lerna-workspace/ — The jest suite in boilerplates/lerna-workspace/ was never exercised because its dependency install refused the committed lockfile — the dependency install for boilerplates/lerna-workspace/ refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
  • Test suite cannot be installed from its own lockfile: boilerplates/npm-boilerplate/ — The jest suite in boilerplates/npm-boilerplate/ was never exercised because its dependency install refused the committed lockfile — the dependency install for boilerplates/npm-boilerplate/ refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
  • Test suite cannot be installed from its own lockfile: boilerplates/telescope/ — The jest suite in boilerplates/telescope/ was never exercised because its dependency install refused the committed lockfile — the dependency install for boilerplates/telescope/ refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
  • Test suite cannot be installed from its own lockfile: boilerplates/telescope/packages/__MODULENAME__/ — The jest suite in boilerplates/telescope/packages/__MODULENAME__/ was never exercised because its dependency install refused the committed lockfile — the dependency install for boilerplates/telescope/packages/__MODULENAME__/ refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
  • Test suite cannot be installed from its own lockfile: boilerplates/ts-codegen-npm-module/ — The jest suite in boilerplates/ts-codegen-npm-module/ was never exercised because its dependency install refused the committed lockfile — the dependency install for boilerplates/ts-codegen-npm-module/ refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
  • Test suite cannot be installed from its own lockfile: packages/create-cosmos-app/ — The jest suite in packages/create-cosmos-app/ was never exercised because its dependency install refused the committed lockfile — the dependency install for packages/create-cosmos-app/ refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. The suite is declared and committed but cannot be installed from what the repository ships, so neither this scan nor a new contributor can run it. The ask is the one the owner performs: run the install locally and commit the lockfile it writes.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
R8 · Dependency Hygiene · Unlisted import '@cosmos-kit/core' · ×2
  • Unlisted import '@cosmos-kit/core' templates/chain-template/components/common/Wallet/Connected.tsx:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
  • Unlisted import '@cosmos-kit/core' templates/connect-multi-chain/components/wallet/Wallet.tsx:8 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
AC2 · Forms & labels · <input> without a programmatic label · ×1
  • <input> without a programmatic label templates/chain-template/components/common/Radio/Radio.tsx:46 — This control has no associated label. Add a <label htmlFor> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import '@cosmjs/encoding' · ×1
  • Unlisted import '@cosmjs/encoding' templates/chain-template/utils/contract.ts:2 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (8 files) · ×1
  • Import cycle (8 files) templates/chain-template/components/asset-list/AssetListSection.tsx:3 — templates/chain-template/components/asset-list/AssetListSection.tsx → templates/chain-template/components/asset-list/AssetsOverview.tsx → templates/chain-template/components/asset-list/DropdownTransferModal.tsx → templates/chain-template/hooks/index.ts → templates/chain-template/hooks/asset-list/index.ts → templates/chain-template/hooks/asset-list/useAssets.ts → templates/chain-template/components/index.ts → templates/chain-template/components/asset-list/index.ts → templates/chain-template/components/asset-list/AssetListSection.tsx (one verified cycle inside a mutually-dependent group of 82 files)
Serious — 401 finding(s)
D30 · Dependency Vulnerabilities · Medium CVE · ×183
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 158 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×39
  • No test reaches this file templates/chain-template/utils/asset-list/pool.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 templates/chain-template/hooks/staking/useStakingData.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 REDACTED: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 templates/chain-template/hooks/asset-list/useTotalAssets.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 templates/chain-template/hooks/voting/useVotingData.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 templates/chain-template/utils/contract.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 templates/chain-template/utils/staking/staking.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 templates/chain-template/hooks/asset-list/useChainUtils.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 packages/create-cosmos-app/src/utils.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 packages/create-cosmos-app/src/git-question-template.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 templates/chain-template/hooks/asset-list/useAssets.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 templates/chain-template/utils/staking/logos.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 templates/chain-template/hooks/common/useTx.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 boilerplates/telescope/packages/__MODULENAME__/scripts/codegen.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 templates/chain-template/utils/asset-list/base.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 templates/chain-template/hooks/voting/useVotingTx.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 templates/chain-template/utils/faucet.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 templates/chain-template/utils/voting.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 templates/chain-template/hooks/voting/useVoting.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 packages/create-cosmos-app/src/prompt.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 templates/chain-template/utils/common.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 templates/chain-template/hooks/staking/useAssetsPrices.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 templates/chain-template/hooks/asset-list/useBalance.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 templates/chain-template/hooks/asset-list/useChainAssetsPrices.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 templates/chain-template/utils/staking/math.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.
  • + 14 more in this group — see findings.md.
R6 · Tooling · This package's lint script runs in no CI job · ×19
  • This package's lint script runs in no CI job boilerplates/lerna-module/REDACTED:28 — The package in `boilerplates/lerna-module` declares the lint script `lint` (`eslint . --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `boilerplates/lerna-module` (or the workspace's task runner).
  • This package's lint script runs in no CI job boilerplates/ts-codegen-npm-module/REDACTED:28 — The package in `boilerplates/ts-codegen-npm-module` declares the lint script `lint` (`eslint src --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `boilerplates/ts-codegen-npm-module` (or the workspace's task runner).
  • This package's lint script runs in no CI job boilerplates/website/REDACTED:9 — The package in `boilerplates/website` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `boilerplates/website` (or the workspace's task runner).
  • This package's lint script runs in no CI job examples/grpc-web-grpc-gateway/REDACTED:9 — The package in `examples/grpc-web-grpc-gateway` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/grpc-web-grpc-gateway` (or the workspace's task runner).
  • This package's lint script runs in no CI job examples/ibc-asset-list/REDACTED:9 — The package in `examples/ibc-asset-list` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/ibc-asset-list` (or the workspace's task runner).
  • This package's lint script runs in no CI job REDACTED:9 — The package in `examples/nft` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/nft` (or the workspace's task runner).
  • This package's lint script runs in no CI job examples/provide-liquidity/REDACTED:9 — The package in `examples/provide-liquidity` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/provide-liquidity` (or the workspace's task runner).
  • This package's lint script runs in no CI job examples/rollkit/REDACTED:9 — The package in `examples/rollkit` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/rollkit` (or the workspace's task runner).
  • This package's lint script runs in no CI job examples/spawn/REDACTED:9 — The package in `examples/spawn` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/spawn` (or the workspace's task runner).
  • This package's lint script runs in no CI job examples/stake-tokens/REDACTED:9 — The package in `examples/stake-tokens` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/stake-tokens` (or the workspace's task runner).
  • This package's lint script runs in no CI job examples/swap-tokens/REDACTED:9 — The package in `examples/swap-tokens` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/swap-tokens` (or the workspace's task runner).
  • This package's lint script runs in no CI job REDACTED:9 — The package in `examples/telescope-with-contracts` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/telescope-with-contracts` (or the workspace's task runner).
  • This package's lint script runs in no CI job examples/telescope/REDACTED:9 — The package in `examples/telescope` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/telescope` (or the workspace's task runner).
  • This package's lint script runs in no CI job examples/vote-proposal/REDACTED:9 — The package in `examples/vote-proposal` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `examples/vote-proposal` (or the workspace's task runner).
  • This package's lint script runs in no CI job packages/create-cosmos-app/REDACTED:27 — The package in `packages/create-cosmos-app` declares the lint script `lint` (`eslint .`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `packages/create-cosmos-app` (or the workspace's task runner).
  • This package's lint script runs in no CI job templates/chain-template/REDACTED:9 — The package in `templates/chain-template` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `templates/chain-template` (or the workspace's task runner).
  • This package's lint script runs in no CI job templates/connect-chain/REDACTED:9 — The package in `templates/connect-chain` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `templates/connect-chain` (or the workspace's task runner).
  • This package's lint script runs in no CI job templates/connect-multi-chain/REDACTED:9 — The package in `templates/connect-multi-chain` declares the lint script `lint` (`next lint`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `templates/connect-multi-chain` (or the workspace's task runner).
  • This package's lint script runs in no CI job boilerplates/telescope/packages/__MODULENAME__/REDACTED:29 — The package in `boilerplates/telescope/packages/__MODULENAME__` declares the lint script `lint` (`eslint . --fix`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `boilerplates/telescope/packages/__MODULENAME__` (or the workspace's task runner).
D30 · Dependency Vulnerabilities · Medium vulnerability · ×15
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
PF3 · Async & latency hygiene · Sync-over-async blocking · ×13
  • Sync-over-async blocking REDACTED:72 — `fs.readFileSync` in `warnIfOutdated` 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 REDACTED:132 — `fs.lstatSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:138 — `fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:140 — `fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:192 — `fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:214 — `fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking REDACTED:221 — `fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-cosmos-app/src/git-question-template.ts:26 — `fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-cosmos-app/src/git-question-template.ts:84 — `fs.lstatSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-cosmos-app/src/git-question-template.ts:86 — `fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-cosmos-app/src/git-question-template.ts:125 — `fs.writeFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/create-cosmos-app/src/utils.ts:70 — `fs.existsSync` in `getQuestionsAndAnswers` 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/create-cosmos-app/src/utils.ts:71 — `fs.readFileSync` in `getQuestionsAndAnswers` 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.
D17 · Explicit Debt · TodoComment · ×9
  • TodoComment templates/chain-template/utils/asset-list/pool.ts:265 — // TODO fix the fact this is seemingly using long — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment examples/spawn/utils/asset-list/pool.ts:265 — // TODO fix the fact this is seemingly using long — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment examples/ibc-asset-list/utils/pool.ts:265 — // TODO fix the fact this is seemingly using long — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment templates/chain-template/utils/asset-list/pool.ts:266 — // TODO or, why do we even have pools here??? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment examples/spawn/utils/asset-list/pool.ts:266 — // TODO or, why do we even have pools here??? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment examples/ibc-asset-list/utils/pool.ts:266 — // TODO or, why do we even have pools here??? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment examples/stake-tokens/pages/_app.tsx:35 — // TODO fix type error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment examples/stake-tokens/pages/_app.tsx:40 — // TODO fix type error — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment examples/stake-tokens/components/wallet/WarnBlock.tsx:30 — // TODO fix type error — 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.
R11 · Import Boundaries · Boundary violation [package · ×8
  • Boundary violation [package:third-party-deep-import] templates/chain-template/hooks/asset-list/useTotalAssets.ts:9 — templates/chain-template/hooks/asset-list/useTotalAssets.ts:9 imports osmo-query/dist/codegen/osmosis/gamm/pool-models/balancer/balancerPool, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] templates/chain-template/utils/asset-list/pool.ts:1 — templates/chain-template/utils/asset-list/pool.ts:1 imports osmo-query/dist/codegen/osmosis/gamm/pool-models/balancer/balancerPool, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] templates/chain-template/utils/asset-list/pool.ts:2 — templates/chain-template/utils/asset-list/pool.ts:2 imports osmo-query/dist/codegen/cosmos/base/v1beta1/coin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] templates/chain-template/utils/asset-list/types.ts:2 — templates/chain-template/utils/asset-list/types.ts:2 imports osmo-query/dist/codegen/google/protobuf/duration, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] templates/chain-template/utils/asset-list/types.ts:3 — templates/chain-template/utils/asset-list/types.ts:3 imports osmo-query/dist/codegen/osmosis/incentives/gauge, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] templates/chain-template/utils/asset-list/types.ts:4 — templates/chain-template/utils/asset-list/types.ts:4 imports osmo-query/dist/codegen/osmosis/superfluid/superfluid, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] templates/chain-template/utils/asset-list/types.ts:5 — templates/chain-template/utils/asset-list/types.ts:5 imports osmo-query/dist/codegen/cosmos/base/v1beta1/coin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] templates/chain-template/utils/asset-list/types.ts:6 — templates/chain-template/utils/asset-list/types.ts:6 imports osmo-query/dist/codegen/osmosis/gamm/pool-models/balancer/balancerPool, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
X2 · Cancellation propagation · Async function without AbortSignal · ×7
  • Async function without AbortSignal: creditFromFaucet templates/chain-template/utils/faucet.ts:51 — `creditFromFaucet` 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: isUrlValid templates/chain-template/utils/staking/logos.ts:43 — `isUrlValid` 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: getLogoUrls templates/chain-template/utils/staking/logos.ts:70 — `getLogoUrls` 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: fetchPrices templates/chain-template/hooks/staking/useAssetsPrices.ts:34 — `fetchPrices` 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: fetcher templates/chain-template/hooks/common/useStarshipChains.ts:38 — `fetcher` 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: fetchPrices templates/chain-template/hooks/asset-list/useChainAssetsPrices.ts:28 — `fetchPrices` 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: fetchTokens templates/chain-template/hooks/asset-list/useTopTokens.ts:22 — `fetchTokens` 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 })`.
D12 · Dependency Hygiene · Deprecated · ×6
  • Deprecated: eslint boilerplates/lerna-workspace/REDACTED:34 — eslint 8.57.1, declared in boilerplates/lerna-workspace/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint boilerplates/npm-boilerplate/REDACTED:38 — eslint 8.57.1, declared in boilerplates/npm-boilerplate/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint boilerplates/telescope/REDACTED:35 — eslint 8.57.1, declared in boilerplates/telescope/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint REDACTED:28 — eslint 8.28.0, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint packages/create-cosmos-app/REDACTED:52 — eslint 8.28.0, declared in packages/create-cosmos-app/REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: glob packages/create-cosmos-app/REDACTED:55 — glob 8.0.3, declared in packages/create-cosmos-app/REDACTED, is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". Replace it with the package or version that message names, or record why this one must stay.
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×5
  • JavaScript dependencies are not locked boilerplates/lerna-tsx-module/REDACTED:30 — boilerplates/lerna-tsx-module/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked boilerplates/lerna-workspace/REDACTED:25 — boilerplates/lerna-workspace/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked boilerplates/npm-boilerplate/REDACTED:30 — boilerplates/npm-boilerplate/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked boilerplates/telescope/REDACTED:26 — boilerplates/telescope/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked boilerplates/ts-codegen-npm-module/REDACTED:44 — boilerplates/ts-codegen-npm-module/REDACTED declares dependencies that no committed lockfile resolves — there is no package-lock.json / REDACTED / pnpm-lock.yaml / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
D10 · Test Quality · No assertions · ×4
  • No assertions: it works boilerplates/ts-codegen-npm-module/__tests__/example.test.ts:1 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: works boilerplates/npm-boilerplate/__tests__/first.test.ts:3 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: works boilerplates/lerna-tsx-module/__tests__/first.test.ts:1 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: works boilerplates/lerna-module/__tests__/first.test.ts:1 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
D10 · Test Quality · Test project verifies nothing · ×4
  • Test project verifies nothing: boilerplates/lerna-module boilerplates/lerna-module/__tests__/first.test.ts:1 — No conventional assertion call was detected in 1 of 1 tests in `boilerplates/lerna-module` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: boilerplates/lerna-tsx-module boilerplates/lerna-tsx-module/__tests__/first.test.ts:1 — No conventional assertion call was detected in 1 of 1 tests in `boilerplates/lerna-tsx-module` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: boilerplates/npm-boilerplate boilerplates/npm-boilerplate/__tests__/first.test.ts:3 — No conventional assertion call was detected in 1 of 1 tests in `boilerplates/npm-boilerplate` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
  • Test project verifies nothing: boilerplates/ts-codegen-npm-module boilerplates/ts-codegen-npm-module/__tests__/example.test.ts:1 — No conventional assertion call was detected in 1 of 1 tests in `boilerplates/ts-codegen-npm-module` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×3
  • Duplicated block (18 lines × 2 locations) templates/chain-template/components/contract/ExecuteTab.tsx:70 — templates/chain-template/components/contract/ExecuteTab.tsx:70 · templates/chain-template/components/contract/UploadContract.tsx:65 — 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 (18 lines × 2 locations) templates/chain-template/components/staking/AllValidators.tsx:30 — templates/chain-template/components/staking/AllValidators.tsx:30 · templates/chain-template/components/staking/MyValidators.tsx:43 — 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 (18 lines × 2 locations) templates/connect-chain/components/wallet/User.tsx:10 — templates/connect-chain/components/wallet/User.tsx:10 · templates/connect-multi-chain/components/wallet/User.tsx:10 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×3
  • Duplicated block (17 lines × 2 locations) templates/chain-template/components/asset-list/RowTransferModal.tsx:137 — templates/chain-template/components/asset-list/RowTransferModal.tsx:137 · templates/chain-template/components/asset-list/RowTransferModal.tsx:202 — 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 (17 lines × 2 locations) templates/chain-template/hooks/voting/useVotingData.ts:15 — templates/chain-template/hooks/voting/useVotingData.ts:15 · templates/chain-template/utils/voting.ts:57 — 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 (17 lines × 2 locations) templates/chain-template/pages/faucet.tsx:83 — templates/chain-template/pages/faucet.tsx:83 · templates/chain-template/pages/index.tsx:17 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×3
  • Duplicated block (14 lines × 2 locations) templates/chain-template/components/staking/AllValidatorsList.tsx:94 — templates/chain-template/components/staking/AllValidatorsList.tsx:94 · templates/chain-template/components/staking/SelectValidatorModal.tsx:100 — 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 (14 lines × 2 locations) templates/chain-template/hooks/asset-list/useAssets.ts:45 — templates/chain-template/hooks/asset-list/useAssets.ts:45 · templates/chain-template/hooks/asset-list/useTotalAssets.ts:91 — 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 (14 lines × 2 locations) templates/connect-chain/components/common/Layout.tsx:6 — templates/connect-chain/components/common/Layout.tsx:6 · templates/connect-multi-chain/components/common/Layout.tsx:6 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
AC2 · Forms & labels · <Combobox> field component without a label · ×2
  • <Combobox> field component without a label templates/chain-template/components/common/Header/ChainDropdown.tsx:47 — 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.
  • <Combobox> field component without a label templates/chain-template/components/contract/ContractAddressField.tsx:146 — 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.
AC2 · Forms & labels · <RadioGroup> field component without a label · ×2
  • <RadioGroup> field component without a label templates/chain-template/components/contract/AttachFundsRadio.tsx:130 — 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.
  • <RadioGroup> field component without a label templates/chain-template/components/contract/InstantiatePermissionRadio.tsx:83 — 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.
AC6 · Visual & motion safety · Focus outline removed in CSS without a · ×2
  • Focus outline removed in CSS without a :focus replacement templates/chain-template/components/common/Radio/Radio.module.css:9 — `.radio` 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 examples/spawn/components/common/Radio/Radio.module.css:9 — `.radio` 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.
AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×2
  • Animation without a prefers-reduced-motion guard templates/chain-template/components/common/Wallet/RingLoader/ring.module.css:3 — `.ringLoader` moves (`animation: rotate-ring 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
  • Animation without a prefers-reduced-motion guard examples/spawn/components/common/Wallet/RingLoader/ring.module.css:3 — `.ringLoader` moves (`animation: rotate-ring 2s linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×2
  • REDACTED
  • REDACTED
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×2
  • Duplicated block (12 lines × 2 locations) packages/create-cosmos-app/src/git-question-template.ts:26 — packages/create-cosmos-app/src/git-question-template.ts:26 · packages/create-cosmos-app/src/utils.ts:71 — 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 (12 lines × 2 locations) templates/chain-template/hooks/asset-list/useAssets.ts:24 — templates/chain-template/hooks/asset-list/useAssets.ts:24 · templates/chain-template/hooks/asset-list/useTotalAssets.ts:33 — 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.
R8 · Dependency Hygiene · Unused dependency 'strip-ansi' · ×2
  • Unused dependency 'strip-ansi' boilerplates/lerna-workspace/REDACTED:39 — Declared in boilerplates/lerna-workspace/REDACTED 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 'strip-ansi' boilerplates/telescope/REDACTED:40 — Declared in boilerplates/telescope/REDACTED 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.
R8 · Dependency Hygiene · Unused dependency '@emotion/react' · ×2
  • Unused dependency '@emotion/react' templates/connect-chain/REDACTED:25 — Declared in templates/connect-chain/REDACTED 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 '@emotion/react' templates/connect-multi-chain/REDACTED:25 — Declared in templates/connect-multi-chain/REDACTED 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.
R8 · Dependency Hygiene · Unused dependency '@emotion/styled' · ×2
  • Unused dependency '@emotion/styled' templates/connect-chain/REDACTED:26 — Declared in templates/connect-chain/REDACTED 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 '@emotion/styled' templates/connect-multi-chain/REDACTED:26 — Declared in templates/connect-multi-chain/REDACTED 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.
R8 · Dependency Hygiene · Unused dependency 'framer-motion' · ×2
  • Unused dependency 'framer-motion' templates/connect-chain/REDACTED:31 — Declared in templates/connect-chain/REDACTED 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 'framer-motion' templates/connect-multi-chain/REDACTED:32 — Declared in templates/connect-multi-chain/REDACTED 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.
AC2 · Forms & labels · <NumberField> field component without a label · ×1
  • <NumberField> field component without a label templates/chain-template/components/contract/SelectAssetItem.tsx:134 — 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 · <StakingDelegateInput> field component without a label · ×1
  • <StakingDelegateInput> field component without a label templates/chain-template/components/staking/RedelegateModal.tsx:113 — This UI-library field component has no label / aria-label / aria-labelledby / id at this call site, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id, even one the component sets on what it renders, names nothing until a label points at it) — so it likely renders an unlabelled control. 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.
D1 · Cyclomatic Complexity · git-cca-template.createGitApp.<returned closure> (cyclomatic 22) · ×1
  • git-cca-template.createGitApp.<returned closure> (cyclomatic 22) REDACTED:80 — git-cca-template.createGitApp.<returned closure> has cyclomatic complexity 22 (threshold 15). Of this number, 19 points are the body's own statements and 3 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.
D11 · Test Reliability · Test reliability not measured · ×1
  • Test reliability not measured — JavaScript/TypeScript suite install refused the lockfile — Test reliability NOT MEASURED: the JavaScript/TypeScript suite's dependency install refused the committed lockfile, so no test ever ran and flakiness could not be exercised — the dependency install for the repository root refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. It is excluded from the score rather than counted as a defect; a lockfile in sync with REDACTED is what lets the suite be re-run.
D17 · Explicit Debt · TodoComment repeated across 34 files · ×1
  • TodoComment repeated across 34 files examples/authz/pages/_app.tsx:1 — The identical TodoComment appears in 34 files (34 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 34 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO fix type issues". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
D2 · Cognitive Complexity · git-cca-template.createGitApp.<returned closure> (cognitive 39) · ×1
  • git-cca-template.createGitApp.<returned closure> (cognitive 39) REDACTED:80 — git-cca-template.createGitApp.<returned closure> has cognitive complexity 39 (threshold 15). Drivers by points: if/else 20 (36 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 16). Of this number, 33 points are the body's own statements and 6 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.
D2 · Cognitive Complexity · git-question-template.createQuestionTemplate.<returned closure> (cognitive 17) · ×1
  • git-question-template.createQuestionTemplate.<returned closure> (cognitive 17) packages/create-cosmos-app/src/git-question-template.ts:9 — git-question-template.createQuestionTemplate.<returned closure> has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 1, loops 1 (nesting depth added 6). 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 into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D3 · God Classes · FunctionTooLong · ×1
  • FunctionTooLong: Connect.SVGComponent boilerplates/website/components/common/Connect.tsx:2 — FunctionTooLong — SVGComponent runs 644 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 544 over it, 6.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.
D3 · God Classes · FileTooLong · ×1
  • FileTooLong: common/Connect.tsx boilerplates/website/components/common/Connect.tsx — FileTooLong — 646 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 146 over it, 1.29× 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.
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root refused the committed lockfile (➤ YN0000: · Yarn 4.1.0), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan.
IC1 · Incompleteness & stubs · Fake-async · ×1
  • Fake-async — async method never awaits REDACTED:69 — `warnIfOutdated` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
IC1 · Incompleteness & stubs · Markup wires an event to an empty handler · ×1
  • Markup wires an event to an empty handler templates/chain-template/components/contract/SelectAssetItem.tsx:98 — `onClick` 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.
P12 · CI test-gate honesty · Test suite runs only after the merge · ×1
  • Test suite runs only after the merge — `REDACTED` run(s) the test suite, but no workflow that runs tests is triggered by a pull request (or a merge queue) — so the suite reports on code that is already on the default branch. A red build there blocks nothing and the only remedy is a revert. Add the pull-request trigger to the workflow that runs your suite so the gate applies before the merge, not after it.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 176 JavaScript/TypeScript production file(s) this check read across 10 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.
R10 · Code Duplication · Forked directory tree (136 identical files, ~8671 lines × 2 trees) · ×1
  • Forked directory tree (136 identical files, ~8671 lines × 2 trees) templates/chain-template/components/contract/InstantiateContract.tsx:1 — examples/spawn/ and templates/chain-template/ are near-verbatim copies of each other: 136 files are byte-identical under the same relative paths (~8671 lines; the trees hold 170 and 173 files). That is one structural fact, not 136 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
R10 · Code Duplication · Forked directory tree (15 identical files, ~688 lines × 2 trees) · ×1
  • Forked directory tree (15 identical files, ~688 lines × 2 trees) templates/connect-multi-chain/components/common/Footer.tsx:1 — examples/rollkit/ and templates/connect-multi-chain/ are near-verbatim copies of each other: 15 files are byte-identical under the same relative paths (~688 lines; the trees hold 26 and 28 files). That is one structural fact, not 15 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (11 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (11 clone groups) templates/connect-chain/components/common/Footer.tsx:9 — 11 of the duplicated blocks reported below have copies in at least two of the sibling directories connect-chain, connect-multi-chain under templates/. That concentration is one structural fact, not 11 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 11 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 · Duplication concentrated across 4 sibling directories (6 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (6 clone groups) templates/chain-template/components/contract/InstantiateContract.tsx:262 — 6 duplicated blocks under templates/chain-template/ have copies in at least two of the sibling directories components, hooks, pages, utils — 4 of them are reported below, and 2 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 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 6 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 · Wholesale file copy (97 identical lines × 2 files) · ×1
  • Wholesale file copy (97 identical lines × 2 files) templates/connect-chain/components/common/Footer.tsx:9 — templates/connect-chain/components/common/Footer.tsx:9 · templates/connect-multi-chain/components/common/Footer.tsx:9 — these 2 files are line-for-line copies of one another — 97 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (81 identical lines × 2 files) · ×1
  • Wholesale file copy (81 identical lines × 2 files) templates/connect-chain/components/wallet/Astronaut.tsx:1 — templates/connect-chain/components/wallet/Astronaut.tsx:1 · templates/connect-multi-chain/components/wallet/Astronaut.tsx:1 — these 2 files are line-for-line copies of one another — 81 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block with local edits (71 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (71 matched lines × 2 locations) templates/chain-template/components/staking/DelegateModal.tsx:77 — templates/chain-template/components/staking/DelegateModal.tsx:77 · templates/chain-template/components/staking/UndelegateModal.tsx:60 — the two spans are one implementation copied and then locally edited — 316 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 (57 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (57 matched lines × 2 locations) templates/chain-template/components/staking/RedelegateModal.tsx:52 — templates/chain-template/components/staking/RedelegateModal.tsx:52 · templates/chain-template/components/staking/UndelegateModal.tsx:55 — the two spans are one implementation copied and then locally edited — 282 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 (54 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (54 matched lines × 2 locations) templates/chain-template/components/asset-list/DropdownTransferModal.tsx:38 — templates/chain-template/components/asset-list/DropdownTransferModal.tsx:38 · templates/chain-template/components/asset-list/RowTransferModal.tsx:19 — the two spans are one implementation copied and then locally edited — 265 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 (50 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (50 matched lines × 2 locations) templates/connect-chain/components/wallet/Wallet.tsx:34 — templates/connect-chain/components/wallet/Wallet.tsx:34 · templates/connect-multi-chain/components/wallet/Wallet.tsx:43 — the two spans are one implementation copied and then locally edited — 304 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 (49 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (49 matched lines × 2 locations) templates/chain-template/components/contract/ExecuteTab.tsx:18 — templates/chain-template/components/contract/ExecuteTab.tsx:18 · templates/chain-template/components/contract/QueryTab.tsx:13 — the two spans are one implementation copied and then locally edited — 199 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) templates/chain-template/hooks/contract/useExecuteContractTx.tsx:23 — templates/chain-template/hooks/contract/useExecuteContractTx.tsx:23 · templates/chain-template/hooks/contract/useInstantiateTx.tsx:24 — the two spans are one implementation copied and then locally edited — 190 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 (43 lines × 2 locations) · ×1
  • Duplicated block (43 lines × 2 locations) templates/chain-template/components/staking/AllValidatorsList.tsx:33 — templates/chain-template/components/staking/AllValidatorsList.tsx:33 · templates/chain-template/components/staking/SelectValidatorModal.tsx:38 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (42 lines × 2 locations) · ×1
  • Duplicated block (42 lines × 2 locations) templates/connect-chain/components/common/Header.tsx:11 — templates/connect-chain/components/common/Header.tsx:11 · templates/connect-multi-chain/components/common/Header.tsx:14 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (40 lines × 2 locations) · ×1
  • Duplicated block (40 lines × 2 locations) templates/connect-chain/config/projects.ts:1 — templates/connect-chain/config/projects.ts:1 · templates/connect-multi-chain/config/projects.ts:1 — the 2 copies are spread across 2 files, and what repeats is a LIST OF ENTRIES rather than behaviour — the same entries written out more than once. Extract them into one shared, exported constant and spread that constant into each site, rather than into a function the sites call: a list like this often lives in declarative metadata (a decorator's options object, a static configuration table) that a build step must be able to read statically, where a function call is not allowed. Adding an entry to one copy and not the other is the failure this prevents.
R10 · Code Duplication · Duplicated block (35 lines × 3 locations) · ×1
  • Duplicated block (35 lines × 3 locations) templates/chain-template/components/asset-list/DropdownTransferModal.tsx:129 — templates/chain-template/components/asset-list/DropdownTransferModal.tsx:129 · templates/chain-template/components/asset-list/RowTransferModal.tsx:108 · templates/chain-template/components/asset-list/RowTransferModal.tsx:173 — the 3 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (31 lines × 3 locations) · ×1
  • Duplicated block (31 lines × 3 locations) templates/chain-template/components/staking/AllValidatorsList.tsx:33 — templates/chain-template/components/staking/AllValidatorsList.tsx:33 · templates/chain-template/components/staking/MyValidatorsList.tsx:32 · templates/chain-template/components/staking/SelectValidatorModal.tsx:38 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×1
  • Duplicated block (26 lines × 2 locations) packages/create-cosmos-app/src/git-question-template.ts:49 — packages/create-cosmos-app/src/git-question-template.ts:49 · packages/create-cosmos-app/src/utils.ts:102 — 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.
R10 · Code Duplication · Duplicated block (25 lines × 2 locations) · ×1
  • Duplicated block (25 lines × 2 locations) templates/connect-chain/components/wallet/Connect.tsx:16 — templates/connect-chain/components/wallet/Connect.tsx:16 · templates/connect-multi-chain/components/wallet/Connect.tsx:16 — 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.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×1
  • Duplicated block (24 lines × 2 locations) templates/chain-template/components/contract/InstantiateContract.tsx:262 — templates/chain-template/components/contract/InstantiateContract.tsx:262 · templates/chain-template/pages/faucet.tsx:114 — 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.
R10 · Code Duplication · Duplicated block with local edits (23 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (23 matched lines × 2 locations) templates/chain-template/components/contract/CodeIdField.tsx:32 — templates/chain-template/components/contract/CodeIdField.tsx:32 · templates/chain-template/components/contract/ContractAddressField.tsx:96 — the two spans are one implementation copied and then locally edited — 121 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 (23 lines × 2 locations) · ×1
  • Duplicated block (23 lines × 2 locations) templates/connect-chain/components/wallet/Warning.tsx:17 — templates/connect-chain/components/wallet/Warning.tsx:17 · templates/connect-multi-chain/components/wallet/Warning.tsx:17 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (17 lines × 3 locations) · ×1
  • Duplicated block (17 lines × 3 locations) templates/chain-template/hooks/contract/useExecuteContractTx.tsx:67 — templates/chain-template/hooks/contract/useExecuteContractTx.tsx:67 · templates/chain-template/hooks/contract/useInstantiateTx.tsx:65 · templates/chain-template/hooks/contract/useStoreCodeTx.tsx:64 — the 3 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. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (16 lines × 2 locations) · ×1
  • Duplicated block (16 lines × 2 locations) templates/connect-chain/pages/_app.tsx:15 — templates/connect-chain/pages/_app.tsx:15 · templates/connect-multi-chain/pages/_app.tsx:15 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (15 lines × 2 locations) · ×1
  • Duplicated block (15 lines × 2 locations) templates/chain-template/hooks/asset-list/useOsmoQueryHooks.ts:5 — templates/chain-template/hooks/asset-list/useOsmoQueryHooks.ts:5 · templates/chain-template/hooks/voting/useQueryHooks.ts:9 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) templates/chain-template/hooks/asset-list/useChainAssetsPrices.ts:23 — templates/chain-template/hooks/asset-list/useChainAssetsPrices.ts:23 · templates/chain-template/hooks/staking/useAssetsPrices.ts:29 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×1
  • Duplicated block (10 lines × 2 locations) templates/chain-template/components/contract/ContractAddressField.tsx:18 — templates/chain-template/components/contract/ContractAddressField.tsx:18 · templates/chain-template/components/contract/JsonInput.tsx:15 — 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.
R10 · Code Duplication · Duplicated block (10 lines × 3 locations) · ×1
  • Duplicated block (10 lines × 3 locations) templates/chain-template/components/staking/DelegateModal.tsx:166 — templates/chain-template/components/staking/DelegateModal.tsx:166 · templates/chain-template/components/staking/UndelegateModal.tsx:93 · templates/chain-template/components/staking/ValidatorInfoModal.tsx:40 — the 3 copies are spread across 3 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.
R10 · Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (10 matched lines × 2 locations) templates/chain-template/hooks/voting/useVotingData.ts:45 — templates/chain-template/hooks/voting/useVotingData.ts:45 · templates/chain-template/hooks/voting/useVotingData.ts:76 — the two spans are one implementation copied and then locally edited — 52 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R2 · Cyclomatic Complexity · Complex function Proposal (cyclomatic 25, cognitive 22) · ×1
  • Complex function Proposal (cyclomatic 25, cognitive 22) templates/chain-template/components/voting/Proposal.tsx:53 — Proposal has cyclomatic complexity 25 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 19, cognitive 38) · ×1
  • Complex function (anonymous) (cyclomatic 19, cognitive 38) REDACTED:80 — (anonymous) has cyclomatic complexity 19 and cognitive complexity 38; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function InstantiateContract (cyclomatic 19, cognitive 14) · ×1
  • Complex function InstantiateContract (cyclomatic 19, cognitive 14) templates/chain-template/components/contract/InstantiateContract.tsx:45 — InstantiateContract has cyclomatic complexity 19 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function Button (cyclomatic 12, cognitive 11) · ×1
  • Complex function Button (cyclomatic 12, cognitive 11) templates/chain-template/components/common/Button.tsx:83 — Button has cyclomatic complexity 12 and cognitive complexity 11; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function getTemplateFolder (cyclomatic 11, cognitive 10) · ×1
  • Complex function getTemplateFolder (cyclomatic 11, cognitive 10) packages/create-cosmos-app/src/utils.ts:15 — getTemplateFolder has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function Drawer (cyclomatic 11, cognitive 10) · ×1
  • Complex function Drawer (cyclomatic 11, cognitive 10) templates/chain-template/components/common/Drawer.tsx:12 — Drawer has cyclomatic complexity 11 and cognitive complexity 10; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R4 · Test Coverage · No test rig can mount a component in this workspace · ×1
  • No test rig can mount a component in this workspace boilerplates/lerna-module/jest.config.js:1 — boilerplates/lerna-module/jest.config.js declares environment "node", and no package here declares a DOM implementation (jsdom / happy-dom), a component testing library or a browser runner — so none of the 96 unreached component module(s) can be tested as written, however the suite is authored: templates/chain-template/components/voting/Proposal.tsx, templates/chain-template/components/contract/InstantiateContract.tsx, templates/chain-template/components/asset-list/DropdownTransferModal.tsx, templates/chain-template/components/asset-list/RowTransferModal.tsx, templates/chain-template/components/staking/DelegateModal.tsx, templates/chain-template/components/voting/Voting.tsx and 90 more. Add a DOM environment and a component testing library (for example jsdom + @testing-library, or the runner's browser mode), then test the components. Reported once because these files share one cause, not one omission each.
R6 · Tooling · Type errors in this package cannot fail any build or CI step · ×1
  • Type errors in this package cannot fail any build or CI step examples/provide-liquidity/next.config.js:4 — `examples/provide-liquidity` is TypeScript, but a type error in it cannot fail anything this repository runs: its Next.js config sets `typescript.ignoreBuildErrors: true`, so `next build` — the one step that would run the type checker — passes over type errors, and no script, config or CI step of the package runs `tsc` instead. Add a type check that can fail — a `typecheck` script running `tsc --noEmit` (or `vue-tsc`/`svelte-check`) that CI or the workspace pipeline runs, or a build step that checks before it bundles.
R7 · Dead Code · Dead file (~140 LoC) · ×1
  • Dead file (~140 LoC) packages/create-cosmos-app/src/git-question-template.ts — no import path from any entry point (25 application, 14 tooling, 5 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~11 LoC) · ×1
  • Dead file (~11 LoC) templates/connect-multi-chain/utils/index.ts — no import path from any entry point (25 application, 14 tooling, 5 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unused dependency 'copyfiles' · ×1
  • Unused dependency 'copyfiles' boilerplates/lerna-workspace/REDACTED:30 — Declared in boilerplates/lerna-workspace/REDACTED 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.
R8 · Dependency Hygiene · Unused dependency 'case' · ×1
  • Unused dependency 'case' packages/create-cosmos-app/REDACTED:51 — Declared in packages/create-cosmos-app/REDACTED 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.
R8 · Dependency Hygiene · Unused dependency 'starshipjs' · ×1
  • Unused dependency 'starshipjs' templates/chain-template/REDACTED:59 — Declared in templates/chain-template/REDACTED 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) templates/chain-template/components/voting/Voting.tsx:86 — 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.
Minor — 195 finding(s)
D12 · Dependency Hygiene · Deprecated · ×107
  • Deprecated: @babel/plugin-proposal-dynamic-import REDACTED:768 — @babel/plugin-proposal-dynamic-import 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:804 — @babel/plugin-proposal-export-namespace-from 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-json-strings REDACTED:816 — @babel/plugin-proposal-json-strings 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:864 — @babel/plugin-proposal-object-rest-spread 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:879 — @babel/plugin-proposal-object-rest-spread 7.19.4 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-optional-catch-binding REDACTED:909 — @babel/plugin-proposal-optional-catch-binding 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @babel/plugin-proposal-private-methods REDACTED:934 — @babel/plugin-proposal-private-methods 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @confio/ics23 REDACTED:4039 — @confio/ics23 0.6.8 is resolved in REDACTED and is marked deprecated by its publisher: "Unmaintained. The codebase for this package was moved to https://github.com/cosmos/ics23 but then the JS implementation was removed in https://github.com/cosmos/ics23/pull/353. Please consult the maintainers of https://github.com/cosmos for further assistance.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @cosmjs/crypto REDACTED:4255 — @cosmjs/crypto 0.31.3 is resolved in REDACTED and is marked deprecated by its publisher: "This uses elliptic for cryptographic operations, which contains several security-relevant bugs. To what degree this affects your application is something you need to carefully investigate. See https://github.com/cosmos/cosmjs/issues/1708 for further pointers. Starting with version 0.34.0 the cryptographic library has been replaced. However, private keys might still be at risk.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @graphql-tools/prisma-loader REDACTED:7913 — @graphql-tools/prisma-loader 8.0.17 is resolved in REDACTED and is marked deprecated by its publisher: "This package was intended to be used with an older versions of Prisma.\nThe newer versions of Prisma has a different approach to GraphQL integration.\nTherefore, this package is no longer needed and has been deprecated and removed.\nLearn more: https://www.prisma.io/graphql". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @humanwhocodes/config-array REDACTED:8048 — @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @ledgerhq/errors REDACTED:8882 — @ledgerhq/errors 6.19.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer maintained and will not receive updates. Published versions remain available.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @ledgerhq/hw-transport-webhid REDACTED:8912 — @ledgerhq/hw-transport-webhid 6.30.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer maintained. Use @ledgerhq/device-transport-kit-web-hid instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/add REDACTED:8955 — @lerna/add 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/bootstrap REDACTED:8973 — @lerna/bootstrap 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/changed REDACTED:9003 — @lerna/changed 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/check-working-tree REDACTED:9015 — @lerna/check-working-tree 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/clean REDACTED:9037 — @lerna/clean 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/cli REDACTED:9053 — @lerna/cli 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/collect-uncommitted REDACTED:9065 — @lerna/collect-uncommitted 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/collect-updates REDACTED:9076 — @lerna/collect-updates 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/command REDACTED:9089 — @lerna/command 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/conventional-commits REDACTED:9107 — @lerna/conventional-commits 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/create-symlink REDACTED:9126 — @lerna/create-symlink 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: @lerna/create REDACTED:9137 — @lerna/create 4.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "This package is an implementation detail of Lerna and is no longer published separately.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • + 82 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Low CVE · ×23
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
AX6 · Interface segregation · Fat interface · ×8
  • Fat interface: IBinaryReader (18 required operations) examples/authz/src/codegen/binary.ts:72 — `IBinaryReader` declares 18 required operations: `tag`, `skip`, `skipType`, `uint32`, `int32`, `sint32`, `fixed32`, `sfixed32`, `int64`, `uint64`, `sint64`, `fixed64`, `sfixed64`, `float`, `double`, `bool`, `bytes`, `string`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IBinaryWriter (20 required operations) examples/authz/src/codegen/binary.ts:245 — `IBinaryWriter` declares 20 required operations: `finish`, `fork`, `reset`, `ldelim`, `tag`, `uint32`, `int32`, `sint32`, `int64`, `uint64`, `sint64`, `fixed64`, `sfixed64`, `bool`, `fixed32`, `sfixed32`, `float`, `double`, `bytes`, `string`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Query (17 required operations) examples/authz/src/codegen/osmosis/lockup/query.rpc.Query.ts:12 — `Query` declares 17 required operations: `moduleBalance`, `moduleLockedAmount`, `accountUnlockableCoins`, `accountUnlockingCoins`, `accountLockedCoins`, `accountLockedPastTime`, `accountLockedPastTimeNotUnlockingOnly`, `accountUnlockedBeforeTime`, `accountLockedPastTimeDenom`, `lockedDenom`, `lockedByID`, `syntheticLockupsByLockupID`, `accountLockedLongerDuration`, `accountLockedDuration`, `accountLockedLongerDurationNotUnlockingOnly`, `accountLockedLongerDurationDenom`, `params`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MarketplaceReadOnlyInterface (23 required operations) examples/telescope-with-contracts/src/codegen/Marketplace.client.ts:10 — `MarketplaceReadOnlyInterface` declares 23 required operations: `collections`, `ask`, `asks`, `reverseAsks`, `asksSortedByPrice`, `reverseAsksSortedByPrice`, `askCount`, `asksBySeller`, `bid`, `bidsByBidder`, `bidsByBidderSortedByExpiration`, `bids`, `bidsSortedByPrice`, `reverseBidsSortedByPrice`, `collectionBid`, `collectionBidsByBidder`, `collectionBidsByBidderSortedByExpiration`, `collectionBidsSortedByPrice`, `reverseCollectionBidsSortedByPrice`, `askHooks`, `bidHooks`, `saleHooks`, `params`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Query (17 required operations) examples/telescope-with-contracts/src/codegen/osmosis/lockup/query.rpc.Query.ts:6 — `Query` declares 17 required operations: `moduleBalance`, `moduleLockedAmount`, `accountUnlockableCoins`, `accountUnlockingCoins`, `accountLockedCoins`, `accountLockedPastTime`, `accountLockedPastTimeNotUnlockingOnly`, `accountUnlockedBeforeTime`, `accountLockedPastTimeDenom`, `lockedDenom`, `lockedByID`, `syntheticLockupsByLockupID`, `accountLockedLongerDuration`, `accountLockedDuration`, `accountLockedLongerDurationNotUnlockingOnly`, `accountLockedLongerDurationDenom`, `params`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IBinaryReader (18 required operations) examples/telescope/src/codegen/binary.ts:71 — `IBinaryReader` declares 18 required operations: `tag`, `skip`, `skipType`, `uint32`, `int32`, `sint32`, `fixed32`, `sfixed32`, `int64`, `uint64`, `sint64`, `fixed64`, `sfixed64`, `float`, `double`, `bool`, `bytes`, `string`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: IBinaryWriter (20 required operations) examples/telescope/src/codegen/binary.ts:244 — `IBinaryWriter` declares 20 required operations: `finish`, `fork`, `reset`, `ldelim`, `tag`, `uint32`, `int32`, `sint32`, `int64`, `uint64`, `sint64`, `fixed64`, `sfixed64`, `bool`, `fixed32`, `sfixed32`, `float`, `double`, `bytes`, `string`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Query (17 required operations) examples/telescope/src/codegen/osmosis/lockup/query.rpc.Query.ts:9 — `Query` declares 17 required operations: `moduleBalance`, `moduleLockedAmount`, `accountUnlockableCoins`, `accountUnlockingCoins`, `accountLockedCoins`, `accountLockedPastTime`, `accountLockedPastTimeNotUnlockingOnly`, `accountUnlockedBeforeTime`, `accountLockedPastTimeDenom`, `lockedDenom`, `lockedByID`, `syntheticLockupsByLockupID`, `accountLockedLongerDuration`, `accountLockedDuration`, `accountLockedLongerDurationNotUnlockingOnly`, `accountLockedLongerDurationDenom`, `params`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
X10 · Duplicated predicate · Duplicated predicate · ×7
  • Duplicated predicate templates/chain-template/hooks/asset-list/useAssets.ts:83 — `!denom.startsWith('gamm') && prices[denom]` appears character-identically in 2 files — templates/chain-template/hooks/asset-list/useAssets.ts, templates/chain-template/hooks/asset-list/useTotalAssets.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 templates/chain-template/hooks/voting/useVotingData.ts:25 — `!proposal.content?.title && proposal.content?.value` appears character-identically in 2 files — templates/chain-template/hooks/voting/useVotingData.ts, templates/chain-template/utils/voting.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 templates/connect-chain/utils/index.ts:5 — `from.logo_URIs?.svg || from.logo_URIs?.png` appears character-identically in 2 files — templates/connect-chain/utils/index.ts, templates/connect-multi-chain/utils/index.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 templates/chain-template/hooks/asset-list/useAssets.ts:56 — `isFetching || isInitialFetching || isRefetching` appears character-identically in 2 files — templates/chain-template/hooks/asset-list/useAssets.ts, templates/chain-template/hooks/asset-list/useTotalAssets.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 templates/chain-template/components/asset-list/DropdownTransferModal.tsx:238 — `isLoading || !inputValue || new BigNumber(inputValue).isEqualTo(0) || isNaN(Number(inputValue))` appears character-identically in 2 files — templates/chain-template/components/asset-list/DropdownTransferModal.tsx, templates/chain-template/components/asset-list/RowTransferModal.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 templates/connect-chain/components/wallet/Wallet.tsx:86 — `message && [WalletStatus.Error, WalletStatus.Rejected].includes(status)` appears character-identically in 2 files — templates/connect-chain/components/wallet/Wallet.tsx, templates/connect-multi-chain/components/wallet/Wallet.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 templates/chain-template/hooks/asset-list/useOsmoQueryHooks.ts:34 — `rpcEndpointQuery.isFetching || rpcClientQuery.isFetching` appears character-identically in 2 files — templates/chain-template/hooks/asset-list/useOsmoQueryHooks.ts, templates/chain-template/hooks/voting/useQueryHooks.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.
D12 · Dependency Hygiene · Outdated (npm) · ×6
  • Outdated (npm): framer-motion boilerplates/website/REDACTED:24 — framer-motion is pinned at 9.0.7; registry.npmjs.org publishes 14.14.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): inquirerer packages/create-cosmos-app/REDACTED:66 — inquirerer is pinned at 0.1.3; registry.npmjs.org publishes 4.9.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.
  • Outdated (npm): mobx-react examples/telescope/REDACTED:45 — mobx-react is pinned at 7.6.0; registry.npmjs.org publishes 10.0.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.
  • Outdated (npm): next boilerplates/website/REDACTED:25 — next is pinned at 13.5.7; registry.npmjs.org publishes 16.4.6 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-ace examples/spawn/REDACTED:39 — react-ace is pinned at 11.0.1; registry.npmjs.org publishes 15.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): react-dropzone examples/spawn/REDACTED:41 — react-dropzone is pinned at 14.3.5; registry.npmjs.org publishes 20.2.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.
D21 · Naming Consistency · `cosmosSdkVersion` spells `Sdk` where 5787 names in the project spell it `SDK` · ×4
  • `cosmosSdkVersion` spells `Sdk` where 5787 names in the project spell it `SDK` examples/authz/src/codegen/cosmos/base/tendermint/v1beta1/query.ts:305 — 5787 of 5791 names in project create-cosmos-app-project spell the token `SDK` (5787 of 5791; unit: names in project create-cosmos-app-project containing `SDK`). Peers: examples.authz.src.codegen.confio.proofs.ExistenceProofSDKType (examples/authz/src/codegen/confio/proofs.ts:237); examples.authz.src.codegen.confio.proofs.NonExistenceProofSDKType (examples/authz/src/codegen/confio/proofs.ts:278); examples.authz.src.codegen.confio.proofs.CommitmentProofSDKType (examples/authz/src/codegen/confio/proofs.ts:306); examples.authz.src.codegen.confio.proofs.LeafOpSDKType (examples/authz/src/codegen/confio/proofs.ts:390); examples.authz.src.codegen.confio.proofs.InnerOpSDKType (examples/authz/src/codegen/confio/proofs.ts:466). Rename to `cosmosSDKVersion`. [rule N6]
  • `cosmosSdkVersion` spells `Sdk` where 5787 names in the project spell it `SDK` examples/grpc-web-grpc-gateway/codegen_grpc_gateway/cosmos/base/tendermint/v1beta1/query.ts:303 — 5787 of 5791 names in project create-cosmos-app-project spell the token `SDK` (5787 of 5791; unit: names in project create-cosmos-app-project containing `SDK`). Peers: examples.authz.src.codegen.confio.proofs.ExistenceProofSDKType (examples/authz/src/codegen/confio/proofs.ts:237); examples.authz.src.codegen.confio.proofs.NonExistenceProofSDKType (examples/authz/src/codegen/confio/proofs.ts:278); examples.authz.src.codegen.confio.proofs.CommitmentProofSDKType (examples/authz/src/codegen/confio/proofs.ts:306); examples.authz.src.codegen.confio.proofs.LeafOpSDKType (examples/authz/src/codegen/confio/proofs.ts:390); examples.authz.src.codegen.confio.proofs.InnerOpSDKType (examples/authz/src/codegen/confio/proofs.ts:466). Rename to `cosmosSDKVersion`. [rule N6]
  • `cosmosSdkVersion` spells `Sdk` where 5787 names in the project spell it `SDK` examples/grpc-web-grpc-gateway/codegen_grpc_web/cosmos/base/tendermint/v1beta1/query.ts:303 — 5787 of 5791 names in project create-cosmos-app-project spell the token `SDK` (5787 of 5791; unit: names in project create-cosmos-app-project containing `SDK`). Peers: examples.authz.src.codegen.confio.proofs.ExistenceProofSDKType (examples/authz/src/codegen/confio/proofs.ts:237); examples.authz.src.codegen.confio.proofs.NonExistenceProofSDKType (examples/authz/src/codegen/confio/proofs.ts:278); examples.authz.src.codegen.confio.proofs.CommitmentProofSDKType (examples/authz/src/codegen/confio/proofs.ts:306); examples.authz.src.codegen.confio.proofs.LeafOpSDKType (examples/authz/src/codegen/confio/proofs.ts:390); examples.authz.src.codegen.confio.proofs.InnerOpSDKType (examples/authz/src/codegen/confio/proofs.ts:466). Rename to `cosmosSDKVersion`. [rule N6]
  • `cosmosSdkVersion` spells `Sdk` where 5787 names in the project spell it `SDK` examples/telescope/src/codegen/cosmos/base/tendermint/v1beta1/query.ts:301 — 5787 of 5791 names in project create-cosmos-app-project spell the token `SDK` (5787 of 5791; unit: names in project create-cosmos-app-project containing `SDK`). Peers: examples.authz.src.codegen.confio.proofs.ExistenceProofSDKType (examples/authz/src/codegen/confio/proofs.ts:237); examples.authz.src.codegen.confio.proofs.NonExistenceProofSDKType (examples/authz/src/codegen/confio/proofs.ts:278); examples.authz.src.codegen.confio.proofs.CommitmentProofSDKType (examples/authz/src/codegen/confio/proofs.ts:306); examples.authz.src.codegen.confio.proofs.LeafOpSDKType (examples/authz/src/codegen/confio/proofs.ts:390); examples.authz.src.codegen.confio.proofs.InnerOpSDKType (examples/authz/src/codegen/confio/proofs.ts:466). Rename to `cosmosSDKVersion`. [rule N6]
D19 · Documentation Quality · Documentation · ×3
  • Documentation: no build, run or usage example boilerplates/npm-boilerplate/README.md:1 — `npm-boilerplate` is a published package (`REDACTED` without `"private": true`) and neither `boilerplates/npm-boilerplate/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example boilerplates/ts-codegen-npm-module/contracts/stargaze-minter/README.md:1 — `stargaze-minter` is a published package (`REDACTED` without `"private": true`) and neither `boilerplates/ts-codegen-npm-module/contracts/stargaze-minter/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example boilerplates/ts-codegen-npm-module/contracts/stargaze-sg721/README.md:1 — `stargaze-sg721` is a published package (`REDACTED` without `"private": true`) and neither `boilerplates/ts-codegen-npm-module/contracts/stargaze-sg721/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D34 · Knowledge Freshness · Orphaned file · ×3
  • Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/create-cosmos-app/src/git-question-template.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 packages/create-cosmos-app/src/utils.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.
X7 · Silent fallback defaults · Silent fallback default in catch · ×3
  • Silent fallback default in catch examples/ibc-asset-list/hooks/useChainUtils.ts:104 — `useChainUtils.getPrettyChainName` swallows every exception into `return 'CHAIN_INFO_NOT_FOUND'` — 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 examples/spawn/hooks/asset-list/useChainUtils.ts:116 — `useChainUtils.getPrettyChainName` swallows every exception into `return 'CHAIN_INFO_NOT_FOUND'` — 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 templates/chain-template/hooks/asset-list/useChainUtils.ts:105 — `useChainUtils.getPrettyChainName` swallows every exception into `return 'CHAIN_INFO_NOT_FOUND'` — 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.
R7 · Dead Code · Unused export 'WarningIcon' · ×2
  • Unused export 'WarningIcon' templates/connect-chain/components/wallet/Warning.tsx:15 — Nothing imports this binding — it is safe to review for removal.
  • Unused export 'WarningIcon' templates/connect-multi-chain/components/wallet/Warning.tsx:15 — Nothing imports this binding — it is safe to review for removal.
X7 · Silent fallback defaults · Pending state with no failure state · ×2
  • Pending state with no failure state templates/chain-template/components/staking/StakingSection.tsx:32 — The view draws `<Box height="$28" display="flex" justifyContent="center" alignItems="center">` under `isLoading || isFetchingLogos || ! data`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
  • Pending state with no failure state templates/chain-template/components/contract/MyContractsTable.tsx:93 — The view draws `<Spinner size="$6xl" color="$blackAlpha600"/>` under `isLoading`, but `isLoading` is settled by a load that can fail and the component draws no failure state, so a failed load is shown as "not yet" for ever, or as the loaded state over its initial value. Give the component a failure state and draw it.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found packages/create-cosmos-app/REDACTED:10 — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `packages/create-cosmos-app/REDACTED` makes this repository a deployable product (line 10).
D21 · Naming Consistency · `renderURLSearchParams` spells `URL` where 5226 names in the project spell it `Url` · ×1
  • `renderURLSearchParams` spells `URL` where 5226 names in the project spell it `Url` examples/grpc-web-grpc-gateway/codegen_grpc_gateway/grpc-gateway.ts:327 — 5226 of 5228 names in project create-cosmos-app-project spell the token `Url` (5226 of 5228; unit: names in project create-cosmos-app-project containing `Url`). Peers: Msg.typeUrl (examples/authz/hooks/useTx.ts:9); ExistenceProofProtoMsg.typeUrl (examples/authz/src/codegen/confio/proofs.ts:182); NonExistenceProofProtoMsg.typeUrl (examples/authz/src/codegen/confio/proofs.ts:255); CommitmentProofProtoMsg.typeUrl (examples/authz/src/codegen/confio/proofs.ts:291); LeafOpProtoMsg.typeUrl (examples/authz/src/codegen/confio/proofs.ts:340). Rename to `renderUrlSearchParams`. [rule N6]
D21 · Naming Consistency · `toDataURL` spells `URL` where 5226 names in the project spell it `Url` · ×1
  • `toDataURL` spells `URL` where 5226 names in the project spell it `Url` examples/telescope-with-contracts/utils/index.ts:49 — 5226 of 5228 names in project create-cosmos-app-project spell the token `Url` (5226 of 5228; unit: names in project create-cosmos-app-project containing `Url`). Peers: Msg.typeUrl (examples/authz/hooks/useTx.ts:9); ExistenceProofProtoMsg.typeUrl (examples/authz/src/codegen/confio/proofs.ts:182); NonExistenceProofProtoMsg.typeUrl (examples/authz/src/codegen/confio/proofs.ts:255); CommitmentProofProtoMsg.typeUrl (examples/authz/src/codegen/confio/proofs.ts:291); LeafOpProtoMsg.typeUrl (examples/authz/src/codegen/confio/proofs.ts:340). Rename to `toDataUrl`. [rule N6]
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 3 of 3 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; 3 of the 28 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: REDACTED, packages/create-cosmos-app/src/git-question-template.ts, packages/create-cosmos-app/src/utils.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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST REDACTED:5 — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 2 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · No dependency-update automation · ×1
  • No dependency-update automation REDACTED:21 — `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
R7 · Dead Code · Unused export 'PrettyAssetOption' · ×1
  • Unused export 'PrettyAssetOption' templates/chain-template/components/asset-list/types.tsx:52 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/components/asset-list/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 templates/chain-template/components/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'convertGeckoPricesToDenomPriceHash' · ×1
  • Unused export 'convertGeckoPricesToDenomPriceHash' templates/chain-template/utils/asset-list/base.ts:51 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'getPoolByGammName' · ×1
  • Unused export 'getPoolByGammName' templates/chain-template/utils/asset-list/pool.ts:34 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'convertDollarValueToCoins' · ×1
  • Unused export 'convertDollarValueToCoins' templates/chain-template/utils/asset-list/pool.ts:52 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'convertDollarValueToShares' · ×1
  • Unused export 'convertDollarValueToShares' templates/chain-template/utils/asset-list/pool.ts:77 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'prettyPool' · ×1
  • Unused export 'prettyPool' templates/chain-template/utils/asset-list/pool.ts:95 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'calcCoinsNeededForValue' · ×1
  • Unused export 'calcCoinsNeededForValue' templates/chain-template/utils/asset-list/pool.ts:144 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'calcMaxCoinsForPool' · ×1
  • Unused export 'calcMaxCoinsForPool' templates/chain-template/utils/asset-list/pool.ts:199 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'calcShareOutAmount' · ×1
  • Unused export 'calcShareOutAmount' templates/chain-template/utils/asset-list/pool.ts:227 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'makePoolPairs' · ×1
  • Unused export 'makePoolPairs' templates/chain-template/utils/asset-list/pool.ts:248 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'CalcPoolAprsParams' · ×1
  • Unused export 'CalcPoolAprsParams' templates/chain-template/utils/asset-list/types.ts:58 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'Trade' · ×1
  • Unused export 'Trade' templates/chain-template/utils/asset-list/types.ts:71 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/asset-list/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 templates/chain-template/utils/asset-list/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'getChainLogo' · ×1
  • Unused export 'getChainLogo' templates/chain-template/utils/voting.ts:9 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/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 templates/chain-template/utils/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'processProposals' · ×1
  • Unused export 'processProposals' templates/chain-template/utils/voting.ts:60 — Nothing ultimately consumes this binding: its only referrer is the re-export in templates/chain-template/utils/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 templates/chain-template/utils/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code · Unused export 'DefaultChainLogo' · ×1
  • Unused export 'DefaultChainLogo' templates/connect-chain/components/wallet/Chain.tsx:9 — Nothing imports this binding — it is safe to review for removal.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 0/7 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1
  • Strict null checking is not enabled everywhere the repository type-checks — 16/24 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X5 · Nullable reference types · Null assertions (`!`) override strict null checking · ×1
  • Null assertions (`!`) override strict null checking — ~1.8 `!` null assertions per 1k TypeScript source lines — 28 assertion(s) across the 15482 source line(s) of the 213 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: templates/chain-template/components/voting/Voting.tsx (6), templates/chain-template/components/contract/AttachFundsRadio.tsx (2), templates/chain-template/components/contract/JsonEditor.tsx (2). 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.
Minor — 59 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×58
  • Outdated (npm): @apollo/client — @apollo/client is pinned at 3.7.14; registry.npmjs.org publishes 4.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): @babel/cli — @babel/cli is pinned at 7.24.7; registry.npmjs.org publishes 8.1.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): @babel/core — @babel/core is pinned at 7.24.7; registry.npmjs.org publishes 8.1.2 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): @babel/eslint-parser — @babel/eslint-parser is pinned at 7.25.9; registry.npmjs.org publishes 8.1.2 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): @babel/node — @babel/node is pinned at 7.26.0; registry.npmjs.org publishes 8.1.2 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): @babel/plugin-proposal-export-default-from — @babel/plugin-proposal-export-default-from is pinned at 7.24.7; registry.npmjs.org publishes 8.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): @babel/plugin-transform-runtime — @babel/plugin-transform-runtime is pinned at 7.24.7; registry.npmjs.org publishes 8.1.2 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): @babel/preset-env — @babel/preset-env is pinned at 7.24.7; registry.npmjs.org publishes 8.0.7 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): @babel/preset-typescript — @babel/preset-typescript is pinned at 7.26.0; registry.npmjs.org publishes 8.0.7 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): @chain-registry/assets — @chain-registry/assets is pinned at 1.70.40; registry.npmjs.org publishes 1.70.240 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): @chain-registry/client — @chain-registry/client is pinned at 1.53.18; registry.npmjs.org publishes 2.0.287 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): @chain-registry/types — @chain-registry/types is pinned at 0.50.18; registry.npmjs.org publishes 2.0.287 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): @chain-registry/utils — @chain-registry/utils is pinned at 1.51.18; registry.npmjs.org publishes 2.0.287 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): @chakra-ui/icons — @chakra-ui/icons is pinned at 2.0.12; registry.npmjs.org publishes 2.2.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.
  • Outdated (npm): @chakra-ui/react — @chakra-ui/react is pinned at 2.5.1; registry.npmjs.org publishes 3.38.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): @cosmjs/amino — @cosmjs/amino is pinned at 0.32.4; registry.npmjs.org publishes 0.39.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): @cosmjs/cosmwasm-stargate — @cosmjs/cosmwasm-stargate is pinned at 0.32.4; registry.npmjs.org publishes 0.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): @cosmjs/encoding — @cosmjs/encoding is pinned at 0.32.4; registry.npmjs.org publishes 0.39.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): @cosmjs/proto-signing — @cosmjs/proto-signing is pinned at 0.32.4; registry.npmjs.org publishes 0.39.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): @cosmjs/stargate — @cosmjs/stargate is pinned at 0.32.4; registry.npmjs.org publishes 0.39.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): @cosmjs/tendermint-rpc — @cosmjs/tendermint-rpc is pinned at 0.32.4; registry.npmjs.org publishes 0.39.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): @cosmology-ui/react — @cosmology-ui/react is pinned at 0.1.8-beta.33; registry.npmjs.org publishes 1.1.0-beta.10 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): @cosmology/ast — @cosmology/ast is pinned at 0.89.0; registry.npmjs.org publishes 2.4.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): @cosmology/lcd — @cosmology/lcd is pinned at 0.12.0; registry.npmjs.org publishes 0.17.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): @cosmology/telescope — @cosmology/telescope is pinned at 0.104.0; registry.npmjs.org publishes 2.1.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.
  • + 33 more in this group — see findings.md.
D24 · Comment Value · doc comments repeat the names · ×1
  • doc comments repeat the names packages/create-cosmos-app/src/utils.ts:138 — 0 of 3 documented parameters and 0 of 2 summaries in `create-cosmos-app` only repeat the member or parameter name (e.g. "" for `input`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=49" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-1.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=249 --max-count=61" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-2.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=310 --max-count=75" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-3.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=385 --max-count=94" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-4.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-4.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=479 --max-count=113" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-5.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-5.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=592 --max-count=138" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-6.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-6.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=730 --max-count=128" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-7.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-7.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=858 --max-count=135" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-8.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-8.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=993 --max-count=149" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-9.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-9.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1142 --max-count=136" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-10.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-10.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1278 --max-count=150" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-11.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-11.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1428 --max-count=161" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-12.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-12.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1589 --max-count=176" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-13.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-13.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1765 --max-count=186" --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/history-14.json --exit-code 0 --source .0artifacts/raw/gitleaks-history-14.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-92f45dc39e9d4550ab4878399a5048c5/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude examples/authz/src/codegen --exclude examples/authz/types/codegen --exclude examples/grpc-web-grpc-gateway/codegen_grpc_gateway --exclude examples/grpc-web-grpc-gateway/codegen_grpc_web --exclude examples/telescope/src --exclude examples/telescope-with-contracts/src .15artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .853artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1eb98-d926-7fe9-bab5-de638c86bf57 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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