Public report of navikt/aksel, published 16 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 16 November 2026, 18:44 UTC · Survey ID cd_a0d176e25cf34e4695dd913f0c8aada8
navikt/aksel
Measured 16 November 2026, 18:44 UTC, at code version 6ed064a
First survey, so nothing to compare with yet
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 135,915 lines of product code in 17 projects, tests not counted · Estimated rebuild effort: about 1.0 person-years · Weakest lens: Security and Compliance, 49.0
Findings by how serious they are
111 critical552 serious197 minor
7 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 18:44 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
75of 75 dimensions measured by tools.
818of 860 findings point to an exact file and line, so you can open each one in the code. The other 42 concern the repository as a whole, such as missing documentation.
75dimensions across 7 lenses, read from 135,915 lines of product code in 17 projects.
navikt/aksel falls short of our standard for production because it has pipeline tools referenced by a changeable name. It scores 52.3 out of 100 and is rated Adequate, and 98 of its 111 critical findings are security problems.
Security and Compliance, at 49.0, is the weakest lens by a small margin, and the weakest lens counts most in the score. The best first step is replacing the six passwords or keys found in the code's history, worth about 2.1 points. Updating the eight dependencies with a known vulnerability comes next, worth about 1.6 points.
Sixty-five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Fourteen secrets can leak from the build pipeline, and seven known security holes in the packages the code depends on can be used by attackers. Pinning each tool to an exact version, limiting each secret to its own step and updating the vulnerable packages would close these risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command, and the six passwords or keys in the code's history need replacing, with the old ones switched off. The six controls that only work with a mouse need to work with the keyboard, or to become a real button.
The product code is 135,915 lines, about €140,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
The weakest lenses score close to each other, so improving any of them moves the score.
Code composition: what the lines of code are
Product code 92%Tests 8%
Rebuild cost: about €140,000 · Estimate
Cost to rebuild
€47,000 to €240,000, for 787 to 2,498 hours of work, about 1.0 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 52. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 135,915 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED.
Raises the score by about 2.1 points · Low effort · Secrets (history)
2
Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8).
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 €140,000 to build again, about 1.0 person-years of work. Its weakest lens is Security and Compliance, at 49.0 (Weak). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 6 REDACTED finding(s) in Secrets (history). Of all the actions in this report, it raises the score most for the work it takes: about 2.1 points for low effort, because it clears the 6 Secrets (history) findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.8 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 3% to 7% on every change. The history of the code shows how much it changes: about 28,773 lines over the last 90 days, which is about 116,690 lines a year. At that pace, the extra work comes to an estimated 8.4 to 50.6 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
871 modules, with 210 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 831 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.
@navikt.aksel.src.codemod.v8-tokens uses @navikt.aksel.src.codemod.v8-tokens.config.TokenStatus, so a change to @navikt.aksel.src.codemod.v8-tokens.config.TokenStatus can break @navikt.aksel.src.codemod.v8-tokens, while a change to @navikt.aksel.src.codemod.v8-tokens can't break @navikt.aksel.src.codemod.v8-tokens.config.TokenStatus.
Position
Below the diagonal: @navikt.aksel.src.codemod.v8-tokens uses a module listed above it, which is the healthy direction.
@navikt.core.react.scripts.metadata uses @navikt.core.react.scripts.metadata.metadata_types, so a change to @navikt.core.react.scripts.metadata.metadata_types can break @navikt.core.react.scripts.metadata, while a change to @navikt.core.react.scripts.metadata can't break @navikt.core.react.scripts.metadata.metadata_types.
Position
Below the diagonal: @navikt.core.react.scripts.metadata uses a module listed above it, which is the healthy direction.
@navikt.core.react.src.chat.root.ChatRoot uses @navikt.core.tokens.types, so a change to @navikt.core.tokens.types can break @navikt.core.react.src.chat.root.ChatRoot, while a change to @navikt.core.react.src.chat.root.ChatRoot can't break @navikt.core.tokens.types.
Position
Below the diagonal: @navikt.core.react.src.chat.root.ChatRoot uses a module listed above it, which is the healthy direction.
5 pairs of types, where a type in @navikt.core.react.src.data.token-filter.helpers uses a type in @navikt.core.react.src.data.token-filter.TokenFilter_types.
@navikt.core.react.src.data.token-filter.helpers uses @navikt.core.react.src.data.token-filter.TokenFilter_types, so a change to @navikt.core.react.src.data.token-filter.TokenFilter_types can break @navikt.core.react.src.data.token-filter.helpers, while a change to @navikt.core.react.src.data.token-filter.helpers can't break @navikt.core.react.src.data.token-filter.TokenFilter_types.
Position
Below the diagonal: @navikt.core.react.src.data.token-filter.helpers uses a module listed above it, which is the healthy direction.
@navikt.core.react.src.form.file-upload.dropzone uses @navikt.core.react.src.badge.Badge, so a change to @navikt.core.react.src.badge.Badge can break @navikt.core.react.src.form.file-upload.dropzone, while a change to @navikt.core.react.src.form.file-upload.dropzone can't break @navikt.core.react.src.badge.Badge.
Position
Below the diagonal: @navikt.core.react.src.form.file-upload.dropzone uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in @navikt.core.react.src.form.file-upload.item-icon.ItemIcon uses a type in @navikt.core.react.src.form.file-upload.item.FileUploadItem_types.
@navikt.core.react.src.form.file-upload.item-icon.ItemIcon uses @navikt.core.react.src.form.file-upload.item.FileUploadItem_types, so a change to @navikt.core.react.src.form.file-upload.item.FileUploadItem_types can break @navikt.core.react.src.form.file-upload.item-icon.ItemIcon, while a change to @navikt.core.react.src.form.file-upload.item-icon.ItemIcon can't break @navikt.core.react.src.form.file-upload.item.FileUploadItem_types.
Position
Below the diagonal: @navikt.core.react.src.form.file-upload.item-icon.ItemIcon uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in @navikt.core.react.src.form.file-upload.item.FileUploadItem uses a type in @navikt.core.react.src.form.file-upload.item.FileUploadItem_types.
@navikt.core.react.src.form.file-upload.item.FileUploadItem uses @navikt.core.react.src.form.file-upload.item.FileUploadItem_types, so a change to @navikt.core.react.src.form.file-upload.item.FileUploadItem_types can break @navikt.core.react.src.form.file-upload.item.FileUploadItem, while a change to @navikt.core.react.src.form.file-upload.item.FileUploadItem can't break @navikt.core.react.src.form.file-upload.item.FileUploadItem_types.
Position
Below the diagonal: @navikt.core.react.src.form.file-upload.item.FileUploadItem uses a module listed above it, which is the healthy direction.
@navikt.core.react.src.read-more.ReadMore uses @navikt.core.tokens.types, so a change to @navikt.core.tokens.types can break @navikt.core.react.src.read-more.ReadMore, while a change to @navikt.core.react.src.read-more.ReadMore can't break @navikt.core.tokens.types.
Position
Below the diagonal: @navikt.core.react.src.read-more.ReadMore uses a module listed above it, which is the healthy direction.
@navikt.core.react.src.toggle-group.ToggleGroup_types uses @navikt.core.tokens.types, so a change to @navikt.core.tokens.types can break @navikt.core.react.src.toggle-group.ToggleGroup_types, while a change to @navikt.core.react.src.toggle-group.ToggleGroup_types can't break @navikt.core.tokens.types.
Position
Below the diagonal: @navikt.core.react.src.toggle-group.ToggleGroup_types uses a module listed above it, which is the healthy direction.
@navikt.core.react.src.utils.helpers uses @navikt.core.react.src.utils.helpers.className, so a change to @navikt.core.react.src.utils.helpers.className can break @navikt.core.react.src.utils.helpers, while a change to @navikt.core.react.src.utils.helpers can't break @navikt.core.react.src.utils.helpers.className.
Position
Below the diagonal: @navikt.core.react.src.utils.helpers uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in aksel_nav_no.website.app.(routes).(designsystemet).designsystemet uses a type in @navikt.core.react.scripts.metadata.metadata_types.
aksel_nav_no.website.app.(routes).(designsystemet).designsystemet uses @navikt.core.react.scripts.metadata.metadata_types, so a change to @navikt.core.react.scripts.metadata.metadata_types can break aksel_nav_no.website.app.(routes).(designsystemet).designsystemet, while a change to aksel_nav_no.website.app.(routes).(designsystemet).designsystemet can't break @navikt.core.react.scripts.metadata.metadata_types.
Position
Below the diagonal: aksel_nav_no.website.app.(routes).(designsystemet).designsystemet uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in aksel_nav_no.website.app.(routes).(designsystemet).designsystemet uses a type in aksel_nav_no.website.app._sanity.live.
aksel_nav_no.website.app.(routes).(designsystemet).designsystemet uses aksel_nav_no.website.app._sanity.live, so a change to aksel_nav_no.website.app._sanity.live can break aksel_nav_no.website.app.(routes).(designsystemet).designsystemet, while a change to aksel_nav_no.website.app.(routes).(designsystemet).designsystemet can't break aksel_nav_no.website.app._sanity.live.
Position
Below the diagonal: aksel_nav_no.website.app.(routes).(designsystemet).designsystemet uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in aksel_nav_no.website.app.(routes).(designsystemet).designsystemet._ui.stats uses a type in aksel_nav_no.website.app._sanity.live.
aksel_nav_no.website.app.(routes).(designsystemet).designsystemet._ui.stats uses aksel_nav_no.website.app._sanity.live, so a change to aksel_nav_no.website.app._sanity.live can break aksel_nav_no.website.app.(routes).(designsystemet).designsystemet._ui.stats, while a change to aksel_nav_no.website.app.(routes).(designsystemet).designsystemet._ui.stats can't break aksel_nav_no.website.app._sanity.live.
Position
Below the diagonal: aksel_nav_no.website.app.(routes).(designsystemet).designsystemet._ui.stats uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category] uses a type in @navikt.core.react.scripts.metadata.metadata_types.
aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category] uses @navikt.core.react.scripts.metadata.metadata_types, so a change to @navikt.core.react.scripts.metadata.metadata_types can break aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category], while a change to aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category] can't break @navikt.core.react.scripts.metadata.metadata_types.
Position
Below the diagonal: aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category] uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category] uses a type in @navikt.core.react.src.badge.Badge.
aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category] uses @navikt.core.react.src.badge.Badge, so a change to @navikt.core.react.src.badge.Badge can break aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category], while a change to aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category] can't break @navikt.core.react.src.badge.Badge.
Position
Below the diagonal: aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.[category] uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.endringslogg._ui uses a type in @navikt.core.react.src.badge.Badge.
aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.endringslogg._ui uses @navikt.core.react.src.badge.Badge, so a change to @navikt.core.react.src.badge.Badge can break aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.endringslogg._ui, while a change to aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.endringslogg._ui can't break @navikt.core.react.src.badge.Badge.
Position
Below the diagonal: aksel_nav_no.website.app.(routes).(designsystemet).grunnleggende.endringslogg._ui uses a module listed above it, which is the healthy direction.
aksel_nav_no.website.app.(routes).(root)._ui.FrontpageMasonryCard uses @navikt.core.react.src.badge.Badge, so a change to @navikt.core.react.src.badge.Badge can break aksel_nav_no.website.app.(routes).(root)._ui.FrontpageMasonryCard, while a change to aksel_nav_no.website.app.(routes).(root)._ui.FrontpageMasonryCard can't break @navikt.core.react.src.badge.Badge.
Position
Below the diagonal: aksel_nav_no.website.app.(routes).(root)._ui.FrontpageMasonryCard uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in @navikt.core.react.src.utils.components.textarea-autosize uses a type in aksel_nav_no.website.app.(routes).(root)._ui.FrontpageMasonryCard.
@navikt.core.react.src.utils.components.textarea-autosize uses aksel_nav_no.website.app.(routes).(root)._ui.FrontpageMasonryCard, so a change to aksel_nav_no.website.app.(routes).(root)._ui.FrontpageMasonryCard can break @navikt.core.react.src.utils.components.textarea-autosize, while a change to @navikt.core.react.src.utils.components.textarea-autosize can't break aksel_nav_no.website.app.(routes).(root)._ui.FrontpageMasonryCard.
Position
Below the diagonal: @navikt.core.react.src.utils.components.textarea-autosize uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
103
High / Critical
A03:2025 — Software Supply Chain Failures
18
High / Critical
A07:2025 — Authentication Failures
7
High / Critical
A02:2025 — Security Misconfiguration
6
High / Critical
Roadmap
Top priorities: Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key; Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED; Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED.
Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 61 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once.
Per-file score 0–10 — a quality signature. Of 172 files carrying findings, judged against the Production bar: 1% slop · 50% mixed · 49% near-clean.
File
Score
Band
Worst signal
REDACTED
0.0
Slop
Dependency Vulnerabilities: High CVE: REDACTED
REDACTED
4.2
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
IaC & Container Security: High IaC: REDACTED
REDACTED
4.4
Mixed
IaC & Container Security: High IaC: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.4
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.5
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.6
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
4.8
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.1
Mixed
Static Analysis (SAST): High: REDACTED
REDACTED
5.4
Mixed
Static Analysis (SAST): Medium: REDACTED
REDACTED
5.9
Mixed
Static Analysis (SAST): Medium: 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 — 111
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 — 552
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 — 197
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 7
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 75 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 75 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 818 of 860 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 403), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
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 NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the dependency install for the repository root failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 403), so the suite never ran. This is OUR limitation, not a defect in the repo — it is excluded from the score.
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 vitest suite in the repository root was NOT MEASURED: the dependency install for the repository root failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 vitest suite in @navikt/aksel/ was NOT MEASURED: the dependency install for @navikt/aksel/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 vitest suite in @navikt/aksel-icons/ was NOT MEASURED: the dependency install for @navikt/aksel-icons/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 node:test suite in @navikt/aksel-stylelint/ was NOT MEASURED: the dependency install for @navikt/aksel-stylelint/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 vitest suite in @navikt/core/react/ was NOT MEASURED: the dependency install for @navikt/core/react/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 vitest suite in @navikt/core/tailwind/ was NOT MEASURED: the dependency install for @navikt/core/tailwind/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 vitest suite in @navikt/core/tokens/ was NOT MEASURED: the dependency install for @navikt/core/tokens/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 vitest suite in aksel.nav.no/sanity-studio/ was NOT MEASURED: the dependency install for aksel.nav.no/sanity-studio/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 vitest suite in aksel.nav.no/website/ was NOT MEASURED: the dependency install for aksel.nav.no/website/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 vitest suite in apps/mcp-server/ was NOT MEASURED: the dependency install for apps/mcp-server/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
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 vitest suite in tooling/analyzer/ was NOT MEASURED: the dependency install for tooling/analyzer/ failed in the analyzer sandbox (➤ YN0001: │ RequestError: Bad response: 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.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D23 Boundary Type-Coupling — 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 measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `.storybook/main.ts`, `@navikt/aksel/src/codemod/migrations.ts`, `@navikt/aksel/src/codemod/v8-tokens/config/legacy.tokens.ts`, `@navikt/aksel/src/codemod/v8-tokens/run-tooling.ts`, `@navikt/aksel/src/migrations-config.ts`, … (+78 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
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 REDACTED) 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. An image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository. (rule: registry). The renderer reported: docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM gcr.io/distroless/nodejs24-debian13 2 | 3 | ENV NODE_ENV=production -------------------- ERROR: failed to solve: gcr.io/distroless/nodejs24-debian13: failed to resolve source metadata for gcr.io/distroless/nodejs24-debian13:latest: failed to do request: Head "https://gcr.io/v2/distroless/nodejs24-debian13/manifests/latest": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via REDACTED (REDACTED). docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM gcr.io/distroless/nodejs24-debian13 2 | 3 | ENV NODE_ENV=production -------------------- ERROR: failed to solve: gcr.io/distroless/nodejs24-debian13: failed to resolve source metadata for gcr.io/distroless/nodejs24-debian13:latest: failed to do request: Head "https://gcr.io/v2/distroless/nodejs24-debian13/manifests/latest": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P2 Observability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 5 further occurrence(s) are not listed individually; the score already reflects all 45.
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. 66 further occurrence(s) are not listed individually; the score already reflects all 106.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 25 further occurrence(s) are not listed individually; the score already reflects all 65.
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. 219 further occurrence(s) are not listed individually; the score already reflects all 259.
R7 Dead Code — 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. 68 further occurrence(s) are not listed individually; the score already reflects all 108.
Repo exclusion declarations: 22 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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
49 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was FocusBoundary.FocusBoundary at 55. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being Tag.variantToColor at 25 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: @navikt/core/react/src/tag/Tag.tsx (Tag.variantToColor at 25). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 44 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 9 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with FocusBoundary.FocusBoundary (cyclomatic 55), Input.Input (cyclomatic 54), list.transformer (cyclomatic 53). — 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 9 together lifts Cyclomatic Complexity from 6.6 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 63 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 4 bodies over 60 down to 60 or less in Cognitive Complexity — start with list.transformer (cognitive 78), status.getStatus (cognitive 78), Input.Input (cognitive 72). — 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 4 together lifts Cognitive Complexity from 5.9 to about 6.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 38 FunctionTooLong finding(s) in God Classes — start with page.tsx (5), useRangeDatepicker.tsx, intro-med-alternativ-soknad.tsx. — One of this dimension's main actionable groups (38 warning-level).
Resolve the 1 FileTooLong finding(s) in God Classes — start with Menu.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.
Do you agree with this assessment?
D5 · Coupling7.0 / 10Strong✓ 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.
16 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 6 module(s) off the main sequence, with abstractness counted on 14 of the 16 (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).
Off the main sequence: @navikt/aksel · ×6
What to do
Resolve the 6 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with FigmaPluginInterface.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.9 / 10Stronggated by 5 serious findings✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
Resolve the 5 Skipped test finding(s) in Test Quality — start with global-search.e2e.ts (5). — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
29 outdated direct production npm dependency(ies) of 71 graded, 0 pinning defect(s), across 17 REDACTED (15 of them the product) and 1 committed lockfile(s). 71 of 73 resolved direct production dependency(ies) were graded against registry.npmjs.org (2 not published there — private or renamed). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 3 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.
Resolve the 32 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (32). — One of this dimension's main actionable groups (32 recommendation-level).
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).
Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with ListboxRoot.tsx, DismissableLayer.tsx, FilteredOptions.tsx. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with DesignsystemetPageFooter.tsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.6 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
53 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is @navikt/core/react/src/dialog/Dialog.stories.tsx. Counted over 366 of the 1055 production source files in this repository: 688 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×3
Further sole-owners (lower concentration)
What to do
Resolve the 3 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
34 deducted task-comment markers across 135421 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 33 TodoComment finding(s) in Explicit Debt — start with ComboboxList.tsx (4), DataGridTableRoot.tsx (4), TableAnimateHeightInternal.tsx (2). — One of this dimension's main actionable groups (33 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with run-version-migration.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 2 documentation facets pass in full; short on: F2 example. 20 document(s) read across 17 unit(s).
Documentation: no build, run or usage exampleapps/playroom/README.md:1
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
10 domain type(s) cross context boundaries across 16 contexts; they are measured and withheld (not published, not scored). Contexts: aksel, aksel-icons, aksel-stylelint, aksel.nav.no, analyzer, changelog, css, figma-icon-plugin, mcp-server, playroom, react, sanity-studio and 4 more.
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.
doc comments repeat the names · ×4@navikt/aksel-icons/util/useId.ts:29
What to do
Resolve the 6 redundant comment finding(s) in Comment Value — start with Menu.tsx (2), box-new.ts, print-remaining.ts. — One of this dimension's main actionable groups (6 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 17 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×4@navikt/core/react/package.json:1
What to do
Resolve the 4 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with REDACTED (4). — One of this dimension's main actionable groups (4 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
33 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 6 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
103 finding(s): 0 critical, 83 high, 20 medium, 0 low. 61 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 145 file(s) — `.storybook/main.ts` (line 119), `@navikt/aksel-icons/icons/ArrowDown.yml`, `@navikt/aksel-icons/icons/ArrowsPointingOut.yml`, `@navikt/aksel-icons/icons/CaretDown.yml`, `@navikt/aksel-icons/icons/CaretDownFill.yml`, … (+140 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 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
+ 6 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 14 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (14 issue-level).
Resolve the 2 REDACTED finding(s) charged to Static Analysis (SAST) — the other 61 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (63 issue-level, 2 of them charged here).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 8 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 warning-level).
Resolve the 7 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 2 High IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
16 of 367 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is @navikt/core/react/src/process/Process.stories.tsx. Counted over 367 of the 1055 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 15 Change coupling finding(s) in Change Coupling — start with Data.data-prop.stories.tsx (2), TimelineClickablePeriodInternal.tsx, DatePickerRoot.tsx. — One of this dimension's main actionable groups (15 warning-level).
Resolve the 2 Change coupling clique finding(s) in Change Coupling — start with Bleed.tsx, Select.tsx. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 Change-coupling hub finding(s) in Change Coupling — start with Combobox.stories.tsx. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
No dependency in any ecosystem this repository declares is published as malicious.
✓ On the Gold path — maintain.
Detailed fixes: d43_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels4.7 / 10Weak✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). (×2) — @navikt/core/react/src/data/drag-and-drop/drag-handler/DragAndDropDragHandler.tsx:49, @navikt/core/react/src/data/drag-and-drop/drag-handler/DragAndDropDragHandler.tsx:119
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. (×15) — aksel.nav.no/website/app/(routes)/(root)/personvernerklaering/_ui/ConsentForm.tsx:35, aksel.nav.no/website/pages/eksempler/datepicker/anchor.tsx:11, aksel.nav.no/website/pages/eksempler/radio-horizontal/horizontal.tsx:6, …
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A <tr> may hold only <td>/<th> cells. Text or a value written between the cells is moved out of the table by the browser, so it is read detached from its row. Wrap it in a <td>. — @navikt/core/react/src/data/table/tr/DataTableTr.tsx:122
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. — aksel.nav.no/sanity-studio/.sanity/runtime/index.html:9
A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component. — aksel.nav.no/website/app/global-error.tsx:23
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — aksel.nav.no/website/app/global-error.tsx:23
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler. (×6) — @navikt/core/react/src/form/checkbox/Checkbox.tsx:30, @navikt/core/react/src/form/file-upload/dropzone/FileUploadDropzone.tsx:94, @navikt/core/react/src/form/radio/Radio.tsx:26, …
This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close. (×2) — @navikt/core/react/src/timeline/period-clickable/TimelineClickablePeriodInternal.tsx:145, @navikt/core/react/src/timeline/pin/TimelinePinInternal.tsx:111
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`#hovedinnhold:focus` 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. — aksel.nav.no/website/app/globals.css:27
`.headingElement:focus` 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. — aksel.nav.no/website/app/_ui/portable-text/CustomPortableText.module.css:34
`.compareImagesHandle` 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. — aksel.nav.no/website/app/_ui/compare-images/CompareImages.module.css:62
`.main:focus` 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. — aksel.nav.no/website/app/(routes)/(produktbloggen)/produktbloggen/_ui/Produktbloggen.module.css:154
`.akselLayersLink:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — aksel.nav.no/website/app/(routes)/(designsystemet)/designsystemet/_ui/ds-layers-overview/DSLayersOverview.module.css:51
`.overviewCardLink:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/overview/DesignsystemetOverview.module.css:13
`.aksel-data-table__th-sort-button:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — @navikt/core/css/src/data-grid-preview.css:397
`.aksel-data-table__th-resize-handle[data-active="true"]:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — @navikt/core/css/src/data-grid-preview.css:515
`.aksel-date__field-input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — @navikt/core/css/src/date.css:224
`.aksel-dialog__popup:focus` 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. — @navikt/core/css/src/dialog.css:20
`.aksel-link-anchor__overlay .aksel-link-anchor:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — @navikt/core/css/src/link-anchor.css:44
`.aksel-tooltip:focus` 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. — @navikt/core/css/src/tooltip.css:17
`.aksel-combobox__input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — @navikt/core/css/src/form/combobox.css:182
`.aksel-combobox__input:focus` 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. — @navikt/core/css/src/form/combobox.css:202
`.aksel-error-summary__heading:focus` 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. — @navikt/core/css/src/form/error-summary.css:38
`.aksel-checkbox__input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — @navikt/core/css/src/form/radio-checkbox.css:133
`.aksel-search__input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — @navikt/core/css/src/form/search.css:39
`.navds-timeline__popover:focus` 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) — @navikt/aksel/src/codemod/transforms/v4.0.0/internal-css/tests/complete.input.css:522, @navikt/aksel/src/codemod/transforms/v4.0.0/internal-css/tests/complete.output.css:521
`.animatedArrow` moves (`transition: transform 200ms`) 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. — aksel.nav.no/website/app/_ui/animated-arrow/AnimatedArrow.module.css:2
`.animated` moves (`animation: rotation 60s ease-in-out infinite,
rainbow-hype 60s ease 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. — aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:14
`.animated1` moves (`animation: shape-1 60s ease-in-out infinite,
rainbow-hype 60s ease 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. — aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:61
`.animated2` moves (`animation: shape-2 60s ease-in-out infinite,
rainbow-hype 60s ease 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. — aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:69
`.animated3` moves (`animation: shape-3 60s ease-in-out infinite,
rainbow-hype 60s ease 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. — aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:77
`.animated5` moves (`animation: shape-5 60s ease-in-out infinite,
rainbow-hype 60s ease 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. — aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:90
`.animated6` moves (`animation: shape-6 60s ease-in-out infinite,
rainbow-hype 60s ease 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. — aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:98
`.card[data-visible="true"]` moves (`animation: fadeInBottom 1s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — aksel.nav.no/website/app/(routes)/(root)/_ui/frontpage.module.css:207
`.godPraksisHero` moves (`transition: margin 500ms`) 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. — aksel.nav.no/website/app/(routes)/(god-praksis)/_ui/hero/Hero.module.css:8
`.navListNotch::before` moves (`transition: width 120ms ease-out`) 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. — aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/sidebar/Sidebar.module.css:112
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
Do you agree with this assessment?
C2 · Access Controls7.0 / 10Strong✓ Tool-verified
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — aksel.nav.no/website/app/_auth/rcs.ts:17
What to do
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
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.
A placeholder string ("Lorem ipsum dolor sit, amet consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. — aksel.nav.no/website/pages/eksempler/fieldset/hide-legend.tsx:10
A placeholder string ("Lorem ipsum dolor sit amet consectetur a…") is still in shipped code — typical of generated boilerplate that was never filled in. (×3) — aksel.nav.no/website/pages/eksempler/info-card/colors.tsx:33, aksel.nav.no/website/pages/eksempler/info-card/sizes.tsx:11, aksel.nav.no/website/pages/eksempler/info-card/sizes.tsx:20
A placeholder string ("Lorem ipsum dolor sit amet consectetur, …") is still in shipped code — typical of generated boilerplate that was never filled in. — aksel.nav.no/website/pages/eksempler/link/anchor.tsx:8
A placeholder string ("Lorem ipsum, dolor sit amet consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. — aksel.nav.no/website/pages/eksempler/modal/placement-top.tsx:20
A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in. (×2) — aksel.nav.no/website/pages/eksempler/popover/placement.tsx:35, aksel.nav.no/website/pages/eksempler/primitive-bleed/full.tsx:7
A placeholder string ("lorem ipsum dolor sit amet consectetur a…") is still in shipped code — typical of generated boilerplate that was never filled in. — aksel.nav.no/website/pages/eksempler/skeleton/link-card.tsx:24
A placeholder string ("lorem ipsum dolor sit amet consectetur") is still in shipped code — typical of generated boilerplate that was never filled in. — aksel.nav.no/website/pages/eksempler/skeleton/link-card.tsx:27
What to do
Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
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.
`generateFile` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — @navikt/aksel-icons/config/zip.js:16
`CopyrightYear` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — aksel.nav.no/website/app/_ui/footer/Footer.tsx:11
`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. — aksel.nav.no/website/pages/eksempler/dropdown/demo.tsx:15
`onSelect` 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. (×2) — aksel.nav.no/website/pages/eksempler/table-menu/demo.tsx:35, aksel.nav.no/website/pages/eksempler/table-menu/demo.tsx:38
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. — @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:3
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×5) — aksel.nav.no/website/e2e/global-search.e2e.ts:177, aksel.nav.no/website/e2e/global-search.e2e.ts:203, aksel.nav.no/website/e2e/global-search.e2e.ts:403, …
What to do
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
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.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `@navikt/aksel`, `apps/mcp-server`.
`aksel.nav.no/website/proxy.ts` reports through `console.*` at line 72 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/proxy.ts:72
`aksel.nav.no/website/proxy.ts` reports through `console.*` at line 141 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/proxy.ts:141
`aksel.nav.no/website/proxy.ts` reports through `console.*` at line 157 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/proxy.ts:157
`aksel.nav.no/website/proxy.ts` reports through `console.*` at line 178 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/proxy.ts:178
`aksel.nav.no/website/pages/templates/skjemavalidering/react-hook-form.tsx` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/templates/skjemavalidering/react-hook-form.tsx:35
`aksel.nav.no/website/pages/eksempler/radio-card/error.tsx` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/radio-card/error.tsx:11
`aksel.nav.no/website/pages/eksempler/radio/description.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/radio/description.tsx:5
`aksel.nav.no/website/pages/eksempler/radio/disabled.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/radio/disabled.tsx:5
`aksel.nav.no/website/pages/eksempler/radio/error.tsx` reports through `console.*` at line 10 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/radio/error.tsx:10
`aksel.nav.no/website/pages/eksempler/radio/hide-legend.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/radio/hide-legend.tsx:5
`aksel.nav.no/website/pages/eksempler/radio/medium.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/radio/medium.tsx:5
`aksel.nav.no/website/pages/eksempler/radio/radio-description.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/radio/radio-description.tsx:5
`aksel.nav.no/website/pages/eksempler/radio/readonly.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/radio/readonly.tsx:5
`aksel.nav.no/website/pages/eksempler/radio/small.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/radio/small.tsx:5
`aksel.nav.no/website/pages/eksempler/progress-bar/indeterminate.tsx` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/progress-bar/indeterminate.tsx:14
`aksel.nav.no/website/pages/eksempler/monthpicker/validation.tsx` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/monthpicker/validation.tsx:18
`aksel.nav.no/website/pages/eksempler/header/search.tsx` reports through `console.*` at line 15 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/header/search.tsx:15
`aksel.nav.no/website/pages/eksempler/datepicker/validation.tsx` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/datepicker/validation.tsx:18
`aksel.nav.no/website/pages/eksempler/combobox/multi-select-controlled.tsx` reports through `console.*` at line 13 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/combobox/multi-select-controlled.tsx:13
`aksel.nav.no/website/pages/eksempler/checkbox-card/demo.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/checkbox-card/demo.tsx:5
`aksel.nav.no/website/pages/eksempler/checkbox/checkbox-description.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/checkbox/checkbox-description.tsx:5
`aksel.nav.no/website/pages/eksempler/checkbox/description.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/checkbox/description.tsx:5
`aksel.nav.no/website/pages/eksempler/checkbox/disabled.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/checkbox/disabled.tsx:5
`aksel.nav.no/website/pages/eksempler/checkbox/group-error.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/checkbox/group-error.tsx:5
`aksel.nav.no/website/pages/eksempler/checkbox/hide-legend.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/checkbox/hide-legend.tsx:5
`aksel.nav.no/website/pages/eksempler/checkbox/medium.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/checkbox/medium.tsx:5
`aksel.nav.no/website/pages/eksempler/checkbox/readonly.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/checkbox/readonly.tsx:5
`aksel.nav.no/website/pages/eksempler/checkbox/small.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/pages/eksempler/checkbox/small.tsx:5
`aksel.nav.no/website/app/api/webhooks/tags/route.ts` reports through `console.*` at line 31 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/api/webhooks/tags/route.ts:31
`aksel.nav.no/website/app/api/webhooks/tags/route.ts` reports through `console.*` at line 55 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/api/webhooks/tags/route.ts:55
`aksel.nav.no/website/app/api/webhooks/tags/route.ts` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/api/webhooks/tags/route.ts:64
`aksel.nav.no/website/app/api/component-props/route.ts` reports through `console.*` at line 147 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/api/component-props/route.ts:147
`aksel.nav.no/website/app/_ui/utils/format-text.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/_ui/utils/format-text.ts:24
`aksel.nav.no/website/app/_ui/global-search/server/GlobalSearch.actions.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/_ui/global-search/server/GlobalSearch.actions.ts:18
`aksel.nav.no/website/app/_ui/global-search/server/GlobalSearch.fetch.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/_ui/global-search/server/GlobalSearch.fetch.ts:24
`aksel.nav.no/website/app/_ui/cookie-consent/CookieConsent.actions.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/_ui/cookie-consent/CookieConsent.actions.ts:29
`aksel.nav.no/website/app/_ui/cookie-consent/CookieConsent.Provider.tsx` reports through `console.*` at line 60 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/_ui/cookie-consent/CookieConsent.Provider.tsx:60
`aksel.nav.no/website/app/_ui/cookie-consent/CookieConsent.Provider.tsx` reports through `console.*` at line 105 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/_ui/cookie-consent/CookieConsent.Provider.tsx:105
`aksel.nav.no/website/app/_ui/cookie-consent/CookieConsent.Provider.tsx` reports through `console.*` at line 117 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — aksel.nav.no/website/app/_ui/cookie-consent/CookieConsent.Provider.tsx:117
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
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 14 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:7
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.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release. — REDACTED:52
Job `upload` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it. (×2) — REDACTED:45, REDACTED:29
Job `build_and_deploy` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it. (×3) — REDACTED:48, REDACTED:81, REDACTED:57
Job `build` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it. — REDACTED:84
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Run the production rollout in a protected environment, behind a manual approval, or after the tests it must pass, so a bad push is stopped before users get it.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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 `callback to test` 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) — @navikt/aksel/src/codemod/utils/check.ts:31, @navikt/aksel/src/codemod/utils/check.ts:32
`clipboardy.writeSync` in `printRemaining` 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. — @navikt/aksel/src/codemod/v8-tokens/tasks/print-remaining.ts:190
`readFileSync` in `writeComponentNames` 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. — @navikt/core/react/scripts/metadata/component-names.ts:71
`writeFileSync` in `writeComponentNames` 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. — @navikt/core/react/scripts/metadata/component-names.ts:76
`fs.readFileSync` in `callback to importDeclarations.forEach` 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. — aksel.nav.no/website/scripts/update-examples/parts/filter-code.ts:65
`fs.readFileSync` in `parseCodeFile` 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. — aksel.nav.no/website/scripts/update-examples/parts/parse-code-files.ts:35
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety9.9 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
23 duplicated blocks under @navikt/core/react/src/ have copies in at least two of the sibling directories accordion, action-menu, chips, data, datepicker, dialog (+17 more sibling(s) not listed) — 10 of them are reported below, and 13 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 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 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 23 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. — @navikt/core/react/src/datepicker/root/useDatepicker.tsx:101
10 duplicated blocks under @navikt/core/react/src/form/ have copies in at least two of the sibling directories checkbox, checkbox-card, radio, radio-card, search, select (+2 more sibling(s) not listed) — 6 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — @navikt/core/react/src/form/textarea/Textarea.tsx:122
7 duplicated blocks under aksel.nav.no/sanity-studio/schema/documents/ have copies in at least two of the sibling directories god-praksis, grunnleggende, komponenter, presets, prinsipper, templates — 6 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 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. — aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:1
@navikt/core/react/src/datepicker/root/useDatepicker.tsx:101 · @navikt/core/react/src/monthpicker/root/useMonthPicker.tsx:82 — the two spans are one implementation copied and then locally edited — 678 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. — @navikt/core/react/src/datepicker/root/useDatepicker.tsx:101
aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:1 · aksel.nav.no/sanity-studio/schema/documents/templates/artikkel.tsx:1 — these 2 files are line-for-line copies of one another — 73 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. — aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:1
@navikt/core/react/src/timeline/period-clickable/TimelineClickablePeriodInternal.tsx:57 · @navikt/core/react/src/timeline/pin/TimelinePinInternal.tsx:43 — the two spans are one implementation copied and then locally edited — 285 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. — @navikt/core/react/src/timeline/period-clickable/TimelineClickablePeriodInternal.tsx:57
aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:19 · aksel.nav.no/sanity-studio/schema/documents/komponenter/artikkel.tsx:21 · aksel.nav.no/sanity-studio/schema/documents/templates/artikkel.tsx:19 — 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. — aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:19
@navikt/core/react/src/typography/BodyLong.tsx:8 · @navikt/core/react/src/typography/BodyShort.tsx:8 — 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. — @navikt/core/react/src/typography/BodyLong.tsx:8
aksel.nav.no/sanity-studio/schema/documents/komponenter/landingsside.tsx:7 · aksel.nav.no/sanity-studio/schema/documents/templates/landingsside.tsx:7 — 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. — aksel.nav.no/sanity-studio/schema/documents/komponenter/landingsside.tsx:7
@navikt/core/react/src/datepicker/root/DatePickerRoot.tsx:131 · @navikt/core/react/src/monthpicker/root/MonthPickerRoot.tsx:130 — the two spans are one implementation copied and then locally edited — 139 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. — @navikt/core/react/src/datepicker/root/DatePickerRoot.tsx:131
aksel.nav.no/sanity-studio/sanity.config.ts:48 · aksel.nav.no/sanity-studio/sanity.config.ts:95 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — aksel.nav.no/sanity-studio/sanity.config.ts:48
@navikt/core/react/src/form/textarea/Textarea.tsx:122 · @navikt/core/react/src/form/textfield/TextField.tsx:82 — 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. — @navikt/core/react/src/form/textarea/Textarea.tsx:122
@navikt/aksel-stylelint/src/rules/aksel-no-class-override/index.ts:11 · @navikt/aksel-stylelint/src/rules/aksel-no-legacy-classes/index.ts:11 — 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. — @navikt/aksel-stylelint/src/rules/aksel-no-class-override/index.ts:11
aksel.nav.no/sanity-studio/schema/documents/grunnleggende/landingsside.tsx:34 · aksel.nav.no/sanity-studio/schema/documents/komponenter/landingsside.tsx:26 · aksel.nav.no/sanity-studio/schema/documents/templates/landingsside.tsx:25 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — aksel.nav.no/sanity-studio/schema/documents/grunnleggende/landingsside.tsx:34
@navikt/core/react/src/form/checkbox/Checkbox.tsx:31 · @navikt/core/react/src/form/radio/Radio.tsx:27 — 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. — @navikt/core/react/src/form/checkbox/Checkbox.tsx:31
@navikt/core/react/src/form/select/Select.tsx:102 · @navikt/core/react/src/form/textarea/Textarea.tsx:122 · @navikt/core/react/src/form/textfield/TextField.tsx:82 — 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. — @navikt/core/react/src/form/select/Select.tsx:102
@navikt/core/react/src/legacy/combobox/Combobox.tsx:37 · @navikt/core/react/src/utils/components/date/input/DateInput.tsx:128 — 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. — @navikt/core/react/src/legacy/combobox/Combobox.tsx:37
REDACTED:86 · REDACTED:205 · REDACTED:253 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:86
@navikt/core/react/src/data-grid-preferences/row-density-settings/DataGridPreferencesRowDensitySettings.tsx:15 · @navikt/core/react/src/data-grid-preferences/text-size-settings/DataGridPreferencesTextSizeSettings.tsx:14 — 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. — @navikt/core/react/src/data-grid-preferences/row-density-settings/DataGridPreferencesRowDensitySettings.tsx:15
@navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:185 · @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:218 — 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. — @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:185
@navikt/aksel/src/codemod/v8-tokens/transforms/v8-tokens-less.ts:13 · @navikt/aksel/src/codemod/v8-tokens/transforms/v8-tokens-scss.ts:13 — 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. — @navikt/aksel/src/codemod/v8-tokens/transforms/v8-tokens-less.ts:13
@navikt/core/tailwind/src/build-v3.ts:6 · @navikt/core/tailwind/src/build-v4.ts:6 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited. — @navikt/core/tailwind/src/build-v3.ts:6
@navikt/core/react/src/timeline/axis-labels/TimelineAxisLabelsInternal.tsx:31 · @navikt/core/react/src/timeline/axis-labels/TimelineAxisLabelsInternal.tsx:59 · @navikt/core/react/src/timeline/axis-labels/TimelineAxisLabelsInternal.tsx:87 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — @navikt/core/react/src/timeline/axis-labels/TimelineAxisLabelsInternal.tsx:31
@navikt/core/react/src/data/table/helpers/table-grid-nav.ts:134 · @navikt/core/react/src/data/table/helpers/table-grid-nav.ts:168 — the two spans are one implementation copied and then locally edited — 122 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. — @navikt/core/react/src/data/table/helpers/table-grid-nav.ts:134
@navikt/core/react/src/dropdown/grouped-list-item/DropdownMenuGroupedListItem.tsx:17 · @navikt/core/react/src/dropdown/list-item/DropdownMenuListItem.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. — @navikt/core/react/src/dropdown/grouped-list-item/DropdownMenuGroupedListItem.tsx:17
aksel.nav.no/sanity-studio/schema/documents/admin/ds-stats.ts:10 · aksel.nav.no/sanity-studio/schema/documents/admin/ds-stats.ts:30 · aksel.nav.no/sanity-studio/schema/documents/admin/ds-stats.ts:50 — all 3 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — aksel.nav.no/sanity-studio/schema/documents/admin/ds-stats.ts:10
@navikt/core/react/src/link-card/description/LinkCardDescription.tsx:4 · @navikt/core/react/src/link-card/footer/LinkCardFooter.tsx:4 — 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. — @navikt/core/react/src/link-card/description/LinkCardDescription.tsx:4
REDACTED:312 · REDACTED:332 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:312
@navikt/core/react/src/action-menu/checkbox-item/ActionMenuCheckboxItem.tsx:43 · @navikt/core/react/src/action-menu/radio-item/ActionMenuRadioItem.tsx:30 — 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. — @navikt/core/react/src/action-menu/checkbox-item/ActionMenuCheckboxItem.tsx:43
tooling/analyzer/src/md-message.ts:61 · tooling/analyzer/src/md-message.ts:86 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — tooling/analyzer/src/md-message.ts:61
@navikt/aksel/src/codemod/transforms/v8.0.0/box/box.ts:50 · @navikt/aksel/src/codemod/transforms/v8.0.0/box/box.ts:76 — 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. — @navikt/aksel/src/codemod/transforms/v8.0.0/box/box.ts:50
@navikt/core/react/src/chips/removable/ChipsRemovable.tsx:58 · @navikt/core/react/src/chips/toggle/ChipsToggle.tsx:84 — 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. — @navikt/core/react/src/chips/removable/ChipsRemovable.tsx:58
@navikt/core/react/src/chips/removable/ChipsRemovable.tsx:58 · @navikt/core/react/src/chips/toggle/ChipsToggle.tsx:84 · @navikt/core/react/src/toggle-group/root/ToggleGroupRoot.tsx:85 — 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. — @navikt/core/react/src/chips/removable/ChipsRemovable.tsx:58
@navikt/core/react/src/data/stories/DataTableProfiler.tsx:142 · @navikt/core/react/src/data/stories/DataTableProfiler.tsx:161 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — @navikt/core/react/src/data/stories/DataTableProfiler.tsx:142
@navikt/core/react/src/form/search/Search.tsx:248 · @navikt/core/react/src/form/select/Select.tsx:142 · @navikt/core/react/src/utils/components/date/input/DateInput.tsx:186 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — @navikt/core/react/src/form/search/Search.tsx:248
@navikt/core/react/src/form/select/Select.tsx:144 · @navikt/core/react/src/form/textarea/Textarea.tsx:178 · @navikt/core/react/src/form/textfield/TextField.tsx:122 — 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. — @navikt/core/react/src/form/select/Select.tsx:144
aksel.nav.no/sanity-studio/schema/documents/designsystem-forside.tsx:130 · aksel.nav.no/sanity-studio/schema/documents/designsystem-forside.tsx:155 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — aksel.nav.no/sanity-studio/schema/documents/designsystem-forside.tsx:130
aksel.nav.no/sanity-studio/structure/article-lists.ts:19 · aksel.nav.no/sanity-studio/structure/article-lists.ts:37 — 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. — aksel.nav.no/sanity-studio/structure/article-lists.ts:19
@navikt/aksel-stylelint/src/rules/aksel-design-token-no-global-override/index.ts:21 · @navikt/aksel-stylelint/src/rules/aksel-no-internal-tokens/index.ts:46 — 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. — @navikt/aksel-stylelint/src/rules/aksel-design-token-no-global-override/index.ts:21
@navikt/aksel/src/codemod/transforms/v8.0.0/box-new/box-new.ts:17 · @navikt/aksel/src/codemod/transforms/v8.0.0/box-new/box-new.ts:36 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — @navikt/aksel/src/codemod/transforms/v8.0.0/box-new/box-new.ts:17
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
@navikt/aksel/src/codemod/run-codeshift.ts:4 imports jscodeshift/src/Runner, 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. — @navikt/aksel/src/codemod/run-codeshift.ts:4
@navikt/aksel/src/codemod/utils/check.ts:2 imports jscodeshift/dist/testUtils, 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. — @navikt/aksel/src/codemod/utils/check.ts:2
@navikt/aksel/src/codemod/v8-tokens/run-tooling.ts:5 imports jscodeshift/src/Runner, 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. — @navikt/aksel/src/codemod/v8-tokens/run-tooling.ts:5
@navikt/core/tailwind/src/build-v3.ts:3 reaches into another package with a relative path (../../tokens/config/kebabCase) — import the package by name instead. — @navikt/core/tailwind/src/build-v3.ts:3
@navikt/core/tailwind/src/build-v3.ts:4 reaches into another package with a relative path (../../tokens/src/tokens/breakpoint) — import the package by name instead. — @navikt/core/tailwind/src/build-v3.ts:4
@navikt/core/tailwind/src/build-v4.ts:3 reaches into another package with a relative path (../../tokens/config/kebabCase) — import the package by name instead. — @navikt/core/tailwind/src/build-v4.ts:3
@navikt/core/tailwind/src/build-v4.ts:4 reaches into another package with a relative path (../../tokens/src/tokens/breakpoint) — import the package by name instead. — @navikt/core/tailwind/src/build-v4.ts:4
aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:7 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:7
aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:18 imports @navikt/ds-react/List, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:18
aksel.nav.no/sanity-studio/schema/custom-components/LinkRenderer.tsx:5 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/custom-components/LinkRenderer.tsx:5
aksel.nav.no/sanity-studio/schema/custom-components/WriteHelp.tsx:1 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/custom-components/WriteHelp.tsx:1
aksel.nav.no/sanity-studio/schema/custom-components/WriteHelp.tsx:2 imports @navikt/ds-react/List, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/custom-components/WriteHelp.tsx:2
aksel.nav.no/sanity-studio/schema/custom-components/gp/EndringsloggReferanser.tsx:6 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/custom-components/gp/EndringsloggReferanser.tsx:6
aksel.nav.no/sanity-studio/schema/custom-components/gp/InnholdstypeHighlight.tsx:10 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/custom-components/gp/InnholdstypeHighlight.tsx:10
aksel.nav.no/sanity-studio/schema/custom-components/gp/UndertemaHighlight.tsx:10 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/custom-components/gp/UndertemaHighlight.tsx:10
aksel.nav.no/sanity-studio/schema/custom-components/updateInfo.tsx:11 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/custom-components/updateInfo.tsx:11
aksel.nav.no/sanity-studio/schema/documents/komponenter/artikkel.tsx:2 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/documents/komponenter/artikkel.tsx:2
aksel.nav.no/sanity-studio/schema/objects/shared/accordion.tsx:4 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/objects/shared/accordion.tsx:4
aksel.nav.no/sanity-studio/schema/objects/shared/description-list.tsx:4 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — aksel.nav.no/sanity-studio/schema/objects/shared/description-list.tsx:4
What to do
Fix the listed violations: declare the workspace packages these files import in the importing package's own REDACTED dependencies (12 rows) — those imports are already bare package specifiers, so the import statements do not change, only the manifest; import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (7 rows).
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.
(anonymous) has cyclomatic complexity 34 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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:62
getAlphaColor has cyclomatic complexity 33 and cognitive complexity 46; 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. — @navikt/core/tokens/src/tokens/colors/create-alpha.ts:87
(anonymous) has cyclomatic complexity 31 and cognitive complexity 47; 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. — @navikt/core/react/src/legacy/combobox/Input/Input.tsx:159
RowSelectionCell has cyclomatic complexity 28 and cognitive complexity 36; 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. — @navikt/core/react/src/data/table/tr/DataTableTr.tsx:289
markdownMessage has cyclomatic complexity 28 and cognitive complexity 35; 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. — tooling/analyzer/src/md-message.ts:7
(anonymous) has cyclomatic complexity 26 and cognitive complexity 35; 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. — @navikt/core/react/src/monthpicker/root/MonthPicker.util.ts:15
RowExpansionCell has cyclomatic complexity 26 and cognitive complexity 34; 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. — @navikt/core/react/src/data/table/tr/DataTableTr.tsx:148
(anonymous) has cyclomatic complexity 24 and cognitive complexity 35; 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. — @navikt/core/react/src/timeline/root/TimelineKeyboardNavProvider.tsx:51
FilteredOptions has cyclomatic complexity 23 and cognitive complexity 13; 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. — @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptions.tsx:16
(anonymous) has cyclomatic complexity 22 and cognitive complexity 20; 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. — @navikt/core/react/src/utils/components/floating/Floating.tsx:273
(anonymous) has cyclomatic complexity 21 and cognitive complexity 16; 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. — @navikt/core/react/src/form/useFormField.ts:63
(anonymous) has cyclomatic complexity 20 and cognitive complexity 28; 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. — @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:94
pickRangeSelection has cyclomatic complexity 19 and cognitive complexity 25; 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. — @navikt/core/react/src/utils/date/pick-range-selection.ts:14
(anonymous) has cyclomatic complexity 19 and cognitive complexity 17; 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. — @navikt/core/react/src/tooltip/Tooltip.tsx:113
handleChange has cyclomatic complexity 19 and cognitive complexity 16; 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. — @navikt/core/react/src/datepicker/root/useDatepicker.tsx:275
(anonymous) has cyclomatic complexity 18 and cognitive complexity 23; 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. — @navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx:328
compareResults has cyclomatic complexity 18 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 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. — tooling/analyzer/src/helpers/compare.ts:45
(anonymous) has cyclomatic complexity 18 and cognitive complexity 17; 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. — @navikt/core/react/src/modal/root/ModalRoot.tsx:26
getJSXLiteralValue has cyclomatic complexity 17 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — @navikt/aksel/src/codemod/utils/jsx-value.ts:27
(anonymous) has cyclomatic complexity 17 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — @navikt/core/react/src/legacy/combobox/Input/Input.tsx:75
(anonymous) has cyclomatic complexity 17 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. — @navikt/core/react/src/form/textarea/Textarea.tsx:76
toValidation has cyclomatic complexity 17 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. — @navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx:147
callback has cyclomatic complexity 16 and cognitive complexity 23; 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. — apps/mcp-server/src/tools/find-docs.ts:54
(anonymous) has cyclomatic complexity 16 and cognitive complexity 23; 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. — tooling/changelog/createMainChangelog.ts:141
(anonymous) has cyclomatic complexity 16 and cognitive complexity 13; 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. — @navikt/core/react/src/button/Button.tsx:71
Program has cyclomatic complexity 15 and cognitive complexity 23; 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. — tooling/eslint/args-check.js:15
(anonymous) has cyclomatic complexity 15 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 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. (×2) — @navikt/core/react/src/monthpicker/root/MonthPicker.util.ts:164, @navikt/core/react/src/timeline/root/TimelineKeyboardNavProvider.tsx:143
getAutoColumnWidth has cyclomatic complexity 15 and cognitive complexity 18; 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. — @navikt/core/react/src/data/table/column-header/useTableColumnResize.ts:325
lockScroll has cyclomatic complexity 15 and cognitive complexity 15; 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. — @navikt/core/react/src/utils/hooks/useScrollLock.ts:97
Items has cyclomatic complexity 15 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. — @navikt/core/react/src/toggle-group/ToggleGroup.stories.tsx:24
analyzeReact has cyclomatic complexity 14 and cognitive complexity 28; 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. — tooling/analyzer/src/analyze-react.ts:25
(anonymous) has cyclomatic complexity 14 and cognitive complexity 13; 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. — @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:155
render has cyclomatic complexity 14 and cognitive complexity 13; 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. — @navikt/core/react/src/process/Process.stories.tsx:341
(anonymous) has cyclomatic complexity 14 and cognitive complexity 12; 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. — @navikt/core/react/src/data/table/column-header/DataTableColumnHeader.tsx:64
handleChange has cyclomatic complexity 14 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. — @navikt/core/react/src/monthpicker/root/useMonthPicker.tsx:264
(anonymous) has cyclomatic complexity 13 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 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. — @navikt/core/react/src/utils/date/parse-date.ts:35
createValueSuggestions has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — @navikt/core/react/src/data/token-filter/helpers/generate-autocomplete-options.ts:267
fn has cyclomatic complexity 13 and cognitive complexity 16; 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. — @navikt/core/react/src/utils/components/floating/Floating.utils.ts:17
generateAutoCompleteOptions has cyclomatic complexity 13 and cognitive complexity 15; 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. — @navikt/core/react/src/data/token-filter/helpers/generate-autocomplete-options.ts:31
Do you agree with this assessment?
R3 · Large Files8.7 / 10Strong✓ 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.
@navikt/aksel/src/codemod/v8-tokens/config/legacy.tokens.ts has 1763 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/aksel/src/codemod/v8-tokens/config/legacy.tokens.ts:1
@navikt/core/react/src/data/stories/Data.test-data.tsx has 1697 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/data/stories/Data.test-data.tsx:1
@navikt/core/react/src/data/stories/dummy-data.tsx has 1527 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/data/stories/dummy-data.tsx:1
@navikt/core/react/src/data/stories/Data.data-prop.stories.tsx has 1106 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/data/stories/Data.data-prop.stories.tsx:1
@navikt/core/react/src/action-menu/ActionMenu.stories.tsx has 987 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/action-menu/ActionMenu.stories.tsx:1
@navikt/core/react/src/utils/components/floating-menu/Menu.tsx has 925 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/utils/components/floating-menu/Menu.tsx:1
@navikt/core/react/src/link-card/LinkCard.stories.tsx has 864 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/link-card/LinkCard.stories.tsx:1
@navikt/core/react/src/modal/helpers/dialog-polyfill.ts has 861 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:1
@navikt/core/react/src/data/stories/Data.stories.tsx has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/data/stories/Data.stories.tsx:1
@navikt/core/react/src/dialog/Dialog.stories.tsx has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/dialog/Dialog.stories.tsx:1
@navikt/core/react/src/dialog/Dialog.tests.stories.tsx has 708 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/dialog/Dialog.tests.stories.tsx:1
@navikt/core/react/src/datepicker/DatePicker.stories.tsx has 652 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/datepicker/DatePicker.stories.tsx:1
@navikt/core/react/src/timeline/Timeline.stories.tsx has 628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/timeline/Timeline.stories.tsx:1
@navikt/core/react/src/legacy/combobox/Combobox.stories.tsx has 623 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/legacy/combobox/Combobox.stories.tsx:1
@navikt/core/react/src/utils/components/floating-menu/Menu.stories.tsx has 583 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/utils/components/floating-menu/Menu.stories.tsx:1
@navikt/core/react/src/data/table/root/DataGridTableRoot.tsx has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:1
@navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tests.stories.tsx has 541 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tests.stories.tsx:1
@navikt/core/react/src/datepicker/DatePicker.tests.stories.tsx has 537 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/datepicker/DatePicker.tests.stories.tsx:1
@navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx has 535 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx:1
@navikt/core/react/src/process/Process.stories.tsx has 531 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/process/Process.stories.tsx:1
@navikt/core/react/src/primitives/box/Box.stories.tsx has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/primitives/box/Box.stories.tsx:1
@navikt/core/react/src/utils/components/floating/Floating.tsx has 487 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/utils/components/floating/Floating.tsx:1
@navikt/core/react/src/modal/Modal.stories.tsx has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/modal/Modal.stories.tsx:1
@navikt/aksel/src/codemod/v8-tokens/config/v8.tokens.ts has 466 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/aksel/src/codemod/v8-tokens/config/v8.tokens.ts:1
@navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx:1
@navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx has 446 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx:1
@navikt/core/react/src/utils/components/Listbox/Listbox.stories.tsx has 442 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/utils/components/Listbox/Listbox.stories.tsx:1
@navikt/core/react/src/primitives/bleed/Bleed.stories.tsx has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/primitives/bleed/Bleed.stories.tsx:1
@navikt/core/react/src/utils/components/floating/Floating.stories.tsx has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/utils/components/floating/Floating.stories.tsx:1
@navikt/core/react/src/form/form-summary/FormSummary.stories.tsx has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/form/form-summary/FormSummary.stories.tsx:1
@navikt/core/react/src/list/List.stories.tsx has 417 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/list/List.stories.tsx:1
@navikt/core/react/src/form/combobox2/Combobox2.stories.tsx has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/form/combobox2/Combobox2.stories.tsx:1
aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx has 409 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx:1
@navikt/core/react/src/form/checkbox/Checkbox.stories.tsx has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — @navikt/core/react/src/form/checkbox/Checkbox.stories.tsx:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage6.8 / 10Adequate✓ Tool-verified
React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.
Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx:1, @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:1, aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each 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.
`tooling/analyzer` is TypeScript, but a type error in it cannot fail anything this repository runs: its `run:analyze-npm-action` script (`yarn clean && concurrently "yarn pack-remote && tsx ./src/runners/analyze-pac…`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. 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. — tooling/analyzer/package.json:20
`tooling/scripts` is TypeScript, but a type error in it cannot fail anything this repository runs: its `script:git-release` script (`tsx ./git-release`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. 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. — tooling/scripts/package.json:6
`@navikt/core/tailwind` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build` script (`yarn tsx ./src/build-v3.ts && yarn tsx ./src/build-v4.ts`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. 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. — @navikt/core/tailwind/package.json:17
`@navikt/core/tokens` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build` script (`tsx ./src && yarn build:figma-config && yarn build:plugin && tsx ./config/ver…`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. 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. — @navikt/core/tokens/package.json:20
Do you agree with this assessment?
R7 · Dead Code8.4 / 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.
99 file(s) (~9309 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: @navikt/aksel/src/index.ts imports './version', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — @navikt/aksel
7 file(s) (~176 LoC) were excluded from dead-code analysis. This package's entry point(s) resolved, but the walk stopped one hop in: apps/playroom/src/components.ts imports './auto-generated-imports', which is not in the scanned tree. That is usually a generated or build-output module, so reachability cannot see past it and no dead-code claim is made about this package. Nothing is necessarily wrong here. — apps/playroom
Unreachable from the 141 application, 32 tooling and 231 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 (141 application, 32 tooling, 231 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 (×36) — @navikt/core/react/src/data/stories/DataTableProfiler.tsx, @navikt/core/react/src/form/combobox2/list/useAnnounce.ts, @navikt/core/react/src/modal/Modal.types.test-d.ts, …
no import path from any entry point (141 application, 32 tooling, 231 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (@navikt/core/react/src/data/filter/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — @navikt/core/react/src/data/filter/root/DataFilterRoot.tsx
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×3) — aksel.nav.no/sanity-studio/functions/unpublish/index.ts:3, aksel.nav.no/sanity-studio/schema/documents/admin/editorialStaff.tsx:2, aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx:1
Declared in the root 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. — REDACTED:114
Declared in aksel.nav.no/sanity-studio/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — aksel.nav.no/sanity-studio/package.json:24
Declared in apps/mcp-server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. — apps/mcp-server/package.json:20
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. Markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. 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. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — aksel.nav.no/website/app/_ui/global-search/server/GlobalSearch.fetch.ts:72
`https://core.sanity-cdn.com/bridge.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. — aksel.nav.no/sanity-studio/.sanity/runtime/index.html:307
`app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — REDACTED:123
What to do
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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/10 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.
`fetchUser` 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) — aksel.nav.no/website/app/_ui/system-panel/SystemPanel.action.tsx:28, aksel.nav.no/website/app/_ui/footer/Footer.edit.tsx:14
`ImageAsThemedSvg` 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 })`. — aksel.nav.no/website/app/_ui/image-as-svg/ImageAsSvg.tsx:7
`fetchAllSanityPages` 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 })`. — aksel.nav.no/website/app/_sanity/live-fetch.ts:17
`GodPraksisPictogram` 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 })`. — aksel.nav.no/website/app/(routes)/(root)/_ui/pictogram/GodPraksisPictogram.tsx:8
`DynamicIconPage` 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 })`. — aksel.nav.no/website/app/(routes)/(designsystemet)/komponenter/ikoner/page.tsx:36
`revalidate` 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 })`. — aksel.nav.no/sanity-studio/functions/invalidate-tags/index.ts:3
`useRemoteConfig` 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 })`. — @navikt/core/tokens/src/figma/plugin/AkselVariablesInterface.ts:30
`fetchIcons` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:12
`fetchDownloadUrls` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:57
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — tooling/analyzer/src/helpers/bundle-size.ts:61, @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:524, @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:536
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`error` at line 34 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — aksel.nav.no/website/app/(routes)/(god-praksis)/_ui/feedback/actions.ts:34
`error` at line 51 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — aksel.nav.no/website/app/(routes)/(god-praksis)/_ui/feedback/actions.ts:51
`error` at line 82 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — aksel.nav.no/website/app/(routes)/(god-praksis)/_ui/feedback/actions.ts:82
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.
10/17 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 18 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 51 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — 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 — docker build failed (exit 1) — ------ REDACTED:1 -------------------- 1 | >>> FROM gcr.io/distroless/nodejs24-debian13 2 | 3 | ENV NODE_ENV=production -------------------- ERROR: failed to solve: gcr.io/distroless/nodejs24-debian13: failed to resolve source metadata for gcr.io/distroless/nodejs24-debian13:latest: failed to do request: Head "https://gcr.io/v2/distroless/nodejs24-debian13/manifests/latest": Forbidden; likely cause (our sandbox): an image the REDACTED builds FROM could not be fetched: our sandbox reaches registries only through its pull-through mirror, and the mirror did not serve it. This is a limit of our sandbox, not of your repository; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — 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.
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 — Test reliability not measured — JavaScript/TypeScript suite did not run
D14 License Compliance — Not scored — this repository's 1299 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 1 of them (registry returned 400), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
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.
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 12 candidate(s) found and not reported.
D22 Internal API Consistency — N/A — too few peer members to establish a convention across 1 exposed TypeScript types.
D25 ADR Conformance — no ADRs to check
D32 Data Compliance (PII/GDPR) — 83 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D4 Code Duplication — This repository's production source (.mts, .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 — JavaScript/TypeScript suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 domain event(s); its domain events are published by services or handlers — no domain entity raises one)
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage 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
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
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
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.
AC4 · Keyboard semantics· Click handler on a non-interactive <div> · ×6
Click handler on a non-interactive <div> @navikt/core/react/src/form/checkbox/Checkbox.tsx:30— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> @navikt/core/react/src/form/file-upload/dropzone/FileUploadDropzone.tsx:94— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> @navikt/core/react/src/form/radio/Radio.tsx:26— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> @navikt/core/react/src/legacy/combobox/Input/InputController.tsx:58— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> @navikt/core/react/src/legacy/combobox/Input/ToggleListButton.tsx:11— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
Click handler on a non-interactive <div> @navikt/core/react/src/tabs/scroll-button/TabsScrollButtonInternal.tsx:17— A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabIndex={0} + a key handler.
AC2 · Forms & labels· <button> with no accessible text · ×2
<button> with no accessible text @navikt/core/react/src/data/drag-and-drop/drag-handler/DragAndDropDragHandler.tsx:49— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
<button> with no accessible text @navikt/core/react/src/data/drag-and-drop/drag-handler/DragAndDropDragHandler.tsx:119— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
Viewport restricts zoom aksel.nav.no/sanity-studio/.sanity/runtime/index.html:9— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
AC3 · Page structure· Document without a <title> · ×1
Document without a <title> aksel.nav.no/website/app/global-error.tsx:23— A page with no <title> gives no name in the tab, history or screen-reader page list. Declare it the way this router does — Next App Router `export const metadata = { title }`, React Router/Remix `export function meta`, TanStack Start `head`, or a Helmet/Head component.
Unlisted import '@sanity/id-utils' aksel.nav.no/sanity-studio/functions/unpublish/index.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'next' aksel.nav.no/sanity-studio/schema/documents/admin/editorialStaff.tsx:2— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Unlisted import 'next-sanity' aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx:1— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
Serious — 552 finding(s)
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.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 aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file @navikt/core/css/config/bundle.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 aksel.nav.no/sanity-studio/schema/documents/designsystem-forside.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file @navikt/aksel/src/codemod/transforms/v8.0.0/box/box.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 @navikt/core/tokens/src/figma/plugin/AkselVariablesInterface.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 tooling/changelog/createMainChangelog.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 aksel.nav.no/sanity-studio/schema/documents/komponenter/artikkel.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file @navikt/core/react/src/data/stories/DataTableProfiler.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file @navikt/core/tokens/src/figma/plugin/FigmaPluginInterface.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 aksel.nav.no/sanity-studio/structure/god-praksis.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 tooling/analyzer/src/md-message.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 tooling/scripts/in-sync-versions.mts: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 aksel.nav.no/sanity-studio/schema/documents/komponenter/component-metadata.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file aksel.nav.no/sanity-studio/schema/documents/prinsipper/artikkel.tsx:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file @navikt/core/react/scripts/metadata/extract-props.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 aksel.nav.no/sanity-studio/schema/schema.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 aksel.nav.no/sanity-studio/structure/article-lists.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 aksel.nav.no/sanity-studio/presentation/resolve.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 aksel.nav.no/sanity-studio/schema/documents/presets/slug.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 @navikt/aksel/src/codemod/utils/ast.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 tooling/analyzer/src/analyze-react.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.
FunctionTooLong: useRangeDatepicker.useRangeDatepicker @navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx:217— FunctionTooLong — useRangeDatepicker runs 265 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 165 over it, 2.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: page.CachedFrontpageContent aksel.nav.no/website/app/(routes)/(root)/page.tsx:96— FunctionTooLong — CachedFrontpageContent runs 211 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 111 over it, 2.11× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: intro-med-alternativ-soknad.Example aksel.nav.no/website/pages/templates/soknad-introside/intro-med-alternativ-soknad.tsx:26— FunctionTooLong — Example runs 197 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 97 over it, 1.97× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: intro-med-fremhevet-info.Example aksel.nav.no/website/pages/templates/soknad-introside/intro-med-fremhevet-info.tsx:27— FunctionTooLong — Example runs 189 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 89 over it, 1.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: list.transformer @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:31— FunctionTooLong — transformer runs 183 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 83 over it, 1.83× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: intro.Example aksel.nav.no/website/pages/templates/soknad-introside/intro.tsx:26— FunctionTooLong — Example runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: page.DynamicTemaPage aksel.nav.no/website/app/(routes)/(god-praksis)/god-praksis/[tema]/page.tsx:139— FunctionTooLong — DynamicTemaPage runs 172 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 72 over it, 1.72× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: status.getStatus REDACTED:15— FunctionTooLong — getStatus runs 164 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 64 over it, 1.64× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: filteredOptionsContext.FilteredOptionsProvider @navikt/core/react/src/legacy/combobox/FilteredOptions/filteredOptionsContext.tsx:53— FunctionTooLong — FilteredOptionsProvider runs 149 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 49 over it, 1.49× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: bundle.bundle @navikt/core/css/config/bundle.ts:23— FunctionTooLong — bundle runs 137 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 37 over it, 1.37× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: standard.Example aksel.nav.no/website/pages/templates/soknad-oppsummeringsside/standard.tsx:25— FunctionTooLong — Example runs 136 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 36 over it, 1.36× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: useTableColumnResize.useTableColumnResize @navikt/core/react/src/data/table/column-header/useTableColumnResize.ts:108— FunctionTooLong — useTableColumnResize runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: god-praksis.godPraksisPanes aksel.nav.no/sanity-studio/structure/god-praksis.ts:21— FunctionTooLong — godPraksisPanes runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: GodPraksisFeedback.parts.GodPraksisFeedbackForm aksel.nav.no/website/app/(routes)/(god-praksis)/_ui/feedback/GodPraksisFeedback.parts.tsx:58— FunctionTooLong — GodPraksisFeedbackForm runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: LogEntry.LogEntry aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/_ui/LogEntry.tsx:31— FunctionTooLong — LogEntry runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: page.CachedArticle aksel.nav.no/website/app/(routes)/(god-praksis)/god-praksis/artikler/[slug]/page.tsx:163— FunctionTooLong — CachedArticle runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: HighlightedBlogg.HighlightedBlogg aksel.nav.no/website/app/(routes)/(produktbloggen)/produktbloggen/_ui/HighlightedBlogg.tsx:23— FunctionTooLong — HighlightedBlogg runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: IconPage.IconPage aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/icon-page/IconPage.tsx:31— FunctionTooLong — IconPage runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: dynamic.Example aksel.nav.no/website/pages/eksempler/timeline-intern/dynamic.tsx:25— FunctionTooLong — Example runs 123 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 23 over it, 1.23× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DataTableProfiler.ProfilerDisplay @navikt/core/react/src/data/stories/DataTableProfiler.tsx:65— FunctionTooLong — ProfilerDisplay runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: print-remaining.printRemaining @navikt/aksel/src/codemod/v8-tokens/tasks/print-remaining.ts:8— FunctionTooLong — printRemaining runs 119 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 19 over it, 1.19× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: selectedOptionsContext.SelectedOptionsProvider @navikt/core/react/src/legacy/combobox/SelectedOptions/selectedOptionsContext.tsx:30— FunctionTooLong — SelectedOptionsProvider runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DatePickerMonthsInternal.DatePickerMonths @navikt/core/react/src/datepicker/months/DatePickerMonthsInternal.tsx:24— FunctionTooLong — DatePickerMonths runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: DatePickerRDPInternal.ReactDayPicker @navikt/core/react/src/datepicker/rdp/DatePickerRDPInternal.tsx:59— FunctionTooLong — ReactDayPicker runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: HighlightedArticle.Highlight aksel.nav.no/website/app/(routes)/(root)/_ui/HighlightedArticle.tsx:27— FunctionTooLong — Highlight runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× 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.
TodoComment aksel.nav.no/website/app/_ui/avatar/Avatar.tsx:96— // TODO: this creates the requirement that children _must_ be Avatar — 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 aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/_ui/FilterGroup.tsx:71— // TODO: don't really want to remove prefetch() — 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 aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/_ui/SearchForm.tsx:3— // TODO: I feel we should probably replace SearchForm and SearchField logic with — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment @navikt/core/react/src/utils/hooks/useSyncExternalStoreShim.ts:120— // TODO: Because there is no cross-renderer API for batching updates, it's — 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 @navikt/core/react/src/table/animate-height/TableAnimateHeightInternal.tsx:150— // TODO solve contentHeight = 0 — 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 @navikt/core/react/src/table/animate-height/TableAnimateHeightInternal.tsx:203— // TODO solve newHeight = 0 — 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 @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:130— // TODO(samthor): tabindex values that are not numeric are not focusable. — 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 @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:750— // TODO: Focus after the dialog, is ignored. — 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 @navikt/core/react/src/form/radio/RadioGroup.tsx:8— // TODO: Omit "role" in next major — 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 @navikt/core/react/src/form/combobox2/Combobox.tsx:209— // TODO: Dumt at ikke får hele option-objektet... Legge til i onChange? Hvis vi tilbyr onToggle så blir det så likt onChange... — 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 @navikt/core/react/src/form/combobox2/trigger/ComboboxTrigger.tsx:17— // TODO: Check ComboboxFilter presence automatically? Or check in dev and warn if prop wrong. — 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 @navikt/core/react/src/form/combobox2/popup/ComboboxPopup.tsx:70— // TODO: For at ting skal funke som det skal med skjermleser, må vi kanskje beholde fokus på knappen. — 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 @navikt/core/react/src/form/combobox2/list/useAnnounce.ts:49— // TODO: Bruk inline style fra FocusGuards.tsx — 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 @navikt/core/react/src/form/combobox2/list/useAnnounce.ts:51— // TODO Bruk root fra Provider (se Portal.tsx) — 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 @navikt/core/react/src/form/combobox2/list/ComboboxList.tsx:20— // TODO: Blir litt rart at children-funksjonen må håndtere både options og grupper. (Usikker på om typen for optOrGroup er riktig også.) — 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 @navikt/core/react/src/form/combobox2/list/ComboboxList.tsx:27— // TODO: Prop for å aktivere "async rendering", ev. basert på antall options. — 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 @navikt/core/react/src/form/combobox2/list/ComboboxList.tsx:90— // TODO: Consider moving outside of role=listbox — 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 @navikt/core/react/src/form/combobox2/list/ComboboxList.tsx:123— // TODO: Vurder å kunne slå av dette for bedre ytelse — 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 @navikt/core/react/src/data/toolbar/search-field/DataToolbarSearchField.tsx:6— // TODO: Vurder om label skal hardkodes (bør jo samsvare med placeholder...) — 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 @navikt/core/react/src/data/toolbar/search-field/DataToolbarSearchField.tsx:22— // TODO: Oversett, og vurder om skal være overstyrbart — 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 @navikt/core/react/src/data/toolbar/button/DataToolbarButton.tsx:12— // TODO: Bør kanskje ikke være innebygget, men funker ikke å bruke Tooltip rundt Button rundt ActionMenu.Trigger i dag pga. props-forwarding i Tooltip — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:249— // TODO: Consider different role that doesn't require aria-selected — 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 @navikt/core/react/src/data/table/sub-row-toggle/DataTableSubRowToggle.tsx:26— // TODO translate — 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 @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:448— // TODO translate — 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 @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:498— // TODO translate — 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.
+ 8 more in this group — see findings.md.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×19
Focus outline removed in CSS without a :focus replacement aksel.nav.no/website/app/globals.css:27— `#hovedinnhold:focus` 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 aksel.nav.no/website/app/_ui/portable-text/CustomPortableText.module.css:34— `.headingElement:focus` 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 aksel.nav.no/website/app/_ui/compare-images/CompareImages.module.css:62— `.compareImagesHandle` 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 aksel.nav.no/website/app/(routes)/(produktbloggen)/produktbloggen/_ui/Produktbloggen.module.css:154— `.main:focus` 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 aksel.nav.no/website/app/(routes)/(designsystemet)/designsystemet/_ui/ds-layers-overview/DSLayersOverview.module.css:51— `.akselLayersLink:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/overview/DesignsystemetOverview.module.css:13— `.overviewCardLink:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement @navikt/core/css/src/data-grid-preview.css:397— `.aksel-data-table__th-sort-button:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement @navikt/core/css/src/data-grid-preview.css:515— `.aksel-data-table__th-resize-handle[data-active="true"]:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement @navikt/core/css/src/date.css:224— `.aksel-date__field-input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement @navikt/core/css/src/dialog.css:20— `.aksel-dialog__popup:focus` 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 @navikt/core/css/src/link-anchor.css:44— `.aksel-link-anchor__overlay .aksel-link-anchor:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement @navikt/core/css/src/tooltip.css:17— `.aksel-tooltip:focus` 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 @navikt/core/css/src/form/combobox.css:182— `.aksel-combobox__input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement @navikt/core/css/src/form/combobox.css:202— `.aksel-combobox__input:focus` 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 @navikt/core/css/src/form/error-summary.css:38— `.aksel-error-summary__heading:focus` 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 @navikt/core/css/src/form/radio-checkbox.css:133— `.aksel-checkbox__input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement @navikt/core/css/src/form/search.css:39— `.aksel-search__input:focus-visible` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
Focus outline removed in CSS without a :focus replacement @navikt/aksel/src/codemod/transforms/v4.0.0/internal-css/tests/complete.input.css:522— `.navds-timeline__popover:focus` 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 @navikt/aksel/src/codemod/transforms/v4.0.0/internal-css/tests/complete.output.css:521— `.navds-timeline__popover:focus` 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.
Boundary violation [package:third-party-deep-import] @navikt/aksel/src/codemod/run-codeshift.ts:4— @navikt/aksel/src/codemod/run-codeshift.ts:4 imports jscodeshift/src/Runner, 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] @navikt/aksel/src/codemod/utils/check.ts:2— @navikt/aksel/src/codemod/utils/check.ts:2 imports jscodeshift/dist/testUtils, 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] @navikt/aksel/src/codemod/v8-tokens/run-tooling.ts:5— @navikt/aksel/src/codemod/v8-tokens/run-tooling.ts:5 imports jscodeshift/src/Runner, 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:relative-cross-package] @navikt/core/tailwind/src/build-v3.ts:3— @navikt/core/tailwind/src/build-v3.ts:3 reaches into another package with a relative path (../../tokens/config/kebabCase) — import the package by name instead.
Boundary violation [package:relative-cross-package] @navikt/core/tailwind/src/build-v3.ts:4— @navikt/core/tailwind/src/build-v3.ts:4 reaches into another package with a relative path (../../tokens/src/tokens/breakpoint) — import the package by name instead.
Boundary violation [package:relative-cross-package] @navikt/core/tailwind/src/build-v4.ts:3— @navikt/core/tailwind/src/build-v4.ts:3 reaches into another package with a relative path (../../tokens/config/kebabCase) — import the package by name instead.
Boundary violation [package:relative-cross-package] @navikt/core/tailwind/src/build-v4.ts:4— @navikt/core/tailwind/src/build-v4.ts:4 reaches into another package with a relative path (../../tokens/src/tokens/breakpoint) — import the package by name instead.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:7— aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:7 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:18— aksel.nav.no/sanity-studio/plugins/publication-flow/actions/lastVerified.tsx:18 imports @navikt/ds-react/List, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/custom-components/LinkRenderer.tsx:5— aksel.nav.no/sanity-studio/schema/custom-components/LinkRenderer.tsx:5 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/custom-components/WriteHelp.tsx:1— aksel.nav.no/sanity-studio/schema/custom-components/WriteHelp.tsx:1 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/custom-components/WriteHelp.tsx:2— aksel.nav.no/sanity-studio/schema/custom-components/WriteHelp.tsx:2 imports @navikt/ds-react/List, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/custom-components/gp/EndringsloggReferanser.tsx:6— aksel.nav.no/sanity-studio/schema/custom-components/gp/EndringsloggReferanser.tsx:6 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/custom-components/gp/InnholdstypeHighlight.tsx:10— aksel.nav.no/sanity-studio/schema/custom-components/gp/InnholdstypeHighlight.tsx:10 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/custom-components/gp/UndertemaHighlight.tsx:10— aksel.nav.no/sanity-studio/schema/custom-components/gp/UndertemaHighlight.tsx:10 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/custom-components/updateInfo.tsx:11— aksel.nav.no/sanity-studio/schema/custom-components/updateInfo.tsx:11 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/documents/komponenter/artikkel.tsx:2— aksel.nav.no/sanity-studio/schema/documents/komponenter/artikkel.tsx:2 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/objects/shared/accordion.tsx:4— aksel.nav.no/sanity-studio/schema/objects/shared/accordion.tsx:4 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Boundary violation [package:undeclared-workspace-dep] aksel.nav.no/sanity-studio/schema/objects/shared/description-list.tsx:4— aksel.nav.no/sanity-studio/schema/objects/shared/description-list.tsx:4 imports @navikt/ds-react, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.
Change coupling: TimelineClickablePeriodInternal.tsx ↔ TimelinePinInternal.tsx @navikt/core/react/src/timeline/period-clickable/TimelineClickablePeriodInternal.tsx:1— `@navikt/core/react/src/timeline/period-clickable/TimelineClickablePeriodInternal.tsx` and `@navikt/core/react/src/timeline/pin/TimelinePinInternal.tsx` change together 88% of the time (15 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 15 shared commits counted here, the most recent 3 are `7acd2a44` [Timeline] Fix Axislabel calculation (#4968) (at that commit the files were still `@navikt/core/react/src/timeline/period/ClickablePeriod.tsx` and `@navikt/core/react/src/timeline/pin/PinInternal.tsx`); `f491aaec` [Timeline] Enhance keyboard navigation, optimize pin interactions, pe… (at that commit the files were still `@navikt/core/react/src/timeline/period/ClickablePeriod.tsx` and `@navikt/core/react/src/timeline/pin/PinInternal.tsx`); `6b64f271` [Timeline] :wheelchair: Improved JAWS support with click-handler for … (at that commit the files were still `@navikt/core/react/src/timeline/period/ClickablePeriod.tsx` and `@navikt/core/react/src/timeline/pin/PinInternal.tsx`) — run `git show` on any of them.
Change coupling: DatePickerRoot.tsx ↔ MonthPickerRoot.tsx @navikt/core/react/src/datepicker/root/DatePickerRoot.tsx:1— `@navikt/core/react/src/datepicker/root/DatePickerRoot.tsx` and `@navikt/core/react/src/monthpicker/root/MonthPickerRoot.tsx` change together 88% of the time (14 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `992a955a` [Datepicker] Ranged logic refactor (#4896) (at that commit the files were still `@navikt/core/react/src/date/datepicker/DatePicker.tsx` and `@navikt/core/react/src/date/monthpicker/MonthPicker.tsx`); `8285d807` Datepicker popover autofocus on open (#4676) (at that commit the files were still `@navikt/core/react/src/date/datepicker/DatePicker.tsx` and `@navikt/core/react/src/date/monthpicker/MonthPicker.tsx`); `90871fef` Refactor exports and JSDoc prop type links in components with sub-com… (at that commit the files were still `@navikt/core/react/src/date/datepicker/DatePicker.tsx` and `@navikt/core/react/src/date/monthpicker/MonthPicker.tsx`) — run `git show` on any of them.
Change coupling: DragAndDropDragHandler.tsx ↔ DragAndDropRoot.tsx @navikt/core/react/src/data/drag-and-drop/drag-handler/DragAndDropDragHandler.tsx:1— `@navikt/core/react/src/data/drag-and-drop/drag-handler/DragAndDropDragHandler.tsx` and `@navikt/core/react/src/data/drag-and-drop/root/DragAndDropRoot.tsx` change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `92fa6410` DataTable: Small cleanup to drag and drop (#4899); `faec2641` DataTable / DND : Improved announcer; `fbfdeba7` DataTable / DND: Better label, handle reset on esc — run `git show` on any of them.
Change coupling: Checkbox.tsx ↔ Radio.tsx @navikt/core/react/src/form/checkbox/Checkbox.tsx:1— `@navikt/core/react/src/form/checkbox/Checkbox.tsx` and `@navikt/core/react/src/form/radio/Radio.tsx` change together 82% of the time (14 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `5ea60690` :bug: Stop className from being fowarded to input-element in radio/ch…; `93465781` [Checkbox, Radio] Inline inputs for use internally in DataTable (#4760); `489fcbb5` Darkside: Avoid empty aria-describedby in Radio and Checkbox (#4111) — run `git show` on any of them.
Change coupling: useDatepicker.tsx ↔ useMonthPicker.tsx @navikt/core/react/src/datepicker/root/useDatepicker.tsx:1— `@navikt/core/react/src/datepicker/root/useDatepicker.tsx` and `@navikt/core/react/src/monthpicker/root/useMonthPicker.tsx` change together 81% of the time (22 of the 27 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 22 shared commits counted here, the most recent 3 are `72a9131a` DatePicker, MonthPicker: Make open button more prominent (#4751) (at that commit the files were still `@navikt/core/react/src/date/datepicker/hooks/useDatepicker.tsx` and `@navikt/core/react/src/date/monthpicker/hooks/useMonthPicker.tsx`); `96a730c7` useDatepicker, useMonthpicker: Add descriptions to validation type (#… (at that commit the files were still `@navikt/core/react/src/date/datepicker/hooks/useDatepicker.tsx` and `@navikt/core/react/src/date/monthpicker/hooks/useMonthPicker.tsx`); `8285d807` Datepicker popover autofocus on open (#4676) (at that commit the files were still `@navikt/core/react/src/date/datepicker/hooks/useDatepicker.tsx` and `@navikt/core/react/src/date/monthpicker/hooks/useMonthPicker.tsx`) — run `git show` on any of them.
Change coupling: REDACTED ↔ Listbox.stories.tsx REDACTED:1— `REDACTED` and `@navikt/core/react/src/utils/components/Listbox/Listbox.stories.tsx` change together 80% of the time (8 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `d8e62db7` fix(Listbox): fix issue where options were not announced by VO in Saf…; `3a1590ab` feat(Listbox): support PageUp and PageDown (#5212); `2dc83067` feat(Listbox): new design + small variant — run `git show` on any of them.
Change coupling: artikkel.tsx ↔ artikkel.tsx aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:1— `aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx` and `aksel.nav.no/sanity-studio/schema/documents/komponenter/artikkel.tsx` change together 77% of the time (10 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `eaa280b9` [Website] Updated header and footer section for ds-pages (#5051) (at that commit the files were still `aksel.nav.no/website/sanity/schema/documents/grunnleggende/artikkel.tsx` and `aksel.nav.no/website/sanity/schema/documents/komponenter/artikkel.tsx`); `ba3ee03d` [Endringslogg] Sanity-structure for new changelog on God praksis (#4945) (at that commit the files were still `aksel.nav.no/website/sanity/schema/documents/grunnleggende/artikkel.tsx` and `aksel.nav.no/website/sanity/schema/documents/komponenter/artikkel.tsx`); `5c25c43e` Redaksjon: cleanup (#4074) (at that commit the files were still `aksel.nav.no/website/sanity/schema/documents/grunnleggende/artikkel.tsx` and `aksel.nav.no/website/sanity/schema/documents/komponenter/artikkel.tsx`) — run `git show` on any of them.
Change coupling: DataTableTd.tsx ↔ DataTableTh.tsx @navikt/core/react/src/data/table/td/DataTableTd.tsx:1— `@navikt/core/react/src/data/table/td/DataTableTd.tsx` and `@navikt/core/react/src/data/table/th/DataTableTh.tsx` change together 69% of the time (9 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `4e49f744` [DataTable] Update Selectionstate to be rendered within tablerows; `9014bf00` [DataTable] Added selection css for testign; `763ed480` [DataTabke] Only add tabIndex when keyboardsupport is enabled — run `git show` on any of them.
Change coupling: List.stories.tsx ↔ ListItem.tsx @navikt/core/react/src/list/List.stories.tsx:1— `@navikt/core/react/src/list/List.stories.tsx` and `@navikt/core/react/src/list/item/ListItem.tsx` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `f2cff91d` refactor: Restructured expansion-card, link-card, list (#5415); `d7e4b494` refactor(core): removed redundant role presentation from icons and sv… (at that commit the file was still `@navikt/core/react/src/list/List.Item.tsx`); `ca1d9be8` List: Add indentation and remove aria attributes (#3184) (at that commit the files were still `@navikt/core/react/src/list/list.stories.tsx` and `@navikt/core/react/src/list/ListItem.tsx`) — run `git show` on any of them.
Change coupling: semantic-role.tokens.ts ↔ semantic-root.tokens.ts @navikt/core/tokens/src/tokens/colors/semantic-role.tokens.ts:1— `@navikt/core/tokens/src/tokens/colors/semantic-role.tokens.ts` and `@navikt/core/tokens/src/tokens/colors/semantic-root.tokens.ts` change together 62% of the time (10 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `83490d47` [Darkside] Soft-pressed token (#3554) (at that commit the files were still `@navikt/core/tokens/darkside/tokens/semantic-roles.ts` and `@navikt/core/tokens/darkside/tokens/semantic.ts`); `281ac2d9` [Darkside] :truck: `-hover` tokens are now `soft-hover` (#3553) (at that commit the files were still `@navikt/core/tokens/darkside/tokens/semantic-roles.ts` and `@navikt/core/tokens/darkside/tokens/semantic.ts`); `ddd04367` [Darkside]: SoftA-token added for use in Table zebra-stripes (at that commit the files were still `@navikt/core/tokens/darkside/tokens/semantic-roles.ts` and `@navikt/core/tokens/darkside/tokens/semantic.ts`) — run `git show` on any of them.
Change coupling: useRangeDatepicker.tsx ↔ useMonthPicker.tsx @navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx:1— `@navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx` and `@navikt/core/react/src/monthpicker/root/useMonthPicker.tsx` change together 61% of the time (17 of the 28 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 17 shared commits counted here, the most recent 3 are `8285d807` Datepicker popover autofocus on open (#4676) (at that commit the files were still `@navikt/core/react/src/date/datepicker/hooks/useRangeDatepicker.tsx` and `@navikt/core/react/src/date/monthpicker/hooks/useMonthPicker.tsx`); `1f4ac7bf` DatePicker/MonthPicker: add support for translations provider (#3390) (at that commit the files were still `@navikt/core/react/src/date/hooks/useRangeDatepicker.tsx` and `@navikt/core/react/src/date/hooks/useMonthPicker.tsx`); `51eee7f0` [Datepicker/Modal] Datepicker bruker nå Modal på mobil og for nested … (at that commit the files were still `@navikt/core/react/src/date/hooks/useRangeDatepicker.tsx` and `@navikt/core/react/src/date/hooks/useMonthPicker.tsx`) — run `git show` on any of them.
Change coupling: AccordionContent.tsx ↔ AccordionHeader.tsx @navikt/core/react/src/accordion/content/AccordionContent.tsx:1— `@navikt/core/react/src/accordion/content/AccordionContent.tsx` and `@navikt/core/react/src/accordion/header/AccordionHeader.tsx` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `875c5fcc` refactor(Accordion): Update structure and import/exports (#5057); `a04ac983` [ExpansionCard] Content defaults to app-color from Theme. (#4075) (at that commit the files were still `@navikt/core/react/src/accordion/AccordionContent.tsx` and `@navikt/core/react/src/accordion/AccordionHeader.tsx`); `561fecbc` [Darkside] Updated `<Theme />` component (#3467) (at that commit the files were still `@navikt/core/react/src/accordion/AccordionContent.tsx` and `@navikt/core/react/src/accordion/AccordionHeader.tsx`) — run `git show` on any of them.
Change coupling: Data.data-prop.stories.tsx ↔ getMultipleSelectProps.ts @navikt/core/react/src/data/stories/Data.data-prop.stories.tsx:1— `@navikt/core/react/src/data/stories/Data.data-prop.stories.tsx` and `@navikt/core/react/src/data/table/helpers/selection/getMultipleSelectProps.ts` change together 53% of the time (9 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `5e43726f` [DataGrid] Update selection API; `cc38262d` [DataGrid] Move isLoading to root, rename loading -> loadingContent; `79fd31c1` [DataTable] rename disableRowSelectionOnClick to selectionTrigger and… — run `git show` on any of them.
Change coupling: Data.kb-nav.stories.tsx ↔ useTableKeyboardNav.ts @navikt/core/react/src/data/stories/Data.kb-nav.stories.tsx:1— `@navikt/core/react/src/data/stories/Data.kb-nav.stories.tsx` and `@navikt/core/react/src/data/table/hooks/useTableKeyboardNav.ts` change together 50% of the time (8 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `1073f5d5` [DataTable] Keyboard-nav now acts like rowing tabindex pattern; `f51ca8e1` [DataTable] Misc CSS-adjustments to header, cells and resize-handle (at that commit the files were still `@navikt/core/react/src/data/stories/Data.focusable.stories.tsx` and `@navikt/core/react/src/data/table/root/useTableKeyboardNav.ts`); `aa977f0c` [DataTable] Extract maxCols from table grid on the fly (at that commit the files were still `@navikt/core/react/src/data/stories/Data.focusable.stories.tsx` and `@navikt/core/react/src/data/table/root/useTableKeyboardNav.ts`) — run `git show` on any of them.
Change coupling: Data.data-prop.stories.tsx ↔ getSingleSelectProps.ts @navikt/core/react/src/data/stories/Data.data-prop.stories.tsx:1— `@navikt/core/react/src/data/stories/Data.data-prop.stories.tsx` and `@navikt/core/react/src/data/table/helpers/selection/getSingleSelectProps.ts` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `5e43726f` [DataGrid] Update selection API; `79fd31c1` [DataTable] rename disableRowSelectionOnClick to selectionTrigger and…; `8028ff69` [DataTable] Refactor getRowId to only accept string, reference TableR… — run `git show` on any of them.
AC2 · Forms & labels· <RadioGroup> field component without a label · ×14
<RadioGroup> field component without a label aksel.nav.no/website/app/(routes)/(root)/personvernerklaering/_ui/ConsentForm.tsx:35— 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 aksel.nav.no/website/pages/eksempler/radio-horizontal/horizontal.tsx:6— 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 aksel.nav.no/website/pages/eksempler/radio/controlled.tsx:9— 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 aksel.nav.no/website/pages/eksempler/radio/description.tsx:8— 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 aksel.nav.no/website/pages/eksempler/radio/disabled.tsx:8— 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 aksel.nav.no/website/pages/eksempler/radio/error.tsx:15— 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 aksel.nav.no/website/pages/eksempler/radio/hide-legend.tsx:8— 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 aksel.nav.no/website/pages/eksempler/radio/medium.tsx:8— 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 aksel.nav.no/website/pages/eksempler/radio/radio-description.tsx:8— 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 aksel.nav.no/website/pages/eksempler/radio/readonly.tsx:8— 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 aksel.nav.no/website/pages/eksempler/radio/small.tsx:8— 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 aksel.nav.no/website/pages/eksempler/readmore/demo.tsx:7— 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 aksel.nav.no/website/pages/templates/skjemavalidering/demo.tsx:102— 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 aksel.nav.no/website/pages/templates/skjemavalidering/react-hook-form.tsx:78— 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· Animation without a prefers-reduced-motion guard · ×10
Animation without a prefers-reduced-motion guard aksel.nav.no/website/app/_ui/animated-arrow/AnimatedArrow.module.css:2— `.animatedArrow` moves (`transition: transform 200ms`) 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 aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:14— `.animated` moves (`animation: rotation 60s ease-in-out infinite,
rainbow-hype 60s ease 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 aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:61— `.animated1` moves (`animation: shape-1 60s ease-in-out infinite,
rainbow-hype 60s ease 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 aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:69— `.animated2` moves (`animation: shape-2 60s ease-in-out infinite,
rainbow-hype 60s ease 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 aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:77— `.animated3` moves (`animation: shape-3 60s ease-in-out infinite,
rainbow-hype 60s ease 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 aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:90— `.animated5` moves (`animation: shape-5 60s ease-in-out infinite,
rainbow-hype 60s ease 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 aksel.nav.no/website/app/_ui/aksel-cube/aksel-cube.module.css:98— `.animated6` moves (`animation: shape-6 60s ease-in-out infinite,
rainbow-hype 60s ease 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 aksel.nav.no/website/app/(routes)/(root)/_ui/frontpage.module.css:207— `.card[data-visible="true"]` moves (`animation: fadeInBottom 1s ease`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard aksel.nav.no/website/app/(routes)/(god-praksis)/_ui/hero/Hero.module.css:8— `.godPraksisHero` moves (`transition: margin 500ms`) 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 aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/sidebar/Sidebar.module.css:112— `.navListNotch::before` moves (`transition: width 120ms ease-out`) 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×10
Async function without AbortSignal: fetchUser aksel.nav.no/website/app/_ui/system-panel/SystemPanel.action.tsx:28— `fetchUser` 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: ImageAsThemedSvg aksel.nav.no/website/app/_ui/image-as-svg/ImageAsSvg.tsx:7— `ImageAsThemedSvg` 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: fetchUser aksel.nav.no/website/app/_ui/footer/Footer.edit.tsx:14— `fetchUser` 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: fetchAllSanityPages aksel.nav.no/website/app/_sanity/live-fetch.ts:17— `fetchAllSanityPages` 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: GodPraksisPictogram aksel.nav.no/website/app/(routes)/(root)/_ui/pictogram/GodPraksisPictogram.tsx:8— `GodPraksisPictogram` 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: DynamicIconPage aksel.nav.no/website/app/(routes)/(designsystemet)/komponenter/ikoner/page.tsx:36— `DynamicIconPage` 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: revalidate aksel.nav.no/sanity-studio/functions/invalidate-tags/index.ts:3— `revalidate` 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: useRemoteConfig @navikt/core/tokens/src/figma/plugin/AkselVariablesInterface.ts:30— `useRemoteConfig` 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: fetchIcons REDACTED:12— `fetchIcons` 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: fetchDownloadUrls REDACTED:57— `fetchDownloadUrls` 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 })`.
Sync-over-async blocking @navikt/aksel/src/codemod/utils/check.ts:31— `fs.readFileSync` in `callback to test` 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 @navikt/aksel/src/codemod/utils/check.ts:32— `fs.readFileSync` in `callback to test` 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 @navikt/aksel/src/codemod/v8-tokens/tasks/print-remaining.ts:190— `clipboardy.writeSync` in `printRemaining` 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 @navikt/core/react/scripts/metadata/component-names.ts:71— `readFileSync` in `writeComponentNames` 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 @navikt/core/react/scripts/metadata/component-names.ts:76— `writeFileSync` in `writeComponentNames` 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 aksel.nav.no/website/scripts/update-examples/parts/filter-code.ts:65— `fs.readFileSync` in `callback to importDeclarations.forEach` 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 aksel.nav.no/website/scripts/update-examples/parts/parse-code-files.ts:35— `fs.readFileSync` in `parseCodeFile` 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.
Off the main sequence: @navikt/aksel — @navikt/aksel: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @navikt/aksel-icons — @navikt/aksel-icons: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 4 project(s), so it's rigid to change.
Off the main sequence: @navikt/ds-css — @navikt/ds-css: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
Off the main sequence: @navikt/ds-tailwind — @navikt/ds-tailwind: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: @navikt/ds-tokens — @navikt/ds-tokens: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: aksel-sanity-studio — aksel-sanity-studio: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Duplicated block (17 lines × 2 locations) @navikt/aksel/src/codemod/transforms/v8.0.0/box/box.ts:50— @navikt/aksel/src/codemod/transforms/v8.0.0/box/box.ts:50 · @navikt/aksel/src/codemod/transforms/v8.0.0/box/box.ts:76 — 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) @navikt/core/react/src/chips/removable/ChipsRemovable.tsx:58— @navikt/core/react/src/chips/removable/ChipsRemovable.tsx:58 · @navikt/core/react/src/chips/toggle/ChipsToggle.tsx:84 — 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) @navikt/core/react/src/data/stories/DataTableProfiler.tsx:142— @navikt/core/react/src/data/stories/DataTableProfiler.tsx:142 · @navikt/core/react/src/data/stories/DataTableProfiler.tsx:161 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 2 locations) aksel.nav.no/sanity-studio/schema/documents/designsystem-forside.tsx:130— aksel.nav.no/sanity-studio/schema/documents/designsystem-forside.tsx:130 · aksel.nav.no/sanity-studio/schema/documents/designsystem-forside.tsx:155 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (17 lines × 2 locations) aksel.nav.no/sanity-studio/structure/article-lists.ts:19— aksel.nav.no/sanity-studio/structure/article-lists.ts:19 · aksel.nav.no/sanity-studio/structure/article-lists.ts:37 — 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.
Dead file (~23 LoC) @navikt/core/react/src/global-alert/GlobalAlert.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~23 LoC) @navikt/core/react/src/info-card/InfoCard.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~23 LoC) @navikt/core/react/src/local-alert/LocalAlert.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~23 LoC) @navikt/core/react/src/monthpicker/MonthPicker.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~23 LoC) aksel.nav.no/sanity-studio/sanity.cli.ts— no import path from any entry point (141 application, 32 tooling, 231 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
Hotspot: @navikt/core/react/src/utils/components/Listbox/root/ListboxRoot.tsx @navikt/core/react/src/utils/components/Listbox/root/ListboxRoot.tsx:27— @navikt/core/react/src/utils/components/Listbox/root/ListboxRoot.tsx changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ListboxRoot.ListboxComponent at line 27. 2 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:34:15 +01:00' --until='2026-11-16 10:34:15 +01:00' --full-history --no-merges -- @navikt/core/react/src/utils/components/Listbox/root/ListboxRoot.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx:100— @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 43 in DismissableLayer.DismissableLayer at line 100. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:34:15 +01:00' --until='2026-11-16 10:34:15 +01:00' --full-history --no-merges -- @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptions.tsx @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptions.tsx:16— @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptions.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in FilteredOptions.FilteredOptions at line 16. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:34:15 +01:00' --until='2026-11-16 10:34:15 +01:00' --full-history --no-merges -- @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptions.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: @navikt/core/react/src/table/animate-height/TableAnimateHeightInternal.tsx @navikt/core/react/src/table/animate-height/TableAnimateHeightInternal.tsx:61— @navikt/core/react/src/table/animate-height/TableAnimateHeightInternal.tsx changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in TableAnimateHeightInternal.TableAnimateHeightInternal at line 61. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:34:15 +01:00' --until='2026-11-16 10:34:15 +01:00' --full-history --no-merges -- @navikt/core/react/src/table/animate-height/TableAnimateHeightInternal.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
R6 · Tooling· Type errors in this package cannot fail any build or CI step · ×4
Type errors in this package cannot fail any build or CI step tooling/analyzer/package.json:20— `tooling/analyzer` is TypeScript, but a type error in it cannot fail anything this repository runs: its `run:analyze-npm-action` script (`yarn clean && concurrently "yarn pack-remote && tsx ./src/runners/analyze-pac…`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. 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.
Type errors in this package cannot fail any build or CI step tooling/scripts/package.json:6— `tooling/scripts` is TypeScript, but a type error in it cannot fail anything this repository runs: its `script:git-release` script (`tsx ./git-release`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. 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.
Type errors in this package cannot fail any build or CI step @navikt/core/tailwind/package.json:17— `@navikt/core/tailwind` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build` script (`yarn tsx ./src/build-v3.ts && yarn tsx ./src/build-v4.ts`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. 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.
Type errors in this package cannot fail any build or CI step @navikt/core/tokens/package.json:20— `@navikt/core/tokens` is TypeScript, but a type error in it cannot fail anything this repository runs: its `build` script (`tsx ./src && yarn build:figma-config && yarn build:plugin && tsx ./config/ver…`) compiles TypeScript with a transpile-only tool that strips types without checking them, and no script, config or CI step of the package runs `tsc --noEmit` or another type checker over it. 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.
Deprecated: prom-client apps/mcp-server/package.json:31— prom-client 15.1.3, declared in apps/mcp-server/package.json, is marked deprecated by its publisher: "prom-client has been replaced by @prometheus-io/client". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @svitejs/changesets-changelog-github-compact REDACTED:85— @svitejs/changesets-changelog-github-compact 1.2.0, declared in REDACTED, is marked deprecated by its publisher: "unmaintained". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:95— eslint 9.39.5, 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.
IC1 · Incompleteness & stubs· Markup wires an event to an empty handler · ×3
Markup wires an event to an empty handler aksel.nav.no/website/pages/eksempler/dropdown/demo.tsx:15— `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.
Markup wires an event to an empty handler aksel.nav.no/website/pages/eksempler/table-menu/demo.tsx:35— `onSelect` is wired to an arrow whose body is empty — the markup attaches a listener that does nothing. Implement the handler, or remove the attribute that wires it.
Markup wires an event to an empty handler aksel.nav.no/website/pages/eksempler/table-menu/demo.tsx:38— `onSelect` 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.
Duplicated block (24 lines × 2 locations) @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:185— @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:185 · @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:218 — 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 (24 lines × 2 locations) @navikt/aksel/src/codemod/v8-tokens/transforms/v8-tokens-less.ts:13— @navikt/aksel/src/codemod/v8-tokens/transforms/v8-tokens-less.ts:13 · @navikt/aksel/src/codemod/v8-tokens/transforms/v8-tokens-scss.ts:13 — 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 (24 lines × 2 locations) @navikt/core/tailwind/src/build-v3.ts:6— @navikt/core/tailwind/src/build-v3.ts:6 · @navikt/core/tailwind/src/build-v4.ts:6 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of MODULE-LEVEL DECLARATIONS — bindings the module declares and exports — rather than statements with a call site. Do not read this as an extract-a-helper row: a call expression cannot stand where a declaration was, and putting one there would delete the names themselves, which are what the rest of the codebase imports. What actually repeats here is the INITIALISER — the same expression shape written once per binding. So give that expression one name (a small helper the initialisers call, or a shared base value they are each derived from) and keep every binding under the name it already has. Where the run is an enumeration — one binding per distinct thing, differing precisely in the thing each one names — the repetition IS the enumeration and collapsing it would delete entries; consider instead whether the set belongs in one exported table the individual names are read out of. Reported because the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2 locations) REDACTED:312— REDACTED:312 · REDACTED:332 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (18 lines × 2 locations) @navikt/core/react/src/action-menu/checkbox-item/ActionMenuCheckboxItem.tsx:43— @navikt/core/react/src/action-menu/checkbox-item/ActionMenuCheckboxItem.tsx:43 · @navikt/core/react/src/action-menu/radio-item/ActionMenuRadioItem.tsx:30 — 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.
Duplicated block (18 lines × 2 locations) tooling/analyzer/src/md-message.ts:61— tooling/analyzer/src/md-message.ts:61 · tooling/analyzer/src/md-message.ts:86 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 3 locations) @navikt/core/react/src/chips/removable/ChipsRemovable.tsx:58— @navikt/core/react/src/chips/removable/ChipsRemovable.tsx:58 · @navikt/core/react/src/chips/toggle/ChipsToggle.tsx:84 · @navikt/core/react/src/toggle-group/root/ToggleGroupRoot.tsx:85 — 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.
Duplicated block (17 lines × 3 locations) @navikt/core/react/src/form/search/Search.tsx:248— @navikt/core/react/src/form/search/Search.tsx:248 · @navikt/core/react/src/form/select/Select.tsx:142 · @navikt/core/react/src/utils/components/date/input/DateInput.tsx:186 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (17 lines × 3 locations) @navikt/core/react/src/form/select/Select.tsx:144— @navikt/core/react/src/form/select/Select.tsx:144 · @navikt/core/react/src/form/textarea/Textarea.tsx:178 · @navikt/core/react/src/form/textfield/TextField.tsx:122 — 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.
Dead file (~77 LoC) @navikt/core/tokens/src/figma/index.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~77 LoC) aksel.nav.no/sanity-studio/functions/invalidate-tags/index.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~77 LoC) aksel.nav.no/sanity-studio/sanity.blueprint.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~20 LoC) @navikt/core/react/src/accordion/Accordion.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~20 LoC) @navikt/core/react/src/data/table/caption/DataTableCaption.tsx— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~20 LoC) @navikt/core/react/src/form/form-progress/FormProgress.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 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
Swallowed exception (empty catch) tooling/analyzer/src/helpers/bundle-size.ts:61— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:524— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:536— 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.
AC4 · Keyboard semantics· Modal dialog does not manage focus · ×2
Modal dialog does not manage focus @navikt/core/react/src/timeline/period-clickable/TimelineClickablePeriodInternal.tsx:145— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
Modal dialog does not manage focus @navikt/core/react/src/timeline/pin/TimelinePinInternal.tsx:111— This <div role="dialog"> is a modal dialog, but focus is moved into it, but nothing keeps it there: Tab walks out to the page behind, so a keyboard or screen-reader user keeps acting on the content behind it (WCAG 2.4.3). Use a native <dialog> opened with showModal(), a dialog component that traps focus, or move focus to the dialog on open, trap Tab inside it (or make the page behind inert) and return focus to the control that opened it on close.
className.toVal (cognitive 27) @navikt/core/react/src/utils/helpers/className.ts:13— className.toVal has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
className.toVal (cognitive 27) aksel.nav.no/website/app/_ui/utils/className.ts:13— className.toVal has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (6 pts), boolean chains 3 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
Change coupling clique: Bleed.tsx, HGrid.tsx, Stack.tsx @navikt/core/react/src/primitives/bleed/Bleed.tsx— 3 files — `@navikt/core/react/src/primitives/bleed/Bleed.tsx`, `@navikt/core/react/src/primitives/grid/HGrid.tsx`, `@navikt/core/react/src/primitives/stack/Stack.tsx` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Change coupling clique: Select.tsx, Textarea.tsx, TextField.tsx @navikt/core/react/src/form/select/Select.tsx— 3 files — `@navikt/core/react/src/form/select/Select.tsx`, `@navikt/core/react/src/form/textarea/Textarea.tsx`, `@navikt/core/react/src/form/textfield/TextField.tsx` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Fake-async — async method never awaits @navikt/aksel-icons/config/zip.js:16— `generateFile` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits aksel.nav.no/website/app/_ui/footer/Footer.tsx:11— `CopyrightYear` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Duplicated block (16 lines × 2 locations) @navikt/aksel-stylelint/src/rules/aksel-design-token-no-global-override/index.ts:21— @navikt/aksel-stylelint/src/rules/aksel-design-token-no-global-override/index.ts:21 · @navikt/aksel-stylelint/src/rules/aksel-no-internal-tokens/index.ts:46 — 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 (16 lines × 2 locations) @navikt/aksel/src/codemod/transforms/v8.0.0/box-new/box-new.ts:17— @navikt/aksel/src/codemod/transforms/v8.0.0/box-new/box-new.ts:17 · @navikt/aksel/src/codemod/transforms/v8.0.0/box-new/box-new.ts:36 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Complex function (anonymous) (cyclomatic 15, cognitive 22) @navikt/core/react/src/monthpicker/root/MonthPicker.util.ts:164— (anonymous) has cyclomatic complexity 15 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 15, cognitive 22) @navikt/core/react/src/timeline/root/TimelineKeyboardNavProvider.tsx:143— (anonymous) has cyclomatic complexity 15 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 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.
Dead file (~39 LoC) @navikt/aksel-icons/util/useId.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~39 LoC) @navikt/core/react/src/action-menu/ActionMenu.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~31 LoC) @navikt/core/react/src/dialog/Dialog.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~31 LoC) @navikt/core/react/src/dropdown/Dropdown.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~29 LoC) @navikt/core/react/src/expansion-card/ExpansionCard.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~29 LoC) @navikt/core/react/src/table/Table.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~26 LoC) @navikt/core/react/src/form/file-upload/FileUpload.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~26 LoC) @navikt/core/react/src/typography/Typography.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~24 LoC) @navikt/core/react/src/data/table/tfoot/DataTableTfoot.tsx— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~24 LoC) @navikt/core/react/src/data/table/th/DataTableTh.tsx— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~19 LoC) @navikt/core/react/src/form/error-summary/ErrorSummary.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~19 LoC) @navikt/core/react/src/legacy/confirmation-panel/ConfirmationPanel.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~16 LoC) @navikt/core/react/src/modal/Modal.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~16 LoC) @navikt/core/react/src/tabs/Tabs.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~15 LoC) @navikt/core/react/src/chips/Chips.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~15 LoC) @navikt/core/react/src/collapsible/Collapsible.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 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
AC2 · Forms & labels· <DatePicker> field component without a label · ×1
<DatePicker> field component without a label aksel.nav.no/website/pages/eksempler/datepicker/anchor.tsx:11— This UI-library field component has no label / aria-label / aria-labelledby / id, and nothing written inside it here carries one either (a name prop is the form-submission key, not a label; an id alone, wherever it is set, names nothing until a label points at it). The text inside it does not stand in for one: these compound APIs render a trigger with role="combobox" (or role="button"), and those roles take their name from the AUTHOR, not from their content — so the words on screen never reach the accessibility tree as a name. Name it whichever way this library supports: a label prop, an aria-label, or an id on the rendered control with a <label htmlFor> pointing at it. For a group of controls, name the group itself (aria-label, or a fieldset with a legend) — labelling each item leaves the set unnamed.
AC3 · Page structure· Text directly inside a table row · ×1
Text directly inside a table row @navikt/core/react/src/data/table/tr/DataTableTr.tsx:122— A <tr> may hold only <td>/<th> cells. Text or a value written between the cells is moved out of the table by the browser, so it is read detached from its row. Wrap it in a <td>.
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark aksel.nav.no/website/app/global-error.tsx:23— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
FocusBoundary.FocusBoundary (cyclomatic 55) @navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx:78— FocusBoundary.FocusBoundary has cyclomatic complexity 55 (threshold 15). Most of this is not in the body itself: 1 of the 55 points is its own statement and the rest belongs to 13 function literals inside it that branch (lines 328, 232, 279, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Input.Input (cyclomatic 54) @navikt/core/react/src/legacy/combobox/Input/Input.tsx:35— Input.Input has cyclomatic complexity 54 (threshold 15). Most of this is not in the body itself: 3 of the 54 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 159, a function literal at line 75, a function literal at line 258, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
list.transformer (cyclomatic 53) @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:31— list.transformer has cyclomatic complexity 53 (threshold 15). Most of this is not in the body itself: 5 of the 53 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 94, 52, 143, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DismissableLayer.DismissableLayer (cyclomatic 43) @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx:100— DismissableLayer.DismissableLayer has cyclomatic complexity 43 (threshold 15). Most of this is not in the body itself: 6 of the 43 points are its own statements and the rest belongs to 11 function items inside it that branch (handleOutsideEvent, a function literal at line 215, a function literal at line 391, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TimelineKeyboardNavProvider.TimelineKeyboardNavProvider (cyclomatic 38) @navikt/core/react/src/timeline/root/TimelineKeyboardNavProvider.tsx:37— TimelineKeyboardNavProvider.TimelineKeyboardNavProvider has cyclomatic complexity 38 (threshold 15). Most of this is not in the body itself: 1 of the 38 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 51, 143). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
status.getStatus (cyclomatic 37) REDACTED:15— status.getStatus has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 62, 76). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ModalRoot.ModalRoot (cyclomatic 37) @navikt/core/react/src/modal/root/ModalRoot.tsx:26— ModalRoot.ModalRoot has cyclomatic complexity 37 (threshold 15). Of this number, 17 points are the body's own statements and 20 belong to 5 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DragAndDropRoot.DragAndDropInner (cyclomatic 35) @navikt/core/react/src/data/drag-and-drop/root/DragAndDropRoot.tsx:37— DragAndDropRoot.DragAndDropInner has cyclomatic complexity 35 (threshold 15). Most of this is not in the body itself: 5 of the 35 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 188, a function literal at line 129, a function literal at line 250, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
create-alpha.getAlphaColor (cyclomatic 34) @navikt/core/tokens/src/tokens/colors/create-alpha.ts:87— create-alpha.getAlphaColor has cyclomatic complexity 34 (threshold 15). Of this number, 32 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
box-new.transformer (cyclomatic 30) @navikt/aksel/src/codemod/transforms/v8.0.0/box-new/box-new.ts:5— box-new.transformer has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 2 of the 30 points are its own statements and the rest belongs to 8 function literals inside it that branch (lines 63, 20, 38, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FilteredOptions.FilteredOptions (cyclomatic 29) @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptions.tsx:16— FilteredOptions.FilteredOptions has cyclomatic complexity 29 (threshold 15). Of this number, 24 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DataTableTr.RowSelectionCell (cyclomatic 28) @navikt/core/react/src/data/table/tr/DataTableTr.tsx:289— DataTableTr.RowSelectionCell has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Floating.FloatingContent (cyclomatic 27) @navikt/core/react/src/utils/components/floating/Floating.tsx:273— Floating.FloatingContent has cyclomatic complexity 27 (threshold 15). Of this number, 22 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
md-message.markdownMessage (cyclomatic 27) tooling/analyzer/src/md-message.ts:7— md-message.markdownMessage has cyclomatic complexity 27 (threshold 15). Of this number, 24 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.
createMainChangelog.parseMarkdownFiles (cyclomatic 27) tooling/changelog/createMainChangelog.ts:77— createMainChangelog.parseMarkdownFiles has cyclomatic complexity 27 (threshold 15). Most of this is not in the body itself: 2 of the 27 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 141, 89, 125, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DataTableTr.RowExpansionCell (cyclomatic 26) @navikt/core/react/src/data/table/tr/DataTableTr.tsx:148— DataTableTr.RowExpansionCell has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TextareaAutoSize.TextareaAutosize (cyclomatic 26) @navikt/core/react/src/utils/components/textarea-autosize/TextareaAutoSize.tsx:62— TextareaAutoSize.TextareaAutosize has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 6 of the 26 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 83, a function literal at line 182, syncHeight, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
MonthPicker.util.nextEnabled (cyclomatic 26) @navikt/core/react/src/monthpicker/root/MonthPicker.util.ts:5— MonthPicker.util.nextEnabled has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
page.DynamicTemaPage (cyclomatic 26) aksel.nav.no/website/app/(routes)/(god-praksis)/god-praksis/[tema]/page.tsx:139— page.DynamicTemaPage has cyclomatic complexity 26 (threshold 15). Of this number, 23 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, 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.
useTableKeyboardNav.useTableKeyboardNav (cyclomatic 25) @navikt/core/react/src/data/table/hooks/useTableKeyboardNav.ts:23— useTableKeyboardNav.useTableKeyboardNav has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 34, 124, 104, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
filteredOptionsContext.FilteredOptionsProvider (cyclomatic 25) @navikt/core/react/src/legacy/combobox/FilteredOptions/filteredOptionsContext.tsx:53— filteredOptionsContext.FilteredOptionsProvider has cyclomatic complexity 25 (threshold 15). Most of this is not in the body itself: 1 of the 25 points is its own statement and the rest belongs to 9 function literals inside it that branch (lines 188, 132, 161, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
useTransitionStatus.useTransitionStatus (cyclomatic 23) @navikt/core/react/src/utils/hooks/useTransitionStatus.ts:39— useTransitionStatus.useTransitionStatus has cyclomatic complexity 23 (threshold 15). Of this number, 12 points are the body's own statements and 11 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
pagination.transformer (cyclomatic 22) @navikt/aksel/src/codemod/transforms/v1.0.0/pagination/pagination.ts:11— pagination.transformer has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 77, a function literal at line 54, a function literal at line 20, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
tabs.transformer (cyclomatic 22) @navikt/aksel/src/codemod/transforms/v1.0.0/tabs/tabs.ts:5— tabs.transformer has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 2 of the 22 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 39, 57, 17, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
move-variant-to-data-color.moveVariantToDataColor (cyclomatic 22) @navikt/aksel/src/codemod/utils/move-variant-to-data-color.ts:16— move-variant-to-data-color.moveVariantToDataColor has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 4 of the 22 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 68, 76, 42, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
box.transformer (cyclomatic 22) @navikt/aksel/src/codemod/transforms/v8.0.0/box/box.ts:9— box.transformer has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 44, 96, 107). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DataTableTr.DataTableTr (cyclomatic 21) @navikt/core/react/src/data/table/tr/DataTableTr.tsx:43— DataTableTr.DataTableTr has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 10 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 69). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
useTableColumnResize.useTableColumnResize (cyclomatic 20) @navikt/core/react/src/data/table/column-header/useTableColumnResize.ts:108— useTableColumnResize.useTableColumnResize has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 171, 213, 143, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
token-utils.sortTokens (cyclomatic 20) aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/styling/design-tokens/_ui/token-utils.tsx:3— token-utils.sortTokens has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
TokenFilter.TokenFilter (cyclomatic 19) @navikt/core/react/src/data/token-filter/TokenFilter.tsx:47— TokenFilter.TokenFilter has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 1 of the 19 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 77, 137, 198, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
pick-range-selection.pickRangeSelection (cyclomatic 19) @navikt/core/react/src/utils/date/pick-range-selection.ts:14— pick-range-selection.pickRangeSelection has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DatePickerRDPInternal.ReactDayPicker (cyclomatic 19) @navikt/core/react/src/datepicker/rdp/DatePickerRDPInternal.tsx:59— DatePickerRDPInternal.ReactDayPicker has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 3 of the 19 points are its own statements and the rest belongs to 6 function literals inside it that branch (lines 173, 165, 89, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TableAnimateHeightInternal.TableAnimateHeightInternal (cyclomatic 19) @navikt/core/react/src/table/animate-height/TableAnimateHeightInternal.tsx:61— TableAnimateHeightInternal.TableAnimateHeightInternal has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 9 of the 19 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 120, 101, 193). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
ShowMore.ShowMore (cyclomatic 19) aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/_ui/ShowMore.tsx:122— ShowMore.ShowMore has cyclomatic complexity 19 (threshold 15). Most of this is not in the body itself: 4 of the 19 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 166, 144). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
useScrollLock.preventScrollStandard (cyclomatic 18) @navikt/core/react/src/utils/hooks/useScrollLock.ts:78— useScrollLock.preventScrollStandard has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 3 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (lockScroll, handleResize). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Button.Button (cyclomatic 18) @navikt/core/react/src/button/Button.tsx:71— Button.Button has cyclomatic complexity 18 (threshold 15). Of this number, 15 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DragAndDropDragHandler.DragAndDropDragHandler (cyclomatic 17) @navikt/core/react/src/data/drag-and-drop/drag-handler/DragAndDropDragHandler.tsx:26— DragAndDropDragHandler.DragAndDropDragHandler has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 85, 67, 72, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SearchForm.SearchForm (cyclomatic 17) aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/_ui/SearchForm.tsx:19— SearchForm.SearchForm has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 6 of the 17 points are its own statements and the rest belongs to 5 function items inside it that branch (updateSearchParam, handleSemverToggle, handleYearSelection, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
page.DynamicEndringslogg (cyclomatic 17) aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/page.tsx:73— page.DynamicEndringslogg has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
jsx-value.getJSXLiteralValue (cyclomatic 16) @navikt/aksel/src/codemod/utils/jsx-value.ts:27— jsx-value.getJSXLiteralValue has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useFormField.useFormField (cyclomatic 16) @navikt/core/react/src/form/useFormField.ts:60— useFormField.useFormField has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
DataGridTableRoot.DataTableTBodyContent (cyclomatic 16) @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:434— DataGridTableRoot.DataTableTBodyContent has cyclomatic complexity 16 (threshold 15). Of this number, 10 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ListboxRoot.ListboxComponent (cyclomatic 16) @navikt/core/react/src/utils/components/Listbox/root/ListboxRoot.tsx:27— ListboxRoot.ListboxComponent has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 3 function items inside it that branch (a function literal at line 49, a function literal at line 75, virtuallyFocusOption). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
Tooltip.Tooltip (cyclomatic 16) @navikt/core/react/src/tooltip/Tooltip.tsx:113— Tooltip.Tooltip has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
useRangeDatepicker.toValidation (cyclomatic 16) @navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx:147— useRangeDatepicker.toValidation has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Sidebar.nav.DesignsystemSidebarNav (cyclomatic 16) aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/sidebar/Sidebar.nav.tsx:20— Sidebar.nav.DesignsystemSidebarNav has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 28, 95, 111). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
HighlightedArticle.Highlight (cyclomatic 16) aksel.nav.no/website/app/(routes)/(root)/_ui/HighlightedArticle.tsx:27— HighlightedArticle.Highlight has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
sorting.Example (cyclomatic 16) aksel.nav.no/website/pages/eksempler/data-grid/sorting.tsx:9— sorting.Example has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 1 of the 16 points is its own statement and the rest belongs to 2 function items inside it that branch (a function literal at line 24, handleSortOrderChange). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
create.Program (cyclomatic 16) tooling/eslint/args-check.js:15— create.Program has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Repeated repair: aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/DesignsystemetPageFooter.tsx aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/DesignsystemetPageFooter.tsx:13— aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/DesignsystemetPageFooter.tsx changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is DesignsystemetPageFooter.DesignsystemetPageFooter at line 13), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(website): Forvalter-field now has updated spacing”; “refactor(apps): Handle links better for bug-reports from website”; “fix(apps): Forvalter text now a heading”; “fix(apps): Reduce gap to endringslogg-table”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 10:34:15 +01:00' --until='2026-11-16 10:34:15 +01:00' --full-history --no-merges -- aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/DesignsystemetPageFooter.tsx`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
HackComment @navikt/aksel/src/codemod/run-version-migration.ts:84— // Hack: 'v8-tokens' needs to run last because it's interactive — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
list.transformer (cognitive 78) @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:31— list.transformer has cognitive complexity 78 (threshold 15). Drivers by points: if/else 37 (60 pts), boolean chains 18 (nesting depth added 23). Most of this is not in the body itself: 9 of the 78 points are its own statements and the rest belongs to 10 function literals inside it that branch (lines 94, 52, 143, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
status.getStatus (cognitive 78) REDACTED:15— status.getStatus has cognitive complexity 78 (threshold 15). Drivers by points: if/else 19 (42 pts), loops 15 (31 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 42). Most of this is not in the body itself: 2 of the 78 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 62, 76). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Input.Input (cognitive 72) @navikt/core/react/src/legacy/combobox/Input/Input.tsx:35— Input.Input has cognitive complexity 72 (threshold 15). Drivers by points: if/else 36 (54 pts), boolean chains 15, ternaries 2, match/switch 1 (nesting depth added 18). Most of this is not in the body itself: 2 of the 72 points are its own statements and the rest belongs to 5 function items inside it that branch (a function literal at line 159, a function literal at line 75, a function literal at line 258, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
FocusBoundary.FocusBoundary (cognitive 62) @navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx:78— FocusBoundary.FocusBoundary has cognitive complexity 62 (threshold 15). Drivers by points: if/else 29 (37 pts), boolean chains 21, ternaries 3 (4 pts) (nesting depth added 9). None of this is in the body itself: all 62 points belong to 13 function literals inside it that branch (lines 328, 232, 279, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
box.transformer (cognitive 57) @navikt/aksel/src/codemod/transforms/v8.0.0/box/box.ts:9— box.transformer has cognitive complexity 57 (threshold 15). Drivers by points: if/else 19 (51 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 34). Most of this is not in the body itself: 8 of the 57 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 44, 96, 107). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
TimelineKeyboardNavProvider.TimelineKeyboardNavProvider (cognitive 57) @navikt/core/react/src/timeline/root/TimelineKeyboardNavProvider.tsx:37— TimelineKeyboardNavProvider.TimelineKeyboardNavProvider has cognitive complexity 57 (threshold 15). Drivers by points: if/else 24 (39 pts), boolean chains 9, ternaries 4 (9 pts) (nesting depth added 20). None of this is in the body itself: all 57 points belong to 2 function literals inside it that branch (lines 51, 143). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
createMainChangelog.parseMarkdownFiles (cognitive 49) tooling/changelog/createMainChangelog.ts:77— createMainChangelog.parseMarkdownFiles has cognitive complexity 49 (threshold 15). Drivers by points: if/else 15 (37 pts), boolean chains 11, loops 1 (nesting depth added 22). Most of this is not in the body itself: 1 of the 49 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 141, 89, 125, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DismissableLayer.DismissableLayer (cognitive 42) @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx:100— DismissableLayer.DismissableLayer has cognitive complexity 42 (threshold 15). Drivers by points: if/else 21 (22 pts), boolean chains 15, ternaries 4 (5 pts) (nesting depth added 2). Most of this is not in the body itself: 6 of the 42 points are its own statements and the rest belongs to 11 function items inside it that branch (handleOutsideEvent, a function literal at line 215, a function literal at line 335, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
tabs.transformer (cognitive 39) @navikt/aksel/src/codemod/transforms/v1.0.0/tabs/tabs.ts:5— tabs.transformer has cognitive complexity 39 (threshold 15). Drivers by points: if/else 11 (34 pts), boolean chains 5 (nesting depth added 23). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 39, 66, 57, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
box-new.transformer (cognitive 39) @navikt/aksel/src/codemod/transforms/v8.0.0/box-new/box-new.ts:5— box-new.transformer has cognitive complexity 39 (threshold 15). Drivers by points: if/else 13 (27 pts), boolean chains 12 (nesting depth added 14). Most of this is not in the body itself: 1 of the 39 points is its own statement and the rest belongs to 8 function literals inside it that branch (lines 63, 20, 38, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
move-variant-to-data-color.moveVariantToDataColor (cognitive 37) @navikt/aksel/src/codemod/utils/move-variant-to-data-color.ts:16— move-variant-to-data-color.moveVariantToDataColor has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (31 pts), boolean chains 5, ternaries 1 (nesting depth added 14). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 68, 76, 42, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DataTableTr.RowSelectionCell (cognitive 36) @navikt/core/react/src/data/table/tr/DataTableTr.tsx:289— DataTableTr.RowSelectionCell has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 6 (13 pts), boolean chains 12, if/else 9 (11 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MonthPicker.util.nextEnabled (cognitive 35) @navikt/core/react/src/monthpicker/root/MonthPicker.util.ts:5— MonthPicker.util.nextEnabled has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 7 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataTableTr.RowExpansionCell (cognitive 34) @navikt/core/react/src/data/table/tr/DataTableTr.tsx:148— DataTableTr.RowExpansionCell has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 10 (18 pts), boolean chains 8, if/else 7 (8 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModalRoot.ModalRoot (cognitive 34) @navikt/core/react/src/modal/root/ModalRoot.tsx:26— ModalRoot.ModalRoot has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 16, if/else 12 (14 pts), ternaries 4 (nesting depth added 2). Of this number, 16 points are the body's own statements and 18 belong to 5 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
md-message.markdownMessage (cognitive 34) tooling/analyzer/src/md-message.ts:7— md-message.markdownMessage has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 9, ternaries 4 (8 pts), loops 3 (6 pts) (nesting depth added 9). Of this number, 31 points are the body's own statements and 3 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.
DragAndDropRoot.DragAndDropInner (cognitive 33) @navikt/core/react/src/data/drag-and-drop/root/DragAndDropRoot.tsx:37— DragAndDropRoot.DragAndDropInner has cognitive complexity 33 (threshold 15). Drivers by points: if/else 18 (21 pts), boolean chains 11, ternaries 1 (nesting depth added 3). Most of this is not in the body itself: 2 of the 33 points are its own statements and the rest belongs to 10 function items inside it that branch (a function literal at line 188, a function literal at line 129, a function literal at line 250, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
page.DynamicTemaPage (cognitive 33) aksel.nav.no/website/app/(routes)/(god-praksis)/god-praksis/[tema]/page.tsx:139— page.DynamicTemaPage has cognitive complexity 33 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 9, ternaries 5 (8 pts), loops 2 (nesting depth added 10). Of this number, 30 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sorting.Example (cognitive 32) aksel.nav.no/website/pages/eksempler/data-grid/sorting.tsx:9— sorting.Example has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 3 (12 pts), boolean chains 3, loops 1 (nesting depth added 17). None of this is in the body itself: all 32 points belong to 2 function items inside it that branch (a function literal at line 24, handleSortOrderChange). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
create-alpha.getAlphaColor (cognitive 29) @navikt/core/tokens/src/tokens/colors/create-alpha.ts:87— create-alpha.getAlphaColor has cognitive complexity 29 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 8, ternaries 2 (nesting depth added 6). Of this number, 27 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DataTableTr.DataTableTr (cognitive 28) @navikt/core/react/src/data/table/tr/DataTableTr.tsx:43— DataTableTr.DataTableTr has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 10, ternaries 1 (nesting depth added 9). Most of this is not in the body itself: 8 of the 28 points are its own statements and the rest belongs to one function literal inside it that branches (line 69). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
design-tokens.markdown (cognitive 28) aksel.nav.no/website/app/api/markdown/routes/design-tokens.ts:6— design-tokens.markdown has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (23 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 17). Of this number, 14 points are the body's own statements and 14 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
analyze-react.analyzeReact (cognitive 28) tooling/analyzer/src/analyze-react.ts:25— analyze-react.analyzeReact has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 2 (3 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
create.Program (cognitive 27) tooling/eslint/args-check.js:15— create.Program has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (21 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 14). Of this number, 23 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
spacing.transformer (cognitive 26) @navikt/aksel/src/codemod/transforms/v8.0.0/primitives-spacing/spacing.ts:10— spacing.transformer has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 16). Most of this is not in the body itself: 3 of the 26 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 56, 74, 54). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
MetadataSeksjon.md.propsSeksjonMarkdown (cognitive 26) aksel.nav.no/website/app/api/markdown/blocks/MetadataSeksjon.md.tsx:25— MetadataSeksjon.md.propsSeksjonMarkdown has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 4 (8 pts), boolean chains 1, loops 1 (nesting depth added 12). Of this number, 18 points are the body's own statements and 8 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.
useTableColumnResize.useTableColumnResize (cognitive 25) @navikt/core/react/src/data/table/column-header/useTableColumnResize.ts:108— useTableColumnResize.useTableColumnResize has cognitive complexity 25 (threshold 15). Drivers by points: if/else 15 (18 pts), ternaries 3 (6 pts), boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 2 of the 25 points are its own statements and the rest belongs to 5 function literals inside it that branch (lines 171, 213, 143, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
pick-range-selection.pickRangeSelection (cognitive 25) @navikt/core/react/src/utils/date/pick-range-selection.ts:14— pick-range-selection.pickRangeSelection has cognitive complexity 25 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
in-sync-versions.validateVersions (cognitive 25) tooling/scripts/in-sync-versions.mts:27— in-sync-versions.validateVersions has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 6 (11 pts), boolean chains 1 (nesting depth added 11). Of this number, 23 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Floating.FloatingContent (cognitive 24) @navikt/core/react/src/utils/components/floating/Floating.tsx:273— Floating.FloatingContent has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 12, ternaries 10, if/else 2. Of this number, 19 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
table-grid-nav.buildTableGridMap (cognitive 24) @navikt/core/react/src/data/table/helpers/table-grid-nav.ts:6— table-grid-nav.buildTableGridMap has cognitive complexity 24 (threshold 15). Drivers by points: loops 5 (13 pts), if/else 3 (9 pts), boolean chains 2 (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
useTableKeyboardNav.useTableKeyboardNav (cognitive 24) @navikt/core/react/src/data/table/hooks/useTableKeyboardNav.ts:23— useTableKeyboardNav.useTableKeyboardNav has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 5, match/switch 1, ternaries 1 (nesting depth added 4). Most of this is not in the body itself: 1 of the 24 points is its own statement and the rest belongs to 4 function literals inside it that branch (lines 34, 124, 104, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
chat.transformer (cognitive 23) @navikt/aksel/src/codemod/transforms/v1.0.0/chat/chat.ts:5— chat.transformer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3 (nesting depth added 9). Most of this is not in the body itself: 1 of the 23 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 16, 63, 48). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
filteredOptionsContext.FilteredOptionsProvider (cognitive 23) @navikt/core/react/src/legacy/combobox/FilteredOptions/filteredOptionsContext.tsx:53— filteredOptionsContext.FilteredOptionsProvider has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 12, if/else 9 (10 pts), ternaries 1 (nesting depth added 1). None of this is in the body itself: all 23 points belong to 9 function literals inside it that branch (lines 188, 132, 161, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
page.DynamicEndringslogg (cognitive 23) aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/page.tsx:73— page.DynamicEndringslogg has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 8 (13 pts), boolean chains 6, if/else 4 (nesting depth added 5). Of this number, 18 points are the body's own statements and 5 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
copybutton.transformer (cognitive 22) @navikt/aksel/src/codemod/transforms/v3.0.0/copybutton/copybutton.ts:7— copybutton.transformer has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 4, error handling 1 (nesting depth added 8). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 42, 80). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
parse-date.parseDate (cognitive 22) @navikt/core/react/src/utils/date/parse-date.ts:29— parse-date.parseDate has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (5 pts), boolean chains 3, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TextareaAutoSize.TextareaAutosize (cognitive 22) @navikt/core/react/src/utils/components/textarea-autosize/TextareaAutoSize.tsx:62— TextareaAutoSize.TextareaAutosize has cognitive complexity 22 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 3, ternaries 2 (nesting depth added 1). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 83, a function literal at line 182, syncHeight, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
TableAnimateHeightInternal.TableAnimateHeightInternal (cognitive 22) @navikt/core/react/src/table/animate-height/TableAnimateHeightInternal.tsx:61— TableAnimateHeightInternal.TableAnimateHeightInternal has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (19 pts), ternaries 2, boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 120, 101, 193). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
Sidebar.nav.DesignsystemSidebarNav (cognitive 22) aksel.nav.no/website/app/(routes)/(designsystemet)/_ui/sidebar/Sidebar.nav.tsx:20— Sidebar.nav.DesignsystemSidebarNav has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 3 (6 pts), ternaries 4, boolean chains 2 (nesting depth added 8). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 28, 95, 111). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
token-utils.sortTokens (cognitive 21) aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/styling/design-tokens/_ui/token-utils.tsx:3— token-utils.sortTokens has cognitive complexity 21 (threshold 15). Drivers by points: boolean chains 9, if/else 4 (9 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
dialog-polyfill.dialogPolyfill.isInlinePositionSetByStylesheet (cognitive 20) @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:517— dialog-polyfill.dialogPolyfill.isInlinePositionSetByStylesheet has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 2 (5 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MonthPicker.util.searchEnabledMonth (cognitive 20) @navikt/core/react/src/monthpicker/root/MonthPicker.util.ts:154— MonthPicker.util.searchEnabledMonth has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 4, ternaries 3 (4 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ShowMore.ShowMore (cognitive 20) aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/_ui/ShowMore.tsx:122— ShowMore.ShowMore has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 11, if/else 7 (9 pts) (nesting depth added 2). Most of this is not in the body itself: 3 of the 20 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 166, 144). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
SearchForm.SearchForm (cognitive 20) aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/_ui/SearchForm.tsx:19— SearchForm.SearchForm has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 7, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 5 of the 20 points are its own statements and the rest belongs to 5 function items inside it that branch (updateSearchParam, handleSemverToggle, handleYearSelection, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
hideNonTargetElements.applyAttributeToOthers::applyAttributes (cognitive 19) @navikt/core/react/src/utils/helpers/hideNonTargetElements.ts:82— hideNonTargetElements.applyAttributeToOthers::applyAttributes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 5, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TokenFilter.TokenFilter (cognitive 19) @navikt/core/react/src/data/token-filter/TokenFilter.tsx:47— TokenFilter.TokenFilter has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 7, ternaries 3 (nesting depth added 1). None of this is in the body itself: all 19 points belong to 4 function literals inside it that branch (lines 77, 137, 198, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
pagination.transformer (cognitive 18) @navikt/aksel/src/codemod/transforms/v1.0.0/pagination/pagination.ts:11— pagination.transformer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 8 (nesting depth added 3). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 7 function items inside it that branch (a function literal at line 77, addMigrationTag, addExplicitStandardProp, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
packageImports.moveAndRenameImport (cognitive 18) @navikt/aksel/src/codemod/utils/packageImports.ts:31— packageImports.moveAndRenameImport has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 4). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parse-meta.isOverridableComponent (cognitive 18) @navikt/core/react/scripts/metadata/parse-meta.ts:123— parse-meta.isOverridableComponent has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useScrollLock.preventScrollStandard (cognitive 18) @navikt/core/react/src/utils/hooks/useScrollLock.ts:78— useScrollLock.preventScrollStandard has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (7 pts), if/else 3 (nesting depth added 1). Most of this is not in the body itself: 2 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (lockScroll, handleResize). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
useTableDetailsPanel.DataTableDetailsPanelProvider (cognitive 18) @navikt/core/react/src/data/table/hooks/useTableDetailsPanel.tsx:65— useTableDetailsPanel.DataTableDetailsPanelProvider has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 3, loops 2, ternaries 2 (nesting depth added 3). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to 7 function literals inside it that branch (lines 97, 147, 134, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
useTableColumnResize.getAutoColumnWidth (cognitive 18) @navikt/core/react/src/data/table/column-header/useTableColumnResize.ts:325— useTableColumnResize.getAutoColumnWidth has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 3 (4 pts), boolean chains 3, ternaries 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate-autocomplete-options.createValueSuggestions (cognitive 18) @navikt/core/react/src/data/token-filter/helpers/generate-autocomplete-options.ts:267— generate-autocomplete-options.createValueSuggestions has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
jsx-value.getJSXLiteralValue (cognitive 17) @navikt/aksel/src/codemod/utils/jsx-value.ts:27— jsx-value.getJSXLiteralValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
print-remaining.printRemaining (cognitive 17) @navikt/aksel/src/codemod/v8-tokens/tasks/print-remaining.ts:8— print-remaining.printRemaining has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 1 (3 pts), error handling 1 (2 pts) (nesting depth added 7). Of this number, 9 points are the body's own statements and 8 belong to 4 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DragAndDropDragHandler.DragAndDropDragHandler (cognitive 17) @navikt/core/react/src/data/drag-and-drop/drag-handler/DragAndDropDragHandler.tsx:26— DragAndDropDragHandler.DragAndDropDragHandler has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10, boolean chains 5, ternaries 1 (2 pts) (nesting depth added 1). Most of this is not in the body itself: 4 of the 17 points are its own statements and the rest belongs to 4 function literals inside it that branch (lines 85, 67, 72, …). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
DataGridTableRoot.DataTableTBodyContent (cognitive 17) @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:434— DataGridTableRoot.DataTableTBodyContent has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 7, ternaries 4 (6 pts), if/else 4 (nesting depth added 2). Of this number, 9 points are the body's own statements and 8 belong to 2 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
dates-disabled.disableDate (cognitive 17) @navikt/core/react/src/utils/date/dates-disabled.ts:4— dates-disabled.disableDate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilteredOptions.FilteredOptions (cognitive 17) @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptions.tsx:16— FilteredOptions.FilteredOptions has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 15, if/else 1, ternaries 1. Of this number, 14 points are the body's own statements and 3 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GlobalSearch.search.globalSearch (cognitive 17) aksel.nav.no/website/app/_ui/global-search/server/GlobalSearch.search.ts:31— GlobalSearch.search.globalSearch has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 3 (4 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
route.GET (cognitive 17) aksel.nav.no/website/app/api/component-props/route.ts:64— route.GET has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, error handling 1, loops 1 (nesting depth added 4). Of this number, 11 points are the body's own statements and 6 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
proxy.proxy (cognitive 17) aksel.nav.no/website/proxy.ts:94— proxy.proxy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), error handling 2 (4 pts), boolean chains 2 (nesting depth added 5). Of this number, 14 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
validate-meta.validateMetas (cognitive 16) @navikt/core/react/scripts/metadata/validate-meta.ts:12— validate-meta.validateMetas has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
useTransitionStatus.useTransitionStatus (cognitive 16) @navikt/core/react/src/utils/hooks/useTransitionStatus.ts:39— useTransitionStatus.useTransitionStatus has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 7, ternaries 1. Of this number, 8 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
selectedOptionsContext.SelectedOptionsProvider (cognitive 16) @navikt/core/react/src/legacy/combobox/SelectedOptions/selectedOptionsContext.tsx:30— selectedOptionsContext.SelectedOptionsProvider has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, boolean chains 6, ternaries 1. Most of this is not in the body itself: 4 of the 16 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 70, 125, 97). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
HighlightedArticle.Highlight (cognitive 16) aksel.nav.no/website/app/(routes)/(root)/_ui/HighlightedArticle.tsx:27— HighlightedArticle.Highlight has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, ternaries 6 (7 pts), if/else 1 (nesting depth added 1). Of this number, 14 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
FileTooLong: floating-menu/Menu.tsx @navikt/core/react/src/utils/components/floating-menu/Menu.tsx— FileTooLong — 678 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 178 over it, 1.36× 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.
Change-coupling hub: Combobox.stories.tsx → filteredOptionsContext.tsx, Input.context.tsx, Input.tsx, selectedOptionsContext.tsx @navikt/core/react/src/legacy/combobox/Combobox.stories.tsx— `@navikt/core/react/src/legacy/combobox/Combobox.stories.tsx` changes together with 4 other files — `@navikt/core/react/src/legacy/combobox/FilteredOptions/filteredOptionsContext.tsx`, `@navikt/core/react/src/legacy/combobox/Input/Input.context.tsx`, `@navikt/core/react/src/legacy/combobox/Input/Input.tsx`, `@navikt/core/react/src/legacy/combobox/SelectedOptions/selectedOptionsContext.tsx` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Low cohesion: FigmaPluginInterface (LCOM4 6) @navikt/core/tokens/src/figma/plugin/FigmaPluginInterface.ts:5— FigmaPluginInterface's methods fall into 6 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 6 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Duplication concentrated across 23 sibling directories (23 clone groups) @navikt/core/react/src/datepicker/root/useDatepicker.tsx:101— 23 duplicated blocks under @navikt/core/react/src/ have copies in at least two of the sibling directories accordion, action-menu, chips, data, datepicker, dialog (+17 more sibling(s) not listed) — 10 of them are reported below, and 13 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 23 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 23 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 23 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 8 sibling directories (10 clone groups) @navikt/core/react/src/form/textarea/Textarea.tsx:122— 10 duplicated blocks under @navikt/core/react/src/form/ have copies in at least two of the sibling directories checkbox, checkbox-card, radio, radio-card, search, select (+2 more sibling(s) not listed) — 6 of them are reported below, and 4 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (7 clone groups) aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:1— 7 duplicated blocks under aksel.nav.no/sanity-studio/schema/documents/ have copies in at least two of the sibling directories god-praksis, grunnleggende, komponenter, presets, prinsipper, templates — 6 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 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 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (128 matched lines × 2 locations) · ×1
Duplicated block with local edits (128 matched lines × 2 locations) @navikt/core/react/src/datepicker/root/useDatepicker.tsx:101— @navikt/core/react/src/datepicker/root/useDatepicker.tsx:101 · @navikt/core/react/src/monthpicker/root/useMonthPicker.tsx:82 — the two spans are one implementation copied and then locally edited — 678 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.
Wholesale file copy (73 identical lines × 2 files) aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:1— aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:1 · aksel.nav.no/sanity-studio/schema/documents/templates/artikkel.tsx:1 — these 2 files are line-for-line copies of one another — 73 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 (67 matched lines × 2 locations) · ×1
Duplicated block with local edits (67 matched lines × 2 locations) @navikt/core/react/src/timeline/period-clickable/TimelineClickablePeriodInternal.tsx:57— @navikt/core/react/src/timeline/period-clickable/TimelineClickablePeriodInternal.tsx:57 · @navikt/core/react/src/timeline/pin/TimelinePinInternal.tsx:43 — the two spans are one implementation copied and then locally edited — 285 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (53 lines × 3 locations) aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:19— aksel.nav.no/sanity-studio/schema/documents/grunnleggende/artikkel.tsx:19 · aksel.nav.no/sanity-studio/schema/documents/komponenter/artikkel.tsx:21 · aksel.nav.no/sanity-studio/schema/documents/templates/artikkel.tsx:19 — 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.
Duplicated block (47 lines × 2 locations) @navikt/core/react/src/typography/BodyLong.tsx:8— @navikt/core/react/src/typography/BodyLong.tsx:8 · @navikt/core/react/src/typography/BodyShort.tsx:8 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (46 lines × 2 locations) aksel.nav.no/sanity-studio/schema/documents/komponenter/landingsside.tsx:7— aksel.nav.no/sanity-studio/schema/documents/komponenter/landingsside.tsx:7 · aksel.nav.no/sanity-studio/schema/documents/templates/landingsside.tsx:7 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (37 matched lines × 2 locations) · ×1
Duplicated block with local edits (37 matched lines × 2 locations) @navikt/core/react/src/datepicker/root/DatePickerRoot.tsx:131— @navikt/core/react/src/datepicker/root/DatePickerRoot.tsx:131 · @navikt/core/react/src/monthpicker/root/MonthPickerRoot.tsx:130 — the two spans are one implementation copied and then locally edited — 139 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (37 lines × 2 locations) aksel.nav.no/sanity-studio/sanity.config.ts:48— aksel.nav.no/sanity-studio/sanity.config.ts:48 · aksel.nav.no/sanity-studio/sanity.config.ts:95 — all 2 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (30 lines × 2 locations) @navikt/core/react/src/form/textarea/Textarea.tsx:122— @navikt/core/react/src/form/textarea/Textarea.tsx:122 · @navikt/core/react/src/form/textfield/TextField.tsx:82 — 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 (29 lines × 2 locations) @navikt/aksel-stylelint/src/rules/aksel-no-class-override/index.ts:11— @navikt/aksel-stylelint/src/rules/aksel-no-class-override/index.ts:11 · @navikt/aksel-stylelint/src/rules/aksel-no-legacy-classes/index.ts:11 — 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 (29 lines × 3 locations) aksel.nav.no/sanity-studio/schema/documents/grunnleggende/landingsside.tsx:34— aksel.nav.no/sanity-studio/schema/documents/grunnleggende/landingsside.tsx:34 · aksel.nav.no/sanity-studio/schema/documents/komponenter/landingsside.tsx:26 · aksel.nav.no/sanity-studio/schema/documents/templates/landingsside.tsx:25 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (28 lines × 2 locations) @navikt/core/react/src/form/checkbox/Checkbox.tsx:31— @navikt/core/react/src/form/checkbox/Checkbox.tsx:31 · @navikt/core/react/src/form/radio/Radio.tsx:27 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (27 lines × 3 locations) @navikt/core/react/src/form/select/Select.tsx:102— @navikt/core/react/src/form/select/Select.tsx:102 · @navikt/core/react/src/form/textarea/Textarea.tsx:122 · @navikt/core/react/src/form/textfield/TextField.tsx:82 — 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.
Duplicated block (27 lines × 2 locations) @navikt/core/react/src/legacy/combobox/Combobox.tsx:37— @navikt/core/react/src/legacy/combobox/Combobox.tsx:37 · @navikt/core/react/src/utils/components/date/input/DateInput.tsx:128 — 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 (26 lines × 3 locations) REDACTED:86— REDACTED:86 · REDACTED:205 · REDACTED:253 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (25 lines × 2 locations) @navikt/core/react/src/data-grid-preferences/row-density-settings/DataGridPreferencesRowDensitySettings.tsx:15— @navikt/core/react/src/data-grid-preferences/row-density-settings/DataGridPreferencesRowDensitySettings.tsx:15 · @navikt/core/react/src/data-grid-preferences/text-size-settings/DataGridPreferencesTextSizeSettings.tsx:14 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (21 lines × 3 locations) @navikt/core/react/src/timeline/axis-labels/TimelineAxisLabelsInternal.tsx:31— @navikt/core/react/src/timeline/axis-labels/TimelineAxisLabelsInternal.tsx:31 · @navikt/core/react/src/timeline/axis-labels/TimelineAxisLabelsInternal.tsx:59 · @navikt/core/react/src/timeline/axis-labels/TimelineAxisLabelsInternal.tsx:87 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (20 matched lines × 2 locations) · ×1
Duplicated block with local edits (20 matched lines × 2 locations) @navikt/core/react/src/data/table/helpers/table-grid-nav.ts:134— @navikt/core/react/src/data/table/helpers/table-grid-nav.ts:134 · @navikt/core/react/src/data/table/helpers/table-grid-nav.ts:168 — the two spans are one implementation copied and then locally edited — 122 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (20 lines × 2 locations) @navikt/core/react/src/dropdown/grouped-list-item/DropdownMenuGroupedListItem.tsx:17— @navikt/core/react/src/dropdown/grouped-list-item/DropdownMenuGroupedListItem.tsx:17 · @navikt/core/react/src/dropdown/list-item/DropdownMenuListItem.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.
Duplicated block (20 lines × 3 locations) aksel.nav.no/sanity-studio/schema/documents/admin/ds-stats.ts:10— aksel.nav.no/sanity-studio/schema/documents/admin/ds-stats.ts:10 · aksel.nav.no/sanity-studio/schema/documents/admin/ds-stats.ts:30 · aksel.nav.no/sanity-studio/schema/documents/admin/ds-stats.ts:50 — all 3 copies are in the same file, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Duplicated block (19 lines × 2 locations) @navikt/core/react/src/link-card/description/LinkCardDescription.tsx:4— @navikt/core/react/src/link-card/description/LinkCardDescription.tsx:4 · @navikt/core/react/src/link-card/footer/LinkCardFooter.tsx:4 — 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.
Complex function (anonymous) (cyclomatic 34, cognitive 75) REDACTED:62— (anonymous) has cyclomatic complexity 34 and cognitive complexity 75; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getAlphaColor (cyclomatic 33, cognitive 46) @navikt/core/tokens/src/tokens/colors/create-alpha.ts:87— getAlphaColor has cyclomatic complexity 33 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 47) @navikt/core/react/src/legacy/combobox/Input/Input.tsx:159— (anonymous) has cyclomatic complexity 31 and cognitive complexity 47; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function RowSelectionCell (cyclomatic 28, cognitive 36) @navikt/core/react/src/data/table/tr/DataTableTr.tsx:289— RowSelectionCell has cyclomatic complexity 28 and cognitive complexity 36; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function markdownMessage (cyclomatic 28, cognitive 35) tooling/analyzer/src/md-message.ts:7— markdownMessage has cyclomatic complexity 28 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 26, cognitive 35) @navikt/core/react/src/monthpicker/root/MonthPicker.util.ts:15— (anonymous) has cyclomatic complexity 26 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function RowExpansionCell (cyclomatic 26, cognitive 34) @navikt/core/react/src/data/table/tr/DataTableTr.tsx:148— RowExpansionCell has cyclomatic complexity 26 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 24, cognitive 35) @navikt/core/react/src/timeline/root/TimelineKeyboardNavProvider.tsx:51— (anonymous) has cyclomatic complexity 24 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function FilteredOptions (cyclomatic 23, cognitive 13) @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptions.tsx:16— FilteredOptions has cyclomatic complexity 23 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 22, cognitive 20) @navikt/core/react/src/utils/components/floating/Floating.tsx:273— (anonymous) has cyclomatic complexity 22 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 21, cognitive 16) @navikt/core/react/src/form/useFormField.ts:63— (anonymous) has cyclomatic complexity 21 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 20, cognitive 28) @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.ts:94— (anonymous) has cyclomatic complexity 20 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function pickRangeSelection (cyclomatic 19, cognitive 25) @navikt/core/react/src/utils/date/pick-range-selection.ts:14— pickRangeSelection has cyclomatic complexity 19 and cognitive complexity 25; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 19, cognitive 17) @navikt/core/react/src/tooltip/Tooltip.tsx:113— (anonymous) has cyclomatic complexity 19 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleChange (cyclomatic 19, cognitive 16) @navikt/core/react/src/datepicker/root/useDatepicker.tsx:275— handleChange has cyclomatic complexity 19 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 23) @navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx:328— (anonymous) has cyclomatic complexity 18 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function compareResults (cyclomatic 18, cognitive 22) tooling/analyzer/src/helpers/compare.ts:45— compareResults has cyclomatic complexity 18 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 18, cognitive 17) @navikt/core/react/src/modal/root/ModalRoot.tsx:26— (anonymous) has cyclomatic complexity 18 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getJSXLiteralValue (cyclomatic 17, cognitive 19) @navikt/aksel/src/codemod/utils/jsx-value.ts:27— getJSXLiteralValue has cyclomatic complexity 17 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 19) @navikt/core/react/src/legacy/combobox/Input/Input.tsx:75— (anonymous) has cyclomatic complexity 17 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 17, cognitive 14) @navikt/core/react/src/form/textarea/Textarea.tsx:76— (anonymous) has cyclomatic complexity 17 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.
Complex function toValidation (cyclomatic 17, cognitive 10) @navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx:147— toValidation has cyclomatic complexity 17 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.
Complex function callback (cyclomatic 16, cognitive 23) apps/mcp-server/src/tools/find-docs.ts:54— callback has cyclomatic complexity 16 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 23) tooling/changelog/createMainChangelog.ts:141— (anonymous) has cyclomatic complexity 16 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 16, cognitive 13) @navikt/core/react/src/button/Button.tsx:71— (anonymous) has cyclomatic complexity 16 and cognitive complexity 13; 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 Program (cyclomatic 15, cognitive 23) · ×1
Complex function Program (cyclomatic 15, cognitive 23) tooling/eslint/args-check.js:15— Program has cyclomatic complexity 15 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function getAutoColumnWidth (cyclomatic 15, cognitive 18) @navikt/core/react/src/data/table/column-header/useTableColumnResize.ts:325— getAutoColumnWidth has cyclomatic complexity 15 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function lockScroll (cyclomatic 15, cognitive 15) @navikt/core/react/src/utils/hooks/useScrollLock.ts:97— lockScroll has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function Items (cyclomatic 15, cognitive 14) @navikt/core/react/src/toggle-group/ToggleGroup.stories.tsx:24— Items has cyclomatic complexity 15 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.
Complex function analyzeReact (cyclomatic 14, cognitive 28) tooling/analyzer/src/analyze-react.ts:25— analyzeReact has cyclomatic complexity 14 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 13) @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:155— (anonymous) has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function render (cyclomatic 14, cognitive 13) @navikt/core/react/src/process/Process.stories.tsx:341— render has cyclomatic complexity 14 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 12) @navikt/core/react/src/data/table/column-header/DataTableColumnHeader.tsx:64— (anonymous) has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function handleChange (cyclomatic 14, cognitive 11) @navikt/core/react/src/monthpicker/root/useMonthPicker.tsx:264— handleChange has cyclomatic complexity 14 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.
Complex function (anonymous) (cyclomatic 13, cognitive 22) @navikt/core/react/src/utils/date/parse-date.ts:35— (anonymous) has cyclomatic complexity 13 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function createValueSuggestions (cyclomatic 13, cognitive 19) @navikt/core/react/src/data/token-filter/helpers/generate-autocomplete-options.ts:267— createValueSuggestions has cyclomatic complexity 13 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fn (cyclomatic 13, cognitive 16) @navikt/core/react/src/utils/components/floating/Floating.utils.ts:17— fn has cyclomatic complexity 13 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateAutoCompleteOptions (cyclomatic 13, cognitive 15) @navikt/core/react/src/data/token-filter/helpers/generate-autocomplete-options.ts:31— generateAutoCompleteOptions has cyclomatic complexity 13 and cognitive complexity 15; 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.
R3 · Large Files· @navikt/aksel/src/codemod/v8-tokens/config/legacy.tokens.ts · ×1
@navikt/aksel/src/codemod/v8-tokens/config/legacy.tokens.ts: 1763 lines of code @navikt/aksel/src/codemod/v8-tokens/config/legacy.tokens.ts:1— @navikt/aksel/src/codemod/v8-tokens/config/legacy.tokens.ts has 1763 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/data/stories/Data.test-data.tsx · ×1
@navikt/core/react/src/data/stories/Data.test-data.tsx: 1697 lines of code @navikt/core/react/src/data/stories/Data.test-data.tsx:1— @navikt/core/react/src/data/stories/Data.test-data.tsx has 1697 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/data/stories/dummy-data.tsx · ×1
@navikt/core/react/src/data/stories/dummy-data.tsx: 1527 lines of code @navikt/core/react/src/data/stories/dummy-data.tsx:1— @navikt/core/react/src/data/stories/dummy-data.tsx has 1527 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/data/stories/Data.data-prop.stories.tsx · ×1
@navikt/core/react/src/data/stories/Data.data-prop.stories.tsx: 1106 lines of code @navikt/core/react/src/data/stories/Data.data-prop.stories.tsx:1— @navikt/core/react/src/data/stories/Data.data-prop.stories.tsx has 1106 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/action-menu/ActionMenu.stories.tsx · ×1
@navikt/core/react/src/action-menu/ActionMenu.stories.tsx: 987 lines of code @navikt/core/react/src/action-menu/ActionMenu.stories.tsx:1— @navikt/core/react/src/action-menu/ActionMenu.stories.tsx has 987 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/utils/components/floating-menu/Menu.tsx · ×1
@navikt/core/react/src/utils/components/floating-menu/Menu.tsx: 925 lines of code @navikt/core/react/src/utils/components/floating-menu/Menu.tsx:1— @navikt/core/react/src/utils/components/floating-menu/Menu.tsx has 925 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/link-card/LinkCard.stories.tsx · ×1
@navikt/core/react/src/link-card/LinkCard.stories.tsx: 864 lines of code @navikt/core/react/src/link-card/LinkCard.stories.tsx:1— @navikt/core/react/src/link-card/LinkCard.stories.tsx has 864 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/modal/helpers/dialog-polyfill.ts · ×1
@navikt/core/react/src/modal/helpers/dialog-polyfill.ts: 861 lines of code @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:1— @navikt/core/react/src/modal/helpers/dialog-polyfill.ts has 861 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/data/stories/Data.stories.tsx · ×1
@navikt/core/react/src/data/stories/Data.stories.tsx: 794 lines of code @navikt/core/react/src/data/stories/Data.stories.tsx:1— @navikt/core/react/src/data/stories/Data.stories.tsx has 794 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/dialog/Dialog.stories.tsx · ×1
@navikt/core/react/src/dialog/Dialog.stories.tsx: 719 lines of code @navikt/core/react/src/dialog/Dialog.stories.tsx:1— @navikt/core/react/src/dialog/Dialog.stories.tsx has 719 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/dialog/Dialog.tests.stories.tsx · ×1
@navikt/core/react/src/dialog/Dialog.tests.stories.tsx: 708 lines of code @navikt/core/react/src/dialog/Dialog.tests.stories.tsx:1— @navikt/core/react/src/dialog/Dialog.tests.stories.tsx has 708 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/datepicker/DatePicker.stories.tsx · ×1
@navikt/core/react/src/datepicker/DatePicker.stories.tsx: 652 lines of code @navikt/core/react/src/datepicker/DatePicker.stories.tsx:1— @navikt/core/react/src/datepicker/DatePicker.stories.tsx has 652 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/timeline/Timeline.stories.tsx · ×1
@navikt/core/react/src/timeline/Timeline.stories.tsx: 628 lines of code @navikt/core/react/src/timeline/Timeline.stories.tsx:1— @navikt/core/react/src/timeline/Timeline.stories.tsx has 628 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/legacy/combobox/Combobox.stories.tsx · ×1
@navikt/core/react/src/legacy/combobox/Combobox.stories.tsx: 623 lines of code @navikt/core/react/src/legacy/combobox/Combobox.stories.tsx:1— @navikt/core/react/src/legacy/combobox/Combobox.stories.tsx has 623 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/utils/components/floating-menu/Menu.stories.tsx · ×1
@navikt/core/react/src/utils/components/floating-menu/Menu.stories.tsx: 583 lines of code @navikt/core/react/src/utils/components/floating-menu/Menu.stories.tsx:1— @navikt/core/react/src/utils/components/floating-menu/Menu.stories.tsx has 583 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx · ×1
@navikt/core/react/src/data/table/root/DataGridTableRoot.tsx: 568 lines of code @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:1— @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx has 568 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tests.stories.tsx · ×1
@navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tests.stories.tsx: 541 lines of code @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tests.stories.tsx:1— @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tests.stories.tsx has 541 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/datepicker/DatePicker.tests.stories.tsx · ×1
@navikt/core/react/src/datepicker/DatePicker.tests.stories.tsx: 537 lines of code @navikt/core/react/src/datepicker/DatePicker.tests.stories.tsx:1— @navikt/core/react/src/datepicker/DatePicker.tests.stories.tsx has 537 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx · ×1
@navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx: 535 lines of code @navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx:1— @navikt/core/react/src/datepicker/root/useRangeDatepicker.tsx has 535 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/process/Process.stories.tsx · ×1
@navikt/core/react/src/process/Process.stories.tsx: 531 lines of code @navikt/core/react/src/process/Process.stories.tsx:1— @navikt/core/react/src/process/Process.stories.tsx has 531 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/primitives/box/Box.stories.tsx · ×1
@navikt/core/react/src/primitives/box/Box.stories.tsx: 497 lines of code @navikt/core/react/src/primitives/box/Box.stories.tsx:1— @navikt/core/react/src/primitives/box/Box.stories.tsx has 497 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/utils/components/floating/Floating.tsx · ×1
@navikt/core/react/src/utils/components/floating/Floating.tsx: 487 lines of code @navikt/core/react/src/utils/components/floating/Floating.tsx:1— @navikt/core/react/src/utils/components/floating/Floating.tsx has 487 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/modal/Modal.stories.tsx · ×1
@navikt/core/react/src/modal/Modal.stories.tsx: 470 lines of code @navikt/core/react/src/modal/Modal.stories.tsx:1— @navikt/core/react/src/modal/Modal.stories.tsx has 470 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/aksel/src/codemod/v8-tokens/config/v8.tokens.ts · ×1
@navikt/aksel/src/codemod/v8-tokens/config/v8.tokens.ts: 466 lines of code @navikt/aksel/src/codemod/v8-tokens/config/v8.tokens.ts:1— @navikt/aksel/src/codemod/v8-tokens/config/v8.tokens.ts has 466 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx · ×1
@navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx: 451 lines of code @navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx:1— @navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx has 451 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx · ×1
@navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx: 446 lines of code @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx:1— @navikt/core/react/src/utils/components/dismissablelayer/DismissableLayer.tsx has 446 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/utils/components/Listbox/Listbox.stories.tsx · ×1
@navikt/core/react/src/utils/components/Listbox/Listbox.stories.tsx: 442 lines of code @navikt/core/react/src/utils/components/Listbox/Listbox.stories.tsx:1— @navikt/core/react/src/utils/components/Listbox/Listbox.stories.tsx has 442 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/primitives/bleed/Bleed.stories.tsx · ×1
@navikt/core/react/src/primitives/bleed/Bleed.stories.tsx: 439 lines of code @navikt/core/react/src/primitives/bleed/Bleed.stories.tsx:1— @navikt/core/react/src/primitives/bleed/Bleed.stories.tsx has 439 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/utils/components/floating/Floating.stories.tsx · ×1
@navikt/core/react/src/utils/components/floating/Floating.stories.tsx: 424 lines of code @navikt/core/react/src/utils/components/floating/Floating.stories.tsx:1— @navikt/core/react/src/utils/components/floating/Floating.stories.tsx has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/form/form-summary/FormSummary.stories.tsx · ×1
@navikt/core/react/src/form/form-summary/FormSummary.stories.tsx: 420 lines of code @navikt/core/react/src/form/form-summary/FormSummary.stories.tsx:1— @navikt/core/react/src/form/form-summary/FormSummary.stories.tsx has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/list/List.stories.tsx · ×1
@navikt/core/react/src/list/List.stories.tsx: 417 lines of code @navikt/core/react/src/list/List.stories.tsx:1— @navikt/core/react/src/list/List.stories.tsx has 417 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/form/combobox2/Combobox2.stories.tsx · ×1
@navikt/core/react/src/form/combobox2/Combobox2.stories.tsx: 410 lines of code @navikt/core/react/src/form/combobox2/Combobox2.stories.tsx:1— @navikt/core/react/src/form/combobox2/Combobox2.stories.tsx has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx · ×1
aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx: 409 lines of code aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx:1— aksel.nav.no/sanity-studio/schema/objects/shared/riktekst.tsx has 409 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· @navikt/core/react/src/form/checkbox/Checkbox.stories.tsx · ×1
@navikt/core/react/src/form/checkbox/Checkbox.stories.tsx: 408 lines of code @navikt/core/react/src/form/checkbox/Checkbox.stories.tsx:1— @navikt/core/react/src/form/checkbox/Checkbox.stories.tsx has 408 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~211 LoC) @navikt/core/react/src/data/stories/DataTableProfiler.tsx— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~108 LoC) @navikt/core/react/src/form/combobox2/list/useAnnounce.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~78 LoC) @navikt/core/react/src/modal/Modal.types.test-d.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~42 LoC) @navikt/core/react/src/data/filter/root/DataFilterRoot.tsx— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), but 2 in-repo import(s) from 1 other file(s) do name it (@navikt/core/react/src/data/filter/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~37 LoC) tooling/scripts/publish-npm.mts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~30 LoC) @navikt/core/react/src/form/form-summary/FormSummary.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~27 LoC) @navikt/core/react/src/link-card/LinkCard.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~25 LoC) @navikt/core/react/src/datepicker/DatePicker.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~22 LoC) @navikt/core/react/src/internal-header/InternalHeader.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~21 LoC) @navikt/core/react/src/badge/Badge.meta.ts— no import path from any entry point (141 application, 32 tooling, 231 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
Unused dependency 'typescript-language-server' REDACTED:114— Declared in the root 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 '@sanity/preview-url-secret' aksel.nav.no/sanity-studio/package.json:24— Declared in aksel.nav.no/sanity-studio/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency '@modelcontextprotocol/inspector' apps/mcp-server/package.json:20— Declared in apps/mcp-server/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Weak hash algorithm aksel.nav.no/website/app/_ui/global-search/server/GlobalSearch.fetch.ts:72— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Third-party script without Subresource Integrity aksel.nav.no/sanity-studio/.sanity/runtime/index.html:307— `https://core.sanity-cdn.com/bridge.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository.
Minor — 170 finding(s)
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel aksel.nav.no/website/proxy.ts:72— `aksel.nav.no/website/proxy.ts` reports through `console.*` at line 72 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/proxy.ts:141— `aksel.nav.no/website/proxy.ts` reports through `console.*` at line 141 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/proxy.ts:157— `aksel.nav.no/website/proxy.ts` reports through `console.*` at line 157 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/proxy.ts:178— `aksel.nav.no/website/proxy.ts` reports through `console.*` at line 178 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/templates/skjemavalidering/react-hook-form.tsx:35— `aksel.nav.no/website/pages/templates/skjemavalidering/react-hook-form.tsx` reports through `console.*` at line 35 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/radio-card/error.tsx:11— `aksel.nav.no/website/pages/eksempler/radio-card/error.tsx` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/radio/description.tsx:5— `aksel.nav.no/website/pages/eksempler/radio/description.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/radio/disabled.tsx:5— `aksel.nav.no/website/pages/eksempler/radio/disabled.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/radio/error.tsx:10— `aksel.nav.no/website/pages/eksempler/radio/error.tsx` reports through `console.*` at line 10 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/radio/hide-legend.tsx:5— `aksel.nav.no/website/pages/eksempler/radio/hide-legend.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/radio/medium.tsx:5— `aksel.nav.no/website/pages/eksempler/radio/medium.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/radio/radio-description.tsx:5— `aksel.nav.no/website/pages/eksempler/radio/radio-description.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/radio/readonly.tsx:5— `aksel.nav.no/website/pages/eksempler/radio/readonly.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/radio/small.tsx:5— `aksel.nav.no/website/pages/eksempler/radio/small.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/progress-bar/indeterminate.tsx:14— `aksel.nav.no/website/pages/eksempler/progress-bar/indeterminate.tsx` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/monthpicker/validation.tsx:18— `aksel.nav.no/website/pages/eksempler/monthpicker/validation.tsx` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/header/search.tsx:15— `aksel.nav.no/website/pages/eksempler/header/search.tsx` reports through `console.*` at line 15 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/datepicker/validation.tsx:18— `aksel.nav.no/website/pages/eksempler/datepicker/validation.tsx` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/combobox/multi-select-controlled.tsx:13— `aksel.nav.no/website/pages/eksempler/combobox/multi-select-controlled.tsx` reports through `console.*` at line 13 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/checkbox-card/demo.tsx:5— `aksel.nav.no/website/pages/eksempler/checkbox-card/demo.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/checkbox/checkbox-description.tsx:5— `aksel.nav.no/website/pages/eksempler/checkbox/checkbox-description.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/checkbox/description.tsx:5— `aksel.nav.no/website/pages/eksempler/checkbox/description.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/checkbox/disabled.tsx:5— `aksel.nav.no/website/pages/eksempler/checkbox/disabled.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/checkbox/group-error.tsx:5— `aksel.nav.no/website/pages/eksempler/checkbox/group-error.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel aksel.nav.no/website/pages/eksempler/checkbox/hide-legend.tsx:5— `aksel.nav.no/website/pages/eksempler/checkbox/hide-legend.tsx` reports through `console.*` at line 5 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Deprecated: @yuku-codegen/binding-android-arm64 REDACTED:9371— @yuku-codegen/binding-android-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-darwin-arm64 REDACTED:9378— @yuku-codegen/binding-darwin-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-darwin-x64 REDACTED:9385— @yuku-codegen/binding-darwin-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-freebsd-x64 REDACTED:9392— @yuku-codegen/binding-freebsd-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm-gnu REDACTED:9399— @yuku-codegen/binding-linux-arm-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm-musl REDACTED:9406— @yuku-codegen/binding-linux-arm-musl 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm64-gnu REDACTED:9413— @yuku-codegen/binding-linux-arm64-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-arm64-musl REDACTED:9420— @yuku-codegen/binding-linux-arm64-musl 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-x64-gnu REDACTED:9427— @yuku-codegen/binding-linux-x64-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-linux-x64-musl REDACTED:9434— @yuku-codegen/binding-linux-x64-musl 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-win32-arm64 REDACTED:9441— @yuku-codegen/binding-win32-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-codegen/binding-win32-x64 REDACTED:9448— @yuku-codegen/binding-win32-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-codegen is pure JavaScript since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-android-arm64 REDACTED:9455— @yuku-parser/binding-android-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-darwin-arm64 REDACTED:9462— @yuku-parser/binding-darwin-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-darwin-x64 REDACTED:9469— @yuku-parser/binding-darwin-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-freebsd-x64 REDACTED:9476— @yuku-parser/binding-freebsd-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-arm-gnu REDACTED:9483— @yuku-parser/binding-linux-arm-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-arm-musl REDACTED:9490— @yuku-parser/binding-linux-arm-musl 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-arm64-gnu REDACTED:9497— @yuku-parser/binding-linux-arm64-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-arm64-musl REDACTED:9504— @yuku-parser/binding-linux-arm64-musl 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-x64-gnu REDACTED:9511— @yuku-parser/binding-linux-x64-gnu 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-linux-x64-musl REDACTED:9518— @yuku-parser/binding-linux-x64-musl 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-win32-arm64 REDACTED:9525— @yuku-parser/binding-win32-arm64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @yuku-parser/binding-win32-x64 REDACTED:9532— @yuku-parser/binding-win32-x64 0.10.2 is resolved in REDACTED and is marked deprecated by its publisher: "yuku-parser runs on yuku-core since 0.14". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: cross-spawn-async REDACTED:11780— cross-spawn-async 2.2.5 is resolved in REDACTED and is marked deprecated by its publisher: "cross-spawn no longer requires a build toolchain, use it instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Duplicated predicate aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/[category]/page.tsx:171— `!categoryPages || categoryPages.length === 0` appears character-identically in 3 files — aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/[category]/page.tsx, aksel.nav.no/website/app/(routes)/(designsystemet)/komponenter/[category]/page.tsx, aksel.nav.no/website/app/(routes)/(designsystemet)/monster-maler/[category]/page.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 aksel.nav.no/website/app/(routes)/(god-praksis)/god-praksis/artikler/@endringslogg/(..)endring/[slug]/page.tsx:73— `!pageData?.heading || !pageData._id || !pageData.endringsdato` appears character-identically in 2 files — aksel.nav.no/website/app/(routes)/(god-praksis)/god-praksis/artikler/@endringslogg/(..)endring/[slug]/page.tsx, aksel.nav.no/website/app/(routes)/(god-praksis)/god-praksis/endring/[slug]/page.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 @navikt/aksel/src/codemod/transforms/v1.0.0/pagination/pagination.ts:38— `attr.type === "JSXAttribute" && attr.name.name === "size"` appears character-identically in 2 files — @navikt/aksel/src/codemod/transforms/v1.0.0/pagination/pagination.ts, @navikt/aksel/src/codemod/transforms/v8.0.0/list/list.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 aksel.nav.no/website/app/(routes)/(designsystemet)/@endringslogg/(.)grunnleggende/endringslogg/[slug]/page.tsx:69— `block._type === "block" && block.style === "h2"` appears character-identically in 2 files — aksel.nav.no/website/app/(routes)/(designsystemet)/@endringslogg/(.)grunnleggende/endringslogg/[slug]/page.tsx, aksel.nav.no/website/app/(routes)/(designsystemet)/grunnleggende/endringslogg/[slug]/page.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 @navikt/core/react/src/datepicker/root/useDatepicker.tsx:298— `disabled && dateMatchModifiers(day, disabled)` appears character-identically in 2 files — @navikt/core/react/src/datepicker/root/useDatepicker.tsx, @navikt/core/react/src/datepicker/root/useRangeDatepicker.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 @navikt/core/react/src/monthpicker/root/MonthPickerRoot.tsx:104— `dropdownCaption && (!fromDate || !toDate)` appears character-identically in 2 files — @navikt/core/react/src/monthpicker/root/MonthPickerRoot.tsx, @navikt/core/react/src/monthpicker/standalone/MonthPickerStandalone.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 @navikt/core/react/src/tabs/list/useTabList.ts:35— `event.shiftKey || event.ctrlKey || event.altKey || event.metaKey` appears character-identically in 2 files — @navikt/core/react/src/tabs/list/useTabList.ts, @navikt/core/react/src/toggle-group/item/useToggleItem.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 @navikt/core/react/src/datepicker/root/useDatepicker.tsx:222— `fromDate && day && differenceInCalendarDays(fromDate, day) > 0` appears character-identically in 2 files — @navikt/core/react/src/datepicker/root/useDatepicker.tsx, @navikt/core/react/src/datepicker/root/useRangeDatepicker.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 @navikt/core/react/src/form/checkbox/Checkbox.tsx:38— `inputProps.disabled || readOnly || !cardContext` appears character-identically in 2 files — @navikt/core/react/src/form/checkbox/Checkbox.tsx, @navikt/core/react/src/form/radio/Radio.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 @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:494— `isLoading && loading?.variant === "overlay"` appears character-identically in 2 files — @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx, @navikt/core/react/src/data/table/tbody/DataTableTbody.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 @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:446— `isLoading && loading?.variant === "skeleton"` appears character-identically in 2 files — @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx, @navikt/core/react/src/data/table/tr/DataTableTr.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 @navikt/core/react/src/data/table/helpers/table-keyboard.ts:88— `key === "ArrowDown" || key === "ArrowUp"` appears character-identically in 2 files — @navikt/core/react/src/data/table/helpers/table-keyboard.ts, @navikt/core/react/src/timeline/root/TimelineKeyboardNavProvider.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 @navikt/core/react/src/form/checkbox/Checkbox.tsx:47— `nativeHandler && event.currentTarget.contains(nativeHandler)` appears character-identically in 2 files — @navikt/core/react/src/form/checkbox/Checkbox.tsx, @navikt/core/react/src/form/radio/Radio.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 aksel.nav.no/website/app/(routes)/(god-praksis)/god-praksis/[tema]/page.tsx:73— `pageOgImage && ogImages.unshift(pageOgImage)` appears character-identically in 2 files — aksel.nav.no/website/app/(routes)/(god-praksis)/god-praksis/[tema]/page.tsx, aksel.nav.no/website/app/(routes)/(produktbloggen)/produktbloggen/[slug]/page.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 @navikt/core/react/src/form/fieldset/useFieldset.ts:30— `props.description && !containsReadMore(props.description)` appears character-identically in 2 files — @navikt/core/react/src/form/fieldset/useFieldset.ts, @navikt/core/react/src/form/useFormField.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 aksel.nav.no/website/pages/eksempler/checkbox/indeterminate.tsx:23— `selectedRows.length > 0 && selectedRows.length !== data.length` appears character-identically in 2 files — aksel.nav.no/website/pages/eksempler/checkbox/indeterminate.tsx, aksel.nav.no/website/pages/eksempler/table/selectable.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 @navikt/core/react/src/datepicker/root/useDatepicker.tsx:224— `toDate && day && differenceInCalendarDays(day, toDate) > 0` appears character-identically in 2 files — @navikt/core/react/src/datepicker/root/useDatepicker.tsx, @navikt/core/react/src/datepicker/root/useRangeDatepicker.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 @navikt/core/react/src/utils/helpers/className.ts:16— `typeof mix === "string" || typeof mix === "number"` appears character-identically in 2 files — @navikt/core/react/src/utils/helpers/className.ts, aksel.nav.no/website/app/_ui/utils/className.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.
Orphaned file @navikt/core/react/src/process/Process.stories.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/core/react/src/form/form-summary/FormSummary.stories.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/core/react/src/form/file-upload/FileUpload.stories.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file tooling/changelog/createMainChangelog.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 @navikt/core/react/src/form/file-upload/FileUploadItem.stories.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/core/react/src/legacy/combobox/FilteredOptions/useVirtualFocus.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 @navikt/core/react/src/form/file-upload/root/FileUploadRoot.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/core/react/src/progress-bar/ProgressBar.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/core/react/src/progress-bar/ProgressBar.stories.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptionsItem.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/core/react/src/legacy/combobox/ComboboxProvider.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/core/react/src/form/form-summary/FormSummary.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/core/tokens/src/tokens/font.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 @navikt/core/react/src/form/file-upload/FileUploadDropzone.stories.tsx:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file @navikt/aksel/src/codemod/utils/ast.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 @navikt/aksel-stylelint/src/rules/aksel-design-token-exists/index.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.
GD1 · Unfinished & placeholder code· Placeholder literal left in code · ×10
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/fieldset/hide-legend.tsx:10— A placeholder string ("Lorem ipsum dolor sit, amet consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/info-card/colors.tsx:33— A placeholder string ("Lorem ipsum dolor sit amet consectetur a…") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/info-card/sizes.tsx:11— A placeholder string ("Lorem ipsum dolor sit amet consectetur a…") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/info-card/sizes.tsx:20— A placeholder string ("Lorem ipsum dolor sit amet consectetur a…") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/link/anchor.tsx:8— A placeholder string ("Lorem ipsum dolor sit amet consectetur, …") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/modal/placement-top.tsx:20— A placeholder string ("Lorem ipsum, dolor sit amet consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/popover/placement.tsx:35— A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/primitive-bleed/full.tsx:7— A placeholder string ("Lorem ipsum dolor sit amet, consectetur …") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/skeleton/link-card.tsx:24— A placeholder string ("lorem ipsum dolor sit amet consectetur a…") is still in shipped code — typical of generated boilerplate that was never filled in.
Placeholder literal left in code aksel.nav.no/website/pages/eksempler/skeleton/link-card.tsx:27— A placeholder string ("lorem ipsum dolor sit amet consectetur") is still in shipped code — typical of generated boilerplate that was never filled in.
Outdated (npm): @navikt/aksel @navikt/aksel/package.json:2— @navikt/aksel is pinned at 0.0.0-use.local; registry.npmjs.org publishes 8.23.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): @navikt/aksel-icons @navikt/aksel-icons/package.json:2— @navikt/aksel-icons is pinned at 0.0.0-use.local; registry.npmjs.org publishes 8.23.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): @navikt/ds-css @navikt/aksel-stylelint/package.json:46— @navikt/ds-css is pinned at 0.0.0-use.local; registry.npmjs.org publishes 8.23.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): @navikt/ds-react @navikt/core/react/package.json:2— @navikt/ds-react is pinned at 0.0.0-use.local; registry.npmjs.org publishes 8.23.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): @navikt/ds-tailwind @navikt/core/tailwind/package.json:2— @navikt/ds-tailwind is pinned at 0.0.0-use.local; registry.npmjs.org publishes 8.23.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): @navikt/ds-tokens @navikt/aksel-stylelint/package.json:47— @navikt/ds-tokens is pinned at 0.0.0-use.local; registry.npmjs.org publishes 8.23.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.
redundant comment @navikt/aksel/src/codemod/transforms/v8.0.0/box-new/box-new.ts:108— "If local name is BoxNew, rename it to Box" repeats the code it sits on: 4 of its 5 words (local, name, box, new) are already in `if (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment @navikt/aksel/src/codemod/v8-tokens/tasks/print-remaining.ts:86— "Sort tokens in file by line number" repeats the code it sits on: 4 of its 5 words (sort, tokens, line, number) are already in `tokens.sort((a, b) => a.lineNumber - b.lineNumber);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment @navikt/core/react/src/utils/components/floating-menu/Menu.tsx:817— "Menu SubMenu Trigger" repeats the code it sits on: 3 of its 3 words (menu, sub, trigger) are already in `type MenuSubTriggerProps = MenuItemInternalProps;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment @navikt/core/react/src/utils/components/floating-menu/Menu.tsx:881— "Menu SubMenu Content" repeats the code it sits on: 3 of its 3 words (menu, sub, content) are already in `type MenuSubContentProps = Omit<`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment @navikt/core/tokens/src/index.ts:312— "SDDictionaryNonCSSFormats.registerFormat({ name: "format-CJS-static", format: formatCJSStatic, });" repeats the code it sits on: 8 of its 10 words (sd, dictionary, non, css, formats, register, format, name) are already in `SDDictionaryNonCSSFormats.registerFormat({`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment aksel.nav.no/website/pages/eksempler/timeline-intern/dynamic.tsx:213— "Stop if periodStart is after rangeEnd" repeats the code it sits on: 4 of its 5 words (period, start, range, end) are already in `if (periodStart > rangeEnd) break;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Irreversible deploy step: production deploy on every push REDACTED:45— Job `upload` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it.
Irreversible deploy step: production deploy on every push REDACTED:29— Job `upload` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it.
Irreversible deploy step: production deploy on every push REDACTED:48— Job `build_and_deploy` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it.
Irreversible deploy step: production deploy on every push REDACTED:81— Job `build_and_deploy` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it.
Irreversible deploy step: production deploy on every push REDACTED:57— Job `build_and_deploy` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it.
Irreversible deploy step: production deploy on every push REDACTED:84— Job `build` rolls out to production on every branch push, with no environment, no manual approval and no test it waits for — every push is a production release, and nothing stops a bad one before users get it.
Disabled test aksel.nav.no/website/e2e/global-search.e2e.ts:177— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test aksel.nav.no/website/e2e/global-search.e2e.ts:203— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test aksel.nav.no/website/e2e/global-search.e2e.ts:403— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test aksel.nav.no/website/e2e/global-search.e2e.ts:433— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test aksel.nav.no/website/e2e/global-search.e2e.ts:478— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×4
Projects may be oversized for their cohesion @navikt/core/react/package.json:1— `@navikt/core/react` (45495 LoC, 691 module-visible types across 275 directories) overshoots its size bounds. 4 of 17 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 5.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion aksel.nav.no/website/package.json:1— `aksel.nav.no/website` (67435 LoC, 822 module-visible types across 217 directories) overshoots its size bounds. 4 of 17 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 5.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion @navikt/aksel/package.json:1— `@navikt/aksel` (7331 LoC, 61 module-visible types across 33 directories) overshoots its size bounds. 4 of 17 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 5.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Projects may be oversized for their cohesion aksel.nav.no/sanity-studio/package.json:1— `aksel.nav.no/sanity-studio` (6619 LoC, 40 module-visible types across 19 directories) overshoots its size bounds. 4 of 17 build unit(s) (npm) overshoot their size bounds, lowering Project Cohesion to 5.3/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 25 significant file(s) lose their only recent owner: @navikt/core/react/src/dialog/Dialog.stories.tsx, @navikt/core/react/src/utils/components/focus-boundary/FocusBoundary.tsx, @navikt/core/react/src/utils/hooks/useScrollLock.ts, @navikt/core/react/src/utils/hooks/base-primitive/useBasePrimitiveProps.stories.tsx, @navikt/core/react/src/table/animate-height/TableAnimateHeightInternal.tsx, @navikt/core/react/src/info-card/InfoCard.stories.tsx, @navikt/core/react/src/timeline/root/TimelineRoot.tsx, @navikt/core/react/src/timeline/root/TimelineKeyboardNavProvider.tsx (+17 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 15 significant file(s) lose their only recent owner: @navikt/core/react/src/utils/components/Listbox/Listbox.stories.tsx, @navikt/core/react/src/modal/Modal.stories.tsx, @navikt/core/react/src/form/combobox2/Combobox2.stories.tsx, @navikt/core/react/src/form/combobox2/popup/ComboboxPopup.stories.tsx, @navikt/core/react/src/form/combobox2/Combobox.tsx, @navikt/core/react/src/utils/hooks/useSyncExternalStoreShim.ts, @navikt/core/react/src/form/combobox2/list/ComboboxList.tsx, @navikt/core/react/src/utils/components/Listbox/root/ListboxRoot.tsx (+7 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 12 significant file(s) lose their only recent owner: @navikt/core/react/src/data/token-filter/TokenFilter.stories.tsx, @navikt/core/react/src/data/token-filter/helpers/generate-autocomplete-options.ts, @navikt/core/react/src/data/table/helpers/table-focus.ts, tooling/analyzer/src/md-message.ts, @navikt/core/react/src/data/table/helpers/table-grid-nav.ts, @navikt/core/react/src/data/table/hooks/useTableKeyboardNav.ts, @navikt/core/react/src/data/table/hooks/useTableSort.ts, @navikt/core/react/src/data/table/hooks/useTableSelection.ts (+4 more). Pair on, review, or document these before any departure.
Interpolated log message defeats structured logging aksel.nav.no/website/app/(routes)/(god-praksis)/_ui/feedback/actions.ts:34— `error` at line 34 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging aksel.nav.no/website/app/(routes)/(god-praksis)/_ui/feedback/actions.ts:51— `error` at line 51 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging aksel.nav.no/website/app/(routes)/(god-praksis)/_ui/feedback/actions.ts:82— `error` at line 82 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
X7 · Silent fallback defaults· Pending state with no failure state · ×2
Pending state with no failure state @navikt/core/react/src/legacy/combobox/FilteredOptions/FilteredOptions.tsx:106— The view draws `<LoadingMessage/>` 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.
Pending state with no failure state @navikt/core/react/src/data/table/root/DataGridTableRoot.tsx:440— The view draws `<DataTableLoadingState colSpan= >` under `isLoading && loading ?. variant === "content"`, 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.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies aksel.nav.no/website/app/_auth/rcs.ts:17— Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (53 single-owned of 366 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 366 of the 1055 production source files in this repository met that bar). They are anonymized user #4 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: @navikt/core/react/src/data/drag-and-drop/drag-handler/DragAndDropDragHandler.tsx.
Documentation: no build, run or usage example apps/playroom/README.md:1— `playroom` is runnable (a `start` script in `REDACTED`) and neither `apps/playroom/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.
No ADRs found apps/playroom/package.json:6— 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 `apps/playroom/package.json` makes this repository a deployable product (line 6).
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Orphaned files with no living knowledge · ×1
Orphaned files with no living knowledge — 16 of 367 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; 367 of the 1055 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: @navikt/core/react/src/process/Process.stories.tsx, @navikt/core/react/src/form/form-summary/FormSummary.stories.tsx, @navikt/core/react/src/form/file-upload/FileUpload.stories.tsx, tooling/changelog/createMainChangelog.ts, @navikt/core/react/src/form/file-upload/FileUploadItem.stories.tsx, @navikt/core/react/src/legacy/combobox/FilteredOptions/useVirtualFocus.ts, @navikt/core/react/src/form/file-upload/root/FileUploadRoot.tsx, @navikt/core/react/src/progress-bar/ProgressBar.tsx (and 8 more). 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.
Blanket warning suppression @navikt/core/react/src/modal/helpers/dialog-polyfill.ts:3— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
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.
Logging is not universal — Only 1/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `@navikt/aksel`, `apps/mcp-server`.
No SAST REDACTED:7— 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 14 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No release approval gate REDACTED:52— The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
No app-layer HTTPS enforcement detected REDACTED:123— `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
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/10 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 — 10/17 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.
Silent fallback default in catch apps/mcp-server/src/helpers/node-cache.ts:35— `createNodeCache.cacheSet` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
Outdated (npm): @navikt/analytics-types — @navikt/analytics-types is pinned at 0.0.9; registry.npmjs.org publishes 0.0.13 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): @sanity/client — @sanity/client is pinned at 7.27.0; registry.npmjs.org publishes 8.16.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): @sanity/code-input — @sanity/code-input is pinned at 7.3.8; registry.npmjs.org publishes 7.3.16 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @sanity/color-input — @sanity/color-input is pinned at 6.1.8; registry.npmjs.org publishes 6.1.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): @sanity/image-url — @sanity/image-url is pinned at 2.1.1; registry.npmjs.org publishes 2.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.
Outdated (npm): @sanity/table — @sanity/table is pinned at 3.1.20; registry.npmjs.org publishes 3.1.21 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): @sanity/vision — @sanity/vision is pinned at 6.17.0; registry.npmjs.org publishes 6.23.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): @slack/web-api — @slack/web-api is pinned at 8.0.0; registry.npmjs.org publishes 8.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): commander — commander is pinned at 15.0.0; registry.npmjs.org publishes 15.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): fuse.js — fuse.js is pinned at 7.4.2; registry.npmjs.org publishes 7.5.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): isomorphic-dompurify — isomorphic-dompurify is pinned at 4.6.0; registry.npmjs.org publishes 4.7.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): next — next is pinned at 16.4.3; 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): next-sanity — next-sanity is pinned at 13.2.3; registry.npmjs.org publishes 13.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): react-hook-form — react-hook-form is pinned at 7.90.0; registry.npmjs.org publishes 7.92.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-markdown — react-markdown is pinned at 9.1.0; registry.npmjs.org publishes 10.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): react-rx — react-rx is pinned at 5.1.2; registry.npmjs.org publishes 7.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): rolldown — rolldown is pinned at 1.2.14; registry.npmjs.org publishes 1.3.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): sanity — sanity is pinned at 6.17.0; registry.npmjs.org publishes 6.23.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): sanity-plugin-iframe-pane — sanity-plugin-iframe-pane is pinned at 5.0.41; registry.npmjs.org publishes 5.0.43 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): sanity-plugin-media — sanity-plugin-media is pinned at 6.1.8; registry.npmjs.org publishes 6.6.3 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): semver — semver is pinned at 7.8.5; registry.npmjs.org publishes 7.8.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): styled-components — styled-components is pinned at 6.4.4; registry.npmjs.org publishes 6.6.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): unist-util-visit-parents — unist-util-visit-parents is pinned at 6.0.2; registry.npmjs.org publishes 6.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.
doc comments repeat the names @navikt/aksel-icons/util/useId.ts:29— 0 of 1 documented parameters and 0 of 3 summaries in `@navikt/aksel-icons` only repeat the member or parameter name (e.g. "" for `idOverride`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names @navikt/core/react/src/action-menu/item/ActionMenuItem.tsx:23— 1 of 39 documented parameters and 11 of 1194 summaries in `@navikt/ds-react` only repeat the member or parameter name (e.g. "Position of icon." for `iconPosition`). 3 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names aksel.nav.no/sanity-studio/schema/schema.utils.ts:63— 0 of 3 documented parameters and 0 of 8 summaries in `aksel-sanity-studio` only repeat the member or parameter name (e.g. "" for `input`). 1 documentation tag(s) are empty. Delete the restating tags, or add what the name does not say.
doc comments repeat the names aksel.nav.no/website/scripts/update-examples/parts/get-directories.ts:7— 0 of 8 documented parameters and 0 of 66 summaries in `website` only repeat the member or parameter name (e.g. "" for `directory`). 1 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.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 83 file(s) — `.storybook/main.ts`, `@navikt/aksel/src/codemod/migrations.ts`, `@navikt/aksel/src/codemod/v8-tokens/config/legacy.tokens.ts`, `@navikt/aksel/src/codemod/v8-tokens/run-tooling.ts`, `@navikt/aksel/src/migrations-config.ts`, … (+78 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1e5ac-7551-73d0-a0ff-5fd19e11d8b5 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 111 · Warnings: 552 · Recommendations: 170 · Info: 27 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 18:44 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.