Public report of prisma/orm, published 7 November 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.2). 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, 7 November 2026, 18:35 UTC · Survey ID cd_fc22434007e548a8a3d886eecd3927b9

prisma/orm

Measured 7 November 2026, 18:31 UTC, at code version 557c0d4

First survey, so nothing to compare with yet
CAI score 54out of 100 At risk

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

Maturity 92 Exemplary Architecture 72 Adequate Performance 60 Adequate Production Readiness 57 Adequate Code Health 56 Adequate Security and Compliance 47 Weak

A large codebase: 330,986 lines of product code in 96 projects, tests not counted · Estimated rebuild effort: about 6.7 person-years · Weakest lens: Security and Compliance, 47

Findings by how serious they are

84 critical 4038 serious 765 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
7 November 2026, 18:31 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

85of 85 dimensions measured by tools.
4828of 4887 findings point to an exact file and line, so you can open each one in the code. The other 59 concern the repository as a whole, such as missing documentation.
85dimensions across 6 lenses, read from 330,986 lines of product code in 96 projects.
Chapters

Executive summary

prisma/orm is rated At risk because critical security findings are open. Its score is held back because we found no encryption of stored data, no key vault and no enforced HTTPS, and it has passwords or keys in the code's history. It scores 54 out of 100, which the At risk rating leaves unchanged.

Security and Compliance, at 47, is the weakest lens and counts most in the score. The best first step is encrypting the sensitive stored data and keeping its keys in a vault, worth about 6 points. Replacing the 26 passwords or keys found in the code's history comes next, worth about 4 points. Raising Security and Compliance to 70 would lift the score to about 59.

Thirty-one passwords or keys are open to anyone who can read the repository. Thirty known security holes in the packages the code depends on can be used by attackers. Replacing each exposed password or key and updating the vulnerable packages would close both risks. Pinning each tool to an exact version would fix the three pipeline tools referenced by a changeable name, and setting a waiting period for automatic updates would deal with the automatic dependency update that takes a new release at once. The 12 tests that check nothing need to check the result they produce.

The product code is 330,986 lines, about €980,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.

Code Health 56 Adequate, capped by Cognitive Complexity and Nullable reference types Architecture 72 Adequate, capped by Circular Imports Maturity 92 ★ Exemplary Production Readiness 57 Adequate, capped by Dependency Hygiene Security and Compliance 47 Weak, capped by Secrets (history), Static Analysis (SAST) and Data Protection Performance 60 Adequate

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

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

If Security and Compliance rose from 47 to 70, the lowest score rated Strong, the score would rise from 54 to about 59.

Code composition: what the lines of code are
Product code 33%Tests 67%
Rebuild cost: about €980,000 · Estimate
Cost to rebuild€330,000 to €1,600,000, for 5,425 to 17,212 hours of work, about 6.7 person-years for 4 to 13 engineers
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 54. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeLarge: 330,986 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault).
Skip if delegated to infra (Postgres TDE, KMS, etc.).
Raises the score by about 6 points · Medium effort · Data Protection
2
Resolve the 26 High secret finding(s) in Secrets (history) — start with REDACTED (13), REDACTED (6), REDACTED (5).
Raises the score by about 4 points · Medium effort · Secrets (history)
3
Resolve the 26 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25), REDACTED.
Raises the score by about 4 points · Medium effort · Dependency Vulnerabilities

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €980,000 to build again, about 6.7 person-years of work. Its weakest lens is Security and Compliance, at 47 (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
Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Of all the actions in this report, it raises the score most for the work it takes: about 6 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 1,058,376 lines over the last 90 days, which is about 4,292,303 lines a year. At that pace, the extra work comes to an estimated 416.9 to 2501.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.

arch @internal/adapter-mongo adapter-mongo @internal/config config @internal/adapter-mongo->@internal/config @internal/contract contract @internal/adapter-mongo->@internal/contract @internal/errors errors @internal/adapter-mongo->@internal/errors @internal/family-mongo family-mongo @internal/adapter-mongo->@internal/family-mongo @internal/framework-components framework-components @internal/adapter-mongo->@internal/framework-components @internal/migration-tools migration-tools @internal/adapter-mongo->@internal/migration-tools @internal/utils utils @internal/adapter-mongo->@internal/utils @internal/adapter-postgres adapter-postgres @internal/adapter-postgres->@internal/contract @internal/contract-authoring contract-authoring @internal/adapter-postgres->@internal/contract-authoring @internal/adapter-postgres->@internal/errors @internal/family-sql family-sql @internal/adapter-postgres->@internal/family-sql @internal/adapter-postgres->@internal/framework-components @internal/sql-contract sql-contract @internal/adapter-postgres->@internal/sql-contract @internal/sql-relational-core sql-relational-core @internal/adapter-postgres->@internal/sql-relational-core @internal/sql-runtime sql-runtime @internal/adapter-postgres->@internal/sql-runtime @internal/target-postgres target-postgres @internal/adapter-postgres->@internal/target-postgres @internal/adapter-postgres->@internal/utils @internal/adapter-sqlite adapter-sqlite @internal/cli cli @internal/adapter-sqlite->@internal/cli @internal/adapter-sqlite->@internal/contract @internal/adapter-sqlite->@internal/contract-authoring @internal/adapter-sqlite->@internal/errors @internal/adapter-sqlite->@internal/family-sql @internal/adapter-sqlite->@internal/framework-components @internal/adapter-sqlite->@internal/sql-contract @internal/adapter-sqlite->@internal/sql-relational-core @internal/adapter-sqlite->@internal/sql-runtime @internal/adapter-sqlite->@internal/utils @internal/cli->@internal/config @internal/cli->@internal/contract @internal/cli->@internal/errors @internal/cli->@internal/framework-components @internal/cli->@internal/migration-tools @internal/cli->@internal/utils @internal/config->@internal/contract @internal/config->@internal/framework-components @internal/config->@internal/utils @internal/contract->@internal/utils @internal/contract-authoring->@internal/contract @internal/contract-authoring->@internal/errors @internal/contract-authoring->@internal/framework-components @internal/contract-authoring->@internal/utils @internal/errors->@internal/framework-components @internal/errors->@internal/utils @internal/extension-supabase extension-supabase @internal/extension-supabase->@internal/adapter-postgres @internal/extension-supabase->@internal/contract @internal/extension-supabase->@internal/contract-authoring @internal/extension-supabase->@internal/family-sql @internal/extension-supabase->@internal/framework-components @internal/extension-supabase->@internal/migration-tools @internal/postgres postgres @internal/extension-supabase->@internal/postgres @internal/extension-supabase->@internal/sql-contract @internal/extension-supabase->@internal/sql-relational-core @internal/extension-supabase->@internal/sql-runtime @internal/extension-supabase->@internal/target-postgres @internal/extension-supabase->@internal/utils @internal/family-mongo->@internal/contract @internal/family-mongo->@internal/contract-authoring @internal/family-mongo->@internal/errors @internal/family-mongo->@internal/framework-components @internal/family-mongo->@internal/migration-tools @internal/family-mongo->@internal/utils @internal/family-sql->@internal/contract @internal/family-sql->@internal/contract-authoring @internal/family-sql->@internal/framework-components @internal/family-sql->@internal/migration-tools @internal/family-sql->@internal/sql-contract @internal/family-sql->@internal/sql-relational-core @internal/family-sql->@internal/utils @internal/framework-components->@internal/contract @internal/framework-components->@internal/utils @internal/migration-tools->@internal/contract @internal/migration-tools->@internal/errors @internal/migration-tools->@internal/framework-components @internal/migration-tools->@internal/utils @internal/postgres->@internal/adapter-postgres @internal/postgres->@internal/cli @internal/postgres->@internal/config @internal/postgres->@internal/contract @internal/postgres->@internal/family-sql @internal/postgres->@internal/framework-components @internal/postgres->@internal/sql-contract @internal/postgres->@internal/sql-relational-core @internal/postgres->@internal/sql-runtime @internal/postgres->@internal/target-postgres @internal/postgres->@internal/utils @internal/sql-contract->@internal/contract @internal/sql-contract->@internal/framework-components @internal/sql-contract->@internal/utils @internal/sql-relational-core->@internal/contract @internal/sql-relational-core->@internal/framework-components @internal/sql-relational-core->@internal/sql-contract @internal/sql-relational-core->@internal/utils @internal/sql-runtime->@internal/contract @internal/sql-runtime->@internal/framework-components @internal/sql-runtime->@internal/sql-contract @internal/sql-runtime->@internal/sql-relational-core @internal/sql-runtime->@internal/utils @internal/target-postgres->@internal/cli @internal/target-postgres->@internal/contract @internal/target-postgres->@internal/errors @internal/target-postgres->@internal/family-sql @internal/target-postgres->@internal/framework-components @internal/target-postgres->@internal/migration-tools @internal/target-postgres->@internal/sql-contract @internal/target-postgres->@internal/sql-relational-core @internal/target-postgres->@internal/utils @prisma/orm-framework orm-framework __more__ +76 more projects

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.

1241 modules, with 3437 dependencies between them. 9 loops run through 26 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 1201 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 packages.1-framework.0-foundation.contract.src.domain-types2 packages.1-framework.0-foundation.contract.src.types3 packages.1-framework.0-foundation.utils.src.result4 packages.1-framework.0-foundation.utils.src.structured-error5 packages.1-framework.1-core.config.src.config-types6 packages.1-framework.1-core.framework-components.src.control.migration-statements7 packages.1-framework.1-core.framework-components.src.control.schema-diff8 packages.2-sql-family.4-lanes.relational-core.src.ast.driver-types9 skills.prisma-8.upgrading.app.upgrades.8_0_0-rc_14-to-8_0_0-rc_15.scripts.data-type-in-contract.data-type-in-contract10 packages.1-framework.0-foundation.contract.src.contract-types11 packages.1-framework.1-core.framework-components.src.shared.codec12 packages.1-framework.1-core.framework-components.src.shared.written-value13 packages.2-sql-family.1-core.contract.src.ir.sql-storage14 packages.1-framework.1-core.framework-components.src.shared.codec-types15 packages.1-framework.1-core.framework-components.src.shared.psl-extension-block16 packages.1-framework.3-tooling.cli.src.control-api.types17 packages.1-framework.1-core.framework-components.src.shared.framework-authoring18 packages.1-framework.2-authoring.psl-parser.src.source-file19 packages.2-sql-family.4-lanes.relational-core.src.ast.types20 packages.1-framework.1-core.framework-components.src.control.control-stack21 packages.1-framework.1-core.framework-components.src.shared.framework-components22 packages.1-framework.2-authoring.psl-parser.src.symbol-table23 packages.2-sql-family.2-authoring.contract-ts.src24 packages.2-sql-family.5-runtime.src.sql-runtime25 packages.3-targets.postgres.1-target.src.core26 packages.1-framework.1-core.framework-components.src.control.control-migration-types27 packages.1-framework.2-authoring.psl-parser.src.binder28 packages.2-sql-family.9-family.src.core.control-adapter29 packages.3-extensions.sql-orm-client.src30 packages.1-framework.2-authoring.psl-parser.src31 packages.1-framework.3-tooling.cli.src.control-api.operations32 packages.1-framework.3-tooling.language-server.src33 packages.1-framework.3-tooling.migration.src.migration-base34 packages.2-mongo-family.2-authoring.contract-psl.src35 packages.2-sql-family.2-authoring.contract-psl.src36 packages.2-sql-family.9-family.src.core.migrations.types37 packages.2-sql-family.9-family.src.core38 packages.2-sql-family.9-family.src.core.migrations39 packages.3-targets.postgres.1-target.src.core.migrations40 packages.3-targets.sqlite.1-target.src.core.migrations
1 packages.1-framework.0-foundation.contract.src.domain-types
2 packages.1-framework.0-foundation.contract.src.types
3 packages.1-framework.0-foundation.utils.src.result
4 packages.1-framework.0-foundation.utils.src.structured-error
5 packages.1-framework.1-core.config.src.config-types
6 packages.1-framework.1-core.framework-components.src.control.migration-statements
7 packages.1-framework.1-core.framework-components.src.control.schema-diff
8 packages.2-sql-family.4-lanes.relational-core.src.ast.driver-types
9 skills.prisma-8.upgrading.app.upgrades.8_0_0-rc_14-to-8_0_0-rc_15.scripts.data-type-in-contract.data-type-in-contract
10 packages.1-framework.0-foundation.contract.src.contract-types1
11 packages.1-framework.1-core.framework-components.src.shared.codec12
12 packages.1-framework.1-core.framework-components.src.shared.written-value2
13 packages.2-sql-family.1-core.contract.src.ir.sql-storage2
14 packages.1-framework.1-core.framework-components.src.shared.codec-types21
15 packages.1-framework.1-core.framework-components.src.shared.psl-extension-block1
16 packages.1-framework.3-tooling.cli.src.control-api.types1122
17 packages.1-framework.1-core.framework-components.src.shared.framework-authoring11
18 packages.1-framework.2-authoring.psl-parser.src.source-file1
19 packages.2-sql-family.4-lanes.relational-core.src.ast.types2
20 packages.1-framework.1-core.framework-components.src.control.control-stack1112
21 packages.1-framework.1-core.framework-components.src.shared.framework-components2
22 packages.1-framework.2-authoring.psl-parser.src.symbol-table72
23 packages.2-sql-family.2-authoring.contract-ts.src2431311132
24 packages.2-sql-family.5-runtime.src.sql-runtime7224
25 packages.3-targets.postgres.1-target.src.core622123
26 packages.1-framework.1-core.framework-components.src.control.control-migration-types52
27 packages.1-framework.2-authoring.psl-parser.src.binder245
28 packages.2-sql-family.9-family.src.core.control-adapter1111
29 packages.3-extensions.sql-orm-client.src143117217463
30 packages.1-framework.2-authoring.psl-parser.src41331712016
31 packages.1-framework.3-tooling.cli.src.control-api.operations172415105
32 packages.1-framework.3-tooling.language-server.src1491713
33 packages.1-framework.3-tooling.migration.src.migration-base12
34 packages.2-mongo-family.2-authoring.contract-psl.src111111112131
35 packages.2-sql-family.2-authoring.contract-psl.src121211162343163
36 packages.2-sql-family.9-family.src.core.migrations.types3326
37 packages.2-sql-family.9-family.src.core23112112211211
38 packages.2-sql-family.9-family.src.core.migrations241121591071521
39 packages.3-targets.postgres.1-target.src.core.migrations117710523312
40 packages.3-targets.sqlite.1-target.src.core.migrations3133114434
Uses a module listed above itPart of a loopThe module itself
1 packages.1-framework.0-foundation.contract.src.domain-types2 packages.1-framework.0-foundation.contract.src.types3 packages.1-framework.0-foundation.utils.src.result4 packages.1-framework.0-foundation.utils.src.structured-error5 packages.1-framework.1-core.config.src.config-types6 packages.1-framework.1-core.framework-components.src.control.migration-statements7 packages.1-framework.1-core.framework-components.src.control.schema-diff8 packages.2-sql-family.4-lanes.relational-core.src.ast.driver-types9 skills.prisma-8.upgrading.app.upgrades.8_0_0-rc_14-to-8_0_0-rc_15.scripts.data-type-in-contract.data-type-in-contract10 packages.1-framework.0-foundation.contract.src.contract-types11 packages.1-framework.1-core.framework-components.src.shared.codec12 packages.1-framework.1-core.framework-components.src.shared.written-value13 packages.2-sql-family.1-core.contract.src.ir.sql-storage14 packages.1-framework.1-core.framework-components.src.shared.codec-types15 packages.1-framework.1-core.framework-components.src.shared.psl-extension-block16 packages.1-framework.3-tooling.cli.src.control-api.types17 packages.1-framework.1-core.framework-components.src.shared.framework-authoring18 packages.1-framework.2-authoring.psl-parser.src.source-file19 packages.2-sql-family.4-lanes.relational-core.src.ast.types20 packages.1-framework.1-core.framework-components.src.control.control-stack21 packages.1-framework.1-core.framework-components.src.shared.framework-components22 packages.1-framework.2-authoring.psl-parser.src.symbol-table23 packages.2-sql-family.2-authoring.contract-ts.src24 packages.2-sql-family.5-runtime.src.sql-runtime25 packages.3-targets.postgres.1-target.src.core26 packages.1-framework.1-core.framework-components.src.control.control-migration-types27 packages.1-framework.2-authoring.psl-parser.src.binder28 packages.2-sql-family.9-family.src.core.control-adapter29 packages.3-extensions.sql-orm-client.src30 packages.1-framework.2-authoring.psl-parser.src31 packages.1-framework.3-tooling.cli.src.control-api.operations32 packages.1-framework.3-tooling.language-server.src33 packages.1-framework.3-tooling.migration.src.migration-base34 packages.2-mongo-family.2-authoring.contract-psl.src35 packages.2-sql-family.2-authoring.contract-psl.src36 packages.2-sql-family.9-family.src.core.migrations.types37 packages.2-sql-family.9-family.src.core38 packages.2-sql-family.9-family.src.core.migrations39 packages.3-targets.postgres.1-target.src.core.migrations40 packages.3-targets.sqlite.1-target.src.core.migrationspackages.1-framework.0-foundation.contract.src.domain-types1packages.1-framework.0-foundation.contract.src.types2packages.1-framework.0-foundation.utils.src.result3packages.1-framework.0-foundation.utils.src.structured-error4packages.1-framework.1-core.config.src.config-types5packages.1-framework.1-core.framework-components.src.control.migration-statements6packages.1-framework.1-core.framework-components.src.control.schema-diff7packages.2-sql-family.4-lanes.relational-core.src.ast.driver-types8skills.prisma-8.upgrading.app.upgrades.8_0_0-rc_14-to-8_0_0-rc_15.scripts.data-type-in-contract.data-type-in-contract9packages.1-framework.0-foundation.contract.src.contract-types10packages.1-framework.1-core.framework-components.src.shared.codec11packages.1-framework.1-core.framework-components.src.shared.written-value12packages.2-sql-family.1-core.contract.src.ir.sql-storage13packages.1-framework.1-core.framework-components.src.shared.codec-types14packages.1-framework.1-core.framework-components.src.shared.psl-extension-block15packages.1-framework.3-tooling.cli.src.control-api.types16packages.1-framework.1-core.framework-components.src.shared.framework-authoring17packages.1-framework.2-authoring.psl-parser.src.source-file18packages.2-sql-family.4-lanes.relational-core.src.ast.types19packages.1-framework.1-core.framework-components.src.control.control-stack20packages.1-framework.1-core.framework-components.src.shared.framework-components21packages.1-framework.2-authoring.psl-parser.src.symbol-table22packages.2-sql-family.2-authoring.contract-ts.src23packages.2-sql-family.5-runtime.src.sql-runtime24packages.3-targets.postgres.1-target.src.core25packages.1-framework.1-core.framework-components.src.control.control-migration-types26packages.1-framework.2-authoring.psl-parser.src.binder27packages.2-sql-family.9-family.src.core.control-adapter28packages.3-extensions.sql-orm-client.src29packages.1-framework.2-authoring.psl-parser.src30packages.1-framework.3-tooling.cli.src.control-api.operations31packages.1-framework.3-tooling.language-server.src32packages.1-framework.3-tooling.migration.src.migration-base33packages.2-mongo-family.2-authoring.contract-psl.src34packages.2-sql-family.2-authoring.contract-psl.src35packages.2-sql-family.9-family.src.core.migrations.types36packages.2-sql-family.9-family.src.core37packages.2-sql-family.9-family.src.core.migrations38packages.3-targets.postgres.1-target.src.core.migrations39packages.3-targets.sqlite.1-target.src.core.migrations401122221111221112111227224313111327224622123522451111143117217463413317120161724151051491713121111111121311212111623431633326231121122112112411215910715211177105233123133114434+1201 more modules (most-connected shown)

At a glance — Code Health · 56% · Adequate · gated by D2, X5 ·

The Good
D3 · TypeScript God Classes 8.2 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 IC1 · Repo Incompleteness & stubs 7.6 R1 · React / TS Type Safety 9.8 R10 · React / TS Code Duplication 8.8 R2 · React / TS Cyclomatic Complexity 8.0 R7 · React / TS Dead Code 7.8 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X2 · Repo Cancellation propagation 7.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0
The Bad
D1 · TypeScript Cyclomatic Complexity 6.1 R3 · React / TS Large Files 6.7 X3 · Repo Exception handling 5.9
The Ugly
D2 · TypeScript Cognitive Complexity 3.3 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 72% · Adequate · gated by R9 ·

The Good
D5 · TypeScript Coupling 7.4 D6 · TypeScript Cohesion (LCOM4) 9.9 D23 · TypeScript Boundary Type-Coupling 10.0 D26 · TypeScript Project Cohesion 8.1 D35 · TypeScript Change Coupling 9.9 AX10 · Repo Code composition 8.7 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 9.9 AX8 · Repo Test isolation 10.0 R11 · React / TS Import Boundaries 8.8
The Bad
D7 · TypeScript Architectural Integrity 6.0
The Ugly
R9 · React / TS Circular Imports 2.7

At a glance — Maturity · 92% · Exemplary ·

The Good
D15 · TypeScript Churn × Complexity Hotspots 9.9 D16 · TypeScript Bus Factor 7.9 D19 · TypeScript Documentation Quality 8.3 D20 · TypeScript ADR Quality 8.5 D21 · TypeScript Naming Consistency 9.4 D24 · TypeScript Comment Value 9.3 D34 · TypeScript Knowledge Freshness 9.7 M1 · Repo Documentation (README) 9.2 M2 · Repo Architecture documentation 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 8.6
The Bad
D25 · TypeScript ADR Conformance 5.0

At a glance — Readiness · 57% · Adequate · gated by R8 ·

The Good
D8 · TypeScript Code Coverage 9.9 D9 · TypeScript Test Distribution 9.6 D10 · TypeScript Test Quality 8.7 D11 · TypeScript Test Reliability 10.0 D13 · TypeScript REDACTED Scanning 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 P8 · Repo Schema migrations 10.0 R4 · React / TS Test Coverage 8.5 R6 · React / TS Tooling 10.0
The Bad
P2 · Repo Observability 5.3
The Ugly
R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 47% · Weak · gated by D28, D29, C1 ·

The Good
D31 · TypeScript IaC & Container Security 9.8 D37 · TypeScript Vulnerability-disclosure Policy 10.0 D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 C2 · Repo Access Controls 7.0 C3 · Repo Audit Trail 7.5 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0
The Bad
D36 · TypeScript Supply-chain Provenance & Signing 5.0 C4 · Repo Data Retention 6.5
The Ugly
D28 · TypeScript Secrets (history) 0.0 D29 · TypeScript Static Analysis (SAST) 0.8 D30 · TypeScript Dependency Vulnerabilities 0.0 C1 · Repo Data Protection 0.0 X17 · Repo Uncapped recursion over a caller-supplied document 1.1

At a glance — Performance · 60% · Adequate ·

The Bad
PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures45High / Critical
A05:2025 — Injection41High / Critical
A07:2025 — Authentication Failures32High / Critical
A02:2025 — Security Misconfiguration2Medium

Roadmap

Top priorities: Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.); Resolve the 26 High secret finding(s) in Secrets (history) — start with REDACTED (13), REDACTED (6), REDACTED (5); Resolve the 26 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25), REDACTED.

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

Do thisHelpsEffortDimension
Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).+5.7 ptsMediumData Protection
Resolve the 26 High secret finding(s) in Secrets (history) — start with REDACTED (13), REDACTED (6), REDACTED (5).+4.5 ptsMediumSecrets (history)
Resolve the 26 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (25), REDACTED.+3.8 ptsMediumDependency Vulnerabilities
Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2).+1.2 ptsLowSecrets (history)
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+1.2 ptsLowStatic Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+1.2 ptsLowStatic Analysis (SAST)
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED.+1.2 ptsLowDependency Vulnerabilities
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2).+1.2 ptsLowDependency Vulnerabilities

File quality

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

FileScoreBandWorst signal
REDACTED0.0SlopSecrets (history): High secret: REDACTED
packages/3-extensions/middleware-cache/test/cache-middleware.types.test-d.ts3.5SlopTest Quality: No assertions (empty test): invalidate rejects other shapes
REDACTED3.5SlopStatic Analysis (SAST): High: REDACTED
REDACTED4.5MixedSecrets (history): High secret: REDACTED
REDACTED4.6MixedSecrets (history): High secret: REDACTED
REDACTED4.6MixedSecrets (history): High secret: REDACTED
scripts/download-mongod-binary.test.mjs4.8MixedTest Quality: No assertions (empty test): deletes a binary that does not run, removes locks and downloads again
packages/1-framework/1-core/framework-components/test/runtime-core.types.test-d.ts4.8MixedTest Quality: No assertions (empty test): a minimal RuntimeCore subclass typechecks
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED4.9MixedStatic Analysis (SAST): Medium: REDACTED
packages/3-extensions/sql-orm-client/test/collection-chaining.types.test-d.ts5.0MixedTest Quality: No assertions (empty test): firstOrThrow returns the row of first without null for a registered class
REDACTED5.1MixedSecrets (history): REDACTED: REDACTED
REDACTED5.1MixedStatic Analysis (SAST): High: REDACTED
scripts/retry-command.test.mjs5.2MixedTest Quality: No assertions (empty test): throws the last error once every attempt fails
REDACTED5.3MixedStatic 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 — 84

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 — 4038

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 — 765

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

Could not be resolved — 8

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 85 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 — 85 dimensions across the health lenses
D1D2D3D5D6D7D8D9D10D11D13D15D16D17D19D20D21D23D24D25D26D28D29D30D31D34D35D36D37D43D44AX10AX3AX4AX6AX8C1C2C3C4GD1IC1M1M2M3M4P1P10P2P3P4P6P8PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X5

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

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

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

Tools & methods

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

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

Every finding is locatable in findings.md. Run 01a1b747-e829-7f50-9731-da80652188b0.

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

Run transparency — what happened this run

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

  • D7 Architectural Integrity — 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. These records DO declare how the decision is enforced; FileSystemAdrInventoryBuilder.ParseEnforcement maps a fixed vocabulary (`prose`, `test`, `analyzer`, `mechanical`, `judgment`, `judgement`, `process`, `not-applicable`) and these values are outside it. Each was therefore treated as Unclassified: counted into the mechanizable set, but excluded from the scored set because nothing claimed it enforceable. That exclusion rests on our word list, not on the repository. Affected ADR(s): docs/architecture docs/adrs/ADR 106 - Canonicalization for extensions.md, docs/architecture docs/adrs/ADR 140 - Package Layering & Target-Family Namespacing.md, docs/architecture docs/adrs/ADR 248 - PostgreSQL floor lowered to 15.md. You can widen what we reach: no action is needed from this repository — the gap is in our parser. The values above are reported so the vocabulary can be added; declaring `enforcement: analyzer`, `test`, `prose` or `not-applicable` alongside your own grading would settle these ADRs immediately.
  • D8 Code 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. 4 test file(s) failed while being loaded here, so none of their cases ran (typically a native addon or generated module the package's install scripts build, which the analyzer's scripts-off install does not run). The 2 production file(s) those files import that read under half covered are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 77.1% rather than published as low coverage. You can widen what we reach: optional: commit the lcov report of a run where those test files load, and their modules are read from it.
  • D11 Test Reliability — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the vitest run in the repository root produced no per-test report (⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯). 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in examples/mongo-demo/ was NOT MEASURED: the vitest run in examples/mongo-demo/ produced no per-test report (⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯). 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in examples/multi-extension-monorepo/ was NOT MEASURED: the vitest run in examples/multi-extension-monorepo/ produced no per-test report (⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯). 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in examples/paradedb-demo/ was NOT MEASURED: the vitest run in examples/paradedb-demo/ produced no per-test report (⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯). 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in examples/prisma-8-demo/ was NOT MEASURED: the vitest run in examples/prisma-8-demo/ produced no per-test report (⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯). 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 — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Test reliability for the vitest suite in examples/prisma-8-postgis-demo/ was NOT MEASURED: the vitest run in examples/prisma-8-postgis-demo/ produced no per-test report (⎯⎯⎯⎯⎯⎯⎯ Startup Error ⎯⎯⎯⎯⎯⎯⎯⎯). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
  • D12 Dependency Hygiene — 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 repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because registry.npmjs.org — the registry that answers it — was asked and did not reply (registry returned 429). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add registry.npmjs.org to the allowlist and re-run — not to build anything.
  • D14 License Compliance — 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. License Compliance couldn't be assessed within its 15-minute budget on a solution this large — not included in this run.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (packages/9-public/@prisma/orm-toolchain/package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • 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. `REDACTED`, `apps/telemetry-backend/src/db.ts`, `apps/telemetry-backend/src/handler.ts`, `apps/telemetry-backend/src/schema.ts`, `dependency-cruiser.config.mjs`, … (+198 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository defines its own container in packages/3-extensions/sql-orm-client/src/types.ts, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • 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. User interface: 1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. Boot: crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5434: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5434/ Call log: - navigating to "http://127.0.0.1:5434/", waiting until "load" .
  • 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.
  • PF3 Async & latency hygiene — 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. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
  • 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. 799 further occurrence(s) are not listed individually; the score already reflects all 839.
  • R11 Import Boundaries — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 27 further occurrence(s) are not listed individually; the score already reflects all 67.
  • R3 Large Files — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 131 further occurrence(s) are not listed individually; the score already reflects all 171.
  • 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. 112 further occurrence(s) are not listed individually; the score already reflects all 152.
  • 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. 122 further occurrence(s) are not listed individually; the score already reflects all 162.
  • X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 29 further occurrence(s) are not listed individually; the score already reflects all 69.
  • X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.

Repo exclusion declarations: 9 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.

Limitations & what we did not check

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

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
  • 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.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
  • D25 ADR Conformance: ADR conformance checks only decisions stated in a checkable form (a ruled-out element, package or dependency, an adr-rules block, a declared delivery status): a decision written only as prose is unverifiable, and decisions never written down are not checked.
  • 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.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
  • 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.
  • C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
  • C4 Data Retention: This control is scored from in-repo evidence only — its real-world effectiveness, exercised only at runtime, is outside a static scan.
  • 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.

Dimensions

D1 · Cyclomatic Complexity6.1 / 10Adequate✓ Tool-verified

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

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

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

298 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was interpreter.buildModelNodeFromPsl at 93. A further 17 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 issue-planner.classifyCall at 44 — they are counted neither in the figure above nor in this dimension's score. 8 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/3-targets/mysql/2-adapter/src/core/sql-renderer.ts (sql-renderer.renderExpr at 26), packages/3-targets/postgres/2-adapter/src/core/sql-renderer.ts (sql-renderer.renderExpr at 26), packages/3-targets/postgres/1-target/src/core/codec-descriptor.ts (codec-descriptor.isPostgresCodecDescriptor at 23), packages/3-targets/mongo/2-adapter/src/mongo-adapter.ts (MongoAdapterImpl.structuralLower at 22), packages/2-mongo-family/7-runtime/src/param-ref-mutator.ts (param-ref-mutator.flattenMongoParamRefs at 21), and 3 more not listed here. 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.

data-type-in-contract.main (cyclomatic 63) · ×4REDACTED:1292
data-type-in-contract.rewriteDts (cyclomatic 53) · ×4REDACTED:1037
data-type-in-contract.rewriteSqliteEnums (cyclomatic 45) · ×4REDACTED:565
rewrite-sql-strings.stringRanges (cyclomatic 35) · ×4scripts/codemods/rewrite-sql-strings.mjs:160
expand-type-aliases.rewriteContract (cyclomatic 27) · ×4skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:456

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

What to do

  1. Bring the 20 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with interpreter.buildModelNodeFromPsl (cyclomatic 93), interpreter.readField (cyclomatic 88), interpreter.interpretPslDocumentToSqlContract (cyclomatic 84). — 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 20 together lifts Cyclomatic Complexity from 6.1 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D2 · Cognitive Complexity3.3 / 10Weak✓ Tool-verified

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

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

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

557 method(s) exceeded the cognitive complexity threshold of 15; the worst was interpreter.buildModelNodeFromPsl at 202.

add-model-map.addModelMapsWithReport (cognitive 21) · ×5scripts/codemods/add-model-map.mjs:147
data-type-in-contract.rewriteSqliteEnums (cognitive 99) · ×4REDACTED:565
data-type-in-contract.main (cognitive 97) · ×4REDACTED:1292
rewrite-sql-strings.stringRanges (cognitive 74) · ×4scripts/codemods/rewrite-sql-strings.mjs:160
data-type-in-contract.rewriteDts (cognitive 62) · ×4REDACTED:1037

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

What to do

  1. Bring the 5 bodies over 120 down to 120 or less in Cognitive Complexity — start with interpreter.buildModelNodeFromPsl (cognitive 202), interpreter.interpretPslDocumentToSqlContract (cognitive 140), migration-graph-grid-layout.buildGrid (cognitive 138). — 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 5 together lifts Cognitive Complexity from 3.3 to about 4.3/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
  2. Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D3 · God Classes8.2 / 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.

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

174 god class(es) detected.

FileTooLong: migrations/op-factory-call.ts · ×85packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts
FunctionTooLong: interpreter.buildModelNodeFromPsl · ×67packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:615
ClassTooLong: CollectionBase · ×10packages/3-extensions/sql-orm-client/src/collection.ts:389
MethodTooLong: PostgresControlAdapter.introspectSchema · ×6packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:859
TooManyMethods: CollectionBase · ×6packages/3-extensions/sql-orm-client/src/collection.ts:389

What to do

  1. Resolve the 85 FileTooLong finding(s) in God Classes — start with interpreter.ts (4), remove-nocheck.ts (4), REDACTED (4). — One of this dimension's main actionable groups (85 warning-level).
  2. Resolve the 67 FunctionTooLong finding(s) in God Classes — start with interpreter.ts (7), control-instance.ts (4), query-plan-select.ts (3). — One of this dimension's main actionable groups (67 warning-level).
  3. Resolve the 10 ClassTooLong finding(s) in God Classes — start with collection.ts (2), control-adapter.ts (2), runner.ts (2). — One of this dimension's main actionable groups (10 warning-level).
  4. Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D5 · Coupling7.4 / 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.

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

96 production modules (npm), 0 dependency cycle(s), 18 unstable depended-on module(s). Read from the build's own module declarations; 11 module(s) off the main sequence, with abstractness counted on 76 of the 96 (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: @internal/mongo-value · ×9
Unstable project @internal/adapter-mongo
Unstable project @internal/adapter-mysql
Unstable project @internal/adapter-sqlite
Unstable project @internal/driver-mongo

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

What to do

  1. Resolve the 9 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (9 warning-level).
  2. Resolve the 1 Unstable project @internal/adapter-mongo finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 Unstable project @internal/adapter-mysql finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
  4. Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D6 · Cohesion (LCOM4)9.9 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

1 of 229 classes have LCOM4 above 3.

Low cohesion: MysqlControlAdapter (LCOM4 5)packages/3-targets/mysql/2-adapter/src/core/migrations/control-adapter.ts:55

What to do

  1. Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with control-adapter.ts. — One of this dimension's main actionable groups (1 warning-level).
  2. Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D7 · Architectural Integrity6.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code respects its intended layering / architecture rules.

Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.

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

No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).

Classify ADR enforcement: ADR 001 — Migrations as Edges · ×235docs/architecture docs/adrs/ADR 001 - Migrations as Edges.md

What to do

  1. Resolve the 235 Classify ADR enforcement finding(s) in Architectural Integrity — start with ADR 001 - Migrations as Edges.md, ADR 002 - Plans are Immutable.md, ADR 003 - One Query One Statement.md. — One of this dimension's main actionable groups (235 recommendation-level).
  2. Enforce Architectural Integrity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D8 · Code Coverage9.9 / 10Exemplary✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

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

Line coverage 77.1%. Measured from the JavaScript/TypeScript suite (vitest in the repository root: not run; vitest + @vitest/coverage-v8 via `pnpm install --frozen-lockfile --ignore-scripts` in apps/telemetry-backend/; vitest in examples/bundle-size/: not run; vitest in examples/mongo-blog-leaderboard/: not run; vitest in examples/mongo-demo/: not run; vitest in examples/multi-extension-monorepo/: not run; vitest in examples/paradedb-demo/: not run; vitest in examples/prisma-8-cloudflare-worker/: not run; vitest in examples/prisma-8-demo/: not run; vitest in examples/prisma-8-demo-mysql/: not run; vitest in examples/prisma-8-demo-sqlite/: not run; vitest in examples/prisma-8-postgis-demo/: not run).

✓ On the Gold path — maintain.

Detailed fixes: d8_recommendation.md.

D9 · Test Distribution9.6 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

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

28162 test methods: 24587 unit, 2770 integration, 0 BDD, 805 e2e. The JavaScript/TypeScript suite contributes 28162 `it`/`test` case(s) across 3321 test file(s) declaring at least one; its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality8.7 / 10Adequategated by 12 critical 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.

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

54 skipped (52 with a documented reason), 2481 zero-assertion, 8 synchronised by a fixed sleep, no mocking-framework packages referenced (hand-written doubles or no mocking) across 28162 tests (1 harness-style project(s) excluded from the assertion penalty).

No assertions (empty test): high concurrency with write conflicts · ×12test/integration/test/ports/prisma/functional/interactive-transactions/interactive-transactions.test.ts:190
No assertions: passes when each destructive operation is named · ×2463test/utils/test/data-loss-expectations.test.ts:11
Fixed-sleep synchronisation: close() closes the client in the same call, so a lazy read awaited a turn of the event loop later is refused · ×8packages/3-targets/postgres/9-facade/test/postgres-close.test.ts:452
Skipped test: MYSQL_URL is not set · ×2test/utils/test/mysql-database.test.ts:31
Mock-dominated test: receives the marker-verification warning when the database has no marker · ×28packages/3-targets/sqlite/9-facade/test/sqlite-log.test.ts:31

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

What to do

  1. Resolve the 12 No assertions (empty test) finding(s) in Test Quality — start with cache-middleware.types.test-d.ts (3), download-mongod-binary.test.mjs (2), runtime-core.types.test-d.ts (2). — One of this dimension's main actionable groups (12 issue-level).
  2. Resolve the 2463 No assertions finding(s) in Test Quality — start with annotations.types.test-d.ts (72), orm-types.test-d.ts (65), contract-builder.types.test-d.ts (59). — One of this dimension's main actionable groups (2463 warning-level).
  3. Resolve the 8 Fixed-sleep synchronisation finding(s) in Test Quality — start with transaction-activity.test.ts (3), client-activity.test.ts (2), postgres-close.test.ts. — One of this dimension's main actionable groups (8 warning-level).
  4. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the tests pass reliably, with no flakiness.

Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.

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

0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in apps/telemetry-backend/ (17 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/bundle-size/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/mongo-blog-leaderboard/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/mongo-demo/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/multi-extension-monorepo/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/paradedb-demo/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/prisma-8-cloudflare-worker/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/prisma-8-demo/; vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/prisma-8-demo-mysql/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/prisma-8-demo-sqlite/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in examples/prisma-8-postgis-demo/): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

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

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

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

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

REDACTED scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots9.9 / 10Stronggated by 97 serious findings✓ Tool-verified

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

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

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

Top hotspots: packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts (48×93=4464); examples/prisma-8-demo/src/main.ts (16×168=2688); packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts (29×88=2552)

Hotspot: packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts · ×97packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:615

What to do

  1. Resolve the 97 Hotspot finding(s) in Churn × Complexity Hotspots — start with interpreter.ts (4), REDACTED (3), issue-planner.ts (2). — One of this dimension's main actionable groups (97 warning-level).

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

D16 · Bus Factor7.9 / 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.

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

208 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts. Counted over 1004 of the 2201 production source files in this repository: 1196 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 · ×4
Further sole-owners (lower concentration)

What to do

  1. Resolve the 4 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (4 recommendation-level).
  2. 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.

D17 · Explicit Debt10.0 / 10Stronggated by 4 serious findings✓ Tool-verified

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

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

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

4 deducted task-comment markers across 317096 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.

TodoComment · ×4packages/2-mongo-family/5-query-builders/orm/src/types.ts:356

What to do

  1. Resolve the 4 TodoComment finding(s) in Explicit Debt — start with types.ts, client.ts, db.server.ts. — One of this dimension's main actionable groups (4 warning-level).
  2. Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

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

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

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

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

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

Documentation: no build, run or usage example · ×8packages/9-public/@prisma/orm-family-mongo/README.md:1

What to do

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

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

D20 · ADR Quality8.5 / 10Strong✓ Tool-verified

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

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

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

235 of 238 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.

ADR lacks an enforcement field · ×235docs/architecture docs/adrs/ADR 001 - Migrations as Edges.md:1detected by adr-integrity
ADR has no Context section · ×23docs/architecture docs/adrs/ADR 065 - Adapter capability schema & negotiation v1.md:1detected by adr-integrity
ADR links a record that does not exist · ×13docs/architecture docs/adrs/ADR 014 - Runtime Hook API.md:3detected by adr-integrity
ADR superseded but its status says otherwise · ×3docs/architecture docs/adrs/ADR 216 - CLI telemetry installation ID is a stored random UUID not a system fingerprint.md:5detected by adr-integrity

What to do

  1. Resolve the 235 ADR lacks an enforcement field finding(s) in ADR Quality — start with ADR 001 - Migrations as Edges.md, ADR 002 - Plans are Immutable.md, ADR 003 - One Query One Statement.md. — One of this dimension's main actionable groups (235 recommendation-level).
  2. Resolve the 23 ADR has no Context section finding(s) in ADR Quality — start with ADR 065 - Adapter capability schema & negotiation v1.md, ADR 068 - Error mapping to RuntimeError.md, ADR 126 - PSL top-level block SPI.md. — One of this dimension's main actionable groups (23 recommendation-level).
  3. Resolve the 13 ADR links a record that does not exist finding(s) in ADR Quality — start with ADR 154 - Component-owned database dependencies.md (3), ADR 239 - Errors are structural envelopes with dotted namespace codes.md (2), ADR 275 - Client generators are field attributes, and a type alias is expanded into each column.md (2). — One of this dimension's main actionable groups (13 recommendation-level).

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

D21 · Naming Consistency9.4 / 10Exemplary✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

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

2 naming inconsistencies among 366 declarations measured against a convention their peers follow.

`MigrationCLI` spells `CLI` where 16 names in the project spell it `Cli`packages/1-framework/3-tooling/cli/src/migration-cli.ts:166
`toJSON` spells `JSON` where 547 names in the project spell it `Json`packages/1-framework/3-tooling/cli/test/fixtures/to-json-circular.ts:4

✓ On the Gold path — maintain.

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

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

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

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

No domain types are scored-flagged across 16 context boundaries; 9 contract project(s) carry advisory strong-ID notes. Contexts: bundle-size, lsp-playground, mongo-blog-leaderboard, mongo-demo, multi-extension-monorepo, paradedb-demo, prisma-8-cloudflare-worker, prisma-8-demo, prisma-8-demo-mysql, prisma-8-demo-sqlite, prisma-8-postgis-demo, prisma7-adoption and 4 more.

Contract: 1 contract type(s) expose producer-owned ids/enums
CrossReference: 1 contract type(s) expose producer-owned ids/enums
ForeignKeyReference: 1 contract type(s) expose producer-owned ids/enums
SqlStorage: 1 contract type(s) expose producer-owned ids/enums
SqlStorageInput: 1 contract type(s) expose producer-owned ids/enums

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

✓ On the Gold path — maintain.

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

D24 · Comment Value9.5 9.3 / 10Exemplary✓ Tool-verified

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

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

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

21 of 4230 judged comments only repeat the code they sit on (0.5 %). 139 comment(s) in another language or script were not judged.

redundant comment · ×21packages/1-framework/3-tooling/cli/src/utils/framework-components.ts:56
doc comments repeat the names · ×7packages/1-framework/3-tooling/cli/src/control-api/statements/statement-text.ts:1

✓ On the Gold path — maintain.

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

D25 · ADR Conformance5.0 / 10Adequate✓ Tool-verified

What it measures: Whether the code actually follows the decisions recorded in the project's ADRs.

Method: Each binding ADR read for checkable forms: a backticked element its Decision section rules out, a ruled-out package the manifests declare, a forbidden module dependency, an opt-in adr-rules block, and a declared delivery status the code does not yet carry. A prose decision with no checkable form is unverifiable, neither a finding nor a pass. Deterministic, no model. Advisory.

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

7 of 14 checkable records are broken by the code or by their own declared delivery (14 of 96 binding records state a rule in checkable form or declare their delivery; prose decisions are unverifiable).

ADR not followed: ADR 224 — Namespace concretions address entities by coordinate · ×8docs/architecture docs/adrs/ADR 224 - Namespace concretions address entities by coordinate.md:56detected by adr-prohibition

What to do

  1. Resolve the 8 ADR not followed finding(s) in ADR Conformance — start with ADR 271 - The runtime middleware observes a tree of activities, each started, ended and finalized.md (2), ADR 224 - Namespace concretions address entities by coordinate.md, ADR 239 - Errors are structural envelopes with dotted namespace codes.md. — One of this dimension's main actionable groups (8 recommendation-level).
  2. Enforce ADR Conformance in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

D26 · Project Cohesion8.1 / 10Strong✓ Tool-verified

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

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

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

8 of 82 build units (npm) flagged as possibly oversized/incoherent.

Projects may be oversized for their cohesion

What to do

  1. Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

D28 · Secrets (history)0.0 / 10Critical✓ Tool-verified

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.

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

31 finding(s): 0 critical, 31 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 26 High secret finding(s) in Secrets (history) — start with REDACTED (13), REDACTED (6), REDACTED (5). — One of this dimension's main actionable groups (26 issue-level).
  2. Resolve the 5 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (5 issue-level).
  3. 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.

D29 · Static Analysis (SAST)0.8 / 10Critical✓ Tool-verified

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

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

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

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

41 finding(s): 0 critical, 6 high, 35 medium, 0 low. 2 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 348 file(s) — `REDACTED` (line 70), `apps/telemetry-backend/migrations/app/20261016T1018_exit_code/migration.ts` (line 4, lines 5–6, line 8, …), `apps/telemetry-backend/src/db.ts` (line 4, line 8), `apps/telemetry-backend/src/handler.ts` (line 1), `apps/telemetry-backend/src/schema.ts` (line 1), … (+343 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 3 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

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

What to do

  1. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 1 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (1 issue-level, 0 of them charged here).

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

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

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

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

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

40 finding(s): 3 critical, 27 high, 9 medium, 1 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

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

What to do

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

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

D31 · IaC & Container Security9.8 / 10Stronggated by 2 serious findings✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (Dockerfile/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

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

2 finding(s): 0 critical, 0 high, 2 medium, 0 low.

REDACTED

What to do

  1. Resolve the 2 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).

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

D34 · Knowledge Freshness9.7 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

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

26 of 1005 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/1-framework/3-tooling/cli/recordings/config.ts. Counted over 1005 of the 2201 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×26packages/1-framework/3-tooling/cli/recordings/config.ts:1
Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

D35 · Change Coupling9.9 / 10Stronggated by 9 serious findings✓ Tool-verified

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

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

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

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

Strongest change-coupling: control-adapter.ts↔control-adapter.ts 69%; factories.ts↔validators.ts 59%; db-init.ts↔db-update.ts 58%

Change coupling: control-adapter.ts ↔ control-adapter.ts · ×9packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:1

What to do

  1. Resolve the 9 Change coupling finding(s) in Change Coupling — start with control-adapter.ts, factories.ts, db-init.ts. — One of this dimension's main actionable groups (9 warning-level).

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

D36 · Supply-chain Provenance & Signing5.0 / 10Adequate✓ Tool-verified

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.

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

2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

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

D37 · Vulnerability-disclosure Policy10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.

Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.

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

A vulnerability-disclosure policy (SECURITY.md) is published with a reporting contact.

✓ On the Gold path — maintain.

Detailed fixes: d37_recommendation.md.

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

D44 · Platform End-of-Life10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.

Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition8.7 / 10Strong✓ Tool-verified

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

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

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

What to do

  • The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

  • `ControlClient` declares 20 required operations: `init`, `connect`, `close`, `verify`, `schemaVerify`, `dbInit`, `dbUpdate`, `dbVerify`, `dbSign`, `readMarker`, `readAllMarkers`, `readLedger`, `migrate`, `introspect`, `toSchemaView`, `inferPslContract`, `getPslBlockDescriptors`, `toOperationPreview`, `emit`, `renderContractDts`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/1-framework/3-tooling/cli/src/control-api/types.ts:861
  • `MongoStageVisitor` declares 28 required operations: `match`, `project`, `sort`, `limit`, `skip`, `lookup`, `unwind`, `group`, `addFields`, `replaceRoot`, `count`, `sortByCount`, `sample`, `redact`, `out`, `unionWith`, `bucket`, `bucketAuto`, `geoNear`, `facet`, `graphLookup`, `merge`, `setWindowFields`, `densify`, `fill`, `search`, `searchMeta`, `vectorSearch`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/2-mongo-family/4-query/query-ast/src/visitors.ts:106
  • `MongoCollection` declares 25 required operations: `variant`, `where`, `where`, `select`, `include`, `orderBy`, `limit`, `offset`, `all`, `first`, `firstOrThrow`, `create`, `createAll`, `createAndCount`, `update`, `update`, `updateAll`, `updateAll`, `updateAndCount`, `updateAndCount`, `delete`, `deleteAll`, `deleteAndCount`, `upsert`, `upsert`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 25 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/2-mongo-family/5-query-builders/orm/src/collection.ts:105
  • `LeafExpression` declares 24 required operations: `eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `in`, `nin`, `exists`, `type`, `set`, `unset`, `rename`, `inc`, `mul`, `min`, `max`, `push`, `addToSet`, `pop`, `pull`, `pullAll`, `currentDate`, `setOnInsert`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/2-mongo-family/5-query-builders/query-builder/src/field-accessor.ts:48
  • `ExprVisitor` declares 22 required operations: `columnRef`, `identifierRef`, `subquery`, `operation`, `aggregate`, `windowFunc`, `functionCall`, `cast`, `case`, `jsonObject`, `jsonArrayAgg`, `binary`, `and`, `or`, `exists`, `nullCheck`, `not`, `literal`, `param`, `preparedParam`, `list`, `rawExpr`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:86

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

C1 · Data Protection0.0 / 10Critical✓ Tool-verified

Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.

Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.

  • No encryption usage (node:crypto createCipheriv, Web Crypto subtle.encrypt, crypto-js AES, tweetnacl/libsodium secretbox, a column-encryption layer such as typeorm-encrypted, prisma-field-encryption or mongoose-field-encryption, or MongoDB client-side field-level encryption) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore. — packages/3-extensions/supabase/src/contract/contract.prisma:34

What to do

  • Encrypt sensitive data at rest (AES-256-GCM through node:crypto createCipheriv, or a column-encryption layer such as typeorm-encrypted / prisma-field-encryption / MongoDB CSFLE) and manage keys in a vault (AWS KMS, Azure Key Vault, GCP KMS, HashiCorp Vault). Skip if delegated to infra (Postgres TDE, KMS, etc.).
  • Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.
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. — packages/1-framework/1-core/framework-components/src/control/control-stack.ts:146

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.
C3 · Audit Trail7.5 / 10Strong✓ Tool-verified

Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.

Method: Roslyn scan: audit-trail mechanism graded (SaveChanges interceptor/immutable AuditLog/[Audited] strong; bare IAuditable/AddAuditing weak). Deterministic.

  • An audit mechanism is present, but the trail is not yet complete — missing: an ORM write hook every change flows through (a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware or a query extension, or an event-store append), per-model coverage (@Audited, or a change-history plugin such as mongoose-history or sequelize-paper-trail applied to each model).

What to do

  • Back the audit convention with a structural mechanism: an ORM write hook (a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware) writing every sensitive change to an audit-log table, and apply it to each model that needs a who-changed-what trail.
C4 · Data Retention6.5 / 10Adequate✓ Tool-verified

Other · Security — Whether data has a defined lifetime — retention periods, TTLs, cleanup jobs (storage limitation).

Method: Roslyn scan: retention/TTL configuration presence in schema; CascadeDelete detected but not scored as retention control. Deterministic, gated by PII presence.

  • A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (a cron task that deletes rows past their retention — purgeExpired… / deleteOld…), a documented retention period / data-expiry.

What to do

  • Complete the data-lifecycle story: an expiry limit (a declared maximum age for the stored data — a retention-age setting, or a store-level TTL where your storage offers one), a scheduled purge/cleanup job that enforces it, and a documented retention period covering the personal data.
GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

IC1 · Incompleteness & stubs7.6 / 10Strong✓ Tool-verified

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

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

  • Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition. (×3) — packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:1537, packages/3-extensions/sql-orm-client/src/collection.ts:1715, skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-closed-mongo-contracts.ts:157
  • `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×4) — skills-contrib/review-fetch-phase/scripts/guard-review-artifacts-ignored.mjs:137, skills-contrib/review-implement-phase/scripts/check-github-admin-ready.mjs:129, skills-contrib/review-implement-phase/scripts/post-review-thread-reply.mjs:271, …
  • `call` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/1-framework/2-authoring/psl-parser/src/authoring-arguments.ts:70
  • `argument` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/1-framework/2-authoring/psl-parser/src/authoring-arguments.ts:71
  • `value` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/1-framework/2-authoring/psl-parser/src/authoring-arguments.ts:72
  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×2) — test/utils/src/mysql-database.ts:77, test/utils/test/mysql-database.test.ts:31

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.
M1 · Documentation (README)9.2 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

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

What to do

  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add a README to the 6 of 117 project(s) that lack one — worth up to 0.1 pts.
M2 · Architecture documentation10.0 / 10Exemplary✓ Tool-verified

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

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

M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

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

M4 · Documentation accuracy8.6 / 10Strong✓ Tool-verified

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.

  • projects/README.md links to `../docs/drive/README.md`, but `docs/drive/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — projects/README.md:18
  • docs/reference/framework-integration-analysis.md names Vite 7, but the manifest declares `vite` ^6.3.5. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/reference/framework-integration-analysis.md:237
  • packages/1-framework/2-authoring/ids/README.md links to `../../../docs/architecture%20docs/subsystems/1.%20Data%20Contract.md`, but `packages/docs/architecture docs/subsystems/1. Data Contract.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/1-framework/2-authoring/ids/README.md:33
  • packages/1-framework/2-authoring/ids/README.md links to `../../../docs/architecture%20docs/subsystems/3.%20Query%20Lanes.md`, but `packages/docs/architecture docs/subsystems/3. Query Lanes.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/1-framework/2-authoring/ids/README.md:34
  • packages/1-framework/3-tooling/vite-plugin-contract-emit/README.md names Vite 7, but the manifest declares `vite` ^6.3.5. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/1-framework/3-tooling/vite-plugin-contract-emit/README.md:29
  • packages/2-sql-family/1-core/contract/README.md links to `../../../docs/architecture%20docs/adrs/ADR%20166%20-%20Referential%20actions%20for%20foreign%20keys.md`, but `packages/docs/architecture docs/adrs/ADR 166 - Referential actions for foreign keys.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/2-sql-family/1-core/contract/README.md:79
  • packages/2-sql-family/1-core/contract/README.md links to `../../../docs/architecture%20docs/subsystems/1.%20Data%20Contract.md`, but `packages/docs/architecture docs/subsystems/1. Data Contract.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/2-sql-family/1-core/contract/README.md:219
  • packages/2-sql-family/1-core/contract/README.md links to `../../../docs/architecture%20docs/subsystems/2.%20Contract%20Emitter%20&%20Types.md`, but `packages/docs/architecture docs/subsystems/2. Contract Emitter & Types.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/2-sql-family/1-core/contract/README.md:220
  • packages/2-sql-family/4-lanes/relational-core/README.md links to `../../../../docs/architecture%20docs/adrs/ADR%20005%20-%20Thin%20Core,%20Fat%20Targets.md`, but `docs/architecture docs/adrs/ADR 005 - Thin Core, Fat Targets.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/2-sql-family/4-lanes/relational-core/README.md:202
  • packages/3-targets/postgres/3-driver/README.md links to `../../docs/architecture%20docs/subsystems/5.%20Adapters%20&%20Targets.md`, but `packages/3-targets/docs/architecture docs/subsystems/5. Adapters & Targets.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/3-targets/postgres/3-driver/README.md:91

What to do

  • Reconcile the README with reality: projects/README.md links to `../docs/drive/README.md`, but `docs/drive/README.md` does not exist; docs/reference/framework-integration-analysis.md names Vite 7, but the manifest declares `vite` ^6.3.5; packages/1-framework/2-authoring/ids/README.md links to `../../../docs/architecture%20docs/subsystems/1.%20Data%20Contract.md`, but `packages/docs/architecture docs/subsystems/1. Data Contract.md` does not exist; packages/1-framework/2-authoring/ids/README.md links to `../../../docs/architecture%20docs/subsystems/3.%20Query%20Lanes.md`, but `packages/docs/architecture docs/subsystems/3. Query Lanes.md` does not exist; packages/1-framework/3-tooling/vite-plugin-contract-emit/README.md names Vite 7, but the manifest declares `vite` ^6.3.5.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

P2 · Observability5.3 / 10Adequate✓ Tool-verified

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

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

  • Only 3/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/lsp-playground`, `packages/0-shared/extension-author-tools`, `packages/1-framework/3-tooling/cli`, `packages/1-framework/3-tooling/language-server`.

What to do

  • Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
  • Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

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.

  • Deployment 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 reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

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

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

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

  • `spawnSync` in `applySchema` 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. — examples/prisma-8-cloudflare-worker/test/global-setup.ts:64
  • `mkdtempSync` in `initTestDatabase` 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. — examples/prisma-8-demo/test/utils/control-client.ts:82
  • `mkdirSync` in `initTestDatabase` 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. — examples/prisma-8-demo/test/utils/control-client.ts:85
  • `rmSync` in `initTestDatabase` 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. — examples/prisma-8-demo/test/utils/control-client.ts:102
  • `rmSync` in `defineShellConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/0-config/tsdown/shell-build.ts:64
  • `mkdirSync` in `defineShellConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/0-config/tsdown/shell-build.ts:65
  • `writeFileSync` in `defineShellConfig` 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. (×4) — packages/0-config/tsdown/shell-build.ts:127, packages/0-config/tsdown/shell-build.ts:146, packages/0-config/tsdown/shell-build.ts:174, …
  • `readFileSync` in `findInternalNames` 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) — packages/0-config/tsdown/shell-testkit.ts:420, packages/0-config/tsdown/shell-testkit.ts:429
  • `readFileSync` in `findInternalImportSpecifiers` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/0-config/tsdown/shell-testkit.ts:454
  • `readFileSync` in `readProjectPackageJson` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/1-framework/3-tooling/cli-telemetry/src/enrich.ts:265
  • `existsSync` in `loadContractFromTs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:213
  • `writeFileSync` in `loadContractFromTs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:270
  • `unlinkSync` in `loadContractFromTs` 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) — packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:276, packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:314
  • `writeFileSync` in `serializeMigrationToDisk` 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) — packages/1-framework/3-tooling/cli/src/migration-cli.ts:525, packages/1-framework/3-tooling/cli/src/migration-cli.ts:526
  • `existsSync` in `handler` 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) — packages/1-framework/3-tooling/cli/src/orm/contract/infer.ts:181, packages/1-framework/3-tooling/cli/src/orm/contract/print.ts:349
  • `existsSync` in `callback to filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/1-framework/3-tooling/cli/src/orm/init-inputs.ts:506, packages/1-framework/3-tooling/cli/src/orm/init-inputs.ts:590
  • `existsSync` in `refHashOf` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/1-framework/3-tooling/cli/test/orm/db-sign-fixtures.ts:89
  • `realpathSync` in `importC12` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/1-framework/3-tooling/config-loader/src/load.ts:207
  • `mkdtempSync` in `createJourneyProject` 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. — test/integration/test/cli-journeys/init-journey/harness.ts:152
  • `writeFileSync` in `createJourneyProject` 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. — test/integration/test/cli-journeys/init-journey/harness.ts:182
  • `rmSync` in `cleanup` 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. — test/integration/test/cli-journeys/init-journey/harness.ts:191
  • `rmSync` in `createJourneyProject` 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. — test/integration/test/cli-journeys/init-journey/harness.ts:195
  • `mkdirSync` in `packAllWorkspacePackages` 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) — test/integration/test/cli-journeys/init-journey/harness.ts:295, test/integration/test/cli-journeys/init-journey/harness.ts:296
  • `existsSync` in `packIfStale` 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) — test/integration/test/cli-journeys/init-journey/harness.ts:378, test/integration/test/cli-journeys/init-journey/harness.ts:416
  • `readFileSync` in `packIfStale` 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) — test/integration/test/cli-journeys/init-journey/harness.ts:388, test/integration/test/cli-journeys/init-journey/harness.ts:418
  • `writeFileSync` in `packIfStale` 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) — test/integration/test/cli-journeys/init-journey/harness.ts:397, test/integration/test/cli-journeys/init-journey/harness.ts:418
  • `rmSync` in `packIfStale` 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) — test/integration/test/cli-journeys/init-journey/harness.ts:417, test/integration/test/cli-journeys/init-journey/harness.ts:419

What to do

  • TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
R1 · Type Safety9.8 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

What to do

  • Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication8.8 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): 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. Deterministic.

  • 233 duplicated blocks under packages/3-targets/ have copies in at least two of the sibling directories mongo, mysql, postgres, sqlite — 183 of them are reported below, and 50 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 233 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 233 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 233 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:142
  • 139 duplicated blocks under packages/ have copies in at least two of the sibling directories 0-config, 1-framework, 2-mongo-family, 2-sql-family, 3-extensions, 3-targets — 66 of them are reported below, and 73 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 139 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 139 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 139 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/2-mongo-family/2-authoring/contract-prisma6/src/provider.ts:18
  • 52 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages, scripts, skills, skills-contrib, upgrade-instructions — 47 of them are reported below, and 5 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 52 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 52 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 52 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. — REDACTED:22
  • 15 duplicated blocks under packages/3-extensions/ have copies in at least two of the sibling directories arktype-json, citext, paradedb, pgvector, postgis, supabase — 9 of them are reported below, and 6 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 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 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 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/3-extensions/pgvector/src/exports/control.ts:91
  • 12 of the duplicated blocks reported below have copies in at least two of the sibling directories app, extension under skills/prisma-8/upgrading/. That concentration is one structural fact, not 12 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 12 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. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:13
  • 10 duplicated blocks under packages/1-framework/3-tooling/ have copies in at least two of the sibling directories cli, config-loader, language-server, migration — 1 of them are reported below, and 9 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. — packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts:647
  • 9 duplicated blocks under skills-contrib/ have copies in at least two of the sibling directories github-review-iteration, review-fetch-phase, review-implement-phase, review-triage-phase — 8 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 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. — skills-contrib/review-fetch-phase/scripts/extract-review-targets.mjs:10
  • 7 duplicated blocks under packages/1-framework/3-tooling/cli/src/orm/ have copies in at least two of the sibling directories contract, db, migration — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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. — packages/1-framework/3-tooling/cli/src/orm/contract/infer.ts:100
  • 7 of the duplicated blocks reported below have copies in at least two of the sibling directories 0.11-to-0.12, 0.12-to-0.13, 8.0.0-rc.18-to-8.0.0-rc.19, 8.0.0-rc.21-to-8.0.0-rc.22 under skills/prisma-8/upgrading/app/upgrades/. 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. — skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts:27
  • 5 duplicated blocks under packages/2-mongo-family/ have copies in at least two of the sibling directories 1-foundation, 4-query, 6-transport — 4 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/2-mongo-family/4-query/query-ast/src/ddl-commands.ts:108
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:13 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:13 — these 2 files are line-for-line copies of one another — 1668 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. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:13
  • REDACTED:22 · REDACTED:22 · REDACTED:22 · REDACTED:22 — these 4 files are line-for-line copies of one another — 1041 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. — REDACTED:22
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:13 · upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:13 — these 2 files are line-for-line copies of one another — 797 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. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:13
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:13 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:13 · upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:13 · upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:13 — these 4 files are line-for-line copies of one another — 765 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. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:13
  • REDACTED:22 · REDACTED:22 · REDACTED:22 — these 3 files are line-for-line copies of one another — 737 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. — REDACTED:22
  • upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:11 · upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:11 — these 2 files are line-for-line copies of one another — 549 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. — upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:11
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:19 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:19 — these 2 files are line-for-line copies of one another — 415 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. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:19
  • upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts:17 · upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:17 — these 2 files are line-for-line copies of one another — 257 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. — upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts:17
  • packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:142 · packages/3-targets/sqlite/1-target/src/core/migrations/runner.ts:62 — the two spans are one implementation copied and then locally edited — 1537 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:142
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.22-to-8.0.0-rc.23/scripts/mongo-index-names/mongo-index-names.ts:11 · upgrade-instructions/releases/8.0.0-rc.22-to-8.0.0-rc.23/sources/mongo-index-names/app/scripts/mongo-index-names.ts:11 — these 2 files are line-for-line copies of one another — 204 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. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.22-to-8.0.0-rc.23/scripts/mongo-index-names/mongo-index-names.ts:11
  • packages/3-targets/postgres/1-target/src/core/stored-inet.ts:28 · skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:645 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:645 — 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. — packages/3-targets/postgres/1-target/src/core/stored-inet.ts:28
  • REDACTED:14 · REDACTED:14 — these 2 files are line-for-line copies of one another — 200 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. — REDACTED:14
  • packages/3-targets/postgres/2-adapter/src/core/sql-renderer.ts:199 · packages/3-targets/sqlite/2-adapter/src/core/adapter.ts:196 — the two spans are one implementation copied and then locally edited — 1111 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/3-targets/postgres/2-adapter/src/core/sql-renderer.ts:199
  • skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:30 · skills/prisma-8/upgrading/extension/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:30 — these 2 files are line-for-line copies of one another — 179 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. — skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:30
  • scripts/codemods/rewrite-sql-strings.mjs:14 · skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.17-to-8.0.0-rc.18/scripts/sql-expression-literals-psl/rewrite-sql-strings.mjs:14 · upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/app/scripts/rewrite-sql-strings.mjs:14 · upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/extension/scripts/rewrite-sql-strings.mjs:14 — these 4 files are line-for-line copies of one another — 177 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. — scripts/codemods/rewrite-sql-strings.mjs:14
  • packages/1-framework/3-tooling/cli/src/orm/db/init.ts:38 · packages/1-framework/3-tooling/cli/src/orm/db/update.ts:77 — the two spans are one implementation copied and then locally edited — 963 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/1-framework/3-tooling/cli/src/orm/db/init.ts:38
  • packages/3-targets/postgres/1-target/src/core/migrations/operations/stored-values.ts:106 · packages/3-targets/sqlite/1-target/src/core/migrations/operations/stored-values.ts:71 — the two spans are one implementation copied and then locally edited — 1036 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/3-targets/postgres/1-target/src/core/migrations/operations/stored-values.ts:106
  • REDACTED:83 · REDACTED:83 — these 2 files are line-for-line copies of one another — 166 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. — REDACTED:83
  • packages/3-targets/postgres/1-target/src/core/codec-descriptor.ts:97 · packages/3-targets/sqlite/1-target/src/core/codec-descriptor.ts:50 — the two spans are one implementation copied and then locally edited — 966 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/3-targets/postgres/1-target/src/core/codec-descriptor.ts:97
  • skills/prisma-8/upgrading/app/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts:79 · skills/prisma-8/upgrading/extension/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts:79 — these 2 files are line-for-line copies of one another — 159 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. — skills/prisma-8/upgrading/app/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts:79
  • packages/3-targets/mysql/2-adapter/src/core/sql-renderer.ts:321 · packages/3-targets/sqlite/2-adapter/src/core/adapter.ts:388 — the two spans are one implementation copied and then locally edited — 1018 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/3-targets/mysql/2-adapter/src/core/sql-renderer.ts:321
  • scripts/codemods/add-model-map.mjs:22 · skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs:22 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs:22 · upgrade-instructions/releases/8.0.0-rc.11-to-8.0.0-rc.12/sources/psl-verbatim-table-names/app/scripts/add-model-map.mjs:22 · +1 more site(s) not listed — these 5 files are line-for-line copies of one another — 147 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. — scripts/codemods/add-model-map.mjs:22
  • REDACTED:67 · REDACTED:67 — these 2 files are line-for-line copies of one another — 147 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. — REDACTED:67
  • REDACTED:77 · REDACTED:77 · REDACTED:32 — 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. — REDACTED:77
  • packages/3-targets/mongo/2-adapter/src/lowering.ts:326 · packages/3-targets/mongo/2-adapter/src/lowering.ts:555 — the two spans are one implementation copied and then locally edited — 1094 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. — packages/3-targets/mongo/2-adapter/src/lowering.ts:326
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:2 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:2 — these 2 files are line-for-line copies of one another — 135 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. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:2
  • skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts:27 · skills/prisma-8/upgrading/app/upgrades/0.12-to-0.13/re-emit-mti-variant-link-columns.ts:31 — the two spans are one implementation copied and then locally edited — 987 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. — skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts:27
  • packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:497 · packages/3-targets/sqlite/1-target/src/core/migrations/runner.ts:483 — the two spans are one implementation copied and then locally edited — 765 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:497
  • packages/2-mongo-family/2-authoring/contract-prisma6/src/provider.ts:18 · packages/2-sql-family/2-authoring/contract-prisma7/src/provider.ts:22 — the two spans are one implementation copied and then locally edited — 740 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/2-mongo-family/2-authoring/contract-prisma6/src/provider.ts:18
  • packages/3-targets/mysql/9-facade/src/contract/define-contract.ts:42 · packages/3-targets/sqlite/9-facade/src/contract/define-contract.ts:42 — 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. — packages/3-targets/mysql/9-facade/src/contract/define-contract.ts:42

What to do

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

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

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

  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:36 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/assemble.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:36
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:37 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/block-attribute.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:37
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:38 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/bool.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:38
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:39 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/data-type-value.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:39
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:43 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/diagnostic.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:43
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:44 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/entity-ref.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:44
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:45 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/enum-member-value.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:45
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:46 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/field-ref.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:46
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:47 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/func-call.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:47
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:48 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/identifier.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:48
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:49 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/int.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:49
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:50 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/json.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:50
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:51 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/json-value.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:51
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:53 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/list.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:53
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:54 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/map-arg.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:54
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:55 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/num.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:55
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:56 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/num-literal.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:56
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:57 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/one-of.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:57
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:58 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/record.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:58
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:59 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/str.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:59
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:60 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/tagged-literal.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:60
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:65 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/written-scalar.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:65
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:66 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/field-attribute.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:66
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:67 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/generator-attribute.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:67
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:74 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/interpret.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:74
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:75 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/model-attribute.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:75
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:76 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/optional.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:76
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:87 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/spec-context.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:87
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:92 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/type-label.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:92
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:153 imports packages/1-framework/2-authoring/psl-parser/src/block-spec/constructors.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:153
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:155 imports packages/1-framework/2-authoring/psl-parser/src/block-spec/descriptor.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:155
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:161 imports packages/1-framework/2-authoring/psl-parser/src/block-spec/interpret.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:161
  • packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:166 imports packages/1-framework/2-authoring/psl-parser/src/block-spec/spec-context.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:166
  • packages/1-framework/3-tooling/cli/scripts/gallery.ts:19 imports packages/1-framework/3-tooling/cli/test/utils/formatters/gallery-cells.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/3-tooling/cli/scripts/gallery.ts:19
  • packages/1-framework/3-tooling/cli/scripts/gallery.ts:20 imports packages/1-framework/3-tooling/cli/test/utils/formatters/gallery-goldens.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/3-tooling/cli/scripts/gallery.ts:20
  • packages/1-framework/3-tooling/cli/scripts/gallery.ts:21 imports packages/1-framework/3-tooling/cli/test/utils/formatters/gallery-goldens-backlink.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/3-tooling/cli/scripts/gallery.ts:21
  • packages/1-framework/3-tooling/cli/scripts/gallery.ts:22 imports packages/1-framework/3-tooling/cli/test/utils/formatters/gallery-goldens-known-broken.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on. — packages/1-framework/3-tooling/cli/scripts/gallery.ts:22
  • packages/2-sql-family/2-authoring/contract-psl/test/fixture-generator-functions.ts:7 reaches past another workspace package's public entry into its internals with a relative path (../../../9-family/src/core/generator-functions) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/2-sql-family/2-authoring/contract-psl/test/fixture-generator-functions.ts:7
  • packages/3-extensions/sql-orm-client/test/namespace-qualification.test.ts:9 reaches past another workspace package's public entry into its internals with a relative path (../../../3-targets/postgres/1-target/src/core/postgres-schema) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/3-extensions/sql-orm-client/test/namespace-qualification.test.ts:9
  • packages/3-extensions/sql-orm-client/test/namespace-qualification.test.ts:11 reaches past another workspace package's public entry into its internals with a relative path (../../../3-targets/sqlite/1-target/src/core/sqlite-unbound-database) — the test is coupled to a file layout that package makes no promise about, so a refactor behind its entry point breaks the suite. Import the package by name instead. — packages/3-extensions/sql-orm-client/test/namespace-qualification.test.ts:11

What to do

  • Fix the listed violations: move the shared test helper into a source directory production code may depend on (38 rows); import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (29 rows).
R2 · Cyclomatic Complexity8.0 / 10Strong✓ Tool-verified

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

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

  • main has cyclomatic complexity 172 and cognitive complexity 257; 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. — examples/prisma-8-demo/src/main.ts:235
  • buildModelNodeFromPsl has cyclomatic complexity 93 and cognitive complexity 200; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:615
  • readField has cyclomatic complexity 91 and cognitive complexity 115; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:1183
  • buildGrid has cyclomatic complexity 84 and cognitive complexity 156; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts:301
  • interpretPslDocumentToSqlContract has cyclomatic complexity 82 and cognitive complexity 138; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:2170
  • executeMigrationPlanCommandInner has cyclomatic complexity 81 and cognitive complexity 118; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts:510
  • lowerStage has cyclomatic complexity 71 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/3-targets/mongo/2-adapter/src/lowering.ts:252
  • main has cyclomatic complexity 70 and cognitive complexity 105; 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) — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:994, skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:994
  • handler has cyclomatic complexity 70 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/1-framework/3-tooling/cli/src/orm/migration/status.ts:293
  • structuralLowerStage has cyclomatic complexity 70 and cognitive complexity 86; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/3-targets/mongo/2-adapter/src/lowering.ts:489
  • main has cyclomatic complexity 69 and cognitive complexity 104; 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) — upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:959, upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:959
  • main has cyclomatic complexity 66 and cognitive complexity 100; 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. (×4) — REDACTED:1292, REDACTED:1292, REDACTED:1292, …
  • main has cyclomatic complexity 66 and cognitive complexity 95; 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) — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2278, skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2278
  • main has cyclomatic complexity 65 and cognitive complexity 100; 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. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:978

What to do

  • Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files6.7 / 10Adequate✓ 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.

  • packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts has 2945 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts:1
  • packages/3-extensions/sql-orm-client/src/collection.ts has 2943 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-extensions/sql-orm-client/src/collection.ts:1
  • packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts has 2823 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:1
  • packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts has 2510 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts:1
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts has 2277 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1
  • skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts has 2277 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1
  • packages/3-extensions/sql-orm-client/src/types.ts has 2240 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-extensions/sql-orm-client/src/types.ts:1
  • packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts has 2111 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:1
  • packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts has 2096 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:1
  • packages/2-sql-family/5-runtime/src/sql-runtime.ts has 1837 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-sql-family/5-runtime/src/sql-runtime.ts:1
  • packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts has 1830 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:1
  • packages/3-targets/sqlite/1-target/src/core/migrations/op-factory-call.ts has 1710 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-targets/sqlite/1-target/src/core/migrations/op-factory-call.ts:1
  • packages/2-mongo-family/2-authoring/contract-ts/src/contract-builder.ts has 1670 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-mongo-family/2-authoring/contract-ts/src/contract-builder.ts:1
  • packages/3-targets/postgres/1-target/src/core/codecs.ts has 1606 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-targets/postgres/1-target/src/core/codecs.ts:1
  • packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts has 1585 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:1
  • packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts has 1563 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:1
  • packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts has 1535 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:1
  • packages/2-sql-family/2-authoring/contract-ts/src/contract-types.ts has 1488 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-sql-family/2-authoring/contract-ts/src/contract-types.ts:1
  • packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts has 1463 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:1
  • REDACTED has 1389 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 1389 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 1389 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • REDACTED has 1389 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
  • packages/2-mongo-family/5-query-builders/orm/src/collection.ts has 1385 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-mongo-family/5-query-builders/orm/src/collection.ts:1
  • packages/3-extensions/sql-orm-client/src/query-plan-select.ts has 1381 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-extensions/sql-orm-client/src/query-plan-select.ts:1
  • packages/3-extensions/sql-orm-client/src/mutation-executor.ts has 1367 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-extensions/sql-orm-client/src/mutation-executor.ts:1
  • packages/2-sql-family/1-core/contract/src/validators.ts has 1320 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-sql-family/1-core/contract/src/validators.ts:1
  • packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts has 1279 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts:1
  • packages/3-targets/postgres/1-target/src/core/migrations/planner.ts has 1278 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-targets/postgres/1-target/src/core/migrations/planner.ts:1
  • packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts has 1223 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts:1
  • packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts has 1212 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts:1
  • packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts has 1157 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts:1
  • packages/2-sql-family/9-family/src/core/control-instance.ts has 1154 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/2-sql-family/9-family/src/core/control-instance.ts:1
  • packages/1-framework/2-authoring/psl-parser/src/binder.ts has 1121 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/1-framework/2-authoring/psl-parser/src/binder.ts:1
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts has 1121 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:1
  • skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts has 1121 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:1
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts has 1099 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:1
  • upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts has 1099 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:1
  • packages/1-framework/3-tooling/cli/src/utils/cli-errors.ts has 1096 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/1-framework/3-tooling/cli/src/utils/cli-errors.ts:1
  • packages/3-targets/postgres/1-target/src/core/migrations/postgres-migration.ts has 1081 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/3-targets/postgres/1-target/src/core/migrations/postgres-migration.ts:1

What to do

  • Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage8.5 / 10Strong✓ 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.

  • packages/1-framework/3-tooling/cli/recordings/fixtures/prisma.config.ts:7 imports './contract', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/1-framework/3-tooling/cli/recordings/fixtures/prisma.config.ts:7
  • packages/2-sql-family/1-core/contract/test/value-type-maps.display.test.ts:7 imports './value-type-maps-display.ts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — packages/2-sql-family/1-core/contract/test/value-type-maps.display.test.ts:7
  • test/integration/test/authoring/templates/prisma.config.parity-psl.ts:9 imports './packs', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/authoring/templates/prisma.config.parity-psl.ts:9
  • test/integration/test/authoring/templates/prisma.config.parity-ts.ts:8 imports './contract', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/authoring/templates/prisma.config.parity-ts.ts:8
  • test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-init-with-contract-space/prisma.config.with-db.ts:7 imports '../../../../contract-space-fixture/control', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-init-with-contract-space/prisma.config.with-db.ts:7
  • test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces-sqlite/prisma.config.racing.with-db.ts:4 imports '../../../../contract-space-fixture/sqlite', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces-sqlite/prisma.config.racing.with-db.ts:4
  • test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces-sqlite/prisma.config.with-db.ts:3 imports '../../../../contract-space-fixture/sqlite', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces-sqlite/prisma.config.with-db.ts:3
  • test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces/prisma.config.racing.with-db.ts:7 imports '../../../../contract-space-fixture/control', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces/prisma.config.racing.with-db.ts:7
  • test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces/prisma.config.with-db.ts:7 imports '../../../../contract-space-fixture/control', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces/prisma.config.with-db.ts:7
  • test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/migrate-external-space/prisma.config.with-db.ts:7 imports '../../../../contract-space-fixture/external-space', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/migrate-external-space/prisma.config.with-db.ts:7
  • test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/mongo-cli-journeys/prisma.config.with-db.ts:7 imports './contract', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/mongo-cli-journeys/prisma.config.with-db.ts:7
  • test/integration/test/upgrade-instructions/client-takes-contract-value/fixtures/refused/before/src/import-equals.ts:5 imports './path', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/upgrade-instructions/client-takes-contract-value/fixtures/refused/before/src/import-equals.ts:5
  • test/integration/test/upgrade-instructions/client-takes-contract-value/fixtures/refused/before/src/reexport.ts:5 imports './other', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing. — test/integration/test/upgrade-instructions/client-takes-contract-value/fixtures/refused/before/src/reexport.ts:5
  • 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. (×27) — packages/2-sql-family/2-authoring/contract-ts/src/contract-types.ts:1, REDACTED:1, REDACTED:1, …

What to do

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

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • This repository declares test tooling, and the ✓ above records that declaration — but packages/1-framework/3-tooling/cli/recordings/fixtures/prisma.config.ts and 12 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to. — packages/1-framework/3-tooling/cli/recordings/fixtures/prisma.config.ts:7
R7 · Dead Code7.8 / 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.

  • Unreachable from the 1352 application, 823 tooling and 4409 test entry point(s) detected in this repo. Gate removals on `pnpm run build` — an undetected custom entry would make these reachable.
  • no import path from any entry point (1352 application, 823 tooling, 4409 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 (×34) — REDACTED, REDACTED, upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts, …
  • no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/probe.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 (×2) — projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/contract-verbose.ts, projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/contract-facade.ts
  • Nothing imports this binding — it is safe to review for removal. (×3) — examples/prisma-8-demo-sqlite/src/transactions/add-posts-within-quota.ts:3, examples/prisma-8-demo/src/prisma-no-emit/context.ts:10, examples/prisma-8-demo/src/prisma-no-emit/context.ts:11

What to do

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

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

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

  • Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — apps/lsp-playground/src/cli.ts:132
  • 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. (×2)
  • Declared in apps/lsp-playground/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.
  • Every import is type-only — move it to devDependencies. — REDACTED:17
  • Only test files import it (first: packages/1-framework/3-tooling/cli/test/orm/contract-emit.test.ts:5) — move it to devDependencies. — packages/1-framework/3-tooling/cli/package.json:46

What to do

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

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

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

  • packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-command-render.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-labels.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-list-styler.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-list-render.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-space-render.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-command-render.ts — packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-command-render.ts:15
  • packages/3-targets/postgres/1-target/src/core/migrations/control-policy.ts → packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts → packages/3-targets/postgres/1-target/src/core/migrations/control-policy.ts (one verified cycle inside a mutually-dependent group of 4 files) — packages/3-targets/postgres/1-target/src/core/migrations/control-policy.ts:20
  • packages/3-targets/sqlite/1-target/src/core/migrations/issue-planner.ts → packages/3-targets/sqlite/1-target/src/core/migrations/planner-strategies.ts → packages/3-targets/sqlite/1-target/src/core/migrations/issue-planner.ts — packages/3-targets/sqlite/1-target/src/core/migrations/issue-planner.ts:62
  • packages/3-targets/sqlite/2-adapter/src/core/adapter.ts → packages/3-targets/sqlite/2-adapter/src/core/control-adapter.ts → packages/3-targets/sqlite/2-adapter/src/core/adapter.ts — packages/3-targets/sqlite/2-adapter/src/core/adapter.ts:57

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

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. 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.

  • `httpServer.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.) — apps/lsp-playground/src/cli.ts:198
  • `server.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:122

What to do

  • 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`.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

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

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

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

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

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

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

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

X17 · Uncapped recursion over a caller-supplied document1.1 / 10Critical✓ Tool-verified

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

  • `packedEntrySpecifiers` is exported, takes a document from its caller (line 430) and hands it to `importableTarget`, which calls itself at line 462 (`importableTarget`) with a piece of `target` (and at line 464) — and nowhere in `importableTarget` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `importableTarget` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — scripts/check-conformance.mjs:462
  • `resolveDraftDoc` is exported, takes a document from its caller (line 146) and hands it to `resolveDraftSlot`, which calls itself at line 126 (`resolveDraftSlot`) with a piece of `value` — and nowhere in `resolveDraftSlot` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `resolveDraftSlot` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/3-targets/mongo/2-adapter/src/resolve-value.ts:126
  • `decodeBsonValue` is exported, takes a document from its caller (line 143) and hands it to `decodeValue`, which calls itself at line 124 (`decodeValue`) with a piece of `value` (and at line 129) — and nowhere in `decodeValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `decodeValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/3-targets/mongo/1-target/src/core/bson-codec-helpers.ts:124
  • `encodeJsonValue` is exported, takes a document from its caller (line 106) and hands it to `assertJsonValue`, which calls itself at line 93 (`assertJsonValue`) with a piece of `value` (and at line 97) — and nowhere in `assertJsonValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `assertJsonValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/3-targets/mongo/1-target/src/core/json-codec-helpers.ts:93
  • `decodeJsonValue` is exported, takes a document from its caller (line 188) and hands it to `decodeValue`, which calls itself at line 174 (`decodeValue`) with a piece of `value` — and nowhere in `decodeValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `decodeValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/3-targets/mongo/1-target/src/core/json-codec-helpers.ts:174
  • `deserializePipelineStage` is exported, takes a document from its caller (line 469) and hands it to `deserializeFilterExpr`, which calls itself at line 442 (`deserializeFilterExpr`) with a piece of `json` (and at line 446, line 450) — and nowhere in `deserializeFilterExpr` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deserializeFilterExpr` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/3-targets/mongo/1-target/src/core/migrations/mongo-ops-serializer.ts:442
  • `deserializePipelineStage` is exported and takes `json: unknown` from its caller, and it calls itself at line 511 (`deserializePipelineStage`) with a piece of `json` (and at line 549) — and nowhere in `deserializePipelineStage` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deserializePipelineStage` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/3-targets/mongo/1-target/src/core/migrations/mongo-ops-serializer.ts:511
  • `normalizeIndexOptionValue` is exported, takes a document from its caller (line 245) and hands it to `withSortedKeys`, which calls itself at line 253 (`withSortedKeys`) with a piece of `value` (and at line 258) — and nowhere in `withSortedKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `withSortedKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/2-sql-family/1-core/schema-ir/src/naming.ts:253
  • `decodeMongoRow` is exported, takes a document from its caller (line 89) and hands it to `walkField`, which calls itself at line 196 (`walkField`) with a piece of `value` — and nowhere in `walkField` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `walkField` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/2-mongo-family/7-runtime/src/codecs/decoding.ts:196
  • `storedPathOfCallerPath` is exported and takes `names: ModelStoredNames` from its caller, and it calls itself at line 109 (`storedPathOfCallerPath`) with a piece of `names` (and at line 111) — and nowhere in `storedPathOfCallerPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `storedPathOfCallerPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/2-mongo-family/5-query-builders/orm/src/model-stored-names.ts:109
  • `rowOfStoredDocument` is exported and takes `document: Record<string, unknown>` from its caller, and it calls itself at line 156 (`rowOfStoredDocument`) with a piece of `document` — and nowhere in `rowOfStoredDocument` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `rowOfStoredDocument` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/2-mongo-family/5-query-builders/orm/src/model-stored-names.ts:156
  • `storedDocumentOfRow` is exported and takes `row: Record<string, unknown>` from its caller, and it calls itself at line 179 (`storedDocumentOfRow`) with a piece of `row` — and nowhere in `storedDocumentOfRow` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `storedDocumentOfRow` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/2-mongo-family/5-query-builders/orm/src/model-stored-names.ts:179
  • `freezeMongoFieldShape` is exported and takes `shape: MongoFieldShape` from its caller, and it calls itself at line 32 (`freezeMongoFieldShape`) with a piece of `shape` (and at line 45) — and nowhere in `freezeMongoFieldShape` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `freezeMongoFieldShape` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/2-mongo-family/4-query/query-ast/src/result-shape.ts:32
  • `deepEqual` is exported and takes `a: unknown` from its caller, and it calls itself at line 15 (`deepEqual`) with a piece of `a` (and at line 29) — and nowhere in `deepEqual` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deepEqual` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/2-mongo-family/3-tooling/mongo-schema-ir/src/index-equivalence.ts:15
  • `canonicalize` is exported and takes `obj: unknown` from its caller, and it calls itself at line 5 (`canonicalize`) with a piece of `obj` (and at line 8) — and nowhere in `canonicalize` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `canonicalize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/2-mongo-family/1-foundation/mongo-contract/src/canonicalize.ts:5
  • `serializeValue` is exported and takes `value: unknown` from its caller, and it calls itself at line 44 (`serializeValue`) with a piece of `value` (and at line 53) — and nowhere in `serializeValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `serializeValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/3-tooling/emitter/src/domain-type-generation.ts:44
  • `metaWithoutConnectionString` is exported, takes a document from its caller (line 269) and hands it to `clean`, which calls itself at line 275 (`clean`) with a piece of `value` (and at line 277) — and nowhere in `clean` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `clean` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/3-tooling/cli/src/utils/command-helpers.ts:275
  • `contributedTypeAt` is exported and takes `namespace: ContributedTypeNamespace` from its caller, and it calls itself at line 132 (`contributedTypeAt`) with a piece of `namespace` — and nowhere in `contributedTypeAt` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `contributedTypeAt` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/2-authoring/psl-parser/src/contributed-type-scope.ts:132
  • `writtenContributedTypeCodecId` is exported, takes a document from its caller (line 136) and hands it to `codecIdAtPath`, which calls itself at line 154 (`codecIdAtPath`) with a piece of `namespace` — and nowhere in `codecIdAtPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `codecIdAtPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/2-authoring/psl-parser/src/contributed-type-scope.ts:154
  • `contributedTypeScope` is exported, takes a document from its caller (line 162) and hands it to `collect`, which calls itself at line 187 (`collect`) with a piece of `namespace` — and nowhere in `collect` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collect` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/2-authoring/psl-parser/src/contributed-type-scope.ts:187
  • `jsonToTsSource` is exported and takes `value: unknown` from its caller, and it calls itself at line 42 (`jsonToTsSource`) with a piece of `value` (and at line 48) — and nowhere in `jsonToTsSource` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `jsonToTsSource` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/ts-render/src/json-to-ts-source.ts:42
  • `canonicalizeJson` is exported, takes a document from its caller (line 20) and hands it to `sortKeys`, which calls itself at line 6 (`sortKeys`) with a piece of `value` (and at line 10) — and nowhere in `sortKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sortKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/utils/canonicalize-json.ts:6
  • `assertTypeChoicesValid` is exported and takes `contributed: AuthoringTypeNamespace` from its caller, and it calls itself at line 429 (`assertTypeChoicesValid`) with a piece of `contributed` — and nowhere in `assertTypeChoicesValid` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `assertTypeChoicesValid` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/authoring-type-choice.ts:429
  • `authoringTypeConstructors` is exported and takes `namespace: AuthoringTypeNamespace` from its caller, and it calls itself at line 32 (`authoringTypeConstructors`) with a piece of `namespace` — and nowhere in `authoringTypeConstructors` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `authoringTypeConstructors` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/authoring-type-constructor-call.ts:32
  • `mergeAuthoringNamespaces` is exported, takes a document from its caller (line 812) and hands it to `deepCopyNamespace`, which calls itself at line 787 (`deepCopyNamespace`) with a piece of `source` — and nowhere in `deepCopyNamespace` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deepCopyNamespace` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:787
  • `mergeAuthoringNamespaces` is exported and takes `target: Record<string, unknown>` from its caller, and it calls itself at line 867 (`mergeAuthoringNamespaces`) with a piece of `target` — and nowhere in `mergeAuthoringNamespaces` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mergeAuthoringNamespaces` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:867
  • `collectContributedDescriptorPaths` is exported and takes `namespace: Record<string, unknown>` from its caller, and it calls itself at line 943 (`collectContributedDescriptorPaths`) with a piece of `namespace` — and nowhere in `collectContributedDescriptorPaths` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collectContributedDescriptorPaths` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:943
  • `assertResolvableTypeConstructorTemplates` is exported, takes a document from its caller (line 984) and hands it to `visitTemplateArgRefs`, which calls itself at line 965 (`visitTemplateArgRefs`) with a piece of `template` (and at line 971) — and nowhere in `visitTemplateArgRefs` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `visitTemplateArgRefs` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:965
  • `assertResolvableTypeConstructorTemplates` is exported and takes `namespace: AuthoringTypeNamespace` from its caller, and it calls itself at line 1004 (`assertResolvableTypeConstructorTemplates`) with a piece of `namespace` — and nowhere in `assertResolvableTypeConstructorTemplates` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `assertResolvableTypeConstructorTemplates` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:1004
  • `assertNoCrossRegistryCollisions` is exported, takes a document from its caller (line 1301) and hands it to `collectDescriptorPaths`, which calls itself at line 1049 (`collectDescriptorPaths`) with a piece of `namespace` — and nowhere in `collectDescriptorPaths` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collectDescriptorPaths` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:1049
  • `assertNoCrossRegistryCollisions` is exported, takes a document from its caller (line 1301) and hands it to `collectModelAttributeEntries`, which calls itself at line 1274 (`collectModelAttributeEntries`) with a piece of `namespace` — and nowhere in `collectModelAttributeEntries` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collectModelAttributeEntries` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:1274
  • `assertTypeAliasesValid` is exported, takes a document from its caller (line 1600) and hands it to `collectDescriptorNodes`, which calls itself at line 1342 (`collectDescriptorNodes`) with a piece of `namespace` — and nowhere in `collectDescriptorNodes` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collectDescriptorNodes` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:1342
  • `resolveAuthoringTemplateValue` is exported and takes `template: AuthoringTemplateValue | undefined` from its caller, and it calls itself at line 1359 (`resolveAuthoringTemplateValue`) with a piece of `template` (and at line 1364) — and nowhere in `resolveAuthoringTemplateValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `resolveAuthoringTemplateValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:1359
  • `canonicalStringify` is exported, takes a document from its caller (line 46) and hands it to `write`, which calls itself at line 103 (`write`) with a piece of `value` — and nowhere in `write` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `write` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/0-foundation/utils/src/canonical-stringify.ts:103
  • `valueObjectTypeProblems` is exported and takes `type: FieldTypeLike | undefined` from its caller, and it calls itself at line 46 (`valueObjectTypeProblems`) with a piece of `type` — and nowhere in `valueObjectTypeProblems` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `valueObjectTypeProblems` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/0-foundation/contract/src/field-problems.ts:46
  • `isColumnDefaultLiteralInputValue` is exported and takes `value: unknown` from its caller, and it calls itself at line 121 (`isColumnDefaultLiteralInputValue`) with a piece of `value` (and at line 123) — and nowhere in `isColumnDefaultLiteralInputValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `isColumnDefaultLiteralInputValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/1-framework/0-foundation/contract/src/types.ts:121

What to do

  • Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X2 · Cancellation propagation7.0 / 10Strong✓ Tool-verified

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

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

  • Only 1/2 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.
  • `loadRuntimeConfig` 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:105

What to do

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

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

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

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back. Also whether a `finally` that gives the primitive back unconditionally can run in a state where the method does not hold it: after a timed wait whose result was discarded, after an acquire inside the `try` that can fail, after the body already released it, or never, because a `return` left between the acquire and the `try`.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

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.

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

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

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.

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

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

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

X3 · Exception handling5.9 / 10Adequate✓ Tool-verified

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

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

  • `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×34) — upgrade-instructions/releases/8.0.0-rc.22-to-8.0.0-rc.23/sources/mongo-index-names/app/scripts/mongo-index-names.ts:235, upgrade-instructions/releases/8.0.0-rc.22-to-8.0.0-rc.23/sources/mongo-index-names/app/scripts/mongo-index-names.ts:292, REDACTED:197, …
  • 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. (×6) — skills/prisma-8/upgrading/extension/upgrades/0.8-to-0.9/strip-inline-contracts.ts:60, skills/prisma-8/upgrading/app/upgrades/0.8-to-0.9/strip-inline-contracts.ts:60, scripts/lint-ratchets.mjs:123, …

What to do

  • Swallowed exception (caught, then discarded)
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.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • 0/200 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.
  • ~0.1 `!` null assertions per 1k TypeScript source lines — 36 assertion(s) across the 325855 source line(s) of the 1976 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts (11), packages/1-framework/3-tooling/cli/scripts/record.ts (9), packages/1-framework/3-tooling/cli/src/control-api/client.ts (3). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

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 `?`).

Reference — by lens

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

LensScoreRatingImpact
Code Health56%Adequate — gated by D2, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture72%Adequate — gated by R9Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity92%ExemplaryStrongest area.
Readiness57%Adequate — gated by R8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security47%Weak — gated by D28, D29, C1Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance60%AdequateAcceptable, with room to improve.
Unscored — 5 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • D12 Dependency Hygiene — 1 observation(s) recorded · Dependency currency not established — registry.npmjs.org did not answer
  • P12 CI test-gate honesty — 2 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X7 Silent fallback defaults — 16 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for

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

  • C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 41 check(s) not relevant to this codebase

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

  • AC1 Text alternatives — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC7 A11y enforcement — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
  • AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • 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
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — The runtime tier booted this repository's service, but crawled PUBLIC routes only — add a Playwright storageState (e.g. playwright/.auth/user.json) or a test auth-setup to crawl authenticated screens rendered 0/1 surface(s) × 2 renders render failed for http://127.0.0.1:5434: page.goto: net::ERR_EMPTY_RESPONSE at http://127.0.0.1:5434/ Call log: - navigating to "http://127.0.0.1:5434/", waiting until "load" . This repository also has a user interface (1 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates) that the booted service does not serve, and this scan has no strategy that reaches it — so no WCAG success criterion was verified in a rendered page on this run. That is a gap in OUR tooling, not a finding about your application: nothing here says the interface is inaccessible. The static accessibility checks still ran.
  • AXS1 Runtime exposed surface — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • D14 License Compliance — License Compliance not included (time budget)
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D27 Navigability — symbol resolution incomplete — navigability not assessed
  • D32 Data Compliance (PII/GDPR) — 203 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (a Domain/Aggregates/ValueObjects layer)
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P9 Domain vs controller coverage — coverage data present for 5 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • R5 Dependency Freshness — uses a pnpm lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • 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.
  • X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 84 finding(s)
D28 · Secrets (history) · High secret · ×26
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 1 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · High CVE · ×26
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 1 more in this group — see findings.md.
D10 · Test Quality · No assertions (empty test) · ×12
  • No assertions (empty test): high concurrency with write conflicts test/integration/test/ports/prisma/functional/interactive-transactions/interactive-transactions.test.ts:190 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): deletes a binary that does not run, removes locks and downloads again scripts/download-mongod-binary.test.mjs:30 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): keeps a configured system binary that does not run scripts/download-mongod-binary.test.mjs:54 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): throws the last error once every attempt fails scripts/retry-command.test.mjs:32 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): firstOrThrow returns the row of first without null for a registered class packages/3-extensions/sql-orm-client/test/collection-chaining.types.test-d.ts:79 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): prepared terminals preserve projections and nested includes packages/3-extensions/sql-orm-client/test/prepared-collection.types.test-d.ts:5 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): invalidate rejects other shapes packages/3-extensions/middleware-cache/test/cache-middleware.types.test-d.ts:22 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): a set returning nothing is a type error packages/3-extensions/middleware-cache/test/cache-middleware.types.test-d.ts:155 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): an old positional unset(key) is a type error packages/3-extensions/middleware-cache/test/cache-middleware.types.test-d.ts:196 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): query accepts an optional second argument carrying { signal } packages/1-framework/1-core/framework-components/test/runtime-core-options.types.test-d.ts:35 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): a minimal RuntimeCore subclass typechecks packages/1-framework/1-core/framework-components/test/runtime-core.types.test-d.ts:35 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): query(plan) enforces the TPlan constraint and returns AsyncIterableResult<Row> packages/1-framework/1-core/framework-components/test/runtime-core.types.test-d.ts:53 — Test method has an empty body — it asserts nothing and exercises no code.
D28 · Secrets (history) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R9 · Circular Imports · Import cycle (2 files) · ×3
  • Import cycle (2 files) packages/3-targets/postgres/1-target/src/core/migrations/control-policy.ts:20 — packages/3-targets/postgres/1-target/src/core/migrations/control-policy.ts → packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts → packages/3-targets/postgres/1-target/src/core/migrations/control-policy.ts (one verified cycle inside a mutually-dependent group of 4 files)
  • Import cycle (2 files) packages/3-targets/sqlite/1-target/src/core/migrations/issue-planner.ts:62 — packages/3-targets/sqlite/1-target/src/core/migrations/issue-planner.ts → packages/3-targets/sqlite/1-target/src/core/migrations/planner-strategies.ts → packages/3-targets/sqlite/1-target/src/core/migrations/issue-planner.ts
  • Import cycle (2 files) packages/3-targets/sqlite/2-adapter/src/core/adapter.ts:57 — packages/3-targets/sqlite/2-adapter/src/core/adapter.ts → packages/3-targets/sqlite/2-adapter/src/core/control-adapter.ts → packages/3-targets/sqlite/2-adapter/src/core/adapter.ts
D30 · Dependency Vulnerabilities · Critical CVE · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · High vulnerability · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import '@codingame/monaco-vscode-extension-api' · ×1
  • Unlisted import '@codingame/monaco-vscode-extension-api' apps/lsp-playground/src/cli.ts:132 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (5 files) · ×1
  • Import cycle (5 files) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-command-render.ts:15 — packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-command-render.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-labels.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-list-styler.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-list-render.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-space-render.ts → packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-command-render.ts
Serious — 4038 finding(s)
D10 · Test Quality · No assertions · ×2463
  • No assertions: passes when each destructive operation is named test/utils/test/data-loss-expectations.test.ts:11 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: passes an unnamed destructive operation whose loss an earlier entry names test/utils/test/data-loss-expectations.test.ts:40 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: builder contract types match fixture contract types test/integration/test/contract-builder.types.test-d.ts:45 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ResultType inference works identically to fixture contract test/integration/test/contract-builder.types.test-d.ts:81 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: refined object contract preserves downstream model token inference test/integration/test/contract-builder.types.test-d.ts:126 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: integrated callback authoring exposes composition-shaped type helpers test/integration/test/contract-builder.types.test-d.ts:204 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: integrated callback authoring hides extension namespaces when packs are absent test/integration/test/contract-builder.types.test-d.ts:269 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: local field and belongsTo sql overlays stay typed test/integration/test/contract-builder.types.test-d.ts:290 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: explicit generated id helpers stay typed test/integration/test/contract-builder.types.test-d.ts:345 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: codec type inference via type option test/integration/test/contract-builder.types.test-d.ts:378 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: contract structure type matches Contract test/integration/test/contract-builder.types.test-d.ts:416 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: arktypeJson and jsonbColumn currently resolve to never in no-emit type path (known gap) test/integration/test/contract-builder.types.test-d.ts:438 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ResolveStandardSchemaOutput resolves Arktype schema via .infer test/integration/test/contract-builder.types.test-d.ts:499 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ResolveStandardSchemaOutput resolves Standard Schema via ~standard.types.output test/integration/test/contract-builder.types.test-d.ts:506 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: ResolveStandardSchemaOutput falls back to JsonValue without schema test/integration/test/contract-builder.types.test-d.ts:520 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: read: non-null text enum is exactly the value union (no | null) test/integration/test/contract-builder.types.test-d.ts:570 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: read: nullable text enum is value union | null test/integration/test/contract-builder.types.test-d.ts:577 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: read: non-null int-backed enum narrows to its int value union (not number) test/integration/test/contract-builder.types.test-d.ts:583 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: read: non-enum fields keep their codec output, unchanged from main test/integration/test/contract-builder.types.test-d.ts:590 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: write: enum insert accepts the value union and rejects out-of-union literals test/integration/test/contract-builder.types.test-d.ts:600 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: connects and closes correctly test/integration/test/control-api.test.ts:97 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: allows reconnect after close test/integration/test/control-api.test.ts:116 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: table name literals survive in storage.tables (single model) test/integration/test/dsl-type-inference.test-d.ts:56 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: column name literals survive in storage.tables[name].columns test/integration/test/dsl-type-inference.test-d.ts:62 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • No assertions: model name literals survive in models test/integration/test/dsl-type-inference.test-d.ts:68 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
  • + 2438 more in this group — see findings.md.
D15 · Churn × Complexity Hotspots · Hotspot · ×97
  • Hotspot: packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:615 — packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts changed 48 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 93 in interpreter.buildModelNodeFromPsl at line 615. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: examples/prisma-8-demo/src/main.ts examples/prisma-8-demo/src/main.ts:235 — examples/prisma-8-demo/src/main.ts changed 16 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 168 in main.main at line 235. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- examples/prisma-8-demo/src/main.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:1183 — packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 88 in interpreter.readField at line 1183. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:1111 — packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts changed 45 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in interpreter.interpretPslDocumentToMongoContract at line 1111. 2 of those changes were fix/bug commits, and the other 43 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts:510 — packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 73 in migration-plan.executeMigrationPlanCommandInner at line 510. 1 of those changes was a fix/bug commit, and the other 22 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:699 — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts changed 26 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 55 in framework-authoring.isWellFormedDescriptor at line 699. 1 of those changes was a fix/bug commit, and the other 25 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts:672 — packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in psl-column-resolution.lowerTypeDefault at line 672. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/2-authoring/psl-parser/src/binder.ts packages/1-framework/2-authoring/psl-parser/src/binder.ts:714 — packages/1-framework/2-authoring/psl-parser/src/binder.ts changed 21 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 54 in binder.tryBindExpression at line 714. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/2-authoring/psl-parser/src/binder.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/2-sql-family/2-authoring/contract-psl/src/psl-field-resolution.ts packages/2-sql-family/2-authoring/contract-psl/src/psl-field-resolution.ts:236 — packages/2-sql-family/2-authoring/contract-psl/src/psl-field-resolution.ts changed 29 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in psl-field-resolution.collectResolvedFields at line 236. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/2-sql-family/2-authoring/contract-psl/src/psl-field-resolution.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts:169 — packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts changed 23 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 44 in issue-planner.classifyCall at line 169. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:859 — packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts changed 31 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in PostgresControlAdapter.introspectSchema at line 859. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/2-sql-family/2-authoring/contract-ts/src/build-contract.ts packages/2-sql-family/2-authoring/contract-ts/src/build-contract.ts:294 — packages/2-sql-family/2-authoring/contract-ts/src/build-contract.ts changed 28 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in build-contract.buildSqlContractFromDefinition at line 294. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/2-sql-family/2-authoring/contract-ts/src/build-contract.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:1024 — packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 42 in interpreter.readModelField at line 1024. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/3-tooling/cli/src/control-api/operations/db-run.ts packages/1-framework/3-tooling/cli/src/control-api/operations/db-run.ts:195 — packages/1-framework/3-tooling/cli/src/control-api/operations/db-run.ts changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 41 in db-run.executeRun at line 195. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/3-tooling/cli/src/control-api/operations/db-run.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/3-tooling/cli/src/orm/migrate.ts packages/1-framework/3-tooling/cli/src/orm/migrate.ts:245 — packages/1-framework/3-tooling/cli/src/orm/migrate.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in migrate.createMigrateCommand at line 245. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/3-tooling/cli/src/orm/migrate.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/3-targets/postgres/1-target/src/core/psl-infer/infer-model-blocks.ts packages/3-targets/postgres/1-target/src/core/psl-infer/infer-model-blocks.ts:53 — packages/3-targets/postgres/1-target/src/core/psl-infer/infer-model-blocks.ts changed 20 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in infer-model-blocks.buildModel at line 53. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/3-targets/postgres/1-target/src/core/psl-infer/infer-model-blocks.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/3-tooling/cli/src/orm/db/sign.ts packages/1-framework/3-tooling/cli/src/orm/db/sign.ts:443 — packages/1-framework/3-tooling/cli/src/orm/db/sign.ts changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in sign.createDbSignCommand at line 443. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/3-tooling/cli/src/orm/db/sign.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/3-tooling/cli/src/control-api/operations/migrate-show.ts packages/1-framework/3-tooling/cli/src/control-api/operations/migrate-show.ts:91 — packages/1-framework/3-tooling/cli/src/control-api/operations/migrate-show.ts changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in migrate-show.executeMigrateShowPlan at line 91. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/3-tooling/cli/src/control-api/operations/migrate-show.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/2-sql-family/1-core/contract/src/validators.ts packages/2-sql-family/1-core/contract/src/validators.ts:713 — packages/2-sql-family/1-core/contract/src/validators.ts changed 14 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in validators.validateStorageSemantics at line 713. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/2-sql-family/1-core/contract/src/validators.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/3-targets/postgres/1-target/src/core/authoring.ts packages/3-targets/postgres/1-target/src/core/authoring.ts:904 — packages/3-targets/postgres/1-target/src/core/authoring.ts changed 27 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in authoring.postgresLowerEntityHandles at line 904. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/3-targets/postgres/1-target/src/core/authoring.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/3-targets/postgres/1-target/src/core/migrations/planner.ts packages/3-targets/postgres/1-target/src/core/migrations/planner.ts:265 — packages/3-targets/postgres/1-target/src/core/migrations/planner.ts changed 19 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in PostgresMigrationPlanner.planSql at line 265. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/3-targets/postgres/1-target/src/core/migrations/planner.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/3-tooling/cli/src/orm/db/update.ts packages/1-framework/3-tooling/cli/src/orm/db/update.ts:254 — packages/1-framework/3-tooling/cli/src/orm/db/update.ts changed 18 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in update.createDbUpdateCommand at line 254. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/3-tooling/cli/src/orm/db/update.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/3-extensions/sql-orm-client/src/query-plan-select.ts packages/3-extensions/sql-orm-client/src/query-plan-select.ts:907 — packages/3-extensions/sql-orm-client/src/query-plan-select.ts changed 12 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 33 in query-plan-select.buildIncludeChildScalarSelect at line 907. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/3-extensions/sql-orm-client/src/query-plan-select.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts:141 — packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts changed 15 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in migrate.executeMigrate at line 141. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: packages/1-framework/3-tooling/language-server/src/completion-values.ts packages/1-framework/3-tooling/language-server/src/completion-values.ts:109 — packages/1-framework/3-tooling/language-server/src/completion-values.ts changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 34 in completion-values.valueItems at line 109. 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-08..2026-11-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-08 19:07:32 +01:00' --until='2026-11-06 19:07:32 +01:00' --full-history --no-merges -- packages/1-framework/3-tooling/language-server/src/completion-values.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • + 72 more in this group — see findings.md.
D3 · God Classes · FileTooLong · ×85
  • FileTooLong: migrations/op-factory-call.ts packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts — FileTooLong — 2260 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1760 over it, 4.52× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/interpreter.ts packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts — FileTooLong — 2145 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1645 over it, 4.29× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/contract-dsl.ts packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts — FileTooLong — 2033 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1533 over it, 4.07× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/collection.ts packages/3-extensions/sql-orm-client/src/collection.ts — FileTooLong — 2006 significant lines (blank, comment-only and punctuation-only lines excluded), about 82% of them inside a single declaration: CollectionBase (389-3032). The bar is 500 significant lines; this is 1506 over it, 4.01× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/types.ts packages/3-extensions/sql-orm-client/src/types.ts — FileTooLong — 1880 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1380 over it, 3.76× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: remove-nocheck/remove-nocheck.ts skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts — FileTooLong — 1840 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1340 over it, 3.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: remove-nocheck/remove-nocheck.ts skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts — FileTooLong — 1840 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1340 over it, 3.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: core/control-adapter.ts packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts — FileTooLong — 1532 significant lines (blank, comment-only and punctuation-only lines excluded), about 60% of them inside a single declaration: PostgresControlAdapter (203-1532). The bar is 500 significant lines; this is 1032 over it, 3.06× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: ast/types.ts packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts — FileTooLong — 1530 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1030 over it, 3.06× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/contract-builder.ts packages/2-mongo-family/2-authoring/contract-ts/src/contract-builder.ts — FileTooLong — 1446 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 946 over it, 2.89× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/sql-runtime.ts packages/2-sql-family/5-runtime/src/sql-runtime.ts — FileTooLong — 1408 significant lines (blank, comment-only and punctuation-only lines excluded), about 72% of them inside a single declaration: SqlRuntimeBase (266-1680). The bar is 500 significant lines; this is 908 over it, 2.82× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: statements/resolve-statements.ts packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts — FileTooLong — 1365 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 865 over it, 2.73× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: migrations/op-factory-call.ts packages/3-targets/sqlite/1-target/src/core/migrations/op-factory-call.ts — FileTooLong — 1287 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 787 over it, 2.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/interpreter.ts packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts — FileTooLong — 1286 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 786 over it, 2.57× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/interpreter.ts packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts — FileTooLong — 1247 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 747 over it, 2.49× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/contract-types.ts packages/2-sql-family/2-authoring/contract-ts/src/contract-types.ts — FileTooLong — 1214 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 714 over it, 2.43× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/interpreter.ts packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts — FileTooLong — 1206 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 706 over it, 2.41× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: core/codecs.ts packages/3-targets/postgres/1-target/src/core/codecs.ts — FileTooLong — 1157 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 657 over it, 2.31× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1136 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 636 over it, 2.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1136 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 636 over it, 2.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1136 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 636 over it, 2.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: REDACTED REDACTED — FileTooLong — 1136 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 636 over it, 2.27× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/collection.ts packages/2-mongo-family/5-query-builders/orm/src/collection.ts — FileTooLong — 1081 significant lines (blank, comment-only and punctuation-only lines excluded), about 80% of them inside a single declaration: MongoCollectionImpl (276-1476). The bar is 500 significant lines; this is 581 over it, 2.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
  • FileTooLong: src/mutation-executor.ts packages/3-extensions/sql-orm-client/src/mutation-executor.ts — FileTooLong — 1078 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 578 over it, 2.16× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: src/contract-lowering.ts packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts — FileTooLong — 998 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 498 over it, 2.00× 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.
  • + 60 more in this group — see findings.md.
D3 · God Classes · FunctionTooLong · ×67
  • FunctionTooLong: interpreter.buildModelNodeFromPsl packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:615 — FunctionTooLong — buildModelNodeFromPsl runs 632 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 532 over it, 6.32× 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: interpreter.interpretPslDocumentToSqlContract packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:2170 — FunctionTooLong — interpretPslDocumentToSqlContract runs 563 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 463 over it, 5.63× 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: control-instance.createSqlFamilyInstance packages/2-sql-family/9-family/src/core/control-instance.ts:504 — FunctionTooLong — createSqlFamilyInstance runs 488 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 388 over it, 4.88× 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: relations.lowerRelations packages/2-sql-family/2-authoring/contract-prisma7/src/relations.ts:388 — FunctionTooLong — lowerRelations runs 339 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 239 over it, 3.39× 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: interpreter.interpretPslDocumentToMongoContract packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:1111 — FunctionTooLong — interpretPslDocumentToMongoContract runs 338 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 238 over it, 3.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: interpreter.readField packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:1183 — FunctionTooLong — readField runs 325 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 225 over it, 3.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: refusal-errors.refusalError packages/2-mongo-family/2-authoring/contract-ts/src/refusal-errors.ts:170 — FunctionTooLong — refusalError runs 309 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 209 over it, 3.09× 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: db-run.executeRun packages/1-framework/3-tooling/cli/src/control-api/operations/db-run.ts:195 — FunctionTooLong — executeRun runs 293 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 193 over it, 2.93× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: plugin.prismaVitePlugin packages/1-framework/3-tooling/vite-plugin-contract-emit/src/plugin.ts:50 — FunctionTooLong — prismaVitePlugin runs 282 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 182 over it, 2.82× 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: interpreter.interpretPrisma7Documents packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:298 — FunctionTooLong — interpretPrisma7Documents runs 281 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 181 over it, 2.81× 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: migrate.createMigrateCommand packages/1-framework/3-tooling/cli/src/orm/migrate.ts:245 — FunctionTooLong — createMigrateCommand runs 245 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 145 over it, 2.45× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • FunctionTooLong: init.createInitCommand packages/1-framework/3-tooling/cli/src/orm/init.ts:82 — FunctionTooLong — createInitCommand runs 236 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 136 over it, 2.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: psl-field-resolution.collectResolvedFields packages/2-sql-family/2-authoring/contract-psl/src/psl-field-resolution.ts:236 — FunctionTooLong — collectResolvedFields runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.21× 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: refusal-diagnostics.refusalDiagnostic packages/2-mongo-family/2-authoring/contract-psl/src/refusal-diagnostics.ts:213 — FunctionTooLong — refusalDiagnostic runs 217 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 117 over it, 2.17× 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: sign.createDbSignCommand packages/1-framework/3-tooling/cli/src/orm/db/sign.ts:443 — FunctionTooLong — createDbSignCommand runs 214 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 114 over it, 2.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: verify.createDbVerifyCommand packages/1-framework/3-tooling/cli/src/orm/db/verify.ts:363 — FunctionTooLong — createDbVerifyCommand runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× 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: update.createDbUpdateCommand packages/1-framework/3-tooling/cli/src/orm/db/update.ts:254 — FunctionTooLong — createDbUpdateCommand runs 195 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× 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: interpreter.interpretPrisma6Documents packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:201 — FunctionTooLong — interpretPrisma6Documents runs 190 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 90 over it, 1.90× 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: build-contract.buildSqlContractFromDefinition packages/2-sql-family/2-authoring/contract-ts/src/build-contract.ts:294 — FunctionTooLong — buildSqlContractFromDefinition 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: contract-dsl.createConstraintsDsl packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts:1314 — FunctionTooLong — createConstraintsDsl 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: check-conformance.runCheck scripts/check-conformance.mjs:656 — FunctionTooLong — runCheck 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: lowering.lowerStage packages/3-targets/mongo/2-adapter/src/lowering.ts:252 — FunctionTooLong — lowerStage runs 175 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 75 over it, 1.75× 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: psl-column-resolution.lowerTypeDefault packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts:672 — FunctionTooLong — lowerTypeDefault runs 165 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 65 over it, 1.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: control-instance.createMongoFamilyInstance packages/2-mongo-family/9-family/src/core/control-instance.ts:139 — FunctionTooLong — createMongoFamilyInstance 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: binder.bind packages/1-framework/2-authoring/psl-parser/src/binder.ts:358 — FunctionTooLong — bind runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× 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.
  • + 42 more in this group — see findings.md.
PF3 · Async & latency hygiene · Sync-over-async blocking · ×40
  • Sync-over-async blocking examples/prisma-8-cloudflare-worker/test/global-setup.ts:64 — `spawnSync` in `applySchema` 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 examples/prisma-8-demo/test/utils/control-client.ts:82 — `mkdtempSync` in `initTestDatabase` 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 examples/prisma-8-demo/test/utils/control-client.ts:85 — `mkdirSync` in `initTestDatabase` 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 examples/prisma-8-demo/test/utils/control-client.ts:102 — `rmSync` in `initTestDatabase` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/0-config/tsdown/shell-build.ts:64 — `rmSync` in `defineShellConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/0-config/tsdown/shell-build.ts:65 — `mkdirSync` in `defineShellConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/0-config/tsdown/shell-build.ts:127 — `writeFileSync` in `defineShellConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/0-config/tsdown/shell-build.ts:146 — `writeFileSync` in `defineShellConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/0-config/tsdown/shell-build.ts:174 — `writeFileSync` in `defineShellConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/0-config/tsdown/shell-build.ts:205 — `writeFileSync` in `defineShellConfig` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/0-config/tsdown/shell-testkit.ts:420 — `readFileSync` in `findInternalNames` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/0-config/tsdown/shell-testkit.ts:429 — `readFileSync` in `findInternalNames` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/0-config/tsdown/shell-testkit.ts:454 — `readFileSync` in `findInternalImportSpecifiers` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli-telemetry/src/enrich.ts:265 — `readFileSync` in `readProjectPackageJson` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:213 — `existsSync` in `loadContractFromTs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:270 — `writeFileSync` in `loadContractFromTs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:276 — `unlinkSync` in `loadContractFromTs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:314 — `unlinkSync` in `loadContractFromTs` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/migration-cli.ts:525 — `writeFileSync` in `serializeMigrationToDisk` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/migration-cli.ts:526 — `writeFileSync` in `serializeMigrationToDisk` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/orm/contract/infer.ts:181 — `existsSync` in `handler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/orm/contract/print.ts:349 — `existsSync` in `handler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/orm/init-inputs.ts:506 — `existsSync` in `callback to filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/src/orm/init-inputs.ts:590 — `existsSync` in `callback to filter` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
  • Sync-over-async blocking packages/1-framework/3-tooling/cli/test/orm/db-sign-fixtures.ts:89 — `existsSync` in `refHashOf` 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.
  • + 15 more in this group — see findings.md.
R11 · Import Boundaries · Boundary violation [package · ×40
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:36 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:36 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/assemble.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:37 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:37 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/block-attribute.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:38 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:38 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/bool.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:39 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:39 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/data-type-value.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:43 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:43 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/diagnostic.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:44 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:44 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/entity-ref.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:45 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:45 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/enum-member-value.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:46 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:46 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/field-ref.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:47 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:47 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/func-call.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:48 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:48 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/identifier.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:49 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:49 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/int.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:50 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:50 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/json.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:51 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:51 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/json-value.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:53 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:53 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/list.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:54 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:54 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/map-arg.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:55 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:55 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/num.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:56 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:56 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/num-literal.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:57 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:57 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/one-of.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:58 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:58 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/record.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:59 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:59 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/str.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:60 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:60 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/tagged-literal.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:65 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:65 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/combinators/written-scalar.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:66 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:66 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/field-attribute.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:67 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:67 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/generator-attribute.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • Boundary violation [package:test-suite-dependency] packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:74 — packages/1-framework/2-authoring/psl-parser/src/exports/index.ts:74 imports packages/1-framework/2-authoring/psl-parser/src/attribute-spec/interpret.ts, a module inside the test suite — test helpers carry no compatibility contract and are maintained for the suite, not as an API, so production code that depends on one is coupled to a module nobody keeps stable. Move the shared helper into a source directory both layers may depend on.
  • + 15 more in this group — see findings.md.
X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×36
  • Recursive walk over a caller-supplied document has no depth cap scripts/check-conformance.mjs:462 — `packedEntrySpecifiers` is exported, takes a document from its caller (line 430) and hands it to `importableTarget`, which calls itself at line 462 (`importableTarget`) with a piece of `target` (and at line 464) — and nowhere in `importableTarget` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `importableTarget` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/3-targets/mongo/2-adapter/src/resolve-value.ts:126 — `resolveDraftDoc` is exported, takes a document from its caller (line 146) and hands it to `resolveDraftSlot`, which calls itself at line 126 (`resolveDraftSlot`) with a piece of `value` — and nowhere in `resolveDraftSlot` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `resolveDraftSlot` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/3-targets/mongo/1-target/src/core/bson-codec-helpers.ts:124 — `decodeBsonValue` is exported, takes a document from its caller (line 143) and hands it to `decodeValue`, which calls itself at line 124 (`decodeValue`) with a piece of `value` (and at line 129) — and nowhere in `decodeValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `decodeValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/3-targets/mongo/1-target/src/core/json-codec-helpers.ts:93 — `encodeJsonValue` is exported, takes a document from its caller (line 106) and hands it to `assertJsonValue`, which calls itself at line 93 (`assertJsonValue`) with a piece of `value` (and at line 97) — and nowhere in `assertJsonValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `assertJsonValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/3-targets/mongo/1-target/src/core/json-codec-helpers.ts:174 — `decodeJsonValue` is exported, takes a document from its caller (line 188) and hands it to `decodeValue`, which calls itself at line 174 (`decodeValue`) with a piece of `value` — and nowhere in `decodeValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `decodeValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/3-targets/mongo/1-target/src/core/migrations/mongo-ops-serializer.ts:442 — `deserializePipelineStage` is exported, takes a document from its caller (line 469) and hands it to `deserializeFilterExpr`, which calls itself at line 442 (`deserializeFilterExpr`) with a piece of `json` (and at line 446, line 450) — and nowhere in `deserializeFilterExpr` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deserializeFilterExpr` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/3-targets/mongo/1-target/src/core/migrations/mongo-ops-serializer.ts:511 — `deserializePipelineStage` is exported and takes `json: unknown` from its caller, and it calls itself at line 511 (`deserializePipelineStage`) with a piece of `json` (and at line 549) — and nowhere in `deserializePipelineStage` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deserializePipelineStage` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/2-sql-family/1-core/schema-ir/src/naming.ts:253 — `normalizeIndexOptionValue` is exported, takes a document from its caller (line 245) and hands it to `withSortedKeys`, which calls itself at line 253 (`withSortedKeys`) with a piece of `value` (and at line 258) — and nowhere in `withSortedKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `withSortedKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/2-mongo-family/7-runtime/src/codecs/decoding.ts:196 — `decodeMongoRow` is exported, takes a document from its caller (line 89) and hands it to `walkField`, which calls itself at line 196 (`walkField`) with a piece of `value` — and nowhere in `walkField` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `walkField` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/2-mongo-family/5-query-builders/orm/src/model-stored-names.ts:109 — `storedPathOfCallerPath` is exported and takes `names: ModelStoredNames` from its caller, and it calls itself at line 109 (`storedPathOfCallerPath`) with a piece of `names` (and at line 111) — and nowhere in `storedPathOfCallerPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `storedPathOfCallerPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/2-mongo-family/5-query-builders/orm/src/model-stored-names.ts:156 — `rowOfStoredDocument` is exported and takes `document: Record<string, unknown>` from its caller, and it calls itself at line 156 (`rowOfStoredDocument`) with a piece of `document` — and nowhere in `rowOfStoredDocument` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `rowOfStoredDocument` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/2-mongo-family/5-query-builders/orm/src/model-stored-names.ts:179 — `storedDocumentOfRow` is exported and takes `row: Record<string, unknown>` from its caller, and it calls itself at line 179 (`storedDocumentOfRow`) with a piece of `row` — and nowhere in `storedDocumentOfRow` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `storedDocumentOfRow` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/2-mongo-family/4-query/query-ast/src/result-shape.ts:32 — `freezeMongoFieldShape` is exported and takes `shape: MongoFieldShape` from its caller, and it calls itself at line 32 (`freezeMongoFieldShape`) with a piece of `shape` (and at line 45) — and nowhere in `freezeMongoFieldShape` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `freezeMongoFieldShape` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/2-mongo-family/3-tooling/mongo-schema-ir/src/index-equivalence.ts:15 — `deepEqual` is exported and takes `a: unknown` from its caller, and it calls itself at line 15 (`deepEqual`) with a piece of `a` (and at line 29) — and nowhere in `deepEqual` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deepEqual` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/2-mongo-family/1-foundation/mongo-contract/src/canonicalize.ts:5 — `canonicalize` is exported and takes `obj: unknown` from its caller, and it calls itself at line 5 (`canonicalize`) with a piece of `obj` (and at line 8) — and nowhere in `canonicalize` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `canonicalize` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/3-tooling/emitter/src/domain-type-generation.ts:44 — `serializeValue` is exported and takes `value: unknown` from its caller, and it calls itself at line 44 (`serializeValue`) with a piece of `value` (and at line 53) — and nowhere in `serializeValue` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `serializeValue` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/3-tooling/cli/src/utils/command-helpers.ts:275 — `metaWithoutConnectionString` is exported, takes a document from its caller (line 269) and hands it to `clean`, which calls itself at line 275 (`clean`) with a piece of `value` (and at line 277) — and nowhere in `clean` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `clean` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/2-authoring/psl-parser/src/contributed-type-scope.ts:132 — `contributedTypeAt` is exported and takes `namespace: ContributedTypeNamespace` from its caller, and it calls itself at line 132 (`contributedTypeAt`) with a piece of `namespace` — and nowhere in `contributedTypeAt` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `contributedTypeAt` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/2-authoring/psl-parser/src/contributed-type-scope.ts:154 — `writtenContributedTypeCodecId` is exported, takes a document from its caller (line 136) and hands it to `codecIdAtPath`, which calls itself at line 154 (`codecIdAtPath`) with a piece of `namespace` — and nowhere in `codecIdAtPath` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `codecIdAtPath` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/2-authoring/psl-parser/src/contributed-type-scope.ts:187 — `contributedTypeScope` is exported, takes a document from its caller (line 162) and hands it to `collect`, which calls itself at line 187 (`collect`) with a piece of `namespace` — and nowhere in `collect` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `collect` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/1-core/ts-render/src/json-to-ts-source.ts:42 — `jsonToTsSource` is exported and takes `value: unknown` from its caller, and it calls itself at line 42 (`jsonToTsSource`) with a piece of `value` (and at line 48) — and nowhere in `jsonToTsSource` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `jsonToTsSource` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/1-core/framework-components/src/utils/canonicalize-json.ts:6 — `canonicalizeJson` is exported, takes a document from its caller (line 20) and hands it to `sortKeys`, which calls itself at line 6 (`sortKeys`) with a piece of `value` (and at line 10) — and nowhere in `sortKeys` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `sortKeys` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/1-core/framework-components/src/shared/authoring-type-choice.ts:429 — `assertTypeChoicesValid` is exported and takes `contributed: AuthoringTypeNamespace` from its caller, and it calls itself at line 429 (`assertTypeChoicesValid`) with a piece of `contributed` — and nowhere in `assertTypeChoicesValid` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `assertTypeChoicesValid` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/1-core/framework-components/src/shared/authoring-type-constructor-call.ts:32 — `authoringTypeConstructors` is exported and takes `namespace: AuthoringTypeNamespace` from its caller, and it calls itself at line 32 (`authoringTypeConstructors`) with a piece of `namespace` — and nowhere in `authoringTypeConstructors` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `authoringTypeConstructors` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • Recursive walk over a caller-supplied document has no depth cap packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:787 — `mergeAuthoringNamespaces` is exported, takes a document from its caller (line 812) and hands it to `deepCopyNamespace`, which calls itself at line 787 (`deepCopyNamespace`) with a piece of `source` — and nowhere in `deepCopyNamespace` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deepCopyNamespace` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
  • + 11 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×34
  • Swallowed exception (caught, then discarded) upgrade-instructions/releases/8.0.0-rc.22-to-8.0.0-rc.23/sources/mongo-index-names/app/scripts/mongo-index-names.ts:235 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) upgrade-instructions/releases/8.0.0-rc.22-to-8.0.0-rc.23/sources/mongo-index-names/app/scripts/mongo-index-names.ts:292 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:197 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:213 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:251 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:267 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/extension/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts:108 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:175 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/extension/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:273 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/extension/upgrades/0.13-to-0.14/uuid-preset-rename.ts:30 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/extension/upgrades/0.11-to-0.12/migrate-contract-testing-imports.ts:40 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/extension/upgrades/0.11-to-0.12/regenerate-extension-public-baseline.ts:54 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:221 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.22-to-8.0.0-rc.23/scripts/mongo-index-names/mongo-index-names.ts:235 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.22-to-8.0.0-rc.23/scripts/mongo-index-names/mongo-index-names.ts:292 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:251 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:267 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/app/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts:108 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) REDACTED:175 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:273 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/uuid-preset-rename.ts:30 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/app/upgrades/0.12-to-0.13/re-emit-mti-variant-link-columns.ts:58 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-closed-mongo-contracts.ts:58 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-domain-namespaced-contracts.ts:53 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • Swallowed exception (caught, then discarded) skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts:54 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
  • + 9 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×27
  • No test reaches this file packages/2-sql-family/2-authoring/contract-ts/src/contract-types.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 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 upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.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 upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.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 upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.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 packages/1-framework/3-tooling/cli/scripts/record.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 upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.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 upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.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 skills-contrib/review-fetch-phase/scripts/fetch-review-state.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file scripts/regen-example-migrations.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/3-extensions/supabase/scripts/generate-contract.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file packages/1-framework/3-tooling/cli/recordings/config.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 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 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 upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.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 upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.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 scripts/regen-extension-migrations.mjs:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
  • No test reaches this file skills/prisma-8/upgrading/app/upgrades/0.9-to-0.10/stamp-storage-types-kind.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 skills/prisma-8/upgrading/extension/upgrades/0.9-to-0.10/stamp-storage-types-kind.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 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 packages/2-mongo-family/6-transport/mongo-wire/src/wire-commands.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.
  • + 2 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED · ×19
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
R4 · Test Coverage · This test file cannot be loaded · ×13
  • This test file cannot be loaded packages/1-framework/3-tooling/cli/recordings/fixtures/prisma.config.ts:7 — packages/1-framework/3-tooling/cli/recordings/fixtures/prisma.config.ts:7 imports './contract', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded packages/2-sql-family/1-core/contract/test/value-type-maps.display.test.ts:7 — packages/2-sql-family/1-core/contract/test/value-type-maps.display.test.ts:7 imports './value-type-maps-display.ts', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/authoring/templates/prisma.config.parity-psl.ts:9 — test/integration/test/authoring/templates/prisma.config.parity-psl.ts:9 imports './packs', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/authoring/templates/prisma.config.parity-ts.ts:8 — test/integration/test/authoring/templates/prisma.config.parity-ts.ts:8 imports './contract', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-init-with-contract-space/prisma.config.with-db.ts:7 — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-init-with-contract-space/prisma.config.with-db.ts:7 imports '../../../../contract-space-fixture/control', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces-sqlite/prisma.config.racing.with-db.ts:4 — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces-sqlite/prisma.config.racing.with-db.ts:4 imports '../../../../contract-space-fixture/sqlite', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces-sqlite/prisma.config.with-db.ts:3 — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces-sqlite/prisma.config.with-db.ts:3 imports '../../../../contract-space-fixture/sqlite', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces/prisma.config.racing.with-db.ts:7 — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces/prisma.config.racing.with-db.ts:7 imports '../../../../contract-space-fixture/control', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either (1 further unresolvable import(s) in the same file). The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces/prisma.config.with-db.ts:7 — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/db-sign-spaces/prisma.config.with-db.ts:7 imports '../../../../contract-space-fixture/control', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/migrate-external-space/prisma.config.with-db.ts:7 — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/migrate-external-space/prisma.config.with-db.ts:7 imports '../../../../contract-space-fixture/external-space', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/mongo-cli-journeys/prisma.config.with-db.ts:7 — test/integration/test/fixtures/cli/cli-e2e-test-app/fixtures/mongo-cli-journeys/prisma.config.with-db.ts:7 imports './contract', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/upgrade-instructions/client-takes-contract-value/fixtures/refused/before/src/import-equals.ts:5 — test/integration/test/upgrade-instructions/client-takes-contract-value/fixtures/refused/before/src/import-equals.ts:5 imports './path', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
  • This test file cannot be loaded test/integration/test/upgrade-instructions/client-takes-contract-value/fixtures/refused/before/src/reexport.ts:5 — test/integration/test/upgrade-instructions/client-takes-contract-value/fixtures/refused/before/src/reexport.ts:5 imports './other', which names no file in this repository — and no rule in its .gitignore chain could cover one, so no build writes it either. The import throws as the runner collects this file, so none of its test cases run and nothing it was written to verify is verified. Restore the missing module or delete the test. It is excluded from the reachability measured above, because a file that cannot load reaches nothing.
D3 · God Classes · ClassTooLong · ×10
  • ClassTooLong: CollectionBase packages/3-extensions/sql-orm-client/src/collection.ts:389 — ClassTooLong — 1635 significant lines (blank, comment-only and punctuation-only lines excluded), 112 methods. The bar is 400 significant lines; this is 1235 over it, 4.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SqlRuntimeBase packages/2-sql-family/5-runtime/src/sql-runtime.ts:266 — ClassTooLong — 1011 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 400 significant lines; this is 611 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PostgresControlAdapter packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:203 — ClassTooLong — 916 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 516 over it, 2.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: MongoCollectionImpl packages/2-mongo-family/5-query-builders/orm/src/collection.ts:276 — ClassTooLong — 864 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. The bar is 400 significant lines; this is 464 over it, 2.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PostgresMigration packages/3-targets/postgres/1-target/src/core/migrations/postgres-migration.ts:116 — ClassTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded), 59 methods. The bar is 400 significant lines; this is 239 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SqliteMigrationRunner packages/3-targets/sqlite/1-target/src/core/migrations/runner.ts:71 — ClassTooLong — 598 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 198 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PostgresMigrationRunner packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:151 — ClassTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 149 over it, 1.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: ControlClientImpl packages/1-framework/3-tooling/cli/src/control-api/client.ts:93 — ClassTooLong — 473 significant lines (blank, comment-only and punctuation-only lines excluded), 25 methods. The bar is 400 significant lines; this is 73 over it, 1.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: PipelineChain packages/2-mongo-family/5-query-builders/query-builder/src/builder.ts:119 — ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 400 significant lines; this is 28 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • ClassTooLong: SqliteControlAdapter packages/3-targets/sqlite/2-adapter/src/core/control-adapter.ts:138 — ClassTooLong — 419 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 19 over it, 1.05× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D30 · Dependency Vulnerabilities · Medium CVE · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D35 · Change Coupling · Change coupling · ×9
  • Change coupling: control-adapter.ts ↔ control-adapter.ts packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:1 — `packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts` and `packages/3-targets/sqlite/2-adapter/src/core/control-adapter.ts` 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 — 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 `c58216a9` refactor: retype all SQL .query call sites to SqlControlDriverInstance (at that commit the files were still `packages/3-targets/6-adapters/postgres/src/core/control-adapter.ts` and `packages/3-targets/6-adapters/sqlite/src/core/control-adapter.ts`); `bcb1a0a2` TML-2770: migration log reads the ledger as one flat chronological ta… (at that commit the files were still `packages/3-targets/6-adapters/postgres/src/core/control-adapter.ts` and `packages/3-targets/6-adapters/sqlite/src/core/control-adapter.ts`); `0f197f28` fix(migration-ledger): address PR review on the per-migration journal (at that commit the files were still `packages/3-targets/6-adapters/postgres/src/core/control-adapter.ts` and `packages/3-targets/6-adapters/sqlite/src/core/control-adapter.ts`) — run `git show` on any of them.
  • Change coupling: factories.ts ↔ validators.ts packages/2-sql-family/1-core/contract/src/factories.ts:1 — `packages/2-sql-family/1-core/contract/src/factories.ts` and `packages/2-sql-family/1-core/contract/src/validators.ts` change together 59% of the time (10 of the 17 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `1aed675f` fix(contract): address PR review feedback on value objects (at that commit the files were still `packages/2-sql/1-core/contract/src/factories.ts` and `packages/2-sql/1-core/contract/src/validators.ts`); `ae790790` SqlStorage extends StorageBase, carrying storageHash (at that commit the files were still `packages/2-sql/1-core/contract/src/factories.ts` and `packages/2-sql/1-core/contract/src/validators.ts`); `5fb8320e` Update sql-contract, emitter, and contract-ts tests for removed fields (at that commit the files were still `packages/2-sql/1-core/contract/src/factories.ts` and `packages/2-sql/1-core/contract/src/validators.ts`) — run `git show` on any of them.
  • Change coupling: db-init.ts ↔ db-update.ts packages/1-framework/3-tooling/cli/src/control-api/operations/db-init.ts:1 — `packages/1-framework/3-tooling/cli/src/control-api/operations/db-init.ts` and `packages/1-framework/3-tooling/cli/src/control-api/operations/db-update.ts` change together 58% of the time (14 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 14 shared commits counted here, the most recent 3 are `bf5f76e4` refactor(cli): rename control-api apply operation files to run/migrat…; `4437de79` refactor(cli): purge control-api apply vocabulary to run (TML-2780); `f90d5649` refactor(framework): drop Aggregate qualifier from public planner/app… — run `git show` on any of them.
  • Change coupling: mongo-adapter.ts ↔ mongo-driver.ts packages/3-targets/mongo/2-adapter/src/mongo-adapter.ts:1 — `packages/3-targets/mongo/2-adapter/src/mongo-adapter.ts` and `packages/3-targets/mongo/3-driver/src/mongo-driver.ts` change together 56% of the time (10 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `c9b92131` feat(mongo): extend find-and-modify AST/wire with sort, skip, returnD… (at that commit the files were still `packages/3-mongo-target/2-mongo-adapter/src/mongo-adapter.ts` and `packages/3-mongo-target/3-mongo-driver/src/mongo-driver.ts`); `d4435286` feat(mongo-query-builder): add find-and-modify and upsert terminals (M3) (at that commit the files were still `packages/3-mongo-target/2-mongo-adapter/src/mongo-adapter.ts` and `packages/3-mongo-target/3-mongo-driver/src/mongo-driver.ts`); `f1117998` refactor: extract @prisma-next/mongo-lowering from mongo-core (at that commit the files were still `packages/3-mongo-target/2-mongo-adapter/src/mongo-adapter.ts` and `packages/3-mongo-target/3-mongo-driver/src/mongo-driver.ts`) — run `git show` on any of them.
  • Change coupling: default-function-registry.ts ↔ interpreter.ts packages/2-sql-family/2-authoring/contract-psl/src/default-function-registry.ts:1 — `packages/2-sql-family/2-authoring/contract-psl/src/default-function-registry.ts` and `packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 6 shared commits counted here, the most recent 3 are `af4d0361` refactor(sql-contract-psl): remove re-exports from default-function-r… (at that commit the files were still `packages/2-sql/2-authoring/contract-psl/src/default-function-registry.ts` and `packages/2-sql/2-authoring/contract-psl/src/interpreter.ts`); `9e002c9e` fix: adapt to upstream ContractSourceContext and nativeType expansion… (at that commit the files were still `packages/2-sql/2-authoring/contract-psl/src/default-function-registry.ts` and `packages/2-sql/2-authoring/contract-psl/src/interpreter.ts`); `cf13c964` refactor(sql): make mutation defaults fully composition-owned (at that commit the files were still `packages/2-sql/2-authoring/contract-psl/src/default-function-registry.ts` and `packages/2-sql/2-authoring/contract-psl/src/interpreter.ts`) — run `git show` on any of them.
  • Change coupling: control.ts ↔ runtime.ts packages/3-targets/postgres/1-target/src/exports/control.ts:1 — `packages/3-targets/postgres/1-target/src/exports/control.ts` and `packages/3-targets/postgres/1-target/src/exports/runtime.ts` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) 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 6 shared commits counted here, the most recent 3 are `07c19aac` Trim redundant JSDoc from descriptor modules (at that commit the files were still `packages/3-targets/3-targets/postgres/src/exports/control.ts` and `packages/3-targets/3-targets/postgres/src/exports/runtime.ts`); `031beec8` refactor(target-postgres): DRY metadata across pack/control/runtime (at that commit the files were still `packages/3-targets/3-targets/postgres/src/exports/control.ts` and `packages/3-targets/3-targets/postgres/src/exports/runtime.ts`); `113b0014` feat: strip manifest property from ComponentDescriptor and all concre… (at that commit the files were still `packages/3-targets/3-targets/postgres/src/exports/control.ts` and `packages/3-targets/3-targets/postgres/src/exports/runtime.ts`) — run `git show` on any of them.
  • Change coupling: collection-dispatch.ts ↔ query-plan-select.ts packages/3-extensions/sql-orm-client/src/collection-dispatch.ts:1 — `packages/3-extensions/sql-orm-client/src/collection-dispatch.ts` and `packages/3-extensions/sql-orm-client/src/query-plan-select.ts` change together 54% of the time (20 of the 37 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 20 shared commits counted here, the most recent 3 are `2086e7c8` docs(sql-orm-client): correct stale nested-mutation JSDoc and sweep d…; `e9e67a9a` TML-2980: support variant-declared relations in SQL ORM includes (#976); `e7ce0358` TML-2785: M:N slice 1 — correlated include read through the junction … — run `git show` on any of them.
  • Change coupling: budgets.ts ↔ lints.ts packages/2-sql-family/5-runtime/src/middleware/budgets.ts:1 — `packages/2-sql-family/5-runtime/src/middleware/budgets.ts` and `packages/2-sql-family/5-runtime/src/middleware/lints.ts` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `c6b86321` Wire budgets severities.latency; drop dead unindexedPredicate lint ke… (at that commit the files were still `packages/2-sql/5-runtime/src/middleware/budgets.ts` and `packages/2-sql/5-runtime/src/middleware/lints.ts`); `815feb3d` feat(sql-runtime): add beforeCompile middleware hook (#373) (at that commit the files were still `packages/2-sql/5-runtime/src/middleware/budgets.ts` and `packages/2-sql/5-runtime/src/middleware/lints.ts`); `9dcf1c17` Strengthen middleware compatibility validation and error reporting (at that commit the files were still `packages/2-sql/5-runtime/src/middleware/budgets.ts` and `packages/2-sql/5-runtime/src/middleware/lints.ts`) — run `git show` on any of them.
  • Change coupling: postgres.ts ↔ sqlite.ts packages/3-targets/postgres/9-facade/src/runtime/postgres.ts:1 — `packages/3-targets/postgres/9-facade/src/runtime/postgres.ts` and `packages/3-targets/sqlite/9-facade/src/runtime/sqlite.ts` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `0fcea1b6` feat: connect() on a client is safe to call again (#30899); `c8a44c99` feat: whole-query raw gets its own lane at db.raw.sql (TML-3214) (#30… (at that commit the files were still `packages/3-extensions/postgres/src/runtime/postgres.ts` and `packages/3-extensions/sqlite/src/runtime/sqlite.ts`); `29859941` TML-3206: Codec ids are checked where they are authored (stacked on #… (at that commit the files were still `packages/3-extensions/postgres/src/runtime/postgres.ts` and `packages/3-extensions/sqlite/src/runtime/sqlite.ts`) — run `git show` on any of them.
D5 · Coupling · Off the main sequence · ×9
  • Off the main sequence: @internal/mongo-value — @internal/mongo-value: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
  • Off the main sequence: @internal/publish-surface — @internal/publish-surface: 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: @internal/sql-errors — @internal/sql-errors: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
  • Off the main sequence: @internal/errors — @internal/errors: abstractness 0.00, instability 0.10, distance 0.90 — zone of pain — concrete and depended on by 19 project(s), so it's rigid to change.
  • Off the main sequence: @internal/sql-operations — @internal/sql-operations: abstractness 0.00, instability 0.13, distance 0.88 — zone of pain — concrete and depended on by 14 project(s), so it's rigid to change.
  • Off the main sequence: @internal/utils — @internal/utils: abstractness 0.16, instability 0.00, distance 0.84 — zone of pain — concrete and depended on by 61 project(s), so it's rigid to change.
  • Off the main sequence: @internal/type-implementations — @internal/type-implementations: abstractness 0.20, instability 0.00, distance 0.80 — zone of pain — concrete and depended on by 3 project(s), so it's rigid to change.
  • Off the main sequence: @internal/sql-schema-ir — @internal/sql-schema-ir: abstractness 0.06, instability 0.20, distance 0.74 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
  • Off the main sequence: @internal/ids — @internal/ids: abstractness 0.00, instability 0.29, distance 0.71 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
D10 · Test Quality · Fixed-sleep synchronisation · ×8
  • Fixed-sleep synchronisation: close() closes the client in the same call, so a lazy read awaited a turn of the event loop later is refused packages/3-targets/postgres/9-facade/test/postgres-close.test.ts:452 — This test starts work it did not wait for (`pending`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: warns once when it waits only for open activity handles packages/2-sql-family/5-runtime/test/client-activity.test.ts:362 — This test starts work it did not wait for (`closing`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 20))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: waits for an open activity on the runtime to end packages/2-sql-family/5-runtime/test/client-activity.test.ts:377 — This test starts work it did not wait for (`closing`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 10))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: resolves only after the commit finalization hooks have run packages/2-sql-family/5-runtime/test/with-transaction.failures.test.ts:165 — This test starts work it did not wait for (`committing`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: resolves the statement only after every finalized hook has resolved packages/1-framework/1-core/framework-components/test/statement-activity.errors.test.ts:186 — This test starts work it did not wait for (`pending`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: finalizes a statement still running when the transaction ends after it ends, with the transaction outcome packages/1-framework/1-core/framework-components/test/transaction-activity.test.ts:174 — This test starts work it did not wait for (`running`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: does not wait for a statement still running when the transaction ends packages/1-framework/1-core/framework-components/test/transaction-activity.test.ts:216 — This test starts work it did not wait for (`running`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
  • Fixed-sleep synchronisation: resolves end only after every finalized hook has resolved packages/1-framework/1-core/framework-components/test/transaction-activity.test.ts:269 — This test starts work it did not wait for (`ending`, still running when the sleep starts) and then orders itself against it with `new Promise((resolve) => setTimeout(resolve, 0))` — a fixed wait, not a signal that the work is done. Whether it passes depends on how loaded the machine is, which is why a test written this way is green on a developer's box and random in CI. Wait for the event itself instead: the process's own exit or output, a completion handle, or a condition polled to a timeout.
D3 · God Classes · MethodTooLong · ×6
  • MethodTooLong: PostgresControlAdapter.introspectSchema packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:859 — MethodTooLong — introspectSchema runs 474 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 374 over it, 4.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: MongoMigrationRunner.apply packages/3-targets/mongo/1-target/src/core/migrations/mongo-runner.ts:248 — MethodTooLong — apply runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
  • MethodTooLong: SqliteMigrationPlanner.planSql packages/3-targets/sqlite/1-target/src/core/migrations/planner.ts:181 — MethodTooLong — planSql 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.
  • MethodTooLong: SqlRuntimeBase.wrapTransaction packages/2-sql-family/5-runtime/src/sql-runtime.ts:1440 — MethodTooLong — wrapTransaction 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.
  • MethodTooLong: SqliteControlAdapter.introspect packages/3-targets/sqlite/2-adapter/src/core/control-adapter.ts:574 — MethodTooLong — introspect runs 111 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 11 over it, 1.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.
  • MethodTooLong: MongoAdapterImpl.structuralLower packages/3-targets/mongo/2-adapter/src/mongo-adapter.ts:94 — MethodTooLong — structuralLower runs 109 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 9 over it, 1.09× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D3 · God Classes · TooManyMethods · ×6
  • TooManyMethods: CollectionBase packages/3-extensions/sql-orm-client/src/collection.ts:389 — TooManyMethods — 112 methods. The bar is 30 methods; this is 82 over it, 3.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: MongoCollectionImpl packages/2-mongo-family/5-query-builders/orm/src/collection.ts:276 — TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PostgresMigration packages/3-targets/postgres/1-target/src/core/migrations/postgres-migration.ts:116 — TooManyMethods — 59 methods. The bar is 30 methods; this is 29 over it, 1.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: SqlRuntimeBase packages/2-sql-family/5-runtime/src/sql-runtime.ts:266 — TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: PipelineChain packages/2-mongo-family/5-query-builders/query-builder/src/builder.ts:119 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
  • TooManyMethods: Project packages/1-framework/3-tooling/language-server/src/project.ts:75 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
X3 · Exception handling · Swallowed exception (empty catch) · ×6
  • Swallowed exception (empty catch) skills/prisma-8/upgrading/extension/upgrades/0.8-to-0.9/strip-inline-contracts.ts:60 — 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) skills/prisma-8/upgrading/app/upgrades/0.8-to-0.9/strip-inline-contracts.ts:60 — 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) scripts/lint-ratchets.mjs:123 — 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) scripts/regen-example-migrations.mjs:400 — 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) scripts/rules-footprint.mjs:115 — 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) scripts/run-logged.mjs:70 — 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.
D2 · Cognitive Complexity · add-model-map.addModelMapsWithReport (cognitive 21) · ×5
  • add-model-map.addModelMapsWithReport (cognitive 21) scripts/codemods/add-model-map.mjs:147 — add-model-map.addModelMapsWithReport has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • add-model-map.addModelMapsWithReport (cognitive 21) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs:147 — add-model-map.addModelMapsWithReport has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • add-model-map.addModelMapsWithReport (cognitive 21) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs:147 — add-model-map.addModelMapsWithReport has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • add-model-map.addModelMapsWithReport (cognitive 21) upgrade-instructions/releases/8.0.0-rc.11-to-8.0.0-rc.12/sources/psl-verbatim-table-names/app/scripts/add-model-map.mjs:147 — add-model-map.addModelMapsWithReport has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • add-model-map.addModelMapsWithReport (cognitive 21) upgrade-instructions/releases/8.0.0-rc.11-to-8.0.0-rc.12/sources/psl-verbatim-table-names/extension/scripts/add-model-map.mjs:147 — add-model-map.addModelMapsWithReport has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×5
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D1 · Cyclomatic Complexity · data-type-in-contract.main (cyclomatic 63) · ×4
  • data-type-in-contract.main (cyclomatic 63) REDACTED:1292 — data-type-in-contract.main has cyclomatic complexity 63 (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.
  • data-type-in-contract.main (cyclomatic 63) REDACTED:1292 — data-type-in-contract.main has cyclomatic complexity 63 (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.
  • data-type-in-contract.main (cyclomatic 63) REDACTED:1292 — data-type-in-contract.main has cyclomatic complexity 63 (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.
  • data-type-in-contract.main (cyclomatic 63) REDACTED:1292 — data-type-in-contract.main has cyclomatic complexity 63 (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.
D1 · Cyclomatic Complexity · data-type-in-contract.rewriteDts (cyclomatic 53) · ×4
  • data-type-in-contract.rewriteDts (cyclomatic 53) REDACTED:1037 — data-type-in-contract.rewriteDts has cyclomatic complexity 53 (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.
  • data-type-in-contract.rewriteDts (cyclomatic 53) REDACTED:1037 — data-type-in-contract.rewriteDts has cyclomatic complexity 53 (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.
  • data-type-in-contract.rewriteDts (cyclomatic 53) REDACTED:1037 — data-type-in-contract.rewriteDts has cyclomatic complexity 53 (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.
  • data-type-in-contract.rewriteDts (cyclomatic 53) REDACTED:1037 — data-type-in-contract.rewriteDts has cyclomatic complexity 53 (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.
D1 · Cyclomatic Complexity · data-type-in-contract.rewriteSqliteEnums (cyclomatic 45) · ×4
  • data-type-in-contract.rewriteSqliteEnums (cyclomatic 45) REDACTED:565 — data-type-in-contract.rewriteSqliteEnums has cyclomatic complexity 45 (threshold 15). Of this number, 19 points are the body's own statements and 26 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.rewriteSqliteEnums (cyclomatic 45) REDACTED:565 — data-type-in-contract.rewriteSqliteEnums has cyclomatic complexity 45 (threshold 15). Of this number, 19 points are the body's own statements and 26 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.rewriteSqliteEnums (cyclomatic 45) REDACTED:565 — data-type-in-contract.rewriteSqliteEnums has cyclomatic complexity 45 (threshold 15). Of this number, 19 points are the body's own statements and 26 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.rewriteSqliteEnums (cyclomatic 45) REDACTED:565 — data-type-in-contract.rewriteSqliteEnums has cyclomatic complexity 45 (threshold 15). Of this number, 19 points are the body's own statements and 26 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · rewrite-sql-strings.stringRanges (cyclomatic 35) · ×4
  • rewrite-sql-strings.stringRanges (cyclomatic 35) scripts/codemods/rewrite-sql-strings.mjs:160 — rewrite-sql-strings.stringRanges has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • rewrite-sql-strings.stringRanges (cyclomatic 35) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.17-to-8.0.0-rc.18/scripts/sql-expression-literals-psl/rewrite-sql-strings.mjs:160 — rewrite-sql-strings.stringRanges has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • rewrite-sql-strings.stringRanges (cyclomatic 35) upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/app/scripts/rewrite-sql-strings.mjs:160 — rewrite-sql-strings.stringRanges has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • rewrite-sql-strings.stringRanges (cyclomatic 35) upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/extension/scripts/rewrite-sql-strings.mjs:160 — rewrite-sql-strings.stringRanges has cyclomatic complexity 35 (threshold 15). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
D1 · Cyclomatic Complexity · expand-type-aliases.rewriteContract (cyclomatic 27) · ×4
  • expand-type-aliases.rewriteContract (cyclomatic 27) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:456 — expand-type-aliases.rewriteContract has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.rewriteContract (cyclomatic 27) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:456 — expand-type-aliases.rewriteContract has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.rewriteContract (cyclomatic 27) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:451 — expand-type-aliases.rewriteContract has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.rewriteContract (cyclomatic 27) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:451 — expand-type-aliases.rewriteContract has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · data-type-in-contract.rewriteContract (cyclomatic 26) · ×4
  • data-type-in-contract.rewriteContract (cyclomatic 26) REDACTED:729 — data-type-in-contract.rewriteContract has cyclomatic complexity 26 (threshold 15). Of this number, 15 points are the body's own statements and 11 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.rewriteContract (cyclomatic 26) REDACTED:729 — data-type-in-contract.rewriteContract has cyclomatic complexity 26 (threshold 15). Of this number, 15 points are the body's own statements and 11 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.rewriteContract (cyclomatic 26) REDACTED:729 — data-type-in-contract.rewriteContract has cyclomatic complexity 26 (threshold 15). Of this number, 15 points are the body's own statements and 11 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.rewriteContract (cyclomatic 26) REDACTED:729 — data-type-in-contract.rewriteContract has cyclomatic complexity 26 (threshold 15). Of this number, 15 points are the body's own statements and 11 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · data-type-in-contract.literalEnd (cyclomatic 20) · ×4
  • data-type-in-contract.literalEnd (cyclomatic 20) REDACTED:980 — data-type-in-contract.literalEnd has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.literalEnd (cyclomatic 20) REDACTED:980 — data-type-in-contract.literalEnd has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.literalEnd (cyclomatic 20) REDACTED:980 — data-type-in-contract.literalEnd has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.literalEnd (cyclomatic 20) REDACTED:980 — data-type-in-contract.literalEnd has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · remove-nocheck.fieldsMappingColumns (cyclomatic 18) · ×4
  • remove-nocheck.fieldsMappingColumns (cyclomatic 18) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1909 — remove-nocheck.fieldsMappingColumns has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • remove-nocheck.fieldsMappingColumns (cyclomatic 18) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1909 — remove-nocheck.fieldsMappingColumns has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • remove-nocheck.fieldsMappingColumns (cyclomatic 18) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:432 — remove-nocheck.fieldsMappingColumns has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • remove-nocheck.fieldsMappingColumns (cyclomatic 18) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:432 — remove-nocheck.fieldsMappingColumns has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · expand-type-aliases.mergedSnapshots (cyclomatic 18) · ×4
  • expand-type-aliases.mergedSnapshots (cyclomatic 18) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:924 — expand-type-aliases.mergedSnapshots has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
  • expand-type-aliases.mergedSnapshots (cyclomatic 18) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:924 — expand-type-aliases.mergedSnapshots has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
  • expand-type-aliases.mergedSnapshots (cyclomatic 18) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:899 — expand-type-aliases.mergedSnapshots has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
  • expand-type-aliases.mergedSnapshots (cyclomatic 18) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:899 — expand-type-aliases.mergedSnapshots has cyclomatic complexity 18 (threshold 15). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
D1 · Cyclomatic Complexity · data-type-in-contract.genericArgumentEnd (cyclomatic 17) · ×4
  • data-type-in-contract.genericArgumentEnd (cyclomatic 17) REDACTED:945 — data-type-in-contract.genericArgumentEnd has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.genericArgumentEnd (cyclomatic 17) REDACTED:945 — data-type-in-contract.genericArgumentEnd has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.genericArgumentEnd (cyclomatic 17) REDACTED:945 — data-type-in-contract.genericArgumentEnd has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-in-contract.genericArgumentEnd (cyclomatic 17) REDACTED:945 — data-type-in-contract.genericArgumentEnd has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · expand-type-aliases.topLevelMembers (cyclomatic 17) · ×4
  • expand-type-aliases.topLevelMembers (cyclomatic 17) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:646 — expand-type-aliases.topLevelMembers has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.topLevelMembers (cyclomatic 17) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:646 — expand-type-aliases.topLevelMembers has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.topLevelMembers (cyclomatic 17) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:623 — expand-type-aliases.topLevelMembers has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.topLevelMembers (cyclomatic 17) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:623 — expand-type-aliases.topLevelMembers has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D17 · Explicit Debt · TodoComment · ×4
  • TodoComment packages/2-mongo-family/5-query-builders/orm/src/types.ts:356 — // TODO(TML-2229): VariantModelRow flows through ResolvedOutputRow, so variant
  • TodoComment packages/1-framework/3-tooling/cli/src/control-api/client.ts:559 — // TODO: Pass schema option to familyInstance.introspect when schema filtering is implemented — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment examples/react-router-demo/app/lib/db.server.ts:47 — // TODO(TML-2368): replace this example-local cache with a hash-keyed dev
  • TodoComment apps/telemetry-backend/src/handler.ts:184 — // TODO: use prepared statements once they are implemented for inserts. — 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.
D2 · Cognitive Complexity · data-type-in-contract.rewriteSqliteEnums (cognitive 99) · ×4
  • data-type-in-contract.rewriteSqliteEnums (cognitive 99) REDACTED:565 — data-type-in-contract.rewriteSqliteEnums has cognitive complexity 99 (threshold 15). Drivers by points: ternaries 21 (53 pts), if/else 11 (35 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 59). Of this number, 38 points are the body's own statements and 61 belong to 10 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • data-type-in-contract.rewriteSqliteEnums (cognitive 99) REDACTED:565 — data-type-in-contract.rewriteSqliteEnums has cognitive complexity 99 (threshold 15). Drivers by points: ternaries 21 (53 pts), if/else 11 (35 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 59). Of this number, 38 points are the body's own statements and 61 belong to 10 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • data-type-in-contract.rewriteSqliteEnums (cognitive 99) REDACTED:565 — data-type-in-contract.rewriteSqliteEnums has cognitive complexity 99 (threshold 15). Drivers by points: ternaries 21 (53 pts), if/else 11 (35 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 59). Of this number, 38 points are the body's own statements and 61 belong to 10 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • data-type-in-contract.rewriteSqliteEnums (cognitive 99) REDACTED:565 — data-type-in-contract.rewriteSqliteEnums has cognitive complexity 99 (threshold 15). Drivers by points: ternaries 21 (53 pts), if/else 11 (35 pts), loops 3 (6 pts), boolean chains 5 (nesting depth added 59). Of this number, 38 points are the body's own statements and 61 belong to 10 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · data-type-in-contract.main (cognitive 97) · ×4
  • data-type-in-contract.main (cognitive 97) REDACTED:1292 — data-type-in-contract.main has cognitive complexity 97 (threshold 15). Drivers by points: if/else 24 (48 pts), ternaries 10 (21 pts), loops 16 (18 pts), boolean chains 9, error handling 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.main (cognitive 97) REDACTED:1292 — data-type-in-contract.main has cognitive complexity 97 (threshold 15). Drivers by points: if/else 24 (48 pts), ternaries 10 (21 pts), loops 16 (18 pts), boolean chains 9, error handling 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.main (cognitive 97) REDACTED:1292 — data-type-in-contract.main has cognitive complexity 97 (threshold 15). Drivers by points: if/else 24 (48 pts), ternaries 10 (21 pts), loops 16 (18 pts), boolean chains 9, error handling 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.main (cognitive 97) REDACTED:1292 — data-type-in-contract.main has cognitive complexity 97 (threshold 15). Drivers by points: if/else 24 (48 pts), ternaries 10 (21 pts), loops 16 (18 pts), boolean chains 9, error handling 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rewrite-sql-strings.stringRanges (cognitive 74) · ×4
  • rewrite-sql-strings.stringRanges (cognitive 74) scripts/codemods/rewrite-sql-strings.mjs:160 — rewrite-sql-strings.stringRanges has cognitive complexity 74 (threshold 15). Drivers by points: if/else 19 (59 pts), boolean chains 9, loops 4 (6 pts) (nesting depth added 42). Of this number, 73 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • rewrite-sql-strings.stringRanges (cognitive 74) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.17-to-8.0.0-rc.18/scripts/sql-expression-literals-psl/rewrite-sql-strings.mjs:160 — rewrite-sql-strings.stringRanges has cognitive complexity 74 (threshold 15). Drivers by points: if/else 19 (59 pts), boolean chains 9, loops 4 (6 pts) (nesting depth added 42). Of this number, 73 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • rewrite-sql-strings.stringRanges (cognitive 74) upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/app/scripts/rewrite-sql-strings.mjs:160 — rewrite-sql-strings.stringRanges has cognitive complexity 74 (threshold 15). Drivers by points: if/else 19 (59 pts), boolean chains 9, loops 4 (6 pts) (nesting depth added 42). Of this number, 73 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • rewrite-sql-strings.stringRanges (cognitive 74) upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/extension/scripts/rewrite-sql-strings.mjs:160 — rewrite-sql-strings.stringRanges has cognitive complexity 74 (threshold 15). Drivers by points: if/else 19 (59 pts), boolean chains 9, loops 4 (6 pts) (nesting depth added 42). Of this number, 73 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-in-contract.rewriteDts (cognitive 62) · ×4
  • data-type-in-contract.rewriteDts (cognitive 62) REDACTED:1037 — data-type-in-contract.rewriteDts has cognitive complexity 62 (threshold 15). Drivers by points: if/else 16 (32 pts), loops 11, ternaries 5 (10 pts), boolean chains 9 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.rewriteDts (cognitive 62) REDACTED:1037 — data-type-in-contract.rewriteDts has cognitive complexity 62 (threshold 15). Drivers by points: if/else 16 (32 pts), loops 11, ternaries 5 (10 pts), boolean chains 9 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.rewriteDts (cognitive 62) REDACTED:1037 — data-type-in-contract.rewriteDts has cognitive complexity 62 (threshold 15). Drivers by points: if/else 16 (32 pts), loops 11, ternaries 5 (10 pts), boolean chains 9 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.rewriteDts (cognitive 62) REDACTED:1037 — data-type-in-contract.rewriteDts has cognitive complexity 62 (threshold 15). Drivers by points: if/else 16 (32 pts), loops 11, ternaries 5 (10 pts), boolean chains 9 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.rewriteContract (cognitive 53) · ×4
  • expand-type-aliases.rewriteContract (cognitive 53) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:456 — expand-type-aliases.rewriteContract has cognitive complexity 53 (threshold 15). Drivers by points: if/else 7 (21 pts), ternaries 9 (19 pts), loops 4 (7 pts), boolean chains 6 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.rewriteContract (cognitive 53) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:456 — expand-type-aliases.rewriteContract has cognitive complexity 53 (threshold 15). Drivers by points: if/else 7 (21 pts), ternaries 9 (19 pts), loops 4 (7 pts), boolean chains 6 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.rewriteContract (cognitive 53) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:451 — expand-type-aliases.rewriteContract has cognitive complexity 53 (threshold 15). Drivers by points: if/else 7 (21 pts), ternaries 9 (19 pts), loops 4 (7 pts), boolean chains 6 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.rewriteContract (cognitive 53) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:451 — expand-type-aliases.rewriteContract has cognitive complexity 53 (threshold 15). Drivers by points: if/else 7 (21 pts), ternaries 9 (19 pts), loops 4 (7 pts), boolean chains 6 (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.fieldsMappingColumns (cognitive 41) · ×4
  • remove-nocheck.fieldsMappingColumns (cognitive 41) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1909 — remove-nocheck.fieldsMappingColumns has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 7 (19 pts), if/else 4 (14 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.fieldsMappingColumns (cognitive 41) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1909 — remove-nocheck.fieldsMappingColumns has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 7 (19 pts), if/else 4 (14 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.fieldsMappingColumns (cognitive 41) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:432 — remove-nocheck.fieldsMappingColumns has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 7 (19 pts), if/else 4 (14 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.fieldsMappingColumns (cognitive 41) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:432 — remove-nocheck.fieldsMappingColumns has cognitive complexity 41 (threshold 15). Drivers by points: ternaries 7 (19 pts), if/else 4 (14 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.mergedSnapshots (cognitive 37) · ×4
  • expand-type-aliases.mergedSnapshots (cognitive 37) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:924 — expand-type-aliases.mergedSnapshots has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (19 pts), ternaries 2 (9 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 23). Of this number, 36 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.mergedSnapshots (cognitive 37) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:924 — expand-type-aliases.mergedSnapshots has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (19 pts), ternaries 2 (9 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 23). Of this number, 36 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.mergedSnapshots (cognitive 37) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:899 — expand-type-aliases.mergedSnapshots has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (19 pts), ternaries 2 (9 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 23). Of this number, 36 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.mergedSnapshots (cognitive 37) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:899 — expand-type-aliases.mergedSnapshots has cognitive complexity 37 (threshold 15). Drivers by points: if/else 6 (19 pts), ternaries 2 (9 pts), loops 4 (7 pts), boolean chains 2 (nesting depth added 23). Of this number, 36 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-in-contract.columnCardinalities (cognitive 27) · ×4
  • data-type-in-contract.columnCardinalities (cognitive 27) REDACTED:536 — data-type-in-contract.columnCardinalities has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (19 pts), loops 3 (6 pts), if/else 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.columnCardinalities (cognitive 27) REDACTED:536 — data-type-in-contract.columnCardinalities has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (19 pts), loops 3 (6 pts), if/else 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.columnCardinalities (cognitive 27) REDACTED:536 — data-type-in-contract.columnCardinalities has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (19 pts), loops 3 (6 pts), if/else 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.columnCardinalities (cognitive 27) REDACTED:536 — data-type-in-contract.columnCardinalities has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 7 (19 pts), loops 3 (6 pts), if/else 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-in-contract.rewriteContract (cognitive 26) · ×4
  • data-type-in-contract.rewriteContract (cognitive 26) REDACTED:729 — data-type-in-contract.rewriteContract has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 8, if/else 6 (8 pts), loops 1 (nesting depth added 5). Of this number, 18 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.rewriteContract (cognitive 26) REDACTED:729 — data-type-in-contract.rewriteContract has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 8, if/else 6 (8 pts), loops 1 (nesting depth added 5). Of this number, 18 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.rewriteContract (cognitive 26) REDACTED:729 — data-type-in-contract.rewriteContract has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 8, if/else 6 (8 pts), loops 1 (nesting depth added 5). Of this number, 18 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.rewriteContract (cognitive 26) REDACTED:729 — data-type-in-contract.rewriteContract has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 6 (9 pts), boolean chains 8, if/else 6 (8 pts), loops 1 (nesting depth added 5). Of this number, 18 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-from-json.topLevelNames (cognitive 26) · ×4
  • contract-from-json.topLevelNames (cognitive 26) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:90 — contract-from-json.topLevelNames has cognitive complexity 26 (threshold 15). Drivers by points: loops 4 (12 pts), if/else 6 (11 pts), boolean chains 3 (nesting depth added 13). 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.
  • contract-from-json.topLevelNames (cognitive 26) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:90 — contract-from-json.topLevelNames has cognitive complexity 26 (threshold 15). Drivers by points: loops 4 (12 pts), if/else 6 (11 pts), boolean chains 3 (nesting depth added 13). 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.
  • contract-from-json.topLevelNames (cognitive 26) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts:87 — contract-from-json.topLevelNames has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • contract-from-json.topLevelNames (cognitive 26) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:87 — contract-from-json.topLevelNames has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (8 pts), boolean chains 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rewrite-sql-strings.closingEnd (cognitive 23) · ×4
  • rewrite-sql-strings.closingEnd (cognitive 23) scripts/codemods/rewrite-sql-strings.mjs:73 — rewrite-sql-strings.closingEnd has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • rewrite-sql-strings.closingEnd (cognitive 23) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.17-to-8.0.0-rc.18/scripts/sql-expression-literals-psl/rewrite-sql-strings.mjs:73 — rewrite-sql-strings.closingEnd has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • rewrite-sql-strings.closingEnd (cognitive 23) upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/app/scripts/rewrite-sql-strings.mjs:73 — rewrite-sql-strings.closingEnd has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • rewrite-sql-strings.closingEnd (cognitive 23) upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/extension/scripts/rewrite-sql-strings.mjs:73 — rewrite-sql-strings.closingEnd has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (17 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-in-contract.sortTableArrays (cognitive 22) · ×4
  • data-type-in-contract.sortTableArrays (cognitive 22) REDACTED:272 — data-type-in-contract.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.sortTableArrays (cognitive 22) REDACTED:272 — data-type-in-contract.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.sortTableArrays (cognitive 22) REDACTED:272 — data-type-in-contract.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.sortTableArrays (cognitive 22) REDACTED:272 — data-type-in-contract.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.sortTableArrays (cognitive 22) · ×4
  • remove-nocheck.sortTableArrays (cognitive 22) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:177 — remove-nocheck.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.sortTableArrays (cognitive 22) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:177 — remove-nocheck.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.sortTableArrays (cognitive 22) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:175 — remove-nocheck.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.sortTableArrays (cognitive 22) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:175 — remove-nocheck.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.sortTableArrays (cognitive 22) · ×4
  • expand-type-aliases.sortTableArrays (cognitive 22) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:183 — expand-type-aliases.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.sortTableArrays (cognitive 22) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:183 — expand-type-aliases.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.sortTableArrays (cognitive 22) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:178 — expand-type-aliases.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.sortTableArrays (cognitive 22) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:178 — expand-type-aliases.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-in-contract.literalEnd (cognitive 20) · ×4
  • data-type-in-contract.literalEnd (cognitive 20) REDACTED:980 — data-type-in-contract.literalEnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.literalEnd (cognitive 20) REDACTED:980 — data-type-in-contract.literalEnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.literalEnd (cognitive 20) REDACTED:980 — data-type-in-contract.literalEnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.literalEnd (cognitive 20) REDACTED:980 — data-type-in-contract.literalEnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-from-json.movedCalls · ×4
  • contract-from-json.movedCalls::visit (cognitive 20) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:272 — contract-from-json.movedCalls::visit has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 3 (6 pts), boolean chains 3 (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.
  • contract-from-json.movedCalls::visit (cognitive 20) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:272 — contract-from-json.movedCalls::visit has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 3 (6 pts), boolean chains 3 (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.
  • contract-from-json.movedCalls::visit (cognitive 20) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts:138 — contract-from-json.movedCalls::visit has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 3 (6 pts), boolean chains 3 (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.
  • contract-from-json.movedCalls::visit (cognitive 20) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:138 — contract-from-json.movedCalls::visit has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (11 pts), if/else 3 (6 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · data-type-in-contract.listFiles.visit (cognitive 18) · ×4
  • data-type-in-contract.listFiles.visit (cognitive 18) REDACTED:405 — data-type-in-contract.listFiles.visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.listFiles.visit (cognitive 18) REDACTED:405 — data-type-in-contract.listFiles.visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.listFiles.visit (cognitive 18) REDACTED:405 — data-type-in-contract.listFiles.visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.listFiles.visit (cognitive 18) REDACTED:405 — data-type-in-contract.listFiles.visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-in-contract.genericArgumentEnd (cognitive 18) · ×4
  • data-type-in-contract.genericArgumentEnd (cognitive 18) REDACTED:945 — data-type-in-contract.genericArgumentEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.genericArgumentEnd (cognitive 18) REDACTED:945 — data-type-in-contract.genericArgumentEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.genericArgumentEnd (cognitive 18) REDACTED:945 — data-type-in-contract.genericArgumentEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.genericArgumentEnd (cognitive 18) REDACTED:945 — data-type-in-contract.genericArgumentEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-in-contract.bracketEnd (cognitive 17) · ×4
  • data-type-in-contract.bracketEnd (cognitive 17) REDACTED:1000 — data-type-in-contract.bracketEnd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.bracketEnd (cognitive 17) REDACTED:1000 — data-type-in-contract.bracketEnd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.bracketEnd (cognitive 17) REDACTED:1000 — data-type-in-contract.bracketEnd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.bracketEnd (cognitive 17) REDACTED:1000 — data-type-in-contract.bracketEnd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.topLevelMembers (cognitive 17) · ×4
  • expand-type-aliases.topLevelMembers (cognitive 17) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:646 — expand-type-aliases.topLevelMembers has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.topLevelMembers (cognitive 17) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:646 — expand-type-aliases.topLevelMembers has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.topLevelMembers (cognitive 17) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:623 — expand-type-aliases.topLevelMembers has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.topLevelMembers (cognitive 17) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:623 — expand-type-aliases.topLevelMembers has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 4, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-in-contract.scanBlocks (cognitive 16) · ×4
  • data-type-in-contract.scanBlocks (cognitive 16) REDACTED:816 — data-type-in-contract.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.scanBlocks (cognitive 16) REDACTED:816 — data-type-in-contract.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.scanBlocks (cognitive 16) REDACTED:816 — data-type-in-contract.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-in-contract.scanBlocks (cognitive 16) REDACTED:816 — data-type-in-contract.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.scanBlocks (cognitive 16) · ×4
  • remove-nocheck.scanBlocks (cognitive 16) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2011 — remove-nocheck.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.scanBlocks (cognitive 16) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2011 — remove-nocheck.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.scanBlocks (cognitive 16) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:511 — remove-nocheck.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.scanBlocks (cognitive 16) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:511 — remove-nocheck.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IC1 · Incompleteness & stubs · Fake-async · ×4
  • Fake-async — async method never awaits skills-contrib/review-fetch-phase/scripts/guard-review-artifacts-ignored.mjs:137 — `main` 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 skills-contrib/review-implement-phase/scripts/check-github-admin-ready.mjs:129 — `main` 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 skills-contrib/review-implement-phase/scripts/post-review-thread-reply.mjs:271 — `main` 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 skills-contrib/review-implement-phase/scripts/resolve-review-thread.mjs:141 — `main` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 66, cognitive 100) · ×4
  • Complex function main (cyclomatic 66, cognitive 100) REDACTED:1292 — main has cyclomatic complexity 66 and cognitive complexity 100; 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 main (cyclomatic 66, cognitive 100) REDACTED:1292 — main has cyclomatic complexity 66 and cognitive complexity 100; 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 main (cyclomatic 66, cognitive 100) REDACTED:1292 — main has cyclomatic complexity 66 and cognitive complexity 100; 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 main (cyclomatic 66, cognitive 100) REDACTED:1292 — main has cyclomatic complexity 66 and cognitive complexity 100; 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.
D1 · Cyclomatic Complexity · data-type-values.main (cyclomatic 59) · ×3
  • data-type-values.main (cyclomatic 59) REDACTED:943 — data-type-values.main has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.main (cyclomatic 59) REDACTED:943 — data-type-values.main has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.main (cyclomatic 59) REDACTED:940 — data-type-values.main has cyclomatic complexity 59 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · data-type-values.rewriteDatetimeEnums (cyclomatic 36) · ×3
  • data-type-values.rewriteDatetimeEnums (cyclomatic 36) REDACTED:693 — data-type-values.rewriteDatetimeEnums has cyclomatic complexity 36 (threshold 15). Of this number, 19 points are the body's own statements and 17 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.rewriteDatetimeEnums (cyclomatic 36) REDACTED:693 — data-type-values.rewriteDatetimeEnums has cyclomatic complexity 36 (threshold 15). Of this number, 19 points are the body's own statements and 17 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.rewriteDatetimeEnums (cyclomatic 36) REDACTED:693 — data-type-values.rewriteDatetimeEnums has cyclomatic complexity 36 (threshold 15). Of this number, 19 points are the body's own statements and 17 belong to 10 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · data-type-values.rewriteDts (cyclomatic 23) · ×3
  • data-type-values.rewriteDts (cyclomatic 23) REDACTED:846 — data-type-values.rewriteDts has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.rewriteDts (cyclomatic 23) REDACTED:846 — data-type-values.rewriteDts has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.rewriteDts (cyclomatic 23) REDACTED:846 — data-type-values.rewriteDts has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · data-type-values.literalEnd (cyclomatic 20) · ×3
  • data-type-values.literalEnd (cyclomatic 20) REDACTED:557 — data-type-values.literalEnd has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.literalEnd (cyclomatic 20) REDACTED:557 — data-type-values.literalEnd has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.literalEnd (cyclomatic 20) REDACTED:557 — data-type-values.literalEnd has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · data-type-values.genericArgumentEnd (cyclomatic 17) · ×3
  • data-type-values.genericArgumentEnd (cyclomatic 17) REDACTED:522 — data-type-values.genericArgumentEnd has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.genericArgumentEnd (cyclomatic 17) REDACTED:522 — data-type-values.genericArgumentEnd has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • data-type-values.genericArgumentEnd (cyclomatic 17) REDACTED:522 — data-type-values.genericArgumentEnd has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D2 · Cognitive Complexity · data-type-values.main (cognitive 87) · ×3
  • data-type-values.main (cognitive 87) REDACTED:943 — data-type-values.main has cognitive complexity 87 (threshold 15). Drivers by points: if/else 22 (43 pts), ternaries 10 (21 pts), loops 13, boolean chains 9, error handling 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.main (cognitive 87) REDACTED:943 — data-type-values.main has cognitive complexity 87 (threshold 15). Drivers by points: if/else 22 (43 pts), ternaries 10 (21 pts), loops 13, boolean chains 9, error handling 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.main (cognitive 87) REDACTED:940 — data-type-values.main has cognitive complexity 87 (threshold 15). Drivers by points: if/else 22 (43 pts), ternaries 10 (21 pts), loops 13, boolean chains 9, error handling 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-values.rewriteDatetimeEnums (cognitive 67) · ×3
  • data-type-values.rewriteDatetimeEnums (cognitive 67) REDACTED:693 — data-type-values.rewriteDatetimeEnums has cognitive complexity 67 (threshold 15). Drivers by points: ternaries 19 (45 pts), if/else 4 (12 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 37). Of this number, 34 points are the body's own statements and 33 belong to 10 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • data-type-values.rewriteDatetimeEnums (cognitive 67) REDACTED:693 — data-type-values.rewriteDatetimeEnums has cognitive complexity 67 (threshold 15). Drivers by points: ternaries 19 (45 pts), if/else 4 (12 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 37). Of this number, 34 points are the body's own statements and 33 belong to 10 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
  • data-type-values.rewriteDatetimeEnums (cognitive 67) REDACTED:693 — data-type-values.rewriteDatetimeEnums has cognitive complexity 67 (threshold 15). Drivers by points: ternaries 19 (45 pts), if/else 4 (12 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 37). Of this number, 34 points are the body's own statements and 33 belong to 10 function items inside it that branch. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
D2 · Cognitive Complexity · data-type-values.rewriteDts (cognitive 23) · ×3
  • data-type-values.rewriteDts (cognitive 23) REDACTED:846 — data-type-values.rewriteDts has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 6, ternaries 2 (4 pts), boolean chains 3 (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.
  • data-type-values.rewriteDts (cognitive 23) REDACTED:846 — data-type-values.rewriteDts has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 6, ternaries 2 (4 pts), boolean chains 3 (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.
  • data-type-values.rewriteDts (cognitive 23) REDACTED:846 — data-type-values.rewriteDts has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 6, ternaries 2 (4 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · data-type-values.sortTableArrays (cognitive 22) · ×3
  • data-type-values.sortTableArrays (cognitive 22) REDACTED:201 — data-type-values.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.sortTableArrays (cognitive 22) REDACTED:201 — data-type-values.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.sortTableArrays (cognitive 22) REDACTED:201 — data-type-values.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mongo-field-storage-names.rewriteModelType (cognitive 21) · ×3
  • mongo-field-storage-names.rewriteModelType (cognitive 21) REDACTED:185 — mongo-field-storage-names.rewriteModelType has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 3 (7 pts), loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • mongo-field-storage-names.rewriteModelType (cognitive 21) REDACTED:185 — mongo-field-storage-names.rewriteModelType has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 3 (7 pts), loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • mongo-field-storage-names.rewriteModelType (cognitive 21) REDACTED:140 — mongo-field-storage-names.rewriteModelType has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 3 (7 pts), loops 2 (3 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-values.literalEnd (cognitive 20) · ×3
  • data-type-values.literalEnd (cognitive 20) REDACTED:557 — data-type-values.literalEnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.literalEnd (cognitive 20) REDACTED:557 — data-type-values.literalEnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.literalEnd (cognitive 20) REDACTED:557 — data-type-values.literalEnd has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 5, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · add-model-map.main (cognitive 18) · ×3
  • add-model-map.main (cognitive 18) scripts/codemods/add-model-map.mjs:213 — add-model-map.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (7 pts), error handling 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.
  • add-model-map.main (cognitive 18) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs:213 — add-model-map.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (7 pts), error handling 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.
  • add-model-map.main (cognitive 18) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs:213 — add-model-map.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (7 pts), error handling 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.
D2 · Cognitive Complexity · data-type-values.genericArgumentEnd (cognitive 18) · ×3
  • data-type-values.genericArgumentEnd (cognitive 18) REDACTED:522 — data-type-values.genericArgumentEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.genericArgumentEnd (cognitive 18) REDACTED:522 — data-type-values.genericArgumentEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.genericArgumentEnd (cognitive 18) REDACTED:522 — data-type-values.genericArgumentEnd has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-values.bracketEnd (cognitive 17) · ×3
  • data-type-values.bracketEnd (cognitive 17) REDACTED:577 — data-type-values.bracketEnd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.bracketEnd (cognitive 17) REDACTED:577 — data-type-values.bracketEnd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.bracketEnd (cognitive 17) REDACTED:577 — data-type-values.bracketEnd has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-values.scanBlocks (cognitive 16) · ×3
  • data-type-values.scanBlocks (cognitive 16) REDACTED:446 — data-type-values.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.scanBlocks (cognitive 16) REDACTED:446 — data-type-values.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.scanBlocks (cognitive 16) REDACTED:446 — data-type-values.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
IC1 · Incompleteness & stubs · Both branches are identical · ×3
  • Both branches are identical — the condition decides nothing packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:1537 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
  • Both branches are identical — the condition decides nothing packages/3-extensions/sql-orm-client/src/collection.ts:1715 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
  • Both branches are identical — the condition decides nothing skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-closed-mongo-contracts.ts:157 — Both arms of this conditional expression are the same, so no input can make the condition matter. Implement the distinction that was intended, or drop the condition.
R7 · Dead Code · Dead file (~16 LoC) · ×3
  • Dead file (~16 LoC) examples/bundle-size/src/postgres-worker/worker.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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) examples/mongo-demo/migrations/app/20260409T1030_migration/migration.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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) projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/probe.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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
D1 · Cyclomatic Complexity · expand-type-aliases.main (cyclomatic 68) · ×2
  • expand-type-aliases.main (cyclomatic 68) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:994 — expand-type-aliases.main has cyclomatic complexity 68 (threshold 15). Of this number, 66 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.main (cyclomatic 68) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:994 — expand-type-aliases.main has cyclomatic complexity 68 (threshold 15). Of this number, 66 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · expand-type-aliases.main (cyclomatic 67) · ×2
  • expand-type-aliases.main (cyclomatic 67) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:959 — expand-type-aliases.main has cyclomatic complexity 67 (threshold 15). Of this number, 65 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.main (cyclomatic 67) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:959 — expand-type-aliases.main has cyclomatic complexity 67 (threshold 15). Of this number, 65 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · remove-nocheck.main (cyclomatic 63) · ×2
  • remove-nocheck.main (cyclomatic 63) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2278 — remove-nocheck.main has cyclomatic complexity 63 (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.
  • remove-nocheck.main (cyclomatic 63) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2278 — remove-nocheck.main has cyclomatic complexity 63 (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.
D1 · Cyclomatic Complexity · value-objects-in-storage.main (cyclomatic 62) · ×2
  • value-objects-in-storage.main (cyclomatic 62) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:978 — value-objects-in-storage.main has cyclomatic complexity 62 (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.
  • value-objects-in-storage.main (cyclomatic 62) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:978 — value-objects-in-storage.main has cyclomatic complexity 62 (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.
D1 · Cyclomatic Complexity · remove-nocheck.main (cyclomatic 58) · ×2
  • remove-nocheck.main (cyclomatic 58) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:648 — remove-nocheck.main has cyclomatic complexity 58 (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.
  • remove-nocheck.main (cyclomatic 58) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:648 — remove-nocheck.main has cyclomatic complexity 58 (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.
D1 · Cyclomatic Complexity · remove-nocheck.dateTimeStoredText (cyclomatic 30) · ×2
  • remove-nocheck.dateTimeStoredText (cyclomatic 30) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1235 — remove-nocheck.dateTimeStoredText has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • remove-nocheck.dateTimeStoredText (cyclomatic 30) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1235 — remove-nocheck.dateTimeStoredText has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · mongo-index-names.main (cyclomatic 28) · ×2
  • mongo-index-names.main (cyclomatic 28) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.22-to-8.0.0-rc.23/scripts/mongo-index-names/mongo-index-names.ts:220 — mongo-index-names.main has cyclomatic complexity 28 (threshold 15). Of this number, 16 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • mongo-index-names.main (cyclomatic 28) upgrade-instructions/releases/8.0.0-rc.22-to-8.0.0-rc.23/sources/mongo-index-names/app/scripts/mongo-index-names.ts:220 — mongo-index-names.main has cyclomatic complexity 28 (threshold 15). Of this number, 16 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · value-objects-in-storage.writeDiscriminatorValueSets (cyclomatic 25) · ×2
  • value-objects-in-storage.writeDiscriminatorValueSets (cyclomatic 25) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:562 — value-objects-in-storage.writeDiscriminatorValueSets has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • value-objects-in-storage.writeDiscriminatorValueSets (cyclomatic 25) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:562 — value-objects-in-storage.writeDiscriminatorValueSets has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · contract-from-json.moveFile (cyclomatic 23) · ×2
  • contract-from-json.moveFile (cyclomatic 23) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:354 — contract-from-json.moveFile has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • contract-from-json.moveFile (cyclomatic 23) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:354 — contract-from-json.moveFile has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · value-objects-in-storage.rewriteContract (cyclomatic 23) · ×2
  • value-objects-in-storage.rewriteContract (cyclomatic 23) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:618 — value-objects-in-storage.rewriteContract has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • value-objects-in-storage.rewriteContract (cyclomatic 23) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:618 — value-objects-in-storage.rewriteContract has cyclomatic complexity 23 (threshold 15). Of this number, 20 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · remove-nocheck.readEwkb (cyclomatic 22) · ×2
  • remove-nocheck.readEwkb (cyclomatic 22) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1420 — remove-nocheck.readEwkb has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (header, body, positions, …). 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.
  • remove-nocheck.readEwkb (cyclomatic 22) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1420 — remove-nocheck.readEwkb has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 6 of the 22 points are its own statements and the rest belongs to 4 function items inside it that branch (header, body, positions, …). 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.
D1 · Cyclomatic Complexity · strip-inline-contracts.jsonValueEnd (cyclomatic 21) · ×2
  • strip-inline-contracts.jsonValueEnd (cyclomatic 21) skills/prisma-8/upgrading/app/upgrades/0.8-to-0.9/strip-inline-contracts.ts:84 — strip-inline-contracts.jsonValueEnd has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • strip-inline-contracts.jsonValueEnd (cyclomatic 21) skills/prisma-8/upgrading/extension/upgrades/0.8-to-0.9/strip-inline-contracts.ts:84 — strip-inline-contracts.jsonValueEnd has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · remove-nocheck.readIpv6 (cyclomatic 21) · ×2
  • remove-nocheck.readIpv6 (cyclomatic 21) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:729 — remove-nocheck.readIpv6 has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • remove-nocheck.readIpv6 (cyclomatic 21) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:729 — remove-nocheck.readIpv6 has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · contract-from-json.moveFile (cyclomatic 21) · ×2
  • contract-from-json.moveFile (cyclomatic 21) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts:219 — contract-from-json.moveFile has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
  • contract-from-json.moveFile (cyclomatic 21) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:219 — contract-from-json.moveFile has cyclomatic complexity 21 (threshold 15). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, 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.
D1 · Cyclomatic Complexity · migration-op-factories-to-methods.readToken (cyclomatic 20) · ×2
  • migration-op-factories-to-methods.readToken (cyclomatic 20) skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:65 — migration-op-factories-to-methods.readToken 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.
  • migration-op-factories-to-methods.readToken (cyclomatic 20) skills/prisma-8/upgrading/extension/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:65 — migration-op-factories-to-methods.readToken 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.
D1 · Cyclomatic Complexity · remove-nocheck.rewriteDts (cyclomatic 20) · ×2
  • remove-nocheck.rewriteDts (cyclomatic 20) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2140 — remove-nocheck.rewriteDts has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • remove-nocheck.rewriteDts (cyclomatic 20) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2140 — remove-nocheck.rewriteDts has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · strip-inline-contracts.removeTopLevelKey (cyclomatic 19) · ×2
  • strip-inline-contracts.removeTopLevelKey (cyclomatic 19) skills/prisma-8/upgrading/app/upgrades/0.8-to-0.9/strip-inline-contracts.ts:138 — strip-inline-contracts.removeTopLevelKey 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.
  • strip-inline-contracts.removeTopLevelKey (cyclomatic 19) skills/prisma-8/upgrading/extension/upgrades/0.8-to-0.9/strip-inline-contracts.ts:138 — strip-inline-contracts.removeTopLevelKey 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.
D1 · Cyclomatic Complexity · remove-nocheck.readIpv4 (cyclomatic 19) · ×2
  • remove-nocheck.readIpv4 (cyclomatic 19) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:654 — remove-nocheck.readIpv4 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.
  • remove-nocheck.readIpv4 (cyclomatic 19) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:654 — remove-nocheck.readIpv4 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.
D1 · Cyclomatic Complexity · remove-nocheck.rewriteContract (cyclomatic 19) · ×2
  • remove-nocheck.rewriteContract (cyclomatic 19) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1938 — remove-nocheck.rewriteContract 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.
  • remove-nocheck.rewriteContract (cyclomatic 19) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1938 — remove-nocheck.rewriteContract 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.
D1 · Cyclomatic Complexity · mongo-field-storage-names.main (cyclomatic 18) · ×2
  • mongo-field-storage-names.main (cyclomatic 18) REDACTED:232 — mongo-field-storage-names.main has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • mongo-field-storage-names.main (cyclomatic 18) REDACTED:232 — mongo-field-storage-names.main has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · contract-from-json.destructuredContractEdit (cyclomatic 17) · ×2
  • contract-from-json.destructuredContractEdit (cyclomatic 17) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:187 — contract-from-json.destructuredContractEdit has cyclomatic complexity 17 (threshold 15). 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: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: contract-from-json.ownBindingOf (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
  • contract-from-json.destructuredContractEdit (cyclomatic 17) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:187 — contract-from-json.destructuredContractEdit has cyclomatic complexity 17 (threshold 15). 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: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: contract-from-json.ownBindingOf (cyclomatic 18) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · remove-nocheck.parseArgs (cyclomatic 17) · ×2
  • remove-nocheck.parseArgs (cyclomatic 17) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2246 — remove-nocheck.parseArgs has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • remove-nocheck.parseArgs (cyclomatic 17) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2246 — remove-nocheck.parseArgs has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · expand-type-aliases.scanBlocks (cyclomatic 17) · ×2
  • expand-type-aliases.scanBlocks (cyclomatic 17) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:549 — expand-type-aliases.scanBlocks has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.scanBlocks (cyclomatic 17) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:549 — expand-type-aliases.scanBlocks has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · value-objects-in-storage.scanBlocks (cyclomatic 17) · ×2
  • value-objects-in-storage.scanBlocks (cyclomatic 17) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:723 — value-objects-in-storage.scanBlocks has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • value-objects-in-storage.scanBlocks (cyclomatic 17) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:723 — value-objects-in-storage.scanBlocks has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · remove-nocheck.rewriteContract (cyclomatic 17) · ×2
  • remove-nocheck.rewriteContract (cyclomatic 17) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:461 — remove-nocheck.rewriteContract has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • remove-nocheck.rewriteContract (cyclomatic 17) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:461 — remove-nocheck.rewriteContract has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · strip-sha256-hash-prefixes.findMigrationArtifacts · ×2
  • strip-sha256-hash-prefixes.findMigrationArtifacts::walk (cyclomatic 16) REDACTED:171 — strip-sha256-hash-prefixes.findMigrationArtifacts::walk has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
  • strip-sha256-hash-prefixes.findMigrationArtifacts::walk (cyclomatic 16) REDACTED:171 — strip-sha256-hash-prefixes.findMigrationArtifacts::walk has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · expand-type-aliases.rewriteDts (cyclomatic 16) · ×2
  • expand-type-aliases.rewriteDts (cyclomatic 16) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:690 — expand-type-aliases.rewriteDts has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
  • expand-type-aliases.rewriteDts (cyclomatic 16) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:690 — expand-type-aliases.rewriteDts has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D10 · Test Quality · Skipped test · ×2
  • Skipped test: MYSQL_URL is not set test/utils/test/mysql-database.test.ts:31 — Skipped — switched off by test.skip
  • Skipped test: MYSQL_URL is not set test/utils/src/mysql-database.ts:77 — Skipped — switched off by test.skip
D2 · Cognitive Complexity · expand-type-aliases.main (cognitive 102) · ×2
  • expand-type-aliases.main (cognitive 102) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:994 — expand-type-aliases.main has cognitive complexity 102 (threshold 15). Drivers by points: if/else 28 (54 pts), loops 16 (19 pts), ternaries 8 (17 pts), boolean chains 11, error handling 1 (nesting depth added 38). Of this number, 100 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.main (cognitive 102) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:994 — expand-type-aliases.main has cognitive complexity 102 (threshold 15). Drivers by points: if/else 28 (54 pts), loops 16 (19 pts), ternaries 8 (17 pts), boolean chains 11, error handling 1 (nesting depth added 38). Of this number, 100 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.main (cognitive 101) · ×2
  • expand-type-aliases.main (cognitive 101) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:959 — expand-type-aliases.main has cognitive complexity 101 (threshold 15). Drivers by points: if/else 27 (53 pts), loops 16 (19 pts), ternaries 8 (17 pts), boolean chains 11, error handling 1 (nesting depth added 38). Of this number, 99 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.main (cognitive 101) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:959 — expand-type-aliases.main has cognitive complexity 101 (threshold 15). Drivers by points: if/else 27 (53 pts), loops 16 (19 pts), ternaries 8 (17 pts), boolean chains 11, error handling 1 (nesting depth added 38). Of this number, 99 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-objects-in-storage.main (cognitive 97) · ×2
  • value-objects-in-storage.main (cognitive 97) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:978 — value-objects-in-storage.main has cognitive complexity 97 (threshold 15). Drivers by points: if/else 27 (55 pts), loops 15 (17 pts), ternaries 6 (13 pts), boolean chains 11, error handling 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • value-objects-in-storage.main (cognitive 97) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:978 — value-objects-in-storage.main has cognitive complexity 97 (threshold 15). Drivers by points: if/else 27 (55 pts), loops 15 (17 pts), ternaries 6 (13 pts), boolean chains 11, error handling 1 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.main (cognitive 91) · ×2
  • remove-nocheck.main (cognitive 91) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2278 — remove-nocheck.main has cognitive complexity 91 (threshold 15). Drivers by points: if/else 23 (45 pts), ternaries 8 (17 pts), loops 15 (16 pts), boolean chains 12, error handling 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.main (cognitive 91) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2278 — remove-nocheck.main has cognitive complexity 91 (threshold 15). Drivers by points: if/else 23 (45 pts), ternaries 8 (17 pts), loops 15 (16 pts), boolean chains 12, error handling 1 (nesting depth added 32). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.main (cognitive 84) · ×2
  • remove-nocheck.main (cognitive 84) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:648 — remove-nocheck.main has cognitive complexity 84 (threshold 15). Drivers by points: if/else 21 (42 pts), ternaries 8 (17 pts), loops 13, boolean chains 11, error handling 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.main (cognitive 84) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:648 — remove-nocheck.main has cognitive complexity 84 (threshold 15). Drivers by points: if/else 21 (42 pts), ternaries 8 (17 pts), loops 13, boolean chains 11, error handling 1 (nesting depth added 30). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-objects-in-storage.writeDiscriminatorValueSets (cognitive 46) · ×2
  • value-objects-in-storage.writeDiscriminatorValueSets (cognitive 46) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:562 — value-objects-in-storage.writeDiscriminatorValueSets has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 10 (30 pts), if/else 3 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • value-objects-in-storage.writeDiscriminatorValueSets (cognitive 46) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:562 — value-objects-in-storage.writeDiscriminatorValueSets has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 10 (30 pts), if/else 3 (9 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 27). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.readIpv6 (cognitive 40) · ×2
  • remove-nocheck.readIpv6 (cognitive 40) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:729 — remove-nocheck.readIpv6 has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (36 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.readIpv6 (cognitive 40) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:729 — remove-nocheck.readIpv6 has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (36 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · strip-inline-contracts.jsonValueEnd (cognitive 37) · ×2
  • strip-inline-contracts.jsonValueEnd (cognitive 37) skills/prisma-8/upgrading/app/upgrades/0.8-to-0.9/strip-inline-contracts.ts:84 — strip-inline-contracts.jsonValueEnd has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (28 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • strip-inline-contracts.jsonValueEnd (cognitive 37) skills/prisma-8/upgrading/extension/upgrades/0.8-to-0.9/strip-inline-contracts.ts:84 — strip-inline-contracts.jsonValueEnd has cognitive complexity 37 (threshold 15). Drivers by points: if/else 14 (28 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mongo-index-names.main (cognitive 37) · ×2
  • mongo-index-names.main (cognitive 37) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.22-to-8.0.0-rc.23/scripts/mongo-index-names/mongo-index-names.ts:220 — mongo-index-names.main has cognitive complexity 37 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 7 (9 pts), ternaries 5 (8 pts), boolean chains 6, error handling 2 (4 pts) (nesting depth added 12). Of this number, 22 points are the body's own statements and 15 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • mongo-index-names.main (cognitive 37) upgrade-instructions/releases/8.0.0-rc.22-to-8.0.0-rc.23/sources/mongo-index-names/app/scripts/mongo-index-names.ts:220 — mongo-index-names.main has cognitive complexity 37 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 7 (9 pts), ternaries 5 (8 pts), boolean chains 6, error handling 2 (4 pts) (nesting depth added 12). Of this number, 22 points are the body's own statements and 15 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.rewriteContract (cognitive 36) · ×2
  • remove-nocheck.rewriteContract (cognitive 36) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1938 — remove-nocheck.rewriteContract has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 8 (18 pts), if/else 3 (9 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.rewriteContract (cognitive 36) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1938 — remove-nocheck.rewriteContract has cognitive complexity 36 (threshold 15). Drivers by points: ternaries 8 (18 pts), if/else 3 (9 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-objects-in-storage.rewriteContract (cognitive 34) · ×2
  • value-objects-in-storage.rewriteContract (cognitive 34) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:618 — value-objects-in-storage.rewriteContract has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 7 (14 pts), ternaries 4 (5 pts), boolean chains 1 (nesting depth added 13). Of this number, 31 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.
  • value-objects-in-storage.rewriteContract (cognitive 34) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:618 — value-objects-in-storage.rewriteContract has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (14 pts), loops 7 (14 pts), ternaries 4 (5 pts), boolean chains 1 (nesting depth added 13). Of this number, 31 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.
D2 · Cognitive Complexity · remove-nocheck.rewriteContract (cognitive 34) · ×2
  • remove-nocheck.rewriteContract (cognitive 34) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:461 — remove-nocheck.rewriteContract has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 7 (17 pts), if/else 3 (9 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.rewriteContract (cognitive 34) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:461 — remove-nocheck.rewriteContract has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 7 (17 pts), if/else 3 (9 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · strip-inline-contracts.removeTopLevelKey (cognitive 31) · ×2
  • strip-inline-contracts.removeTopLevelKey (cognitive 31) skills/prisma-8/upgrading/app/upgrades/0.8-to-0.9/strip-inline-contracts.ts:138 — strip-inline-contracts.removeTopLevelKey has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 5 (9 pts), boolean chains 5 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • strip-inline-contracts.removeTopLevelKey (cognitive 31) skills/prisma-8/upgrading/extension/upgrades/0.8-to-0.9/strip-inline-contracts.ts:138 — strip-inline-contracts.removeTopLevelKey has cognitive complexity 31 (threshold 15). Drivers by points: if/else 9 (17 pts), loops 5 (9 pts), boolean chains 5 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · strip-migration-labels-hints.scanValueEnd (cognitive 28) · ×2
  • strip-migration-labels-hints.scanValueEnd (cognitive 28) REDACTED:129 — strip-migration-labels-hints.scanValueEnd has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (5 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • strip-migration-labels-hints.scanValueEnd (cognitive 28) REDACTED:129 — strip-migration-labels-hints.scanValueEnd has cognitive complexity 28 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 3 (5 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.dateTimeStoredText (cognitive 28) · ×2
  • remove-nocheck.dateTimeStoredText (cognitive 28) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1235 — remove-nocheck.dateTimeStoredText has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 12, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
  • remove-nocheck.dateTimeStoredText (cognitive 28) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1235 — remove-nocheck.dateTimeStoredText has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 12, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · remove-nocheck.readEwkb (cognitive 28) · ×2
  • remove-nocheck.readEwkb (cognitive 28) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1420 — remove-nocheck.readEwkb has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 3 (5 pts), boolean chains 4, ternaries 3 (nesting depth added 5). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 4 function items inside it that branch (header, body, positions, …). 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.
  • remove-nocheck.readEwkb (cognitive 28) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1420 — remove-nocheck.readEwkb has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (16 pts), loops 3 (5 pts), boolean chains 4, ternaries 3 (nesting depth added 5). Most of this is not in the body itself: 9 of the 28 points are its own statements and the rest belongs to 4 function items inside it that branch (header, body, positions, …). 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.
D2 · Cognitive Complexity · remove-nocheck.rewriteDts (cognitive 28) · ×2
  • remove-nocheck.rewriteDts (cognitive 28) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2140 — remove-nocheck.rewriteDts has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 4 (8 pts), boolean chains 6, loops 4 (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.
  • remove-nocheck.rewriteDts (cognitive 28) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2140 — remove-nocheck.rewriteDts has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 4 (8 pts), boolean chains 6, loops 4 (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.
D2 · Cognitive Complexity · mongo-field-storage-names.main (cognitive 27) · ×2
  • mongo-field-storage-names.main (cognitive 27) REDACTED:232 — mongo-field-storage-names.main has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 pts), ternaries 3 (5 pts), error handling 2 (4 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.
  • mongo-field-storage-names.main (cognitive 27) REDACTED:232 — mongo-field-storage-names.main has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 4 (5 pts), ternaries 3 (5 pts), error handling 2 (4 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.
D2 · Cognitive Complexity · remove-nocheck.readIpv4 (cognitive 26) · ×2
  • remove-nocheck.readIpv4 (cognitive 26) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:654 — remove-nocheck.readIpv4 has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 3 (5 pts), boolean chains 4 (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.
  • remove-nocheck.readIpv4 (cognitive 26) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:654 — remove-nocheck.readIpv4 has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 3 (5 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · contract-from-json.moveFile (cognitive 23) · ×2
  • contract-from-json.moveFile (cognitive 23) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:354 — contract-from-json.moveFile has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 7, boolean chains 3, loops 2 (nesting depth added 2). Of this number, 22 points are the body's own statements and 1 belongs 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.
  • contract-from-json.moveFile (cognitive 23) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:354 — contract-from-json.moveFile has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 7, boolean chains 3, loops 2 (nesting depth added 2). Of this number, 22 points are the body's own statements and 1 belongs 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.
D2 · Cognitive Complexity · remove-nocheck.parseArgs (cognitive 23) · ×2
  • remove-nocheck.parseArgs (cognitive 23) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2246 — remove-nocheck.parseArgs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (9 pts), boolean chains 4, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.parseArgs (cognitive 23) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2246 — remove-nocheck.parseArgs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (9 pts), boolean chains 4, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.rewriteDts (cognitive 23) · ×2
  • expand-type-aliases.rewriteDts (cognitive 23) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:690 — expand-type-aliases.rewriteDts has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (6 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.rewriteDts (cognitive 23) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:690 — expand-type-aliases.rewriteDts has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (6 pts), ternaries 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.readIpv4Tail (cognitive 22) · ×2
  • remove-nocheck.readIpv4Tail (cognitive 22) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:702 — remove-nocheck.readIpv4Tail has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.readIpv4Tail (cognitive 22) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:702 — remove-nocheck.readIpv4Tail has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.scanBlocks (cognitive 22) · ×2
  • expand-type-aliases.scanBlocks (cognitive 22) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:549 — expand-type-aliases.scanBlocks has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.scanBlocks (cognitive 22) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:549 — expand-type-aliases.scanBlocks has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-objects-in-storage.sortTableArrays (cognitive 22) · ×2
  • value-objects-in-storage.sortTableArrays (cognitive 22) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:199 — value-objects-in-storage.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • value-objects-in-storage.sortTableArrays (cognitive 22) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:199 — value-objects-in-storage.sortTableArrays has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-objects-in-storage.scanBlocks (cognitive 22) · ×2
  • value-objects-in-storage.scanBlocks (cognitive 22) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:723 — value-objects-in-storage.scanBlocks has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • value-objects-in-storage.scanBlocks (cognitive 22) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:723 — value-objects-in-storage.scanBlocks has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-op-factories-to-methods.readToken (cognitive 20) · ×2
  • migration-op-factories-to-methods.readToken (cognitive 20) skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:65 — migration-op-factories-to-methods.readToken has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 7, loops 3 (4 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • migration-op-factories-to-methods.readToken (cognitive 20) skills/prisma-8/upgrading/extension/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:65 — migration-op-factories-to-methods.readToken has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 7, loops 3 (4 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.rewriteDts (cognitive 20) · ×2
  • expand-type-aliases.rewriteDts (cognitive 20) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:713 — expand-type-aliases.rewriteDts has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (6 pts), boolean chains 2, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.rewriteDts (cognitive 20) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:713 — expand-type-aliases.rewriteDts has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 4 (6 pts), boolean chains 2, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-objects-in-storage.listFiles.visit (cognitive 20) · ×2
  • value-objects-in-storage.listFiles.visit (cognitive 20) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:334 — value-objects-in-storage.listFiles.visit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, loops 1 (nesting depth added 6). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • value-objects-in-storage.listFiles.visit (cognitive 20) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:334 — value-objects-in-storage.listFiles.visit has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, loops 1 (nesting depth added 6). Of this number, 19 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-from-json.moveFile (cognitive 20) · ×2
  • contract-from-json.moveFile (cognitive 20) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts:219 — contract-from-json.moveFile has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 6, boolean chains 3, loops 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
  • contract-from-json.moveFile (cognitive 20) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:219 — contract-from-json.moveFile has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 8 (9 pts), if/else 6, boolean chains 3, loops 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · data-type-values.listFiles.visit (cognitive 19) · ×2
  • data-type-values.listFiles.visit (cognitive 19) REDACTED:334 — data-type-values.listFiles.visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6, loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • data-type-values.listFiles.visit (cognitive 19) REDACTED:334 — data-type-values.listFiles.visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6, loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.listFiles.visit (cognitive 19) · ×2
  • remove-nocheck.listFiles.visit (cognitive 19) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:310 — remove-nocheck.listFiles.visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6, loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.listFiles.visit (cognitive 19) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:310 — remove-nocheck.listFiles.visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6, loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.listFiles.visit (cognitive 19) · ×2
  • expand-type-aliases.listFiles.visit (cognitive 19) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:316 — expand-type-aliases.listFiles.visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6, loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.listFiles.visit (cognitive 19) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:316 — expand-type-aliases.listFiles.visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 6, loops 1 (nesting depth added 6). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-op-factories-to-methods.applyRewrites (cognitive 18) · ×2
  • migration-op-factories-to-methods.applyRewrites (cognitive 18) skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:205 — migration-op-factories-to-methods.applyRewrites has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (6 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.
  • migration-op-factories-to-methods.applyRewrites (cognitive 18) skills/prisma-8/upgrading/extension/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:205 — migration-op-factories-to-methods.applyRewrites has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (6 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.
D2 · Cognitive Complexity · remove-nocheck.rewriteDefaults (cognitive 18) · ×2
  • remove-nocheck.rewriteDefaults (cognitive 18) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1857 — remove-nocheck.rewriteDefaults has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.rewriteDefaults (cognitive 18) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1857 — remove-nocheck.rewriteDefaults has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-objects-in-storage.rewriteDts (cognitive 18) · ×2
  • value-objects-in-storage.rewriteDts (cognitive 18) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:824 — value-objects-in-storage.rewriteDts has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • value-objects-in-storage.rewriteDts (cognitive 18) upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:824 — value-objects-in-storage.rewriteDts has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 4, loops 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.listFiles.visit (cognitive 18) · ×2
  • remove-nocheck.listFiles.visit (cognitive 18) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:308 — remove-nocheck.listFiles.visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.listFiles.visit (cognitive 18) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:308 — remove-nocheck.listFiles.visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.listFiles.visit (cognitive 18) · ×2
  • expand-type-aliases.listFiles.visit (cognitive 18) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:311 — expand-type-aliases.listFiles.visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.listFiles.visit (cognitive 18) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:311 — expand-type-aliases.listFiles.visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · strip-sha256-hash-prefixes.processPackage (cognitive 17) · ×2
  • strip-sha256-hash-prefixes.processPackage (cognitive 17) REDACTED:244 — strip-sha256-hash-prefixes.processPackage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 3, boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • strip-sha256-hash-prefixes.processPackage (cognitive 17) REDACTED:244 — strip-sha256-hash-prefixes.processPackage has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 3, boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-from-json.sourceFiles · ×2
  • contract-from-json.sourceFiles::visit (cognitive 17) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:496 — contract-from-json.sourceFiles::visit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 6, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • contract-from-json.sourceFiles::visit (cognitive 17) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:496 — contract-from-json.sourceFiles::visit has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 6, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.printIpv6 (cognitive 17) · ×2
  • remove-nocheck.printIpv6 (cognitive 17) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:807 — remove-nocheck.printIpv6 has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 1, 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.
  • remove-nocheck.printIpv6 (cognitive 17) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:807 — remove-nocheck.printIpv6 has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 1, 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.
D2 · Cognitive Complexity · add-model-map.main (cognitive 17) · ×2
  • add-model-map.main (cognitive 17) upgrade-instructions/releases/8.0.0-rc.11-to-8.0.0-rc.12/sources/psl-verbatim-table-names/app/scripts/add-model-map.mjs:213 — add-model-map.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (7 pts), error handling 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.
  • add-model-map.main (cognitive 17) upgrade-instructions/releases/8.0.0-rc.11-to-8.0.0-rc.12/sources/psl-verbatim-table-names/extension/scripts/add-model-map.mjs:213 — add-model-map.main has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (7 pts), error handling 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.
D2 · Cognitive Complexity · contract-from-json.main (cognitive 17) · ×2
  • contract-from-json.main (cognitive 17) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts:334 — contract-from-json.main has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 3 (4 pts), boolean chains 2, loops 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • contract-from-json.main (cognitive 17) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:334 — contract-from-json.main has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (10 pts), if/else 3 (4 pts), boolean chains 2, loops 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · rename-execution-ref-keys.main (cognitive 16) · ×2
  • rename-execution-ref-keys.main (cognitive 16) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:167 — rename-execution-ref-keys.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (5 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • rename-execution-ref-keys.main (cognitive 16) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:167 — rename-execution-ref-keys.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 3 (5 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · remove-nocheck.readWritten (cognitive 16) · ×2
  • remove-nocheck.readWritten (cognitive 16) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1132 — remove-nocheck.readWritten has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • remove-nocheck.readWritten (cognitive 16) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1132 — remove-nocheck.readWritten has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · expand-type-aliases.scanBlocks (cognitive 16) · ×2
  • expand-type-aliases.scanBlocks (cognitive 16) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:536 — expand-type-aliases.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
  • expand-type-aliases.scanBlocks (cognitive 16) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:536 — expand-type-aliases.scanBlocks has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×2
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · Medium IaC · ×2
  • REDACTED
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED
  • REDACTED
  • REDACTED
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 70, cognitive 105) · ×2
  • Complex function main (cyclomatic 70, cognitive 105) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:994 — main has cyclomatic complexity 70 and cognitive complexity 105; 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 main (cyclomatic 70, cognitive 105) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:994 — main has cyclomatic complexity 70 and cognitive complexity 105; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 69, cognitive 104) · ×2
  • Complex function main (cyclomatic 69, cognitive 104) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:959 — main has cyclomatic complexity 69 and cognitive complexity 104; 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 main (cyclomatic 69, cognitive 104) upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:959 — main has cyclomatic complexity 69 and cognitive complexity 104; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 66, cognitive 95) · ×2
  • Complex function main (cyclomatic 66, cognitive 95) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2278 — main has cyclomatic complexity 66 and cognitive complexity 95; 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 main (cyclomatic 66, cognitive 95) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:2278 — main has cyclomatic complexity 66 and cognitive complexity 95; 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.
R7 · Dead Code · Dead file (~382 LoC) · ×2
  • Dead file (~382 LoC) REDACTED — no import path from any entry point (1352 application, 823 tooling, 4409 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 (~382 LoC) REDACTED — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~378 LoC) · ×2
  • Dead file (~378 LoC) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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 (~378 LoC) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~360 LoC) · ×2
  • Dead file (~360 LoC) skills/prisma-8/upgrading/app/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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 (~360 LoC) skills/prisma-8/upgrading/extension/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~340 LoC) · ×2
  • Dead file (~340 LoC) REDACTED — no import path from any entry point (1352 application, 823 tooling, 4409 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 (~340 LoC) REDACTED — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~290 LoC) · ×2
  • Dead file (~290 LoC) skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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 (~290 LoC) skills/prisma-8/upgrading/extension/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~226 LoC) · ×2
  • Dead file (~226 LoC) skills/prisma-8/upgrading/app/upgrades/0.8-to-0.9/strip-inline-contracts.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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 (~226 LoC) skills/prisma-8/upgrading/extension/upgrades/0.8-to-0.9/strip-inline-contracts.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~193 LoC) · ×2
  • Dead file (~193 LoC) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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 (~193 LoC) skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~43 LoC) · ×2
  • Dead file (~43 LoC) skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/uuid-preset-rename.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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 (~43 LoC) skills/prisma-8/upgrading/extension/upgrades/0.13-to-0.14/uuid-preset-rename.ts — no import path from any entry point (1352 application, 823 tooling, 4409 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
SC1 · Supply-chain hygiene · JavaScript dependencies are not locked · ×2
  • JavaScript dependencies are not locked examples/bundle-size/src/mongo/package.json:7 — examples/bundle-size/src/mongo/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
  • JavaScript dependencies are not locked examples/bundle-size/src/postgres/package.json:7 — examples/bundle-size/src/postgres/package.json declares dependencies that no committed lockfile resolves — there is no package-lock.json / yarn.lock / REDACTED / bun.lock beside it, and no locked workspace above it names it — so its installs aren't reproducible (SSDF PW.4.4). Commit its package manager's lockfile (or add it to the locked workspace) and install from it (`npm ci`, `yarn --immutable`, `pnpm i --frozen-lockfile` or `bun i --frozen-lockfile`). Advisory — never scored.
C1 · Data Protection · No data-protection/encryption · ×1
  • No data-protection/encryption packages/3-extensions/supabase/src/contract/contract.prisma:34 — No encryption usage (node:crypto createCipheriv, Web Crypto subtle.encrypt, crypto-js AES, tweetnacl/libsodium secretbox, a column-encryption layer such as typeorm-encrypted, prisma-field-encryption or mongoose-field-encryption, or MongoDB client-side field-level encryption) was found, and this repository persists personal data in the model cited here — sensitive data at rest may be unprotected. If TDE/KMS/vault is delegated to infrastructure, ignore.
D1 · Cyclomatic Complexity · interpreter.buildModelNodeFromPsl (cyclomatic 93) · ×1
  • interpreter.buildModelNodeFromPsl (cyclomatic 93) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:615 — interpreter.buildModelNodeFromPsl has cyclomatic complexity 93 (threshold 15). Of this number, 90 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.
D1 · Cyclomatic Complexity · interpreter.readField (cyclomatic 88) · ×1
  • interpreter.readField (cyclomatic 88) packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:1183 — interpreter.readField has cyclomatic complexity 88 (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.
D1 · Cyclomatic Complexity · interpreter.interpretPslDocumentToSqlContract (cyclomatic 84) · ×1
  • interpreter.interpretPslDocumentToSqlContract (cyclomatic 84) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:2170 — interpreter.interpretPslDocumentToSqlContract has cyclomatic complexity 84 (threshold 15). Of this number, 65 points are the body's own statements and 19 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migration-plan.executeMigrationPlanCommandInner (cyclomatic 73) · ×1
  • migration-plan.executeMigrationPlanCommandInner (cyclomatic 73) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts:510 — migration-plan.executeMigrationPlanCommandInner has cyclomatic complexity 73 (threshold 15). Of this number, 71 points are the body's own statements and 2 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · lowering.lowerStage (cyclomatic 71) · ×1
  • lowering.lowerStage (cyclomatic 71) packages/3-targets/mongo/2-adapter/src/lowering.ts:252 — lowering.lowerStage has cyclomatic complexity 71 (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.
D1 · Cyclomatic Complexity · lowering.structuralLowerStage (cyclomatic 70) · ×1
  • lowering.structuralLowerStage (cyclomatic 70) packages/3-targets/mongo/2-adapter/src/lowering.ts:489 — lowering.structuralLowerStage has cyclomatic complexity 70 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migration-graph-grid-layout.buildGrid (cyclomatic 65) · ×1
  • migration-graph-grid-layout.buildGrid (cyclomatic 65) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts:301 — migration-graph-grid-layout.buildGrid has cyclomatic complexity 65 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (migration-graph-grid-layout.buildGrid::emitConnectorRow) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · relations.lowerRelations (cyclomatic 65) · ×1
  • relations.lowerRelations (cyclomatic 65) packages/2-sql-family/2-authoring/contract-prisma7/src/relations.ts:388 — relations.lowerRelations has cyclomatic complexity 65 (threshold 15). Of this number, 58 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · refusal-diagnostics.refusalDiagnostic (cyclomatic 59) · ×1
  • refusal-diagnostics.refusalDiagnostic (cyclomatic 59) packages/2-mongo-family/2-authoring/contract-psl/src/refusal-diagnostics.ts:213 — refusal-diagnostics.refusalDiagnostic has cyclomatic complexity 59 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · review-artifacts.assertReviewActionsV1 (cyclomatic 57) · ×1
  • review-artifacts.assertReviewActionsV1 (cyclomatic 57) skills-contrib/review-triage-phase/scripts/review-artifacts.mjs:23 — review-artifacts.assertReviewActionsV1 has cyclomatic complexity 57 (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.
D1 · Cyclomatic Complexity · framework-authoring.isWellFormedDescriptor (cyclomatic 55) · ×1
  • framework-authoring.isWellFormedDescriptor (cyclomatic 55) packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:699 — framework-authoring.isWellFormedDescriptor has cyclomatic complexity 55 (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.
D1 · Cyclomatic Complexity · binder.tryBindExpression (cyclomatic 54) · ×1
  • binder.tryBindExpression (cyclomatic 54) packages/1-framework/2-authoring/psl-parser/src/binder.ts:714 — binder.tryBindExpression has cyclomatic complexity 54 (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.
D1 · Cyclomatic Complexity · migration-graph-grid-layout.buildLaneAssignment (cyclomatic 50) · ×1
  • migration-graph-grid-layout.buildLaneAssignment (cyclomatic 50) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts:44 — migration-graph-grid-layout.buildLaneAssignment has cyclomatic complexity 50 (threshold 15). Of this number, 47 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.
D1 · Cyclomatic Complexity · interpreter.interpretPrisma7Documents (cyclomatic 49) · ×1
  • interpreter.interpretPrisma7Documents (cyclomatic 49) packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:298 — interpreter.interpretPrisma7Documents has cyclomatic complexity 49 (threshold 15). Of this number, 40 points are the body's own statements and 9 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · refusal-errors.refusalError (cyclomatic 48) · ×1
  • refusal-errors.refusalError (cyclomatic 48) packages/2-mongo-family/2-authoring/contract-ts/src/refusal-errors.ts:170 — refusal-errors.refusalError has cyclomatic complexity 48 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · shell-build.defineShellConfig (cyclomatic 44) · ×1
  • shell-build.defineShellConfig (cyclomatic 44) packages/0-config/tsdown/shell-build.ts:45 — shell-build.defineShellConfig has cyclomatic complexity 44 (threshold 15). Of this number, 40 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · interpreter.readModelField (cyclomatic 42) · ×1
  • interpreter.readModelField (cyclomatic 42) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:1024 — interpreter.readModelField has cyclomatic complexity 42 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · psl-column-resolution.lowerTypeDefault (cyclomatic 42) · ×1
  • psl-column-resolution.lowerTypeDefault (cyclomatic 42) packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts:672 — psl-column-resolution.lowerTypeDefault has cyclomatic complexity 42 (threshold 15). Of this number, 25 points are the body's own statements and 17 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · db-run.executeRun (cyclomatic 41) · ×1
  • db-run.executeRun (cyclomatic 41) packages/1-framework/3-tooling/cli/src/control-api/operations/db-run.ts:195 — db-run.executeRun has cyclomatic complexity 41 (threshold 15). Of this number, 34 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · interpreter.interpretPslDocumentToMongoContract (cyclomatic 39) · ×1
  • interpreter.interpretPslDocumentToMongoContract (cyclomatic 39) packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:1111 — interpreter.interpretPslDocumentToMongoContract has cyclomatic complexity 39 (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.
D1 · Cyclomatic Complexity · psl-field-resolution.collectResolvedFields (cyclomatic 38) · ×1
  • psl-field-resolution.collectResolvedFields (cyclomatic 38) packages/2-sql-family/2-authoring/contract-psl/src/psl-field-resolution.ts:236 — psl-field-resolution.collectResolvedFields has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · lint-no-contract-cast.blankCommentsAndStrings (cyclomatic 38) · ×1
  • lint-no-contract-cast.blankCommentsAndStrings (cyclomatic 38) scripts/lint-no-contract-cast.mjs:68 — lint-no-contract-cast.blankCommentsAndStrings has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · init-scaffold.planScaffold (cyclomatic 37) · ×1
  • init-scaffold.planScaffold (cyclomatic 37) packages/1-framework/3-tooling/cli/src/orm/init-scaffold.ts:205 — init-scaffold.planScaffold has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · tables.buildRecreatePostchecks (cyclomatic 37) · ×1
  • tables.buildRecreatePostchecks (cyclomatic 37) packages/3-targets/sqlite/1-target/src/core/migrations/operations/tables.ts:580 — tables.buildRecreatePostchecks has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migrate-show.executeMigrateShowPlan (cyclomatic 36) · ×1
  • migrate-show.executeMigrateShowPlan (cyclomatic 36) packages/1-framework/3-tooling/cli/src/control-api/operations/migrate-show.ts:91 — migrate-show.executeMigrateShowPlan has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · interpreter.interpretPrisma6Documents (cyclomatic 36) · ×1
  • interpreter.interpretPrisma6Documents (cyclomatic 36) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:201 — interpreter.interpretPrisma6Documents has cyclomatic complexity 36 (threshold 15). Of this number, 33 points are the body's own statements and 3 belong to 2 function items inside it that branch. 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.
D1 · Cyclomatic Complexity · binder.bind (cyclomatic 35) · ×1
  • binder.bind (cyclomatic 35) packages/1-framework/2-authoring/psl-parser/src/binder.ts:358 — binder.bind has cyclomatic complexity 35 (threshold 15). Of this number, 18 points are the body's own statements and 17 belong to 5 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · review-artifacts.normalizeReviewStateV2 (cyclomatic 35) · ×1
  • review-artifacts.normalizeReviewStateV2 (cyclomatic 35) skills-contrib/review-fetch-phase/scripts/review-artifacts.mjs:194 — review-artifacts.normalizeReviewStateV2 has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · resolve-statements.readSide (cyclomatic 34) · ×1
  • resolve-statements.readSide (cyclomatic 34) packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:681 — resolve-statements.readSide has cyclomatic complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migrate.createMigrateCommand (cyclomatic 34) · ×1
  • migrate.createMigrateCommand (cyclomatic 34) packages/1-framework/3-tooling/cli/src/orm/migrate.ts:245 — migrate.createMigrateCommand has cyclomatic complexity 34 (threshold 15). Most of this is not in the body itself: 1 of the 34 points is its own statement and the rest belongs to one function literal inside it that branches (line 282). 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.
D1 · Cyclomatic Complexity · completion-values.valueItems (cyclomatic 34) · ×1
  • completion-values.valueItems (cyclomatic 34) packages/1-framework/3-tooling/language-server/src/completion-values.ts:109 — completion-values.valueItems has cyclomatic complexity 34 (threshold 15). Of this number, 33 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migration-graph-occlusion-render.glyphFor (cyclomatic 33) · ×1
  • migration-graph-occlusion-render.glyphFor (cyclomatic 33) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-occlusion-render.ts:81 — migration-graph-occlusion-render.glyphFor has cyclomatic complexity 33 (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.
D1 · Cyclomatic Complexity · completion-scope.scopeCompletionItems (cyclomatic 33) · ×1
  • completion-scope.scopeCompletionItems (cyclomatic 33) packages/1-framework/3-tooling/language-server/src/completion-scope.ts:37 — completion-scope.scopeCompletionItems has cyclomatic complexity 33 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · validators.validateStorageSemantics (cyclomatic 33) · ×1
  • validators.validateStorageSemantics (cyclomatic 33) packages/2-sql-family/1-core/contract/src/validators.ts:713 — validators.validateStorageSemantics has cyclomatic complexity 33 (threshold 15). Of this number, 32 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.
D1 · Cyclomatic Complexity · query-plan-select.buildIncludeChildScalarSelect (cyclomatic 33) · ×1
  • query-plan-select.buildIncludeChildScalarSelect (cyclomatic 33) packages/3-extensions/sql-orm-client/src/query-plan-select.ts:907 — query-plan-select.buildIncludeChildScalarSelect has cyclomatic complexity 33 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · PostgresMigrationPlanner.planPostgresSchemaDiff (cyclomatic 33) · ×1
  • PostgresMigrationPlanner.planPostgresSchemaDiff (cyclomatic 33) packages/3-targets/postgres/1-target/src/core/migrations/planner.ts:646 — PostgresMigrationPlanner.planPostgresSchemaDiff has cyclomatic complexity 33 (threshold 15). Of this number, 24 points are the body's own statements and 9 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · plan-questions.askPlanQuestions (cyclomatic 32) · ×1
  • plan-questions.askPlanQuestions (cyclomatic 32) packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts:944 — plan-questions.askPlanQuestions has cyclomatic complexity 32 (threshold 15). Of this number, 18 points are the body's own statements and 14 belong to 7 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · enum-value-planning.planEnumValueRewrites (cyclomatic 32) · ×1
  • enum-value-planning.planEnumValueRewrites (cyclomatic 32) packages/2-sql-family/9-family/src/core/migrations/enum-value-planning.ts:405 — enum-value-planning.planEnumValueRewrites has cyclomatic complexity 32 (threshold 15). Of this number, 28 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.
D1 · Cyclomatic Complexity · check-conformance.runCheck (cyclomatic 31) · ×1
  • check-conformance.runCheck (cyclomatic 31) scripts/check-conformance.mjs:656 — check-conformance.runCheck has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · shell-build.validateShellManifest (cyclomatic 30) · ×1
  • shell-build.validateShellManifest (cyclomatic 30) packages/0-config/tsdown/shell-build.ts:416 — shell-build.validateShellManifest has cyclomatic complexity 30 (threshold 15). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, 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.
D1 · Cyclomatic Complexity · canonicalization.omitDefaults (cyclomatic 30) · ×1
  • canonicalization.omitDefaults (cyclomatic 30) packages/1-framework/0-foundation/contract/src/canonicalization.ts:94 — canonicalization.omitDefaults has cyclomatic complexity 30 (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.
D1 · Cyclomatic Complexity · date-time-stored-form.dateTimeStoredText (cyclomatic 30) · ×1
  • date-time-stored-form.dateTimeStoredText (cyclomatic 30) packages/1-framework/1-core/framework-components/src/shared/date-time-stored-form.ts:302 — date-time-stored-form.dateTimeStoredText has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · emit.walkRegion (cyclomatic 30) · ×1
  • emit.walkRegion (cyclomatic 30) packages/1-framework/2-authoring/psl-parser/src/format/emit.ts:457 — emit.walkRegion has cyclomatic complexity 30 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · init.createInitCommand (cyclomatic 30) · ×1
  • init.createInitCommand (cyclomatic 30) packages/1-framework/3-tooling/cli/src/orm/init.ts:82 — init.createInitCommand has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 1 of the 30 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 148, 267). 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.
D1 · Cyclomatic Complexity · value-object-default.valueObjectDefaultMismatches (cyclomatic 30) · ×1
  • value-object-default.valueObjectDefaultMismatches (cyclomatic 30) packages/2-sql-family/2-authoring/contract-psl/src/value-object-default.ts:86 — value-object-default.valueObjectDefaultMismatches has cyclomatic complexity 30 (threshold 15). Most of this is not in the body itself: 10 of the 30 points are its own statements and the rest belongs to 3 function items inside it that branch (checkMember, checkObject, checkOne). 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.
D1 · Cyclomatic Complexity · build-contract.buildSqlContractFromDefinition (cyclomatic 29) · ×1
  • build-contract.buildSqlContractFromDefinition (cyclomatic 29) packages/2-sql-family/2-authoring/contract-ts/src/build-contract.ts:294 — build-contract.buildSqlContractFromDefinition has cyclomatic complexity 29 (threshold 15). Of this number, 19 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · contract-lowering.lowerPackEntityHandles (cyclomatic 29) · ×1
  • contract-lowering.lowerPackEntityHandles (cyclomatic 29) packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts:1213 — contract-lowering.lowerPackEntityHandles has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 14 of the 29 points are its own statements and the rest belongs to 4 function items inside it that branch (declaredModelName, resolveRef, walkEntityTypes, …). 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.
D1 · Cyclomatic Complexity · review-artifacts.assertReviewStateV2 (cyclomatic 29) · ×1
  • review-artifacts.assertReviewStateV2 (cyclomatic 29) skills-contrib/review-fetch-phase/scripts/review-artifacts.mjs:420 — review-artifacts.assertReviewStateV2 has cyclomatic complexity 29 (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.
D1 · Cyclomatic Complexity · sign.createDbSignCommand (cyclomatic 28) · ×1
  • sign.createDbSignCommand (cyclomatic 28) packages/1-framework/3-tooling/cli/src/orm/db/sign.ts:443 — sign.createDbSignCommand has cyclomatic complexity 28 (threshold 15). Most of this is not in the body itself: 1 of the 28 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 496, 646, 674). 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.
D1 · Cyclomatic Complexity · migration-check.checkSingleTarget (cyclomatic 28) · ×1
  • migration-check.checkSingleTarget (cyclomatic 28) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-check.ts:476 — migration-check.checkSingleTarget 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.
D1 · Cyclomatic Complexity · completion-provider.providePslCompletionItems (cyclomatic 28) · ×1
  • completion-provider.providePslCompletionItems (cyclomatic 28) packages/1-framework/3-tooling/language-server/src/completion-provider.ts:125 — completion-provider.providePslCompletionItems has cyclomatic complexity 28 (threshold 15). Of this number, 26 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · psl-column-resolution.resolveFieldTypeDescriptor (cyclomatic 28) · ×1
  • psl-column-resolution.resolveFieldTypeDescriptor (cyclomatic 28) packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts:458 — psl-column-resolution.resolveFieldTypeDescriptor 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.
D1 · Cyclomatic Complexity · PostgresControlAdapter.introspectSchema (cyclomatic 28) · ×1
  • PostgresControlAdapter.introspectSchema (cyclomatic 28) packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:859 — PostgresControlAdapter.introspectSchema has cyclomatic complexity 28 (threshold 15). Of this number, 25 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.
D1 · Cyclomatic Complexity · validate-storage.validateMongoStorage (cyclomatic 27) · ×1
  • validate-storage.validateMongoStorage (cyclomatic 27) packages/2-mongo-family/1-foundation/mongo-contract/src/validate-storage.ts:165 — validate-storage.validateMongoStorage has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · schema-to-view.collectionToSchemaNode (cyclomatic 27) · ×1
  • schema-to-view.collectionToSchemaNode (cyclomatic 27) packages/2-mongo-family/9-family/src/core/schema-to-view.ts:22 — schema-to-view.collectionToSchemaNode has cyclomatic complexity 27 (threshold 15). Of this number, 24 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.
D1 · Cyclomatic Complexity · control-instance.createSqlFamilyInstance.verify (cyclomatic 27) · ×1
  • control-instance.createSqlFamilyInstance.verify (cyclomatic 27) packages/2-sql-family/9-family/src/core/control-instance.ts:745 — control-instance.createSqlFamilyInstance.verify has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index-and-check-renames.pairIndexRenames (cyclomatic 27) · ×1
  • index-and-check-renames.pairIndexRenames (cyclomatic 27) packages/3-targets/postgres/1-target/src/core/migrations/index-and-check-renames.ts:32 — index-and-check-renames.pairIndexRenames has cyclomatic complexity 27 (threshold 15). Of this number, 21 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · adapter.renderExpr (cyclomatic 27) · ×1
  • adapter.renderExpr (cyclomatic 27) packages/3-targets/sqlite/2-adapter/src/core/adapter.ts:384 — adapter.renderExpr has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · sync-agent-rules.syncAgentRules (cyclomatic 27) · ×1
  • sync-agent-rules.syncAgentRules (cyclomatic 27) scripts/sync-agent-rules.mjs:101 — sync-agent-rules.syncAgentRules has cyclomatic complexity 27 (threshold 15). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · resolve-statements.resolveFieldStatement (cyclomatic 26) · ×1
  • resolve-statements.resolveFieldStatement (cyclomatic 26) packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:1687 — resolve-statements.resolveFieldStatement 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.
D1 · Cyclomatic Complexity · unfilled-placeholders.tokenize (cyclomatic 26) · ×1
  • unfilled-placeholders.tokenize (cyclomatic 26) packages/1-framework/3-tooling/cli/src/control-api/operations/unfilled-placeholders.ts:91 — unfilled-placeholders.tokenize has cyclomatic complexity 26 (threshold 15). Of this number, 21 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migration-list-graph-topology.classifyNormalizedEdges (cyclomatic 26) · ×1
  • migration-list-graph-topology.classifyNormalizedEdges (cyclomatic 26) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-list-graph-topology.ts:177 — migration-list-graph-topology.classifyNormalizedEdges has cyclomatic complexity 26 (threshold 15). Of this number, 16 points are the body's own statements and 10 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · operation-subjects.sqliteCallSubjects (cyclomatic 26) · ×1
  • operation-subjects.sqliteCallSubjects (cyclomatic 26) packages/3-targets/sqlite/1-target/src/core/migrations/operation-subjects.ts:92 — operation-subjects.sqliteCallSubjects has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 115, 103). 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.
D1 · Cyclomatic Complexity · migrate.executeMigrate (cyclomatic 25) · ×1
  • migrate.executeMigrate (cyclomatic 25) packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts:141 — migrate.executeMigrate has cyclomatic complexity 25 (threshold 15). Of this number, 18 points are the body's own statements and 7 belong to 5 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · update.createDbUpdateCommand (cyclomatic 25) · ×1
  • update.createDbUpdateCommand (cyclomatic 25) packages/1-framework/3-tooling/cli/src/orm/db/update.ts:254 — update.createDbUpdateCommand 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 4 function literals inside it that branch (lines 290, 294, 301, …). 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.
D1 · Cyclomatic Complexity · validators.validateSqlStorageConsistency (cyclomatic 25) · ×1
  • validators.validateSqlStorageConsistency (cyclomatic 25) packages/2-sql-family/1-core/contract/src/validators.ts:1015 — validators.validateSqlStorageConsistency has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MongoMigrationRunner.apply (cyclomatic 25) · ×1
  • MongoMigrationRunner.apply (cyclomatic 25) packages/3-targets/mongo/1-target/src/core/migrations/mongo-runner.ts:248 — MongoMigrationRunner.apply has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · infer-model-blocks.buildModel (cyclomatic 25) · ×1
  • infer-model-blocks.buildModel (cyclomatic 25) packages/3-targets/postgres/1-target/src/core/psl-infer/infer-model-blocks.ts:53 — infer-model-blocks.buildModel has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · symbol-table.buildSymbolTable (cyclomatic 24) · ×1
  • symbol-table.buildSymbolTable (cyclomatic 24) packages/1-framework/2-authoring/psl-parser/src/symbol-table.ts:157 — symbol-table.buildSymbolTable has cyclomatic complexity 24 (threshold 15). Of this number, 21 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · sql-expression-text.checkSqlExpressionText (cyclomatic 24) · ×1
  • sql-expression-text.checkSqlExpressionText (cyclomatic 24) packages/2-sql-family/9-family/src/core/migrations/sql-expression-text.ts:68 — sql-expression-text.checkSqlExpressionText has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · PostgresMigrationPlanner.planSql (cyclomatic 24) · ×1
  • PostgresMigrationPlanner.planSql (cyclomatic 24) packages/3-targets/postgres/1-target/src/core/migrations/planner.ts:265 — PostgresMigrationPlanner.planSql has cyclomatic complexity 24 (threshold 15). Of this number, 15 points are the body's own statements and 9 belong to 6 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.
D1 · Cyclomatic Complexity · resolve-statements.resolveStatement (cyclomatic 23) · ×1
  • resolve-statements.resolveStatement (cyclomatic 23) packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:1417 — resolve-statements.resolveStatement has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · plan-questions.dataLossQuestion (cyclomatic 23) · ×1
  • plan-questions.dataLossQuestion (cyclomatic 23) packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts:654 — plan-questions.dataLossQuestion has cyclomatic complexity 23 (threshold 15). Of this number, 17 points are the body's own statements and 6 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · interpreter.resolveNonRelationField (cyclomatic 23) · ×1
  • interpreter.resolveNonRelationField (cyclomatic 23) packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:839 — interpreter.resolveNonRelationField has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index-naming.lowerAuthoredIndex (cyclomatic 23) · ×1
  • index-naming.lowerAuthoredIndex (cyclomatic 23) packages/2-sql-family/1-core/contract/src/index-naming.ts:138 — index-naming.lowerAuthoredIndex has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · control-instance.extractCodecTypeIdsFromContract (cyclomatic 23) · ×1
  • control-instance.extractCodecTypeIdsFromContract (cyclomatic 23) packages/2-sql-family/9-family/src/core/control-instance.ts:95 — control-instance.extractCodecTypeIdsFromContract has cyclomatic complexity 23 (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.
D1 · Cyclomatic Complexity · check-upgrade-coverage.runCheck (cyclomatic 23) · ×1
  • check-upgrade-coverage.runCheck (cyclomatic 23) REDACTED:278 — check-upgrade-coverage.runCheck has cyclomatic complexity 23 (threshold 15). Of this number, 19 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · coverage-report.formatCoverageReport (cyclomatic 23) · ×1
  • coverage-report.formatCoverageReport (cyclomatic 23) scripts/coverage-report.mjs:305 — coverage-report.formatCoverageReport has cyclomatic complexity 23 (threshold 15). Of this number, 21 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migration-graph-rows.layerNodesByLongestForwardPath (cyclomatic 22) · ×1
  • migration-graph-rows.layerNodesByLongestForwardPath (cyclomatic 22) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-rows.ts:184 — migration-graph-rows.layerNodesByLongestForwardPath has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · contract-ref.parseContractRef (cyclomatic 22) · ×1
  • contract-ref.parseContractRef (cyclomatic 22) packages/1-framework/3-tooling/migration/src/refs/contract-ref.ts:52 — contract-ref.parseContractRef has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · relations.referentialActionRejections (cyclomatic 22) · ×1
  • relations.referentialActionRejections (cyclomatic 22) packages/2-sql-family/2-authoring/contract-prisma7/src/relations.ts:306 — relations.referentialActionRejections has cyclomatic complexity 22 (threshold 15). Of this number, 20 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · psl-relation-resolution.applyBackrelationCandidates (cyclomatic 22) · ×1
  • psl-relation-resolution.applyBackrelationCandidates (cyclomatic 22) packages/2-sql-family/2-authoring/contract-psl/src/psl-relation-resolution.ts:395 — psl-relation-resolution.applyBackrelationCandidates has cyclomatic complexity 22 (threshold 15). Of this number, 17 points are the body's own statements and 5 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · cache-store.copyObject (cyclomatic 22) · ×1
  • cache-store.copyObject (cyclomatic 22) REDACTED:119 — cache-store.copyObject has cyclomatic complexity 22 (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.
D1 · Cyclomatic Complexity · fragments.declaredFieldSpec (cyclomatic 22) · ×1
  • fragments.declaredFieldSpec (cyclomatic 22) packages/3-extensions/sql-orm-client/src/fragments.ts:272 — fragments.declaredFieldSpec has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · model-accessor.createModelAccessorInScope (cyclomatic 22) · ×1
  • model-accessor.createModelAccessorInScope (cyclomatic 22) packages/3-extensions/sql-orm-client/src/model-accessor.ts:179 — model-accessor.createModelAccessorInScope has cyclomatic complexity 22 (threshold 15). Of this number, 21 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.
D1 · Cyclomatic Complexity · post-review-thread-reply.parseCliArgs (cyclomatic 22) · ×1
  • post-review-thread-reply.parseCliArgs (cyclomatic 22) skills-contrib/review-implement-phase/scripts/post-review-thread-reply.mjs:13 — post-review-thread-reply.parseCliArgs has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · contract-snapshot-resolution.resolveContractRefToSnapshot (cyclomatic 21) · ×1
  • contract-snapshot-resolution.resolveContractRefToSnapshot (cyclomatic 21) packages/1-framework/3-tooling/cli/src/control-api/operations/contract-snapshot-resolution.ts:85 — contract-snapshot-resolution.resolveContractRefToSnapshot has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migration-graph-rows.weaklyConnectedComponents (cyclomatic 21) · ×1
  • migration-graph-rows.weaklyConnectedComponents (cyclomatic 21) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-rows.ts:58 — migration-graph-rows.weaklyConnectedComponents has cyclomatic complexity 21 (threshold 15). Most of this is not in the body itself: 8 of the 21 points are its own statements and the rest belongs to 4 function items inside it that branch (bfsComponent, a function literal at line 119, addAdjacent, …). 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.
D1 · Cyclomatic Complexity · interpreter.readRelationFields (cyclomatic 21) · ×1
  • interpreter.readRelationFields (cyclomatic 21) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:1350 — interpreter.readRelationFields has cyclomatic complexity 21 (threshold 15). Of this number, 20 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.
D1 · Cyclomatic Complexity · mongo-statement-planning.planFieldStatement (cyclomatic 21) · ×1
  • mongo-statement-planning.planFieldStatement (cyclomatic 21) packages/3-targets/mongo/1-target/src/core/migrations/mongo-statement-planning.ts:546 — mongo-statement-planning.planFieldStatement has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · stored-inet.readIpv6 (cyclomatic 21) · ×1
  • stored-inet.readIpv6 (cyclomatic 21) packages/3-targets/postgres/1-target/src/core/stored-inet.ts:127 — stored-inet.readIpv6 has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · summarize-review-state.parseCliArgs (cyclomatic 21) · ×1
  • summarize-review-state.parseCliArgs (cyclomatic 21) skills-contrib/review-fetch-phase/scripts/summarize-review-state.mjs:30 — summarize-review-state.parseCliArgs has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · re-emit-mti-variant-link-columns.contractNeedsMtiLinkColumns (cyclomatic 21) · ×1
  • re-emit-mti-variant-link-columns.contractNeedsMtiLinkColumns (cyclomatic 21) skills/prisma-8/upgrading/app/upgrades/0.12-to-0.13/re-emit-mti-variant-link-columns.ts:96 — re-emit-mti-variant-link-columns.contractNeedsMtiLinkColumns has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · plan-questions.sameCoordinate (cyclomatic 20) · ×1
  • plan-questions.sameCoordinate (cyclomatic 20) packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts:336 — plan-questions.sameCoordinate has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
D1 · Cyclomatic Complexity · migrate.planSpacePath (cyclomatic 20) · ×1
  • migrate.planSpacePath (cyclomatic 20) packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts:414 — migrate.planSpacePath has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migration-graph.findPathWithDecision (cyclomatic 20) · ×1
  • migration-graph.findPathWithDecision (cyclomatic 20) packages/1-framework/3-tooling/migration/src/migration-graph.ts:289 — migration-graph.findPathWithDecision has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · psl-column-resolution.resolveEntityRefTypeConstructorCall (cyclomatic 20) · ×1
  • psl-column-resolution.resolveEntityRefTypeConstructorCall (cyclomatic 20) packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts:269 — psl-column-resolution.resolveEntityRefTypeConstructorCall has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · contract-lowering.resolveModelNode (cyclomatic 20) · ×1
  • contract-lowering.resolveModelNode (cyclomatic 20) packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts:949 — contract-lowering.resolveModelNode has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 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.
D1 · Cyclomatic Complexity · query-plan-aggregate.compileGroupedAggregate (cyclomatic 20) · ×1
  • query-plan-aggregate.compileGroupedAggregate (cyclomatic 20) packages/3-extensions/sql-orm-client/src/query-plan-aggregate.ts:283 — query-plan-aggregate.compileGroupedAggregate has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · query-plan-select.buildIncludeChildRowsSelect (cyclomatic 20) · ×1
  • query-plan-select.buildIncludeChildRowsSelect (cyclomatic 20) packages/3-extensions/sql-orm-client/src/query-plan-select.ts:512 — query-plan-select.buildIncludeChildRowsSelect has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · contract-to-postgres-database-schema-node.contractToPostgresDatabaseSchemaNode (cyclomatic 20) · ×1
  • contract-to-postgres-database-schema-node.contractToPostgresDatabaseSchemaNode (cyclomatic 20) packages/3-targets/postgres/1-target/src/core/migrations/contract-to-postgres-database-schema-node.ts:99 — contract-to-postgres-database-schema-node.contractToPostgresDatabaseSchemaNode has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 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.
D1 · Cyclomatic Complexity · index-and-check-renames.pairCheckRenames (cyclomatic 20) · ×1
  • index-and-check-renames.pairCheckRenames (cyclomatic 20) packages/3-targets/postgres/1-target/src/core/migrations/index-and-check-renames.ts:152 — index-and-check-renames.pairCheckRenames has cyclomatic complexity 20 (threshold 15). Of this number, 17 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · model-attributes.buildModelAttributes (cyclomatic 20) · ×1
  • model-attributes.buildModelAttributes (cyclomatic 20) packages/3-targets/postgres/1-target/src/core/psl-print/model-attributes.ts:122 — model-attributes.buildModelAttributes has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · refusals.refuseFieldColumnMismatch (cyclomatic 20) · ×1
  • refusals.refuseFieldColumnMismatch (cyclomatic 20) packages/3-targets/postgres/1-target/src/core/psl-print/refusals.ts:233 — refusals.refuseFieldColumnMismatch has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · planner-strategies.recreateTableStrategy (cyclomatic 20) · ×1
  • planner-strategies.recreateTableStrategy (cyclomatic 20) packages/3-targets/sqlite/1-target/src/core/migrations/planner-strategies.ts:256 — planner-strategies.recreateTableStrategy has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · authoring-type-choice.assertTypeChoiceValid (cyclomatic 19) · ×1
  • authoring-type-choice.assertTypeChoiceValid (cyclomatic 19) packages/1-framework/1-core/framework-components/src/shared/authoring-type-choice.ts:325 — authoring-type-choice.assertTypeChoiceValid has cyclomatic complexity 19 (threshold 15). Of this number, 15 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · order-issues-by-dependencies.orderIssuesByDependencies (cyclomatic 19) · ×1
  • order-issues-by-dependencies.orderIssuesByDependencies (cyclomatic 19) packages/1-framework/1-core/framework-components/src/control/order-issues-by-dependencies.ts:69 — order-issues-by-dependencies.orderIssuesByDependencies has cyclomatic complexity 19 (threshold 15). Of this number, 16 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · verify.createDbVerifyCommand (cyclomatic 19) · ×1
  • verify.createDbVerifyCommand (cyclomatic 19) packages/1-framework/3-tooling/cli/src/orm/db/verify.ts:363 — verify.createDbVerifyCommand 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 one function literal inside it that branches (line 404). 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.
D1 · Cyclomatic Complexity · migration-new.executeMigrationNewCommand (cyclomatic 19) · ×1
  • migration-new.executeMigrationNewCommand (cyclomatic 19) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-new.ts:62 — migration-new.executeMigrationNewCommand 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.
D1 · Cyclomatic Complexity · domain-type-generation.generateModelRelationsType (cyclomatic 19) · ×1
  • domain-type-generation.generateModelRelationsType (cyclomatic 19) packages/1-framework/3-tooling/emitter/src/domain-type-generation.ts:128 — domain-type-generation.generateModelRelationsType 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.
D1 · Cyclomatic Complexity · MongoIndexOptions.constructor (cyclomatic 19) · ×1
  • MongoIndexOptions.constructor (cyclomatic 19) packages/2-mongo-family/1-foundation/mongo-contract/src/ir/mongo-index-options.ts:61 — MongoIndexOptions.constructor has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · interpreter.collectIndexes (cyclomatic 19) · ×1
  • interpreter.collectIndexes (cyclomatic 19) packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:598 — interpreter.collectIndexes 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.
D1 · Cyclomatic Complexity · decoding.decodeMongoRow · ×1
  • decoding.decodeMongoRow::walkField (cyclomatic 19) packages/2-mongo-family/7-runtime/src/codecs/decoding.ts:129 — decoding.decodeMongoRow::walkField 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.
D1 · Cyclomatic Complexity · control-instance.createSqlFamilyInstance.toSchemaView (cyclomatic 19) · ×1
  • control-instance.createSqlFamilyInstance.toSchemaView (cyclomatic 19) packages/2-sql-family/9-family/src/core/control-instance.ts:1051 — control-instance.createSqlFamilyInstance.toSchemaView 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 3 function literals inside it that branch (lines 1092, 1085, 1195). 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.
D1 · Cyclomatic Complexity · bson-codec-helpers.assertBsonValue (cyclomatic 19) · ×1
  • bson-codec-helpers.assertBsonValue (cyclomatic 19) packages/3-targets/mongo/1-target/src/core/bson-codec-helpers.ts:50 — bson-codec-helpers.assertBsonValue 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.
D1 · Cyclomatic Complexity · stored-inet.readIpv4 (cyclomatic 19) · ×1
  • stored-inet.readIpv4 (cyclomatic 19) packages/3-targets/postgres/1-target/src/core/stored-inet.ts:42 — stored-inet.readIpv4 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.
D1 · Cyclomatic Complexity · infer-psl-contract.inferPostgresPslContract (cyclomatic 19) · ×1
  • infer-psl-contract.inferPostgresPslContract (cyclomatic 19) packages/3-targets/postgres/1-target/src/core/psl-infer/infer-psl-contract.ts:82 — infer-psl-contract.inferPostgresPslContract 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.
D1 · Cyclomatic Complexity · migrate-migrations-layout.applyMigrationsRootPlan (cyclomatic 19) · ×1
  • migrate-migrations-layout.applyMigrationsRootPlan (cyclomatic 19) scripts/migrate-migrations-layout.mjs:514 — migrate-migrations-layout.applyMigrationsRootPlan 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.
D1 · Cyclomatic Complexity · createCrossDomainRules (cyclomatic 19) · ×1
  • createCrossDomainRules (cyclomatic 19) dependency-cruiser.config.mjs:118 — createCrossDomainRules has cyclomatic complexity 19 (threshold 15). Of this number, 16 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.
D1 · Cyclomatic Complexity · data-type-support.enforceDataTypeAssemblyInvariants (cyclomatic 18) · ×1
  • data-type-support.enforceDataTypeAssemblyInvariants (cyclomatic 18) packages/1-framework/1-core/framework-components/src/shared/data-type-support.ts:198 — data-type-support.enforceDataTypeAssemblyInvariants has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · completion-context.classifyAttributeExpression (cyclomatic 18) · ×1
  • completion-context.classifyAttributeExpression (cyclomatic 18) packages/1-framework/3-tooling/language-server/src/completion-context.ts:780 — completion-context.classifyAttributeExpression has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · derive-json-schema.fieldToBsonSchema (cyclomatic 18) · ×1
  • derive-json-schema.fieldToBsonSchema (cyclomatic 18) packages/2-mongo-family/1-foundation/mongo-contract/src/derive-json-schema.ts:130 — derive-json-schema.fieldToBsonSchema has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · refusal-diagnostics.refusalDiagnostic (cyclomatic 18) · ×1
  • refusal-diagnostics.refusalDiagnostic (cyclomatic 18) packages/2-mongo-family/2-authoring/contract-prisma6/src/refusal-diagnostics.ts:52 — refusal-diagnostics.refusalDiagnostic has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index-equivalence.deepEqual (cyclomatic 18) · ×1
  • index-equivalence.deepEqual (cyclomatic 18) packages/2-mongo-family/3-tooling/mongo-schema-ir/src/index-equivalence.ts:5 — index-equivalence.deepEqual has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · indexes.parseIndexAttribute (cyclomatic 18) · ×1
  • indexes.parseIndexAttribute (cyclomatic 18) packages/2-sql-family/2-authoring/contract-prisma7/src/indexes.ts:22 — indexes.parseIndexAttribute has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · defaults.lowerFunction (cyclomatic 18) · ×1
  • defaults.lowerFunction (cyclomatic 18) packages/2-sql-family/2-authoring/contract-prisma7/src/defaults.ts:359 — defaults.lowerFunction has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · contract-lowering.resolveRelationForeignKeys (cyclomatic 18) · ×1
  • contract-lowering.resolveRelationForeignKeys (cyclomatic 18) packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts:275 — contract-lowering.resolveRelationForeignKeys has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.generateTableLiteralType (cyclomatic 18) · ×1
  • index.generateTableLiteralType (cyclomatic 18) packages/2-sql-family/3-tooling/emitter/src/index.ts:396 — index.generateTableLiteralType has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 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.
D1 · Cyclomatic Complexity · SelectAst.collectColumnRefs (cyclomatic 18) · ×1
  • SelectAst.collectColumnRefs (cyclomatic 18) packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:1839 — SelectAst.collectColumnRefs has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · SelectAst.collectParamRefs (cyclomatic 18) · ×1
  • SelectAst.collectParamRefs (cyclomatic 18) packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:1898 — SelectAst.collectParamRefs has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · sql-runtime.withTransaction (cyclomatic 18) · ×1
  • sql-runtime.withTransaction (cyclomatic 18) packages/2-sql-family/5-runtime/src/sql-runtime.ts:1802 — sql-runtime.withTransaction has cyclomatic complexity 18 (threshold 15). Of this number, 11 points are the body's own statements and 7 belong to 4 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · field-event-planner.planFieldEventCalls (cyclomatic 18) · ×1
  • field-event-planner.planFieldEventCalls (cyclomatic 18) packages/2-sql-family/9-family/src/core/migrations/field-event-planner.ts:95 — field-event-planner.planFieldEventCalls has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · mongo-planner.planCollectionDiff (cyclomatic 18) · ×1
  • mongo-planner.planCollectionDiff (cyclomatic 18) packages/3-targets/mongo/1-target/src/core/migrations/mongo-planner.ts:300 — mongo-planner.planCollectionDiff has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MongoMigrationRunner.executeDmlOperation (cyclomatic 18) · ×1
  • MongoMigrationRunner.executeDmlOperation (cyclomatic 18) packages/3-targets/mongo/1-target/src/core/migrations/mongo-runner.ts:477 — MongoMigrationRunner.executeDmlOperation has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · MysqlMigrationRunner.#applySpace (cyclomatic 18) · ×1
  • MysqlMigrationRunner.#applySpace (cyclomatic 18) packages/3-targets/mysql/1-target/src/core/migrations/runner.ts:149 — MysqlMigrationRunner.#applySpace has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · main.main (cyclomatic 17) · ×1
  • main.main (cyclomatic 17) REDACTED:175 — main.main has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 7 of the 17 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 348, openEditorFunc, a function literal at line 291, …). 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.
D1 · Cyclomatic Complexity · written-value.readWrittenValueIntoCodec (cyclomatic 17) · ×1
  • written-value.readWrittenValueIntoCodec (cyclomatic 17) packages/1-framework/1-core/framework-components/src/shared/written-value.ts:369 — written-value.readWrittenValueIntoCodec has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · expressions.decodeStringLiteral (cyclomatic 17) · ×1
  • expressions.decodeStringLiteral (cyclomatic 17) packages/1-framework/2-authoring/psl-parser/src/syntax/ast/expressions.ts:126 — expressions.decodeStringLiteral has cyclomatic complexity 17 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D1 · Cyclomatic Complexity · contract-at-errors.mapContractAtError (cyclomatic 17) · ×1
  • contract-at-errors.mapContractAtError (cyclomatic 17) packages/1-framework/3-tooling/cli/src/control-api/operations/contract-at-errors.ts:12 — contract-at-errors.mapContractAtError has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migration-graph-grid-layout.buildGrid · ×1
  • migration-graph-grid-layout.buildGrid::emitConnectorRow (cyclomatic 17) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts:800 — migration-graph-grid-layout.buildGrid::emitConnectorRow has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (migration-graph-grid-layout.buildGrid) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D1 · Cyclomatic Complexity · migration-plan.runPlannerLeg (cyclomatic 17) · ×1
  • migration-plan.runPlannerLeg (cyclomatic 17) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts:172 — migration-plan.runPlannerLeg has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 4 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · generate-contract-dts.generateContractDts (cyclomatic 17) · ×1
  • generate-contract-dts.generateContractDts (cyclomatic 17) REDACTED:67 — generate-contract-dts.generateContractDts has cyclomatic complexity 17 (threshold 15). Of this number, 12 points are the body's own statements and 5 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.
D1 · Cyclomatic Complexity · signature-context.signatureExpression (cyclomatic 17) · ×1
  • signature-context.signatureExpression (cyclomatic 17) packages/1-framework/3-tooling/language-server/src/signature-context.ts:147 — signature-context.signatureExpression has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · stream-server.runServerOverStreams (cyclomatic 17) · ×1
  • stream-server.runServerOverStreams (cyclomatic 17) packages/1-framework/3-tooling/language-server/src/stream-server.ts:57 — stream-server.runServerOverStreams has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to 6 function literals inside it that branch (lines 116, 80, 120, …). 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.
D1 · Cyclomatic Complexity · SqlColumnDefaultIR.isEqualTo (cyclomatic 17) · ×1
  • SqlColumnDefaultIR.isEqualTo (cyclomatic 17) packages/2-sql-family/1-core/schema-ir/src/ir/sql-column-default-ir.ts:112 — SqlColumnDefaultIR.isEqualTo has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · interpreter.resolveVariants (cyclomatic 17) · ×1
  • interpreter.resolveVariants (cyclomatic 17) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:1786 — interpreter.resolveVariants has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · sql-context.assertColumnCodecIntegrity (cyclomatic 17) · ×1
  • sql-context.assertColumnCodecIntegrity (cyclomatic 17) packages/2-sql-family/5-runtime/src/sql-context.ts:326 — sql-context.assertColumnCodecIntegrity has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · contract-stack-checks.refusedDefaults (cyclomatic 17) · ×1
  • contract-stack-checks.refusedDefaults (cyclomatic 17) packages/2-sql-family/9-family/src/core/contract-stack-checks.ts:125 — contract-stack-checks.refusedDefaults has cyclomatic complexity 17 (threshold 15). Most of this is not in the body itself: 1 of the 17 points is its own statement and the rest belongs to one function literal inside it that branches (line 127). 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.
D1 · Cyclomatic Complexity · control-instance.assertNoCrossSpaceFkReverseReferences (cyclomatic 17) · ×1
  • control-instance.assertNoCrossSpaceFkReverseReferences (cyclomatic 17) packages/2-sql-family/9-family/src/core/control-instance.ts:412 — control-instance.assertNoCrossSpaceFkReverseReferences has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · json-codec-helpers.decodeValue (cyclomatic 17) · ×1
  • json-codec-helpers.decodeValue (cyclomatic 17) packages/3-targets/mongo/1-target/src/core/json-codec-helpers.ts:161 — json-codec-helpers.decodeValue has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · authoring.postgresLowerEntityHandles (cyclomatic 17) · ×1
  • authoring.postgresLowerEntityHandles (cyclomatic 17) packages/3-targets/postgres/1-target/src/core/authoring.ts:904 — authoring.postgresLowerEntityHandles has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · planner-strategies.typeChangeCallStrategy (cyclomatic 17) · ×1
  • planner-strategies.typeChangeCallStrategy (cyclomatic 17) packages/3-targets/postgres/1-target/src/core/migrations/planner-strategies.ts:301 — planner-strategies.typeChangeCallStrategy has cyclomatic complexity 17 (threshold 15). Of this number, 15 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, 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.
D1 · Cyclomatic Complexity · planner-strategies.notNullAddColumnCallStrategy (cyclomatic 17) · ×1
  • planner-strategies.notNullAddColumnCallStrategy (cyclomatic 17) packages/3-targets/postgres/1-target/src/core/migrations/planner-strategies.ts:487 — planner-strategies.notNullAddColumnCallStrategy has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · issue-planner.mapNodeIssueToCall (cyclomatic 17) · ×1
  • issue-planner.mapNodeIssueToCall (cyclomatic 17) packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts:1033 — issue-planner.mapNodeIssueToCall has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: issue-planner.classifyCall (cyclomatic 44) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
D1 · Cyclomatic Complexity · PostgresMigrationRunner.executeOnConnection (cyclomatic 17) · ×1
  • PostgresMigrationRunner.executeOnConnection (cyclomatic 17) packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:159 — PostgresMigrationRunner.executeOnConnection has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · infer-policy-blocks.buildIntrospectedPolicyBlocks (cyclomatic 17) · ×1
  • infer-policy-blocks.buildIntrospectedPolicyBlocks (cyclomatic 17) packages/3-targets/postgres/1-target/src/core/psl-infer/infer-policy-blocks.ts:34 — infer-policy-blocks.buildIntrospectedPolicyBlocks has cyclomatic complexity 17 (threshold 15). 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, 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.
D1 · Cyclomatic Complexity · SqliteMigrationRunner.executeOnConnection (cyclomatic 17) · ×1
  • SqliteMigrationRunner.executeOnConnection (cyclomatic 17) packages/3-targets/sqlite/1-target/src/core/migrations/runner.ts:80 — SqliteMigrationRunner.executeOnConnection has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D1 · Cyclomatic Complexity · fetch-review-state.parseCliArgs (cyclomatic 17) · ×1
  • fetch-review-state.parseCliArgs (cyclomatic 17) skills-contrib/review-fetch-phase/scripts/fetch-review-state.mjs:143 — fetch-review-state.parseCliArgs has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · render-review-actions.parseCliArgs (cyclomatic 17) · ×1
  • render-review-actions.parseCliArgs (cyclomatic 17) skills-contrib/review-triage-phase/scripts/render-review-actions.mjs:31 — render-review-actions.parseCliArgs has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · mongo-field-storage-names.main (cyclomatic 17) · ×1
  • mongo-field-storage-names.main (cyclomatic 17) REDACTED:186 — mongo-field-storage-names.main has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · generator-functions.assembleGeneratorFunctions (cyclomatic 16) · ×1
  • generator-functions.assembleGeneratorFunctions (cyclomatic 16) packages/1-framework/1-core/framework-components/src/shared/generator-functions.ts:146 — generator-functions.assembleGeneratorFunctions has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · control-stack.assembleAuthoringContributions (cyclomatic 16) · ×1
  • control-stack.assembleAuthoringContributions (cyclomatic 16) packages/1-framework/1-core/framework-components/src/control/control-stack.ts:218 — control-stack.assembleAuthoringContributions 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, 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.
D1 · Cyclomatic Complexity · control-stack.buildExtensionLoadOrder (cyclomatic 16) · ×1
  • control-stack.buildExtensionLoadOrder (cyclomatic 16) packages/1-framework/1-core/framework-components/src/control/control-stack.ts:651 — control-stack.buildExtensionLoadOrder has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · resolve-statements.resolveStatements (cyclomatic 16) · ×1
  • resolve-statements.resolveStatements (cyclomatic 16) packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:1862 — resolve-statements.resolveStatements has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · load-ts-contract.loadContractFromTs (cyclomatic 16) · ×1
  • load-ts-contract.loadContractFromTs (cyclomatic 16) packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:207 — load-ts-contract.loadContractFromTs 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.
D1 · Cyclomatic Complexity · attribute-argument-grammar.advanceGrammar (cyclomatic 16) · ×1
  • attribute-argument-grammar.advanceGrammar (cyclomatic 16) packages/1-framework/3-tooling/language-server/src/attribute-argument-grammar.ts:23 — attribute-argument-grammar.advanceGrammar has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · migration-graph.findPathWithInvariants (cyclomatic 16) · ×1
  • migration-graph.findPathWithInvariants (cyclomatic 16) packages/1-framework/3-tooling/migration/src/migration-graph.ts:141 — migration-graph.findPathWithInvariants has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · verify-contract-spaces.verifyContractSpaces (cyclomatic 16) · ×1
  • verify-contract-spaces.verifyContractSpaces (cyclomatic 16) packages/1-framework/3-tooling/migration/src/verify-contract-spaces.ts:189 — verify-contract-spaces.verifyContractSpaces has cyclomatic complexity 16 (threshold 15). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, 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.
D1 · Cyclomatic Complexity · planner.planMigration (cyclomatic 16) · ×1
  • planner.planMigration (cyclomatic 16) packages/1-framework/3-tooling/migration/src/aggregate/planner.ts:51 — planner.planMigration has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · plugin.prismaVitePlugin.emitContract (cyclomatic 16) · ×1
  • plugin.prismaVitePlugin.emitContract (cyclomatic 16) packages/1-framework/3-tooling/vite-plugin-contract-emit/src/plugin.ts:106 — plugin.prismaVitePlugin.emitContract has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · plugin.prismaVitePlugin.resolveWatchedFiles (cyclomatic 16) · ×1
  • plugin.prismaVitePlugin.resolveWatchedFiles (cyclomatic 16) packages/1-framework/3-tooling/vite-plugin-contract-emit/src/plugin.ts:295 — plugin.prismaVitePlugin.resolveWatchedFiles has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · recursive-groups.recursiveGroupsOf (cyclomatic 16) · ×1
  • recursive-groups.recursiveGroupsOf (cyclomatic 16) packages/2-mongo-family/1-foundation/mongo-contract/src/recursive-groups.ts:28 — recursive-groups.recursiveGroupsOf has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to 2 function items inside it that branch (visit, a function literal at line 37). 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.
D1 · Cyclomatic Complexity · MongoCollectionImpl.#wrapFieldOpValue (cyclomatic 16) · ×1
  • MongoCollectionImpl.#wrapFieldOpValue (cyclomatic 16) packages/2-mongo-family/5-query-builders/orm/src/collection.ts:1363 — MongoCollectionImpl.#wrapFieldOpValue 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.
D1 · Cyclomatic Complexity · contract-warnings.emitTypedCrossModelFallbackWarnings (cyclomatic 16) · ×1
  • contract-warnings.emitTypedCrossModelFallbackWarnings (cyclomatic 16) packages/2-sql-family/2-authoring/contract-ts/src/contract-warnings.ts:132 — contract-warnings.emitTypedCrossModelFallbackWarnings has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · budgets.budgets (cyclomatic 16) · ×1
  • budgets.budgets (cyclomatic 16) packages/2-sql-family/5-runtime/src/middleware/budgets.ts:89 — budgets.budgets has cyclomatic complexity 16 (threshold 15). Of this number, 9 points are the body's own statements and 7 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.
D1 · Cyclomatic Complexity · value-object-field-fills.requiredFields (cyclomatic 16) · ×1
  • value-object-field-fills.requiredFields (cyclomatic 16) packages/2-sql-family/9-family/src/core/migrations/value-object-field-fills.ts:131 — value-object-field-fills.requiredFields has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · mongo-ops-serializer.deserializePipelineStage (cyclomatic 16) · ×1
  • mongo-ops-serializer.deserializePipelineStage (cyclomatic 16) packages/3-targets/mongo/1-target/src/core/migrations/mongo-ops-serializer.ts:469 — mongo-ops-serializer.deserializePipelineStage has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · binding.resolveMongoBinding (cyclomatic 16) · ×1
  • binding.resolveMongoBinding (cyclomatic 16) packages/3-targets/mongo/9-facade/src/runtime/binding.ts:84 — binding.resolveMongoBinding has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · codec-helpers.verboseIntervalFields (cyclomatic 16) · ×1
  • codec-helpers.verboseIntervalFields (cyclomatic 16) packages/3-targets/postgres/1-target/src/core/codec-helpers.ts:217 — codec-helpers.verboseIntervalFields 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.
D1 · Cyclomatic Complexity · relation-fields.buildRelationField (cyclomatic 16) · ×1
  • relation-fields.buildRelationField (cyclomatic 16) packages/3-targets/postgres/1-target/src/core/psl-print/relation-fields.ts:221 — relation-fields.buildRelationField has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · index.runPostgresCodecProjection (cyclomatic 16) · ×1
  • index.runPostgresCodecProjection (cyclomatic 16) packages/3-targets/postgres/4-codec-testkit/src/index.ts:399 — index.runPostgresCodecProjection 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.
D1 · Cyclomatic Complexity · check-upgrade-coverage.validateInstructions (cyclomatic 16) · ×1
  • check-upgrade-coverage.validateInstructions (cyclomatic 16) REDACTED:198 — check-upgrade-coverage.validateInstructions 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.
D1 · Cyclomatic Complexity · lint-workflow-triggers.stripYamlComment (cyclomatic 16) · ×1
  • lint-workflow-triggers.stripYamlComment (cyclomatic 16) scripts/lint-workflow-triggers.mjs:47 — lint-workflow-triggers.stripYamlComment has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D1 · Cyclomatic Complexity · review-artifacts.validateBodyEntryShape (cyclomatic 16) · ×1
  • review-artifacts.validateBodyEntryShape (cyclomatic 16) skills-contrib/review-fetch-phase/scripts/review-artifacts.mjs:350 — review-artifacts.validateBodyEntryShape 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.
D1 · Cyclomatic Complexity · fetch-review-state.main (cyclomatic 16) · ×1
  • fetch-review-state.main (cyclomatic 16) skills-contrib/review-fetch-phase/scripts/fetch-review-state.mjs:491 — fetch-review-state.main 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.
D2 · Cognitive Complexity · interpreter.buildModelNodeFromPsl (cognitive 202) · ×1
  • interpreter.buildModelNodeFromPsl (cognitive 202) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:615 — interpreter.buildModelNodeFromPsl has cognitive complexity 202 (threshold 15). Drivers by points: if/else 59 (150 pts), ternaries 19 (40 pts), boolean chains 9, loops 3 (nesting depth added 112). Of this number, 197 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.interpretPslDocumentToSqlContract (cognitive 140) · ×1
  • interpreter.interpretPslDocumentToSqlContract (cognitive 140) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:2170 — interpreter.interpretPslDocumentToSqlContract has cognitive complexity 140 (threshold 15). Drivers by points: if/else 33 (68 pts), loops 29 (51 pts), ternaries 10 (14 pts), boolean chains 6, error handling 1 (nesting depth added 61). Of this number, 116 points are the body's own statements and 24 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-graph-grid-layout.buildGrid (cognitive 138) · ×1
  • migration-graph-grid-layout.buildGrid (cognitive 138) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts:301 — migration-graph-grid-layout.buildGrid has cognitive complexity 138 (threshold 15). Drivers by points: if/else 56 (98 pts), loops 45 (73 pts), ternaries 12 (19 pts), boolean chains 10 (nesting depth added 77). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (migration-graph-grid-layout.buildGrid::emitConnectorRow) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · relations.lowerRelations (cognitive 135) · ×1
  • relations.lowerRelations (cognitive 135) packages/2-sql-family/2-authoring/contract-prisma7/src/relations.ts:388 — relations.lowerRelations has cognitive complexity 135 (threshold 15). Drivers by points: if/else 28 (89 pts), loops 13 (20 pts), boolean chains 15, ternaries 3 (11 pts) (nesting depth added 76). Of this number, 132 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.
D2 · Cognitive Complexity · migration-graph-grid-layout.buildLaneAssignment (cognitive 123) · ×1
  • migration-graph-grid-layout.buildLaneAssignment (cognitive 123) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts:44 — migration-graph-grid-layout.buildLaneAssignment has cognitive complexity 123 (threshold 15). Drivers by points: if/else 27 (74 pts), loops 20 (39 pts), boolean chains 5, ternaries 1 (5 pts) (nesting depth added 70). Of this number, 118 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.readField (cognitive 109) · ×1
  • interpreter.readField (cognitive 109) packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:1183 — interpreter.readField has cognitive complexity 109 (threshold 15). Drivers by points: if/else 40 (57 pts), boolean chains 27, ternaries 17 (24 pts), loops 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-plan.executeMigrationPlanCommandInner (cognitive 108) · ×1
  • migration-plan.executeMigrationPlanCommandInner (cognitive 108) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts:510 — migration-plan.executeMigrationPlanCommandInner has cognitive complexity 108 (threshold 15). Drivers by points: ternaries 26 (56 pts), if/else 28 (41 pts), boolean chains 6, error handling 3, loops 1, match/switch 1 (nesting depth added 43). Of this number, 106 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.
D2 · Cognitive Complexity · shell-build.defineShellConfig (cognitive 88) · ×1
  • shell-build.defineShellConfig (cognitive 88) packages/0-config/tsdown/shell-build.ts:45 — shell-build.defineShellConfig has cognitive complexity 88 (threshold 15). Drivers by points: if/else 25 (62 pts), loops 6 (13 pts), boolean chains 7, ternaries 2 (6 pts) (nesting depth added 48). Of this number, 84 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validate-storage.validateMongoStorage (cognitive 88) · ×1
  • validate-storage.validateMongoStorage (cognitive 88) packages/2-mongo-family/1-foundation/mongo-contract/src/validate-storage.ts:165 — validate-storage.validateMongoStorage has cognitive complexity 88 (threshold 15). Drivers by points: if/else 16 (61 pts), loops 7 (20 pts), ternaries 1 (5 pts), boolean chains 2 (nesting depth added 62). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · lowering.lowerStage (cognitive 86) · ×1
  • lowering.lowerStage (cognitive 86) packages/3-targets/mongo/2-adapter/src/lowering.ts:252 — lowering.lowerStage has cognitive complexity 86 (threshold 15). Drivers by points: if/else 35 (73 pts), loops 5 (10 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 44). 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.
D2 · Cognitive Complexity · lowering.structuralLowerStage (cognitive 83) · ×1
  • lowering.structuralLowerStage (cognitive 83) packages/3-targets/mongo/2-adapter/src/lowering.ts:489 — lowering.structuralLowerStage has cognitive complexity 83 (threshold 15). Drivers by points: if/else 34 (70 pts), loops 5 (10 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 42). 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.
D2 · Cognitive Complexity · review-artifacts.assertReviewActionsV1 (cognitive 83) · ×1
  • review-artifacts.assertReviewActionsV1 (cognitive 83) skills-contrib/review-triage-phase/scripts/review-artifacts.mjs:23 — review-artifacts.assertReviewActionsV1 has cognitive complexity 83 (threshold 15). Drivers by points: if/else 32 (62 pts), boolean chains 15, loops 3 (6 pts) (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · tables.buildRecreatePostchecks (cognitive 82) · ×1
  • tables.buildRecreatePostchecks (cognitive 82) packages/3-targets/sqlite/1-target/src/core/migrations/operations/tables.ts:580 — tables.buildRecreatePostchecks has cognitive complexity 82 (threshold 15). Drivers by points: if/else 20 (44 pts), ternaries 8 (29 pts), loops 3 (5 pts), boolean chains 4 (nesting depth added 47). 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.
D2 · Cognitive Complexity · interpreter.interpretPslDocumentToMongoContract (cognitive 81) · ×1
  • interpreter.interpretPslDocumentToMongoContract (cognitive 81) packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:1111 — interpreter.interpretPslDocumentToMongoContract has cognitive complexity 81 (threshold 15). Drivers by points: if/else 15 (40 pts), ternaries 8 (23 pts), loops 9 (12 pts), boolean chains 6 (nesting depth added 43). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · enum-value-planning.planEnumValueRewrites (cognitive 81) · ×1
  • enum-value-planning.planEnumValueRewrites (cognitive 81) packages/2-sql-family/9-family/src/core/migrations/enum-value-planning.ts:405 — enum-value-planning.planEnumValueRewrites has cognitive complexity 81 (threshold 15). Drivers by points: if/else 14 (43 pts), loops 8 (22 pts), ternaries 2 (10 pts), boolean chains 6 (nesting depth added 51). Of this number, 78 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.
D2 · Cognitive Complexity · interpreter.interpretPrisma7Documents (cognitive 80) · ×1
  • interpreter.interpretPrisma7Documents (cognitive 80) packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:298 — interpreter.interpretPrisma7Documents has cognitive complexity 80 (threshold 15). Drivers by points: loops 17 (30 pts), if/else 14 (28 pts), ternaries 10 (17 pts), match/switch 1 (3 pts), boolean chains 2 (nesting depth added 36). Of this number, 64 points are the body's own statements and 16 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · binder.tryBindExpression (cognitive 76) · ×1
  • binder.tryBindExpression (cognitive 76) packages/1-framework/2-authoring/psl-parser/src/binder.ts:714 — binder.tryBindExpression has cognitive complexity 76 (threshold 15). Drivers by points: if/else 13 (34 pts), loops 12 (30 pts), boolean chains 6, ternaries 2 (5 pts), match/switch 1 (nesting depth added 42). 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.
D2 · Cognitive Complexity · validators.validateStorageSemantics (cognitive 75) · ×1
  • validators.validateStorageSemantics (cognitive 75) packages/2-sql-family/1-core/contract/src/validators.ts:713 — validators.validateStorageSemantics has cognitive complexity 75 (threshold 15). Drivers by points: if/else 14 (46 pts), loops 12 (25 pts), boolean chains 4 (nesting depth added 45). Of this number, 73 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · psl-field-resolution.collectResolvedFields (cognitive 72) · ×1
  • psl-field-resolution.collectResolvedFields (cognitive 72) packages/2-sql-family/2-authoring/contract-psl/src/psl-field-resolution.ts:236 — psl-field-resolution.collectResolvedFields has cognitive complexity 72 (threshold 15). Drivers by points: if/else 19 (41 pts), ternaries 9 (22 pts), boolean chains 8, loops 1 (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · symbol-table.buildSymbolTable (cognitive 71) · ×1
  • symbol-table.buildSymbolTable (cognitive 71) packages/1-framework/2-authoring/psl-parser/src/symbol-table.ts:157 — symbol-table.buildSymbolTable has cognitive complexity 71 (threshold 15). Drivers by points: if/else 18 (50 pts), loops 4 (12 pts), ternaries 2 (9 pts) (nesting depth added 47). Of this number, 64 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · check-conformance.runCheck (cognitive 69) · ×1
  • check-conformance.runCheck (cognitive 69) scripts/check-conformance.mjs:656 — check-conformance.runCheck has cognitive complexity 69 (threshold 15). Drivers by points: if/else 17 (34 pts), loops 9 (18 pts), ternaries 4 (14 pts), boolean chains 2, error handling 1 (nesting depth added 36). 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.
D2 · Cognitive Complexity · control-instance.assertNoCrossSpaceFkReverseReferences (cognitive 67) · ×1
  • control-instance.assertNoCrossSpaceFkReverseReferences (cognitive 67) packages/2-sql-family/9-family/src/core/control-instance.ts:412 — control-instance.assertNoCrossSpaceFkReverseReferences has cognitive complexity 67 (threshold 15). Drivers by points: if/else 11 (52 pts), loops 5 (15 pts) (nesting depth added 51). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validators.validateSqlStorageConsistency (cognitive 66) · ×1
  • validators.validateSqlStorageConsistency (cognitive 66) packages/2-sql-family/1-core/contract/src/validators.ts:1015 — validators.validateSqlStorageConsistency has cognitive complexity 66 (threshold 15). Drivers by points: if/else 11 (39 pts), loops 10 (25 pts), boolean chains 2 (nesting depth added 43). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · lint-no-contract-cast.blankCommentsAndStrings (cognitive 65) · ×1
  • lint-no-contract-cast.blankCommentsAndStrings (cognitive 65) scripts/lint-no-contract-cast.mjs:68 — lint-no-contract-cast.blankCommentsAndStrings has cognitive complexity 65 (threshold 15). Drivers by points: if/else 11 (38 pts), loops 5 (15 pts), boolean chains 10, ternaries 1 (2 pts) (nesting depth added 38). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgresMigrationPlanner.planPostgresSchemaDiff (cognitive 64) · ×1
  • PostgresMigrationPlanner.planPostgresSchemaDiff (cognitive 64) packages/3-targets/postgres/1-target/src/core/migrations/planner.ts:646 — PostgresMigrationPlanner.planPostgresSchemaDiff has cognitive complexity 64 (threshold 15). Drivers by points: if/else 15 (33 pts), ternaries 6 (17 pts), loops 8 (13 pts), boolean chains 1 (nesting depth added 34). Of this number, 46 points are the body's own statements and 18 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.
D2 · Cognitive Complexity · interpreter.interpretPrisma6Documents (cognitive 63) · ×1
  • interpreter.interpretPrisma6Documents (cognitive 63) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:201 — interpreter.interpretPrisma6Documents has cognitive complexity 63 (threshold 15). Drivers by points: loops 18 (32 pts), if/else 13 (27 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 30). Of this number, 57 points are the body's own statements and 6 belong to 2 function items inside it that branch. 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.
D2 · Cognitive Complexity · init-scaffold.planScaffold (cognitive 61) · ×1
  • init-scaffold.planScaffold (cognitive 61) packages/1-framework/3-tooling/cli/src/orm/init-scaffold.ts:205 — init-scaffold.planScaffold has cognitive complexity 61 (threshold 15). Drivers by points: if/else 23 (40 pts), ternaries 8 (11 pts), boolean chains 6, error handling 2 (4 pts) (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · psl-column-resolution.lowerTypeDefault (cognitive 61) · ×1
  • psl-column-resolution.lowerTypeDefault (cognitive 61) packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts:672 — psl-column-resolution.lowerTypeDefault has cognitive complexity 61 (threshold 15). Drivers by points: if/else 27 (43 pts), boolean chains 8, ternaries 3 (6 pts), loops 2 (4 pts) (nesting depth added 21). Of this number, 41 points are the body's own statements and 20 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · framework-authoring.isWellFormedDescriptor (cognitive 60) · ×1
  • framework-authoring.isWellFormedDescriptor (cognitive 60) packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:699 — framework-authoring.isWellFormedDescriptor has cognitive complexity 60 (threshold 15). Drivers by points: if/else 19 (36 pts), boolean chains 18, ternaries 3 (5 pts), match/switch 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migrate-show.executeMigrateShowPlan (cognitive 60) · ×1
  • migrate-show.executeMigrateShowPlan (cognitive 60) packages/1-framework/3-tooling/cli/src/control-api/operations/migrate-show.ts:91 — migrate-show.executeMigrateShowPlan has cognitive complexity 60 (threshold 15). Drivers by points: if/else 19 (34 pts), ternaries 7 (13 pts), loops 3 (6 pts), boolean chains 4, error handling 2 (3 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · plan-questions.askPlanQuestions (cognitive 59) · ×1
  • plan-questions.askPlanQuestions (cognitive 59) packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts:944 — plan-questions.askPlanQuestions has cognitive complexity 59 (threshold 15). Drivers by points: if/else 13 (30 pts), ternaries 5 (11 pts), loops 5 (10 pts), boolean chains 8 (nesting depth added 28). Of this number, 38 points are the body's own statements and 21 belong to 7 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · sync-agent-rules.syncAgentRules (cognitive 59) · ×1
  • sync-agent-rules.syncAgentRules (cognitive 59) scripts/sync-agent-rules.mjs:101 — sync-agent-rules.syncAgentRules has cognitive complexity 59 (threshold 15). Drivers by points: if/else 15 (39 pts), loops 7 (12 pts), boolean chains 4, ternaries 1 (4 pts) (nesting depth added 32). Of this number, 58 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · binder.bind (cognitive 57) · ×1
  • binder.bind (cognitive 57) packages/1-framework/2-authoring/psl-parser/src/binder.ts:358 — binder.bind has cognitive complexity 57 (threshold 15). Drivers by points: if/else 15 (32 pts), loops 11 (14 pts), ternaries 5 (8 pts), boolean chains 3 (nesting depth added 23). Of this number, 32 points are the body's own statements and 25 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgresControlAdapter.introspectSchema (cognitive 57) · ×1
  • PostgresControlAdapter.introspectSchema (cognitive 57) packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:859 — PostgresControlAdapter.introspectSchema has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 9 (24 pts), if/else 9 (19 pts), loops 8 (12 pts), boolean chains 2 (nesting depth added 29). Of this number, 51 points are the body's own statements and 6 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.
D2 · Cognitive Complexity · relations.referentialActionRejections (cognitive 56) · ×1
  • relations.referentialActionRejections (cognitive 56) packages/2-sql-family/2-authoring/contract-prisma7/src/relations.ts:306 — relations.referentialActionRejections has cognitive complexity 56 (threshold 15). Drivers by points: ternaries 13 (42 pts), if/else 4 (10 pts), boolean chains 3, loops 1 (nesting depth added 35). Of this number, 54 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · shell-build.validateShellManifest (cognitive 55) · ×1
  • shell-build.validateShellManifest (cognitive 55) packages/0-config/tsdown/shell-build.ts:416 — shell-build.validateShellManifest has cognitive complexity 55 (threshold 15). Drivers by points: if/else 16 (40 pts), loops 10 (12 pts), boolean chains 3 (nesting depth added 26). Of this number, 54 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.readModelField (cognitive 53) · ×1
  • interpreter.readModelField (cognitive 53) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:1024 — interpreter.readModelField has cognitive complexity 53 (threshold 15). Drivers by points: if/else 18 (28 pts), boolean chains 10, ternaries 6 (10 pts), loops 2 (3 pts), match/switch 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · emit.walkRegion (cognitive 51) · ×1
  • emit.walkRegion (cognitive 51) packages/1-framework/2-authoring/psl-parser/src/format/emit.ts:457 — emit.walkRegion has cognitive complexity 51 (threshold 15). Drivers by points: if/else 18 (44 pts), boolean chains 6, loops 1 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · db-run.executeRun (cognitive 51) · ×1
  • db-run.executeRun (cognitive 51) packages/1-framework/3-tooling/cli/src/control-api/operations/db-run.ts:195 — db-run.executeRun has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 17 (24 pts), if/else 17 (22 pts), boolean chains 5 (nesting depth added 12). Of this number, 43 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · schema-to-view.collectionToSchemaNode (cognitive 51) · ×1
  • schema-to-view.collectionToSchemaNode (cognitive 51) packages/2-mongo-family/9-family/src/core/schema-to-view.ts:22 — schema-to-view.collectionToSchemaNode has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (24 pts), ternaries 6 (13 pts), loops 5 (12 pts), boolean chains 2 (nesting depth added 25). Of this number, 46 points are the body's own statements and 5 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · review-artifacts.normalizeReviewStateV2 (cognitive 51) · ×1
  • review-artifacts.normalizeReviewStateV2 (cognitive 51) skills-contrib/review-fetch-phase/scripts/review-artifacts.mjs:194 — review-artifacts.normalizeReviewStateV2 has cognitive complexity 51 (threshold 15). Drivers by points: ternaries 19 (28 pts), if/else 6 (13 pts), boolean chains 5, loops 4 (5 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-check.checkSingleTarget (cognitive 50) · ×1
  • migration-check.checkSingleTarget (cognitive 50) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-check.ts:476 — migration-check.checkSingleTarget has cognitive complexity 50 (threshold 15). Drivers by points: if/else 20 (38 pts), loops 3 (6 pts), boolean chains 4, ternaries 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migrate.createMigrateCommand (cognitive 48) · ×1
  • migrate.createMigrateCommand (cognitive 48) packages/1-framework/3-tooling/cli/src/orm/migrate.ts:245 — migrate.createMigrateCommand has cognitive complexity 48 (threshold 15). Drivers by points: if/else 17 (25 pts), ternaries 9 (14 pts), error handling 3 (5 pts), boolean chains 4 (nesting depth added 15). None of this is in the body itself: all 48 points belong to one function literal inside it that branches (line 282). 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.
D2 · Cognitive Complexity · validators.validateRelationJoinFields (cognitive 47) · ×1
  • validators.validateRelationJoinFields (cognitive 47) packages/2-sql-family/1-core/contract/src/validators.ts:934 — validators.validateRelationJoinFields has cognitive complexity 47 (threshold 15). Drivers by points: if/else 6 (28 pts), loops 6 (19 pts) (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · psl-relation-resolution.applyBackrelationCandidates (cognitive 47) · ×1
  • psl-relation-resolution.applyBackrelationCandidates (cognitive 47) packages/2-sql-family/2-authoring/contract-psl/src/psl-relation-resolution.ts:395 — psl-relation-resolution.applyBackrelationCandidates has cognitive complexity 47 (threshold 15). Drivers by points: if/else 12 (35 pts), ternaries 3 (7 pts), boolean chains 4, loops 1 (nesting depth added 27). Of this number, 39 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.
D2 · Cognitive Complexity · value-object-default.valueObjectDefaultMismatches (cognitive 45) · ×1
  • value-object-default.valueObjectDefaultMismatches (cognitive 45) packages/2-sql-family/2-authoring/contract-psl/src/value-object-default.ts:86 — value-object-default.valueObjectDefaultMismatches has cognitive complexity 45 (threshold 15). Drivers by points: if/else 22 (33 pts), loops 4 (6 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 14). Most of this is not in the body itself: 15 of the 45 points are its own statements and the rest belongs to 3 function items inside it that branch (checkMember, checkOne, checkObject). 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.
D2 · Cognitive Complexity · coverage-report.formatCoverageReport (cognitive 45) · ×1
  • coverage-report.formatCoverageReport (cognitive 45) scripts/coverage-report.mjs:305 — coverage-report.formatCoverageReport has cognitive complexity 45 (threshold 15). Drivers by points: if/else 17 (32 pts), loops 5 (11 pts), boolean chains 2 (nesting depth added 21). Of this number, 43 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MongoMigrationRunner.apply (cognitive 44) · ×1
  • MongoMigrationRunner.apply (cognitive 44) packages/3-targets/mongo/1-target/src/core/migrations/mongo-runner.ts:248 — MongoMigrationRunner.apply has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (34 pts), ternaries 2 (4 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · control-instance.createSqlFamilyInstance.verify (cognitive 43) · ×1
  • control-instance.createSqlFamilyInstance.verify (cognitive 43) packages/2-sql-family/9-family/src/core/control-instance.ts:745 — control-instance.createSqlFamilyInstance.verify has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 19 (34 pts), if/else 7 (8 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · createCrossDomainRules (cognitive 42) · ×1
  • createCrossDomainRules (cognitive 42) dependency-cruiser.config.mjs:118 — createCrossDomainRules has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (29 pts), loops 4 (8 pts), boolean chains 5 (nesting depth added 24). Of this number, 39 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.
D2 · Cognitive Complexity · unfilled-placeholders.tokenize (cognitive 41) · ×1
  • unfilled-placeholders.tokenize (cognitive 41) packages/1-framework/3-tooling/cli/src/control-api/operations/unfilled-placeholders.ts:91 — unfilled-placeholders.tokenize has cognitive complexity 41 (threshold 15). Drivers by points: if/else 15 (27 pts), loops 4 (8 pts), boolean chains 6 (nesting depth added 16). Of this number, 34 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · io.readMigrationsDir (cognitive 41) · ×1
  • io.readMigrationsDir (cognitive 41) packages/1-framework/3-tooling/migration/src/io.ts:395 — io.readMigrationsDir has cognitive complexity 41 (threshold 15). Drivers by points: if/else 7 (25 pts), ternaries 2 (10 pts), error handling 3 (5 pts), loops 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-to-postgres-database-schema-node.contractToPostgresDatabaseSchemaNode (cognitive 41) · ×1
  • contract-to-postgres-database-schema-node.contractToPostgresDatabaseSchemaNode (cognitive 41) packages/3-targets/postgres/1-target/src/core/migrations/contract-to-postgres-database-schema-node.ts:99 — contract-to-postgres-database-schema-node.contractToPostgresDatabaseSchemaNode has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 6 (11 pts), ternaries 3 (9 pts), boolean chains 1 (nesting depth added 23). Of this number, 34 points are the body's own statements and 7 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · re-emit-mti-variant-link-columns.contractNeedsMtiLinkColumns (cognitive 41) · ×1
  • re-emit-mti-variant-link-columns.contractNeedsMtiLinkColumns (cognitive 41) skills/prisma-8/upgrading/app/upgrades/0.12-to-0.13/re-emit-mti-variant-link-columns.ts:96 — re-emit-mti-variant-link-columns.contractNeedsMtiLinkColumns has cognitive complexity 41 (threshold 15). Drivers by points: if/else 13 (31 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (3 pts), error handling 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stored-inet.readIpv6 (cognitive 40) · ×1
  • stored-inet.readIpv6 (cognitive 40) packages/3-targets/postgres/1-target/src/core/stored-inet.ts:127 — stored-inet.readIpv6 has cognitive complexity 40 (threshold 15). Drivers by points: if/else 16 (36 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · review-artifacts.assertReviewStateV2 (cognitive 40) · ×1
  • review-artifacts.assertReviewStateV2 (cognitive 40) skills-contrib/review-fetch-phase/scripts/review-artifacts.mjs:420 — review-artifacts.assertReviewStateV2 has cognitive complexity 40 (threshold 15). Drivers by points: if/else 20 (31 pts), loops 5 (6 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migrate.executeMigrate (cognitive 39) · ×1
  • migrate.executeMigrate (cognitive 39) packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts:141 — migrate.executeMigrate has cognitive complexity 39 (threshold 15). Drivers by points: if/else 16 (24 pts), ternaries 5 (11 pts), boolean chains 3, loops 1 (nesting depth added 14). Of this number, 30 points are the body's own statements and 9 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-lowering.resolveRelationForeignKeys (cognitive 39) · ×1
  • contract-lowering.resolveRelationForeignKeys (cognitive 39) packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts:275 — contract-lowering.resolveRelationForeignKeys has cognitive complexity 39 (threshold 15). Drivers by points: ternaries 12 (31 pts), if/else 3 (6 pts), boolean chains 1, loops 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · generator-functions.assembleGeneratorFunctions (cognitive 38) · ×1
  • generator-functions.assembleGeneratorFunctions (cognitive 38) packages/1-framework/1-core/framework-components/src/shared/generator-functions.ts:146 — generator-functions.assembleGeneratorFunctions has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (23 pts), loops 7 (14 pts), boolean chains 1 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · init.createInitCommand (cognitive 38) · ×1
  • init.createInitCommand (cognitive 38) packages/1-framework/3-tooling/cli/src/orm/init.ts:82 — init.createInitCommand has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 12 (13 pts), loops 5 (7 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 9). None of this is in the body itself: all 38 points belong to 2 function literals inside it that branch (lines 148, 267). 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.
D2 · Cognitive Complexity · migration-list-graph-topology.classifyNormalizedEdges (cognitive 38) · ×1
  • migration-list-graph-topology.classifyNormalizedEdges (cognitive 38) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-list-graph-topology.ts:177 — migration-list-graph-topology.classifyNormalizedEdges has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (25 pts), loops 11 (12 pts), boolean chains 1 (nesting depth added 11). Of this number, 21 points are the body's own statements and 17 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.
D2 · Cognitive Complexity · migration-graph-rows.layerNodesByLongestForwardPath (cognitive 38) · ×1
  • migration-graph-rows.layerNodesByLongestForwardPath (cognitive 38) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-rows.ts:184 — migration-graph-rows.layerNodesByLongestForwardPath has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 8 (12 pts), boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · sql-expression-text.checkSqlExpressionText (cognitive 38) · ×1
  • sql-expression-text.checkSqlExpressionText (cognitive 38) packages/2-sql-family/9-family/src/core/migrations/sql-expression-text.ts:68 — sql-expression-text.checkSqlExpressionText has cognitive complexity 38 (threshold 15). Drivers by points: if/else 12 (27 pts), boolean chains 7, ternaries 2 (3 pts), loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · infer-psl-contract.inferPostgresPslContract (cognitive 38) · ×1
  • infer-psl-contract.inferPostgresPslContract (cognitive 38) packages/3-targets/postgres/1-target/src/core/psl-infer/infer-psl-contract.ts:82 — infer-psl-contract.inferPostgresPslContract has cognitive complexity 38 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 5 (9 pts), ternaries 2 (5 pts), boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · sign.createDbSignCommand (cognitive 37) · ×1
  • sign.createDbSignCommand (cognitive 37) packages/1-framework/3-tooling/cli/src/orm/db/sign.ts:443 — sign.createDbSignCommand has cognitive complexity 37 (threshold 15). Drivers by points: if/else 16 (23 pts), ternaries 6 (8 pts), boolean chains 2, loops 1 (2 pts), error handling 1, match/switch 1 (nesting depth added 10). None of this is in the body itself: all 37 points belong to 3 function literals inside it that branch (lines 496, 646, 674). 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.
D2 · Cognitive Complexity · field-event-planner.planFieldEventCalls (cognitive 37) · ×1
  • field-event-planner.planFieldEventCalls (cognitive 37) packages/2-sql-family/9-family/src/core/migrations/field-event-planner.ts:95 — field-event-planner.planFieldEventCalls has cognitive complexity 37 (threshold 15). Drivers by points: ternaries 7 (17 pts), if/else 4 (11 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · derive-json-schema.fieldToBsonSchema (cognitive 36) · ×1
  • derive-json-schema.fieldToBsonSchema (cognitive 36) packages/2-mongo-family/1-foundation/mongo-contract/src/derive-json-schema.ts:130 — derive-json-schema.fieldToBsonSchema has cognitive complexity 36 (threshold 15). Drivers by points: if/else 11 (22 pts), ternaries 5 (14 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · sql-context.assertColumnCodecIntegrity (cognitive 36) · ×1
  • sql-context.assertColumnCodecIntegrity (cognitive 36) packages/2-sql-family/5-runtime/src/sql-context.ts:326 — sql-context.assertColumnCodecIntegrity has cognitive complexity 36 (threshold 15). Drivers by points: if/else 6 (26 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolve-statements.readSide (cognitive 35) · ×1
  • resolve-statements.readSide (cognitive 35) packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:681 — resolve-statements.readSide has cognitive complexity 35 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 9, ternaries 7 (9 pts) (nesting depth added 7). Of this number, 34 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · completion-scope.scopeCompletionItems (cognitive 35) · ×1
  • completion-scope.scopeCompletionItems (cognitive 35) packages/1-framework/3-tooling/language-server/src/completion-scope.ts:37 — completion-scope.scopeCompletionItems has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (26 pts), boolean chains 6, match/switch 1 (2 pts), loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · infer-foreign-keys.resolveForeignKeys (cognitive 35) · ×1
  • infer-foreign-keys.resolveForeignKeys (cognitive 35) packages/3-targets/postgres/1-target/src/core/psl-infer/infer-foreign-keys.ts:126 — infer-foreign-keys.resolveForeignKeys has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (32 pts), loops 2 (3 pts) (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migrate-migrations-layout.applyMigrationsRootPlan (cognitive 35) · ×1
  • migrate-migrations-layout.applyMigrationsRootPlan (cognitive 35) scripts/migrate-migrations-layout.mjs:514 — migrate-migrations-layout.applyMigrationsRootPlan has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 4 (10 pts), loops 6 (9 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolve-statements.resolveFieldStatement (cognitive 34) · ×1
  • resolve-statements.resolveFieldStatement (cognitive 34) packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:1687 — resolve-statements.resolveFieldStatement has cognitive complexity 34 (threshold 15). Drivers by points: if/else 15 (20 pts), ternaries 6 (10 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · migration-graph.findPathWithDecision (cognitive 34) · ×1
  • migration-graph.findPathWithDecision (cognitive 34) packages/1-framework/3-tooling/migration/src/migration-graph.ts:289 — migration-graph.findPathWithDecision has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · build-contract.buildSqlContractFromDefinition (cognitive 34) · ×1
  • build-contract.buildSqlContractFromDefinition (cognitive 34) packages/2-sql-family/2-authoring/contract-ts/src/build-contract.ts:294 — build-contract.buildSqlContractFromDefinition has cognitive complexity 34 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 11, boolean chains 6, loops 5 (6 pts) (nesting depth added 6). Of this number, 24 points are the body's own statements and 10 belong to 3 function literals inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · contract-lowering.lowerPackEntityHandles (cognitive 34) · ×1
  • contract-lowering.lowerPackEntityHandles (cognitive 34) packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts:1213 — contract-lowering.lowerPackEntityHandles has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (19 pts), loops 7 (9 pts), boolean chains 5, ternaries 1 (nesting depth added 9). Of this number, 20 points are the body's own statements and 14 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index-and-check-renames.pairIndexRenames (cognitive 34) · ×1
  • index-and-check-renames.pairIndexRenames (cognitive 34) packages/3-targets/postgres/1-target/src/core/migrations/index-and-check-renames.ts:32 — index-and-check-renames.pairIndexRenames has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 5, boolean chains 4, ternaries 3 (4 pts) (nesting depth added 10). Of this number, 29 points are the body's own statements and 5 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · authoring-type-choice.assertTypeChoiceValid (cognitive 33) · ×1
  • authoring-type-choice.assertTypeChoiceValid (cognitive 33) packages/1-framework/1-core/framework-components/src/shared/authoring-type-choice.ts:325 — authoring-type-choice.assertTypeChoiceValid has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (22 pts), loops 4 (6 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 15). Of this number, 26 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · data-type-support.enforceDataTypeAssemblyInvariants (cognitive 33) · ×1
  • data-type-support.enforceDataTypeAssemblyInvariants (cognitive 33) packages/1-framework/1-core/framework-components/src/shared/data-type-support.ts:198 — data-type-support.enforceDataTypeAssemblyInvariants has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 7 (10 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.readRelationFields (cognitive 33) · ×1
  • interpreter.readRelationFields (cognitive 33) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:1350 — interpreter.readRelationFields has cognitive complexity 33 (threshold 15). Drivers by points: if/else 9 (18 pts), ternaries 4 (10 pts), boolean chains 4, loops 1 (nesting depth added 15). Of this number, 31 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.collectIndexes (cognitive 33) · ×1
  • interpreter.collectIndexes (cognitive 33) packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:598 — interpreter.collectIndexes has cognitive complexity 33 (threshold 15). Drivers by points: if/else 12 (25 pts), boolean chains 3, ternaries 1 (3 pts), loops 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · control-instance.assertPackEntitiesDeclaredOnce (cognitive 33) · ×1
  • control-instance.assertPackEntitiesDeclaredOnce (cognitive 33) packages/2-sql-family/9-family/src/core/control-instance.ts:468 — control-instance.assertPackEntitiesDeclaredOnce has cognitive complexity 33 (threshold 15). Drivers by points: if/else 5 (21 pts), loops 4 (10 pts), boolean chains 2 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · query-plan-select.buildIncludeChildScalarSelect (cognitive 33) · ×1
  • query-plan-select.buildIncludeChildScalarSelect (cognitive 33) packages/3-extensions/sql-orm-client/src/query-plan-select.ts:907 — query-plan-select.buildIncludeChildScalarSelect has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 12, ternaries 4 (5 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · shell-testkit.findInternalNames (cognitive 32) · ×1
  • shell-testkit.findInternalNames (cognitive 32) packages/0-config/tsdown/shell-testkit.ts:411 — shell-testkit.findInternalNames has cognitive complexity 32 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 4 (11 pts), boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · order-issues-by-dependencies.orderIssuesByDependencies (cognitive 32) · ×1
  • order-issues-by-dependencies.orderIssuesByDependencies (cognitive 32) packages/1-framework/1-core/framework-components/src/control/order-issues-by-dependencies.ts:69 — order-issues-by-dependencies.orderIssuesByDependencies has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 8 (14 pts), boolean chains 1 (nesting depth added 12). Of this number, 28 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · contract-at-errors.mapContractAtError (cognitive 32) · ×1
  • contract-at-errors.mapContractAtError (cognitive 32) packages/1-framework/3-tooling/cli/src/control-api/operations/contract-at-errors.ts:12 — contract-at-errors.mapContractAtError has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 9 (28 pts), if/else 2, match/switch 1 (2 pts) (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · indexes.parseIndexAttribute (cognitive 32) · ×1
  • indexes.parseIndexAttribute (cognitive 32) packages/2-sql-family/2-authoring/contract-prisma7/src/indexes.ts:22 — indexes.parseIndexAttribute has cognitive complexity 32 (threshold 15). Drivers by points: if/else 5 (17 pts), ternaries 3 (8 pts), loops 2 (4 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · declared-indexes.declaredIndexes (cognitive 32) · ×1
  • declared-indexes.declaredIndexes (cognitive 32) packages/3-targets/mysql/2-adapter/src/core/migrations/declared-indexes.ts:19 — declared-indexes.declaredIndexes has cognitive complexity 32 (threshold 15). Drivers by points: if/else 2 (10 pts), loops 4 (10 pts), ternaries 3 (10 pts), boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · primary-key-change.primaryKeyChangeStrategy (cognitive 32) · ×1
  • primary-key-change.primaryKeyChangeStrategy (cognitive 32) packages/3-targets/postgres/1-target/src/core/migrations/primary-key-change.ts:236 — primary-key-change.primaryKeyChangeStrategy has cognitive complexity 32 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 3 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · planner-strategies.recreateTableStrategy (cognitive 32) · ×1
  • planner-strategies.recreateTableStrategy (cognitive 32) packages/3-targets/sqlite/1-target/src/core/migrations/planner-strategies.ts:256 — planner-strategies.recreateTableStrategy has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (21 pts), ternaries 2 (5 pts), boolean chains 3, loops 3 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · control-stack.extractCodecLookup (cognitive 31) · ×1
  • control-stack.extractCodecLookup (cognitive 31) packages/1-framework/1-core/framework-components/src/control/control-stack.ts:530 — control-stack.extractCodecLookup has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (23 pts), error handling 1 (5 pts), loops 2 (3 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · symbol-table.placeFields (cognitive 31) · ×1
  • symbol-table.placeFields (cognitive 31) packages/1-framework/2-authoring/psl-parser/src/symbol-table.ts:475 — symbol-table.placeFields has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (27 pts), loops 2 (4 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-graph-rows.weaklyConnectedComponents (cognitive 31) · ×1
  • migration-graph-rows.weaklyConnectedComponents (cognitive 31) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-rows.ts:58 — migration-graph-rows.weaklyConnectedComponents has cognitive complexity 31 (threshold 15). Drivers by points: if/else 13 (20 pts), loops 6 (8 pts), boolean chains 3 (nesting depth added 9). Most of this is not in the body itself: 12 of the 31 points are its own statements and the rest belongs to 4 function items inside it that branch (bfsComponent, addAdjacent, a function literal at line 119, …). 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.
D2 · Cognitive Complexity · sql-context.buildContractCodecRegistry (cognitive 31) · ×1
  • sql-context.buildContractCodecRegistry (cognitive 31) packages/2-sql-family/5-runtime/src/sql-context.ts:426 — sql-context.buildContractCodecRegistry has cognitive complexity 31 (threshold 15). Drivers by points: if/else 4 (13 pts), loops 6 (12 pts), ternaries 2 (6 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · infer-model-blocks.buildModel (cognitive 31) · ×1
  • infer-model-blocks.buildModel (cognitive 31) packages/3-targets/postgres/1-target/src/core/psl-infer/infer-model-blocks.ts:53 — infer-model-blocks.buildModel has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 6, ternaries 4, boolean chains 3 (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.
D2 · Cognitive Complexity · binder.bindInclusions (cognitive 30) · ×1
  • binder.bindInclusions (cognitive 30) packages/1-framework/2-authoring/psl-parser/src/binder.ts:576 — binder.bindInclusions has cognitive complexity 30 (threshold 15). Drivers by points: if/else 4 (12 pts), ternaries 4 (11 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · planner.planMigration (cognitive 30) · ×1
  • planner.planMigration (cognitive 30) packages/1-framework/3-tooling/migration/src/aggregate/planner.ts:51 — planner.planMigration has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (20 pts), ternaries 3 (7 pts), boolean chains 2, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.resolveNonRelationField (cognitive 30) · ×1
  • interpreter.resolveNonRelationField (cognitive 30) packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:839 — interpreter.resolveNonRelationField has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 6 (12 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · validators.validateToOneRelationNullabilityAgainstStorage (cognitive 30) · ×1
  • validators.validateToOneRelationNullabilityAgainstStorage (cognitive 30) packages/2-sql-family/1-core/contract/src/validators.ts:1184 — validators.validateToOneRelationNullabilityAgainstStorage has cognitive complexity 30 (threshold 15). Drivers by points: if/else 4 (17 pts), loops 3 (6 pts), ternaries 1 (4 pts), boolean chains 3 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.resolveVariants (cognitive 30) · ×1
  • interpreter.resolveVariants (cognitive 30) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:1786 — interpreter.resolveVariants has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (22 pts), boolean chains 4, loops 3 (4 pts) (nesting depth added 14). Of this number, 29 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · model-accessor.createModelAccessorInScope (cognitive 30) · ×1
  • model-accessor.createModelAccessorInScope (cognitive 30) packages/3-extensions/sql-orm-client/src/model-accessor.ts:179 — model-accessor.createModelAccessorInScope has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (19 pts), ternaries 5, loops 2 (4 pts), boolean chains 2 (nesting depth added 9). Of this number, 29 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgresMigrationRunner.runExecuteSteps (cognitive 30) · ×1
  • PostgresMigrationRunner.runExecuteSteps (cognitive 30) packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:547 — PostgresMigrationRunner.runExecuteSteps has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 4 (16 pts), if/else 3 (10 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolve-statements.resolveStatements (cognitive 29) · ×1
  • resolve-statements.resolveStatements (cognitive 29) packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:1862 — resolve-statements.resolveStatements has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 3, boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · psl-relation-resolution.findJunctionFkPairs (cognitive 29) · ×1
  • psl-relation-resolution.findJunctionFkPairs (cognitive 29) packages/2-sql-family/2-authoring/contract-psl/src/psl-relation-resolution.ts:256 — psl-relation-resolution.findJunctionFkPairs has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (19 pts), loops 3 (6 pts), boolean chains 4 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-object-field-fills.requiredFields (cognitive 29) · ×1
  • value-object-field-fills.requiredFields (cognitive 29) packages/2-sql-family/9-family/src/core/migrations/value-object-field-fills.ts:131 — value-object-field-fills.requiredFields has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 2 (6 pts), loops 3 (4 pts), boolean chains 3 (nesting depth added 14). Of this number, 28 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgresMigrationRunner.runExpectationSteps (cognitive 29) · ×1
  • PostgresMigrationRunner.runExpectationSteps (cognitive 29) packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:410 — PostgresMigrationRunner.runExpectationSteps has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 6 (19 pts), if/else 3 (8 pts), boolean chains 1, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validate-domain.validateVariantsAndBases (cognitive 28) · ×1
  • validate-domain.validateVariantsAndBases (cognitive 28) packages/1-framework/0-foundation/contract/src/validate-domain.ts:128 — validate-domain.validateVariantsAndBases has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · written-value.readWrittenValueIntoCodec (cognitive 28) · ×1
  • written-value.readWrittenValueIntoCodec (cognitive 28) packages/1-framework/1-core/framework-components/src/shared/written-value.ts:369 — written-value.readWrittenValueIntoCodec has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (21 pts), error handling 2 (3 pts), loops 1 (2 pts), ternaries 2 (nesting depth added 12). Of this number, 24 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · date-time-stored-form.dateTimeStoredText (cognitive 28) · ×1
  • date-time-stored-form.dateTimeStoredText (cognitive 28) packages/1-framework/1-core/framework-components/src/shared/date-time-stored-form.ts:302 — date-time-stored-form.dateTimeStoredText has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 12, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · plan-questions.dataLossQuestion (cognitive 28) · ×1
  • plan-questions.dataLossQuestion (cognitive 28) packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts:654 — plan-questions.dataLossQuestion has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 10 (13 pts), if/else 7 (12 pts), boolean chains 3 (nesting depth added 8). Of this number, 16 points are the body's own statements and 12 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.
D2 · Cognitive Complexity · update.createDbUpdateCommand (cognitive 28) · ×1
  • update.createDbUpdateCommand (cognitive 28) packages/1-framework/3-tooling/cli/src/orm/db/update.ts:254 — update.createDbUpdateCommand has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (15 pts), ternaries 9 (10 pts), boolean chains 2, error handling 1 (nesting depth added 5). None of this is in the body itself: all 28 points belong to 4 function literals inside it that branch (lines 290, 294, 301, …). 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.
D2 · Cognitive Complexity · index-equivalence.deepEqual (cognitive 28) · ×1
  • index-equivalence.deepEqual (cognitive 28) packages/2-mongo-family/3-tooling/mongo-schema-ir/src/index-equivalence.ts:5 — index-equivalence.deepEqual has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (21 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-warnings.emitTypedCrossModelFallbackWarnings (cognitive 28) · ×1
  • contract-warnings.emitTypedCrossModelFallbackWarnings (cognitive 28) packages/2-sql-family/2-authoring/contract-ts/src/contract-warnings.ts:132 — contract-warnings.emitTypedCrossModelFallbackWarnings has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · sql-runtime.withTransaction (cognitive 28) · ×1
  • sql-runtime.withTransaction (cognitive 28) packages/2-sql-family/5-runtime/src/sql-runtime.ts:1802 — sql-runtime.withTransaction has cognitive complexity 28 (threshold 15). Drivers by points: if/else 13 (20 pts), error handling 5 (7 pts), loops 1 (nesting depth added 9). Of this number, 20 points are the body's own statements and 8 belong to 4 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · control-instance.extractCodecTypeIdsFromContract (cognitive 28) · ×1
  • control-instance.extractCodecTypeIdsFromContract (cognitive 28) packages/2-sql-family/9-family/src/core/control-instance.ts:95 — control-instance.extractCodecTypeIdsFromContract has cognitive complexity 28 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 3 (10 pts), boolean chains 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mongo-planner.planCollectionDiff (cognitive 28) · ×1
  • mongo-planner.planCollectionDiff (cognitive 28) packages/3-targets/mongo/1-target/src/core/migrations/mongo-planner.ts:300 — mongo-planner.planCollectionDiff has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 4 (6 pts), ternaries 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · infer-policy-blocks.buildIntrospectedPolicyBlocks (cognitive 28) · ×1
  • infer-policy-blocks.buildIntrospectedPolicyBlocks (cognitive 28) packages/3-targets/postgres/1-target/src/core/psl-infer/infer-policy-blocks.ts:34 — infer-policy-blocks.buildIntrospectedPolicyBlocks has cognitive complexity 28 (threshold 15). Drivers by points: ternaries 7 (13 pts), if/else 5 (8 pts), loops 4 (7 pts) (nesting depth added 12). Of this number, 19 points are the body's own statements and 9 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.
D2 · Cognitive Complexity · SqliteControlAdapter.introspect (cognitive 28) · ×1
  • SqliteControlAdapter.introspect (cognitive 28) packages/3-targets/sqlite/2-adapter/src/core/control-adapter.ts:574 — SqliteControlAdapter.introspect has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 3 (9 pts), loops 4 (7 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · createPlaneRules (cognitive 28) · ×1
  • createPlaneRules (cognitive 28) dependency-cruiser.config.mjs:201 — createPlaneRules has cognitive complexity 28 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 4 (10 pts), boolean chains 2 (nesting depth added 17). Of this number, 27 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · control-stack.buildExtensionLoadOrder (cognitive 27) · ×1
  • control-stack.buildExtensionLoadOrder (cognitive 27) packages/1-framework/1-core/framework-components/src/control/control-stack.ts:651 — control-stack.buildExtensionLoadOrder has cognitive complexity 27 (threshold 15). Drivers by points: if/else 9 (19 pts), loops 6 (8 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-graph-grid-layout.buildGrid · ×1
  • migration-graph-grid-layout.buildGrid::emitConnectorRow (cognitive 27) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts:800 — migration-graph-grid-layout.buildGrid::emitConnectorRow has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 5 (8 pts), loops 4 (6 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (migration-graph-grid-layout.buildGrid) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · contract-ref.parseContractRef (cognitive 27) · ×1
  • contract-ref.parseContractRef (cognitive 27) packages/1-framework/3-tooling/migration/src/refs/contract-ref.ts:52 — contract-ref.parseContractRef has cognitive complexity 27 (threshold 15). Drivers by points: if/else 18 (24 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · plugin.prismaVitePlugin.resolveWatchedFiles (cognitive 27) · ×1
  • plugin.prismaVitePlugin.resolveWatchedFiles (cognitive 27) packages/1-framework/3-tooling/vite-plugin-contract-emit/src/plugin.ts:295 — plugin.prismaVitePlugin.resolveWatchedFiles has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 4 (6 pts), ternaries 2 (6 pts), error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · enum-value-planning.columnsTypedBy (cognitive 27) · ×1
  • enum-value-planning.columnsTypedBy (cognitive 27) packages/2-sql-family/9-family/src/core/migrations/enum-value-planning.ts:93 — enum-value-planning.columnsTypedBy has cognitive complexity 27 (threshold 15). Drivers by points: if/else 5 (19 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mongo-statement-planning.planStatements (cognitive 27) · ×1
  • mongo-statement-planning.planStatements (cognitive 27) packages/3-targets/mongo/1-target/src/core/migrations/mongo-statement-planning.ts:349 — mongo-statement-planning.planStatements has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 6 (17 pts), if/else 4 (9 pts), loops 1 (nesting depth added 16). 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.
D2 · Cognitive Complexity · MongoMigrationRunner.executeDmlOperation (cognitive 27) · ×1
  • MongoMigrationRunner.executeDmlOperation (cognitive 27) packages/3-targets/mongo/1-target/src/core/migrations/mongo-runner.ts:477 — MongoMigrationRunner.executeDmlOperation has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 4, loops 2 (3 pts), error handling 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · authoring.postgresLowerEntityHandles (cognitive 27) · ×1
  • authoring.postgresLowerEntityHandles (cognitive 27) packages/3-targets/postgres/1-target/src/core/authoring.ts:904 — authoring.postgresLowerEntityHandles has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 5, ternaries 1 (4 pts), match/switch 1 (2 pts) (nesting depth added 14). Of this number, 23 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · SqliteMigrationRunner.runExpectationSteps (cognitive 27) · ×1
  • SqliteMigrationRunner.runExpectationSteps (cognitive 27) packages/3-targets/sqlite/1-target/src/core/migrations/runner.ts:400 — SqliteMigrationRunner.runExpectationSteps has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 6 (19 pts), if/else 2 (5 pts), boolean chains 2, loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · check-upgrade-coverage.runCheck (cognitive 27) · ×1
  • check-upgrade-coverage.runCheck (cognitive 27) REDACTED:278 — check-upgrade-coverage.runCheck has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 7, if/else 5 (7 pts), loops 4 (7 pts), ternaries 6 (nesting depth added 5). Of this number, 23 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · contract-snapshot-resolution.resolveContractRefToSnapshot (cognitive 26) · ×1
  • contract-snapshot-resolution.resolveContractRefToSnapshot (cognitive 26) packages/1-framework/3-tooling/cli/src/control-api/operations/contract-snapshot-resolution.ts:85 — contract-snapshot-resolution.resolveContractRefToSnapshot has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 4 (8 pts), error handling 3, boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · init-scaffold.scaffoldProject (cognitive 26) · ×1
  • init-scaffold.scaffoldProject (cognitive 26) packages/1-framework/3-tooling/cli/src/orm/init-scaffold.ts:466 — init-scaffold.scaffoldProject has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 3 (8 pts), if/else 3 (7 pts), error handling 3 (6 pts), loops 4, boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-new.executeMigrationNewCommand (cognitive 26) · ×1
  • migration-new.executeMigrationNewCommand (cognitive 26) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-new.ts:62 — migration-new.executeMigrationNewCommand has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (19 pts), error handling 3, 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.
D2 · Cognitive Complexity · model-types-emission.generateModelTypesBlock (cognitive 26) · ×1
  • model-types-emission.generateModelTypesBlock (cognitive 26) packages/1-framework/3-tooling/emitter/src/model-types-emission.ts:279 — model-types-emission.generateModelTypesBlock has cognitive complexity 26 (threshold 15). Drivers by points: loops 7 (11 pts), if/else 3 (8 pts), ternaries 4 (7 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · completion-values.valueItems (cognitive 26) · ×1
  • completion-values.valueItems (cognitive 26) packages/1-framework/3-tooling/language-server/src/completion-values.ts:109 — completion-values.valueItems has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 6, boolean chains 5, match/switch 1 (nesting depth added 7). Of this number, 24 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.
D2 · Cognitive Complexity · migration-graph.findPathWithInvariants (cognitive 26) · ×1
  • migration-graph.findPathWithInvariants (cognitive 26) packages/1-framework/3-tooling/migration/src/migration-graph.ts:141 — migration-graph.findPathWithInvariants has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 3 (5 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 11). Of this number, 15 points are the body's own statements and 11 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · refusal-diagnostics.refusalDiagnostic (cognitive 26) · ×1
  • refusal-diagnostics.refusalDiagnostic (cognitive 26) packages/2-mongo-family/2-authoring/contract-psl/src/refusal-diagnostics.ts:213 — refusal-diagnostics.refusalDiagnostic has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (18 pts), match/switch 3 (5 pts), ternaries 1 (3 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · index-naming.lowerAuthoredIndex (cognitive 26) · ×1
  • index-naming.lowerAuthoredIndex (cognitive 26) packages/2-sql-family/1-core/contract/src/index-naming.ts:138 — index-naming.lowerAuthoredIndex has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (11 pts), boolean chains 10, ternaries 3 (5 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validators.validateTableScopedEntryNames (cognitive 26) · ×1
  • validators.validateTableScopedEntryNames (cognitive 26) packages/2-sql-family/1-core/contract/src/validators.ts:340 — validators.validateTableScopedEntryNames has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (17 pts), loops 3 (6 pts), boolean chains 3 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · data-type-default.readDataTypeDefault (cognitive 26) · ×1
  • data-type-default.readDataTypeDefault (cognitive 26) packages/2-sql-family/2-authoring/contract-psl/src/data-type-default.ts:269 — data-type-default.readDataTypeDefault has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 3 (8 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 13). Of this number, 22 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.
D2 · Cognitive Complexity · stored-inet.readIpv4 (cognitive 26) · ×1
  • stored-inet.readIpv4 (cognitive 26) packages/3-targets/postgres/1-target/src/core/stored-inet.ts:42 — stored-inet.readIpv4 has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 3 (5 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · index-and-check-renames.pairCheckRenames (cognitive 26) · ×1
  • index-and-check-renames.pairCheckRenames (cognitive 26) packages/3-targets/postgres/1-target/src/core/migrations/index-and-check-renames.ts:152 — index-and-check-renames.pairCheckRenames has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (15 pts), loops 4, ternaries 3 (4 pts), boolean chains 3 (nesting depth added 7). Of this number, 22 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · check-catalogue-links.main (cognitive 26) · ×1
  • check-catalogue-links.main (cognitive 26) scripts/check-catalogue-links.mjs:104 — check-catalogue-links.main has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 6 (10 pts), ternaries 1 (4 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mongo-field-storage-names.main (cognitive 26) · ×1
  • mongo-field-storage-names.main (cognitive 26) REDACTED:186 — mongo-field-storage-names.main has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 4 (5 pts), ternaries 3 (5 pts), error handling 2 (4 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.
D2 · Cognitive Complexity · control-stack.assembleAuthoringContributions (cognitive 25) · ×1
  • control-stack.assembleAuthoringContributions (cognitive 25) packages/1-framework/1-core/framework-components/src/control/control-stack.ts:218 — control-stack.assembleAuthoringContributions has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (20 pts), loops 3, boolean chains 1, ternaries 1 (nesting depth added 10). Of this number, 22 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · verify.createDbVerifyCommand (cognitive 25) · ×1
  • verify.createDbVerifyCommand (cognitive 25) packages/1-framework/3-tooling/cli/src/orm/db/verify.ts:363 — verify.createDbVerifyCommand has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 6 (12 pts), if/else 10 (11 pts), boolean chains 1, error handling 1 (nesting depth added 7). None of this is in the body itself: all 25 points belong to one function literal inside it that branches (line 404). 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.
D2 · Cognitive Complexity · migration-graph-sections.buildMigrationGraphTreeSections (cognitive 25) · ×1
  • migration-graph-sections.buildMigrationGraphTreeSections (cognitive 25) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-sections.ts:25 — migration-graph-sections.buildMigrationGraphTreeSections has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 10 (21 pts), if/else 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 12). Of this number, 23 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.
D2 · Cognitive Complexity · domain-type-generation.generateModelRelationsType (cognitive 25) · ×1
  • domain-type-generation.generateModelRelationsType (cognitive 25) packages/1-framework/3-tooling/emitter/src/domain-type-generation.ts:128 — domain-type-generation.generateModelRelationsType has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (19 pts), boolean chains 5, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · completion-context.classifyAttributeExpression (cognitive 25) · ×1
  • completion-context.classifyAttributeExpression (cognitive 25) packages/1-framework/3-tooling/language-server/src/completion-context.ts:780 — completion-context.classifyAttributeExpression has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 4 (9 pts), boolean chains 4 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.buildIndexes (cognitive 25) · ×1
  • interpreter.buildIndexes (cognitive 25) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:1516 — interpreter.buildIndexes has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 3 (6 pts), boolean chains 1, loops 1 (nesting depth added 12). Of this number, 24 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · build-execution-defaults.buildExecutionDefaults (cognitive 25) · ×1
  • build-execution-defaults.buildExecutionDefaults (cognitive 25) packages/2-mongo-family/2-authoring/contract-ts/src/build-execution-defaults.ts:112 — build-execution-defaults.buildExecutionDefaults has cognitive complexity 25 (threshold 15). Drivers by points: if/else 7 (22 pts), loops 2 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · decoding.decodeMongoRow · ×1
  • decoding.decodeMongoRow::walkField (cognitive 25) packages/2-mongo-family/7-runtime/src/codecs/decoding.ts:129 — decoding.decodeMongoRow::walkField has cognitive complexity 25 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (6 pts), boolean chains 4, loops 2 (4 pts), match/switch 1 (nesting depth added 11). 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.
D2 · Cognitive Complexity · psl-column-resolution.resolveFieldTypeDescriptor (cognitive 25) · ×1
  • psl-column-resolution.resolveFieldTypeDescriptor (cognitive 25) packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts:458 — psl-column-resolution.resolveFieldTypeDescriptor has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 3 (7 pts), match/switch 2, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-lowering.resolveModelNode (cognitive 25) · ×1
  • contract-lowering.resolveModelNode (cognitive 25) packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts:949 — contract-lowering.resolveModelNode has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 16 (21 pts), if/else 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). Of this number, 21 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · cache-store.copyObject (cognitive 25) · ×1
  • cache-store.copyObject (cognitive 25) REDACTED:119 — cache-store.copyObject has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 7, loops 4 (7 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · default-normalizer.splitArrayElements (cognitive 25) · ×1
  • default-normalizer.splitArrayElements (cognitive 25) packages/3-targets/postgres/1-target/src/core/default-normalizer.ts:155 — default-normalizer.splitArrayElements has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (23 pts), boolean chains 1, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · planner-strategies.typeChangeCallStrategy (cognitive 25) · ×1
  • planner-strategies.typeChangeCallStrategy (cognitive 25) packages/3-targets/postgres/1-target/src/core/migrations/planner-strategies.ts:301 — planner-strategies.typeChangeCallStrategy has cognitive complexity 25 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 2 (5 pts), boolean chains 3, loops 1 (nesting depth added 10). Of this number, 24 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · summarize-review-state.parseCliArgs (cognitive 25) · ×1
  • summarize-review-state.parseCliArgs (cognitive 25) skills-contrib/review-fetch-phase/scripts/summarize-review-state.mjs:30 — summarize-review-state.parseCliArgs has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (18 pts), boolean chains 6, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · post-review-thread-reply.parseCliArgs (cognitive 25) · ×1
  • post-review-thread-reply.parseCliArgs (cognitive 25) skills-contrib/review-implement-phase/scripts/post-review-thread-reply.mjs:13 — post-review-thread-reply.parseCliArgs has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (20 pts), boolean chains 4, 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.
D2 · Cognitive Complexity · indexes.parseIndexAttribute (cognitive 24) · ×1
  • indexes.parseIndexAttribute (cognitive 24) packages/2-mongo-family/2-authoring/contract-prisma6/src/indexes.ts:206 — indexes.parseIndexAttribute has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 4, ternaries 1 (2 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.generateTableLiteralType (cognitive 24) · ×1
  • index.generateTableLiteralType (cognitive 24) packages/2-sql-family/3-tooling/emitter/src/index.ts:396 — index.generateTableLiteralType has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 5 (11 pts), boolean chains 1, loops 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SelectAst.collectColumnRefs (cognitive 24) · ×1
  • SelectAst.collectColumnRefs (cognitive 24) packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:1839 — SelectAst.collectColumnRefs has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (14 pts), loops 7 (10 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · query-plan-aggregate.compileGroupedAggregate (cognitive 24) · ×1
  • query-plan-aggregate.compileGroupedAggregate (cognitive 24) packages/3-extensions/sql-orm-client/src/query-plan-aggregate.ts:283 — query-plan-aggregate.compileGroupedAggregate has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 7, ternaries 2 (4 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · planner-strategies.notNullAddColumnCallStrategy (cognitive 24) · ×1
  • planner-strategies.notNullAddColumnCallStrategy (cognitive 24) packages/3-targets/postgres/1-target/src/core/migrations/planner-strategies.ts:487 — planner-strategies.notNullAddColumnCallStrategy has cognitive complexity 24 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 6, ternaries 2 (4 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgresMigrationPlanner.planSql (cognitive 24) · ×1
  • PostgresMigrationPlanner.planSql (cognitive 24) packages/3-targets/postgres/1-target/src/core/migrations/planner.ts:265 — PostgresMigrationPlanner.planSql has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9, ternaries 8 (9 pts), boolean chains 6 (nesting depth added 1). Of this number, 15 points are the body's own statements and 9 belong to 6 function literals inside it that branch. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · model-attributes.buildModelAttributes (cognitive 24) · ×1
  • model-attributes.buildModelAttributes (cognitive 24) packages/3-targets/postgres/1-target/src/core/psl-print/model-attributes.ts:122 — model-attributes.buildModelAttributes has cognitive complexity 24 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 4, loops 3, ternaries 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · operation-subjects.sqliteCallSubjects (cognitive 24) · ×1
  • operation-subjects.sqliteCallSubjects (cognitive 24) packages/3-targets/sqlite/1-target/src/core/migrations/operation-subjects.ts:92 — operation-subjects.sqliteCallSubjects has cognitive complexity 24 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 8, boolean chains 3, loops 1 (2 pts) (nesting depth added 6). None of this is in the body itself: all 24 points belong to 2 function literals inside it that branch (lines 115, 103). 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.
D2 · Cognitive Complexity · framework-authoring.collectDescriptorEntries (cognitive 23) · ×1
  • framework-authoring.collectDescriptorEntries (cognitive 23) packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:1060 — framework-authoring.collectDescriptorEntries has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (17 pts), boolean chains 5, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · binder.bindBlock (cognitive 23) · ×1
  • binder.bindBlock (cognitive 23) packages/1-framework/2-authoring/psl-parser/src/binder.ts:643 — binder.bindBlock has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 2 (4 pts), boolean chains 2, loops 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · resolve-statements.resolveStatement (cognitive 23) · ×1
  • resolve-statements.resolveStatement (cognitive 23) packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:1417 — resolve-statements.resolveStatement has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 9, ternaries 1 (2 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · check-integrity.computeIntegrityViolations (cognitive 23) · ×1
  • check-integrity.computeIntegrityViolations (cognitive 23) packages/1-framework/3-tooling/migration/src/aggregate/check-integrity.ts:50 — check-integrity.computeIntegrityViolations has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 4 (7 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · build-execution-defaults.executionDefaultsOf (cognitive 23) · ×1
  • build-execution-defaults.executionDefaultsOf (cognitive 23) packages/2-mongo-family/2-authoring/contract-ts/src/build-execution-defaults.ts:36 — build-execution-defaults.executionDefaultsOf has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 5 (9 pts), loops 2, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validators.validateModelStorageReferences (cognitive 23) · ×1
  • validators.validateModelStorageReferences (cognitive 23) packages/2-sql-family/1-core/contract/src/validators.ts:854 — validators.validateModelStorageReferences has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 4 (9 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · relations.parseRelationAttribute (cognitive 23) · ×1
  • relations.parseRelationAttribute (cognitive 23) packages/2-sql-family/2-authoring/contract-prisma7/src/relations.ts:152 — relations.parseRelationAttribute has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (18 pts), match/switch 1 (2 pts), ternaries 1 (2 pts), loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.buildValueObjectNodes (cognitive 23) · ×1
  • interpreter.buildValueObjectNodes (cognitive 23) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:1467 — interpreter.buildValueObjectNodes has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 5 (11 pts), if/else 3 (6 pts), loops 4 (6 pts) (nesting depth added 11). None of this is in the body itself: all 23 points belong to one function literal inside it that branches (line 1470). 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.
D2 · Cognitive Complexity · SelectAst.collectParamRefs (cognitive 23) · ×1
  • SelectAst.collectParamRefs (cognitive 23) packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:1898 — SelectAst.collectParamRefs has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (13 pts), loops 7 (10 pts) (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · contract-stack-checks.refusedDefaults (cognitive 23) · ×1
  • contract-stack-checks.refusedDefaults (cognitive 23) packages/2-sql-family/9-family/src/core/contract-stack-checks.ts:125 — contract-stack-checks.refusedDefaults has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 3 (7 pts), boolean chains 4, error handling 1 (2 pts), loops 1 (nesting depth added 8). None of this is in the body itself: all 23 points belong to one function literal inside it that branches (line 127). 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.
D2 · Cognitive Complexity · mutation-executor.updateFirstGraph (cognitive 23) · ×1
  • mutation-executor.updateFirstGraph (cognitive 23) packages/3-extensions/sql-orm-client/src/mutation-executor.ts:390 — mutation-executor.updateFirstGraph has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 6 (9 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · audit-notice.runAudit (cognitive 23) · ×1
  • audit-notice.runAudit (cognitive 23) scripts/audit-notice.mjs:158 — audit-notice.runAudit has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 4 (7 pts), boolean chains 2, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 9). Of this number, 20 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · lint-single-import-root.findMixedPackages (cognitive 23) · ×1
  • lint-single-import-root.findMixedPackages (cognitive 23) scripts/lint-single-import-root.mjs:110 — lint-single-import-root.findMixedPackages has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 2 (9 pts), if/else 2 (6 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · publish-packages.worker (cognitive 23) · ×1
  • publish-packages.worker (cognitive 23) scripts/publish-packages.mjs:109 — publish-packages.worker has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 4 (9 pts), boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validate-domain.validateDiscriminators (cognitive 22) · ×1
  • validate-domain.validateDiscriminators (cognitive 22) packages/1-framework/0-foundation/contract/src/validate-domain.ts:221 — validate-domain.validateDiscriminators has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (18 pts), boolean chains 3, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · json-text.nonFiniteNumberIn (cognitive 22) · ×1
  • json-text.nonFiniteNumberIn (cognitive 22) packages/1-framework/1-core/framework-components/src/shared/json-text.ts:41 — json-text.nonFiniteNumberIn has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 3 (8 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migrate.planSpacePath (cognitive 22) · ×1
  • migrate.planSpacePath (cognitive 22) packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts:414 — migrate.planSpacePath has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 8, ternaries 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · signature-context.signatureExpression (cognitive 22) · ×1
  • signature-context.signatureExpression (cognitive 22) packages/1-framework/3-tooling/language-server/src/signature-context.ts:147 — signature-context.signatureExpression has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 6 (8 pts), boolean chains 5 (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.
D2 · Cognitive Complexity · refs.readRefsTolerant (cognitive 22) · ×1
  • refs.readRefsTolerant (cognitive 22) packages/1-framework/3-tooling/migration/src/refs.ts:182 — refs.readRefsTolerant has cognitive complexity 22 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (6 pts), error handling 3 (5 pts), boolean chains 3, loops 1 (nesting depth added 10). Of this number, 21 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · verify-contract-spaces.verifyContractSpaces (cognitive 22) · ×1
  • verify-contract-spaces.verifyContractSpaces (cognitive 22) packages/1-framework/3-tooling/migration/src/verify-contract-spaces.ts:189 — verify-contract-spaces.verifyContractSpaces has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 3, boolean chains 1 (nesting depth added 7). Of this number, 19 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.
D2 · Cognitive Complexity · plugin.prismaVitePlugin.collectModuleGraphFiles (cognitive 22) · ×1
  • plugin.prismaVitePlugin.collectModuleGraphFiles (cognitive 22) packages/1-framework/3-tooling/vite-plugin-contract-emit/src/plugin.ts:245 — plugin.prismaVitePlugin.collectModuleGraphFiles has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 3 (4 pts), error handling 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · build-collections.buildCollections (cognitive 22) · ×1
  • build-collections.buildCollections (cognitive 22) packages/2-mongo-family/2-authoring/contract-ts/src/build-collections.ts:229 — build-collections.buildCollections has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 10). Of this number, 11 points are the body's own statements and 11 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · encoding.encodeParamValue (cognitive 22) · ×1
  • encoding.encodeParamValue (cognitive 22) packages/2-sql-family/5-runtime/src/codecs/encoding.ts:92 — encoding.encodeParamValue has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (14 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · schema-verify.computeStorageTypeVerdict (cognitive 22) · ×1
  • schema-verify.computeStorageTypeVerdict (cognitive 22) packages/2-sql-family/9-family/src/core/diff/schema-verify.ts:228 — schema-verify.computeStorageTypeVerdict has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (16 pts), loops 3 (6 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-to-schema-ir.detectDestructiveChanges (cognitive 22) · ×1
  • contract-to-schema-ir.detectDestructiveChanges (cognitive 22) packages/2-sql-family/9-family/src/core/migrations/contract-to-schema-ir.ts:380 — contract-to-schema-ir.detectDestructiveChanges has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 3 (6 pts), ternaries 2 (3 pts) (nesting depth added 12). Of this number, 19 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.
D2 · Cognitive Complexity · bson-codec-helpers.assertBsonValue (cognitive 22) · ×1
  • bson-codec-helpers.assertBsonValue (cognitive 22) packages/3-targets/mongo/1-target/src/core/bson-codec-helpers.ts:50 — bson-codec-helpers.assertBsonValue has cognitive complexity 22 (threshold 15). Drivers by points: if/else 11 (15 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stored-inet.readIpv4Tail (cognitive 22) · ×1
  • stored-inet.readIpv4Tail (cognitive 22) packages/3-targets/postgres/1-target/src/core/stored-inet.ts:96 — stored-inet.readIpv4Tail has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · refusals.refuseFieldColumnMismatch (cognitive 22) · ×1
  • refusals.refuseFieldColumnMismatch (cognitive 22) packages/3-targets/postgres/1-target/src/core/psl-print/refusals.ts:233 — refusals.refuseFieldColumnMismatch has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 8, ternaries 4 (8 pts), if/else 6 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · check-publish-deps.runCheck (cognitive 22) · ×1
  • check-publish-deps.runCheck (cognitive 22) scripts/check-publish-deps.mjs:461 — check-publish-deps.runCheck has cognitive complexity 22 (threshold 15). Drivers by points: loops 5 (12 pts), if/else 6 (8 pts), boolean chains 1, ternaries 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · lint-workflow-triggers.stripYamlComment (cognitive 22) · ×1
  • lint-workflow-triggers.stripYamlComment (cognitive 22) scripts/lint-workflow-triggers.mjs:47 — lint-workflow-triggers.stripYamlComment has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 2 (4 pts), ternaries 1 (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.
D2 · Cognitive Complexity · canonicalization.omitDefaults (cognitive 21) · ×1
  • canonicalization.omitDefaults (cognitive 21) packages/1-framework/0-foundation/contract/src/canonicalization.ts:94 — canonicalization.omitDefaults has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 7, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · symbol-table.placeEntries (cognitive 21) · ×1
  • symbol-table.placeEntries (cognitive 21) packages/1-framework/2-authoring/psl-parser/src/symbol-table.ts:521 — symbol-table.placeEntries has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 2 (4 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.
D2 · Cognitive Complexity · db-update-failure.dbUpdateRunnerFailureError (cognitive 21) · ×1
  • db-update-failure.dbUpdateRunnerFailureError (cognitive 21) packages/1-framework/3-tooling/cli/src/utils/db-update-failure.ts:21 — db-update-failure.dbUpdateRunnerFailureError has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 6 (21 pts) (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.
D2 · Cognitive Complexity · combine-verify-results.combineVerifyResults (cognitive 21) · ×1
  • combine-verify-results.combineVerifyResults (cognitive 21) packages/1-framework/3-tooling/cli/src/utils/combine-verify-results.ts:41 — combine-verify-results.combineVerifyResults has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 7 (11 pts), if/else 3 (6 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · plan-resolution.resolveFromForPlan (cognitive 21) · ×1
  • plan-resolution.resolveFromForPlan (cognitive 21) packages/1-framework/3-tooling/cli/src/control-api/operations/plan-resolution.ts:211 — plan-resolution.resolveFromForPlan has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (20 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.
D2 · Cognitive Complexity · plugin.prismaVitePlugin.emitContract (cognitive 21) · ×1
  • plugin.prismaVitePlugin.emitContract (cognitive 21) packages/1-framework/3-tooling/vite-plugin-contract-emit/src/plugin.ts:106 — plugin.prismaVitePlugin.emitContract has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (6 pts), boolean chains 4, error handling 1, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · contract-refusals.validatedEnumNames (cognitive 21) · ×1
  • contract-refusals.validatedEnumNames (cognitive 21) packages/2-mongo-family/1-foundation/mongo-contract/src/contract-refusals.ts:111 — contract-refusals.validatedEnumNames has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (6 pts), boolean chains 1, ternaries 1 (nesting depth added 9). Of this number, 13 points are the body's own statements and 8 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · recursive-groups.recursiveGroupsOf (cognitive 21) · ×1
  • recursive-groups.recursiveGroupsOf (cognitive 21) packages/2-mongo-family/1-foundation/mongo-contract/src/recursive-groups.ts:28 — recursive-groups.recursiveGroupsOf has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), loops 6 (7 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 6). Most of this is not in the body itself: 5 of the 21 points are its own statements and the rest belongs to 2 function items inside it that branch (visit, a function literal at line 37). 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.
D2 · Cognitive Complexity · index-deduplication.deduplicateIndexes (cognitive 21) · ×1
  • index-deduplication.deduplicateIndexes (cognitive 21) packages/2-sql-family/1-core/contract/src/index-deduplication.ts:38 — index-deduplication.deduplicateIndexes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · defaults.lowerFunction (cognitive 21) · ×1
  • defaults.lowerFunction (cognitive 21) packages/2-sql-family/2-authoring/contract-prisma7/src/defaults.ts:359 — defaults.lowerFunction has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (12 pts), ternaries 4 (6 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · control-instance.createSqlFamilyInstance.toSchemaView (cognitive 21) · ×1
  • control-instance.createSqlFamilyInstance.toSchemaView (cognitive 21) packages/2-sql-family/9-family/src/core/control-instance.ts:1051 — control-instance.createSqlFamilyInstance.toSchemaView has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 8 (11 pts), if/else 5 (6 pts), loops 3, boolean chains 1 (nesting depth added 4). Most of this is not in the body itself: 2 of the 21 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 1092, 1085, 1195). 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.
D2 · Cognitive Complexity · mutation-executor.applyChildOwnedMutation (cognitive 21) · ×1
  • mutation-executor.applyChildOwnedMutation (cognitive 21) packages/3-extensions/sql-orm-client/src/mutation-executor.ts:733 — mutation-executor.applyChildOwnedMutation has cognitive complexity 21 (threshold 15). Drivers by points: loops 6 (12 pts), if/else 5 (8 pts), boolean chains 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · check-publish-deps.findDeclarationDepViolations (cognitive 21) · ×1
  • check-publish-deps.findDeclarationDepViolations (cognitive 21) scripts/check-publish-deps.mjs:285 — check-publish-deps.findDeclarationDepViolations has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 3, loops 2 (3 pts), ternaries 1 (nesting depth added 10). Of this number, 19 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · regen-extension-migrations.processExtension (cognitive 21) · ×1
  • regen-extension-migrations.processExtension (cognitive 21) scripts/regen-extension-migrations.mjs:228 — regen-extension-migrations.processExtension has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validate-skills.validateSkillMd (cognitive 21) · ×1
  • validate-skills.validateSkillMd (cognitive 21) scripts/validate-skills.mjs:30 — validate-skills.validateSkillMd has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, loops 1 (3 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fetch-review-state.paginateAll (cognitive 21) · ×1
  • fetch-review-state.paginateAll (cognitive 21) skills-contrib/review-fetch-phase/scripts/fetch-review-state.mjs:378 — fetch-review-state.paginateAll has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 5 (6 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.
D2 · Cognitive Complexity · project-import-root.nearestManifest (cognitive 20) · ×1
  • project-import-root.nearestManifest (cognitive 20) packages/1-framework/3-tooling/cli/src/utils/project-import-root.ts:49 — project-import-root.nearestManifest has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (8 pts), ternaries 2 (7 pts), error handling 2 (4 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · pair-back-relations.pairMongoBackRelations (cognitive 20) · ×1
  • pair-back-relations.pairMongoBackRelations (cognitive 20) packages/2-mongo-family/2-authoring/contract-psl/src/pair-back-relations.ts:39 — pair-back-relations.pairMongoBackRelations has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 2 (4 pts), boolean chains 2, loops 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · extensions.readDatasourceExtensions (cognitive 20) · ×1
  • extensions.readDatasourceExtensions (cognitive 20) packages/2-sql-family/2-authoring/contract-prisma7/src/extensions.ts:84 — extensions.readDatasourceExtensions has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-object-field-planning.storedColumns (cognitive 20) · ×1
  • value-object-field-planning.storedColumns (cognitive 20) packages/2-sql-family/9-family/src/core/migrations/value-object-field-planning.ts:143 — value-object-field-planning.storedColumns has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 3 (6 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-object-field-fills.planValueObjectFieldFills (cognitive 20) · ×1
  • value-object-field-fills.planValueObjectFieldFills (cognitive 20) packages/2-sql-family/9-family/src/core/migrations/value-object-field-fills.ts:271 — value-object-field-fills.planValueObjectFieldFills has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (7 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · relation-fields.buildRelationFields (cognitive 20) · ×1
  • relation-fields.buildRelationFields (cognitive 20) packages/3-targets/postgres/1-target/src/core/psl-print/relation-fields.ts:368 — relation-fields.buildRelationFields has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (9 pts), ternaries 4 (9 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · issue-planner.planIssues (cognitive 20) · ×1
  • issue-planner.planIssues (cognitive 20) packages/3-targets/sqlite/1-target/src/core/migrations/issue-planner.ts:432 — issue-planner.planIssues has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 3, loops 2, ternaries 2 (nesting depth added 5). Of this number, 13 points are the body's own statements and 7 belong to 5 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · lint-consumer-internal-imports.scanManifests (cognitive 20) · ×1
  • lint-consumer-internal-imports.scanManifests (cognitive 20) scripts/lint-consumer-internal-imports.mjs:159 — lint-consumer-internal-imports.scanManifests has cognitive complexity 20 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (6 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · type-aliases.resolveTypeAliases (cognitive 19) · ×1
  • type-aliases.resolveTypeAliases (cognitive 19) packages/1-framework/2-authoring/psl-parser/src/type-aliases.ts:222 — type-aliases.resolveTypeAliases has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · runner-failure-advice.migrateRowsWithoutValueAdvice (cognitive 19) · ×1
  • runner-failure-advice.migrateRowsWithoutValueAdvice (cognitive 19) packages/1-framework/3-tooling/cli/src/utils/runner-failure-advice.ts:420 — runner-failure-advice.migrateRowsWithoutValueAdvice has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (15 pts), if/else 3, boolean chains 1 (nesting depth added 7). Of this number, 17 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-check.checkManifestFilesPresent (cognitive 19) · ×1
  • migration-check.checkManifestFilesPresent (cognitive 19) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-check.ts:249 — migration-check.checkManifestFilesPresent has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · load-ts-contract.loadContractFromTs (cognitive 19) · ×1
  • load-ts-contract.loadContractFromTs (cognitive 19) packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:207 — load-ts-contract.loadContractFromTs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · refs.readRefs (cognitive 19) · ×1
  • refs.readRefs (cognitive 19) packages/1-framework/3-tooling/migration/src/refs.ts:116 — refs.readRefs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 3 (7 pts), error handling 3 (5 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (nesting depth added 8). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · psl-column-resolution.resolveEntityRefTypeConstructorCall (cognitive 19) · ×1
  • psl-column-resolution.resolveEntityRefTypeConstructorCall (cognitive 19) packages/2-sql-family/2-authoring/contract-psl/src/psl-column-resolution.ts:269 — psl-column-resolution.resolveEntityRefTypeConstructorCall has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 5, boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · aggregate-descriptor-registry.buildSqlAggregateDescriptorRegistry (cognitive 19) · ×1
  • aggregate-descriptor-registry.buildSqlAggregateDescriptorRegistry (cognitive 19) packages/2-sql-family/4-lanes/relational-core/src/aggregate-descriptor-registry.ts:52 — aggregate-descriptor-registry.buildSqlAggregateDescriptorRegistry has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (5 pts), loops 3, boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · query-plan-select.resolvePolymorphicProjectionSelection (cognitive 19) · ×1
  • query-plan-select.resolvePolymorphicProjectionSelection (cognitive 19) packages/3-extensions/sql-orm-client/src/query-plan-select.ts:136 — query-plan-select.resolvePolymorphicProjectionSelection has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · query-plan-select.buildIncludeChildRowsSelect (cognitive 19) · ×1
  • query-plan-select.buildIncludeChildRowsSelect (cognitive 19) packages/3-extensions/sql-orm-client/src/query-plan-select.ts:512 — query-plan-select.buildIncludeChildRowsSelect has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · fragments.assertDeclaredFieldsFragmentFields (cognitive 19) · ×1
  • fragments.assertDeclaredFieldsFragmentFields (cognitive 19) packages/3-extensions/sql-orm-client/src/fragments.ts:538 — fragments.assertDeclaredFieldsFragmentFields has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 5 (12 pts), if/else 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · binding.resolveMongoBinding (cognitive 19) · ×1
  • binding.resolveMongoBinding (cognitive 19) packages/3-targets/mongo/9-facade/src/runtime/binding.ts:84 — binding.resolveMongoBinding has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mysql-database.rejectSqlBodyIndexes (cognitive 19) · ×1
  • mysql-database.rejectSqlBodyIndexes (cognitive 19) packages/3-targets/mysql/1-target/src/core/mysql-database.ts:204 — mysql-database.rejectSqlBodyIndexes has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 2 (6 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · issue-planner.planIssues (cognitive 19) · ×1
  • issue-planner.planIssues (cognitive 19) packages/3-targets/mysql/1-target/src/core/migrations/issue-planner.ts:546 — issue-planner.planIssues has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 4 (5 pts), ternaries 1 (nesting depth added 7). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · codec-helpers.verboseIntervalFields (cognitive 19) · ×1
  • codec-helpers.verboseIntervalFields (cognitive 19) packages/3-targets/postgres/1-target/src/core/codec-helpers.ts:217 — codec-helpers.verboseIntervalFields has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, ternaries 2, loops 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · PostgresMigrationRunner.applyPlan (cognitive 19) · ×1
  • PostgresMigrationRunner.applyPlan (cognitive 19) packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:317 — PostgresMigrationRunner.applyPlan has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · relation-fields.buildRelationField (cognitive 19) · ×1
  • relation-fields.buildRelationField (cognitive 19) packages/3-targets/postgres/1-target/src/core/psl-print/relation-fields.ts:221 — relation-fields.buildRelationField has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 4, ternaries 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · psl-contract.buildModel (cognitive 19) · ×1
  • psl-contract.buildModel (cognitive 19) packages/3-targets/postgres/1-target/src/core/psl-print/psl-contract.ts:166 — psl-contract.buildModel has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (7 pts), loops 2 (5 pts), ternaries 2 (5 pts), boolean chains 2 (nesting depth added 9). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqliteMigrationRunner.applyPlan (cognitive 19) · ×1
  • SqliteMigrationRunner.applyPlan (cognitive 19) packages/3-targets/sqlite/1-target/src/core/migrations/runner.ts:299 — SqliteMigrationRunner.applyPlan has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · control-adapter.sqliteInlineLiteral (cognitive 19) · ×1
  • control-adapter.sqliteInlineLiteral (cognitive 19) packages/3-targets/sqlite/2-adapter/src/core/control-adapter.ts:788 — control-adapter.sqliteInlineLiteral has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (14 pts), ternaries 2 (5 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · render-review-actions.parseCliArgs (cognitive 19) · ×1
  • render-review-actions.parseCliArgs (cognitive 19) skills-contrib/review-triage-phase/scripts/render-review-actions.mjs:31 — render-review-actions.parseCliArgs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2, loops 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · control-stack.enforceHelperCodecInvariants (cognitive 18) · ×1
  • control-stack.enforceHelperCodecInvariants (cognitive 18) packages/1-framework/1-core/framework-components/src/control/control-stack.ts:402 — control-stack.enforceHelperCodecInvariants has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · emit.streamRow (cognitive 18) · ×1
  • emit.streamRow (cognitive 18) packages/1-framework/2-authoring/psl-parser/src/format/emit.ts:197 — emit.streamRow has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · plan-question-prompt.askOneAtATime (cognitive 18) · ×1
  • plan-question-prompt.askOneAtATime (cognitive 18) packages/1-framework/3-tooling/cli/src/orm/plan-question-prompt.ts:81 — plan-question-prompt.askOneAtATime 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). 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.
D2 · Cognitive Complexity · migration-list-graph-topology.forwardDistances (cognitive 18) · ×1
  • migration-list-graph-topology.forwardDistances (cognitive 18) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-list-graph-topology.ts:51 — migration-list-graph-topology.forwardDistances has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 6 (7 pts), ternaries 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.
D2 · Cognitive Complexity · migration-graph-labels.formatEdgeAnnotationSuffix (cognitive 18) · ×1
  • migration-graph-labels.formatEdgeAnnotationSuffix (cognitive 18) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-labels.ts:184 — migration-graph-labels.formatEdgeAnnotationSuffix has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 4 (7 pts), boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migrate-show-render.renderMigrateShowGraph (cognitive 18) · ×1
  • migrate-show-render.renderMigrateShowGraph (cognitive 18) packages/1-framework/3-tooling/cli/src/utils/formatters/migrate-show-render.ts:63 — migrate-show-render.renderMigrateShowGraph has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 9 (14 pts), if/else 1 (2 pts), loops 2 (nesting depth added 6). Of this number, 14 points are the body's own statements and 4 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.
D2 · Cognitive Complexity · migration-plan.runPlannerLeg (cognitive 18) · ×1
  • migration-plan.runPlannerLeg (cognitive 18) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts:172 — migration-plan.runPlannerLeg has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 3, boolean chains 2, error handling 1, loops 1 (nesting depth added 4). Of this number, 16 points are the body's own statements and 2 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.
D2 · Cognitive Complexity · domain-type-generation.generateModelsType (cognitive 18) · ×1
  • domain-type-generation.generateModelsType (cognitive 18) packages/1-framework/3-tooling/emitter/src/domain-type-generation.ts:214 — domain-type-generation.generateModelsType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (7 pts), boolean chains 1, loops 1 (nesting depth added 9). Of this number, 11 points are the body's own statements and 7 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.
D2 · Cognitive Complexity · generate-contract-dts.generateContractDts (cognitive 18) · ×1
  • generate-contract-dts.generateContractDts (cognitive 18) REDACTED:67 — generate-contract-dts.generateContractDts has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 8, if/else 5 (7 pts), loops 2, boolean chains 1 (nesting depth added 2). Of this number, 13 points are the body's own statements and 5 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.
D2 · Cognitive Complexity · attribute-argument-grammar.advanceGrammar (cognitive 18) · ×1
  • attribute-argument-grammar.advanceGrammar (cognitive 18) packages/1-framework/3-tooling/language-server/src/attribute-argument-grammar.ts:23 — attribute-argument-grammar.advanceGrammar has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 6 (11 pts), if/else 3 (5 pts), boolean chains 1, match/switch 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.
D2 · Cognitive Complexity · references.provideReferences (cognitive 18) · ×1
  • references.provideReferences (cognitive 18) packages/1-framework/3-tooling/language-server/src/references.ts:18 — references.provideReferences has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (3 pts), ternaries 3, boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · semantic-tokens.collectExpression (cognitive 18) · ×1
  • semantic-tokens.collectExpression (cognitive 18) packages/1-framework/3-tooling/language-server/src/semantic-tokens.ts:434 — semantic-tokens.collectExpression has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (12 pts), loops 3 (6 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · migration-ref.parseMigrationRef (cognitive 18) · ×1
  • migration-ref.parseMigrationRef (cognitive 18) packages/1-framework/3-tooling/migration/src/refs/migration-ref.ts:19 — migration-ref.parseMigrationRef has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · refusal-diagnostics.refusalDiagnostic (cognitive 18) · ×1
  • refusal-diagnostics.refusalDiagnostic (cognitive 18) packages/2-mongo-family/2-authoring/contract-prisma6/src/refusal-diagnostics.ts:52 — refusal-diagnostics.refusalDiagnostic has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, match/switch 1 (nesting depth added 7). 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.
D2 · Cognitive Complexity · interpreter.buildEnum (cognitive 18) · ×1
  • interpreter.buildEnum (cognitive 18) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:568 — interpreter.buildEnum has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.readRelationArguments (cognitive 18) · ×1
  • interpreter.readRelationArguments (cognitive 18) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:1261 — interpreter.readRelationArguments has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (9 pts), ternaries 3 (6 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.nestedIndexPath (cognitive 18) · ×1
  • interpreter.nestedIndexPath (cognitive 18) packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:563 — interpreter.nestedIndexPath has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 2 (6 pts), if/else 2 (5 pts), boolean chains 4, loops 2 (3 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.
D2 · Cognitive Complexity · index-type-validation.validateIndexTypes (cognitive 18) · ×1
  • index-type-validation.validateIndexTypes (cognitive 18) packages/2-sql-family/1-core/contract/src/index-type-validation.ts:15 — index-type-validation.validateIndexTypes has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (12 pts), loops 3 (6 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · validators.validateRelationThroughConsistency (cognitive 18) · ×1
  • validators.validateRelationThroughConsistency (cognitive 18) packages/2-sql-family/1-core/contract/src/validators.ts:1355 — validators.validateRelationThroughConsistency has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 2 (8 pts), loops 3 (6 pts), if/else 1 (4 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · SqlColumnDefaultIR.isEqualTo (cognitive 18) · ×1
  • SqlColumnDefaultIR.isEqualTo (cognitive 18) packages/2-sql-family/1-core/schema-ir/src/ir/sql-column-default-ir.ts:112 — SqlColumnDefaultIR.isEqualTo has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 8 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · interpreter.lowerExtensionBlocksForNamespace (cognitive 18) · ×1
  • interpreter.lowerExtensionBlocksForNamespace (cognitive 18) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:383 — interpreter.lowerExtensionBlocksForNamespace has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (4 pts), 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.
D2 · Cognitive Complexity · interpreter.collectPolymorphismDeclarations (cognitive 18) · ×1
  • interpreter.collectPolymorphismDeclarations (cognitive 18) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:1601 — interpreter.collectPolymorphismDeclarations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 4 (5 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.
D2 · Cognitive Complexity · decoding.decodeField (cognitive 18) · ×1
  • decoding.decodeField (cognitive 18) packages/2-sql-family/5-runtime/src/codecs/decoding.ts:251 — decoding.decodeField has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 3 (4 pts), boolean chains 1 (nesting depth added 5). Of this number, 13 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · lints.evaluateAstLints (cognitive 18) · ×1
  • lints.evaluateAstLints (cognitive 18) packages/2-sql-family/5-runtime/src/middleware/lints.ts:48 — lints.evaluateAstLints has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 3 (9 pts), if/else 4 (8 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · json-path.readStringLiteral (cognitive 18) · ×1
  • json-path.readStringLiteral (cognitive 18) packages/2-sql-family/9-family/src/core/migrations/json-path.ts:64 — json-path.readStringLiteral has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mongo-statement-planning.planFieldStatement (cognitive 18) · ×1
  • mongo-statement-planning.planFieldStatement (cognitive 18) packages/3-targets/mongo/1-target/src/core/migrations/mongo-statement-planning.ts:546 — mongo-statement-planning.planFieldStatement has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, boolean chains 6, ternaries 1. 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: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · planner-strategies.notNullBackfillCallStrategy (cognitive 18) · ×1
  • planner-strategies.notNullBackfillCallStrategy (cognitive 18) packages/3-targets/postgres/1-target/src/core/migrations/planner-strategies.ts:239 — planner-strategies.notNullBackfillCallStrategy has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · PostgresMigrationRunner.executeOnConnection (cognitive 18) · ×1
  • PostgresMigrationRunner.executeOnConnection (cognitive 18) packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:159 — PostgresMigrationRunner.executeOnConnection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · refusals.refuseUnmodelledTablesAndColumns (cognitive 18) · ×1
  • refusals.refuseUnmodelledTablesAndColumns (cognitive 18) packages/3-targets/postgres/1-target/src/core/psl-print/refusals.ts:396 — refusals.refuseUnmodelledTablesAndColumns has cognitive complexity 18 (threshold 15). Drivers by points: loops 6 (11 pts), if/else 2 (7 pts) (nesting depth added 10). 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.
D2 · Cognitive Complexity · sql-renderer.renderInsert (cognitive 18) · ×1
  • sql-renderer.renderInsert (cognitive 18) packages/3-targets/postgres/2-adapter/src/core/sql-renderer.ts:1015 — sql-renderer.renderInsert has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 3 (4 pts), match/switch 1 (2 pts) (nesting depth added 8). 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 literals inside it that branch (lines 1056, 1024). 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.
D2 · Cognitive Complexity · SqliteMigrationRunner.executeOnConnection (cognitive 18) · ×1
  • SqliteMigrationRunner.executeOnConnection (cognitive 18) packages/3-targets/sqlite/1-target/src/core/migrations/runner.ts:80 — SqliteMigrationRunner.executeOnConnection has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · check-publish-deps.findPnPinViolations (cognitive 18) · ×1
  • check-publish-deps.findPnPinViolations (cognitive 18) scripts/check-publish-deps.mjs:127 — check-publish-deps.findPnPinViolations has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 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.
D2 · Cognitive Complexity · fetch-review-state.main (cognitive 18) · ×1
  • fetch-review-state.main (cognitive 18) skills-contrib/review-fetch-phase/scripts/fetch-review-state.mjs:491 — fetch-review-state.main has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2, error handling 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · data-type-values.listFiles.visit (cognitive 18) · ×1
  • data-type-values.listFiles.visit (cognitive 18) REDACTED:334 — data-type-values.listFiles.visit has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, loops 1 (nesting depth added 6). Of this number, 17 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · canonicalization-path-match.matchesPathPattern (cognitive 17) · ×1
  • canonicalization-path-match.matchesPathPattern (cognitive 17) packages/1-framework/0-foundation/contract/src/canonicalization-path-match.ts:7 — canonicalization-path-match.matchesPathPattern has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · framework-authoring.assertResolvableTypeConstructorTemplates (cognitive 17) · ×1
  • framework-authoring.assertResolvableTypeConstructorTemplates (cognitive 17) packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:984 — framework-authoring.assertResolvableTypeConstructorTemplates has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 3 (6 pts) (nesting depth added 9). 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.
D2 · Cognitive Complexity · aggregate-overloads.settleAggregateOverloads (cognitive 17) · ×1
  • aggregate-overloads.settleAggregateOverloads (cognitive 17) packages/1-framework/1-core/framework-components/src/shared/aggregate-overloads.ts:66 — aggregate-overloads.settleAggregateOverloads has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (11 pts), loops 3 (4 pts), match/switch 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · ObjectFieldAst.value (cognitive 17) · ×1
  • ObjectFieldAst.value (cognitive 17) packages/1-framework/2-authoring/psl-parser/src/syntax/ast/expressions.ts:392 — ObjectFieldAst.value has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (AttributeArgAst.value) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · AttributeArgAst.value (cognitive 17) · ×1
  • AttributeArgAst.value (cognitive 17) packages/1-framework/2-authoring/psl-parser/src/syntax/ast/expressions.ts:466 — AttributeArgAst.value has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ObjectFieldAst.value) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
D2 · Cognitive Complexity · record.recordOne (cognitive 17) · ×1
  • record.recordOne (cognitive 17) packages/1-framework/3-tooling/cli/scripts/record.ts:507 — record.recordOne has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 2 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · framework-components.assertFrameworkComponentsCompatible (cognitive 17) · ×1
  • framework-components.assertFrameworkComponentsCompatible (cognitive 17) packages/1-framework/3-tooling/cli/src/utils/framework-components.ts:45 — framework-components.assertFrameworkComponentsCompatible has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · init-emit.errorFromEnvelope (cognitive 17) · ×1
  • init-emit.errorFromEnvelope (cognitive 17) packages/1-framework/3-tooling/cli/src/orm/init-emit.ts:64 — init-emit.errorFromEnvelope has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (6 pts), ternaries 3 (6 pts), boolean chains 2, error handling 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.
D2 · Cognitive Complexity · migration-graph-grid-layout.assertSingleOwner (cognitive 17) · ×1
  • migration-graph-grid-layout.assertSingleOwner (cognitive 17) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts:1118 — migration-graph-grid-layout.assertSingleOwner has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-graph.detectCycles (cognitive 17) · ×1
  • migration-graph.detectCycles (cognitive 17) packages/1-framework/3-tooling/migration/src/migration-graph.ts:437 — migration-graph.detectCycles has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (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.
D2 · Cognitive Complexity · migration-graph.detectOrphans (cognitive 17) · ×1
  • migration-graph.detectOrphans (cognitive 17) packages/1-framework/3-tooling/migration/src/migration-graph.ts:499 — migration-graph.detectOrphans has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 5 (8 pts) (nesting depth added 7). 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.
D2 · Cognitive Complexity · MongoIndexOptions.constructor (cognitive 17) · ×1
  • MongoIndexOptions.constructor (cognitive 17) packages/2-mongo-family/1-foundation/mongo-contract/src/ir/mongo-index-options.ts:61 — MongoIndexOptions.constructor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · indexes.parseFieldUnique (cognitive 17) · ×1
  • indexes.parseFieldUnique (cognitive 17) packages/2-mongo-family/2-authoring/contract-prisma6/src/indexes.ts:244 — indexes.parseFieldUnique has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.collectPolymorphismDeclarations (cognitive 17) · ×1
  • interpreter.collectPolymorphismDeclarations (cognitive 17) packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:306 — interpreter.collectPolymorphismDeclarations has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (16 pts), loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · refusal-errors.refusalError (cognitive 17) · ×1
  • refusal-errors.refusalError (cognitive 17) packages/2-mongo-family/2-authoring/contract-ts/src/refusal-errors.ts:170 — refusal-errors.refusalError has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (14 pts), if/else 1 (2 pts), match/switch 1 (nesting depth added 9). 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.
D2 · Cognitive Complexity · compile.compileMongoQuery (cognitive 17) · ×1
  • compile.compileMongoQuery (cognitive 17) packages/2-mongo-family/5-query-builders/orm/src/compile.ts:62 — compile.compileMongoQuery has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), loops 2 (4 pts), boolean chains 2, ternaries 2 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · validators.validateThroughJoinSide (cognitive 17) · ×1
  • validators.validateThroughJoinSide (cognitive 17) packages/2-sql-family/1-core/contract/src/validators.ts:1261 — validators.validateThroughJoinSide has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · derived-checks.stripDerivedChecksFromNonManagedTables (cognitive 17) · ×1
  • derived-checks.stripDerivedChecksFromNonManagedTables (cognitive 17) packages/2-sql-family/2-authoring/contract-ts/src/derived-checks.ts:81 — derived-checks.stripDerivedChecksFromNonManagedTables has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (3 pts), ternaries 1 (3 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.
D2 · Cognitive Complexity · assembly.enforceSqlDataTypeInvariants (cognitive 17) · ×1
  • assembly.enforceSqlDataTypeInvariants (cognitive 17) packages/2-sql-family/9-family/src/core/assembly.ts:77 — assembly.enforceSqlDataTypeInvariants has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 3, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · value-object-field-planning.fieldChanges (cognitive 17) · ×1
  • value-object-field-planning.fieldChanges (cognitive 17) packages/2-sql-family/9-family/src/core/migrations/value-object-field-planning.ts:222 — value-object-field-planning.fieldChanges has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 7). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · column-types.inferColumnTypes (cognitive 17) · ×1
  • column-types.inferColumnTypes (cognitive 17) packages/2-sql-family/9-family/src/core/psl-build/column-types.ts:149 — column-types.inferColumnTypes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (7 pts), ternaries 2 (7 pts), loops 2 (3 pts) (nesting depth added 10). 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.
D2 · Cognitive Complexity · generator-calls.generatorCallsFor (cognitive 17) · ×1
  • generator-calls.generatorCallsFor (cognitive 17) packages/2-sql-family/9-family/src/core/psl-build/generator-calls.ts:43 — generator-calls.generatorCallsFor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (6 pts), boolean chains 2, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MongoControlAdapterImpl.readLedger (cognitive 17) · ×1
  • MongoControlAdapterImpl.readLedger (cognitive 17) packages/3-targets/mongo/2-adapter/src/core/migrations/mongo-control-adapter.ts:253 — MongoControlAdapterImpl.readLedger has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · stored-inet.printIpv6 (cognitive 17) · ×1
  • stored-inet.printIpv6 (cognitive 17) packages/3-targets/postgres/1-target/src/core/stored-inet.ts:212 — stored-inet.printIpv6 has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, loops 1, 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.
D2 · Cognitive Complexity · planner-strategies.nullableTighteningCallStrategy (cognitive 17) · ×1
  • planner-strategies.nullableTighteningCallStrategy (cognitive 17) packages/3-targets/postgres/1-target/src/core/migrations/planner-strategies.ts:372 — planner-strategies.nullableTighteningCallStrategy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · scalar-fields.buildScalarFields (cognitive 17) · ×1
  • scalar-fields.buildScalarFields (cognitive 17) packages/3-targets/postgres/1-target/src/core/psl-print/scalar-fields.ts:96 — scalar-fields.buildScalarFields has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (10 pts), boolean chains 4, if/else 1 (2 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · index.runPostgresCodecProjection (cognitive 17) · ×1
  • index.runPostgresCodecProjection (cognitive 17) packages/3-targets/postgres/4-codec-testkit/src/index.ts:399 — index.runPostgresCodecProjection has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7, ternaries 3 (5 pts), error handling 4, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · check-conformance.packedEntrySpecifiers (cognitive 17) · ×1
  • check-conformance.packedEntrySpecifiers (cognitive 17) scripts/check-conformance.mjs:430 — check-conformance.packedEntrySpecifiers has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · fetch-review-state.parseCliArgs (cognitive 17) · ×1
  • fetch-review-state.parseCliArgs (cognitive 17) skills-contrib/review-fetch-phase/scripts/fetch-review-state.mjs:143 — fetch-review-state.parseCliArgs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · main.main (cognitive 16) · ×1
  • main.main (cognitive 16) REDACTED:175 — main.main has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (12 pts), loops 3, boolean chains 1 (nesting depth added 1). Most of this is not in the body itself: 6 of the 16 points are its own statements and the rest belongs to 6 function items inside it that branch (a function literal at line 291, openEditorFunc, a function literal at line 348, …). 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.
D2 · Cognitive Complexity · validate-domain.validateRelationNullability (cognitive 16) · ×1
  • validate-domain.validateRelationNullability (cognitive 16) packages/1-framework/0-foundation/contract/src/validate-domain.ts:197 — validate-domain.validateRelationNullability has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (10 pts), boolean chains 3, loops 2 (3 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.
D2 · Cognitive Complexity · framework-authoring.mergeAuthoringAttributeSpecs (cognitive 16) · ×1
  • framework-authoring.mergeAuthoringAttributeSpecs (cognitive 16) packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:873 — framework-authoring.mergeAuthoringAttributeSpecs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · mutation-defaults.applyMutationDefaults (cognitive 16) · ×1
  • mutation-defaults.applyMutationDefaults (cognitive 16) packages/1-framework/1-core/framework-components/src/execution/mutation-defaults.ts:152 — mutation-defaults.applyMutationDefaults has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 2, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · StatementActivityRunImpl.runQuery (cognitive 16) · ×1
  • StatementActivityRunImpl.runQuery (cognitive 16) packages/1-framework/1-core/framework-components/src/execution/run-with-middleware.ts:210 — StatementActivityRunImpl.runQuery has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 4 (7 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.
D2 · Cognitive Complexity · date-time-stored-form.readWritten (cognitive 16) · ×1
  • date-time-stored-form.readWritten (cognitive 16) packages/1-framework/1-core/framework-components/src/shared/date-time-stored-form.ts:182 — date-time-stored-form.readWritten has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · binder.resolveTypeReference (cognitive 16) · ×1
  • binder.resolveTypeReference (cognitive 16) packages/1-framework/2-authoring/psl-parser/src/binder.ts:1115 — binder.resolveTypeReference has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 6, 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.
D2 · Cognitive Complexity · serialize-print-document.serializeModel (cognitive 16) · ×1
  • serialize-print-document.serializeModel (cognitive 16) packages/1-framework/2-authoring/psl-printer/src/serialize-print-document.ts:177 — serialize-print-document.serializeModel has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 2 (4 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 7). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · init-prisma7-check.createPrisma7SourceCheck.<returned closure> (cognitive 16) · ×1
  • init-prisma7-check.createPrisma7SourceCheck.<returned closure> (cognitive 16) packages/1-framework/3-tooling/cli/src/orm/init-prisma7-check.ts:111 — init-prisma7-check.createPrisma7SourceCheck.<returned closure> has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (5 pts), boolean chains 1, error handling 1 (nesting depth added 4). Of this number, 11 points are the body's own statements and 5 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-list-graph-topology.canReachForward (cognitive 16) · ×1
  • migration-list-graph-topology.canReachForward (cognitive 16) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-list-graph-topology.ts:96 — migration-list-graph-topology.canReachForward 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.
D2 · Cognitive Complexity · migration-graph-rows.buildMigrationGraphRows (cognitive 16) · ×1
  • migration-graph-rows.buildMigrationGraphRows (cognitive 16) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-rows.ts:376 — migration-graph-rows.buildMigrationGraphRows has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 4 (6 pts), ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · migration-graph-occlusion-render.glyphFor (cognitive 16) · ×1
  • migration-graph-occlusion-render.glyphFor (cognitive 16) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-occlusion-render.ts:81 — migration-graph-occlusion-render.glyphFor has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 8. 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.
D2 · Cognitive Complexity · migration-check.checkSnapshotConsistency (cognitive 16) · ×1
  • migration-check.checkSnapshotConsistency (cognitive 16) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-check.ts:99 — migration-check.checkSnapshotConsistency has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (7 pts), boolean chains 4, error handling 3 (4 pts), ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · load-ts-contract.validatePurity (cognitive 16) · ×1
  • load-ts-contract.validatePurity (cognitive 16) packages/1-framework/3-tooling/cli/src/load-ts-contract.ts:63 — load-ts-contract.validatePurity has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, error handling 1, loops 1 (nesting depth added 3). Most of this is not in the body itself: 5 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (check). 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.
D2 · Cognitive Complexity · signature-context.signatureArguments (cognitive 16) · ×1
  • signature-context.signatureArguments (cognitive 16) packages/1-framework/3-tooling/language-server/src/signature-context.ts:99 — signature-context.signatureArguments has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (7 pts), if/else 5 (6 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.
D2 · Cognitive Complexity · refs.deleteRef (cognitive 16) · ×1
  • refs.deleteRef (cognitive 16) packages/1-framework/3-tooling/migration/src/refs.ts:260 — refs.deleteRef has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (6 pts), boolean chains 3, error handling 2 (3 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · check-integrity.contractViolations (cognitive 16) · ×1
  • check-integrity.contractViolations (cognitive 16) packages/1-framework/3-tooling/migration/src/aggregate/check-integrity.ts:203 — check-integrity.contractViolations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (4 pts), error handling 1 (2 pts), boolean chains 1, ternaries 1 (nesting depth added 6). Of this number, 14 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.
D2 · Cognitive Complexity · indexes.readFields (cognitive 16) · ×1
  • indexes.readFields (cognitive 16) packages/2-mongo-family/2-authoring/contract-prisma6/src/indexes.ts:137 — indexes.readFields has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, loops 1, 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.
D2 · Cognitive Complexity · interpreter.resolveFieldType (cognitive 16) · ×1
  • interpreter.resolveFieldType (cognitive 16) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:775 — interpreter.resolveFieldType has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 3 (4 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · interpreter.readCompositeFields (cognitive 16) · ×1
  • interpreter.readCompositeFields (cognitive 16) packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:863 — interpreter.readCompositeFields has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 3 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · build-polymorphism.decideDiscriminator (cognitive 16) · ×1
  • build-polymorphism.decideDiscriminator (cognitive 16) packages/2-mongo-family/2-authoring/contract-ts/src/build-polymorphism.ts:78 — build-polymorphism.decideDiscriminator has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), loops 4, ternaries 3 (4 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MongoCollectionImpl.#encodeFieldFilter (cognitive 16) · ×1
  • MongoCollectionImpl.#encodeFieldFilter (cognitive 16) packages/2-mongo-family/5-query-builders/orm/src/collection.ts:1037 — MongoCollectionImpl.#encodeFieldFilter has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 6, boolean chains 3 (nesting depth added 3). Of this number, 10 points are the body's own statements and 6 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
D2 · Cognitive Complexity · extensions.readArguments (cognitive 16) · ×1
  • extensions.readArguments (cognitive 16) packages/2-sql-family/2-authoring/contract-prisma7/src/extensions.ts:150 — extensions.readArguments has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 1 (3 pts), boolean chains 2, match/switch 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.
D2 · Cognitive Complexity · psl-attribute-parsing.reportFieldDbAttributes (cognitive 16) · ×1
  • psl-attribute-parsing.reportFieldDbAttributes (cognitive 16) packages/2-sql-family/2-authoring/contract-psl/src/psl-attribute-parsing.ts:86 — psl-attribute-parsing.reportFieldDbAttributes has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 1 (5 pts), boolean chains 1 (nesting depth added 10). 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.
D2 · Cognitive Complexity · removed-field-presets.codecIdAt (cognitive 16) · ×1
  • removed-field-presets.codecIdAt (cognitive 16) packages/2-sql-family/2-authoring/contract-ts/src/removed-field-presets.ts:173 — removed-field-presets.codecIdAt has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 3, ternaries 2 (3 pts), error handling 1 (2 pts) (nesting depth added 4). Of this number, 13 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · owned-transaction.beginOwnedTransaction (cognitive 16) · ×1
  • owned-transaction.beginOwnedTransaction (cognitive 16) packages/2-sql-family/5-runtime/src/owned-transaction.ts:9 — owned-transaction.beginOwnedTransaction has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), error handling 5 (6 pts), ternaries 1 (2 pts), boolean chains 1 (nesting depth added 4). Of this number, 11 points are the body's own statements and 5 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · control-policy.partitionIssuesByControlPolicy (cognitive 16) · ×1
  • control-policy.partitionIssuesByControlPolicy (cognitive 16) packages/2-sql-family/9-family/src/core/migrations/control-policy.ts:159 — control-policy.partitionIssuesByControlPolicy has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · relation-inference.inferRelations (cognitive 16) · ×1
  • relation-inference.inferRelations (cognitive 16) packages/2-sql-family/9-family/src/core/psl-contract-infer/relation-inference.ts:25 — relation-inference.inferRelations has cognitive complexity 16 (threshold 15). Drivers by points: loops 6 (9 pts), if/else 1 (3 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 7). 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.
D2 · Cognitive Complexity · fragments.declaredFieldSpec (cognitive 16) · ×1
  • fragments.declaredFieldSpec (cognitive 16) packages/3-extensions/sql-orm-client/src/fragments.ts:272 — fragments.declaredFieldSpec has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 6, if/else 4 (6 pts), ternaries 2 (4 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · model-accessor.toRelationWhereExpr (cognitive 16) · ×1
  • model-accessor.toRelationWhereExpr (cognitive 16) packages/3-extensions/sql-orm-client/src/model-accessor.ts:722 — model-accessor.toRelationWhereExpr has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · json-codec-helpers.decodeValue (cognitive 16) · ×1
  • json-codec-helpers.decodeValue (cognitive 16) packages/3-targets/mongo/1-target/src/core/json-codec-helpers.ts:161 — json-codec-helpers.decodeValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12, ternaries 2 (3 pts), boolean chains 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
D2 · Cognitive Complexity · resolve-value.resolveValue (cognitive 16) · ×1
  • resolve-value.resolveValue (cognitive 16) packages/3-targets/mongo/2-adapter/src/resolve-value.ts:62 — resolve-value.resolveValue has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (10 pts), error handling 1 (4 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · MysqlMigrationRunner.#applyOperations (cognitive 16) · ×1
  • MysqlMigrationRunner.#applyOperations (cognitive 16) packages/3-targets/mysql/1-target/src/core/migrations/runner.ts:234 — MysqlMigrationRunner.#applyOperations has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (14 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · control-adapter.sqliteRenderDdlColumnDefault (cognitive 16) · ×1
  • control-adapter.sqliteRenderDdlColumnDefault (cognitive 16) packages/3-targets/sqlite/2-adapter/src/core/control-adapter.ts:857 — control-adapter.sqliteRenderDdlColumnDefault has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), ternaries 2 (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.
D2 · Cognitive Complexity · index.runSqliteCodecProjection (cognitive 16) · ×1
  • index.runSqliteCodecProjection (cognitive 16) packages/3-targets/sqlite/4-codec-testkit/src/index.ts:310 — index.runSqliteCodecProjection has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (10 pts), error handling 3, ternaries 2 (3 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
D2 · Cognitive Complexity · audit-notice.collectRuntimeRedistributedSet (cognitive 16) · ×1
  • audit-notice.collectRuntimeRedistributedSet (cognitive 16) scripts/audit-notice.mjs:92 — audit-notice.collectRuntimeRedistributedSet has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 3, error handling 2, loops 2 (nesting depth added 4). Most of this is not in the body itself: 3 of the 16 points are its own statements and the rest belongs to one function item inside it that branches (visit). 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.
D2 · Cognitive Complexity · lint-no-contract-cast.walk (cognitive 16) · ×1
  • lint-no-contract-cast.walk (cognitive 16) scripts/lint-no-contract-cast.mjs:150 — lint-no-contract-cast.walk has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 2 (3 pts), loops 2 (3 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.
D2 · Cognitive Complexity · validate-rules.parseFrontmatter (cognitive 16) · ×1
  • validate-rules.parseFrontmatter (cognitive 16) scripts/validate-rules.mjs:55 — validate-rules.parseFrontmatter has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 1, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D2 · Cognitive Complexity · render-review-state.parseCliArgs (cognitive 16) · ×1
  • render-review-state.parseCliArgs (cognitive 16) skills-contrib/review-fetch-phase/scripts/render-review-state.mjs:29 — render-review-state.parseCliArgs has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, loops 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D5 · Coupling · Unstable project @internal/adapter-mongo · ×1
  • Unstable project @internal/adapter-mongo — @internal/adapter-mongo has instability 0.95 with 1 dependents.
D5 · Coupling · Unstable project @internal/adapter-mysql · ×1
  • Unstable project @internal/adapter-mysql — @internal/adapter-mysql has instability 0.92 with 1 dependents.
D5 · Coupling · Unstable project @internal/adapter-sqlite · ×1
  • Unstable project @internal/adapter-sqlite — @internal/adapter-sqlite has instability 0.89 with 2 dependents.
D5 · Coupling · Unstable project @internal/driver-mongo · ×1
  • Unstable project @internal/driver-mongo — @internal/driver-mongo has instability 0.83 with 1 dependents.
D5 · Coupling · Unstable project @internal/driver-mysql · ×1
  • Unstable project @internal/driver-mysql — @internal/driver-mysql has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project @internal/driver-sqlite · ×1
  • Unstable project @internal/driver-sqlite — @internal/driver-sqlite has instability 0.89 with 1 dependents.
D5 · Coupling · Unstable project @internal/family-mongo · ×1
  • Unstable project @internal/family-mongo — @internal/family-mongo has instability 0.83 with 3 dependents.
D5 · Coupling · Unstable project @internal/language-server · ×1
  • Unstable project @internal/language-server — @internal/language-server has instability 0.86 with 1 dependents.
D5 · Coupling · Unstable project @internal/mongo-contract-prisma6 · ×1
  • Unstable project @internal/mongo-contract-prisma6 — @internal/mongo-contract-prisma6 has instability 0.90 with 1 dependents.
D5 · Coupling · Unstable project @internal/mongo-emitter · ×1
  • Unstable project @internal/mongo-emitter — @internal/mongo-emitter has instability 0.83 with 1 dependents.
D5 · Coupling · Unstable project @internal/mongo-orm · ×1
  • Unstable project @internal/mongo-orm — @internal/mongo-orm has instability 0.88 with 1 dependents.
D5 · Coupling · Unstable project @internal/mongo-runtime · ×1
  • Unstable project @internal/mongo-runtime — @internal/mongo-runtime has instability 0.82 with 2 dependents.
D5 · Coupling · Unstable project @internal/postgres · ×1
  • Unstable project @internal/postgres — @internal/postgres has instability 0.94 with 1 dependents.
D5 · Coupling · Unstable project @internal/sql-contract-emitter · ×1
  • Unstable project @internal/sql-contract-emitter — @internal/sql-contract-emitter has instability 0.83 with 1 dependents.
D5 · Coupling · Unstable project @internal/sql-contract-prisma7 · ×1
  • Unstable project @internal/sql-contract-prisma7 — @internal/sql-contract-prisma7 has instability 0.90 with 1 dependents.
D5 · Coupling · Unstable project @internal/target-mongo · ×1
  • Unstable project @internal/target-mongo — @internal/target-mongo has instability 0.88 with 2 dependents.
D5 · Coupling · Unstable project @internal/target-mysql · ×1
  • Unstable project @internal/target-mysql — @internal/target-mysql has instability 0.81 with 3 dependents.
D5 · Coupling · Unstable project @internal/target-sqlite · ×1
  • Unstable project @internal/target-sqlite — @internal/target-sqlite has instability 0.82 with 3 dependents.
D6 · Cohesion (LCOM4) · Low cohesion · ×1
  • Low cohesion: MysqlControlAdapter (LCOM4 5) packages/3-targets/mysql/2-adapter/src/core/migrations/control-adapter.ts:55 — MysqlControlAdapter's methods fall into 5 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 5 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.
P12 · CI test-gate honesty · Test failure does not fail the CI gate · ×1
  • Test failure does not fail the CI gate REDACTED:215 — `continue-on-error: true` lets the step or job that runs `pnpm coverage:packages --reporter=default --reporter=github-actions --reporter=blob --shard=${{ matrix.index }}/4` fail without failing the pipeline — the suite can go red and the change still merges. Remove it from the test step, or quarantine the specific failing tests instead.
P12 · CI test-gate honesty · Runner config excludes tests no gate runs · ×1
  • Runner config excludes tests no gate runs test/integration/vitest.config.ts:81 — `test/packaging/**` removes 17 test(s) in 2 file(s) (e.g. `test/integration/test/packaging/extension-tarball.test.ts`, `test/integration/test/packaging/facade-tarball.test.ts`) from what vitest collects, and no other runner or CI command runs them — they are dead tests. Run them (another runner, project or job), or delete them.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (233 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (233 clone groups) packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:142 — 233 duplicated blocks under packages/3-targets/ have copies in at least two of the sibling directories mongo, mysql, postgres, sqlite — 183 of them are reported below, and 50 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 233 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 233 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 233 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (139 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (139 clone groups) packages/2-mongo-family/2-authoring/contract-prisma6/src/provider.ts:18 — 139 duplicated blocks under packages/ have copies in at least two of the sibling directories 0-config, 1-framework, 2-mongo-family, 2-sql-family, 3-extensions, 3-targets — 66 of them are reported below, and 73 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 139 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 139 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 139 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (52 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (52 clone groups) REDACTED:22 — 52 duplicated blocks under the repository root have copies in at least two of the sibling directories apps, packages, scripts, skills, skills-contrib, upgrade-instructions — 47 of them are reported below, and 5 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 52 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 52 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 52 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 6 sibling directories (15 clone groups) · ×1
  • Duplication concentrated across 6 sibling directories (15 clone groups) packages/3-extensions/pgvector/src/exports/control.ts:91 — 15 duplicated blocks under packages/3-extensions/ have copies in at least two of the sibling directories arktype-json, citext, paradedb, pgvector, postgis, supabase — 9 of them are reported below, and 6 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 15 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 15 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 15 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 2 sibling directories (12 clone groups) · ×1
  • Duplication concentrated across 2 sibling directories (12 clone groups) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:13 — 12 of the duplicated blocks reported below have copies in at least two of the sibling directories app, extension under skills/prisma-8/upgrading/. That concentration is one structural fact, not 12 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 12 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (10 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (10 clone groups) packages/1-framework/3-tooling/cli/src/control-api/operations/migrate.ts:647 — 10 duplicated blocks under packages/1-framework/3-tooling/ have copies in at least two of the sibling directories cli, config-loader, language-server, migration — 1 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 4 sibling directories (9 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (9 clone groups) skills-contrib/review-fetch-phase/scripts/extract-review-targets.mjs:10 — 9 duplicated blocks under skills-contrib/ have copies in at least two of the sibling directories github-review-iteration, review-fetch-phase, review-implement-phase, review-triage-phase — 8 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 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 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 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Duplication concentrated across 3 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (7 clone groups) packages/1-framework/3-tooling/cli/src/orm/contract/infer.ts:100 — 7 duplicated blocks under packages/1-framework/3-tooling/cli/src/orm/ have copies in at least two of the sibling directories contract, db, migration — 5 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 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 · Duplication concentrated across 4 sibling directories (7 clone groups) · ×1
  • Duplication concentrated across 4 sibling directories (7 clone groups) skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts:27 — 7 of the duplicated blocks reported below have copies in at least two of the sibling directories 0.11-to-0.12, 0.12-to-0.13, 8.0.0-rc.18-to-8.0.0-rc.19, 8.0.0-rc.21-to-8.0.0-rc.22 under skills/prisma-8/upgrading/app/upgrades/. 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 · Duplication concentrated across 3 sibling directories (5 clone groups) · ×1
  • Duplication concentrated across 3 sibling directories (5 clone groups) packages/2-mongo-family/4-query/query-ast/src/ddl-commands.ts:108 — 5 duplicated blocks under packages/2-mongo-family/ have copies in at least two of the sibling directories 1-foundation, 4-query, 6-transport — 4 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 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 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 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication · Wholesale file copy (1668 identical lines × 2 files) · ×1
  • Wholesale file copy (1668 identical lines × 2 files) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:13 — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:13 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:13 — these 2 files are line-for-line copies of one another — 1668 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (1041 identical lines × 4 files) · ×1
  • Wholesale file copy (1041 identical lines × 4 files) REDACTED:22 — REDACTED:22 · REDACTED:22 · REDACTED:22 · REDACTED:22 — these 4 files are line-for-line copies of one another — 1041 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (797 identical lines × 2 files) · ×1
  • Wholesale file copy (797 identical lines × 2 files) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:13 — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:13 · upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:13 — these 2 files are line-for-line copies of one another — 797 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (765 identical lines × 4 files) · ×1
  • Wholesale file copy (765 identical lines × 4 files) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:13 — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:13 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:13 · upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:13 · upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:13 — these 4 files are line-for-line copies of one another — 765 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (737 identical lines × 3 files) · ×1
  • Wholesale file copy (737 identical lines × 3 files) REDACTED:22 — REDACTED:22 · REDACTED:22 · REDACTED:22 — these 3 files are line-for-line copies of one another — 737 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (549 identical lines × 2 files) · ×1
  • Wholesale file copy (549 identical lines × 2 files) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:11 — upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/app/scripts/remove-nocheck/remove-nocheck.ts:11 · upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:11 — these 2 files are line-for-line copies of one another — 549 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (415 identical lines × 2 files) · ×1
  • Wholesale file copy (415 identical lines × 2 files) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:19 — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:19 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:19 — these 2 files are line-for-line copies of one another — 415 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (257 identical lines × 2 files) · ×1
  • Wholesale file copy (257 identical lines × 2 files) upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts:17 — upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts:17 · upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:17 — these 2 files are line-for-line copies of one another — 257 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 (256 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (256 matched lines × 2 locations) packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:142 — packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:142 · packages/3-targets/sqlite/1-target/src/core/migrations/runner.ts:62 — the two spans are one implementation copied and then locally edited — 1537 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (204 identical lines × 2 files) · ×1
  • Wholesale file copy (204 identical lines × 2 files) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.22-to-8.0.0-rc.23/scripts/mongo-index-names/mongo-index-names.ts:11 — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.22-to-8.0.0-rc.23/scripts/mongo-index-names/mongo-index-names.ts:11 · upgrade-instructions/releases/8.0.0-rc.22-to-8.0.0-rc.23/sources/mongo-index-names/app/scripts/mongo-index-names.ts:11 — these 2 files are line-for-line copies of one another — 204 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 (202 lines × 3 locations) · ×1
  • Duplicated block (202 lines × 3 locations) packages/3-targets/postgres/1-target/src/core/stored-inet.ts:28 — packages/3-targets/postgres/1-target/src/core/stored-inet.ts:28 · skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:645 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:645 — 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.
R10 · Code Duplication · Wholesale file copy (200 identical lines × 2 files) · ×1
  • Wholesale file copy (200 identical lines × 2 files) REDACTED:14 — REDACTED:14 · REDACTED:14 — these 2 files are line-for-line copies of one another — 200 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 (185 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (185 matched lines × 2 locations) packages/3-targets/postgres/2-adapter/src/core/sql-renderer.ts:199 — packages/3-targets/postgres/2-adapter/src/core/sql-renderer.ts:199 · packages/3-targets/sqlite/2-adapter/src/core/adapter.ts:196 — the two spans are one implementation copied and then locally edited — 1111 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (179 identical lines × 2 files) · ×1
  • Wholesale file copy (179 identical lines × 2 files) skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:30 — skills/prisma-8/upgrading/app/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:30 · skills/prisma-8/upgrading/extension/upgrades/0.13-to-0.14/migration-op-factories-to-methods.ts:30 — these 2 files are line-for-line copies of one another — 179 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (177 identical lines × 4 files) · ×1
  • Wholesale file copy (177 identical lines × 4 files) scripts/codemods/rewrite-sql-strings.mjs:14 — scripts/codemods/rewrite-sql-strings.mjs:14 · skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.17-to-8.0.0-rc.18/scripts/sql-expression-literals-psl/rewrite-sql-strings.mjs:14 · upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/app/scripts/rewrite-sql-strings.mjs:14 · upgrade-instructions/releases/8.0.0-rc.17-to-8.0.0-rc.18/sources/sql-expression-literals-psl/extension/scripts/rewrite-sql-strings.mjs:14 — these 4 files are line-for-line copies of one another — 177 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 (175 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (175 matched lines × 2 locations) packages/1-framework/3-tooling/cli/src/orm/db/init.ts:38 — packages/1-framework/3-tooling/cli/src/orm/db/init.ts:38 · packages/1-framework/3-tooling/cli/src/orm/db/update.ts:77 — the two spans are one implementation copied and then locally edited — 963 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (173 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (173 matched lines × 2 locations) packages/3-targets/postgres/1-target/src/core/migrations/operations/stored-values.ts:106 — packages/3-targets/postgres/1-target/src/core/migrations/operations/stored-values.ts:106 · packages/3-targets/sqlite/1-target/src/core/migrations/operations/stored-values.ts:71 — the two spans are one implementation copied and then locally edited — 1036 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (166 identical lines × 2 files) · ×1
  • Wholesale file copy (166 identical lines × 2 files) REDACTED:83 — REDACTED:83 · REDACTED:83 — these 2 files are line-for-line copies of one another — 166 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 (160 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (160 matched lines × 2 locations) packages/3-targets/postgres/1-target/src/core/codec-descriptor.ts:97 — packages/3-targets/postgres/1-target/src/core/codec-descriptor.ts:97 · packages/3-targets/sqlite/1-target/src/core/codec-descriptor.ts:50 — the two spans are one implementation copied and then locally edited — 966 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (159 identical lines × 2 files) · ×1
  • Wholesale file copy (159 identical lines × 2 files) skills/prisma-8/upgrading/app/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts:79 — skills/prisma-8/upgrading/app/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts:79 · skills/prisma-8/upgrading/extension/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts:79 — these 2 files are line-for-line copies of one another — 159 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 (151 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (151 matched lines × 2 locations) packages/3-targets/mysql/2-adapter/src/core/sql-renderer.ts:321 — packages/3-targets/mysql/2-adapter/src/core/sql-renderer.ts:321 · packages/3-targets/sqlite/2-adapter/src/core/adapter.ts:388 — the two spans are one implementation copied and then locally edited — 1018 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (147 identical lines × 5 files) · ×1
  • Wholesale file copy (147 identical lines × 5 files) scripts/codemods/add-model-map.mjs:22 — scripts/codemods/add-model-map.mjs:22 · skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs:22 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs:22 · upgrade-instructions/releases/8.0.0-rc.11-to-8.0.0-rc.12/sources/psl-verbatim-table-names/app/scripts/add-model-map.mjs:22 · +1 more site(s) not listed — these 5 files are line-for-line copies of one another — 147 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Wholesale file copy (147 identical lines × 2 files) · ×1
  • Wholesale file copy (147 identical lines × 2 files) REDACTED:67 — REDACTED:67 · REDACTED:67 — these 2 files are line-for-line copies of one another — 147 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 (136 lines × 3 locations) · ×1
  • Duplicated block (136 lines × 3 locations) REDACTED:77 — REDACTED:77 · REDACTED:77 · REDACTED:32 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (135 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (135 matched lines × 2 locations) packages/3-targets/mongo/2-adapter/src/lowering.ts:326 — packages/3-targets/mongo/2-adapter/src/lowering.ts:326 · packages/3-targets/mongo/2-adapter/src/lowering.ts:555 — the two spans are one implementation copied and then locally edited — 1094 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Wholesale file copy (135 identical lines × 2 files) · ×1
  • Wholesale file copy (135 identical lines × 2 files) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:2 — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:2 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:2 — these 2 files are line-for-line copies of one another — 135 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 (134 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (134 matched lines × 2 locations) skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts:27 — skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts:27 · skills/prisma-8/upgrading/app/upgrades/0.12-to-0.13/re-emit-mti-variant-link-columns.ts:31 — the two spans are one implementation copied and then locally edited — 987 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (131 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (131 matched lines × 2 locations) packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:497 — packages/3-targets/postgres/1-target/src/core/migrations/runner.ts:497 · packages/3-targets/sqlite/1-target/src/core/migrations/runner.ts:483 — the two spans are one implementation copied and then locally edited — 765 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block with local edits (128 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (128 matched lines × 2 locations) packages/2-mongo-family/2-authoring/contract-prisma6/src/provider.ts:18 — packages/2-mongo-family/2-authoring/contract-prisma6/src/provider.ts:18 · packages/2-sql-family/2-authoring/contract-prisma7/src/provider.ts:22 — the two spans are one implementation copied and then locally edited — 740 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (128 lines × 2 locations) · ×1
  • Duplicated block (128 lines × 2 locations) packages/3-targets/mysql/9-facade/src/contract/define-contract.ts:42 — packages/3-targets/mysql/9-facade/src/contract/define-contract.ts:42 · packages/3-targets/sqlite/9-facade/src/contract/define-contract.ts:42 — 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.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 172, cognitive 257) · ×1
  • Complex function main (cyclomatic 172, cognitive 257) examples/prisma-8-demo/src/main.ts:235 — main has cyclomatic complexity 172 and cognitive complexity 257; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function buildModelNodeFromPsl (cyclomatic 93, cognitive 200) · ×1
  • Complex function buildModelNodeFromPsl (cyclomatic 93, cognitive 200) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:615 — buildModelNodeFromPsl has cyclomatic complexity 93 and cognitive complexity 200; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function readField (cyclomatic 91, cognitive 115) · ×1
  • Complex function readField (cyclomatic 91, cognitive 115) packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:1183 — readField has cyclomatic complexity 91 and cognitive complexity 115; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function buildGrid (cyclomatic 84, cognitive 156) · ×1
  • Complex function buildGrid (cyclomatic 84, cognitive 156) packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts:301 — buildGrid has cyclomatic complexity 84 and cognitive complexity 156; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function interpretPslDocumentToSqlContract (cyclomatic 82, cognitive 138) · ×1
  • Complex function interpretPslDocumentToSqlContract (cyclomatic 82, cognitive 138) packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:2170 — interpretPslDocumentToSqlContract has cyclomatic complexity 82 and cognitive complexity 138; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function executeMigrationPlanCommandInner (cyclomatic 81, cognitive 118) · ×1
  • Complex function executeMigrationPlanCommandInner (cyclomatic 81, cognitive 118) packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts:510 — executeMigrationPlanCommandInner has cyclomatic complexity 81 and cognitive complexity 118; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function lowerStage (cyclomatic 71, cognitive 89) · ×1
  • Complex function lowerStage (cyclomatic 71, cognitive 89) packages/3-targets/mongo/2-adapter/src/lowering.ts:252 — lowerStage has cyclomatic complexity 71 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function handler (cyclomatic 70, cognitive 89) · ×1
  • Complex function handler (cyclomatic 70, cognitive 89) packages/1-framework/3-tooling/cli/src/orm/migration/status.ts:293 — handler has cyclomatic complexity 70 and cognitive complexity 89; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function structuralLowerStage (cyclomatic 70, cognitive 86) · ×1
  • Complex function structuralLowerStage (cyclomatic 70, cognitive 86) packages/3-targets/mongo/2-adapter/src/lowering.ts:489 — structuralLowerStage has cyclomatic complexity 70 and cognitive complexity 86; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R2 · Cyclomatic Complexity · Complex function main (cyclomatic 65, cognitive 100) · ×1
  • Complex function main (cyclomatic 65, cognitive 100) skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:978 — main has cyclomatic complexity 65 and cognitive complexity 100; 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 · packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts · ×1
  • packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts: 2945 lines of code packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts:1 — packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts has 2945 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-extensions/sql-orm-client/src/collection.ts · ×1
  • packages/3-extensions/sql-orm-client/src/collection.ts: 2943 lines of code packages/3-extensions/sql-orm-client/src/collection.ts:1 — packages/3-extensions/sql-orm-client/src/collection.ts has 2943 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts · ×1
  • packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts: 2823 lines of code packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts:1 — packages/2-sql-family/2-authoring/contract-psl/src/interpreter.ts has 2823 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts · ×1
  • packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts: 2510 lines of code packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts:1 — packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts has 2510 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 · skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts · ×1
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts: 2277 lines of code skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1 — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts has 2277 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 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts · ×1
  • skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts: 2277 lines of code skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts:1 — skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/remove-nocheck/remove-nocheck.ts has 2277 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-extensions/sql-orm-client/src/types.ts · ×1
  • packages/3-extensions/sql-orm-client/src/types.ts: 2240 lines of code packages/3-extensions/sql-orm-client/src/types.ts:1 — packages/3-extensions/sql-orm-client/src/types.ts has 2240 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts · ×1
  • packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts: 2111 lines of code packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts:1 — packages/3-targets/postgres/2-adapter/src/core/control-adapter.ts has 2111 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts · ×1
  • packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts: 2096 lines of code packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:1 — packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts has 2096 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-sql-family/5-runtime/src/sql-runtime.ts · ×1
  • packages/2-sql-family/5-runtime/src/sql-runtime.ts: 1837 lines of code packages/2-sql-family/5-runtime/src/sql-runtime.ts:1 — packages/2-sql-family/5-runtime/src/sql-runtime.ts has 1837 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts · ×1
  • packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts: 1830 lines of code packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts:1 — packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts has 1830 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-targets/sqlite/1-target/src/core/migrations/op-factory-call.ts · ×1
  • packages/3-targets/sqlite/1-target/src/core/migrations/op-factory-call.ts: 1710 lines of code packages/3-targets/sqlite/1-target/src/core/migrations/op-factory-call.ts:1 — packages/3-targets/sqlite/1-target/src/core/migrations/op-factory-call.ts has 1710 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-mongo-family/2-authoring/contract-ts/src/contract-builder.ts · ×1
  • packages/2-mongo-family/2-authoring/contract-ts/src/contract-builder.ts: 1670 lines of code packages/2-mongo-family/2-authoring/contract-ts/src/contract-builder.ts:1 — packages/2-mongo-family/2-authoring/contract-ts/src/contract-builder.ts has 1670 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-targets/postgres/1-target/src/core/codecs.ts · ×1
  • packages/3-targets/postgres/1-target/src/core/codecs.ts: 1606 lines of code packages/3-targets/postgres/1-target/src/core/codecs.ts:1 — packages/3-targets/postgres/1-target/src/core/codecs.ts has 1606 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts · ×1
  • packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts: 1585 lines of code packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts:1 — packages/2-mongo-family/2-authoring/contract-prisma6/src/interpreter.ts has 1585 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts · ×1
  • packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts: 1563 lines of code packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts:1 — packages/1-framework/1-core/framework-components/src/shared/framework-authoring.ts has 1563 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts · ×1
  • packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts: 1535 lines of code packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts:1 — packages/2-sql-family/2-authoring/contract-prisma7/src/interpreter.ts has 1535 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-sql-family/2-authoring/contract-ts/src/contract-types.ts · ×1
  • packages/2-sql-family/2-authoring/contract-ts/src/contract-types.ts: 1488 lines of code packages/2-sql-family/2-authoring/contract-ts/src/contract-types.ts:1 — packages/2-sql-family/2-authoring/contract-ts/src/contract-types.ts has 1488 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts · ×1
  • packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts: 1463 lines of code packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts:1 — packages/2-mongo-family/2-authoring/contract-psl/src/interpreter.ts has 1463 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 · REDACTED · ×1
  • REDACTED: 1389 lines of code REDACTED:1 — REDACTED has 1389 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 · REDACTED · ×1
  • REDACTED: 1389 lines of code REDACTED:1 — REDACTED has 1389 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 · REDACTED · ×1
  • REDACTED: 1389 lines of code REDACTED:1 — REDACTED has 1389 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 · REDACTED · ×1
  • REDACTED: 1389 lines of code REDACTED:1 — REDACTED has 1389 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-mongo-family/5-query-builders/orm/src/collection.ts · ×1
  • packages/2-mongo-family/5-query-builders/orm/src/collection.ts: 1385 lines of code packages/2-mongo-family/5-query-builders/orm/src/collection.ts:1 — packages/2-mongo-family/5-query-builders/orm/src/collection.ts has 1385 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-extensions/sql-orm-client/src/query-plan-select.ts · ×1
  • packages/3-extensions/sql-orm-client/src/query-plan-select.ts: 1381 lines of code packages/3-extensions/sql-orm-client/src/query-plan-select.ts:1 — packages/3-extensions/sql-orm-client/src/query-plan-select.ts has 1381 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-extensions/sql-orm-client/src/mutation-executor.ts · ×1
  • packages/3-extensions/sql-orm-client/src/mutation-executor.ts: 1367 lines of code packages/3-extensions/sql-orm-client/src/mutation-executor.ts:1 — packages/3-extensions/sql-orm-client/src/mutation-executor.ts has 1367 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-sql-family/1-core/contract/src/validators.ts · ×1
  • packages/2-sql-family/1-core/contract/src/validators.ts: 1320 lines of code packages/2-sql-family/1-core/contract/src/validators.ts:1 — packages/2-sql-family/1-core/contract/src/validators.ts has 1320 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts · ×1
  • packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts: 1279 lines of code packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts:1 — packages/2-sql-family/2-authoring/contract-ts/src/contract-lowering.ts has 1279 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-targets/postgres/1-target/src/core/migrations/planner.ts · ×1
  • packages/3-targets/postgres/1-target/src/core/migrations/planner.ts: 1278 lines of code packages/3-targets/postgres/1-target/src/core/migrations/planner.ts:1 — packages/3-targets/postgres/1-target/src/core/migrations/planner.ts has 1278 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts · ×1
  • packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts: 1223 lines of code packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts:1 — packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts has 1223 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts · ×1
  • packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts: 1212 lines of code packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts:1 — packages/3-targets/postgres/1-target/src/core/migrations/issue-planner.ts has 1212 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts · ×1
  • packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts: 1157 lines of code packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts:1 — packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts has 1157 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/2-sql-family/9-family/src/core/control-instance.ts · ×1
  • packages/2-sql-family/9-family/src/core/control-instance.ts: 1154 lines of code packages/2-sql-family/9-family/src/core/control-instance.ts:1 — packages/2-sql-family/9-family/src/core/control-instance.ts has 1154 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/1-framework/2-authoring/psl-parser/src/binder.ts · ×1
  • packages/1-framework/2-authoring/psl-parser/src/binder.ts: 1121 lines of code packages/1-framework/2-authoring/psl-parser/src/binder.ts:1 — packages/1-framework/2-authoring/psl-parser/src/binder.ts has 1121 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 · skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts · ×1
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts: 1121 lines of code skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:1 — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts has 1121 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 · skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts · ×1
  • skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts: 1121 lines of code skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts:1 — skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.19-to-8.0.0-rc.20/scripts/expand-type-aliases/expand-type-aliases.ts has 1121 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 · skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts · ×1
  • skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts: 1099 lines of code skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:1 — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts has 1099 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 · upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts · ×1
  • upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts: 1099 lines of code upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:1 — upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts has 1099 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/1-framework/3-tooling/cli/src/utils/cli-errors.ts · ×1
  • packages/1-framework/3-tooling/cli/src/utils/cli-errors.ts: 1096 lines of code packages/1-framework/3-tooling/cli/src/utils/cli-errors.ts:1 — packages/1-framework/3-tooling/cli/src/utils/cli-errors.ts has 1096 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files · packages/3-targets/postgres/1-target/src/core/migrations/postgres-migration.ts · ×1
  • packages/3-targets/postgres/1-target/src/core/migrations/postgres-migration.ts: 1081 lines of code packages/3-targets/postgres/1-target/src/core/migrations/postgres-migration.ts:1 — packages/3-targets/postgres/1-target/src/core/migrations/postgres-migration.ts has 1081 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling · The declared test suite includes a file that cannot be loaded · ×1
  • The declared test suite includes a file that cannot be loaded packages/1-framework/3-tooling/cli/recordings/fixtures/prisma.config.ts:7 — This repository declares test tooling, and the ✓ above records that declaration — but packages/1-framework/3-tooling/cli/recordings/fixtures/prisma.config.ts and 12 other test file(s) in this workspace cannot be loaded at all: it imports a module that names no file in this repository, so the runner throws while collecting it and none of its cases execute. The wiring is present and the suite it points at does not run as written, which is why the tooling tick must not be read as a statement that the tests pass. Fix the unloadable file(s) — each one is reported with its failing import under Test Coverage — then the declared script exercises what it claims to.
R7 · Dead Code · Dead file (~229 LoC) · ×1
  • Dead file (~229 LoC) skills/prisma-8/upgrading/app/upgrades/0.12-to-0.13/re-emit-mti-variant-link-columns.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~223 LoC) · ×1
  • Dead file (~223 LoC) skills/prisma-8/upgrading/extension/upgrades/0.11-to-0.12/regenerate-extension-public-baseline.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~202 LoC) · ×1
  • Dead file (~202 LoC) skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-closed-mongo-contracts.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~201 LoC) · ×1
  • Dead file (~201 LoC) skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-domain-namespaced-contracts.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~198 LoC) · ×1
  • Dead file (~198 LoC) skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~106 LoC) · ×1
  • Dead file (~106 LoC) examples/mongo-demo/scripts/cache-demo.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~89 LoC) · ×1
  • Dead file (~89 LoC) projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/probe-mongoquery.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~42 LoC) · ×1
  • Dead file (~42 LoC) examples/retail-store/src/components/ui/dropdown-menu.tsx — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~30 LoC) · ×1
  • Dead file (~30 LoC) examples/prisma-8-demo/src/queries/dml-operations.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~26 LoC) · ×1
  • Dead file (~26 LoC) examples/supabase/src/session-queries.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~20 LoC) · ×1
  • Dead file (~20 LoC) examples/bundle-size/src/postgres-worker/worker-emit.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~18 LoC) · ×1
  • Dead file (~18 LoC) projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/contract-verbose.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/probe.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
R7 · Dead Code · Dead file (~15 LoC) · ×1
  • Dead file (~15 LoC) examples/supabase/src/profile-queries.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~14 LoC) · ×1
  • Dead file (~14 LoC) projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/contract-facade.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/probe.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
R7 · Dead Code · Dead file (~12 LoC) · ×1
  • Dead file (~12 LoC) packages/1-framework/3-tooling/cli/src/utils/migration-types.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~11 LoC) · ×1
  • Dead file (~11 LoC) examples/prisma-8-demo/isolated-programs/facade-library.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R7 · Dead Code · Dead file (~5 LoC) · ×1
  • Dead file (~5 LoC) examples/prisma-8-demo/isolated-programs/contract-only-library.ts — no import path from any entry point (1352 application, 823 tooling, 4409 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
R8 · Dependency Hygiene · Unused dependency '@cursor/sdk' · ×1
  • Unused dependency '@cursor/sdk' — 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.
R8 · Dependency Hygiene · Unused dependency 'tslib' · ×1
  • Unused dependency 'tslib' — 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.
R8 · Dependency Hygiene · Unused dependency '@codingame/monaco-vscode-textmate-service-override' · ×1
  • Unused dependency '@codingame/monaco-vscode-textmate-service-override' — Declared in apps/lsp-playground/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.
X2 · Cancellation propagation · Async function without AbortSignal · ×1
  • Async function without AbortSignal: loadRuntimeConfig REDACTED:105 — `loadRuntimeConfig` 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 })`.
Minor — 695 finding(s)
D20 · ADR Quality · ADR lacks an enforcement field · ×235
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 001 - Migrations as Edges.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 002 - Plans are Immutable.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 003 - One Query One Statement.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 004 - Storage Hash vs Profile Hash.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 005 - Thin Core Fat Targets.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 006 - Dual Authoring Modes.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 007 - Types Only Emission.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 008 - Dev Auto Emit CI Explicit Emit.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 009 - Deterministic Naming Scheme.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 010 - Canonicalization Rules.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 011 - Unified Plan Model.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 012 - Raw SQL Escape Hatch.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 013 - Lane Agnostic Plan Identity.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 014 - Runtime Hook API.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 015 - ORM as Optional Extension.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 016 - Adapter SPI for Lowering.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 017 - Extension Compatibility Policy.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 018 - Plan Annotations Schema.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 019 - TypedSQL as Separate CLI.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 020 - Result Typing Rules.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 021 - Contract Marker Storage.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 022 - Lint Rule Taxonomy.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 023 - Budget Evaluation.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 024 - Telemetry Schema.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • ADR lacks an enforcement field docs/architecture docs/adrs/ADR 025 - Plan Caching Memoization.md:1 — Add an `enforcement:` frontmatter field or a plain `Enforcement:` header line (prose/test/analyzer/not-applicable) to make the rung explicit — the other ADRs in this repo already declare one.
  • + 210 more in this group — see findings.md.
D7 · Architectural Integrity · Classify ADR enforcement · ×235
  • Classify ADR enforcement: ADR 001 — Migrations as Edges docs/architecture docs/adrs/ADR 001 - Migrations as Edges.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 002 — Plans are Immutable docs/architecture docs/adrs/ADR 002 - Plans are Immutable.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 003 — One Query → One Statement docs/architecture docs/adrs/ADR 003 - One Query One Statement.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 004 — Storage Hash vs Profile Hash (formerly “core hash”) docs/architecture docs/adrs/ADR 004 - Storage Hash vs Profile Hash.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 005 — Thin Core, Fat Targets docs/architecture docs/adrs/ADR 005 - Thin Core Fat Targets.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 006 — Dual Authoring Modes (PSL-first and TS-first) with a Single Canonical Artifact docs/architecture docs/adrs/ADR 006 - Dual Authoring Modes.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 007 — Types-Only Emission and No Runtime Client Codegen docs/architecture docs/adrs/ADR 007 - Types Only Emission.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 008 — Dev Auto-Emit, CI Explicit Emit docs/architecture docs/adrs/ADR 008 - Dev Auto Emit CI Explicit Emit.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 009 — Deterministic Naming Scheme for Constraints docs/architecture docs/adrs/ADR 009 - Deterministic Naming Scheme.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 010 — Canonicalization Rules for contract.json docs/architecture docs/adrs/ADR 010 - Canonicalization Rules.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 011 — Unified Plan model across lanes docs/architecture docs/adrs/ADR 011 - Unified Plan Model.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 012 — Raw SQL escape hatch with required annotations docs/architecture docs/adrs/ADR 012 - Raw SQL Escape Hatch.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 013 — Lane-agnostic Plan identity and hashing docs/architecture docs/adrs/ADR 013 - Lane Agnostic Plan Identity.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 014 — Runtime hook API v1 (lane-neutral) docs/architecture docs/adrs/ADR 014 - Runtime Hook API.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 015 — ORM as an optional extension over the DSL docs/architecture docs/adrs/ADR 015 - ORM as Optional Extension.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 016 — Adapter SPI for lowering relational AST docs/architecture docs/adrs/ADR 016 - Adapter SPI for Lowering.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 017 — Extension and Alternate Runtime Compatibility Policy docs/architecture docs/adrs/ADR 017 - Extension Compatibility Policy.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 018 — Plan Annotations Schema and Validation docs/architecture docs/adrs/ADR 018 - Plan Annotations Schema.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 019 — TypedSQL as a Separate CLI that Emits Plan Factories docs/architecture docs/adrs/ADR 019 - TypedSQL as Separate CLI.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 020 — Result Typing and Projection Inference Rules docs/architecture docs/adrs/ADR 020 - Result Typing Rules.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 021 — Contract marker storage & verification modes docs/architecture docs/adrs/ADR 021 - Contract Marker Storage.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 022 — Lint rule taxonomy & configuration model docs/architecture docs/adrs/ADR 022 - Lint Rule Taxonomy.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 023 — Budget evaluation & EXPLAIN policy docs/architecture docs/adrs/ADR 023 - Budget Evaluation.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 024 — Telemetry schema & privacy docs/architecture docs/adrs/ADR 024 - Telemetry Schema.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • Classify ADR enforcement: ADR 025 — Plan caching & memoization in runtime docs/architecture docs/adrs/ADR 025 - Plan Caching Memoization.md — This record carries no `enforcement:` field, so nothing says whether the decision is checked by anything or is upheld by convention alone — and an unclassified record is counted as UNENFORCED in this dimension's score, which is the same bucket as a rule known to have no check behind it. If this is a mechanizable rule, add an analyzer/test (or `enforcement: analyzer|test`); if it's a design decision, mark `enforcement: not-applicable` so it isn't counted as unenforced.
  • + 210 more in this group — see findings.md.
D10 · Test Quality · Mock-dominated test · ×28
  • Mock-dominated test: receives the marker-verification warning when the database has no marker packages/3-targets/sqlite/9-facade/test/sqlite-log.test.ts:31 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: reuses in-flight connect promise for concurrent queries packages/3-targets/postgres/3-driver/test/driver.errors.test.ts:212 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: closes direct client once when close called multiple times packages/3-targets/postgres/3-driver/test/driver.errors.test.ts:283 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: keeps bound direct and pool connect operations as no-ops packages/3-targets/postgres/3-driver/test/driver.prepared.test.ts:258 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: close() leaves a caller-supplied mongoClient to the driver, which keeps it open packages/3-targets/mongo/9-facade/test/mongo.test.ts:313 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: creates its driver on the first use packages/3-targets/mongo/9-facade/test/no-database.test.ts:40 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: an annotated ORM read on a role session is neither served from nor stored in the cache packages/3-extensions/supabase/test/rls-role-binding.integration.test.ts:373 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: receives the marker-verification warning when the database has no marker packages/3-extensions/supabase/test/supabase-log.test.ts:56 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: receives the lints() warning for a read through the auth and storage runtime packages/3-extensions/supabase/test/supabase-log.test.ts:73 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: misses a call when the key holds statement rows, and stores the call result in their place packages/3-extensions/middleware-cache/test/cache-activity.test.ts:127 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: misses a statement when the key holds a call result, and stores the rows in its place packages/3-extensions/middleware-cache/test/cache-activity.test.ts:149 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: does not store the result of a call that missed before an invalidate of its key packages/3-extensions/middleware-cache/test/cache-activity.test.ts:192 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: warns once when it waits only for open activity handles packages/2-sql-family/5-runtime/test/client-activity.test.ts:362 — This test sets up 3 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: warns with CONTRACT.MARKER_MISSING when the marker is absent packages/2-sql-family/5-runtime/test/marker-verification.test.ts:217 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: warns with CONTRACT.MARKER_MISSING when the marker table is missing packages/2-sql-family/5-runtime/test/marker-verification.test.ts:237 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: emits no log when the marker record matches the contract packages/2-sql-family/5-runtime/test/marker-verification.test.ts:253 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: warns with CONTRACT.MARKER_MISMATCH when the storage hash differs packages/2-sql-family/5-runtime/test/marker-verification.test.ts:265 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: warns with CONTRACT.MARKER_MISMATCH when the profile hash differs packages/2-sql-family/5-runtime/test/marker-verification.test.ts:291 — This test sets up 3 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: skips the marker reader entirely when verifyMarker is false packages/2-sql-family/5-runtime/test/marker-verification.test.ts:314 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: emits at most one warning per runtime lifetime regardless of query count packages/2-sql-family/5-runtime/test/marker-verification.test.ts:331 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: single-flights the marker read under concurrent first queries packages/2-sql-family/5-runtime/test/marker-verification.test.ts:348 — This test sets up 4 test doubles (for example `vi.fn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: runs the beforeCompile middleware chain exactly once at prepare time packages/2-sql-family/5-runtime/test/prepared.test.ts:207 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: keeps close() waiting for a transaction on it until the %s packages/2-sql-family/5-runtime/test/raw-connection-seam.test.ts:318 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: is named in the warning close() logs while it waits only for it packages/2-sql-family/5-runtime/test/raw-connection-seam.test.ts:502 — This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • Mock-dominated test: skips beforeCompile for raw execution plans with no AST packages/2-sql-family/5-runtime/test/sql-runtime.test.ts:697 — This test sets up 6 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
  • + 3 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×26
  • Orphaned file packages/1-framework/3-tooling/cli/recordings/config.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 skills/prisma-8/upgrading/extension/upgrades/0.11-to-0.12/regenerate-extension-public-baseline.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/2-sql-family/2-authoring/contract-ts/src/contract-warnings.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/2-mongo-family/1-foundation/mongo-contract/src/ir/mongo-collection-options.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 skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-closed-mongo-contracts.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 skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.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 skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-domain-namespaced-contracts.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/1-framework/0-foundation/utils/src/canonical-stringify.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/1-framework/2-authoring/contract/src/composed-helpers-scaffolding.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/2-sql-family/5-runtime/src/guardrails/raw.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/2-mongo-family/1-foundation/mongo-contract/src/ir/mongo-index-options.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/1-framework/1-core/framework-components/src/meta-builder.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/1-framework/3-tooling/cli/src/utils/publish-contract-artifact-pair.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/3-extensions/postgis/src/types/operation-types.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/3-extensions/paradedb/src/types/operation-types.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/1-framework/0-foundation/utils/src/casts.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/1-framework/3-tooling/migration/src/concatenate-space-apply-inputs.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/1-framework/3-tooling/cli/src/commands/init/reinit-cleanup.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/2-mongo-family/1-foundation/mongo-contract/src/ir/mongo-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.
  • Orphaned file packages/2-mongo-family/1-foundation/mongo-contract/src/ir/mongo-collation-options.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/3-targets/postgres/3-driver/src/named-cursor.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/1-framework/0-foundation/utils/src/hash-content.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file packages/1-framework/1-core/framework-components/src/ir/ir-node.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 projects/facade-import-surface-completion/manual-qa-reports/artefacts/S4-probe/probe-mongoquery.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 skills/prisma-8/upgrading/extension/upgrades/0.11-to-0.12/migrate-contract-testing-imports.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.
  • + 1 more in this group — see findings.md.
X10 · Duplicated predicate · Duplicated predicate · ×25
  • Duplicated predicate packages/2-mongo-family/5-query-builders/query-builder/src/result-shape.ts:35 — `!!field.many && field.many.elementNullable` appears character-identically in 3 files — packages/2-mongo-family/5-query-builders/query-builder/src/result-shape.ts, packages/3-targets/postgres/1-target/src/core/psl-print/domain-types.ts, packages/3-targets/postgres/1-target/src/core/psl-print/scalar-fields.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/2-mongo-family/1-foundation/mongo-contract/src/relation-fields.ts:42 — `!('on' in relation) && !('through' in relation)` appears character-identically in 2 files — packages/2-mongo-family/1-foundation/mongo-contract/src/relation-fields.ts, packages/2-mongo-family/1-foundation/mongo-contract/src/stored-names.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/1-framework/2-authoring/psl-parser/src/syntax/ast-helpers.ts:61 — `!(child instanceof SyntaxNode) && child.kind === kind` appears character-identically in 2 files — packages/1-framework/2-authoring/psl-parser/src/syntax/ast-helpers.ts, packages/1-framework/2-authoring/psl-parser/src/syntax/ast/qualified-name.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/3-extensions/pgvector/src/core/data-types.ts:56 — `!Array.isArray(json) || (length !== undefined && json.length !== length)` appears character-identically in 2 files — packages/3-extensions/pgvector/src/core/data-types.ts, packages/3-targets/mongo/1-target/src/core/bson-scalar-helpers.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/1-framework/3-tooling/cli/src/orm/db/init.ts:226 — `!CliStructuredError.is(error) && isStructuredError(error) && error.code === 'CONTRACT.VALIDATION_FAILED'` appears character-identically in 2 files — packages/1-framework/3-tooling/cli/src/orm/db/init.ts, packages/1-framework/3-tooling/cli/src/orm/db/update.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate scripts/codemods/add-model-map.mjs:155 — `!MODEL_LINE.test(lines[i]) || !isModelDeclaration(lines, i)` appears character-identically in 5 files — scripts/codemods/add-model-map.mjs, skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs, skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.11-to-8.0.0-rc.12/scripts/psl-verbatim-table-names/add-model-map.mjs, upgrade-instructions/releases/8.0.0-rc.11-to-8.0.0-rc.12/sources/psl-verbatim-table-names/app/scripts/add-model-map.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/3-extensions/postgis/src/core/ewkb.ts:299 — `!Number.isFinite(position[0]) || !Number.isFinite(position[1])` appears character-identically in 2 files — packages/3-extensions/postgis/src/core/ewkb.ts, packages/3-extensions/postgis/src/core/geojson.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 REDACTED:57 — `!SKIPPED_DIRECTORIES.has(entry) && !entry.startsWith('.')` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:503 — `!SKIPPED_DIRECTORIES.has(entry.name) && !entry.name.startsWith('.')` appears character-identically in 4 files — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts, REDACTED, skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate skills-contrib/review-fetch-phase/scripts/extract-review-targets.mjs:26 — `!arg.startsWith('--') || !knownFlags.has(arg)` appears character-identically in 5 files — skills-contrib/review-fetch-phase/scripts/extract-review-targets.mjs, skills-contrib/review-fetch-phase/scripts/fetch-review-state.mjs, skills-contrib/review-fetch-phase/scripts/render-review-state.mjs, skills-contrib/review-fetch-phase/scripts/summarize-review-state.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts:292 — `!constraints || constraints.length === 0` appears character-identically in 2 files — packages/3-targets/postgres/1-target/src/core/migrations/op-factory-call.ts, packages/3-targets/sqlite/1-target/src/core/migrations/op-factory-call.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 REDACTED:768 — `!datetimeEnums.has(enumKey(namespaceId, name)) || !isRecord(valueSet) || !Array.isArray(values)` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts:82 — `!element.isTypeOnly && FACTORY_EXPORTS.has(imported)` appears character-identically in 4 files — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts, skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.18-to-8.0.0-rc.19/scripts/client-takes-contract-value/contract-from-json.ts, upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/app/scripts/contract-from-json.ts, upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.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 REDACTED:60 — `!entry.endsWith('.json') || !isFile(path)` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:320 — `!entry.name.endsWith('.json') && !entry.name.endsWith('.ts')` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:65 — `!isObject(contract) || !isObject(contract['execution'])` appears character-identically in 2 files — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts, skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.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 REDACTED:254 — `!isObject(contract) || contract['targetFamily'] !== 'mongo'` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:81 — `!isObject(domain) || !isObject(domain['namespaces'])` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts:71 — `!isObject(entry) || !isObject(entry['ref'])` appears character-identically in 2 files — skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.ts, skills/prisma-8/upgrading/extension/upgrades/8.0.0-rc.12-to-8.0.0-rc.13/scripts/execution-ref-entry-field/rename-execution-ref-keys.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 REDACTED:972 — `!isRecord(contract) || contract['targetFamily'] !== 'sql' || contract['target'] !== 'sqlite' || !isRecord(contract['storage'])` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:1315 — `!isRecord(contract) || contract['targetFamily'] !== 'sql' || typeof contract['target'] !== 'string'` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:712 — `!isRecord(enumType) || enumType['codecId'] !== DATETIME_CODEC || !Array.isArray(members)` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:592 — `!isRecord(enumType) || typeof codecId !== 'string' || !Array.isArray(members)` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:612 — `!isRecord(member) || value === undefined` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate REDACTED:769 — `!isRecord(pack) || !isRecord(types) || !('storage' in types)` appears character-identically in 4 files — REDACTED, REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D20 · ADR Quality · ADR has no Context section · ×23
  • ADR has no Context section docs/architecture docs/adrs/ADR 065 - Adapter capability schema & negotiation v1.md:1 — docs/architecture docs/adrs/ADR 065 - Adapter capability schema & negotiation v1.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 068 - Error mapping to RuntimeError.md:1 — docs/architecture docs/adrs/ADR 068 - Error mapping to RuntimeError.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 126 - PSL top-level block SPI.md:1 — docs/architecture docs/adrs/ADR 126 - PSL top-level block SPI.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 225 - Three-layer extensibility for pack-contributed entity kinds.md:1 — docs/architecture docs/adrs/ADR 225 - Three-layer extensibility for pack-contributed entity kinds.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 230 - Runtime target layer session-coupled connections.md:1 — docs/architecture docs/adrs/ADR 230 - Runtime target layer session-coupled connections.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 234 - Content-addressed wire names for Postgres-normalized objects.md:1 — docs/architecture docs/adrs/ADR 234 - Content-addressed wire names for Postgres-normalized objects.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 235 - The schema differ walks two derived schema IRs.md:1 — docs/architecture docs/adrs/ADR 235 - The schema differ walks two derived schema IRs.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 236 - Target-contributed model attributes.md:1 — docs/architecture docs/adrs/ADR 236 - Target-contributed model attributes.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 237 - Supabase-internal access is a service_role-only secondary root.md:1 — docs/architecture docs/adrs/ADR 237 - Supabase-internal access is a service_role-only secondary root.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 242 - Public npm surface - single @prisma scope with consolidated publish packages.md:1 — docs/architecture docs/adrs/ADR 242 - Public npm surface - single @prisma scope with consolidated publish packages.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 243 - Name-identified indexes and exact-name adoption.md:1 — docs/architecture docs/adrs/ADR 243 - Name-identified indexes and exact-name adoption.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 244 - Check constraints are opaque wire-named expressions.md:1 — docs/architecture docs/adrs/ADR 244 - Check constraints are opaque wire-named expressions.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 252 - An earlier Prisma version's schema is a contract source.md:1 — docs/architecture docs/adrs/ADR 252 - An earlier Prisma version's schema is a contract source.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 256 - Mutation-default generators are a framework runtime concern.md:1 — docs/architecture docs/adrs/ADR 256 - Mutation-default generators are a framework runtime concern.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 257 - Scalar types are named after the target on every surface.md:1 — docs/architecture docs/adrs/ADR 257 - Scalar types are named after the target on every surface.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 260 - Every query has an afterTransaction stage that fires when its enclosing transaction ends.md:1 — docs/architecture docs/adrs/ADR 260 - Every query has an afterTransaction stage that fires when its enclosing transaction ends.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 264 - A model names its storage verbatim, and a rename is an operation.md:1 — docs/architecture docs/adrs/ADR 264 - A model names its storage verbatim, and a rename is an operation.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 266 - The cache middleware passes data to its store, and the store decides how to cache.md:1 — docs/architecture docs/adrs/ADR 266 - The cache middleware passes data to its store, and the store decides how to cache.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 267 - A table may hold columns its model does not map.md:1 — docs/architecture docs/adrs/ADR 267 - A table may hold columns its model does not map.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 273 - A column of a type no data type claims is a raw column.md:1 — docs/architecture docs/adrs/ADR 273 - A column of a type no data type claims is a raw column.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 307 - No recovery resets or drops a database.md:1 — docs/architecture docs/adrs/ADR 307 - No recovery resets or drops a database.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 308 - Community packages are named prisma-orm-name.md:1 — docs/architecture docs/adrs/ADR 308 - Community packages are named prisma-orm-name.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
  • ADR has no Context section docs/architecture docs/adrs/ADR 313 - Postgres extension packs are published by tier.md:1 — docs/architecture docs/adrs/ADR 313 - Postgres extension packs are published by tier.md has no Context section (a heading such as `## Context`, or the MADR equivalent). A decision record states the context that forced it, the decision and its consequences, so a reader can tell later whether it still holds.
D24 · Comment Value · redundant comment · ×21
  • redundant comment packages/1-framework/3-tooling/cli/src/utils/framework-components.ts:56 — "Check that component is an object" repeats the code it sits on: 3 of its 3 words (check, component, object) are already in `if (typeof component !== 'object' || component === null)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/1-framework/3-tooling/cli/src/utils/framework-components.ts:79 — "Check familyId" repeats the code it sits on: 3 of its 3 words (check, family, id) are already in `if (!Object.hasOwn(record, 'familyId'))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/1-framework/3-tooling/cli/src/utils/framework-components.ts:93 — "Check targetId" repeats the code it sits on: 3 of its 3 words (check, target, id) are already in `if (!Object.hasOwn(record, 'targetId'))`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/2-sql-family/2-authoring/contract-ts/src/contract-dsl.ts:1055 — "The options are typed as the index type declares them." repeats the code it sits on: 4 of its 5 words (options, typed, index, type) are already in `type IndexSpecFrom<Map, Type, Where, Unique, IndexTypes extends IndexTypeMap> = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/2-sql-family/9-family/test/psl-contract-infer/relation-inference.test.ts:430 — "Child relation field" repeats the code it sits on: 3 of its 3 words (child, relation, field) are already in `const childRel = relations!.find((r) => r.fields);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/2-sql-family/9-family/test/psl-contract-infer/relation-inference.test.ts:438 — "Back-relation field" repeats the code it sits on: 3 of its 3 words (back, relation, field) are already in `const backRel = relations!.find((r) => !r.fields);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/3-targets/mongo/9-facade/test/mongo.types.test-d.ts:244 — "MongoStaticContext type tests" repeats the code it sits on: 4 of its 5 words (mongo, static, context, tests) are already in `test('MongoStaticContext carries the right members', () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/3-targets/postgres/2-adapter/test/ddl-rls-lowering.test.ts:113 — "RESTRICTIVE + multiple roles render alongside WITH CHECK." repeats the code it sits on: 5 of its 6 words (restrictive, multiple, roles, render, check) are already in `it('renders AS RESTRICTIVE with multiple roles and WITH CHECK', async () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/3-targets/postgres/2-adapter/test/migrations/runner.errors.integration.test.ts:334 — "Verify no marker/ledger writes" repeats the code it sits on: 4 of its 5 words (no, marker, ledger, writes) are already in `await expectNoMarkerOrLedgerWrites(driver!);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/3-targets/postgres/2-adapter/test/migrations/runner.policy.integration.test.ts:107 — "Verify no marker/ledger writes" repeats the code it sits on: 4 of its 5 words (no, marker, ledger, writes) are already in `await expectNoMarkerOrLedgerWrites(driver!);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment packages/3-targets/postgres/2-adapter/test/migrations/runner.policy.integration.test.ts:234 — "Policy that allows destructive operations" repeats the code it sits on: 4 of its 4 words (policy, allows, destructive, operations) are already in `const permissivePolicy = {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment scripts/lint-deps-focused.mjs:87 — "No staged files, skip check" repeats the code it sits on: 4 of its 5 words (no, staged, files, check) are already in `console.log('No staged TypeScript files found, skipping dependency check');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment scripts/lint-deps-focused.mjs:95 — "No package roots found, skip check" repeats the code it sits on: 5 of its 6 words (no, package, roots, found, check) are already in `console.log('No package roots found in staged files, skipping dependency check');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment scripts/lint-deps-focused.mjs:130 — "If focused check fails, fall back to full check" repeats the code it sits on: 6 of its 6 words (focused, check, fails, fall, back, full) are already in `console.log('Focused check failed, falling back to full dependency check...');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment test/integration/test/cli.emit-command.test.ts:79 — "Test with custom output path in config" repeats the code it sits on: 4 of its 5 words (test, custom, output, config) are already in `const customSetup = setupIntegrationTestDirectoryFromFixtures(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment test/integration/test/cli.emit-command.test.ts:137 — "Default output is 'src/prisma/contract.json'" repeats the code it sits on: 5 of its 6 words (default, src, prisma, contract, json) are already in `const defaultJsonPath = join(defaultsSetup.testDir, 'src/prisma/contract.json');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment test/integration/test/control-api.test.ts:165 — "Summary contains "Marker missing"" repeats the code it sits on: 4 of its 4 words (summary, contains, marker, missing) are already in `expect(result.summary.toLowerCase()).toContain('marker missing');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment test/integration/test/family.introspect.test.ts:61 — "Drop existing tables if they exist" repeats the code it sits on: 4 of its 4 words (drop, existing, tables, exist) are already in `await client.query('DROP TABLE IF EXISTS "post"');`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment test/integration/test/family.verify-database.errors.test.ts:265 — "Write marker with different profileHash" repeats the code it sits on: 4 of its 5 words (marker, different, profile, hash) are already in `await seedTestMarker(client, {`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment test/integration/test/ports/prisma/functional/issues-14271/issues-14271.test.ts:47 — "Verify all battery levels ordered by id" repeats the code it sits on: 4 of its 5 words (battery, levels, ordered, id) are already in `const batteryLevels = await db.public.BatteryLevel.orderBy((b) => b.id.asc()).all();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
  • redundant comment test/integration/test/sql-builder/playground/mutations.test-d.ts:127 — "UPDATE callback overload — type-level tests" repeats the code it sits on: 5 of its 6 words (update, callback, overload, type, tests) are already in `test('UPDATE callback overload type-checks with field reference', () =>`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
X7 · Silent fallback defaults · Silent fallback default in catch · ×16
  • Silent fallback default in catch packages/1-framework/3-tooling/cli-telemetry/src/user-config.ts:81 — `readUserConfig` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/1-framework/3-tooling/cli/scripts/record.ts:98 — `readCache` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/1-framework/3-tooling/language-server/src/project.ts:160 — `completions` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/1-framework/3-tooling/language-server/src/project.ts:252 — `references` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/2-sql-family/9-family/src/core/verify.ts:18 — `parseMeta` swallows every exception into `return {}` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/3-extensions/sql-orm-client/src/collection-dispatch.ts:970 — `parseIncludePayload` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch packages/3-targets/sqlite/2-adapter/src/core/ledger-decode.ts:21 — `operationCountFromStored` swallows every exception into `return 0` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch scripts/audit-notice.mjs:66 — `findNoticeFiles` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch scripts/audit-notice.mjs:85 — `listPnpmStoreEntries` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch scripts/check-commit-signoff.mjs:110 — `getCommentChar` swallows every exception into `return '#'` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch scripts/lint-deps-focused.mjs:40 — `getStagedFiles` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch scripts/lint-workflow-triggers.mjs:88 — `listWorkflowFiles` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch scripts/migrate-migrations-layout.mjs:97 — `listSubdirs` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch scripts/migrate-migrations-layout.mjs:256 — `findRefContractJsonPaths` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch scripts/sync-agent-rules.mjs:60 — `listEntries` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
  • Silent fallback default in catch scripts/validate-skills.mjs:86 — `listSkillFiles` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
D20 · ADR Quality · ADR links a record that does not exist · ×13
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 014 - Runtime Hook API.md:3 — docs/architecture docs/adrs/ADR 014 - Runtime Hook API.md:3 names `ADR%20271%20-%20The%20runtime%20middleware%20observes%20a%20tree%20of%20activities%2C%20each%20started%2C%20ended%20and%20finalized.md` as the record it is superseded by, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 098 - Runtime accepts contract object or JSON.md:3 — docs/architecture docs/adrs/ADR 098 - Runtime accepts contract object or JSON.md:3 names `ADR%20274%20-%20A%20client%20takes%20a%20typed%20contract%20value%2C%20so%20every%20other%20option%20is%20inferred.md` as the record it is superseded by, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 154 - Component-owned database dependencies.md:5 — docs/architecture docs/adrs/ADR 154 - Component-owned database dependencies.md:5 names `./ADR%20212%20-%20Contract%20spaces.md` as the record it is superseded by, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 154 - Component-owned database dependencies.md:5 — docs/architecture docs/adrs/ADR 154 - Component-owned database dependencies.md:5 names `./ADR%20213%20-%20Codec%20lifecycle%20hooks.md` as the record it is superseded by, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 154 - Component-owned database dependencies.md:5 — docs/architecture docs/adrs/ADR 154 - Component-owned database dependencies.md:5 names `ADR%20312%20-%20A%20Postgres%20extension%20is%20a%20contract%20entity%2C%20and%20db%20sign%20refuses%20a%20space%20with%20unmet%20invariants.md` as the record it is superseded by, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 160 - Plan grouping keys for multi-statement orchestration.md:3 — docs/architecture docs/adrs/ADR 160 - Plan grouping keys for multi-statement orchestration.md:3 names `ADR%20271%20-%20The%20runtime%20middleware%20observes%20a%20tree%20of%20activities%2C%20each%20started%2C%20ended%20and%20finalized.md` as the record it is superseded by, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 212 - Contract spaces.md:5 — docs/architecture docs/adrs/ADR 212 - Contract spaces.md:5 names `./ADR%20154%20-%20Component-owned%20database%20dependencies.md` as the record it supersedes, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 220 - Plan execution identity for middleware correlation.md:3 — docs/architecture docs/adrs/ADR 220 - Plan execution identity for middleware correlation.md:3 names `ADR%20271%20-%20The%20runtime%20middleware%20observes%20a%20tree%20of%20activities%2C%20each%20started%2C%20ended%20and%20finalized.md` as the record it is superseded by, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 239 - Errors are structural envelopes with dotted namespace codes.md:5 — docs/architecture docs/adrs/ADR 239 - Errors are structural envelopes with dotted namespace codes.md:5 names `ADR%20027%20-%20Error%20Envelope%20Stable%20Codes.md` as the record it supersedes, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 239 - Errors are structural envelopes with dotted namespace codes.md:5 — docs/architecture docs/adrs/ADR 239 - Errors are structural envelopes with dotted namespace codes.md:5 names `ADR%20068%20-%20Error%20mapping%20to%20RuntimeError.md` as the record it supersedes, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 260 - Every query has an afterTransaction stage that fires when its enclosing transaction ends.md:3 — docs/architecture docs/adrs/ADR 260 - Every query has an afterTransaction stage that fires when its enclosing transaction ends.md:3 names `ADR%20271%20-%20The%20runtime%20middleware%20observes%20a%20tree%20of%20activities%2C%20each%20started%2C%20ended%20and%20finalized.md` as the record it is superseded by, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 275 - Client generators are field attributes, and a type alias is expanded into each column.md:6 — docs/architecture docs/adrs/ADR 275 - Client generators are field attributes, and a type alias is expanded into each column.md:6 names `ADR%20170%20-%20Pack-provided%20type%20constructors%20and%20field%20presets.md` as the record it supersedes, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
  • ADR links a record that does not exist docs/architecture docs/adrs/ADR 275 - Client generators are field attributes, and a type alias is expanded into each column.md:6 — docs/architecture docs/adrs/ADR 275 - Client generators are field attributes, and a type alias is expanded into each column.md:6 names `ADR%20246%20-%20Option%20arguments%20and%20select%20templates%20for%20authoring%20helpers.md` as the record it supersedes, and no such record is in the decision log. Fix the link, or restore the record, so a reader can follow the decision's history.
M4 · Documentation accuracy · README/code drift · ×10
  • README/code drift projects/README.md:18 — projects/README.md links to `../docs/drive/README.md`, but `docs/drive/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift docs/reference/framework-integration-analysis.md:237 — docs/reference/framework-integration-analysis.md names Vite 7, but the manifest declares `vite` ^6.3.5. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/1-framework/2-authoring/ids/README.md:33 — packages/1-framework/2-authoring/ids/README.md links to `../../../docs/architecture%20docs/subsystems/1.%20Data%20Contract.md`, but `packages/docs/architecture docs/subsystems/1. Data Contract.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/1-framework/2-authoring/ids/README.md:34 — packages/1-framework/2-authoring/ids/README.md links to `../../../docs/architecture%20docs/subsystems/3.%20Query%20Lanes.md`, but `packages/docs/architecture docs/subsystems/3. Query Lanes.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/1-framework/3-tooling/vite-plugin-contract-emit/README.md:29 — packages/1-framework/3-tooling/vite-plugin-contract-emit/README.md names Vite 7, but the manifest declares `vite` ^6.3.5. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/2-sql-family/1-core/contract/README.md:79 — packages/2-sql-family/1-core/contract/README.md links to `../../../docs/architecture%20docs/adrs/ADR%20166%20-%20Referential%20actions%20for%20foreign%20keys.md`, but `packages/docs/architecture docs/adrs/ADR 166 - Referential actions for foreign keys.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/2-sql-family/1-core/contract/README.md:219 — packages/2-sql-family/1-core/contract/README.md links to `../../../docs/architecture%20docs/subsystems/1.%20Data%20Contract.md`, but `packages/docs/architecture docs/subsystems/1. Data Contract.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/2-sql-family/1-core/contract/README.md:220 — packages/2-sql-family/1-core/contract/README.md links to `../../../docs/architecture%20docs/subsystems/2.%20Contract%20Emitter%20&%20Types.md`, but `packages/docs/architecture docs/subsystems/2. Contract Emitter & Types.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/2-sql-family/4-lanes/relational-core/README.md:202 — packages/2-sql-family/4-lanes/relational-core/README.md links to `../../../../docs/architecture%20docs/adrs/ADR%20005%20-%20Thin%20Core,%20Fat%20Targets.md`, but `docs/architecture docs/adrs/ADR 005 - Thin Core, Fat Targets.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
  • README/code drift packages/3-targets/postgres/3-driver/README.md:91 — packages/3-targets/postgres/3-driver/README.md links to `../../docs/architecture%20docs/subsystems/5.%20Adapters%20&%20Targets.md`, but `packages/3-targets/docs/architecture docs/subsystems/5. Adapters & Targets.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
D19 · Documentation Quality · Documentation · ×8
  • Documentation: no build, run or usage example packages/9-public/@prisma/orm-family-mongo/README.md:1 — `orm-family-mongo` is a published package (`REDACTED` without `"private": true`) and neither `packages/9-public/@prisma/orm-family-mongo/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/9-public/@prisma/orm-family-sql/README.md:1 — `orm-family-sql` is a published package (`REDACTED` without `"private": true`) and neither `packages/9-public/@prisma/orm-family-sql/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/9-public/@prisma/orm-framework/README.md:1 — `orm-framework` is a published package (`REDACTED` without `"private": true`) and neither `packages/9-public/@prisma/orm-framework/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/9-public/@prisma/orm-target-mongo/README.md:1 — `orm-target-mongo` is a published package (`REDACTED` without `"private": true`) and neither `packages/9-public/@prisma/orm-target-mongo/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/9-public/@prisma/orm-target-mysql/README.md:1 — `orm-target-mysql` is a published package (`REDACTED` without `"private": true`) and neither `packages/9-public/@prisma/orm-target-mysql/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/9-public/@prisma/orm-target-postgres/README.md:1 — `orm-target-postgres` is a published package (`REDACTED` without `"private": true`) and neither `packages/9-public/@prisma/orm-target-postgres/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/9-public/@prisma/orm-target-sqlite/README.md:1 — `orm-target-sqlite` is a published package (`REDACTED` without `"private": true`) and neither `packages/9-public/@prisma/orm-target-sqlite/README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
  • Documentation: no build, run or usage example packages/9-public/@prisma/orm-toolchain/README.md:1 — `orm-toolchain` is a published package (`REDACTED` without `"private": true`) and neither `packages/9-public/@prisma/orm-toolchain/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.
D25 · ADR Conformance · ADR not followed · ×8
  • ADR not followed: ADR 224 — Namespace concretions address entities by coordinate docs/architecture docs/adrs/ADR 224 - Namespace concretions address entities by coordinate.md:56 — docs/architecture docs/adrs/ADR 224 - Namespace concretions address entities by coordinate.md:56 rules out `entityKind`, but production code uses it: upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:468, upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:469, upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:840, skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:468, skills/prisma-8/upgrading/app/upgrades/8.0.0-rc.21-to-8.0.0-rc.22/scripts/value-objects-in-storage/value-objects-in-storage.ts:469 (+165 more). Remove the use, or supersede the record if the decision changed.
  • ADR not followed: ADR 239 — Errors are structural envelopes with dotted namespace codes docs/architecture docs/adrs/ADR 239 - Errors are structural envelopes with dotted namespace codes.md:114 — docs/architecture docs/adrs/ADR 239 - Errors are structural envelopes with dotted namespace codes.md:114 rules out `instanceof` in type, monorepo, but production code uses it: upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:1141, upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:1141, REDACTED:1102, REDACTED:1477, REDACTED:1477 (+13 more). Remove the use, or supersede the record if the decision changed.
  • ADR not followed: ADR 271 — The runtime middleware observes a tree of activities, each started, ended and finalized docs/architecture docs/adrs/ADR 271 - The runtime middleware observes a tree of activities, each started, ended and finalized.md:55 — docs/architecture docs/adrs/ADR 271 - The runtime middleware observes a tree of activities, each started, ended and finalized.md:55 rules out `statement` in client, kind, but production code uses it: upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:58, upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:59, upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:70, upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:71, upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/client-takes-contract-value/extension/scripts/contract-from-json.ts:72 (+118 more). Remove the use, or supersede the record if the decision changed.
  • ADR not followed: ADR 271 — The runtime middleware observes a tree of activities, each started, ended and finalized docs/architecture docs/adrs/ADR 271 - The runtime middleware observes a tree of activities, each started, ended and finalized.md:55 — docs/architecture docs/adrs/ADR 271 - The runtime middleware observes a tree of activities, each started, ended and finalized.md:55 rules out `transaction` in client, kind, but production code uses it: packages/3-extensions/sql-orm-client/src/mutation-executor.ts:259, packages/3-extensions/sql-orm-client/src/mutation-executor.ts:260, packages/3-extensions/sql-orm-client/src/mutation-executor.ts:270, packages/3-extensions/sql-orm-client/src/mutation-executor.ts:271, packages/3-extensions/sql-orm-client/src/mutation-executor.ts:284 (+8 more). Remove the use, or supersede the record if the decision changed.
  • ADR not followed: ADR 312 — A Postgres extension is a contract entity, and db sign refuses a space with unmet invariants docs/architecture docs/adrs/ADR 312 - A Postgres extension is a contract entity, and db sign refuses a space with unmet invariants.md:44 — docs/architecture docs/adrs/ADR 312 - A Postgres extension is a contract entity, and db sign refuses a space with unmet invariants.md:44 rules out `db` in Sign, writes, but production code uses it: packages/1-framework/3-tooling/cli/src/orm/db/sign.ts:481, packages/1-framework/3-tooling/cli/src/orm/db/sign.ts:582, packages/1-framework/3-tooling/cli/src/orm/db/sign.ts:589, packages/1-framework/3-tooling/cli/src/orm/db/sign.ts:635, examples/prisma-8-demo-mysql/src/orm-client/user-writes.ts:4 (+9 more). Remove the use, or supersede the record if the decision changed.
  • ADR not followed: ADR 314 — Code shared by several targets' type implementations lives in one package docs/architecture docs/adrs/ADR 314 - Code shared by several targets' type implementations lives in one package.md:31 — docs/architecture docs/adrs/ADR 314 - Code shared by several targets' type implementations lives in one package.md:31 rules out `extensions` in adapter, but production code uses it: packages/3-targets/sqlite/2-adapter/src/exports/control.ts:18, packages/3-targets/sqlite/2-adapter/src/core/runtime/runtime-adapter.ts:52, packages/3-targets/sqlite/2-adapter/src/core/runtime/runtime-adapter.ts:55, packages/3-targets/postgres/2-adapter/src/exports/control.ts:22, packages/3-targets/postgres/2-adapter/src/exports/runtime.ts:53 (+6 more). Remove the use, or supersede the record if the decision changed.
  • ADR not followed: ADR 315 — Each target declares the convenience date and time types over its own explicit types docs/architecture docs/adrs/ADR 315 - Each target declares the convenience date and time types over its own explicit types.md:27 — docs/architecture docs/adrs/ADR 315 - Each target declares the convenience date and time types over its own explicit types.md:27 rules out `Duration` in target, but production code uses it: packages/3-targets/sqlite/1-target/src/core/type-constructors.ts:190, packages/3-targets/postgres/1-target/src/core/type-constructors.ts:439, packages/3-targets/mysql/1-target/src/core/type-constructors.ts:235. Remove the use, or supersede the record if the decision changed.
  • ADR not followed: ADR 316 — PostgreSQL scalars get convenience types docs/architecture docs/adrs/ADR 316 - PostgreSQL scalars get convenience types.md:69 — docs/architecture docs/adrs/ADR 316 - PostgreSQL scalars get convenience types.md:69 rules out `String`, but production code uses it: upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:387, upgrade-instructions/releases/8.0.0-rc.21-to-8.0.0-rc.22/sources/value-objects-in-storage/app/scripts/value-objects-in-storage/value-objects-in-storage.ts:1161, upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/extension/scripts/expand-type-aliases/expand-type-aliases.ts:1141, upgrade-instructions/releases/8.0.0-rc.19-to-8.0.0-rc.20/sources/expand-type-aliases/app/scripts/expand-type-aliases/expand-type-aliases.ts:1141, upgrade-instructions/releases/8.0.0-rc.18-to-8.0.0-rc.19/sources/remove-nocheck/extension/scripts/remove-nocheck/remove-nocheck.ts:801 (+364 more). Remove the use, or supersede the record if the decision changed.
D10 · Test Quality · No direct assertions · ×6
  • No direct assertions: asServiceRole().supabase.sql exposes the internal auth and storage namespaces examples/supabase/test/service-role-namespaces.test-d.ts:24 — No conventional assertion call was detected, and 6 of 9 tests in `examples/supabase` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: asServiceRole().supabase.orm exposes the internal auth and storage namespaces examples/supabase/test/service-role-namespaces.test-d.ts:30 — No conventional assertion call was detected, and 6 of 9 tests in `examples/supabase` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: asServiceRole() primary root is app-only — public but not auth/storage examples/supabase/test/service-role-namespaces.test-d.ts:36 — No conventional assertion call was detected, and 6 of 9 tests in `examples/supabase` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: asAnon() is app-only and has no .supabase secondary root examples/supabase/test/service-role-namespaces.test-d.ts:46 — No conventional assertion call was detected, and 6 of 9 tests in `examples/supabase` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: asUser(jwt) is app-only and has no .supabase secondary root examples/supabase/test/service-role-namespaces.test-d.ts:54 — No conventional assertion call was detected, and 6 of 9 tests in `examples/supabase` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
  • No direct assertions: asAnon() and asUser() return the plain app-contract RoleBoundDb examples/supabase/test/service-role-namespaces.test-d.ts:63 — No conventional assertion call was detected, and 6 of 9 tests in `examples/supabase` read the same way — so this is treated as that project's convention rather than a broken test, and it does not drag the score. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a project of runnable samples compiled as tests, where a run that does not throw is the only check. If it is the latter, these methods genuinely verify nothing.
AX6 · Interface segregation · Fat interface · ×5
  • Fat interface: ControlClient (20 required operations) packages/1-framework/3-tooling/cli/src/control-api/types.ts:861 — `ControlClient` declares 20 required operations: `init`, `connect`, `close`, `verify`, `schemaVerify`, `dbInit`, `dbUpdate`, `dbVerify`, `dbSign`, `readMarker`, `readAllMarkers`, `readLedger`, `migrate`, `introspect`, `toSchemaView`, `inferPslContract`, `getPslBlockDescriptors`, `toOperationPreview`, `emit`, `renderContractDts`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MongoStageVisitor (28 required operations) packages/2-mongo-family/4-query/query-ast/src/visitors.ts:106 — `MongoStageVisitor` declares 28 required operations: `match`, `project`, `sort`, `limit`, `skip`, `lookup`, `unwind`, `group`, `addFields`, `replaceRoot`, `count`, `sortByCount`, `sample`, `redact`, `out`, `unionWith`, `bucket`, `bucketAuto`, `geoNear`, `facet`, `graphLookup`, `merge`, `setWindowFields`, `densify`, `fill`, `search`, `searchMeta`, `vectorSearch`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: MongoCollection (25 required operations) packages/2-mongo-family/5-query-builders/orm/src/collection.ts:105 — `MongoCollection` declares 25 required operations: `variant`, `where`, `where`, `select`, `include`, `orderBy`, `limit`, `offset`, `all`, `first`, `firstOrThrow`, `create`, `createAll`, `createAndCount`, `update`, `update`, `updateAll`, `updateAll`, `updateAndCount`, `updateAndCount`, `delete`, `deleteAll`, `deleteAndCount`, `upsert`, `upsert`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. Those 25 declarations carry 20 distinct name(s), so part of the width is overloading rather than separate responsibilities — but 20 operations clears the >15 bar on its own, so the row is about responsibilities, not signatures. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: LeafExpression (24 required operations) packages/2-mongo-family/5-query-builders/query-builder/src/field-accessor.ts:48 — `LeafExpression` declares 24 required operations: `eq`, `ne`, `gt`, `gte`, `lt`, `lte`, `in`, `nin`, `exists`, `type`, `set`, `unset`, `rename`, `inc`, `mul`, `min`, `max`, `push`, `addToSet`, `pop`, `pull`, `pullAll`, `currentDate`, `setOnInsert`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ExprVisitor (22 required operations) packages/2-sql-family/4-lanes/relational-core/src/ast/types.ts:86 — `ExprVisitor` declares 22 required operations: `columnRef`, `identifierRef`, `subquery`, `operation`, `aggregate`, `windowFunc`, `functionCall`, `cast`, `case`, `jsonObject`, `jsonArrayAgg`, `binary`, `and`, `or`, `exists`, `nullCheck`, `not`, `literal`, `param`, `preparedParam`, `list`, `rawExpr`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D16 · Bus Factor · Off-boarding risk · ×4
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 153 significant file(s) lose their only recent owner: packages/1-framework/3-tooling/cli/src/control-api/statements/resolve-statements.ts, packages/1-framework/3-tooling/cli/src/control-api/statements/plan-questions.ts, packages/3-targets/postgres/1-target/src/core/psl-print/refusals.ts, packages/1-framework/3-tooling/cli/src/control-api/operations/migration-plan.ts, packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts, packages/2-sql-family/9-family/src/core/migrations/statement-planning.ts, packages/3-targets/postgres/1-target/src/contract-free/checks.ts, packages/3-extensions/sql-orm-client/src/fragments.ts (+145 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 39 significant file(s) lose their only recent owner: packages/2-mongo-family/4-query/query-ast/src/stages.ts, packages/3-targets/mongo/2-adapter/src/lowering.ts, packages/2-mongo-family/5-query-builders/query-builder/src/expression-helpers.ts, packages/2-mongo-family/9-family/src/core/schema-verify/canonicalize-introspection.ts, packages/2-mongo-family/9-family/src/core/control-instance.ts, packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-rows.ts, packages/2-mongo-family/4-query/query-ast/src/aggregation-expressions.ts, skills/prisma-8/upgrading/extension/upgrades/0.9-to-0.10/stamp-storage-types-kind.ts (+31 more). Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 8 significant file(s) lose their only recent owner: skills/prisma-8/upgrading/app/upgrades/0.12-to-0.13/re-emit-mti-variant-link-columns.ts, packages/2-sql-family/4-lanes/sql-builder/src/types/raw-query.ts, packages/1-framework/3-tooling/cli-telemetry/src/spawn.ts, apps/telemetry-backend/src/server-runtime.ts, packages/1-framework/3-tooling/cli-telemetry/src/payload.ts, REDACTED, apps/telemetry-backend/src/rate-limiter.ts, packages/1-framework/3-tooling/cli-telemetry/src/sender.ts. Pair on, review, or document these before any departure.
  • Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 6 significant file(s) lose their only recent owner: packages/1-framework/2-authoring/psl-parser/src/symbol-table.ts, packages/1-framework/3-tooling/language-server/src/rename.ts, packages/1-framework/3-tooling/language-server/src/signature-context.ts, packages/1-framework/2-authoring/psl-parser/src/scope.ts, packages/1-framework/3-tooling/language-server/src/project-registry.ts, packages/1-framework/2-authoring/psl-parser/src/entity-reference.ts. Pair on, review, or document these before any departure.
D20 · ADR Quality · ADR superseded but its status says otherwise · ×3
  • ADR superseded but its status says otherwise docs/architecture docs/adrs/ADR 216 - CLI telemetry installation ID is a stored random UUID not a system fingerprint.md:5 — docs/architecture docs/adrs/ADR 216 - CLI telemetry installation ID is a stored random UUID not a system fingerprint.md:5 says "Accepted. CLI telemetry is implemented as described in [`docs/Telemetry.md`](../../Telemetry.md), which is the user-facing reference for the installation ID's lifecycle and the consent surface this ADR scopes. This ADR scopes only the CLI usage telemetry installation identifier; it does not concern the existing runtime telemetry surface in [ADR 024 — Telemetry Schema](./ADR%20024%20-%20Telemetry%20Schema.md), which is an internal query-execution observability SPI with no client-stored identifier.", but docs/architecture docs/adrs/ADR 223 - CLI telemetry defaults to opt-out with a first-run notice.md supersedes it. Two records now claim the same ground; mark this one "Superseded by" its successor.
  • ADR superseded but its status says otherwise docs/architecture docs/adrs/ADR 217 - CLI telemetry runs in a detached subprocess spawned at command start.md:5 — docs/architecture docs/adrs/ADR 217 - CLI telemetry runs in a detached subprocess spawned at command start.md:5 says "Accepted. CLI telemetry subprocess pattern is implemented as described in [`docs/Telemetry.md`](../../Telemetry.md), which is the user-facing reference for the telemetry surface this ADR scopes. This ADR is the engineering-architecture companion to [ADR 216 — CLI telemetry installation ID is a stored random UUID](./ADR%20216%20-%20CLI%20telemetry%20installation%20ID%20is%20a%20stored%20random%20UUID%20not%20a%20system%20fingerprint.md). It does not cover crash/error reporting, which is Phase 2 of the project and is expected to require a different isolation contract (synchronous-flush-before-exit rather than fire-and-forget).", but docs/architecture docs/adrs/ADR 223 - CLI telemetry defaults to opt-out with a first-run notice.md supersedes it. Two records now claim the same ground; mark this one "Superseded by" its successor.
  • ADR superseded but its status says otherwise docs/architecture docs/adrs/ADR 222 - Version support policy.md:1 — docs/architecture docs/adrs/ADR 222 - Version support policy.md:1 says "Accepted — PostgreSQL floor amended by [ADR 248](ADR%20248%20-%20PostgreSQL%20floor%20lowered%20to%2015.md)", but docs/architecture docs/adrs/ADR 248 - PostgreSQL floor lowered to 15.md supersedes it. Two records now claim the same ground; mark this one "Superseded by" its successor.
IC1 · Incompleteness & stubs · Empty method body · ×3
  • Empty method body packages/1-framework/2-authoring/psl-parser/src/authoring-arguments.ts:70 — `call` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/1-framework/2-authoring/psl-parser/src/authoring-arguments.ts:71 — `argument` has an empty body — confirm it's an intentional no-op and not an unfinished method.
  • Empty method body packages/1-framework/2-authoring/psl-parser/src/authoring-arguments.ts:72 — `value` has an empty body — confirm it's an intentional no-op and not an unfinished method.
IC1 · Incompleteness & stubs · Disabled test · ×2
  • Disabled test test/utils/src/mysql-database.ts:77 — 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 test/utils/test/mysql-database.test.ts:31 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×2
  • No app-layer HTTPS enforcement detected apps/lsp-playground/src/cli.ts:198 — `httpServer.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.)
  • No app-layer HTTPS enforcement detected REDACTED:122 — `server.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.)
C2 · Access Controls · No named authorization policies · ×1
  • No named authorization policies packages/1-framework/1-core/framework-components/src/control/control-stack.ts:146 — 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.
C3 · Audit Trail · Partial audit-trail evidence · ×1
  • Partial audit-trail evidence — An audit mechanism is present, but the trail is not yet complete — missing: an ORM write hook every change flows through (a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware or a query extension, or an event-store append), per-model coverage (@Audited, or a change-history plugin such as mongoose-history or sequelize-paper-trail applied to each model).
C4 · Data Retention · Partial data-retention evidence · ×1
  • Partial data-retention evidence — A retention mechanism is present, but the data-lifecycle is not yet complete — missing: a scheduled purge / cleanup job (a cron task that deletes rows past their retention — purgeExpired… / deleteOld…), a documented retention period / data-expiry.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 2 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 (208 single-owned of 1004 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; 1004 of the 2201 production source files in this repository met that bar). They are anonymized user #5 (1 file(s)), anonymized user #6 (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: packages/1-framework/3-tooling/migration/src/graph-ops.ts, packages/1-framework/2-authoring/psl-parser/src/syntax/ast/type-annotation.ts.
D21 · Naming Consistency · `MigrationCLI` spells `CLI` where 16 names in the project spell it `Cli` · ×1
  • `MigrationCLI` spells `CLI` where 16 names in the project spell it `Cli` packages/1-framework/3-tooling/cli/src/migration-cli.ts:166 — 16 of 17 names in project @internal/monorepo spell the token `Cli` (16 of 17; unit: names in project @internal/monorepo containing `Cli`). Peers: cli.resolveCliEntry (apps/lsp-playground/src/cli.ts:48); control.errorMigrationCliConfigNotFound (packages/1-framework/1-core/errors/src/control.ts:475); control.errorMigrationCliInvalidConfigArg (packages/1-framework/1-core/errors/src/control.ts:509); control.errorMigrationCliUnknownFlag (packages/1-framework/1-core/errors/src/control.ts:536); record.probeCliOutput (packages/1-framework/3-tooling/cli/scripts/record.ts:115). Rename to `MigrationCli`. [rule N6]
D21 · Naming Consistency · `toJSON` spells `JSON` where 547 names in the project spell it `Json` · ×1
  • `toJSON` spells `JSON` where 547 names in the project spell it `Json` packages/1-framework/3-tooling/cli/test/fixtures/to-json-circular.ts:4 — 547 of 548 names in project @internal/monorepo spell the token `Json` (547 of 548; unit: names in project @internal/monorepo containing `Json`). Peers: M.startContractJson (apps/telemetry-backend/migrations/app/20261016T1018_exit_code/migration.ts:13); M.endContractJson (apps/telemetry-backend/migrations/app/20261016T1018_exit_code/migration.ts:14); handler.parseJson (apps/telemetry-backend/src/handler.ts:75); InitialMigration.endContractJson (examples/mongo-demo/migrations/app/20260409T1030_migration/migration.ts:8); M.startContractJson (examples/mongo-demo/migrations/app/20260626T1605_add_user_role_enum/migration.ts:13). Rename to `toJson`. [rule N6]
D26 · Project Cohesion · Projects may be oversized for their cohesion · ×1
  • Projects may be oversized for their cohesion — 8 of 82 project(s) overshoot their size bounds, lowering Project Cohesion to 8.1/10. The most over is `(repository root)` (40227 LoC, 119 module-visible types across 54 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D30 · Dependency Vulnerabilities · Low vulnerability · ×1
  • REDACTED
D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1
  • Orphaned files with no living knowledge — 26 of 1005 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; 1005 of the 2201 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: packages/1-framework/3-tooling/cli/recordings/config.ts, skills/prisma-8/upgrading/extension/upgrades/0.11-to-0.12/regenerate-extension-public-baseline.ts, packages/2-sql-family/2-authoring/contract-ts/src/contract-warnings.ts, packages/2-mongo-family/1-foundation/mongo-contract/src/ir/mongo-collection-options.ts, skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-closed-mongo-contracts.ts, skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-postgres-public-default.ts, skills/prisma-8/upgrading/app/upgrades/0.11-to-0.12/re-emit-domain-namespaced-contracts.ts, packages/1-framework/0-foundation/utils/src/canonical-stringify.ts (and 18 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
P2 · Observability · Logging is not universal · ×1
  • Logging is not universal — Only 3/7 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `apps/lsp-playground`, `packages/0-shared/extension-author-tools`, `packages/1-framework/3-tooling/cli`, `packages/1-framework/3-tooling/language-server`.
P4 · Deployment & Rollback · No release approval gate · ×1
  • No release approval gate — Deployment 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 reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.
R7 · Dead Code · Unused export 'MAX_POSTS_PER_USER' · ×1
  • Unused export 'MAX_POSTS_PER_USER' examples/prisma-8-demo-sqlite/src/transactions/add-posts-within-quota.ts:3 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'context' · ×1
  • Unused export 'context' examples/prisma-8-demo/src/prisma-no-emit/context.ts:10 — Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code · Unused export 'stack' · ×1
  • Unused export 'stack' examples/prisma-8-demo/src/prisma-no-emit/context.ts:11 — Nothing imports this binding — it is safe to review for removal.
R8 · Dependency Hygiene · Type-only dependency '@codingame/monaco-vscode-editor-service-override' in production deps · ×1
  • Type-only dependency '@codingame/monaco-vscode-editor-service-override' in production deps REDACTED:17 — Every import is type-only — move it to devDependencies.
R8 · Dependency Hygiene · Test-only dependency 'strip-ansi' in production deps · ×1
  • Test-only dependency 'strip-ansi' in production deps packages/1-framework/3-tooling/cli/package.json:46 — Only test files import it (first: packages/1-framework/3-tooling/cli/test/orm/contract-emit.test.ts:5) — move it to devDependencies.
X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1
  • Not all async functions that make a request accept an AbortSignal — Only 1/2 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 — 0/200 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1
  • Null assertions (`!`) reduce the strict null checking score — ~0.1 `!` null assertions per 1k TypeScript source lines — 36 assertion(s) across the 325855 source line(s) of the 1976 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/1-framework/3-tooling/cli/src/utils/formatters/migration-graph-grid-layout.ts (11), packages/1-framework/3-tooling/cli/scripts/record.ts (9), packages/1-framework/3-tooling/cli/src/control-api/client.ts (3). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Minor — 70 finding(s)
D10 · Test Quality · Skipped (documented) · ×52
  • Skipped (documented): [update] post id — upstream expects success (implicit onUpdate=Cascade); Prisma 8 default onUpdate=NoAction throws test/integration/test/ports/prisma/functional/relation-mode-gh-m-to-n/update.test.ts:284 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): [update] category id — upstream expects success (implicit onUpdate=Cascade); Prisma 8 default onUpdate=NoAction throws test/integration/test/ports/prisma/functional/relation-mode-gh-m-to-n/update.test.ts:306 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): include _count should fail test/integration/test/ports/prisma/functional/methods-updateManyAndReturn/methods-updateManyAndReturn.test.ts:187 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): include _count should fail test/integration/test/ports/prisma/functional/methods-createManyAndReturn/methods-createManyAndReturn.test.ts:143 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): returns a structured error when reading an enum value unknown to the schema test/integration/test/ports/prisma/functional/issues-TML-1664-unknown-enum-value-read-error/issues-TML-1664-unknown-enum-value-read-error.test.ts:107 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): retrieves a cursor against a DATE column test/integration/test/ports/prisma/functional/issues-29309-datetime-cursor/issues-29309-datetime-cursor.test.ts:27 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): serializes Uint8Array nested in object as base64 test/integration/test/ports/prisma/functional/issues-29267-uint8array-in-json/issues-29267-uint8array-in-json.test.ts:23 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): serializes Uint8Array nested in array as base64 test/integration/test/ports/prisma/functional/issues-29267-uint8array-in-json/issues-29267-uint8array-in-json.test.ts:36 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): serializes Uint8Array directly as base64 test/integration/test/ports/prisma/functional/issues-29267-uint8array-in-json/issues-29267-uint8array-in-json.test.ts:49 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): serializes deeply nested Uint8Array as base64 test/integration/test/ports/prisma/functional/issues-29267-uint8array-in-json/issues-29267-uint8array-in-json.test.ts:62 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): correctly handles two subsequent queries with a different cursor test/integration/test/ports/prisma/functional/issues-29254-query-plan-cache-mutation/issues-29254-query-plan-cache-mutation.test.ts:38 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): correctly handles a cursor with parameterised values test/integration/test/ports/prisma/functional/issues-29176-cursor-parameter-regression/issues-29176-cursor-parameter-regression.test.ts:30 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): create with mapped enum test/integration/test/ports/prisma/functional/issues-28591-mapped-enums/issues-28591-mapped-enums.test.ts:26 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): correctly parses $label test/integration/test/ports/prisma/functional/issues-28192-pg-historical-dates/issues-28192-pg-historical-dates.test.ts:81 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails.each — the body is expected to fail, so its failure is not reported
  • Skipped (documented): nested set should result in all expected linked rows test/integration/test/ports/prisma/functional/issues-28151-broken-nested-set/issues-28151-broken-nested-set.test.ts:22 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): findMany with cursor 1 unique (PK) test/integration/test/ports/prisma/functional/extended-where/extended-where.test.ts:75 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): findMany with cursor 2 uniques (PK & non-PK) test/integration/test/ports/prisma/functional/extended-where/extended-where.test.ts:90 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): findMany with cursor 1 unique (non-PK) test/integration/test/ports/prisma/functional/extended-where/extended-where.test.ts:105 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): findFirst with cursor 1 unique (PK) test/integration/test/ports/prisma/functional/extended-where/extended-where.test.ts:122 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): findFirst with cursor 2 uniques (PK & non-PK) test/integration/test/ports/prisma/functional/extended-where/extended-where.test.ts:137 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): findFirst with cursor 1 unique (non-PK) test/integration/test/ports/prisma/functional/extended-where/extended-where.test.ts:150 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): findFirstOrThrow with cursor 1 unique (PK) test/integration/test/ports/prisma/functional/extended-where/extended-where.test.ts:165 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): findFirstOrThrow with cursor 2 uniques (PK & non-PK) test/integration/test/ports/prisma/functional/extended-where/extended-where.test.ts:179 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): findFirstOrThrow with cursor 1 unique (non-PK) test/integration/test/ports/prisma/functional/extended-where/extended-where.test.ts:193 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • Skipped (documented): fails at runtime when an invalid entry is entered manually in Mongo test/integration/test/ports/prisma/functional/enums/enums.test.ts:8 — Skipped with a documented reason — a deferral, not lazy debt: declared it.fails — the body is expected to fail, so its failure is not reported
  • + 27 more in this group — see findings.md.
D24 · Comment Value · doc comments repeat the names · ×7
  • doc comments repeat the names packages/1-framework/3-tooling/cli/src/control-api/statements/statement-text.ts:1 — 0 of 22 documented parameters and 1 of 1307 summaries in `@internal/cli` only repeat the member or parameter name (e.g. "The verbs a statement can have." for `StatementVerb`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/1-framework/1-core/errors/src/control.ts:222 — 0 of 0 documented parameters and 2 of 50 summaries in `@internal/errors` only repeat the member or parameter name (e.g. "Contract validation failed." for `errorContractValidationFailed`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/2-sql-family/9-family/src/core/migrations/enum-value-planning.ts:61 — 0 of 4 documented parameters and 1 of 477 summaries in `@internal/family-sql` only repeat the member or parameter name (e.g. "One replacement of a stored value by another." for `StoredValueReplacement`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/1-framework/1-core/framework-components/src/control/control-descriptors.ts:94 — 0 of 2 documented parameters and 1 of 895 summaries in `@internal/framework-components` only repeat the member or parameter name (e.g. "How a control driver connects." for `ControlDriverConnectOptions`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/3-extensions/sql-orm-client/src/collection-types.ts:71 — 0 of 0 documented parameters and 1 of 289 summaries in `@internal/sql-orm-client` only repeat the member or parameter name (e.g. "The type state of a collection." for `CollectionTypeStateOf`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names packages/1-framework/3-tooling/vite-plugin-contract-emit/src/types.ts:2 — 0 of 2 documented parameters and 1 of 4 summaries in `@internal/vite-plugin-contract-emit` only repeat the member or parameter name (e.g. "Options for the Prisma Vite plugin." for `PrismaVitePluginOptions`). Delete the restating tags, or add what the name does not say.
  • doc comments repeat the names test/integration/test/control-api.test.ts:27 — 0 of 0 documented parameters and 4 of 393 summaries in `integration-tests` only repeat the member or parameter name (e.g. "Creates a test contract for testing." for `createTestContract`). Delete the restating tags, or add what the name does not say.
D5 · Coupling · Off the main sequence · ×2
  • Off the main sequence: @internal/contract — @internal/contract: abstractness 0.08, instability 0.02, distance 0.90 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
  • Off the main sequence: @internal/mongo-contract — @internal/mongo-contract: abstractness 0.00, instability 0.24, distance 0.76 — the shape a shared-kernel / building-block library has BY DESIGN — concrete and widely depended-on is what makes it useful, and this dimension does not penalise it (the distance is reported for completeness, not as a defect). Worth a look only if it has grown past one coherent kernel into an everything-bucket.
D23 · Boundary Type-Coupling · Contract · ×1
  • Contract: 1 contract type(s) expose producer-owned ids/enums — In Contract, 1 contract type(s) (Contract) expose strong-typed ids/value objects (ProfileHashBase); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
D23 · Boundary Type-Coupling · CrossReference · ×1
  • CrossReference: 1 contract type(s) expose producer-owned ids/enums — In CrossReference, 1 contract type(s) (CrossReference) expose strong-typed ids/value objects (NamespaceId); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
D23 · Boundary Type-Coupling · ForeignKeyReference · ×1
  • ForeignKeyReference: 1 contract type(s) expose producer-owned ids/enums — In ForeignKeyReference, 1 contract type(s) (ForeignKeyReference) expose strong-typed ids/value objects (NamespaceId); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
D23 · Boundary Type-Coupling · SqlStorage · ×1
  • SqlStorage: 1 contract type(s) expose producer-owned ids/enums — In SqlStorage, 1 contract type(s) (SqlStorage) expose strong-typed ids/value objects (StorageHashBase); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
D23 · Boundary Type-Coupling · SqlStorageInput · ×1
  • SqlStorageInput: 1 contract type(s) expose producer-owned ids/enums — In SqlStorageInput, 1 contract type(s) (SqlStorageInput) expose strong-typed ids/value objects (StorageHashBase); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
D23 · Boundary Type-Coupling · StorageBase · ×1
  • StorageBase: 1 contract type(s) expose producer-owned ids/enums — In StorageBase, 1 contract type(s) (StorageBase) expose strong-typed ids/value objects (StorageHashBase); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
D23 · Boundary Type-Coupling · hashing · ×1
  • hashing: 1 contract type(s) expose producer-owned ids/enums — In hashing, 1 contract type(s) (hashing) expose strong-typed ids/value objects (ExecutionHashBase, ProfileHashBase, StorageHashBase); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
D23 · Boundary Type-Coupling · namespace-id · ×1
  • namespace-id: 1 contract type(s) expose producer-owned ids/enums — In namespace-id, 1 contract type(s) (namespace-id) expose strong-typed ids/value objects (NamespaceId); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
D23 · Boundary Type-Coupling · types · ×1
  • types: 1 contract type(s) expose producer-owned ids/enums — In types, 1 contract type(s) (types) expose strong-typed ids/value objects (ExecutionHashBase, ProfileHashBase, StorageHashBase); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a65d23069eed40699dea971206fab31e/history.json --exit-code 0 --source .13artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-a65d23069eed40699dea971206fab31e/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude apps/telemetry-backend/migrations/snapshots --exclude examples/mongo-demo/migrations/snapshots --exclude examples/multi-extension-monorepo/app/migrations/audit/20260601T0000_create_audit_event --exclude examples/multi-extension-monorepo/app/migrations/feature-flags/20260601T0000_create_feature_flag --exclude examples/multi-extension-monorepo/app/migrations/snapshots --exclude examples/multi-extension-monorepo/packages/audit/migrations/snapshots --exclude examples/multi-extension-monorepo/packages/feature-flags/migrations/snapshots --exclude examples/paradedb-demo/migrations/paradedb/20260601T0000_install_pg_search_extension --exclude examples/paradedb-demo/migrations/paradedb/20261029T1342_create_pg_search_extension --exclude examples/paradedb-demo/migrations/paradedb/20261029T1342_declare_pg_search_extension --exclude examples/paradedb-demo/migrations/paradedb/20261106T1036_find_pg_search_on_search_path --exclude examples/paradedb-demo/migrations/paradedb/20261106T1401_install_pg_search_on_search_path --exclude examples/paradedb-demo/migrations/snapshots --exclude examples/prisma-8-demo/fixtures/converging-branches/migrations/snapshots --exclude examples/prisma-8-demo/fixtures/diamond/migrations/snapshots --exclude examples/prisma-8-demo/fixtures/long-spine/migrations/snapshots --exclude examples/prisma-8-demo/fixtures/multi-branch/migrations/snapshots --exclude examples/prisma-8-demo/fixtures/showcase/migrations/app/20260601T0729_reapply_noop --exclude examples/prisma-8-demo/fixtures/showcase/migrations/snapshots --exclude examples/prisma-8-demo/fixtures/skip-rollback/migrations/snapshots --exclude examples/prisma-8-demo/fixtures/wide-fan/migrations/snapshots --exclude examples/prisma-8-demo/migrations/pgvector/20260601T0000_install_vector_extension --exclude examples/prisma-8-demo/migrations/pgvector/20261029T1342_create_vector_extension --exclude examples/prisma-8-demo/migrations/pgvector/20261029T1342_declare_vector_extension --exclude examples/prisma-8-demo/migrations/pgvector/20261106T1035_find_vector_on_search_path --exclude examples/prisma-8-demo/migrations/pgvector/20261106T1401_install_vector_on_search_path --exclude examples/prisma-8-demo/migrations/snapshots --exclude examples/prisma-8-demo-mysql/migrations/snapshots --exclude examples/prisma-8-postgis-demo/migrations/postgis/20260601T0000_install_postgis_extension --exclude examples/prisma-8-postgis-demo/migrations/postgis/20261029T1342_create_postgis_extension --exclude examples/prisma-8-postgis-demo/migrations/postgis/20261029T1342_declare_postgis_extension --exclude examples/prisma-8-postgis-demo/migrations/postgis/20261106T1036_find_postgis_on_search_path --exclude examples/prisma-8-postgis-demo/migrations/postgis/20261106T1401_install_postgis_on_search_path --exclude examples/prisma-8-postgis-demo/migrations/snapshots --exclude examples/prisma7-adoption/generated --exclude examples/prisma7-adoption/migrations/citext/20261029T1520_create_citext_extension --exclude examples/prisma7-adoption/migrations/citext/20261106T1036_find_citext_on_search_path --exclude examples/prisma7-adoption/migrations/citext/20261106T1401_install_citext_on_search_path --exclude examples/prisma7-adoption/migrations/snapshots --exclude examples/retail-store/migrations/snapshots --exclude examples/supabase/migrations/snapshots --exclude packages/1-framework/3-tooling/cli/recordings/ascii --exclude packages/2-mongo-family/7-runtime/test/fixtures --exclude packages/2-sql-family/4-lanes/sql-builder/test/fixtures/generated --exclude packages/3-extensions/citext/migrations/snapshots --exclude packages/3-extensions/paradedb/migrations/snapshots --exclude packages/3-extensions/pgvector/migrations/snapshots --exclude packages/3-extensions/postgis/migrations/snapshots --exclude packages/3-extensions/sql-orm-client/test/fixtures/collection-methods --exclude packages/3-extensions/sql-orm-client/test/fixtures/fragment-namespace --exclude packages/3-extensions/sql-orm-client/test/fixtures/generated --exclude packages/3-extensions/sql-orm-client/test/fixtures/junction-namespaces --exclude packages/3-extensions/sql-orm-client/test/fixtures/on-update-only --exclude packages/3-extensions/sql-orm-client/test/fixtures/polymorphism --exclude packages/3-extensions/sql-orm-client/test/fixtures/scope-namespace --exclude packages/3-extensions/sql-orm-client/test/fixtures/soft-delete --exclude packages/3-extensions/sql-orm-client/test/fixtures/value-objects --exclude packages/3-targets/mysql/9-facade/test/fixtures/generated --exclude packages/3-targets/postgres/9-facade/test/fixtures/generated --exclude test/e2e/framework/test/fixtures/generated --exclude test/e2e/framework/test/sqlite/fixtures/generated --exclude test/integration/test/contract-parity/fixtures/mongo/generated --exclude test/integration/test/contract-parity/fixtures/postgres/generated --exclude test/integration/test/contract-parity/fixtures/sqlite/generated --exclude test/integration/test/date-time-defaults/_fixture-before-canonical-form/emitted-before --exclude test/integration/test/enum-members/_fixture-mongo/generated --exclude test/integration/test/enum-members/_fixture-native-enums/generated --exclude test/integration/test/enum-members/_fixture-postgres/generated --exclude test/integration/test/enum-members/_fixture-sqlite/generated --exclude test/integration/test/enum-order-by/_fixture/generated --exclude test/integration/test/mongo/bson-scalars/_fixture/generated --exclude test/integration/test/mongo/fixtures/generated --exclude test/integration/test/mongo/list-filters/_fixture/generated --exclude test/integration/test/mongo/prisma6-source/_fixture/generated --exclude test/integration/test/mongo/recursive-value-objects/_fixture/generated --exclude test/integration/test/mongo/temporal-generators/_fixture/generated --exclude test/integration/test/mongo/temporal-generators/_fixture-aliases/generated --exclude test/integration/test/mongo/temporal-generators/_fixture-attributes/generated --exclude test/integration/test/namespaced-accessors/fixtures/generated --exclude test/integration/test/planner-golden/fixtures/postgres/generated --exclude test/integration/test/planner-golden/fixtures/sqlite/generated --exclude test/integration/test/ports/engines/queries/aggregation/avg/_fixture/decimal/generated --exclude test/integration/test/ports/engines/queries/aggregation/avg/_fixture/numeric/generated --exclude test/integration/test/ports/engines/queries/aggregation/count/_fixture/generated --exclude test/integration/test/ports/engines/queries/aggregation/group_by/_fixture/main/generated --exclude test/integration/test/ports/engines/queries/aggregation/group_by/_fixture/regression-21789/generated --exclude test/integration/test/ports/engines/queries/aggregation/group_by_having/_fixture/common/generated --exclude test/integration/test/ports/engines/queries/aggregation/group_by_having/_fixture/decimal/generated --exclude test/integration/test/ports/engines/queries/aggregation/many_count_relation/_fixture/compound/generated --exclude test/integration/test/ports/engines/queries/aggregation/many_count_relation/_fixture/generated --exclude test/integration/test/ports/engines/queries/aggregation/many_count_relation/_fixture/nested/generated --exclude test/integration/test/ports/engines/queries/aggregation/many_count_relation/_fixture/self/generated --exclude test/integration/test/ports/engines/queries/aggregation/max/_fixture/common/generated --exclude test/integration/test/ports/engines/queries/aggregation/max/_fixture/decimal/generated --exclude test/integration/test/ports/engines/queries/aggregation/min/_fixture/common/generated --exclude test/integration/test/ports/engines/queries/aggregation/min/_fixture/decimal/generated --exclude test/integration/test/ports/engines/queries/aggregation/sum/_fixture/decimal/generated --exclude test/integration/test/ports/engines/queries/aggregation/sum/_fixture/numeric/generated --exclude test/integration/test/ports/engines/queries/aggregation/uniq-count-relation/_fixture/base/generated --exclude test/integration/test/ports/engines/queries/aggregation/uniq-count-relation/_fixture/nested/generated --exclude test/integration/test/ports/engines/queries/data_types/bigint/_fixture/generated --exclude test/integration/test/ports/engines/queries/data_types/bool/_fixture/generated --exclude test/integration/test/ports/engines/queries/data_types/bytes/_fixture/relations/generated --exclude test/integration/test/ports/engines/queries/data_types/bytes/_fixture/scalars/generated --exclude test/integration/test/ports/engines/queries/data_types/datetime/_fixture/generated --exclude test/integration/test/ports/engines/queries/data_types/decimal/_fixture/generated --exclude test/integration/test/ports/engines/queries/data_types/enum_type/_fixture/postgres/generated --exclude test/integration/test/ports/engines/queries/data_types/float/_fixture/generated --exclude test/integration/test/ports/engines/queries/data_types/int/_fixture/generated --exclude test/integration/test/ports/engines/queries/data_types/json/_fixture/scalar/generated --exclude test/integration/test/ports/engines/queries/data_types/native/postgres/_fixture/other/generated --exclude test/integration/test/ports/engines/queries/data_types/native/postgres/_fixture/string/generated --exclude test/integration/test/ports/engines/queries/data_types/string/_fixture/generated --exclude test/integration/test/ports/engines/queries/data_types/through_relation/_fixture/common/generated --exclude test/integration/test/ports/engines/queries/data_types/through_relation/_fixture/decimal/generated --exclude test/integration/test/ports/engines/queries/data_types/through_relation/_fixture/enum/generated --exclude test/integration/test/ports/engines/queries/data_types/through_relation/_fixture/json/generated --exclude test/integration/test/ports/engines/queries/data_types/through_relation/_fixture/lists/generated --exclude test/integration/test/ports/engines/queries/distinct/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/bigint_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/bytes_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/decimal_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/_fixture/decimal-list/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/_fixture/enum/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/_fixture/list/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/_fixture/mixed/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/bigint_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/bytes_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/datetime_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/decimal_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/failure/_fixture/common/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/failure/_fixture/default/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/failure/_fixture/list/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/float_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/having_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/int_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/json_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/json_filter/_fixture/list/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/relation_filter/_fixture/complex/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/relation_filter/_fixture/one-to-many/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/relation_filter/_fixture/one-to-one/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/relation_filter/_fixture/one-to-one-list/generated --exclude test/integration/test/ports/engines/queries/filters/field_reference/string_filter/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/filter_regression/_fixture/compound-one-to-many/generated --exclude test/integration/test/ports/engines/queries/filters/filter_regression/_fixture/many-to-many/generated --exclude test/integration/test/ports/engines/queries/filters/filter_regression/_fixture/one-to-many/generated --exclude test/integration/test/ports/engines/queries/filters/filters/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/json/_fixture/optional/generated --exclude test/integration/test/ports/engines/queries/filters/list_filters/_fixture/base/generated --exclude test/integration/test/ports/engines/queries/filters/list_filters/_fixture/decimal/generated --exclude test/integration/test/ports/engines/queries/filters/list_filters/_fixture/json/generated --exclude test/integration/test/ports/engines/queries/filters/many_relation/_fixture/25103/generated --exclude test/integration/test/ports/engines/queries/filters/many_relation/_fixture/l2-to-one/generated --exclude test/integration/test/ports/engines/queries/filters/one2one_regression/_fixture/generated --exclude test/integration/test/ports/engines/queries/filters/one_relation/_fixture/21356/generated --exclude test/integration/test/ports/engines/queries/filters/one_relation/_fixture/21366/generated --exclude test/integration/test/ports/engines/writes/top_level_mutations/create_many/_fixture/generated --exclude test/integration/test/ports/prisma/functional/batching-bigint/_fixture/generated --exclude test/integration/test/ports/prisma/functional/batching-bytes/_fixture/generated --exclude test/integration/test/ports/prisma/functional/blog-update/_fixture/generated --exclude test/integration/test/ports/prisma/functional/bytes-upsert/_fixture/generated --exclude test/integration/test/ports/prisma/functional/chunking-query/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-create/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-createMany/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-delete/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-deleteMany/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-findFirst/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-findMany/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-update/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-updateMany/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-upsert-create/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-list-upsert-update/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-create/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-createMany/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-delete/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-deleteMany/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-findFirst/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-findMany/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-update/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-updateMany/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-upsert-create/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-object-upsert-update/_fixture/generated --exclude test/integration/test/ports/prisma/functional/composites-selection/_fixture/generated --exclude test/integration/test/ports/prisma/functional/create-default-date/_fixture/generated --exclude test/integration/test/ports/prisma/functional/decimal-list/_fixture/generated --exclude test/integration/test/ports/prisma/functional/decimal-precision/_fixture/generated --exclude test/integration/test/ports/prisma/functional/decimal-scalar/_fixture/generated --exclude test/integration/test/ports/prisma/functional/default-selection/_fixture/generated --exclude test/integration/test/ports/prisma/functional/default-selection/_fixture/mongo/generated --exclude test/integration/test/ports/prisma/functional/distinct/_fixture/generated --exclude test/integration/test/ports/prisma/functional/driver-adapters-error-forwarding/_fixture/generated --exclude test/integration/test/ports/prisma/functional/driver-adapters-team-orm-687-bytes/_fixture/generated --exclude test/integration/test/ports/prisma/functional/driver-adapters-validate-active-provider/_fixture/generated --exclude test/integration/test/ports/prisma/functional/driver-adapters-validate-active-provider/_fixture/sqlite/generated --exclude test/integration/test/ports/prisma/functional/enum-array/_fixture/generated --exclude test/integration/test/ports/prisma/functional/enums/_fixture/generated --exclude test/integration/test/ports/prisma/functional/extended-where/_fixture/generated --exclude test/integration/test/ports/prisma/functional/filter-count-relations/_fixture/generated --exclude test/integration/test/ports/prisma/functional/find-unique-or-throw-batching/_fixture/generated --exclude test/integration/test/ports/prisma/functional/handle-int-overflow/_fixture/generated --exclude test/integration/test/ports/prisma/functional/interactive-transactions/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-11974/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-12378/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-12557/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-12572/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-13089-dollar-in-search/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-14271/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-14954-date-batch/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-15044/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-16535-select-enum/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-17005-args-type-conflict/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-17030-args-type-conflict/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-18970-invalid-date/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-20261-group-by-shortcut/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-21352-id-does-not-exist/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-21454-type-in-json/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-21631-batching-in-transaction/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-22098-column-does-not-exist/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-22610-parallel-batch/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-23201-non-ascii-comments/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-23902/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-25404/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-27455-bytes-id/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-27511-include-enum-array/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-28151-broken-nested-set/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-28192-pg-historical-dates/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-28591-mapped-enums/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-29010-bigint-precision-relation-joins/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-29174-jsonb-parameter-regression/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-29176-cursor-parameter-regression/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-29254-query-plan-cache-mutation/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-29267-uint8array-in-json/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-29309-datetime-cursor/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-29331-query-plan-cache-bloat/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-4004/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-5952-decimal-batch/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-TML-1664-invalid-enum-value-error/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-TML-1664-unknown-enum-value-read-error/_fixture/generated --exclude test/integration/test/ports/prisma/functional/issues-unmapped-driver-error-user-facing/_fixture/generated --exclude test/integration/test/ports/prisma/functional/json-fields/_fixture/generated --exclude test/integration/test/ports/prisma/functional/large-floats/_fixture/generated --exclude test/integration/test/ports/prisma/functional/legacy-aggregate-raw/_fixture/generated --exclude test/integration/test/ports/prisma/functional/legacy-aggregations/_fixture/generated --exclude test/integration/test/ports/prisma/functional/legacy-json/_fixture/generated --exclude test/integration/test/ports/prisma/functional/legacy-malformed-id/_fixture/generated --exclude test/integration/test/ports/prisma/functional/legacy-optional-relation-filters/_fixture/generated --exclude test/integration/test/ports/prisma/functional/methods-count/_fixture/generated --exclude test/integration/test/ports/prisma/functional/methods-createMany/_fixture/generated --exclude test/integration/test/ports/prisma/functional/methods-createManyAndReturn/_fixture/generated --exclude test/integration/test/ports/prisma/functional/methods-findFirstOrThrow/_fixture/generated --exclude test/integration/test/ports/prisma/functional/methods-findUniqueOrThrow/_fixture/generated --exclude test/integration/test/ports/prisma/functional/methods-updateManyAndReturn/_fixture/generated --exclude test/integration/test/ports/prisma/functional/methods-upsert-native-atomic/_fixture/generated --exclude test/integration/test/ports/prisma/functional/methods-upsert-simple/_fixture/generated --exclude test/integration/test/ports/prisma/functional/mixed-string-uuid-datetime-list-inputs/_fixture/generated --exclude test/integration/test/ports/prisma/functional/multi-schema/_fixture/different-names/generated --exclude test/integration/test/ports/prisma/functional/multi-schema/_fixture/identical-names/generated --exclude test/integration/test/ports/prisma/functional/multi-schema/_fixture/no-map/generated --exclude test/integration/test/ports/prisma/functional/multiple-types/_fixture/generated --exclude test/integration/test/ports/prisma/functional/optimistic-concurrency-control/_fixture/generated --exclude test/integration/test/ports/prisma/functional/referential-actions-set-default-1to1/_fixture/generated --exclude test/integration/test/ports/prisma/functional/referential-actions-set-default-1ton/_fixture/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-17255-mixed-actions/_fixture/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-17255-same-actions/_fixture/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-1/_fixture/cascade-map/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-1/_fixture/cascade-plain/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-1/_fixture/noaction-map/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-1/_fixture/noaction-plain/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-1/_fixture/restrict-map/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-1/_fixture/restrict-plain/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-1/_fixture/setnull-map/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-1/_fixture/setnull-plain/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-n/_fixture/cascade-map/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-n/_fixture/cascade-plain/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-n/_fixture/noaction-map/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-n/_fixture/noaction-plain/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-n/_fixture/restrict-map/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-n/_fixture/restrict-plain/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-n/_fixture/setnull-map/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-1-to-n/_fixture/setnull-plain/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-m-to-n/_fixture/cascade-nomap/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-m-to-n/_fixture/default-nomap/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-m-to-n/_fixture/noaction-nomap/generated --exclude test/integration/test/ports/prisma/functional/relation-mode-gh-m-to-n/_fixture/restrict-nomap/generated --exclude test/integration/test/sql-builder/fixtures/generated --exclude test/integration/test/sql-builder/fixtures/generated-no-pgvector --exclude test/integration/test/sql-orm-client/fixtures/collection-methods/generated --exclude test/integration/test/sql-orm-client/fixtures/execution-defaulted-tags/generated --exclude test/integration/test/sql-orm-client/fixtures/fragment-namespace/generated --exclude test/integration/test/sql-orm-client/fixtures/generated --exclude test/integration/test/sql-orm-client/fixtures/integer-representation/generated --exclude test/integration/test/sql-orm-client/fixtures/integer-representation-sqlite/generated --exclude test/integration/test/sql-orm-client/fixtures/junction-namespaces/generated --exclude test/integration/test/sql-orm-client/fixtures/mn-psl/generated --exclude test/integration/test/sql-orm-client/fixtures/non-identifier-names/generated --exclude test/integration/test/sql-orm-client/fixtures/on-update-only/generated --exclude test/integration/test/sql-orm-client/fixtures/polymorphism/generated --exclude test/integration/test/sql-orm-client/fixtures/polymorphism-namespaces/generated --exclude test/integration/test/sql-orm-client/fixtures/polymorphism-self-relation/generated --exclude test/integration/test/sql-orm-client/fixtures/scalar-lists/generated --exclude test/integration/test/sql-orm-client/fixtures/scope-namespace/generated --exclude test/integration/test/sql-orm-client/fixtures/self-relations/generated --exclude test/integration/test/sql-orm-client/fixtures/soft-delete/generated --exclude test/integration/test/sql-orm-client/fixtures/value-objects/generated --exclude test/integration/test/sql-orm-client/fixtures/without-conflict-target/generated --exclude test/integration/test/sql-orm-client/fixtures/without-returning-sqlite/generated --exclude test/integration/test/temporal-defaults/_fixture/generated --exclude test/integration/test/temporal-defaults/_fixture-aliases/generated --exclude test/integration/test/temporal-defaults/_fixture-attributes/generated --exclude test/integration/test/temporal-defaults/_fixture-now/generated --exclude test/integration/test/temporal-defaults/_fixture-timestamp/generated --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/db-migrations/after/db/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/db-migrations/before/db/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/extension-package/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/extension-package/after/src --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/extension-package/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/extension-package/before/src --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/json-default-document --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/postgres-extension-space/after/migrations/pgvector/20260601T0000_install_vector_extension --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/postgres-extension-space/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/postgres-extension-space/after/mongo --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/postgres-extension-space/after/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/postgres-extension-space/before/migrations/pgvector/20260601T0000_install_vector_extension --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/postgres-extension-space/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/postgres-extension-space/before/mongo --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/postgres-extension-space/before/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-enum-list/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-enum-list/after/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-enum-list/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-enum-list/before/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-lists/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-lists/after/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-lists/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-lists/before/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-no-lists/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-no-lists/after/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-no-lists/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/rc14-no-lists/before/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/snapshot-already-present --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/snapshot-collision --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-defaults/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-defaults/after/src --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-defaults/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-defaults/before/src --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-integer-enums/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-integer-enums/after/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-integer-enums/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-integer-enums/before/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-json-enums/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-json-enums/after/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-json-enums/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/sqlite-json-enums/before/prisma --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/stale-hash/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/stale-hash/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/two-migration-roots/after/billing/history/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/two-migration-roots/after/db/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/two-migration-roots/before/billing/history/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/two-migration-roots/before/db/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/unknown-codec --exclude test/integration/test/upgrade-instructions/data-type-in-contract/fixtures/unknown-target --exclude test/integration/test/upgrade-instructions/data-type-values/fixtures/sqlite-project/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-values/fixtures/sqlite-project/after/src --exclude test/integration/test/upgrade-instructions/data-type-values/fixtures/sqlite-project/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/data-type-values/fixtures/sqlite-project/before/src --exclude test/integration/test/upgrade-instructions/expand-type-aliases/fixtures/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/expand-type-aliases/fixtures/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/mongo-field-storage-names/fixtures --exclude test/integration/test/upgrade-instructions/mongo-index-names/fixtures/monorepo --exclude test/integration/test/upgrade-instructions/mongo-index-names/fixtures/prisma6-project/after/migrations --exclude test/integration/test/upgrade-instructions/mongo-index-names/fixtures/prisma6-project/before/migrations --exclude test/integration/test/upgrade-instructions/mongo-index-names/fixtures/project --exclude test/integration/test/upgrade-instructions/mongo-index-names/fixtures/two-projects --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/extension-default-forms/after --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/extension-default-forms/before --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/list-defaults --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/nocheck/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/nocheck/after/prisma --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/nocheck/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/nocheck/before/prisma --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-default-forms/after --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-default-forms/before --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-default-not-a-value/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-default-not-a-value/after/src --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-default-not-a-value/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-default-not-a-value/before/src --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-defaults/after/migrations/snapshots --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-defaults/after/src --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-defaults/before/migrations/snapshots --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/postgres-defaults/before/src --exclude test/integration/test/upgrade-instructions/remove-nocheck/fixtures/rc18-emitted --exclude test/integration/test/upgrade-instructions/value-objects-in-storage/fixtures/after/mongo/migrations/snapshots --exclude test/integration/test/upgrade-instructions/value-objects-in-storage/fixtures/after/mongo/src --exclude test/integration/test/upgrade-instructions/value-objects-in-storage/fixtures/after/sql/migrations/snapshots --exclude test/integration/test/upgrade-instructions/value-objects-in-storage/fixtures/before/mongo/migrations/snapshots --exclude test/integration/test/upgrade-instructions/value-objects-in-storage/fixtures/before/mongo/src --exclude test/integration/test/upgrade-instructions/value-objects-in-storage/fixtures/before/sql/migrations/snapshots .41artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update40artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .2artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 203 file(s) — `REDACTED`, `apps/telemetry-backend/src/db.ts`, `apps/telemetry-backend/src/handler.ts`, `apps/telemetry-backend/src/schema.ts`, `dependency-cruiser.config.mjs`, … (+198 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update0artifacts/raw/trivy-fs.json

Run 01a1b747-e829-7f50-9731-da80652188b0 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 84 · Warnings: 4038 · Recommendations: 695 · Info: 70 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 07-11-2026 @ 18:31 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.

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