Public report of drizzle-team/drizzle-orm, published 26 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog 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, 26 October 2026, 18:58 UTC · Survey ID cd_883548c969f24051ac98aad08d3834ce
drizzle-team/drizzle-orm
Measured 26 October 2026, 18:41 UTC, at code version eab8bed
A regression is a drop of 0.5 points or more in the score, or of 2.5 or more out of 10 in a dimension, since the last survey.
Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureNoCollector).
CAI scoreAt riskUp 2 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 215,596 lines of product code in 8 projects, tests not counted · Estimated rebuild effort: about 2.0 person-years · Weakest lens: Security and Compliance, 30
Findings by how serious they are
112 critical596 serious252 minor
13 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks 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
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
26 October 2026, 18:41 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 Watchdog. It is open to any tool that
implements it, and today Watchdog 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. Watchdog works 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 ▸
73of 73 dimensions measured by tools.
914of 960 findings point to an exact file and line, so you can open each one in the code. The other 46 concern the repository as a whole, such as missing documentation.
73dimensions across 6 lenses, read from 215,596 lines of product code in 8 projects.
drizzle-team/drizzle-orm is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because 52 of the dependencies have a known vulnerability and we found no encryption of stored data, no key vault and no enforced HTTPS. It scores 45 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 30, 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 13 points. Replacing the 21 deprecated dependencies comes next, worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 57.
Sixty-two known security holes in the packages the code depends on can be used by attackers. Thirty-two pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and five weaknesses in the code could be used by an attacker. Updating the vulnerable packages, pinning each tool to an exact version and fixing the weaknesses the scanner points to would close these risks. Passing outside input through environment variables would fix the two pipeline steps that put outside input straight into a shell command, and limiting each secret to its own step would deal with the two secrets exposed to more of the pipeline than needed. The two loops of files that import each other need breaking.
The product code is 215,596 lines, about €300,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Incompleteness & stubs · Both branches are identical — the condition decides nothing drizzle-seed/src/index.ts
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 409 findings
These 409 critical or serious findings were in the previous survey, on 12 October 2026, and are gone from this one. The first 100 are listed here.
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Supply-chain Provenance & Signing REDACTED
Code Duplication · Duplicated block with local edits (84 matched lines × 2 locations) drizzle-orm/src/mysql-core/columns/common.ts
Code Duplication · Duplicated block with local edits (33 matched lines × 2 locations) drizzle-orm/src/pg-core/columns/vector_extension/sparsevec.ts
Rebuild cost: about €300,000 · Estimate
Cost to rebuild
€99,000 to €490,000, for 1,642 to 5,210 hours of work, about 2.0 person-years for 1 to 4 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 45. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 215,596 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: Watchdog prices 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 13 points · Medium effort · Data Protection
2
Resolve the 21 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (21).
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 €300,000 to build again, about 2.0 person-years of work. Its weakest lens is Security and Compliance, at 30 (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 13 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 7.3 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 55 lines over the last 90 days, which is about 223 lines a year. At that pace, the extra work comes to an estimated 0 to 0.1 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 Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
428 modules, with 1057 dependencies between them. 7 loops run through 45 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 388 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.
drizzle-orm.src.gel-core.indexes uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.gel-core.indexes, while a change to drizzle-orm.src.gel-core.indexes can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.gel-core.indexes uses a module listed above it, which is the healthy direction.
11→29 drizzle-orm.src.gel-core.indexes uses drizzle-orm.src.gel-core.tablepart of a loop✕
Connections
2 pairs of types, where a type in drizzle-orm.src.gel-core.indexes uses a type in drizzle-orm.src.gel-core.table.
drizzle-orm.src.gel-core.indexes uses drizzle-orm.src.gel-core.table, so a change to drizzle-orm.src.gel-core.table can break drizzle-orm.src.gel-core.indexes, while a change to drizzle-orm.src.gel-core.indexes can't break drizzle-orm.src.gel-core.table.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
drizzle-orm.src.gel-core.query-builders.select_types uses drizzle-orm.src.query-builders.select_types, so a change to drizzle-orm.src.query-builders.select_types can break drizzle-orm.src.gel-core.query-builders.select_types, while a change to drizzle-orm.src.gel-core.query-builders.select_types can't break drizzle-orm.src.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.gel-core.query-builders.select_types uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.query-builders.select_types uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.gel-core.query-builders.select_types, while a change to drizzle-orm.src.gel-core.query-builders.select_types can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.gel-core.query-builders.select_types uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.table uses drizzle-orm.src.table, so a change to drizzle-orm.src.table can break drizzle-orm.src.mysql-core.table, while a change to drizzle-orm.src.mysql-core.table can't break drizzle-orm.src.table.
Position
Below the diagonal: drizzle-orm.src.mysql-core.table uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.table uses drizzle-orm.src.table, so a change to drizzle-orm.src.table can break drizzle-orm.src.pg-core.table, while a change to drizzle-orm.src.pg-core.table can't break drizzle-orm.src.table.
Position
Below the diagonal: drizzle-orm.src.pg-core.table uses a module listed above it, which is the healthy direction.
14→24 drizzle-orm.src.pg-core.table uses drizzle-orm.src.pg-core.columns.commonpart of a loop✕
Connections
1 pair of types, where a type in drizzle-orm.src.pg-core.table uses a type in drizzle-orm.src.pg-core.columns.common.
drizzle-orm.src.pg-core.table uses drizzle-orm.src.pg-core.columns.common, so a change to drizzle-orm.src.pg-core.columns.common can break drizzle-orm.src.pg-core.table, while a change to drizzle-orm.src.pg-core.table can't break drizzle-orm.src.pg-core.columns.common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
drizzle-orm.src.relations uses drizzle-orm.src.column, so a change to drizzle-orm.src.column can break drizzle-orm.src.relations, while a change to drizzle-orm.src.relations can't break drizzle-orm.src.column.
Position
Below the diagonal: drizzle-orm.src.relations uses a module listed above it, which is the healthy direction.
drizzle-orm.src.relations uses drizzle-orm.src.table, so a change to drizzle-orm.src.table can break drizzle-orm.src.relations, while a change to drizzle-orm.src.relations can't break drizzle-orm.src.table.
Position
Below the diagonal: drizzle-orm.src.relations uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.columns.common uses drizzle-orm.src.column, so a change to drizzle-orm.src.column can break drizzle-orm.src.singlestore-core.columns.common, while a change to drizzle-orm.src.singlestore-core.columns.common can't break drizzle-orm.src.column.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.columns.common uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.session uses drizzle-orm.src.cache.core.cache, so a change to drizzle-orm.src.cache.core.cache can break drizzle-orm.src.sqlite-core.session, while a change to drizzle-orm.src.sqlite-core.session can't break drizzle-orm.src.cache.core.cache.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.session uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.session uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.sqlite-core.session, while a change to drizzle-orm.src.sqlite-core.session can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.session uses a module listed above it, which is the healthy direction.
17→28 drizzle-orm.src.sqlite-core.session uses drizzle-orm.src.sqlite-core.dbpart of a loop✕
Connections
1 pair of types, where a type in drizzle-orm.src.sqlite-core.session uses a type in drizzle-orm.src.sqlite-core.db.
drizzle-orm.src.sqlite-core.session uses drizzle-orm.src.sqlite-core.db, so a change to drizzle-orm.src.sqlite-core.db can break drizzle-orm.src.sqlite-core.session, while a change to drizzle-orm.src.sqlite-core.session can't break drizzle-orm.src.sqlite-core.db.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
drizzle-orm.src.sqlite-core.table uses drizzle-orm.src.table, so a change to drizzle-orm.src.table can break drizzle-orm.src.sqlite-core.table, while a change to drizzle-orm.src.sqlite-core.table can't break drizzle-orm.src.table.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.table uses a module listed above it, which is the healthy direction.
drizzle-orm.src.utils uses drizzle-orm.src.cache.core.cache, so a change to drizzle-orm.src.cache.core.cache can break drizzle-orm.src.utils, while a change to drizzle-orm.src.utils can't break drizzle-orm.src.cache.core.cache.
Position
Below the diagonal: drizzle-orm.src.utils uses a module listed above it, which is the healthy direction.
drizzle-kit.src.cli.commands uses drizzle-orm.src.column, so a change to drizzle-orm.src.column can break drizzle-kit.src.cli.commands, while a change to drizzle-kit.src.cli.commands can't break drizzle-orm.src.column.
Position
Below the diagonal: drizzle-kit.src.cli.commands uses a module listed above it, which is the healthy direction.
drizzle-kit.src.cli.commands uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-kit.src.cli.commands, while a change to drizzle-kit.src.cli.commands can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-kit.src.cli.commands uses a module listed above it, which is the healthy direction.
drizzle-kit.src.cli.commands uses drizzle-orm.src.table, so a change to drizzle-orm.src.table can break drizzle-kit.src.cli.commands, while a change to drizzle-kit.src.cli.commands can't break drizzle-orm.src.table.
Position
Below the diagonal: drizzle-kit.src.cli.commands uses a module listed above it, which is the healthy direction.
drizzle-kit.src.cli.commands uses drizzle-orm.src.utils, so a change to drizzle-orm.src.utils can break drizzle-kit.src.cli.commands, while a change to drizzle-kit.src.cli.commands can't break drizzle-orm.src.utils.
Position
Below the diagonal: drizzle-kit.src.cli.commands uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.columns.common uses drizzle-orm.src.column, so a change to drizzle-orm.src.column can break drizzle-orm.src.gel-core.columns.common, while a change to drizzle-orm.src.gel-core.columns.common can't break drizzle-orm.src.column.
Position
Below the diagonal: drizzle-orm.src.gel-core.columns.common uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.columns.common uses drizzle-orm.src.gel-core.indexes, so a change to drizzle-orm.src.gel-core.indexes can break drizzle-orm.src.gel-core.columns.common, while a change to drizzle-orm.src.gel-core.columns.common can't break drizzle-orm.src.gel-core.indexes.
Position
Below the diagonal: drizzle-orm.src.gel-core.columns.common uses a module listed above it, which is the healthy direction.
21→29 drizzle-orm.src.gel-core.columns.common uses drizzle-orm.src.gel-core.tablepart of a loop✕
Connections
2 pairs of types, where a type in drizzle-orm.src.gel-core.columns.common uses a type in drizzle-orm.src.gel-core.table.
drizzle-orm.src.gel-core.columns.common uses drizzle-orm.src.gel-core.table, so a change to drizzle-orm.src.gel-core.table can break drizzle-orm.src.gel-core.columns.common, while a change to drizzle-orm.src.gel-core.columns.common can't break drizzle-orm.src.gel-core.table.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
drizzle-orm.src.mysql-core.columns.common uses drizzle-orm.src.column, so a change to drizzle-orm.src.column can break drizzle-orm.src.mysql-core.columns.common, while a change to drizzle-orm.src.mysql-core.columns.common can't break drizzle-orm.src.column.
Position
Below the diagonal: drizzle-orm.src.mysql-core.columns.common uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.columns.common uses drizzle-orm.src.mysql-core.table, so a change to drizzle-orm.src.mysql-core.table can break drizzle-orm.src.mysql-core.columns.common, while a change to drizzle-orm.src.mysql-core.columns.common can't break drizzle-orm.src.mysql-core.table.
Position
Below the diagonal: drizzle-orm.src.mysql-core.columns.common uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.session uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.mysql-core.session, while a change to drizzle-orm.src.mysql-core.session can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.mysql-core.session uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.session uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.mysql-core.session, while a change to drizzle-orm.src.mysql-core.session can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.mysql-core.session uses a module listed above it, which is the healthy direction.
23→30 drizzle-orm.src.mysql-core.session uses drizzle-orm.src.mysql-core.dialectpart of a loop✕
Connections
2 pairs of types, where a type in drizzle-orm.src.mysql-core.session uses a type in drizzle-orm.src.mysql-core.dialect.
drizzle-orm.src.mysql-core.session uses drizzle-orm.src.mysql-core.dialect, so a change to drizzle-orm.src.mysql-core.dialect can break drizzle-orm.src.mysql-core.session, while a change to drizzle-orm.src.mysql-core.session can't break drizzle-orm.src.mysql-core.dialect.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→36 drizzle-orm.src.mysql-core.session uses drizzle-orm.src.mysql-core.dbpart of a loop✕
Connections
1 pair of types, where a type in drizzle-orm.src.mysql-core.session uses a type in drizzle-orm.src.mysql-core.db.
drizzle-orm.src.mysql-core.session uses drizzle-orm.src.mysql-core.db, so a change to drizzle-orm.src.mysql-core.db can break drizzle-orm.src.mysql-core.session, while a change to drizzle-orm.src.mysql-core.session can't break drizzle-orm.src.mysql-core.db.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
drizzle-orm.src.pg-core.columns.common uses drizzle-orm.src.column, so a change to drizzle-orm.src.column can break drizzle-orm.src.pg-core.columns.common, while a change to drizzle-orm.src.pg-core.columns.common can't break drizzle-orm.src.column.
Position
Below the diagonal: drizzle-orm.src.pg-core.columns.common uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.columns.common uses drizzle-orm.src.pg-core.table, so a change to drizzle-orm.src.pg-core.table can break drizzle-orm.src.pg-core.columns.common, while a change to drizzle-orm.src.pg-core.columns.common can't break drizzle-orm.src.pg-core.table.
Position
Below the diagonal: drizzle-orm.src.pg-core.columns.common uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.session uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.pg-core.session, while a change to drizzle-orm.src.pg-core.session can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.pg-core.session uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.session uses drizzle-orm.src.utils, so a change to drizzle-orm.src.utils can break drizzle-orm.src.pg-core.session, while a change to drizzle-orm.src.pg-core.session can't break drizzle-orm.src.utils.
Position
Below the diagonal: drizzle-orm.src.pg-core.session uses a module listed above it, which is the healthy direction.
25→31 drizzle-orm.src.pg-core.session uses drizzle-orm.src.pg-core.dialectpart of a loop✕
Connections
2 pairs of types, where a type in drizzle-orm.src.pg-core.session uses a type in drizzle-orm.src.pg-core.dialect.
drizzle-orm.src.pg-core.session uses drizzle-orm.src.pg-core.dialect, so a change to drizzle-orm.src.pg-core.dialect can break drizzle-orm.src.pg-core.session, while a change to drizzle-orm.src.pg-core.session can't break drizzle-orm.src.pg-core.dialect.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→37 drizzle-orm.src.pg-core.session uses drizzle-orm.src.pg-core.dbpart of a loop✕
Connections
1 pair of types, where a type in drizzle-orm.src.pg-core.session uses a type in drizzle-orm.src.pg-core.db.
drizzle-orm.src.pg-core.session uses drizzle-orm.src.pg-core.db, so a change to drizzle-orm.src.pg-core.db can break drizzle-orm.src.pg-core.session, while a change to drizzle-orm.src.pg-core.session can't break drizzle-orm.src.pg-core.db.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
drizzle-orm.src.singlestore-core.session uses drizzle-orm.src.cache.core.cache, so a change to drizzle-orm.src.cache.core.cache can break drizzle-orm.src.singlestore-core.session, while a change to drizzle-orm.src.singlestore-core.session can't break drizzle-orm.src.cache.core.cache.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.session uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.session uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.singlestore-core.session, while a change to drizzle-orm.src.singlestore-core.session can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.session uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.session uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.singlestore-core.session, while a change to drizzle-orm.src.singlestore-core.session can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.session uses a module listed above it, which is the healthy direction.
26→32 drizzle-orm.src.singlestore-core.session uses drizzle-orm.src.singlestore-core.dialectpart of a loop✕
Connections
2 pairs of types, where a type in drizzle-orm.src.singlestore-core.session uses a type in drizzle-orm.src.singlestore-core.dialect.
drizzle-orm.src.singlestore-core.session uses drizzle-orm.src.singlestore-core.dialect, so a change to drizzle-orm.src.singlestore-core.dialect can break drizzle-orm.src.singlestore-core.session, while a change to drizzle-orm.src.singlestore-core.session can't break drizzle-orm.src.singlestore-core.dialect.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
drizzle-orm.src.sqlite-core.columns.common uses drizzle-orm.src.column, so a change to drizzle-orm.src.column can break drizzle-orm.src.sqlite-core.columns.common, while a change to drizzle-orm.src.sqlite-core.columns.common can't break drizzle-orm.src.column.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.columns.common uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.columns.common uses drizzle-orm.src.sqlite-core.table, so a change to drizzle-orm.src.sqlite-core.table can break drizzle-orm.src.sqlite-core.columns.common, while a change to drizzle-orm.src.sqlite-core.columns.common can't break drizzle-orm.src.sqlite-core.table.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.columns.common uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.db uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.sqlite-core.db, while a change to drizzle-orm.src.sqlite-core.db can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.db uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.sqlite-core.db, while a change to drizzle-orm.src.sqlite-core.db can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.db uses drizzle-orm.src.sqlite-core.session, so a change to drizzle-orm.src.sqlite-core.session can break drizzle-orm.src.sqlite-core.db, while a change to drizzle-orm.src.sqlite-core.db can't break drizzle-orm.src.sqlite-core.session.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.table uses drizzle-orm.src.table, so a change to drizzle-orm.src.table can break drizzle-orm.src.gel-core.table, while a change to drizzle-orm.src.gel-core.table can't break drizzle-orm.src.table.
Position
Below the diagonal: drizzle-orm.src.gel-core.table uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.table uses drizzle-orm.src.gel-core.columns.common, so a change to drizzle-orm.src.gel-core.columns.common can break drizzle-orm.src.gel-core.table, while a change to drizzle-orm.src.gel-core.table can't break drizzle-orm.src.gel-core.columns.common.
Position
Below the diagonal: drizzle-orm.src.gel-core.table uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.dialect uses drizzle-orm.src.durable-sqlite.migrator, so a change to drizzle-orm.src.durable-sqlite.migrator can break drizzle-orm.src.mysql-core.dialect, while a change to drizzle-orm.src.mysql-core.dialect can't break drizzle-orm.src.durable-sqlite.migrator.
Position
Below the diagonal: drizzle-orm.src.mysql-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.dialect uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.mysql-core.dialect, while a change to drizzle-orm.src.mysql-core.dialect can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.mysql-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.dialect uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.mysql-core.dialect, while a change to drizzle-orm.src.mysql-core.dialect can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.mysql-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.dialect uses drizzle-orm.src.mysql-core.table, so a change to drizzle-orm.src.mysql-core.table can break drizzle-orm.src.mysql-core.dialect, while a change to drizzle-orm.src.mysql-core.dialect can't break drizzle-orm.src.mysql-core.table.
Position
Below the diagonal: drizzle-orm.src.mysql-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.dialect uses drizzle-orm.src.relations, so a change to drizzle-orm.src.relations can break drizzle-orm.src.mysql-core.dialect, while a change to drizzle-orm.src.mysql-core.dialect can't break drizzle-orm.src.relations.
Position
Below the diagonal: drizzle-orm.src.mysql-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.dialect uses drizzle-orm.src.utils, so a change to drizzle-orm.src.utils can break drizzle-orm.src.mysql-core.dialect, while a change to drizzle-orm.src.mysql-core.dialect can't break drizzle-orm.src.utils.
Position
Below the diagonal: drizzle-orm.src.mysql-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.dialect uses drizzle-orm.src.mysql-core.columns.common, so a change to drizzle-orm.src.mysql-core.columns.common can break drizzle-orm.src.mysql-core.dialect, while a change to drizzle-orm.src.mysql-core.dialect can't break drizzle-orm.src.mysql-core.columns.common.
Position
Below the diagonal: drizzle-orm.src.mysql-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.dialect uses drizzle-orm.src.mysql-core.session, so a change to drizzle-orm.src.mysql-core.session can break drizzle-orm.src.mysql-core.dialect, while a change to drizzle-orm.src.mysql-core.dialect can't break drizzle-orm.src.mysql-core.session.
Position
Below the diagonal: drizzle-orm.src.mysql-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.dialect uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.pg-core.dialect, while a change to drizzle-orm.src.pg-core.dialect can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.pg-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.dialect uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.pg-core.dialect, while a change to drizzle-orm.src.pg-core.dialect can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.pg-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.dialect uses drizzle-orm.src.pg-core.table, so a change to drizzle-orm.src.pg-core.table can break drizzle-orm.src.pg-core.dialect, while a change to drizzle-orm.src.pg-core.dialect can't break drizzle-orm.src.pg-core.table.
Position
Below the diagonal: drizzle-orm.src.pg-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.dialect uses drizzle-orm.src.relations, so a change to drizzle-orm.src.relations can break drizzle-orm.src.pg-core.dialect, while a change to drizzle-orm.src.pg-core.dialect can't break drizzle-orm.src.relations.
Position
Below the diagonal: drizzle-orm.src.pg-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.dialect uses drizzle-orm.src.utils, so a change to drizzle-orm.src.utils can break drizzle-orm.src.pg-core.dialect, while a change to drizzle-orm.src.pg-core.dialect can't break drizzle-orm.src.utils.
Position
Below the diagonal: drizzle-orm.src.pg-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.dialect uses drizzle-orm.src.pg-core.columns.common, so a change to drizzle-orm.src.pg-core.columns.common can break drizzle-orm.src.pg-core.dialect, while a change to drizzle-orm.src.pg-core.dialect can't break drizzle-orm.src.pg-core.columns.common.
Position
Below the diagonal: drizzle-orm.src.pg-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.dialect uses drizzle-orm.src.pg-core.session, so a change to drizzle-orm.src.pg-core.session can break drizzle-orm.src.pg-core.dialect, while a change to drizzle-orm.src.pg-core.dialect can't break drizzle-orm.src.pg-core.session.
Position
Below the diagonal: drizzle-orm.src.pg-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.dialect uses drizzle-orm.src.durable-sqlite.migrator, so a change to drizzle-orm.src.durable-sqlite.migrator can break drizzle-orm.src.singlestore-core.dialect, while a change to drizzle-orm.src.singlestore-core.dialect can't break drizzle-orm.src.durable-sqlite.migrator.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.dialect uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.singlestore-core.dialect, while a change to drizzle-orm.src.singlestore-core.dialect can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.dialect uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.singlestore-core.dialect, while a change to drizzle-orm.src.singlestore-core.dialect can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.dialect uses drizzle-orm.src.relations, so a change to drizzle-orm.src.relations can break drizzle-orm.src.singlestore-core.dialect, while a change to drizzle-orm.src.singlestore-core.dialect can't break drizzle-orm.src.relations.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.dialect uses drizzle-orm.src.singlestore-core.columns.common, so a change to drizzle-orm.src.singlestore-core.columns.common can break drizzle-orm.src.singlestore-core.dialect, while a change to drizzle-orm.src.singlestore-core.dialect can't break drizzle-orm.src.singlestore-core.columns.common.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.dialect uses drizzle-orm.src.utils, so a change to drizzle-orm.src.utils can break drizzle-orm.src.singlestore-core.dialect, while a change to drizzle-orm.src.singlestore-core.dialect can't break drizzle-orm.src.utils.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.singlestore-core.dialect uses drizzle-orm.src.singlestore-core.session, so a change to drizzle-orm.src.singlestore-core.session can break drizzle-orm.src.singlestore-core.dialect, while a change to drizzle-orm.src.singlestore-core.dialect can't break drizzle-orm.src.singlestore-core.session.
Position
Below the diagonal: drizzle-orm.src.singlestore-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.dialect uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.sqlite-core.dialect, while a change to drizzle-orm.src.sqlite-core.dialect can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.dialect uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.sqlite-core.dialect, while a change to drizzle-orm.src.sqlite-core.dialect can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.dialect uses drizzle-orm.src.relations, so a change to drizzle-orm.src.relations can break drizzle-orm.src.sqlite-core.dialect, while a change to drizzle-orm.src.sqlite-core.dialect can't break drizzle-orm.src.relations.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.dialect uses drizzle-orm.src.sqlite-core.session, so a change to drizzle-orm.src.sqlite-core.session can break drizzle-orm.src.sqlite-core.dialect, while a change to drizzle-orm.src.sqlite-core.dialect can't break drizzle-orm.src.sqlite-core.session.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.dialect uses drizzle-orm.src.sqlite-core.table, so a change to drizzle-orm.src.sqlite-core.table can break drizzle-orm.src.sqlite-core.dialect, while a change to drizzle-orm.src.sqlite-core.dialect can't break drizzle-orm.src.sqlite-core.table.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.dialect uses drizzle-orm.src.utils, so a change to drizzle-orm.src.utils can break drizzle-orm.src.sqlite-core.dialect, while a change to drizzle-orm.src.sqlite-core.dialect can't break drizzle-orm.src.utils.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.sqlite-core.dialect uses drizzle-orm.src.sqlite-core.columns.common, so a change to drizzle-orm.src.sqlite-core.columns.common can break drizzle-orm.src.sqlite-core.dialect, while a change to drizzle-orm.src.sqlite-core.dialect can't break drizzle-orm.src.sqlite-core.columns.common.
Position
Below the diagonal: drizzle-orm.src.sqlite-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.gel-core, while a change to drizzle-orm.src.gel-core can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.gel-core uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core uses drizzle-orm.src.gel-core.indexes, so a change to drizzle-orm.src.gel-core.indexes can break drizzle-orm.src.gel-core, while a change to drizzle-orm.src.gel-core can't break drizzle-orm.src.gel-core.indexes.
Position
Below the diagonal: drizzle-orm.src.gel-core uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core uses drizzle-orm.src.gel-core.columns.common, so a change to drizzle-orm.src.gel-core.columns.common can break drizzle-orm.src.gel-core, while a change to drizzle-orm.src.gel-core can't break drizzle-orm.src.gel-core.columns.common.
Position
Below the diagonal: drizzle-orm.src.gel-core uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core uses drizzle-orm.src.gel-core.table, so a change to drizzle-orm.src.gel-core.table can break drizzle-orm.src.gel-core, while a change to drizzle-orm.src.gel-core can't break drizzle-orm.src.gel-core.table.
Position
Below the diagonal: drizzle-orm.src.gel-core uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.dialect uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.gel-core.dialect, while a change to drizzle-orm.src.gel-core.dialect can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.gel-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.dialect uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.gel-core.dialect, while a change to drizzle-orm.src.gel-core.dialect can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.gel-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.dialect uses drizzle-orm.src.relations, so a change to drizzle-orm.src.relations can break drizzle-orm.src.gel-core.dialect, while a change to drizzle-orm.src.gel-core.dialect can't break drizzle-orm.src.relations.
Position
Below the diagonal: drizzle-orm.src.gel-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.dialect uses drizzle-orm.src.utils, so a change to drizzle-orm.src.utils can break drizzle-orm.src.gel-core.dialect, while a change to drizzle-orm.src.gel-core.dialect can't break drizzle-orm.src.utils.
Position
Below the diagonal: drizzle-orm.src.gel-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.dialect uses drizzle-orm.src.gel-core.columns.common, so a change to drizzle-orm.src.gel-core.columns.common can break drizzle-orm.src.gel-core.dialect, while a change to drizzle-orm.src.gel-core.dialect can't break drizzle-orm.src.gel-core.columns.common.
Position
Below the diagonal: drizzle-orm.src.gel-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.dialect uses drizzle-orm.src.gel-core.table, so a change to drizzle-orm.src.gel-core.table can break drizzle-orm.src.gel-core.dialect, while a change to drizzle-orm.src.gel-core.dialect can't break drizzle-orm.src.gel-core.table.
Position
Below the diagonal: drizzle-orm.src.gel-core.dialect uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.db uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.mysql-core.db, while a change to drizzle-orm.src.mysql-core.db can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.mysql-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.db uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.mysql-core.db, while a change to drizzle-orm.src.mysql-core.db can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.mysql-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.db uses drizzle-orm.src.mysql-core.session, so a change to drizzle-orm.src.mysql-core.session can break drizzle-orm.src.mysql-core.db, while a change to drizzle-orm.src.mysql-core.db can't break drizzle-orm.src.mysql-core.session.
Position
Below the diagonal: drizzle-orm.src.mysql-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.mysql-core.db uses drizzle-orm.src.mysql-core.dialect, so a change to drizzle-orm.src.mysql-core.dialect can break drizzle-orm.src.mysql-core.db, while a change to drizzle-orm.src.mysql-core.db can't break drizzle-orm.src.mysql-core.dialect.
Position
Below the diagonal: drizzle-orm.src.mysql-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.db uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.pg-core.db, while a change to drizzle-orm.src.pg-core.db can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.pg-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.db uses drizzle-orm.src.utils, so a change to drizzle-orm.src.utils can break drizzle-orm.src.pg-core.db, while a change to drizzle-orm.src.pg-core.db can't break drizzle-orm.src.utils.
Position
Below the diagonal: drizzle-orm.src.pg-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.db uses drizzle-orm.src.pg-core.session, so a change to drizzle-orm.src.pg-core.session can break drizzle-orm.src.pg-core.db, while a change to drizzle-orm.src.pg-core.db can't break drizzle-orm.src.pg-core.session.
Position
Below the diagonal: drizzle-orm.src.pg-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.pg-core.db uses drizzle-orm.src.pg-core.dialect, so a change to drizzle-orm.src.pg-core.dialect can break drizzle-orm.src.pg-core.db, while a change to drizzle-orm.src.pg-core.db can't break drizzle-orm.src.pg-core.dialect.
Position
Below the diagonal: drizzle-orm.src.pg-core.db uses a module listed above it, which is the healthy direction.
drizzle-kit.src uses drizzle-orm.src.table, so a change to drizzle-orm.src.table can break drizzle-kit.src, while a change to drizzle-kit.src can't break drizzle-orm.src.table.
Position
Below the diagonal: drizzle-kit.src uses a module listed above it, which is the healthy direction.
drizzle-kit.src uses drizzle-orm.src.relations, so a change to drizzle-orm.src.relations can break drizzle-kit.src, while a change to drizzle-kit.src can't break drizzle-orm.src.relations.
Position
Below the diagonal: drizzle-kit.src uses a module listed above it, which is the healthy direction.
drizzle-kit.src uses drizzle-orm.src.utils, so a change to drizzle-orm.src.utils can break drizzle-kit.src, while a change to drizzle-kit.src can't break drizzle-orm.src.utils.
Position
Below the diagonal: drizzle-kit.src uses a module listed above it, which is the healthy direction.
drizzle-kit.src uses drizzle-orm.src.pg-core.db, so a change to drizzle-orm.src.pg-core.db can break drizzle-kit.src, while a change to drizzle-kit.src can't break drizzle-orm.src.pg-core.db.
Position
Below the diagonal: drizzle-kit.src uses a module listed above it, which is the healthy direction.
drizzle-orm.src.aws-data-api.pg.driver uses drizzle-orm.src.cache.core.cache, so a change to drizzle-orm.src.cache.core.cache can break drizzle-orm.src.aws-data-api.pg.driver, while a change to drizzle-orm.src.aws-data-api.pg.driver can't break drizzle-orm.src.cache.core.cache.
Position
Below the diagonal: drizzle-orm.src.aws-data-api.pg.driver uses a module listed above it, which is the healthy direction.
drizzle-orm.src.aws-data-api.pg.driver uses drizzle-orm.src.logger, so a change to drizzle-orm.src.logger can break drizzle-orm.src.aws-data-api.pg.driver, while a change to drizzle-orm.src.aws-data-api.pg.driver can't break drizzle-orm.src.logger.
Position
Below the diagonal: drizzle-orm.src.aws-data-api.pg.driver uses a module listed above it, which is the healthy direction.
drizzle-orm.src.aws-data-api.pg.driver uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.aws-data-api.pg.driver, while a change to drizzle-orm.src.aws-data-api.pg.driver can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.aws-data-api.pg.driver uses a module listed above it, which is the healthy direction.
drizzle-orm.src.aws-data-api.pg.driver uses drizzle-orm.src.pg-core.table, so a change to drizzle-orm.src.pg-core.table can break drizzle-orm.src.aws-data-api.pg.driver, while a change to drizzle-orm.src.aws-data-api.pg.driver can't break drizzle-orm.src.pg-core.table.
Position
Below the diagonal: drizzle-orm.src.aws-data-api.pg.driver uses a module listed above it, which is the healthy direction.
drizzle-orm.src.aws-data-api.pg.driver uses drizzle-orm.src.gel-core.table, so a change to drizzle-orm.src.gel-core.table can break drizzle-orm.src.aws-data-api.pg.driver, while a change to drizzle-orm.src.aws-data-api.pg.driver can't break drizzle-orm.src.gel-core.table.
Position
Below the diagonal: drizzle-orm.src.aws-data-api.pg.driver uses a module listed above it, which is the healthy direction.
drizzle-orm.src.aws-data-api.pg.driver uses drizzle-orm.src.pg-core.dialect, so a change to drizzle-orm.src.pg-core.dialect can break drizzle-orm.src.aws-data-api.pg.driver, while a change to drizzle-orm.src.aws-data-api.pg.driver can't break drizzle-orm.src.pg-core.dialect.
Position
Below the diagonal: drizzle-orm.src.aws-data-api.pg.driver uses a module listed above it, which is the healthy direction.
drizzle-orm.src.aws-data-api.pg.driver uses drizzle-orm.src.pg-core.db, so a change to drizzle-orm.src.pg-core.db can break drizzle-orm.src.aws-data-api.pg.driver, while a change to drizzle-orm.src.aws-data-api.pg.driver can't break drizzle-orm.src.pg-core.db.
Position
Below the diagonal: drizzle-orm.src.aws-data-api.pg.driver uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.db uses drizzle-orm.src.sql.sql, so a change to drizzle-orm.src.sql.sql can break drizzle-orm.src.gel-core.db, while a change to drizzle-orm.src.gel-core.db can't break drizzle-orm.src.sql.sql.
Position
Below the diagonal: drizzle-orm.src.gel-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.db uses drizzle-orm.src.gel-core.query-builders.select_types, so a change to drizzle-orm.src.gel-core.query-builders.select_types can break drizzle-orm.src.gel-core.db, while a change to drizzle-orm.src.gel-core.db can't break drizzle-orm.src.gel-core.query-builders.select_types.
Position
Below the diagonal: drizzle-orm.src.gel-core.db uses a module listed above it, which is the healthy direction.
drizzle-orm.src.gel-core.db uses drizzle-orm.src.gel-core.dialect, so a change to drizzle-orm.src.gel-core.dialect can break drizzle-orm.src.gel-core.db, while a change to drizzle-orm.src.gel-core.db can't break drizzle-orm.src.gel-core.dialect.
Position
Below the diagonal: drizzle-orm.src.gel-core.db uses a module listed above it, which is the healthy direction.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
95
High / Critical
A05:2025 — Injection
44
High / Critical
A07:2025 — Authentication Failures
2
High / Critical
Roadmap
Immediately secure sensitive data by implementing encryption at rest and managing keys in a dedicated vault. Concurrently, resolve all high-severity dependency vulnerabilities and address deprecated packages to stabilize the codebase. Finally, remove unused dependencies to reduce risk and document key architectural decisions to ensure long-term maintainability.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.).
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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 — 112
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 — 596
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 — 252
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog 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. 73 of 73 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); none rely on LLM judgement. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three 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; ◐ Advisory — an LLM prose judgement. 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; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 73 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 914 of 960 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D19 Documentation Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D21 Naming Consistency — not measured this run — Watchdog 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. 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.
D22 Internal API Consistency — not measured this run — Watchdog 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 (eslint-plugin-drizzle/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.
D24 Comment Value — not measured this run — Watchdog 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog 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. `drizzle-arktype/benchmarks/types.ts`, `drizzle-arktype/src/column.ts`, `drizzle-arktype/src/column.types.ts`, `drizzle-arktype/src/schema.ts`, `drizzle-arktype/src/schema.types.internal.ts`, … (+26 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.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
P8 Schema migrations — not measured this run — Watchdog 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. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 342 further occurrence(s) are not listed individually; the score already reflects all 382.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. 57 further occurrence(s) are not listed individually; the score already reflects all 97.
S1 Web-Security Posture — not measured this run — Watchdog 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. 521 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation and obsolete TLS versions, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
X2 Cancellation propagation — not measured this run — Watchdog 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, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, 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.
X4 Structured logging — not measured this run — Watchdog 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 make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 16 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
Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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.
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 — Watchdog runs the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
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.
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.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
61 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SeedService.selectGeneratorForPostgresColumn::pickGenerator at 60. A further 3 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 NeonPreparedQuery.constructor at 19 — they are counted neither in the figure above nor in this dimension's score. 3 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: drizzle-orm/src/neon-serverless/session.ts (NeonPreparedQuery.constructor at 19), drizzle-orm/src/node-postgres/session.ts (NodePgPreparedQuery.constructor at 19), drizzle-orm/src/vercel-postgres/session.ts (VercelPgPreparedQuery.constructor at 19). 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.
+ 50 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 61 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with SeedService.selectGeneratorForPostgresColumn::pickGenerator (cyclomatic 60), SeedService.generatePossibleGenerators (cyclomatic 57), SeedService.selectGeneratorForMysqlColumn::pickGenerator (cyclomatic 57). — 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 61 together lifts Cyclomatic Complexity from 6.5 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
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.
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.
+ 70 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 8 bodies over 60 down to 60 or less in Cognitive Complexity — start with SeedService.generatePossibleGenerators (cognitive 114), MySqlDialect.buildRelationalQueryWithoutLateralSubqueries (cognitive 78), GelDialect.buildRelationalQueryWithoutPK (cognitive 75). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 8 together lifts Cognitive Complexity from 5.4 to about 6.2/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
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.
Do you agree with this assessment?
D3 · God Classes9.7 / 10Stronggated by 17 serious findings✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 11 FileTooLong finding(s) in God Classes — start with dialect.ts (5), select.ts (2), Generators.ts. — One of this dimension's main actionable groups (11 warning-level).
Resolve the 5 MethodTooLong finding(s) in God Classes — start with SeedService.ts (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 ClassTooLong finding(s) in God Classes — start with SeedService.ts. — One of this dimension's main actionable groups (1 warning-level).
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.
Do you agree with this assessment?
D5 · Coupling8.9 / 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.
7 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
Off the main sequence: drizzle-orm
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
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.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with dialect.ts. — One of this dimension's main actionable groups (1 warning-level).
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.
Do you agree with this assessment?
D9 · Test Distribution10.0 / 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.
4112 test methods: 1388 unit, 2724 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 4112 `it`/`test` case(s) across 188 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.
Do you agree with this assessment?
D10 · Test Quality9.7 / 10Adequategated by 2 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.
37 skipped (18 with a documented reason), 58 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4112 tests.
Assertions commented out: Simple case from GHintegration-tests/tests/relational/issues-schemas/wrong-mapping/pg.test.ts:191
No assertions (empty test): add table #5drizzle-kit/tests/sqlite-tables.test.ts:133
No assertions: all date and time columns · ×56integration-tests/tests/gel/gel.test.ts:2497
Mock-dominated test: default global config - no cache should be hit · ×76integration-tests/tests/sqlite/sqlite-common-cache.ts:142
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with pg.test.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with sqlite-tables.test.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 56 No assertions finding(s) in Test Quality — start with common.ts (20), better-sqlite3.test.mjs (3), pglite.test.mjs (3). — One of this dimension's main actionable groups (56 warning-level).
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.
Do you agree with this assessment?
D11 · Test Reliability10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
30 outdated direct production npm dependency(ies) of 38 graded, 0 pinning defect(s), across 10 REDACTED (10 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 8 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
Resolve the 21 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (21). — One of this dimension's main actionable groups (21 recommendation-level).
Resolve the 18 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (18). — One of this dimension's main actionable groups (18 warning-level).
Resolve the 2 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 38 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 38 production dependency(ies) this repository's committed lockfile resolves, across 10 product REDACTED manifest(s). Its 235 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under Apache-2.0 / MIT, which is its own choice and is not judged here.
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.
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.
2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is drizzle-seed/src/services/SeedService.ts. Counted over 274 of the 618 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
96 deducted task-comment markers across 215484 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 96 TodoComment finding(s) in Explicit Debt — start with gel.test.ts (15), select.ts (9), SeedService.ts (8). — One of this dimension's main actionable groups (96 warning-level).
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.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
What it measures: Whether 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.
36 domain type(s) cross context boundaries across 8 contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) · ×21drizzle-kit/src/cli/commands/utils.ts:103
Cross-context type Casing (drizzle-orm → drizzle-kit) · ×14drizzle-kit/src/cli/commands/utils.ts:462
Cross-context type D1Response (drizzle-kit → drizzle-orm)drizzle-orm/src/d1/session.ts:199
What to do
Resolve the 21 Cross-context type Dialect (drizzle-orm → drizzle-kit) finding(s) in Boundary Type-Coupling — start with sqlgenerator.ts (12), utils.ts (8), check.ts. — One of this dimension's main actionable groups (21 warning-level).
Resolve the 14 Cross-context type Casing (drizzle-orm → drizzle-kit) finding(s) in Boundary Type-Coupling — start with introspect.ts (7), utils.ts, introspect-sqlite.ts. — One of this dimension's main actionable groups (14 warning-level).
Resolve the 1 Cross-context type D1Response (drizzle-kit → drizzle-orm) finding(s) in Boundary Type-Coupling — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d23_recommendation.md · top locations in Appendix A, every location in findings.md.
1 of 8 build units (npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
44 finding(s): 0 critical, 42 high, 2 medium, 0 low. 32 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 91 file(s) — `drizzle-arktype/benchmarks/types.ts` (line 2), `drizzle-arktype/src/column.ts` (line 1), `drizzle-arktype/src/column.types.ts` (line 1), `drizzle-arktype/src/schema.ts` (line 1), `drizzle-arktype/src/schema.types.internal.ts` (line 1, lines 51–60), … (+86 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 4 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
No action in Static Analysis (SAST) — all 32 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 (32 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 52 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (50), REDACTED (2). — One of this dimension's main actionable groups (52 issue-level).
Resolve the 8 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (8). — One of this dimension's main actionable groups (8 issue-level).
Resolve the 2 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
33 of 274 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is drizzle-seed/src/services/SeedService.ts. Counted over 274 of the 618 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 2 Orphaned knowledge finding(s) in Knowledge Freshness — start with SeedService.ts, GeneratorFuncs.ts. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 31 Orphaned file finding(s) in Knowledge Freshness — start with column.ts (4), schema.ts (4), fix-imports.ts (4). — One of this dimension's main actionable groups (31 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 9 Change coupling finding(s) in Change Coupling — start with delete.ts (3), tables.ts (2), driver.ts (2). — One of this dimension's main actionable groups (9 warning-level).
Resolve the 5 Change-coupling hub finding(s) in Change Coupling — start with driver.ts (5). — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 Change coupling clique finding(s) in Change Coupling — start with dialect.ts. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 4 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
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. Scored 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. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 1 platform declaration(s) and 0 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
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.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').
Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.
`DialectSuite` declares 17 required operations: `allTypes`, `addBasicIndexes`, `changeIndexFields`, `dropIndex`, `indexesToBeNotTriggered`, `indexesTestCase1`, `addNotNull`, `addNotNullWithDataNoRollback`, `addBasicSequences`, `addGeneratedColumn`, `addGeneratedToColumn`, `dropGeneratedConstraint`, `alterGeneratedConstraint`, `createTableWithGeneratedConstraint`, `createCompositePrimaryKey`, `renameTableWithCompositePrimaryKey`, `case1`. 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. — drizzle-kit/tests/push/common.ts:3
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Do you agree with this assessment?
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.
Do you agree with this assessment?
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. — drizzle-orm/src/prisma/schema.prisma:12
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.
Other · Code Health — Unreviewed-generation residue in this repository's JavaScript/TypeScript: functions whose whole body still throws a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings and JSX of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface. (×9) — REDACTED:61, REDACTED:71, REDACTED:68, …
A placeholder string ("You can't use lorem ipsum generator with…") is still in shipped code — typical of generated boilerplate that was never filled in. — drizzle-seed/src/services/Generators.ts:2788
What to do
Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's JavaScript/TypeScript: functions that only throw a "not implemented" error, functions that take inputs and return a constant or do nothing, async functions that never await, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`migrate` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — drizzle-orm/src/durable-sqlite/migrator.ts:41
`PrismaMySqlSession` has 2 unfinished members out of 4 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented. — REDACTED:43
`all` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — REDACTED:61
`transaction` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. (×3) — REDACTED:71, REDACTED:68, REDACTED:84
`generatedAlwaysAs` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. (×3) — drizzle-orm/src/singlestore-core/columns/datetime.ts:30, drizzle-orm/src/singlestore-core/columns/datetime.ts:93, drizzle-orm/src/singlestore-core/columns/vector.ts:40
`mapAllResult` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — drizzle-orm/src/sqlite-core/session.ts:169
`mapGetResult` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — drizzle-orm/src/sqlite-core/session.ts:175
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. — drizzle-seed/src/index.ts:209
`initMappers` has an empty body — confirm it's an intentional no-op and not an unfinished method. — drizzle-orm/src/xata-http/driver.ts:38
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. — eslint/eslint-plugin-drizzle-internal/index.js:1
A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×19) — integration-tests/tests/bun/bun-sql.test.ts:1963, integration-tests/tests/bun/bun-sql.test.ts:2477, integration-tests/tests/bun/bun-sql.test.ts:2977, …
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
Maturity · Maturity — Whether the 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
Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 3 of 10 project(s) that lack one — worth up to 0.6 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Do you agree with this assessment?
P2 · Observability2.0 / 10Critical✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
No logging call was found in the 598 JavaScript/TypeScript production file(s) this check read across 10 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
Adopt pino (or winston) and log at meaningful points in the services you run.
Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
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 the language 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.
Do you agree with this assessment?
R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
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.
266 duplicated blocks under drizzle-orm/src/ have copies in at least two of the sibling directories aws-data-api, better-sqlite3, bun-sql, bun-sqlite, d1, durable-sqlite (+27 more sibling(s) not listed) — 222 of them are reported below, and 44 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 266 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 266 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 266 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. — drizzle-orm/src/gel-core/query-builders/select.ts:60
32 duplicated blocks under the repository root have copies in at least two of the sibling directories drizzle-arktype, drizzle-orm, drizzle-seed, drizzle-typebox, drizzle-valibot, drizzle-zod — 24 of them are reported below, and 8 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 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. — drizzle-typebox/src/column.ts:143
drizzle-orm/src/gel-core/query-builders/select.ts:60 · drizzle-orm/src/pg-core/query-builders/select.ts:62 — the two spans are one implementation copied and then locally edited — 3406 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. — drizzle-orm/src/gel-core/query-builders/select.ts:60
drizzle-orm/src/gel-core/dialect.ts:1 · drizzle-orm/src/pg-core/dialect.ts:1 — these 2 files are line-for-line copies of one another — 466 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. — drizzle-orm/src/gel-core/dialect.ts:1
drizzle-orm/src/mysql-core/query-builders/select.ts:70 · drizzle-orm/src/singlestore-core/query-builders/select.ts:69 — the two spans are one implementation copied and then locally edited — 2910 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. — drizzle-orm/src/mysql-core/query-builders/select.ts:70
drizzle-orm/src/singlestore-core/query-builders/select.ts:179 · drizzle-orm/src/sqlite-core/query-builders/select.ts:178 — the two spans are one implementation copied and then locally edited — 2502 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. — drizzle-orm/src/singlestore-core/query-builders/select.ts:179
drizzle-orm/src/mysql-core/dialect.ts:80 · drizzle-orm/src/singlestore-core/dialect.ts:79 — the two spans are one implementation copied and then locally edited — 1874 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. — drizzle-orm/src/mysql-core/dialect.ts:80
drizzle-orm/src/neon-serverless/session.ts:40 · drizzle-orm/src/vercel-postgres/session.ts:39 — the two spans are one implementation copied and then locally edited — 1387 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. — drizzle-orm/src/neon-serverless/session.ts:40
drizzle-orm/src/gel-core/query-builders/select.types.ts:131 · drizzle-orm/src/pg-core/query-builders/select.types.ts:143 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — drizzle-orm/src/gel-core/query-builders/select.types.ts:131
drizzle-orm/src/mysql-core/db.ts:34 · drizzle-orm/src/singlestore-core/db.ts:31 — the two spans are one implementation copied and then locally edited — 1374 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. — drizzle-orm/src/mysql-core/db.ts:34
drizzle-orm/src/bun-sql/session.ts:32 · drizzle-orm/src/postgres-js/session.ts:31 — the two spans are one implementation copied and then locally edited — 1158 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. — drizzle-orm/src/bun-sql/session.ts:32
drizzle-orm/src/mysql-core/db.ts:40 · drizzle-orm/src/sqlite-core/db.ts:38 — the two spans are one implementation copied and then locally edited — 1125 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. — drizzle-orm/src/mysql-core/db.ts:40
drizzle-orm/src/pg-core/query-builders/delete.ts:30 · drizzle-orm/src/pg-core/query-builders/insert.ts:137 — the two spans are one implementation copied and then locally edited — 875 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. — drizzle-orm/src/pg-core/query-builders/delete.ts:30
drizzle-orm/src/gel-core/db.ts:27 · drizzle-orm/src/pg-core/db.ts:36 — the two spans are one implementation copied and then locally edited — 1065 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. — drizzle-orm/src/gel-core/db.ts:27
drizzle-orm/src/d1/session.ts:23 · drizzle-orm/src/libsql/session.ts:22 — the two spans are one implementation copied and then locally edited — 1042 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. — drizzle-orm/src/d1/session.ts:23
drizzle-orm/src/mysql-core/query-builders/delete.ts:23 · drizzle-orm/src/singlestore-core/query-builders/delete.ts:23 — 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. — drizzle-orm/src/mysql-core/query-builders/delete.ts:23
drizzle-seed/src/services/Generators.ts:1316 · drizzle-seed/src/services/versioning/v2.ts:5 — the two spans are one implementation copied and then locally edited — 932 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. — drizzle-seed/src/services/Generators.ts:1316
drizzle-orm/src/gel-core/table.ts:13 · drizzle-orm/src/pg-core/table.ts:13 — the two spans are one implementation copied and then locally edited — 866 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. — drizzle-orm/src/gel-core/table.ts:13
drizzle-seed/src/index.ts:758 · drizzle-seed/src/index.ts:1120 — the two spans are one implementation copied and then locally edited — 761 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. — drizzle-seed/src/index.ts:758
drizzle-orm/src/gel-core/columns/common.ts:135 · drizzle-orm/src/pg-core/columns/common.ts:136 — 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. — drizzle-orm/src/gel-core/columns/common.ts:135
drizzle-orm/src/mysql-core/query-builders/select.types.ts:235 · drizzle-orm/src/singlestore-core/query-builders/select.types.ts:220 — 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. — drizzle-orm/src/mysql-core/query-builders/select.types.ts:235
drizzle-orm/src/mysql2/driver.ts:43 · drizzle-orm/src/singlestore/driver.ts:44 — the two spans are one implementation copied and then locally edited — 749 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. — drizzle-orm/src/mysql2/driver.ts:43
drizzle-typebox/src/column.ts:143 · drizzle-valibot/src/column.ts:128 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — drizzle-typebox/src/column.ts:143
drizzle-orm/src/planetscale-serverless/session.ts:35 · drizzle-orm/src/tidb-serverless/session.ts:36 — the two spans are one implementation copied and then locally edited — 717 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. — drizzle-orm/src/planetscale-serverless/session.ts:35
drizzle-orm/src/gel-core/view.ts:290 · drizzle-orm/src/pg-core/view.ts:290 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — drizzle-orm/src/gel-core/view.ts:290
drizzle-typebox/src/schema.ts:29 · drizzle-zod/src/schema.ts:30 — the two spans are one implementation copied and then locally edited — 778 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. — drizzle-typebox/src/schema.ts:29
drizzle-arktype/src/column.ts:128 · drizzle-typebox/src/column.ts:143 · drizzle-valibot/src/column.ts:128 · drizzle-zod/src/column.ts:143 — the 4 copies are spread across 4 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. — drizzle-arktype/src/column.ts:128
drizzle-orm/src/mysql2/session.ts:223 · drizzle-orm/src/singlestore/session.ts:219 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — drizzle-orm/src/mysql2/session.ts:223
drizzle-orm/src/mysql-core/dialect.ts:852 · drizzle-orm/src/singlestore-core/dialect.ts:802 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — drizzle-orm/src/mysql-core/dialect.ts:852
drizzle-orm/src/mysql-core/table.ts:43 · drizzle-orm/src/singlestore-core/table.ts:31 — 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. — drizzle-orm/src/mysql-core/table.ts:43
drizzle-orm/src/durable-sqlite/session.ts:31 · drizzle-orm/src/expo-sqlite/session.ts:29 — the two spans are one implementation copied and then locally edited — 704 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. — drizzle-orm/src/durable-sqlite/session.ts:31
drizzle-arktype/scripts/fix-imports.ts:2 · drizzle-typebox/scripts/fix-imports.ts:2 · drizzle-valibot/scripts/fix-imports.ts:2 · drizzle-zod/scripts/fix-imports.ts:2 — these 4 files are line-for-line copies of one another — 90 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. — drizzle-arktype/scripts/fix-imports.ts:2
drizzle-orm/src/sqlite-core/query-builders/delete.ts:59 · drizzle-orm/src/sqlite-core/query-builders/update.ts:125 — the two spans are one implementation copied and then locally edited — 535 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. — drizzle-orm/src/sqlite-core/query-builders/delete.ts:59
drizzle-orm/src/mysql-core/query-builders/query.ts:37 · drizzle-orm/src/singlestore-core/query-builders/query.ts:35 — the two spans are one implementation copied and then locally edited — 596 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. — drizzle-orm/src/mysql-core/query-builders/query.ts:37
drizzle-orm/src/gel-core/columns/custom.ts:37 · drizzle-orm/src/mysql-core/columns/custom.ts:37 · drizzle-orm/src/pg-core/columns/custom.ts:37 · drizzle-orm/src/singlestore-core/columns/custom.ts:38 — the 4 copies are spread across 4 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. — drizzle-orm/src/gel-core/columns/custom.ts:37
drizzle-orm/src/pg-core/columns/line.ts:13 · drizzle-orm/src/pg-core/columns/point.ts:13 — the two spans are one implementation copied and then locally edited — 705 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. — drizzle-orm/src/pg-core/columns/line.ts:13
drizzle-orm/src/gel-core/query-builders/update.ts:348 · drizzle-orm/src/pg-core/query-builders/update.ts:388 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — drizzle-orm/src/gel-core/query-builders/update.ts:348
drizzle-orm/src/gel-core/session.ts:42 · drizzle-orm/src/sqlite-core/session.ts:71 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — drizzle-orm/src/gel-core/session.ts:42
drizzle-orm/src/gel-core/session.ts:42 · drizzle-orm/src/mysql-core/session.ts:70 · drizzle-orm/src/singlestore-core/session.ts:68 · drizzle-orm/src/sqlite-core/session.ts:71 — the 4 copies are spread across 4 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 4 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. — drizzle-orm/src/gel-core/session.ts:42
drizzle-orm/src/mysql-core/session.ts:70 · drizzle-orm/src/singlestore-core/session.ts:68 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — drizzle-orm/src/mysql-core/session.ts:70
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · 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.
pickGenerator has cyclomatic complexity 60 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — drizzle-seed/src/services/SeedService.ts:507
pickGenerator has cyclomatic complexity 57 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — drizzle-seed/src/services/SeedService.ts:801
(top-level) has cyclomatic complexity 55 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — drizzle-orm/src/query-builders/select.types.ts:1
generatePossibleGenerators has cyclomatic complexity 52 and cognitive complexity 112; 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. — drizzle-seed/src/services/SeedService.ts:34
(top-level) has cyclomatic complexity 44 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — drizzle-valibot/src/column.types.ts:1
buildRelationalQuery has cyclomatic complexity 37 and cognitive complexity 84; 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) — drizzle-orm/src/mysql-core/dialect.ts:658, drizzle-orm/src/singlestore-core/dialect.ts:605
pickGenerator has cyclomatic complexity 37 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — drizzle-seed/src/services/SeedService.ts:997
buildRelationalQueryWithoutLateralSubqueries has cyclomatic complexity 36 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — drizzle-orm/src/mysql-core/dialect.ts:1000
buildRelationalQueryWithoutPK has cyclomatic complexity 35 and cognitive complexity 82; 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) — drizzle-orm/src/gel-core/dialect.ts:1141, drizzle-orm/src/pg-core/dialect.ts:1150
(anonymous) has cyclomatic complexity 35 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — drizzle-orm/src/sql/sql.ts:163
(top-level) has cyclomatic complexity 35 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — drizzle-zod/src/column.types.ts:1
buildRelationalQuery has cyclomatic complexity 34 and cognitive complexity 79; 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. — drizzle-orm/src/sqlite-core/dialect.ts:606
generateTablesValues has cyclomatic complexity 34 and cognitive complexity 66; 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. — drizzle-seed/src/services/SeedService.ts:1142
buildSelectQuery has cyclomatic complexity 34 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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. — drizzle-orm/src/mysql-core/dialect.ts:312
buildSelectQuery has cyclomatic complexity 33 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — drizzle-orm/src/singlestore-core/dialect.ts:299
buildSelectQuery has cyclomatic complexity 28 and cognitive complexity 39; 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) — drizzle-orm/src/gel-core/dialect.ts:336, drizzle-orm/src/pg-core/dialect.ts:341
columnToSchema has cyclomatic complexity 28 and cognitive complexity 37; 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. — drizzle-zod/src/column.ts:70
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files6.9 / 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.
drizzle-seed/src/services/Generators.ts has 2548 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-seed/src/services/Generators.ts:1
drizzle-seed/src/services/SeedService.ts has 1405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-seed/src/services/SeedService.ts:1
drizzle-orm/type-tests/pg/tables.ts has 1371 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/pg/tables.ts:1
drizzle-seed/src/index.ts has 1335 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-seed/src/index.ts:1
drizzle-orm/type-tests/pg/select.ts has 1332 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/pg/select.ts:1
drizzle-orm/src/mysql-core/query-builders/select.ts has 1303 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/mysql-core/query-builders/select.ts:1
drizzle-orm/src/pg-core/dialect.ts has 1276 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/pg-core/dialect.ts:1
drizzle-orm/src/pg-core/query-builders/select.ts has 1270 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/pg-core/query-builders/select.ts:1
drizzle-orm/src/gel-core/dialect.ts has 1267 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/gel-core/dialect.ts:1
drizzle-orm/src/gel-core/query-builders/select.ts has 1257 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/gel-core/query-builders/select.ts:1
drizzle-orm/type-tests/geldb/select.ts has 1191 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/geldb/select.ts:1
drizzle-orm/src/mysql-core/dialect.ts has 1190 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/mysql-core/dialect.ts:1
drizzle-orm/src/singlestore-core/query-builders/select.ts has 1120 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/singlestore-core/query-builders/select.ts:1
drizzle-orm/type-tests/mysql/select.ts has 1071 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/mysql/select.ts:1
drizzle-orm/src/sqlite-core/query-builders/select.ts has 1035 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/sqlite-core/query-builders/select.ts:1
drizzle-orm/type-tests/mysql/tables.ts has 1020 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/mysql/tables.ts:1
drizzle-orm/type-tests/singlestore/tables.ts has 972 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/singlestore/tables.ts:1
drizzle-orm/src/sqlite-core/dialect.ts has 913 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/sqlite-core/dialect.ts:1
drizzle-orm/type-tests/singlestore/select.ts has 908 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/singlestore/select.ts:1
drizzle-orm/type-tests/geldb/tables.ts has 886 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/geldb/tables.ts:1
drizzle-seed/src/services/GeneratorFuncs.ts has 884 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-seed/src/services/GeneratorFuncs.ts:1
drizzle-orm/src/singlestore-core/dialect.ts has 834 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/singlestore-core/dialect.ts:1
drizzle-orm/type-tests/sqlite/select.ts has 771 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/sqlite/select.ts:1
drizzle-orm/src/sql/expressions/conditions.ts has 703 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/sql/expressions/conditions.ts:1
drizzle-orm/src/relations.ts has 667 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/relations.ts:1
drizzle-orm/src/pg-core/db.ts has 665 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/pg-core/db.ts:1
drizzle-orm/src/gel-core/db.ts has 644 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/gel-core/db.ts:1
drizzle-orm/src/sqlite-core/db.ts has 620 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/sqlite-core/db.ts:1
drizzle-orm/src/sql/sql.ts has 611 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/sql/sql.ts:1
drizzle-orm/src/pg-core/query-builders/update.ts has 575 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/pg-core/query-builders/update.ts:1
drizzle-orm/type-tests/sqlite/tables.ts has 535 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/type-tests/sqlite/tables.ts:1
drizzle-orm/src/gel-core/query-builders/update.ts has 513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/gel-core/query-builders/update.ts:1
drizzle-orm/src/mysql-core/db.ts has 512 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/mysql-core/db.ts:1
drizzle-orm/src/singlestore-core/db.ts has 505 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/singlestore-core/db.ts:1
drizzle-orm/src/sqlite-core/query-builders/select.types.ts has 438 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/sqlite-core/query-builders/select.types.ts:1
drizzle-orm/src/singlestore-core/query-builders/select.types.ts has 437 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/singlestore-core/query-builders/select.types.ts:1
drizzle-orm/src/mysql-core/query-builders/select.types.ts has 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/mysql-core/query-builders/select.types.ts:1
drizzle-orm/src/sqlite-core/query-builders/update.ts has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/sqlite-core/query-builders/update.ts:1
drizzle-orm/src/pg-core/query-builders/insert.ts has 415 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/pg-core/query-builders/insert.ts:1
drizzle-orm/src/pg-core/query-builders/select.types.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — drizzle-orm/src/pg-core/query-builders/select.types.ts:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Do you agree with this assessment?
R4 · Test Coverage7.7 / 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.
No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — drizzle-orm/src/vercel-postgres/session.ts:1, drizzle-orm/src/neon-serverless/session.ts:1, drizzle-orm/src/netlify-db/session.ts:1, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
Do you agree with this assessment?
R7 · Dead Code9.6 / 10Exemplary✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
1 file(s) (~81 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package.
56 file(s) (~38585 LoC) were excluded from dead-code analysis. This package DOES declare main/module/exports — but every declared target is missing from the scanned tree, which is what a build-output entry (dist/, lib/, out/) looks like before the package is built. Point a declared target at the source entry, or build the package before scanning, so reachability can follow it. — drizzle-kit
5 file(s) (~194 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — integration-tests/type-tests/join-nodenext
Nothing imports this binding — it is safe to review for removal. — drizzle-seed/src/services/Generators.ts:944
Nothing ultimately consumes this binding: its only referrer is the re-export in drizzle-typebox/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in drizzle-typebox/src/index.ts in the same commit, or the barrel will import a name that no longer exists. — drizzle-typebox/src/schema.ts:115
Nothing ultimately consumes this binding: its only referrer is the re-export in drizzle-valibot/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in drizzle-valibot/src/index.ts in the same commit, or the barrel will import a name that no longer exists. — drizzle-valibot/src/utils.ts:31
This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×5) — drizzle-orm/src/gel-core/view.ts:433, drizzle-orm/src/gel-core/view.ts:437, drizzle-orm/src/utils.ts:284, …
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — integration-tests/tests/sqlite/durable-objects/index.ts:3
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. (×3)
Only test files import it (first: drizzle-kit/tests/cli-export.test.ts:1) — move it to devDependencies. — REDACTED:46
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
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.
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.
Do you agree with this assessment?
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.
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.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document2.2 / 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.
`createSelectSchema` is exported, takes a document from its caller (line 94) and hands it to `handleColumns`, which calls itself at line 32 (`handleColumns`) with a piece of `refinements` — and nowhere in `handleColumns` 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 `handleColumns` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — drizzle-zod/src/schema.ts:32
`createSelectSchema` is exported, takes a document from its caller (line 58) and hands it to `handleColumns`, which calls itself at line 24 (`handleColumns`) with a piece of `refinements` — and nowhere in `handleColumns` 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 `handleColumns` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — drizzle-valibot/src/schema.ts:24
`handleColumns` is exported and takes `refinements: Record<string, any>` from its caller, and it calls itself at line 31 (`handleColumns`) with a piece of `refinements` — and nowhere in `handleColumns` 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 `handleColumns` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — drizzle-typebox/src/schema.ts:31
What to do
Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
Other · Code Health — Whether 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.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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.
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.
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.
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.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
~2.2 `!` null assertions per 1k TypeScript source lines — 455 assertion(s) across the 205053 source line(s) of the 520 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: drizzle-seed/src/services/SeedService.ts (92), drizzle-seed/src/services/Generators.ts (65), drizzle-seed/src/index.ts (25). 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 `?`).
Do you agree with this assessment?
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.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
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 — 53 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
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.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D21 Naming Consistency — Naming consistency is measured on C# only; JavaScript, TypeScript not measured.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D24 Comment Value — D24 reads C# and Visual Basic comments only — this repository's production source is .ts, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.js,.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 31 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) 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.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — drizzle-arktype/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
M4 Documentation accuracy — Not applicable: the 19 current-state document(s) make no claim of a kind M4 checks. 23 claim(s) of kinds M4 does not check were not checked (path 4, command argument 4, install 15); M4 checks only links and versions.
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — Drizzle, Knex, Prisma is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
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 applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
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
S1 Web-Security Posture — Not assessed: 521 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. The server controls — HTTPS enforcement, HSTS, cookie flags, 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.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — 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
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.
Orphaned knowledge drizzle-seed/src/services/SeedService.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge drizzle-seed/src/services/GeneratorFuncs.ts:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Assertions commented out: Simple case from GH integration-tests/tests/relational/issues-schemas/wrong-mapping/pg.test.ts:191— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
D10 · Test Quality· No assertions (empty test) · ×1
No assertions (empty test): add table #5 drizzle-kit/tests/sqlite-tables.test.ts:133— Test method has an empty body — it asserts nothing and exercises no code.
Unlisted import 'chai' integration-tests/tests/sqlite/durable-objects/index.ts:3— Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.
TodoComment integration-tests/tests/utils/is-config.test.ts:23— // todo get back after we will have a pool for vercel — 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 integration-tests/tests/singlestore/singlestore-common.ts:2343— // TODO: Unskip when views are supported — 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 integration-tests/tests/singlestore/singlestore-common.ts:2766— // TODO: Unskip when views are supported — 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 integration-tests/tests/singlestore/singlestore-common.ts:2805— // TODO: Unskip when views are supported — 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 integration-tests/tests/singlestore/singlestore-prefixed.test.ts:1087— // TODO: Unskip when views are supported — 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 integration-tests/tests/singlestore/singlestore-prefixed.test.ts:1399— // TODO: Unskip when views are supported — 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 integration-tests/tests/singlestore/singlestore-prefixed.test.ts:1436— // TODO: Unskip when views are supported — 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 integration-tests/tests/singlestore/singlestore-common.ts:3013— // TODO (https://memsql.atlassian.net/browse/MCDB-63261) allow chaining limit and orderby in subquery
TodoComment integration-tests/tests/singlestore/singlestore-common.ts:4284— // TODO: Unkip this test when views are supported — 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 integration-tests/tests/seeder/pgSchema.ts:272— // TODO: add tests for data type with different modes — 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 drizzle-seed/tests/pg/generatorsTest/pgSchema.ts:90— // TODO: add tests for data type with different modes — 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 integration-tests/tests/relational/bettersqlite.test.ts:3234— // TODO Check order — 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 integration-tests/tests/relational/turso.test.ts:3259— // TODO Check order — 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 integration-tests/tests/relational/turso.test.ts:464— // TODO check order — 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 integration-tests/tests/relational/turso.test.ts:1983— // TODO. Check order — 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 integration-tests/tests/relational/issues-schemas/wrong-mapping/pg.test.ts:306— // TODO: don't rely on items order — 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 integration-tests/tests/relational/issues-schemas/wrong-mapping/pg.test.ts:311— // TODO: add correct IDs — 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 integration-tests/tests/pg/pg-common.ts:1435— // TODO change tests to new structure — 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 integration-tests/tests/bun/bun-sql.test.ts:1335— // TODO change tests to new structure — 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 integration-tests/tests/pg/pg-common.ts:2456— // TODO: copy to SQLite and MySQL, add to docs — 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 integration-tests/tests/bun/bun-sql.test.ts:2221— // TODO: copy to SQLite and MySQL, add to docs — 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 integration-tests/tests/gel/gel-custom.test.ts:565— // TODO on conflict does not work — 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 integration-tests/tests/gel/gel-custom.test.ts:581— // // TODO on conflict does not work — 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 integration-tests/tests/gel/gel-custom.test.ts:597— // // TODO on conflict does not work — 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 integration-tests/tests/gel/gel-custom.test.ts:612— // // TODO on conflict does not work — 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.
No assertions: all date and time columns integration-tests/tests/gel/gel.test.ts:2497— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: select integration-tests/tests/bun/sqlite-nw.test.ts:61— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle() integration-tests/js-tests/driver-init/module/better-sqlite3.test.mjs:8— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/module/better-sqlite3.test.mjs:16— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(client) integration-tests/js-tests/driver-init/module/better-sqlite3.test.mjs:89— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/module/libsql.test.mjs:8— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(client) integration-tests/js-tests/driver-init/module/libsql.test.mjs: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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/module/neon-http.test.mjs:12— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(client) integration-tests/js-tests/driver-init/module/neon-http.test.mjs:57— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/module/neon-ws.test.mjs:15— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle() integration-tests/js-tests/driver-init/module/pglite.test.mjs:8— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/module/pglite.test.mjs:15— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(client) integration-tests/js-tests/driver-init/module/pglite.test.mjs: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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/module/postgres-js.test.mjs:12— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(client) integration-tests/js-tests/driver-init/module/postgres-js.test.mjs:52— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/module/tidb.test.mjs:12— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(client) integration-tests/js-tests/driver-init/module/tidb.test.mjs:54— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle() integration-tests/js-tests/driver-init/commonjs/better-sqlite3.test.cjs:8— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/commonjs/better-sqlite3.test.cjs:16— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(client) integration-tests/js-tests/driver-init/commonjs/better-sqlite3.test.cjs:89— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/commonjs/libsql.test.cjs:8— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(client) integration-tests/js-tests/driver-init/commonjs/libsql.test.cjs: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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/commonjs/neon-http.test.cjs:12— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(client) integration-tests/js-tests/driver-init/commonjs/neon-http.test.cjs:57— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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: drizzle(string) integration-tests/js-tests/driver-init/commonjs/neon-ws.test.cjs:15— 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* — so verification routed through a helper of your own naming, through a base-class or callback object whose members hold the assertions, or through a harness that fails by throwing under some other name, 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.
+ 31 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file drizzle-orm/src/vercel-postgres/session.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 drizzle-orm/src/neon-serverless/session.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 drizzle-orm/src/netlify-db/session.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 drizzle-orm/src/neon-http/session.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 drizzle-orm/src/sqlite-proxy/session.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 drizzle-orm/src/netlify-db/driver.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 drizzle-orm/src/neon-http/driver.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 drizzle-orm/src/pglite/session.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 drizzle-orm/src/bun-sql/session.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 drizzle-orm/src/cache/upstash/cache.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 drizzle-orm/src/sql-js/session.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 drizzle-orm/src/op-sqlite/session.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 drizzle-orm/src/mysql-proxy/session.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 drizzle-orm/src/xata-http/session.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 drizzle-orm/src/singlestore-core/view.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 drizzle-orm/src/singlestore-proxy/session.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 drizzle-orm/src/expo-sqlite/session.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 drizzle-orm/src/pg-proxy/session.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 drizzle-orm/src/pglite/driver.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 drizzle-orm/src/neon-serverless/driver.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 drizzle-orm/src/singlestore-core/query-builders/query.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 drizzle-arktype/scripts/fix-imports.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 drizzle-typebox/scripts/fix-imports.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 drizzle-valibot/scripts/fix-imports.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 drizzle-zod/scripts/fix-imports.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.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/utils.ts:103— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via utils.prepareCheckParams — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/utils.ts:125— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via utils.prepareDropParams — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/utils.ts:169— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via utils.prepareGenerateConfig — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/utils.ts:219— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via utils.prepareExportConfig — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/utils.ts:75— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via utils.dryJournal — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/utils.ts:96— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via utils.prepareOutFolder — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/utils.ts:132— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via utils.validateWithReport — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/utils.ts:193— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via utils.prepareMigrationFolder — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:583— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via SingleStoreCreateTableConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:659— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via SQLiteCreateTableConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:1560— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via SingleStoreDropTableConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:1571— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via SQLiteDropTableConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:1597— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via SqliteRenameTableConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:1619— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via SingleStoreRenameTableConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:1865— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via SQLiteAlterTableAddColumnConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:2377— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via LibSQLModifyColumn.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:3580— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via CreateSingleStoreIndexConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:3606— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via CreateSqliteIndexConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:3732— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via SqliteDropIndexConvertor.can — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/sqlgenerator.ts:4122— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via sqlgenerator.fromJson — couples the contexts.
Cross-context type Dialect (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/check.ts:4— Dialect (context drizzle-orm) is exposed in drizzle-kit's public surface via check.checkHandler — couples the contexts.
Skipped test: insert + db.all + db.get + db.values + db.run integration-tests/tests/sqlite/sqlite-proxy-batch.test.ts:501— Skipped — switched off by test.skip
Skipped test: set operations (mixed) from query builder integration-tests/tests/singlestore/singlestore-common.ts:3404— Skipped — switched off by test.skip
Skipped test: [Find One] Get users with posts + orderBy integration-tests/tests/relational/bettersqlite.test.ts:1959— Skipped — switched off by test.skip
Skipped test: Get user with invitee and posts + orderBy integration-tests/tests/relational/bettersqlite.test.ts:3235— Skipped — switched off by test.skip
Skipped test: [Find Many] Get users with posts + orderBy integration-tests/tests/relational/turso.test.ts:465— Skipped — switched off by test.skip
Skipped test: [Find One] Get users with posts + orderBy integration-tests/tests/relational/turso.test.ts:1984— Skipped — switched off by test.skip
Skipped test: Get user with invitee and posts + orderBy integration-tests/tests/relational/turso.test.ts:3260— Skipped — switched off by test.skip
Skipped test: all date and time columns with timezone integration-tests/tests/pg/awsdatapi.test.ts:1383— Skipped — switched off by test.skip
Skipped test: test mode string for timestamp with timezone in different timezone integration-tests/tests/pg/neon-http.test.ts:368— Skipped — switched off by test.skip
Skipped test: test mode string for timestamp with timezone in different timezone integration-tests/tests/pg/neon-serverless.test.ts:376— Skipped — switched off by test.skip
Skipped test: test mode string for timestamp with timezone in different timezone integration-tests/tests/pg/netlify-db.test.ts:362— Skipped — switched off by test.skip
Skipped test: getTableConfig: policies integration-tests/tests/pg/rls/rls.definition.test.ts:5— Skipped — switched off by test.skip
Skipped test: select with group by as sql + column integration-tests/tests/gel/gel.test.ts:1209— Skipped — switched off by test.skip
Skipped test: array types integration-tests/tests/bun/bun-sql.test.ts:1963— Skipped — switched off by test.skip
Skipped test: all date and time columns integration-tests/tests/bun/bun-sql.test.ts:2477— Skipped — switched off by test.skip
Skipped test: insert undefined integration-tests/tests/bun/bun-sql.test.ts:2977— Skipped — switched off by test.skip
Skipped test: array mapping and parsing integration-tests/tests/bun/bun-sql.test.ts:3608— Skipped — switched off by test.skip
Skipped test: proper json and jsonb handling integration-tests/tests/bun/bun-sql.test.ts:4401— Skipped — switched off by test.skip
Skipped test: select large integer integration-tests/tests/bun/sqlite.test.ts:48— Skipped — switched off by test.skip
Deprecated: @esbuild-kit/esm-loader REDACTED:47— @esbuild-kit/esm-loader 2.6.5, declared in REDACTED, is marked deprecated by its publisher: "Merged into tsx: https://tsx.hirok.io". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @vercel/postgres REDACTED:76— @vercel/postgres 0.8.0, declared in REDACTED, is marked deprecated by its publisher: "@vercel/postgres is deprecated. If you are setting up a new database, you can choose an alternate storage solution from the Vercel Marketplace. If you had an existing Vercel Postgres database, it should have been migrated to Neon as a native Vercel integration. You can find more details and the guide to migrate to Neon's SDKs here: https://neon.com/docs/guides/vercel-postgres-transition-guide". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:88— eslint 8.57.1, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: glob REDACTED:93— glob 8.1.0, declared in REDACTED, is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid REDACTED:110— uuid 9.0.1, declared in REDACTED, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @miniflare/d1 drizzle-orm/package.json:176— @miniflare/d1 2.14.4, declared in drizzle-orm/package.json, is marked deprecated by its publisher: "Miniflare v2 is no longer supported. Please upgrade to Miniflare v4". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @vercel/postgres drizzle-orm/package.json:191— @vercel/postgres 0.8.0, declared in drizzle-orm/package.json, is marked deprecated by its publisher: "@vercel/postgres is deprecated. If you are setting up a new database, you can choose an alternate storage solution from the Vercel Marketplace. If you had an existing Vercel Postgres database, it should have been migrated to Neon as a native Vercel integration. You can find more details and the guide to migrate to Neon's SDKs here: https://neon.com/docs/guides/vercel-postgres-transition-guide". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @xata.io/client drizzle-orm/package.json:192— @xata.io/client 0.29.5, declared in drizzle-orm/package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: glob drizzle-orm/package.json:198— glob 11.0.2, declared in drizzle-orm/package.json, is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid drizzle-seed/package.json:98— uuid 10.0.0, declared in drizzle-seed/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint eslint-plugin-drizzle/package.json:30— eslint 8.57.1, declared in eslint-plugin-drizzle/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @miniflare/d1 integration-tests/package.json:47— @miniflare/d1 2.14.4, declared in integration-tests/package.json, is marked deprecated by its publisher: "Miniflare v2 is no longer supported. Please upgrade to Miniflare v4". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @miniflare/shared integration-tests/package.json:48— @miniflare/shared 2.14.4, declared in integration-tests/package.json, is marked deprecated by its publisher: "Miniflare v2 is no longer supported. Please upgrade to Miniflare v4". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @vercel/postgres integration-tests/package.json:54— @vercel/postgres 0.8.0, declared in integration-tests/package.json, is marked deprecated by its publisher: "@vercel/postgres is deprecated. If you are setting up a new database, you can choose an alternate storage solution from the Vercel Marketplace. If you had an existing Vercel Postgres database, it should have been migrated to Neon as a native Vercel integration. You can find more details and the guide to migrate to Neon's SDKs here: https://neon.com/docs/guides/vercel-postgres-transition-guide". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @xata.io/client integration-tests/package.json:55— @xata.io/client 0.29.5, declared in integration-tests/package.json, is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid integration-tests/package.json:75— uuid 9.0.1, declared in integration-tests/package.json, is marked deprecated by its publisher: "uuid@10 and below is no longer supported. For ESM codebases, update to uuid@latest. For CommonJS codebases, use uuid@11 (but be aware this version will likely be deprecated in 2028).". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:27— eslint 8.57.1, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: glob REDACTED:33— glob 10.4.5, declared in REDACTED, is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". Replace it with the package or version that message names, or record why this one must stay.
D30 · Dependency Vulnerabilities· Medium CVE · ×15
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/utils.ts:462— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via utils.preparePullConfig — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/introspect-sqlite.ts:73— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect-sqlite.schemaToTypeScript — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/sqliteIntrospect.ts:12— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via sqliteIntrospect.sqliteIntrospect — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/introspect-gel.ts:211— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect-gel.schemaToTypeScript — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/introspect-mysql.ts:133— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect-mysql.schemaToTypeScript — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/introspect-pg.ts:309— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect-pg.schemaToTypeScript — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/introspect-singlestore.ts:139— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect-singlestore.schemaToTypeScript — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/introspect.ts:55— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect.introspectPostgres — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/introspect.ts:181— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect.introspectGel — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/introspect.ts:307— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect.introspectMysql — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/introspect.ts:418— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect.introspectSingleStore — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/introspect.ts:515— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect.introspectSqlite — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/introspect.ts:627— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect.introspectLibSQL — couples the contexts.
Cross-context type Casing (drizzle-orm → drizzle-kit) drizzle-kit/src/cli/commands/introspect.ts:750— Casing (context drizzle-orm) is exposed in drizzle-kit's public surface via introspect.relationsToTypeScript — couples the contexts.
FileTooLong: services/Generators.ts drizzle-seed/src/services/Generators.ts— FileTooLong — 2007 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1507 over it, 4.01× 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: services/SeedService.ts drizzle-seed/src/services/SeedService.ts— FileTooLong — 1048 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: SeedService (22-1611). The bar is 500 significant lines; this is 548 over it, 2.10× 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/index.ts drizzle-seed/src/index.ts— FileTooLong — 995 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 495 over it, 1.99× 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: mysql-core/dialect.ts drizzle-orm/src/mysql-core/dialect.ts— FileTooLong — 945 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 445 over it, 1.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: sqlite-core/dialect.ts drizzle-orm/src/sqlite-core/dialect.ts— FileTooLong — 722 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 222 over it, 1.44× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: singlestore-core/dialect.ts drizzle-orm/src/singlestore-core/dialect.ts— FileTooLong — 661 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 161 over it, 1.32× 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: pg-core/dialect.ts drizzle-orm/src/pg-core/dialect.ts— FileTooLong — 639 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 139 over it, 1.28× 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: gel-core/dialect.ts drizzle-orm/src/gel-core/dialect.ts— FileTooLong — 583 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 83 over it, 1.17× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/relations.ts drizzle-orm/src/relations.ts— FileTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 53 over it, 1.11× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: query-builders/select.ts drizzle-orm/src/mysql-core/query-builders/select.ts— FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 26 over it, 1.05× 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: query-builders/select.ts drizzle-orm/src/pg-core/query-builders/select.ts— FileTooLong — 501 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1 over it, 1.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.
Change coupling: delete.ts ↔ update.ts drizzle-orm/src/pg-core/query-builders/delete.ts:1— `drizzle-orm/src/pg-core/query-builders/delete.ts` and `drizzle-orm/src/pg-core/query-builders/update.ts` change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 `25882a40` Add insert, update and delete as CTE tests and fixes for PG; `67f3c1ab` Add delete as a valid CTE in PG; `18791925` Remove manual casing caching — run `git show` on any of them.
Change coupling: delete.ts ↔ update.ts drizzle-orm/src/mysql-core/query-builders/delete.ts:1— `drizzle-orm/src/mysql-core/query-builders/delete.ts` and `drizzle-orm/src/mysql-core/query-builders/update.ts` change together 83% of the time (10 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — 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 `e348b8cd` Implement limit and order by in MySQL; `18791925` Remove manual casing caching; `68b351fc` [MySQL | SQLite] Extend with clause — run `git show` on any of them.
Change coupling: tables.ts ↔ tables.ts drizzle-orm/type-tests/pg/tables.ts:1— `drizzle-orm/type-tests/pg/tables.ts` and `drizzle-orm/type-tests/sqlite/tables.ts` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `64f1bf77` Add ability to define column types without imports (callback fn); `4d0047df` Add returning ids to mysql insert; `e20b29b0` [All] fixed update set types and added type tests — run `git show` on any of them.
Change coupling: tables.ts ↔ tables.ts drizzle-orm/type-tests/mysql/tables.ts:1— `drizzle-orm/type-tests/mysql/tables.ts` and `drizzle-orm/type-tests/sqlite/tables.ts` change together 70% of the time (7 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `64f1bf77` Add ability to define column types without imports (callback fn); `4d0047df` Add returning ids to mysql insert; `e20b29b0` [All] fixed update set types and added type tests — run `git show` on any of them.
Change coupling: db.ts ↔ db.ts drizzle-orm/src/mysql-core/db.ts:1— `drizzle-orm/src/mysql-core/db.ts` and `drizzle-orm/src/sqlite-core/db.ts` change together 67% of the time (18 of the 27 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 18 shared commits counted here, the most recent 3 are `b529598c` dprint; `e31c65f5` feat: add `$replicas` reference (#4874); `dd5de506` feat: add `$replicas` reference — run `git show` on any of them.
Change coupling: driver.ts ↔ driver.ts drizzle-orm/src/mysql2/driver.ts:1— `drizzle-orm/src/mysql2/driver.ts` and `drizzle-orm/src/planetscale-serverless/driver.ts` change together 60% of the time (9 of the 15 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 `16ce08fb` Removed type-level import existence checks on driver init (fixes #352…; `9a563af0` Fixed broken connection, added missing cases; `00e689ea` Added `drizzle.mock()`, reworked replicas tests — run `git show` on any of them.
Change coupling: REDACTED ↔ REDACTED drizzle-orm/src/neon-serverless/session.ts:1— `drizzle-orm/src/neon-serverless/session.ts` and `drizzle-orm/src/node-postgres/session.ts` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `8cac5d25` Remove global set for node-postgres, neon and vercel; move to on per-…; `3d06cf23` Add full schema information to DB; `508106c6` Improve relational mapper logic for pg — run `git show` on any of them.
Change coupling: delete.ts ↔ insert.ts drizzle-orm/src/pg-core/query-builders/delete.ts:1— `drizzle-orm/src/pg-core/query-builders/delete.ts` and `drizzle-orm/src/pg-core/query-builders/insert.ts` change together 58% of the time (7 of the 12 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 `18791925` Remove manual casing caching; `eeef2de6` [PG] Add insert, delete and update after with; `48d0d7a8` Add jsdoc for Pg insert & update; Fix jsdoc for Pg delete — run `git show` on any of them.
Change coupling: driver.ts ↔ driver.ts drizzle-orm/src/better-sqlite3/driver.ts:1— `drizzle-orm/src/better-sqlite3/driver.ts` and `drizzle-orm/src/postgres-js/driver.ts` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `16ce08fb` Removed type-level import existence checks on driver init (fixes #352…; `00e689ea` Added `drizzle.mock()`, reworked replicas tests; `bff08bf4` Fixed tests, added MockDriver & mock support for reworked drivers — run `git show` on any of them.
Unfinished stub — throws a "not implemented" error REDACTED:61— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error REDACTED:71— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error REDACTED:68— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error REDACTED:84— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error drizzle-orm/src/singlestore-core/columns/datetime.ts:30— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error drizzle-orm/src/singlestore-core/columns/datetime.ts:93— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error drizzle-orm/src/singlestore-core/columns/vector.ts:40— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error drizzle-orm/src/sqlite-core/session.ts:169— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" error drizzle-orm/src/sqlite-core/session.ts:175— A shipped function's whole body still throws a "not implemented" error — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws a "not implemented" exception REDACTED:61— `all` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception REDACTED:71— `transaction` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception REDACTED:68— `transaction` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception REDACTED:84— `transaction` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception drizzle-orm/src/singlestore-core/columns/datetime.ts:30— `generatedAlwaysAs` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception drizzle-orm/src/singlestore-core/columns/datetime.ts:93— `generatedAlwaysAs` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception drizzle-orm/src/singlestore-core/columns/vector.ts:40— `generatedAlwaysAs` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception drizzle-orm/src/sqlite-core/session.ts:169— `mapAllResult` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Unfinished stub — throws a "not implemented" exception drizzle-orm/src/sqlite-core/session.ts:175— `mapGetResult` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
MethodTooLong: SeedService.generatePossibleGenerators drizzle-seed/src/services/SeedService.ts:34— MethodTooLong — generatePossibleGenerators runs 180 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 80 over it, 1.80× 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: SeedService.selectGeneratorForPostgresColumn drizzle-seed/src/services/SeedService.ts:503— MethodTooLong — selectGeneratorForPostgresColumn runs 160 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 60 over it, 1.60× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SeedService.generateTablesValues drizzle-seed/src/services/SeedService.ts:1142— MethodTooLong — generateTablesValues runs 143 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 43 over it, 1.43× 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: SeedService.selectGeneratorForMysqlColumn drizzle-seed/src/services/SeedService.ts:797— MethodTooLong — selectGeneratorForMysqlColumn runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SeedService.generateColumnsValuesByGenerators drizzle-seed/src/services/SeedService.ts:1354— MethodTooLong — generateColumnsValuesByGenerators runs 128 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 28 over it, 1.28× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Change-coupling hub: driver.ts → driver.ts, driver.ts, driver.ts, driver.ts, driver.ts, driver.ts, driver.ts, driver.ts drizzle-orm/src/bun-sqlite/driver.ts— `drizzle-orm/src/bun-sqlite/driver.ts` changes together with 8 other files — `drizzle-orm/src/aws-data-api/pg/driver.ts`, `drizzle-orm/src/better-sqlite3/driver.ts`, `drizzle-orm/src/mysql2/driver.ts`, `drizzle-orm/src/neon-serverless/driver.ts`, `drizzle-orm/src/node-postgres/driver.ts`, `drizzle-orm/src/planetscale-serverless/driver.ts`, `drizzle-orm/src/postgres-js/driver.ts`, `drizzle-orm/src/vercel-postgres/driver.ts` — none of which declares a dependency on it: one file is the hub of 8 separate couplings, not 8 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 8.
Change-coupling hub: driver.ts → driver.ts, driver.ts, driver.ts, driver.ts, driver.ts, driver.ts drizzle-orm/src/vercel-postgres/driver.ts— `drizzle-orm/src/vercel-postgres/driver.ts` changes together with 6 other files — `drizzle-orm/src/better-sqlite3/driver.ts`, `drizzle-orm/src/mysql2/driver.ts`, `drizzle-orm/src/neon-http/driver.ts`, `drizzle-orm/src/neon-serverless/driver.ts`, `drizzle-orm/src/node-postgres/driver.ts`, `drizzle-orm/src/postgres-js/driver.ts` — none of which declares a dependency on it: one file is the hub of 6 separate couplings, not 6 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 6.
Change-coupling hub: driver.ts → driver.ts, driver.ts, driver.ts, driver.ts drizzle-orm/src/neon-serverless/driver.ts— `drizzle-orm/src/neon-serverless/driver.ts` changes together with 4 other files — `drizzle-orm/src/better-sqlite3/driver.ts`, `drizzle-orm/src/mysql2/driver.ts`, `drizzle-orm/src/node-postgres/driver.ts`, `drizzle-orm/src/postgres-js/driver.ts` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: driver.ts → driver.ts, driver.ts, driver.ts, driver.ts, driver.ts, driver.ts, driver.ts, driver.ts, driver.ts, driver.ts drizzle-orm/src/libsql/driver.ts— `drizzle-orm/src/libsql/driver.ts` changes together with 10 other files — `drizzle-orm/src/aws-data-api/pg/driver.ts`, `drizzle-orm/src/better-sqlite3/driver.ts`, `drizzle-orm/src/bun-sqlite/driver.ts`, `drizzle-orm/src/mysql2/driver.ts`, `drizzle-orm/src/neon-http/driver.ts`, `drizzle-orm/src/neon-serverless/driver.ts`, `drizzle-orm/src/node-postgres/driver.ts`, `drizzle-orm/src/planetscale-serverless/driver.ts`, `drizzle-orm/src/postgres-js/driver.ts`, `drizzle-orm/src/vercel-postgres/driver.ts` — none of which declares a dependency on it: one file is the hub of 10 separate couplings, not 10 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 10.
Change-coupling hub: driver.ts → driver.ts, driver.ts, driver.ts drizzle-orm/src/node-postgres/driver.ts— `drizzle-orm/src/node-postgres/driver.ts` changes together with 3 other files — `drizzle-orm/src/better-sqlite3/driver.ts`, `drizzle-orm/src/mysql2/driver.ts`, `drizzle-orm/src/neon-http/driver.ts` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
column.columnToSchema (cyclomatic 22) drizzle-arktype/src/column.ts:66— column.columnToSchema has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
column.columnToSchema (cyclomatic 22) drizzle-typebox/src/column.ts:71— column.columnToSchema has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
column.columnToSchema (cyclomatic 22) drizzle-valibot/src/column.ts:73— column.columnToSchema has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
column.numberColumnToSchema (cyclomatic 21) drizzle-arktype/src/column.ts:128— column.numberColumnToSchema has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
column.numberColumnToSchema (cyclomatic 21) drizzle-typebox/src/column.ts:143— column.numberColumnToSchema has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
column.numberColumnToSchema (cyclomatic 21) drizzle-valibot/src/column.ts:128— column.numberColumnToSchema has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
schema.handleColumns (cyclomatic 17) drizzle-typebox/src/schema.ts:20— schema.handleColumns 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.
schema.handleColumns (cyclomatic 17) drizzle-valibot/src/schema.ts:14— schema.handleColumns 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.
schema.handleColumns (cyclomatic 17) drizzle-zod/src/schema.ts:19— schema.handleColumns 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.
schema.handleColumns (cognitive 28) drizzle-typebox/src/schema.ts:20— schema.handleColumns has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 4 (9 pts), boolean chains 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
schema.handleColumns (cognitive 28) drizzle-valibot/src/schema.ts:14— schema.handleColumns has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 4 (9 pts), boolean chains 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
schema.handleColumns (cognitive 28) drizzle-zod/src/schema.ts:19— schema.handleColumns has cognitive complexity 28 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 4 (9 pts), boolean chains 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
column.columnToSchema (cognitive 19) drizzle-arktype/src/column.ts:66— column.columnToSchema has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18 (19 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
column.columnToSchema (cognitive 19) drizzle-typebox/src/column.ts:71— column.columnToSchema has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18 (19 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
column.columnToSchema (cognitive 19) drizzle-valibot/src/column.ts:73— column.columnToSchema has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18 (19 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Duplicated block (85 lines × 2 locations) drizzle-orm/src/gel-core/query-builders/update.ts:348— drizzle-orm/src/gel-core/query-builders/update.ts:348 · drizzle-orm/src/pg-core/query-builders/update.ts:388 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (85 lines × 2 locations) drizzle-orm/src/gel-core/session.ts:42— drizzle-orm/src/gel-core/session.ts:42 · drizzle-orm/src/sqlite-core/session.ts:71 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (85 lines × 2 locations) drizzle-orm/src/mysql-core/session.ts:70— drizzle-orm/src/mysql-core/session.ts:70 · drizzle-orm/src/singlestore-core/session.ts:68 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
X17 · Uncapped recursion over a caller-supplied document· Recursive walk over a caller-supplied document has no depth cap · ×3
Recursive walk over a caller-supplied document has no depth cap drizzle-zod/src/schema.ts:32— `createSelectSchema` is exported, takes a document from its caller (line 94) and hands it to `handleColumns`, which calls itself at line 32 (`handleColumns`) with a piece of `refinements` — and nowhere in `handleColumns` 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 `handleColumns` 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 drizzle-valibot/src/schema.ts:24— `createSelectSchema` is exported, takes a document from its caller (line 58) and hands it to `handleColumns`, which calls itself at line 24 (`handleColumns`) with a piece of `refinements` — and nowhere in `handleColumns` 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 `handleColumns` 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 drizzle-typebox/src/schema.ts:31— `handleColumns` is exported and takes `refinements: Record<string, any>` from its caller, and it calls itself at line 31 (`handleColumns`) with a piece of `refinements` — and nowhere in `handleColumns` 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 `handleColumns` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.
PreparedQuery.execute (cognitive 31) drizzle-orm/src/mysql-proxy/session.ts:130— PreparedQuery.execute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PreparedQuery.execute (cognitive 31) drizzle-orm/src/singlestore-proxy/session.ts:116— PreparedQuery.execute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
column.stringColumnToSchema (cognitive 17) drizzle-typebox/src/column.ts:261— column.stringColumnToSchema has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (13 pts), ternaries 2 (3 pts), boolean chains 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.
column.stringColumnToSchema (cognitive 17) drizzle-zod/src/column.ts:267— column.stringColumnToSchema has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 3 (4 pts), boolean chains 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×2
Duplicated block (94 lines × 2 locations) drizzle-orm/src/mysql-core/dialect.ts:852— drizzle-orm/src/mysql-core/dialect.ts:852 · drizzle-orm/src/singlestore-core/dialect.ts:802 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (94 lines × 2 locations) drizzle-orm/src/mysql-core/table.ts:43— drizzle-orm/src/mysql-core/table.ts:43 · drizzle-orm/src/singlestore-core/table.ts:31 — 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.
Complex function buildRelationalQuery (cyclomatic 37, cognitive 84) drizzle-orm/src/mysql-core/dialect.ts:658— buildRelationalQuery has cyclomatic complexity 37 and cognitive complexity 84; 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 buildRelationalQuery (cyclomatic 37, cognitive 84) drizzle-orm/src/singlestore-core/dialect.ts:605— buildRelationalQuery has cyclomatic complexity 37 and cognitive complexity 84; 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 buildRelationalQueryWithoutPK (cyclomatic 35, cognitive 82) drizzle-orm/src/gel-core/dialect.ts:1141— buildRelationalQueryWithoutPK has cyclomatic complexity 35 and cognitive complexity 82; 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 buildRelationalQueryWithoutPK (cyclomatic 35, cognitive 82) drizzle-orm/src/pg-core/dialect.ts:1150— buildRelationalQueryWithoutPK has cyclomatic complexity 35 and cognitive complexity 82; 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 buildSelectQuery (cyclomatic 28, cognitive 39) drizzle-orm/src/gel-core/dialect.ts:336— buildSelectQuery has cyclomatic complexity 28 and cognitive complexity 39; 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 buildSelectQuery (cyclomatic 28, cognitive 39) drizzle-orm/src/pg-core/dialect.ts:341— buildSelectQuery has cyclomatic complexity 28 and cognitive complexity 39; 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.
C1 · Data Protection· No data-protection/encryption · ×1
No data-protection/encryption drizzle-orm/src/prisma/schema.prisma:12— 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.
SeedService.selectGeneratorForPostgresColumn::pickGenerator (cyclomatic 60) drizzle-seed/src/services/SeedService.ts:507— SeedService.selectGeneratorForPostgresColumn::pickGenerator has cyclomatic complexity 60 (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 file is where this pass's cyclomatic complexity CONCENTRATES: drizzle-seed/src/services/SeedService.ts holds 6 of the 61 methods over the threshold — including the worst — and 182 of the 607 points over it (30%), 2.4× the next-largest file (drizzle-orm/src/mysql-core/dialect.ts at 75). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
SeedService.generatePossibleGenerators (cyclomatic 57) drizzle-seed/src/services/SeedService.ts:34— SeedService.generatePossibleGenerators has cyclomatic complexity 57 (threshold 15). Of this number, 54 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. This file is where this pass's cyclomatic complexity CONCENTRATES: drizzle-seed/src/services/SeedService.ts holds 6 of the 61 methods over the threshold — including the worst — and 182 of the 607 points over it (30%), 2.4× the next-largest file (drizzle-orm/src/mysql-core/dialect.ts at 75). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
SeedService.selectGeneratorForMysqlColumn::pickGenerator (cyclomatic 57) drizzle-seed/src/services/SeedService.ts:801— SeedService.selectGeneratorForMysqlColumn::pickGenerator has cyclomatic complexity 57 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: drizzle-seed/src/services/SeedService.ts holds 6 of the 61 methods over the threshold — including the worst — and 182 of the 607 points over it (30%), 2.4× the next-largest file (drizzle-orm/src/mysql-core/dialect.ts at 75). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
MySqlDialect.buildRelationalQueryWithoutLateralSubqueries (cyclomatic 40) drizzle-orm/src/mysql-core/dialect.ts:1000— MySqlDialect.buildRelationalQueryWithoutLateralSubqueries has cyclomatic complexity 40 (threshold 15). Of this number, 35 points are the body's own statements and 5 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.
GelDialect.buildRelationalQueryWithoutPK (cyclomatic 39) drizzle-orm/src/gel-core/dialect.ts:1141— GelDialect.buildRelationalQueryWithoutPK has cyclomatic complexity 39 (threshold 15). Of this number, 34 points are the body's own statements and 5 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.
MySqlDialect.buildRelationalQuery (cyclomatic 39) drizzle-orm/src/mysql-core/dialect.ts:658— MySqlDialect.buildRelationalQuery has cyclomatic complexity 39 (threshold 15). Of this number, 34 points are the body's own statements and 5 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.
PgDialect.buildRelationalQueryWithoutPK (cyclomatic 39) drizzle-orm/src/pg-core/dialect.ts:1150— PgDialect.buildRelationalQueryWithoutPK has cyclomatic complexity 39 (threshold 15). Of this number, 34 points are the body's own statements and 5 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.
SingleStoreDialect.buildRelationalQuery (cyclomatic 39) drizzle-orm/src/singlestore-core/dialect.ts:605— SingleStoreDialect.buildRelationalQuery has cyclomatic complexity 39 (threshold 15). Of this number, 34 points are the body's own statements and 5 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.
SQLiteDialect.buildRelationalQuery (cyclomatic 38) drizzle-orm/src/sqlite-core/dialect.ts:606— SQLiteDialect.buildRelationalQuery has cyclomatic complexity 38 (threshold 15). Of this number, 33 points are the body's own statements and 5 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.
SQL.buildQueryFromSourceParams (cyclomatic 37) drizzle-orm/src/sql/sql.ts:148— SQL.buildQueryFromSourceParams has cyclomatic complexity 37 (threshold 15). Most of this is not in the body itself: 3 of the 37 points are its own statements and the rest belongs to one function literal inside it that branches (line 163). 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.
SeedService.selectGeneratorForSqlite::pickGenerator (cyclomatic 37) drizzle-seed/src/services/SeedService.ts:997— SeedService.selectGeneratorForSqlite::pickGenerator has cyclomatic complexity 37 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This file is where this pass's cyclomatic complexity CONCENTRATES: drizzle-seed/src/services/SeedService.ts holds 6 of the 61 methods over the threshold — including the worst — and 182 of the 607 points over it (30%), 2.4× the next-largest file (drizzle-orm/src/mysql-core/dialect.ts at 75). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
MySqlDialect.buildSelectQuery (cyclomatic 36) drizzle-orm/src/mysql-core/dialect.ts:312— MySqlDialect.buildSelectQuery has cyclomatic complexity 36 (threshold 15). Of this number, 33 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.
SingleStoreDialect.buildSelectQuery (cyclomatic 35) drizzle-orm/src/singlestore-core/dialect.ts:299— SingleStoreDialect.buildSelectQuery has cyclomatic complexity 35 (threshold 15). Of this number, 32 points are the body's own statements and 3 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SeedService.generateTablesValues (cyclomatic 35) drizzle-seed/src/services/SeedService.ts:1142— SeedService.generateTablesValues 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. This file is where this pass's cyclomatic complexity CONCENTRATES: drizzle-seed/src/services/SeedService.ts holds 6 of the 61 methods over the threshold — including the worst — and 182 of the 607 points over it (30%), 2.4× the next-largest file (drizzle-orm/src/mysql-core/dialect.ts at 75). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
GenerateValuesFromArray.checks (cyclomatic 32) drizzle-seed/src/services/Generators.ts:212— GenerateValuesFromArray.checks has cyclomatic complexity 32 (threshold 15). Of this number, 30 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
GelDialect.buildSelectQuery (cyclomatic 28) drizzle-orm/src/gel-core/dialect.ts:336— GelDialect.buildSelectQuery has cyclomatic complexity 28 (threshold 15). 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: 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.
PgDialect.buildSelectQuery (cyclomatic 28) drizzle-orm/src/pg-core/dialect.ts:341— PgDialect.buildSelectQuery has cyclomatic complexity 28 (threshold 15). 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: 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.
utils.isConfig (cyclomatic 28) drizzle-orm/src/utils.ts:286— utils.isConfig 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.
MySqlSelectQueryBuilderBase.createJoin (cyclomatic 26) drizzle-orm/src/mysql-core/query-builders/select.ts:235— MySqlSelectQueryBuilderBase.createJoin has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to one function literal inside it that branches (line 244). 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.
SeedService.generateColumnsValuesByGenerators (cyclomatic 26) drizzle-seed/src/services/SeedService.ts:1354— SeedService.generateColumnsValuesByGenerators 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. This file is where this pass's cyclomatic complexity CONCENTRATES: drizzle-seed/src/services/SeedService.ts holds 6 of the 61 methods over the threshold — including the worst — and 182 of the 607 points over it (30%), 2.4× the next-largest file (drizzle-orm/src/mysql-core/dialect.ts at 75). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
column.columnToSchema (cyclomatic 26) drizzle-zod/src/column.ts:70— column.columnToSchema has cyclomatic complexity 26 (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.
column.numberColumnToSchema (cyclomatic 24) drizzle-zod/src/column.ts:137— column.numberColumnToSchema has cyclomatic complexity 24 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GelPreparedQuery.queryWithCache (cyclomatic 20) drizzle-orm/src/gel-core/session.ts:42— GelPreparedQuery.queryWithCache 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.
MySqlPreparedQuery.queryWithCache (cyclomatic 20) drizzle-orm/src/mysql-core/session.ts:70— MySqlPreparedQuery.queryWithCache 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.
PgPreparedQuery.queryWithCache (cyclomatic 20) drizzle-orm/src/pg-core/session.ts:64— PgPreparedQuery.queryWithCache 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.
SingleStorePreparedQuery.queryWithCache (cyclomatic 20) drizzle-orm/src/singlestore-core/session.ts:68— SingleStorePreparedQuery.queryWithCache 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.
utils.mapResultRow (cyclomatic 20) drizzle-orm/src/utils.ts:15— utils.mapResultRow has cyclomatic complexity 20 (threshold 15). Most of this is not in the body itself: 6 of the 20 points are its own statements and the rest belongs to one function literal inside it that branches (line 24). 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.
SQLitePreparedQuery.queryWithCache (cyclomatic 20) drizzle-orm/src/sqlite-core/session.ts:71— SQLitePreparedQuery.queryWithCache 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.
schema.handleColumns (cyclomatic 19) drizzle-arktype/src/schema.ts:14— schema.handleColumns 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.
GelSelectQueryBuilderBase.createJoin (cyclomatic 19) drizzle-orm/src/gel-core/query-builders/select.ts:222— GelSelectQueryBuilderBase.createJoin 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 231). 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.
PgSelectQueryBuilderBase.createJoin (cyclomatic 19) drizzle-orm/src/pg-core/query-builders/select.ts:229— PgSelectQueryBuilderBase.createJoin 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 238). 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.
SQLiteSelectQueryBuilderBase.createJoin (cyclomatic 19) drizzle-orm/src/sqlite-core/query-builders/select.ts:207— SQLiteSelectQueryBuilderBase.createJoin 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 212). 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.
SQLiteDialect.buildSelection (cyclomatic 19) drizzle-orm/src/sqlite-core/dialect.ts:178— SQLiteDialect.buildSelection 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 2 function literals inside it that branch (lines 184, 195). 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.
SQLiteDialect.buildSelectQuery (cyclomatic 19) drizzle-orm/src/sqlite-core/dialect.ts:344— SQLiteDialect.buildSelectQuery has cyclomatic complexity 19 (threshold 15). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SQLiteDialect.buildInsertQuery (cyclomatic 19) drizzle-orm/src/sqlite-core/dialect.ts:510— SQLiteDialect.buildInsertQuery 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.
MySqlDialect.buildInsertQuery (cyclomatic 18) drizzle-orm/src/mysql-core/dialect.ts:561— MySqlDialect.buildInsertQuery 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.
SingleStoreSelectQueryBuilderBase.createJoin (cyclomatic 18) drizzle-orm/src/singlestore-core/query-builders/select.ts:208— SingleStoreSelectQueryBuilderBase.createJoin has cyclomatic complexity 18 (threshold 15). Most of this is not in the body itself: 1 of the 18 points is its own statement and the rest belongs to one function literal inside it that branches (line 217). 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.
GelDialect.buildInsertQuery (cyclomatic 17) drizzle-orm/src/gel-core/dialect.ts:508— GelDialect.buildInsertQuery 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.
MySqlDialect.buildSelection (cyclomatic 17) drizzle-orm/src/mysql-core/dialect.ts:215— MySqlDialect.buildSelection 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 2 function literals inside it that branch (lines 221, 232). 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.
PgDialect.buildSelection (cyclomatic 17) drizzle-orm/src/pg-core/dialect.ts:211— PgDialect.buildSelection 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 2 function literals inside it that branch (lines 218, 229). 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.
PgDialect.buildInsertQuery (cyclomatic 17) drizzle-orm/src/pg-core/dialect.ts:513— PgDialect.buildInsertQuery 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.
SingleStoreDialect.buildSelection (cyclomatic 17) drizzle-orm/src/singlestore-core/dialect.ts:214— SingleStoreDialect.buildSelection 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 2 function literals inside it that branch (lines 220, 231). 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.
relations.normalizeRelation (cyclomatic 17) drizzle-orm/src/relations.ts:559— relations.normalizeRelation 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.
GenerateValuesFromArray.init (cyclomatic 17) drizzle-seed/src/services/Generators.ts:283— GenerateValuesFromArray.init 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.
GelDialect.buildJoins (cyclomatic 16) drizzle-orm/src/gel-core/dialect.ts:274— GelDialect.buildJoins 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.
PgDialect.buildJoins (cyclomatic 16) drizzle-orm/src/pg-core/dialect.ts:279— PgDialect.buildJoins 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.
SingleStoreDialect.buildInsertQuery (cyclomatic 16) drizzle-orm/src/singlestore-core/dialect.ts:519— SingleStoreDialect.buildInsertQuery 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.
relations.extractTablesRelationalConfig (cyclomatic 16) drizzle-orm/src/relations.ts:416— relations.extractTablesRelationalConfig 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.
rls.crudPolicy (cyclomatic 16) drizzle-orm/src/neon/rls.ts:15— rls.crudPolicy 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, 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.
GeneratePhoneNumber.init (cyclomatic 16) drizzle-seed/src/services/Generators.ts:1905— GeneratePhoneNumber.init 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.
index.getPostgresInfo::getTypeParams (cyclomatic 16) drizzle-seed/src/index.ts:744— index.getPostgresInfo::getTypeParams 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.
column.stringColumnToSchema (cyclomatic 16) drizzle-zod/src/column.ts:267— column.stringColumnToSchema 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.
SeedService.generatePossibleGenerators (cognitive 114) drizzle-seed/src/services/SeedService.ts:34— SeedService.generatePossibleGenerators has cognitive complexity 114 (threshold 15). Drivers by points: if/else 24 (75 pts), boolean chains 20, loops 5 (12 pts), ternaries 2 (7 pts) (nesting depth added 63). Of this number, 113 points are the body's own statements and 1 belongs to 2 function literals 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.
MySqlDialect.buildRelationalQueryWithoutLateralSubqueries (cognitive 78) drizzle-orm/src/mysql-core/dialect.ts:1000— MySqlDialect.buildRelationalQueryWithoutLateralSubqueries has cognitive complexity 78 (threshold 15). Drivers by points: if/else 19 (40 pts), ternaries 8 (23 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 43). Of this number, 73 points are the body's own statements and 5 belong to 4 function literals 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.
GelDialect.buildRelationalQueryWithoutPK (cognitive 75) drizzle-orm/src/gel-core/dialect.ts:1141— GelDialect.buildRelationalQueryWithoutPK has cognitive complexity 75 (threshold 15). Drivers by points: if/else 18 (37 pts), ternaries 8 (23 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 41). Of this number, 70 points are the body's own statements and 5 belong to 4 function literals 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.
MySqlDialect.buildRelationalQuery (cognitive 75) drizzle-orm/src/mysql-core/dialect.ts:658— MySqlDialect.buildRelationalQuery has cognitive complexity 75 (threshold 15). Drivers by points: if/else 18 (37 pts), ternaries 8 (23 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 41). Of this number, 70 points are the body's own statements and 5 belong to 4 function literals 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.
PgDialect.buildRelationalQueryWithoutPK (cognitive 75) drizzle-orm/src/pg-core/dialect.ts:1150— PgDialect.buildRelationalQueryWithoutPK has cognitive complexity 75 (threshold 15). Drivers by points: if/else 18 (37 pts), ternaries 8 (23 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 41). Of this number, 70 points are the body's own statements and 5 belong to 4 function literals 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.
SingleStoreDialect.buildRelationalQuery (cognitive 75) drizzle-orm/src/singlestore-core/dialect.ts:605— SingleStoreDialect.buildRelationalQuery has cognitive complexity 75 (threshold 15). Drivers by points: if/else 18 (37 pts), ternaries 8 (23 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 41). Of this number, 70 points are the body's own statements and 5 belong to 4 function literals 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.
SQLiteDialect.buildRelationalQuery (cognitive 75) drizzle-orm/src/sqlite-core/dialect.ts:606— SQLiteDialect.buildRelationalQuery has cognitive complexity 75 (threshold 15). Drivers by points: if/else 18 (37 pts), ternaries 8 (23 pts), loops 5 (12 pts), boolean chains 3 (nesting depth added 41). Of this number, 70 points are the body's own statements and 5 belong to 4 function literals 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.
SeedService.selectGeneratorForPostgresColumn::pickGenerator (cognitive 62) drizzle-seed/src/services/SeedService.ts:507— SeedService.selectGeneratorForPostgresColumn::pickGenerator has cognitive complexity 62 (threshold 15). Drivers by points: if/else 35 (43 pts), boolean chains 14, ternaries 1 (3 pts), loops 1 (2 pts) (nesting depth added 11). 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.
SeedService.generateTablesValues (cognitive 58) drizzle-seed/src/services/SeedService.ts:1142— SeedService.generateTablesValues has cognitive complexity 58 (threshold 15). Drivers by points: if/else 13 (33 pts), loops 5 (13 pts), boolean chains 10, ternaries 2 (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.
MySqlDialect.buildSelectQuery (cognitive 56) drizzle-orm/src/mysql-core/dialect.ts:312— MySqlDialect.buildSelectQuery has cognitive complexity 56 (threshold 15). Drivers by points: ternaries 11 (27 pts), if/else 12 (20 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 25). 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.
SingleStoreDialect.buildSelectQuery (cognitive 56) drizzle-orm/src/singlestore-core/dialect.ts:299— SingleStoreDialect.buildSelectQuery has cognitive complexity 56 (threshold 15). Drivers by points: ternaries 11 (27 pts), if/else 12 (20 pts), boolean chains 6, loops 2 (3 pts) (nesting depth added 25). 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.
SQL.buildQueryFromSourceParams (cognitive 51) drizzle-orm/src/sql/sql.ts:148— SQL.buildQueryFromSourceParams has cognitive complexity 51 (threshold 15). Drivers by points: if/else 24 (34 pts), ternaries 4 (8 pts), boolean chains 7, loops 1 (2 pts) (nesting depth added 15). Most of this is not in the body itself: 2 of the 51 points are its own statements and the rest belongs to one function literal inside it that branches (line 163). 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.
MySqlDialect.buildInsertQuery (cognitive 48) drizzle-orm/src/mysql-core/dialect.ts:561— MySqlDialect.buildInsertQuery has cognitive complexity 48 (threshold 15). Drivers by points: if/else 11 (25 pts), ternaries 4 (14 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 27). 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.
GelDialect.buildInsertQuery (cognitive 43) drizzle-orm/src/gel-core/dialect.ts:508— GelDialect.buildInsertQuery has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 5 (15 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 23). 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.
PgDialect.buildInsertQuery (cognitive 43) drizzle-orm/src/pg-core/dialect.ts:513— PgDialect.buildInsertQuery has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 5 (15 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 23). 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.
relations.extractTablesRelationalConfig (cognitive 43) drizzle-orm/src/relations.ts:416— relations.extractTablesRelationalConfig has cognitive complexity 43 (threshold 15). Drivers by points: if/else 10 (31 pts), loops 4 (11 pts), boolean chains 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.
SeedService.selectGeneratorForMysqlColumn::pickGenerator (cognitive 41) drizzle-seed/src/services/SeedService.ts:801— SeedService.selectGeneratorForMysqlColumn::pickGenerator has cognitive complexity 41 (threshold 15). Drivers by points: if/else 25 (27 pts), boolean chains 11, ternaries 1 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
SQLiteDialect.buildSelection (cognitive 40) drizzle-orm/src/sqlite-core/dialect.ts:178— SQLiteDialect.buildSelection has cognitive complexity 40 (threshold 15). Drivers by points: if/else 17 (29 pts), ternaries 3 (9 pts), boolean chains 2 (nesting depth added 18). None of this is in the body itself: all 40 points belong to 2 function literals inside it that branch (lines 184, 195). 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.
SingleStoreDialect.buildInsertQuery (cognitive 35) drizzle-orm/src/singlestore-core/dialect.ts:519— SingleStoreDialect.buildInsertQuery has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 4 (12 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SeedService.selectGeneratorForSqlite::pickGenerator (cognitive 34) drizzle-seed/src/services/SeedService.ts:997— SeedService.selectGeneratorForSqlite::pickGenerator has cognitive complexity 34 (threshold 15). Drivers by points: boolean chains 18, if/else 12 (13 pts), ternaries 1 (3 pts) (nesting depth added 3). 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.
SeedService.generateColumnsValuesByGenerators (cognitive 33) drizzle-seed/src/services/SeedService.ts:1354— SeedService.generateColumnsValuesByGenerators has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (22 pts), boolean chains 6, loops 3 (4 pts), ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MySqlSelectQueryBuilderBase.createJoin (cognitive 32) drizzle-orm/src/mysql-core/query-builders/select.ts:235— MySqlSelectQueryBuilderBase.createJoin has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (16 pts), ternaries 4 (9 pts), boolean chains 4, match/switch 1 (2 pts), loops 1 (nesting depth added 11). None of this is in the body itself: all 32 points belong to one function literal inside it that branches (line 244). 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.
MySqlDialect.buildSelection (cognitive 32) drizzle-orm/src/mysql-core/dialect.ts:215— MySqlDialect.buildSelection has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 3 (9 pts), boolean chains 2 (nesting depth added 14). None of this is in the body itself: all 32 points belong to 2 function literals inside it that branch (lines 221, 232). 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.
PgDialect.buildSelection (cognitive 32) drizzle-orm/src/pg-core/dialect.ts:211— PgDialect.buildSelection has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 3 (9 pts), boolean chains 2 (nesting depth added 14). None of this is in the body itself: all 32 points belong to 2 function literals inside it that branch (lines 218, 229). 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.
SingleStoreDialect.buildSelection (cognitive 32) drizzle-orm/src/singlestore-core/dialect.ts:214— SingleStoreDialect.buildSelection has cognitive complexity 32 (threshold 15). Drivers by points: if/else 13 (21 pts), ternaries 3 (9 pts), boolean chains 2 (nesting depth added 14). None of this is in the body itself: all 32 points belong to 2 function literals inside it that branch (lines 220, 231). 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.
SQLiteDialect.buildInsertQuery (cognitive 32) drizzle-orm/src/sqlite-core/dialect.ts:510— SQLiteDialect.buildInsertQuery has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (21 pts), loops 2 (5 pts), boolean chains 4, ternaries 2 (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.
MySql2PreparedQuery.execute (cognitive 31) drizzle-orm/src/mysql2/session.ts:92— MySql2PreparedQuery.execute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
PlanetScalePreparedQuery.execute (cognitive 31) drizzle-orm/src/planetscale-serverless/session.ts:49— PlanetScalePreparedQuery.execute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SingleStoreDriverPreparedQuery.execute (cognitive 31) drizzle-orm/src/singlestore/session.ts:93— SingleStoreDriverPreparedQuery.execute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TiDBServerlessPreparedQuery.execute (cognitive 31) drizzle-orm/src/tidb-serverless/session.ts:50— TiDBServerlessPreparedQuery.execute has cognitive complexity 31 (threshold 15). Drivers by points: if/else 6 (21 pts), loops 2 (7 pts), boolean chains 3 (nesting depth added 20). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
GenerateValuesFromArray.init (cognitive 31) drizzle-seed/src/services/Generators.ts:283— GenerateValuesFromArray.init has cognitive complexity 31 (threshold 15). Drivers by points: if/else 10 (18 pts), loops 3 (9 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
schema.handleColumns (cognitive 30) drizzle-arktype/src/schema.ts:14— schema.handleColumns has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 4 (9 pts), boolean chains 5, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GelDialect.buildJoins (cognitive 29) drizzle-orm/src/gel-core/dialect.ts:274— GelDialect.buildJoins has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 6 (16 pts), if/else 6 (9 pts), boolean chains 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PgDialect.buildJoins (cognitive 29) drizzle-orm/src/pg-core/dialect.ts:279— PgDialect.buildJoins has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 6 (16 pts), if/else 6 (9 pts), boolean chains 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
utils.mapResultRow (cognitive 29) drizzle-orm/src/utils.ts:15— utils.mapResultRow has cognitive complexity 29 (threshold 15). Drivers by points: if/else 12 (22 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 11). Most of this is not in the body itself: 8 of the 29 points are its own statements and the rest belongs to one function literal inside it that branches (line 24). 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.
utils.isConfig (cognitive 29) drizzle-orm/src/utils.ts:286— utils.isConfig has cognitive complexity 29 (threshold 15). Drivers by points: if/else 15 (21 pts), boolean chains 8 (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.
SQLiteDialect.buildJoins (cognitive 27) drizzle-orm/src/sqlite-core/dialect.ts:260— SQLiteDialect.buildJoins has cognitive complexity 27 (threshold 15). Drivers by points: if/else 6 (12 pts), ternaries 3 (11 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
index.getPostgresInfo (cognitive 27) drizzle-seed/src/index.ts:571— index.getPostgresInfo has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (18 pts), ternaries 2 (4 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 13). Most of this is not in the body itself: 5 of the 27 points are its own statements and the rest belongs to 4 function items inside it that branch (getTypeParams, a function literal at line 688, getAllBaseColumns, …). 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.
GelDialect.buildSelectQuery (cognitive 26) drizzle-orm/src/gel-core/dialect.ts:336— GelDialect.buildSelectQuery has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 5 (7 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.
GelPreparedQuery.queryWithCache (cognitive 26) drizzle-orm/src/gel-core/session.ts:42— GelPreparedQuery.queryWithCache has cognitive complexity 26 (threshold 15). Drivers by points: error handling 6 (12 pts), if/else 6 (7 pts), boolean chains 4, 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.
MySqlPreparedQuery.queryWithCache (cognitive 26) drizzle-orm/src/mysql-core/session.ts:70— MySqlPreparedQuery.queryWithCache has cognitive complexity 26 (threshold 15). Drivers by points: error handling 6 (12 pts), if/else 6 (7 pts), boolean chains 4, 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.
PgDialect.buildSelectQuery (cognitive 26) drizzle-orm/src/pg-core/dialect.ts:341— PgDialect.buildSelectQuery has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (12 pts), ternaries 5 (7 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.
PgPreparedQuery.queryWithCache (cognitive 26) drizzle-orm/src/pg-core/session.ts:64— PgPreparedQuery.queryWithCache has cognitive complexity 26 (threshold 15). Drivers by points: error handling 6 (12 pts), if/else 6 (7 pts), boolean chains 4, 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.
SingleStorePreparedQuery.queryWithCache (cognitive 26) drizzle-orm/src/singlestore-core/session.ts:68— SingleStorePreparedQuery.queryWithCache has cognitive complexity 26 (threshold 15). Drivers by points: error handling 6 (12 pts), if/else 6 (7 pts), boolean chains 4, 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.
SQLitePreparedQuery.queryWithCache (cognitive 26) drizzle-orm/src/sqlite-core/session.ts:71— SQLitePreparedQuery.queryWithCache has cognitive complexity 26 (threshold 15). Drivers by points: error handling 6 (12 pts), if/else 6 (7 pts), boolean chains 4, 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.
MySql2PreparedQuery.iterator (cognitive 25) drizzle-orm/src/mysql2/session.ts:145— MySql2PreparedQuery.iterator has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 3 (7 pts), boolean chains 3, 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.
SingleStoreDriverPreparedQuery.iterator (cognitive 25) drizzle-orm/src/singlestore/session.ts:144— SingleStoreDriverPreparedQuery.iterator has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 3 (7 pts), boolean chains 3, 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.
GenerateValuesFromArray.checks (cognitive 24) drizzle-seed/src/services/Generators.ts:212— GenerateValuesFromArray.checks has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 17, if/else 7. 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.
GelDialect.buildSelection (cognitive 23) drizzle-orm/src/gel-core/dialect.ts:201— GelDialect.buildSelection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (12 pts), ternaries 3 (9 pts), boolean chains 2 (nesting depth added 10). None of this is in the body itself: all 23 points belong to one function literal inside it that branches (line 209). 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.
GelDialect.buildSetOperationQuery (cognitive 23) drizzle-orm/src/gel-core/dialect.ts:463— GelDialect.buildSetOperationQuery has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (6 pts), boolean chains 3, ternaries 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.
MySqlDialect.buildSetOperationQuery (cognitive 23) drizzle-orm/src/mysql-core/dialect.ts:509— MySqlDialect.buildSetOperationQuery has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (6 pts), boolean chains 3, ternaries 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.
PgDialect.buildSetOperationQuery (cognitive 23) drizzle-orm/src/pg-core/dialect.ts:468— PgDialect.buildSetOperationQuery has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (6 pts), boolean chains 3, ternaries 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.
SingleStoreDialect.buildSetOperationQuery (cognitive 23) drizzle-orm/src/singlestore-core/dialect.ts:467— SingleStoreDialect.buildSetOperationQuery has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (6 pts), boolean chains 3, ternaries 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.
SQLiteDialect.buildSetOperationQuery (cognitive 23) drizzle-orm/src/sqlite-core/dialect.ts:459— SQLiteDialect.buildSetOperationQuery has cognitive complexity 23 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (6 pts), boolean chains 3, ternaries 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.
GelSelectQueryBuilderBase.createJoin (cognitive 22) drizzle-orm/src/gel-core/query-builders/select.ts:222— GelSelectQueryBuilderBase.createJoin has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (7 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 8). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 231). 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.
PgSelectQueryBuilderBase.createJoin (cognitive 22) drizzle-orm/src/pg-core/query-builders/select.ts:229— PgSelectQueryBuilderBase.createJoin has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (7 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 8). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 238). 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.
SQLiteSelectQueryBuilderBase.createJoin (cognitive 22) drizzle-orm/src/sqlite-core/query-builders/select.ts:207— SQLiteSelectQueryBuilderBase.createJoin has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 2 (7 pts), boolean chains 3, match/switch 1 (2 pts), loops 1 (nesting depth added 8). None of this is in the body itself: all 22 points belong to one function literal inside it that branches (line 212). 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.
column.columnToSchema (cognitive 21) drizzle-zod/src/column.ts:70— column.columnToSchema has cognitive complexity 21 (threshold 15). Drivers by points: if/else 18 (19 pts), boolean chains 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.
enum.mysqlEnum (cognitive 20) drizzle-orm/src/mysql-core/columns/enum.ts:110— enum.mysqlEnum has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (9 pts), if/else 4 (6 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.
GeneratePhoneNumber.init (cognitive 20) drizzle-seed/src/services/Generators.ts:1905— GeneratePhoneNumber.init has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (15 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.
SingleStoreSelectQueryBuilderBase.createJoin (cognitive 18) drizzle-orm/src/singlestore-core/query-builders/select.ts:208— SingleStoreSelectQueryBuilderBase.createJoin has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 3, ternaries 1 (3 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 5). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 217). 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.
SQLiteUpdateBase.createJoin (cognitive 18) drizzle-orm/src/sqlite-core/query-builders/update.ts:262— SQLiteUpdateBase.createJoin has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 4 (14 pts), boolean chains 2, if/else 2 (nesting depth added 10). None of this is in the body itself: all 18 points belong to one function literal inside it that branches (line 265). 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.
index.getValueFromDataApi (cognitive 18) drizzle-orm/src/aws-data-api/common/index.ts:5— index.getValueFromDataApi has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (18 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.
driver.drizzle (cognitive 18) drizzle-orm/src/netlify-db/driver.ts:186— driver.drizzle has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, ternaries 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.
SelectionProxyHandler.get (cognitive 18) drizzle-orm/src/selection-proxy.ts:47— SelectionProxyHandler.get has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 2 (3 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.
index.getMySqlInfo (cognitive 18) drizzle-seed/src/index.ts:963— index.getMySqlInfo has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 2 function items inside it that branch (getTypeParams, a function literal at line 1080). 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.
SQLiteDialect.buildSelectQuery (cognitive 17) drizzle-orm/src/sqlite-core/dialect.ts:344— SQLiteDialect.buildSelectQuery has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (7 pts), ternaries 5, loops 2 (3 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.
index.getSqliteInfo (cognitive 17) drizzle-seed/src/index.ts:1285— index.getSqliteInfo has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 8). Most of this is not in the body itself: 5 of the 17 points are its own statements and the rest belongs to 2 function items inside it that branch (getTypeParams, a function literal at line 1400). 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.
ast.resolveMemberExpressionPath (cognitive 17) eslint-plugin-drizzle/src/utils/ast.ts:3— ast.resolveMemberExpressionPath has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 5). Of this number, 16 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
relations.normalizeRelation (cognitive 16) drizzle-orm/src/relations.ts:559— relations.normalizeRelation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 5, ternaries 1 (2 pts), 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.
column.stringColumnToSchema (cognitive 16) drizzle-valibot/src/column.ts:243— column.stringColumnToSchema has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (14 pts), boolean chains 1, ternaries 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.
Cross-context type D1Response (drizzle-kit → drizzle-orm) drizzle-orm/src/d1/session.ts:199— D1Response (context drizzle-kit) is exposed in drizzle-orm's public surface via D1PreparedQuery.run — couples the contexts.
ClassTooLong: SeedService drizzle-seed/src/services/SeedService.ts:22— ClassTooLong — 1030 significant lines (blank, comment-only and punctuation-only lines excluded), 14 methods. The bar is 400 significant lines; this is 630 over it, 2.58× 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.
Change coupling clique: dialect.ts, dialect.ts, dialect.ts drizzle-orm/src/mysql-core/dialect.ts— 3 files — `drizzle-orm/src/mysql-core/dialect.ts`, `drizzle-orm/src/pg-core/dialect.ts`, `drizzle-orm/src/sqlite-core/dialect.ts` — all change together with no explicit dependency: a fully-connected co-change clique, not 3 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
Off the main sequence: drizzle-orm — drizzle-orm: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.
Low cohesion: PgDialect (LCOM4 4) drizzle-orm/src/pg-core/dialect.ts:63— PgDialect's methods fall into 4 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 4 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — drizzle-arktype/ runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
Fake-async — async method never awaits drizzle-orm/src/durable-sqlite/migrator.ts:41— `migrate` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Skeleton type — most members are unfinished REDACTED:43— `PrismaMySqlSession` has 2 unfinished members out of 4 declared members (methods and accessors, whether or not each carries a body) — a scaffolded class that was never implemented.
IC1 · Incompleteness & stubs· Both branches are identical · ×1
Both branches are identical — the condition decides nothing drizzle-seed/src/index.ts:209— 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.
No structured logging — No logging call was found in the 598 JavaScript/TypeScript production file(s) this check read across 10 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
Duplication concentrated across 33 sibling directories (266 clone groups) drizzle-orm/src/gel-core/query-builders/select.ts:60— 266 duplicated blocks under drizzle-orm/src/ have copies in at least two of the sibling directories aws-data-api, better-sqlite3, bun-sql, bun-sqlite, d1, durable-sqlite (+27 more sibling(s) not listed) — 222 of them are reported below, and 44 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 266 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 266 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 266 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 6 sibling directories (32 clone groups) drizzle-typebox/src/column.ts:143— 32 duplicated blocks under the repository root have copies in at least two of the sibling directories drizzle-arktype, drizzle-orm, drizzle-seed, drizzle-typebox, drizzle-valibot, drizzle-zod — 24 of them are reported below, and 8 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 32 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 32 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 32 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (483 matched lines × 2 locations) · ×1
Duplicated block with local edits (483 matched lines × 2 locations) drizzle-orm/src/gel-core/query-builders/select.ts:60— drizzle-orm/src/gel-core/query-builders/select.ts:60 · drizzle-orm/src/pg-core/query-builders/select.ts:62 — the two spans are one implementation copied and then locally edited — 3406 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (466 identical lines × 2 files) drizzle-orm/src/gel-core/dialect.ts:1— drizzle-orm/src/gel-core/dialect.ts:1 · drizzle-orm/src/pg-core/dialect.ts:1 — these 2 files are line-for-line copies of one another — 466 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 (408 matched lines × 2 locations) · ×1
Duplicated block with local edits (408 matched lines × 2 locations) drizzle-orm/src/mysql-core/query-builders/select.ts:70— drizzle-orm/src/mysql-core/query-builders/select.ts:70 · drizzle-orm/src/singlestore-core/query-builders/select.ts:69 — the two spans are one implementation copied and then locally edited — 2910 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 (348 matched lines × 2 locations) · ×1
Duplicated block with local edits (348 matched lines × 2 locations) drizzle-orm/src/singlestore-core/query-builders/select.ts:179— drizzle-orm/src/singlestore-core/query-builders/select.ts:179 · drizzle-orm/src/sqlite-core/query-builders/select.ts:178 — the two spans are one implementation copied and then locally edited — 2502 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 (246 matched lines × 2 locations) · ×1
Duplicated block with local edits (246 matched lines × 2 locations) drizzle-orm/src/mysql-core/dialect.ts:80— drizzle-orm/src/mysql-core/dialect.ts:80 · drizzle-orm/src/singlestore-core/dialect.ts:79 — the two spans are one implementation copied and then locally edited — 1874 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 (204 matched lines × 2 locations) · ×1
Duplicated block with local edits (204 matched lines × 2 locations) drizzle-orm/src/neon-serverless/session.ts:40— drizzle-orm/src/neon-serverless/session.ts:40 · drizzle-orm/src/vercel-postgres/session.ts:39 — the two spans are one implementation copied and then locally edited — 1387 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (179 lines × 2 locations) drizzle-orm/src/gel-core/query-builders/select.types.ts:131— drizzle-orm/src/gel-core/query-builders/select.types.ts:131 · drizzle-orm/src/pg-core/query-builders/select.types.ts:143 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (169 matched lines × 2 locations) · ×1
Duplicated block with local edits (169 matched lines × 2 locations) drizzle-orm/src/mysql-core/db.ts:34— drizzle-orm/src/mysql-core/db.ts:34 · drizzle-orm/src/singlestore-core/db.ts:31 — the two spans are one implementation copied and then locally edited — 1374 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 (166 matched lines × 2 locations) · ×1
Duplicated block with local edits (166 matched lines × 2 locations) drizzle-orm/src/bun-sql/session.ts:32— drizzle-orm/src/bun-sql/session.ts:32 · drizzle-orm/src/postgres-js/session.ts:31 — the two spans are one implementation copied and then locally edited — 1158 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 (161 matched lines × 2 locations) · ×1
Duplicated block with local edits (161 matched lines × 2 locations) drizzle-orm/src/mysql-core/db.ts:40— drizzle-orm/src/mysql-core/db.ts:40 · drizzle-orm/src/sqlite-core/db.ts:38 — the two spans are one implementation copied and then locally edited — 1125 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 (150 matched lines × 2 locations) · ×1
Duplicated block with local edits (150 matched lines × 2 locations) drizzle-orm/src/pg-core/query-builders/delete.ts:30— drizzle-orm/src/pg-core/query-builders/delete.ts:30 · drizzle-orm/src/pg-core/query-builders/insert.ts:137 — the two spans are one implementation copied and then locally edited — 875 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 (147 matched lines × 2 locations) · ×1
Duplicated block with local edits (147 matched lines × 2 locations) drizzle-orm/src/gel-core/db.ts:27— drizzle-orm/src/gel-core/db.ts:27 · drizzle-orm/src/pg-core/db.ts:36 — the two spans are one implementation copied and then locally edited — 1065 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 (141 matched lines × 2 locations) · ×1
Duplicated block with local edits (141 matched lines × 2 locations) drizzle-orm/src/d1/session.ts:23— drizzle-orm/src/d1/session.ts:23 · drizzle-orm/src/libsql/session.ts:22 — the two spans are one implementation copied and then locally edited — 1042 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (141 lines × 2 locations) drizzle-orm/src/mysql-core/query-builders/delete.ts:23— drizzle-orm/src/mysql-core/query-builders/delete.ts:23 · drizzle-orm/src/singlestore-core/query-builders/delete.ts:23 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (138 matched lines × 2 locations) · ×1
Duplicated block with local edits (138 matched lines × 2 locations) drizzle-seed/src/services/Generators.ts:1316— drizzle-seed/src/services/Generators.ts:1316 · drizzle-seed/src/services/versioning/v2.ts:5 — the two spans are one implementation copied and then locally edited — 932 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 (129 matched lines × 2 locations) · ×1
Duplicated block with local edits (129 matched lines × 2 locations) drizzle-orm/src/gel-core/table.ts:13— drizzle-orm/src/gel-core/table.ts:13 · drizzle-orm/src/pg-core/table.ts:13 — the two spans are one implementation copied and then locally edited — 866 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 (120 matched lines × 2 locations) · ×1
Duplicated block with local edits (120 matched lines × 2 locations) drizzle-seed/src/index.ts:758— drizzle-seed/src/index.ts:758 · drizzle-seed/src/index.ts:1120 — the two spans are one implementation copied and then locally edited — 761 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (117 lines × 2 locations) drizzle-orm/src/gel-core/columns/common.ts:135— drizzle-orm/src/gel-core/columns/common.ts:135 · drizzle-orm/src/pg-core/columns/common.ts:136 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (113 lines × 2 locations) drizzle-orm/src/mysql-core/query-builders/select.types.ts:235— drizzle-orm/src/mysql-core/query-builders/select.types.ts:235 · drizzle-orm/src/singlestore-core/query-builders/select.types.ts:220 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (109 matched lines × 2 locations) · ×1
Duplicated block with local edits (109 matched lines × 2 locations) drizzle-orm/src/mysql2/driver.ts:43— drizzle-orm/src/mysql2/driver.ts:43 · drizzle-orm/src/singlestore/driver.ts:44 — the two spans are one implementation copied and then locally edited — 749 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (106 lines × 2 locations) drizzle-typebox/src/column.ts:143— drizzle-typebox/src/column.ts:143 · drizzle-valibot/src/column.ts:128 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (105 matched lines × 2 locations) · ×1
Duplicated block with local edits (105 matched lines × 2 locations) drizzle-orm/src/planetscale-serverless/session.ts:35— drizzle-orm/src/planetscale-serverless/session.ts:35 · drizzle-orm/src/tidb-serverless/session.ts:36 — the two spans are one implementation copied and then locally edited — 717 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (103 lines × 2 locations) drizzle-orm/src/gel-core/view.ts:290— drizzle-orm/src/gel-core/view.ts:290 · drizzle-orm/src/pg-core/view.ts:290 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (99 matched lines × 2 locations) · ×1
Duplicated block with local edits (99 matched lines × 2 locations) drizzle-typebox/src/schema.ts:29— drizzle-typebox/src/schema.ts:29 · drizzle-zod/src/schema.ts:30 — the two spans are one implementation copied and then locally edited — 778 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (98 lines × 4 locations) drizzle-arktype/src/column.ts:128— drizzle-arktype/src/column.ts:128 · drizzle-typebox/src/column.ts:143 · drizzle-valibot/src/column.ts:128 · drizzle-zod/src/column.ts:143 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (96 lines × 2 locations) drizzle-orm/src/mysql2/session.ts:223— drizzle-orm/src/mysql2/session.ts:223 · drizzle-orm/src/singlestore/session.ts:219 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (91 matched lines × 2 locations) · ×1
Duplicated block with local edits (91 matched lines × 2 locations) drizzle-orm/src/durable-sqlite/session.ts:31— drizzle-orm/src/durable-sqlite/session.ts:31 · drizzle-orm/src/expo-sqlite/session.ts:29 — the two spans are one implementation copied and then locally edited — 704 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (90 identical lines × 4 files) drizzle-arktype/scripts/fix-imports.ts:2— drizzle-arktype/scripts/fix-imports.ts:2 · drizzle-typebox/scripts/fix-imports.ts:2 · drizzle-valibot/scripts/fix-imports.ts:2 · drizzle-zod/scripts/fix-imports.ts:2 — these 4 files are line-for-line copies of one another — 90 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 (90 matched lines × 2 locations) · ×1
Duplicated block with local edits (90 matched lines × 2 locations) drizzle-orm/src/sqlite-core/query-builders/delete.ts:59— drizzle-orm/src/sqlite-core/query-builders/delete.ts:59 · drizzle-orm/src/sqlite-core/query-builders/update.ts:125 — the two spans are one implementation copied and then locally edited — 535 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 (89 matched lines × 2 locations) · ×1
Duplicated block with local edits (89 matched lines × 2 locations) drizzle-orm/src/mysql-core/query-builders/query.ts:37— drizzle-orm/src/mysql-core/query-builders/query.ts:37 · drizzle-orm/src/singlestore-core/query-builders/query.ts:35 — the two spans are one implementation copied and then locally edited — 596 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (86 lines × 4 locations) drizzle-orm/src/gel-core/columns/custom.ts:37— drizzle-orm/src/gel-core/columns/custom.ts:37 · drizzle-orm/src/mysql-core/columns/custom.ts:37 · drizzle-orm/src/pg-core/columns/custom.ts:37 · drizzle-orm/src/singlestore-core/columns/custom.ts:38 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
R10 · Code Duplication· Duplicated block with local edits (86 matched lines × 2 locations) · ×1
Duplicated block with local edits (86 matched lines × 2 locations) drizzle-orm/src/pg-core/columns/line.ts:13— drizzle-orm/src/pg-core/columns/line.ts:13 · drizzle-orm/src/pg-core/columns/point.ts:13 — the two spans are one implementation copied and then locally edited — 705 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (85 lines × 4 locations) drizzle-orm/src/gel-core/session.ts:42— drizzle-orm/src/gel-core/session.ts:42 · drizzle-orm/src/mysql-core/session.ts:70 · drizzle-orm/src/singlestore-core/session.ts:68 · drizzle-orm/src/sqlite-core/session.ts:71 — the 4 copies are spread across 4 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 4 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.
Complex function pickGenerator (cyclomatic 60, cognitive 62) drizzle-seed/src/services/SeedService.ts:507— pickGenerator has cyclomatic complexity 60 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function pickGenerator (cyclomatic 57, cognitive 41) drizzle-seed/src/services/SeedService.ts:801— pickGenerator has cyclomatic complexity 57 and cognitive complexity 41; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (top-level) (cyclomatic 55, cognitive 54) drizzle-orm/src/query-builders/select.types.ts:1— (top-level) has cyclomatic complexity 55 and cognitive complexity 54; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generatePossibleGenerators (cyclomatic 52, cognitive 112) drizzle-seed/src/services/SeedService.ts:34— generatePossibleGenerators has cyclomatic complexity 52 and cognitive complexity 112; 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 (top-level) (cyclomatic 44, cognitive 43) drizzle-valibot/src/column.types.ts:1— (top-level) has cyclomatic complexity 44 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function pickGenerator (cyclomatic 37, cognitive 34) drizzle-seed/src/services/SeedService.ts:997— pickGenerator has cyclomatic complexity 37 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildRelationalQueryWithoutLateralSubqueries (cyclomatic 36, cognitive 85) drizzle-orm/src/mysql-core/dialect.ts:1000— buildRelationalQueryWithoutLateralSubqueries has cyclomatic complexity 36 and cognitive complexity 85; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 35, cognitive 49) drizzle-orm/src/sql/sql.ts:163— (anonymous) has cyclomatic complexity 35 and cognitive complexity 49; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 (top-level) (cyclomatic 35, cognitive 34) drizzle-zod/src/column.types.ts:1— (top-level) has cyclomatic complexity 35 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildRelationalQuery (cyclomatic 34, cognitive 79) drizzle-orm/src/sqlite-core/dialect.ts:606— buildRelationalQuery has cyclomatic complexity 34 and cognitive complexity 79; 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 generateTablesValues (cyclomatic 34, cognitive 66) drizzle-seed/src/services/SeedService.ts:1142— generateTablesValues has cyclomatic complexity 34 and cognitive complexity 66; 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 buildSelectQuery (cyclomatic 34, cognitive 65) drizzle-orm/src/mysql-core/dialect.ts:312— buildSelectQuery has cyclomatic complexity 34 and cognitive complexity 65; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 buildSelectQuery (cyclomatic 33, cognitive 62) drizzle-orm/src/singlestore-core/dialect.ts:299— buildSelectQuery has cyclomatic complexity 33 and cognitive complexity 62; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function columnToSchema (cyclomatic 28, cognitive 37) drizzle-zod/src/column.ts:70— columnToSchema has cyclomatic complexity 28 and cognitive complexity 37; 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· drizzle-seed/src/services/Generators.ts · ×1
drizzle-seed/src/services/Generators.ts: 2548 lines of code drizzle-seed/src/services/Generators.ts:1— drizzle-seed/src/services/Generators.ts has 2548 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· drizzle-seed/src/services/SeedService.ts · ×1
drizzle-seed/src/services/SeedService.ts: 1405 lines of code drizzle-seed/src/services/SeedService.ts:1— drizzle-seed/src/services/SeedService.ts has 1405 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· drizzle-orm/type-tests/pg/tables.ts · ×1
drizzle-orm/type-tests/pg/tables.ts: 1371 lines of code drizzle-orm/type-tests/pg/tables.ts:1— drizzle-orm/type-tests/pg/tables.ts has 1371 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
drizzle-seed/src/index.ts: 1335 lines of code drizzle-seed/src/index.ts:1— drizzle-seed/src/index.ts has 1335 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· drizzle-orm/type-tests/pg/select.ts · ×1
drizzle-orm/type-tests/pg/select.ts: 1332 lines of code drizzle-orm/type-tests/pg/select.ts:1— drizzle-orm/type-tests/pg/select.ts has 1332 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· drizzle-orm/src/mysql-core/query-builders/select.ts · ×1
drizzle-orm/src/mysql-core/query-builders/select.ts: 1303 lines of code drizzle-orm/src/mysql-core/query-builders/select.ts:1— drizzle-orm/src/mysql-core/query-builders/select.ts has 1303 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· drizzle-orm/src/pg-core/dialect.ts · ×1
drizzle-orm/src/pg-core/dialect.ts: 1276 lines of code drizzle-orm/src/pg-core/dialect.ts:1— drizzle-orm/src/pg-core/dialect.ts has 1276 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· drizzle-orm/src/pg-core/query-builders/select.ts · ×1
drizzle-orm/src/pg-core/query-builders/select.ts: 1270 lines of code drizzle-orm/src/pg-core/query-builders/select.ts:1— drizzle-orm/src/pg-core/query-builders/select.ts has 1270 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· drizzle-orm/src/gel-core/dialect.ts · ×1
drizzle-orm/src/gel-core/dialect.ts: 1267 lines of code drizzle-orm/src/gel-core/dialect.ts:1— drizzle-orm/src/gel-core/dialect.ts has 1267 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· drizzle-orm/src/gel-core/query-builders/select.ts · ×1
drizzle-orm/src/gel-core/query-builders/select.ts: 1257 lines of code drizzle-orm/src/gel-core/query-builders/select.ts:1— drizzle-orm/src/gel-core/query-builders/select.ts has 1257 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· drizzle-orm/type-tests/geldb/select.ts · ×1
drizzle-orm/type-tests/geldb/select.ts: 1191 lines of code drizzle-orm/type-tests/geldb/select.ts:1— drizzle-orm/type-tests/geldb/select.ts has 1191 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· drizzle-orm/src/mysql-core/dialect.ts · ×1
drizzle-orm/src/mysql-core/dialect.ts: 1190 lines of code drizzle-orm/src/mysql-core/dialect.ts:1— drizzle-orm/src/mysql-core/dialect.ts has 1190 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· drizzle-orm/src/singlestore-core/query-builders/select.ts · ×1
drizzle-orm/src/singlestore-core/query-builders/select.ts: 1120 lines of code drizzle-orm/src/singlestore-core/query-builders/select.ts:1— drizzle-orm/src/singlestore-core/query-builders/select.ts has 1120 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· drizzle-orm/type-tests/mysql/select.ts · ×1
drizzle-orm/type-tests/mysql/select.ts: 1071 lines of code drizzle-orm/type-tests/mysql/select.ts:1— drizzle-orm/type-tests/mysql/select.ts has 1071 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· drizzle-orm/src/sqlite-core/query-builders/select.ts · ×1
drizzle-orm/src/sqlite-core/query-builders/select.ts: 1035 lines of code drizzle-orm/src/sqlite-core/query-builders/select.ts:1— drizzle-orm/src/sqlite-core/query-builders/select.ts has 1035 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· drizzle-orm/type-tests/mysql/tables.ts · ×1
drizzle-orm/type-tests/mysql/tables.ts: 1020 lines of code drizzle-orm/type-tests/mysql/tables.ts:1— drizzle-orm/type-tests/mysql/tables.ts has 1020 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· drizzle-orm/type-tests/singlestore/tables.ts · ×1
drizzle-orm/type-tests/singlestore/tables.ts: 972 lines of code drizzle-orm/type-tests/singlestore/tables.ts:1— drizzle-orm/type-tests/singlestore/tables.ts has 972 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· drizzle-orm/src/sqlite-core/dialect.ts · ×1
drizzle-orm/src/sqlite-core/dialect.ts: 913 lines of code drizzle-orm/src/sqlite-core/dialect.ts:1— drizzle-orm/src/sqlite-core/dialect.ts has 913 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· drizzle-orm/type-tests/singlestore/select.ts · ×1
drizzle-orm/type-tests/singlestore/select.ts: 908 lines of code drizzle-orm/type-tests/singlestore/select.ts:1— drizzle-orm/type-tests/singlestore/select.ts has 908 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· drizzle-orm/type-tests/geldb/tables.ts · ×1
drizzle-orm/type-tests/geldb/tables.ts: 886 lines of code drizzle-orm/type-tests/geldb/tables.ts:1— drizzle-orm/type-tests/geldb/tables.ts has 886 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· drizzle-seed/src/services/GeneratorFuncs.ts · ×1
drizzle-seed/src/services/GeneratorFuncs.ts: 884 lines of code drizzle-seed/src/services/GeneratorFuncs.ts:1— drizzle-seed/src/services/GeneratorFuncs.ts has 884 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· drizzle-orm/src/singlestore-core/dialect.ts · ×1
drizzle-orm/src/singlestore-core/dialect.ts: 834 lines of code drizzle-orm/src/singlestore-core/dialect.ts:1— drizzle-orm/src/singlestore-core/dialect.ts has 834 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· drizzle-orm/type-tests/sqlite/select.ts · ×1
drizzle-orm/type-tests/sqlite/select.ts: 771 lines of code drizzle-orm/type-tests/sqlite/select.ts:1— drizzle-orm/type-tests/sqlite/select.ts has 771 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· drizzle-orm/src/sql/expressions/conditions.ts · ×1
drizzle-orm/src/sql/expressions/conditions.ts: 703 lines of code drizzle-orm/src/sql/expressions/conditions.ts:1— drizzle-orm/src/sql/expressions/conditions.ts has 703 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· drizzle-orm/src/relations.ts · ×1
drizzle-orm/src/relations.ts: 667 lines of code drizzle-orm/src/relations.ts:1— drizzle-orm/src/relations.ts has 667 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· drizzle-orm/src/pg-core/db.ts · ×1
drizzle-orm/src/pg-core/db.ts: 665 lines of code drizzle-orm/src/pg-core/db.ts:1— drizzle-orm/src/pg-core/db.ts has 665 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· drizzle-orm/src/gel-core/db.ts · ×1
drizzle-orm/src/gel-core/db.ts: 644 lines of code drizzle-orm/src/gel-core/db.ts:1— drizzle-orm/src/gel-core/db.ts has 644 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· drizzle-orm/src/sqlite-core/db.ts · ×1
drizzle-orm/src/sqlite-core/db.ts: 620 lines of code drizzle-orm/src/sqlite-core/db.ts:1— drizzle-orm/src/sqlite-core/db.ts has 620 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
drizzle-orm/src/sql/sql.ts: 611 lines of code drizzle-orm/src/sql/sql.ts:1— drizzle-orm/src/sql/sql.ts has 611 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· drizzle-orm/src/pg-core/query-builders/update.ts · ×1
drizzle-orm/src/pg-core/query-builders/update.ts: 575 lines of code drizzle-orm/src/pg-core/query-builders/update.ts:1— drizzle-orm/src/pg-core/query-builders/update.ts has 575 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· drizzle-orm/type-tests/sqlite/tables.ts · ×1
drizzle-orm/type-tests/sqlite/tables.ts: 535 lines of code drizzle-orm/type-tests/sqlite/tables.ts:1— drizzle-orm/type-tests/sqlite/tables.ts has 535 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· drizzle-orm/src/gel-core/query-builders/update.ts · ×1
drizzle-orm/src/gel-core/query-builders/update.ts: 513 lines of code drizzle-orm/src/gel-core/query-builders/update.ts:1— drizzle-orm/src/gel-core/query-builders/update.ts has 513 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· drizzle-orm/src/mysql-core/db.ts · ×1
drizzle-orm/src/mysql-core/db.ts: 512 lines of code drizzle-orm/src/mysql-core/db.ts:1— drizzle-orm/src/mysql-core/db.ts has 512 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· drizzle-orm/src/singlestore-core/db.ts · ×1
drizzle-orm/src/singlestore-core/db.ts: 505 lines of code drizzle-orm/src/singlestore-core/db.ts:1— drizzle-orm/src/singlestore-core/db.ts has 505 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· drizzle-orm/src/sqlite-core/query-builders/select.types.ts · ×1
drizzle-orm/src/sqlite-core/query-builders/select.types.ts: 438 lines of code drizzle-orm/src/sqlite-core/query-builders/select.types.ts:1— drizzle-orm/src/sqlite-core/query-builders/select.types.ts has 438 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· drizzle-orm/src/singlestore-core/query-builders/select.types.ts · ×1
drizzle-orm/src/singlestore-core/query-builders/select.types.ts: 437 lines of code drizzle-orm/src/singlestore-core/query-builders/select.types.ts:1— drizzle-orm/src/singlestore-core/query-builders/select.types.ts has 437 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· drizzle-orm/src/mysql-core/query-builders/select.types.ts · ×1
drizzle-orm/src/mysql-core/query-builders/select.types.ts: 426 lines of code drizzle-orm/src/mysql-core/query-builders/select.types.ts:1— drizzle-orm/src/mysql-core/query-builders/select.types.ts has 426 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· drizzle-orm/src/sqlite-core/query-builders/update.ts · ×1
drizzle-orm/src/sqlite-core/query-builders/update.ts: 420 lines of code drizzle-orm/src/sqlite-core/query-builders/update.ts:1— drizzle-orm/src/sqlite-core/query-builders/update.ts has 420 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· drizzle-orm/src/pg-core/query-builders/insert.ts · ×1
drizzle-orm/src/pg-core/query-builders/insert.ts: 415 lines of code drizzle-orm/src/pg-core/query-builders/insert.ts:1— drizzle-orm/src/pg-core/query-builders/insert.ts has 415 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· drizzle-orm/src/pg-core/query-builders/select.types.ts · ×1
drizzle-orm/src/pg-core/query-builders/select.types.ts: 404 lines of code drizzle-orm/src/pg-core/query-builders/select.types.ts:1— drizzle-orm/src/pg-core/query-builders/select.types.ts has 404 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Unused dependency '@arethetypeswrong/cli' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'drizzle-orm-old' — Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Unused dependency 'resolve-tspaths' — 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.
Mock-dominated test: default global config - no cache should be hit integration-tests/tests/sqlite/sqlite-common-cache.ts:142— This test sets up 3 test doubles (for example `vi.spyOn`) 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: default global config + enable cache on select: get, put integration-tests/tests/sqlite/sqlite-common-cache.ts:159— This test sets up 3 test doubles (for example `vi.spyOn`) 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: default global config + enable cache on select + write: get, put, onMutate integration-tests/tests/sqlite/sqlite-common-cache.ts:176— This test sets up 3 test doubles (for example `vi.spyOn`) 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: default global config + enable cache on select + disable invalidate: get, put integration-tests/tests/sqlite/sqlite-common-cache.ts:203— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true + disable cache integration-tests/tests/sqlite/sqlite-common-cache.ts:225— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true - cache should be hit integration-tests/tests/sqlite/sqlite-common-cache.ts:242— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true - cache: false on select - no cache hit integration-tests/tests/sqlite/sqlite-common-cache.ts:259— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true - disable invalidate - cache hit + no invalidate integration-tests/tests/sqlite/sqlite-common-cache.ts:276— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true - with custom tag integration-tests/tests/sqlite/sqlite-common-cache.ts:303— This test sets up 3 test doubles (for example `vi.spyOn`) 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: default global config - no cache should be hit integration-tests/tests/singlestore/singlestore-cache.ts:151— This test sets up 3 test doubles (for example `vi.spyOn`) 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: default global config + enable cache on select: get, put integration-tests/tests/singlestore/singlestore-cache.ts:168— This test sets up 3 test doubles (for example `vi.spyOn`) 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: default global config + enable cache on select + write: get, put, onMutate integration-tests/tests/singlestore/singlestore-cache.ts:185— This test sets up 3 test doubles (for example `vi.spyOn`) 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: default global config + enable cache on select + disable invalidate: get, put integration-tests/tests/singlestore/singlestore-cache.ts:212— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true + disable cache integration-tests/tests/singlestore/singlestore-cache.ts:234— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true - cache should be hit integration-tests/tests/singlestore/singlestore-cache.ts:251— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true - cache: false on select - no cache hit integration-tests/tests/singlestore/singlestore-cache.ts:268— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true - disable invalidate - cache hit + no invalidate integration-tests/tests/singlestore/singlestore-cache.ts:285— This test sets up 3 test doubles (for example `vi.spyOn`) 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: global: true - with custom tag integration-tests/tests/singlestore/singlestore-cache.ts:312— This test sets up 3 test doubles (for example `vi.spyOn`) 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: primary with integration-tests/tests/replicas/mysql.test.ts:252— This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: random replica with integration-tests/tests/replicas/mysql.test.ts:275— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: always first read with integration-tests/tests/replicas/mysql.test.ts:338— This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 7 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: primary findFirst integration-tests/tests/replicas/mysql.test.ts:560— This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: always first read findFirst integration-tests/tests/replicas/mysql.test.ts:646— This test sets up 3 test doubles (for example `vi.spyOn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: primary $count integration-tests/tests/replicas/mysql.test.ts:808— This test sets up 3 test doubles (for example `vi.spyOn`) 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: random replica $count integration-tests/tests/replicas/mysql.test.ts:826— This test sets up 4 test doubles (for example `vi.fn`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Orphaned file drizzle-zod/src/column.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 drizzle-typebox/src/column.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 drizzle-arktype/src/column.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 drizzle-valibot/src/column.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 drizzle-orm/type-tests/pg/set-operators.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 drizzle-orm/type-tests/sqlite/set-operators.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 drizzle-orm/type-tests/mysql/set-operators.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 drizzle-orm/type-tests/pg/with.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 drizzle-valibot/src/column.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 drizzle-seed/src/services/versioning/v2.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 drizzle-orm/src/pg-proxy/session.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 drizzle-zod/src/schema.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 drizzle-typebox/src/schema.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 drizzle-zod/src/column.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 drizzle-zod/scripts/fix-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.
Orphaned file drizzle-valibot/scripts/fix-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.
Orphaned file drizzle-typebox/scripts/fix-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.
Orphaned file drizzle-arktype/scripts/fix-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.
Orphaned file drizzle-orm/src/sql/functions/aggregate.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 drizzle-orm/type-tests/pg/generated-columns.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 drizzle-typebox/src/column.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 drizzle-arktype/src/schema.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 drizzle-valibot/src/schema.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 drizzle-valibot/src/schema.types.internal.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 drizzle-orm/type-tests/mysql/generated-columns.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.
Duplicated predicate drizzle-orm/src/gel-core/dialect.ts:543— `!col.default && col.onUpdateFn !== undefined` appears character-identically in 5 files — drizzle-orm/src/gel-core/dialect.ts, drizzle-orm/src/mysql-core/dialect.ts, drizzle-orm/src/pg-core/dialect.ts, drizzle-orm/src/singlestore-core/dialect.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 drizzle-arktype/src/schema.ts:83— `!column.notNull || (column.notNull && column.hasDefault)` appears character-identically in 4 files — drizzle-arktype/src/schema.ts, drizzle-typebox/src/schema.ts, drizzle-valibot/src/schema.ts, drizzle-zod/src/schema.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 drizzle-orm/src/pg-core/columns/line.ts:113— `!config?.mode || config.mode === 'tuple'` appears character-identically in 3 files — drizzle-orm/src/pg-core/columns/line.ts, drizzle-orm/src/pg-core/columns/point.ts, drizzle-orm/src/pg-core/columns/postgis_extension/geometry.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 drizzle-kit/src/introspect-gel.ts:380— `!fields.createDb && !fields.createRole && fields.inherit` appears character-identically in 2 files — drizzle-kit/src/introspect-gel.ts, drizzle-kit/src/introspect-pg.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 drizzle-orm/src/gel-core/query-builders/insert.ts:122— `!is(select, SQL) && !haveSameKeys(this.table[Columns], select._.selectedFields)` appears character-identically in 4 files — drizzle-orm/src/gel-core/query-builders/insert.ts, drizzle-orm/src/mysql-core/query-builders/insert.ts, drizzle-orm/src/pg-core/query-builders/insert.ts, drizzle-orm/src/sqlite-core/query-builders/insert.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 drizzle-arktype/src/schema.ts:22— `!is(selected, Column) && !is(selected, SQL) && !is(selected, SQL.Aliased) && typeof selected === 'object'` appears character-identically in 4 files — drizzle-arktype/src/schema.ts, drizzle-typebox/src/schema.ts, drizzle-valibot/src/schema.ts, drizzle-zod/src/schema.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 drizzle-orm/src/mysql-core/dialect.ts:82— `!lastDbMigration || Number(lastDbMigration.created_at) < migration.folderMillis` appears character-identically in 7 files — drizzle-orm/src/mysql-core/dialect.ts, drizzle-orm/src/mysql-proxy/migrator.ts, drizzle-orm/src/neon-http/migrator.ts, drizzle-orm/src/pg-core/dialect.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 drizzle-orm/src/d1/migrator.ts:31— `!lastDbMigration || Number(lastDbMigration[2])! < migration.folderMillis` appears character-identically in 5 files — drizzle-orm/src/d1/migrator.ts, drizzle-orm/src/durable-sqlite/migrator.ts, drizzle-orm/src/libsql/migrator.ts, drizzle-orm/src/sqlite-core/dialect.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 drizzle-orm/src/aws-data-api/pg/session.ts:104— `!this.fields && !this.customResultMapper` appears character-identically in 5 files — drizzle-orm/src/aws-data-api/pg/session.ts, drizzle-orm/src/d1/session.ts, drizzle-orm/src/libsql/session.ts, drizzle-orm/src/neon-http/session.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 drizzle-arktype/src/utils.ts:11— `'enumValues' in column && Array.isArray(column.enumValues) && column.enumValues.length > 0` appears character-identically in 4 files — drizzle-arktype/src/utils.ts, drizzle-typebox/src/utils.ts, drizzle-valibot/src/utils.ts, drizzle-zod/src/utils.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 drizzle-kit/src/cli/validations/gel.ts:62— `'host' in options || 'database' in options` appears character-identically in 2 files — drizzle-kit/src/cli/validations/gel.ts, drizzle-kit/src/cli/validations/postgres.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 drizzle-orm/src/gel-core/session.ts:66— `( this.queryMetadata.type === 'insert' || this.queryMetadata.type === 'update' || this.queryMetadata.type === 'delete' ) && this.queryMetada…` appears character-identically in 5 files — drizzle-orm/src/gel-core/session.ts, drizzle-orm/src/mysql-core/session.ts, drizzle-orm/src/pg-core/session.ts, drizzle-orm/src/singlestore-core/session.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 drizzle-kit/src/introspect-gel.ts:416— `Object.keys(table.indexes).length > 0 || Object.values(table.foreignKeys).length > 0 || Object.values(table.policies).length > 0 || Object.k…` appears character-identically in 2 files — drizzle-kit/src/introspect-gel.ts, drizzle-kit/src/introspect-pg.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 drizzle-orm/src/gel-core/query-builders/select.ts:247— `Object.keys(this.joinsNotNullableMap).length === 1 && typeof baseTableName === 'string'` appears character-identically in 5 files — drizzle-orm/src/gel-core/query-builders/select.ts, drizzle-orm/src/mysql-core/query-builders/select.ts, drizzle-orm/src/pg-core/query-builders/select.ts, drizzle-orm/src/singlestore-core/query-builders/select.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 drizzle-orm/src/gel-core/session.ts:33— `cache && cache.strategy() === 'all' && cacheConfig === undefined` appears character-identically in 5 files — drizzle-orm/src/gel-core/session.ts, drizzle-orm/src/mysql-core/session.ts, drizzle-orm/src/pg-core/session.ts, drizzle-orm/src/singlestore-core/session.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 drizzle-orm/src/gel-core/dialect.ts:536— `colValue === undefined || (is(colValue, Param) && colValue.value === undefined)` appears character-identically in 5 files — drizzle-orm/src/gel-core/dialect.ts, drizzle-orm/src/mysql-core/dialect.ts, drizzle-orm/src/pg-core/dialect.ts, drizzle-orm/src/singlestore-core/dialect.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 drizzle-kit/src/serializer/gelSerializer.ts:1581— `column.data_type === 'json' || column.data_type === 'jsonb'` appears character-identically in 2 files — drizzle-kit/src/serializer/gelSerializer.ts, drizzle-kit/src/serializer/pgSerializer.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 drizzle-kit/src/cli/commands/mysqlUp.ts:21— `column.default.startsWith("'") && column.default.endsWith("'")` appears character-identically in 2 files — drizzle-kit/src/cli/commands/mysqlUp.ts, drizzle-kit/src/cli/commands/pgUp.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 drizzle-orm/src/mysql-proxy/session.ts:154— `column.field.primary && column.field.autoIncrement` appears character-identically in 6 files — drizzle-orm/src/mysql-proxy/session.ts, drizzle-orm/src/mysql2/session.ts, drizzle-orm/src/planetscale-serverless/session.ts, drizzle-orm/src/singlestore-proxy/session.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 drizzle-arktype/src/schema.ts:82— `column?.generated?.type === 'always' || column?.generatedIdentity?.type === 'always'` appears character-identically in 4 files — drizzle-arktype/src/schema.ts, drizzle-typebox/src/schema.ts, drizzle-valibot/src/schema.ts, drizzle-zod/src/schema.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 drizzle-kit/src/serializer/gelSerializer.ts:1587— `columnDefaultAsString.startsWith("'") && columnDefaultAsString.endsWith("'")` appears character-identically in 2 files — drizzle-kit/src/serializer/gelSerializer.ts, drizzle-kit/src/serializer/pgSerializer.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 drizzle-kit/src/serializer/mysqlSerializer.ts:649— `columnType === 'bigint unsigned' && !isNullable && isAutoincrement` appears character-identically in 2 files — drizzle-kit/src/serializer/mysqlSerializer.ts, drizzle-kit/src/serializer/singlestoreSerializer.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 drizzle-kit/src/serializer/mysqlSerializer.ts:668— `columnType.startsWith('timestamp') && typeof columnExtra !== 'undefined' && columnExtra.includes('on update CURRENT_TIMESTAMP')` appears character-identically in 2 files — drizzle-kit/src/serializer/mysqlSerializer.ts, drizzle-kit/src/serializer/singlestoreSerializer.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 drizzle-orm/src/pg-core/query-builders/insert.ts:372— `config.where && (config.targetWhere || config.setWhere)` appears character-identically in 2 files — drizzle-orm/src/pg-core/query-builders/insert.ts, drizzle-orm/src/sqlite-core/query-builders/insert.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 drizzle-kit/src/cli/commands/libSqlPushUtils.ts:276— `count > 0 && columnConf.notNull && !columnConf.default` appears character-identically in 3 files — drizzle-kit/src/cli/commands/libSqlPushUtils.ts, drizzle-kit/src/cli/commands/singlestorePushUtils.ts, drizzle-kit/src/cli/commands/sqlitePushUtils.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.
Deprecated: @esbuild-kit/core-utils REDACTED:1608— @esbuild-kit/core-utils 3.3.2 is resolved in REDACTED and is marked deprecated by its publisher: "Merged into tsx: https://tsx.hirok.io". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/config-array REDACTED:2464— @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:2473— @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @miniflare/core REDACTED:2628— @miniflare/core 2.14.4 is resolved in REDACTED and is marked deprecated by its publisher: "Miniflare v2 is no longer supported. Please upgrade to Miniflare v4". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @miniflare/queues REDACTED:2638— @miniflare/queues 2.14.4 is resolved in REDACTED and is marked deprecated by its publisher: "Miniflare v2 is no longer supported. Please upgrade to Miniflare v4". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @miniflare/watcher REDACTED:2648— @miniflare/watcher 2.14.4 is resolved in REDACTED and is marked deprecated by its publisher: "Miniflare v2 is no longer supported. Please upgrade to Miniflare v4". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @npmcli/move-file REDACTED:2699— @npmcli/move-file 1.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "This functionality has been moved to @npmcli/fs". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @xmldom/xmldom REDACTED:3591— @xmldom/xmldom 0.8.10 is resolved in REDACTED and is marked deprecated by its publisher: "this version has critical issues, please update to the latest version". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: are-we-there-yet REDACTED:3713— are-we-there-yet 3.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: aws-sdk REDACTED:3817— aws-sdk 2.1692.0 is resolved in REDACTED and is marked deprecated by its publisher: "The AWS SDK for JavaScript (v2) has reached end-of-support, and no longer receives updates. Please migrate your code to use AWS SDK for JavaScript (v3). More info https://a.co/cUPnyil". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: gauge REDACTED:5355— gauge 4.0.4 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:5442— glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:5650— inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: node-domexception REDACTED:6593— node-domexception 1.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native DOMException instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: npmlog REDACTED:6656— npmlog 6.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: prebuild-install REDACTED:7097— prebuild-install 7.1.3 is resolved in REDACTED and is marked deprecated by its publisher: "No longer maintained. Please contact the author of the relevant native addon; alternatives are available.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: querystring REDACTED:7197— querystring 0.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "The querystring API is considered Legacy. new code should use the URLSearchParams API instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: rimraf REDACTED:7390— rimraf 3.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map REDACTED:7631— source-map 0.8.0-beta.0 is resolved in REDACTED and is marked deprecated by its publisher: "The work that was done in this beta branch won't be included in future versions". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: tar REDACTED:7881— tar 6.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: tar REDACTED:7886— tar 7.4.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of tar are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Disabled test integration-tests/tests/bun/bun-sql.test.ts:1963— 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 integration-tests/tests/bun/bun-sql.test.ts:2477— 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 integration-tests/tests/bun/bun-sql.test.ts:2977— 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 integration-tests/tests/bun/bun-sql.test.ts:3608— 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 integration-tests/tests/bun/bun-sql.test.ts:4401— 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 integration-tests/tests/bun/sqlite.test.ts:48— 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 integration-tests/tests/gel/gel.test.ts:1209— 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 integration-tests/tests/pg/awsdatapi.test.ts:1383— 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 integration-tests/tests/pg/neon-http.test.ts:368— 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 integration-tests/tests/pg/neon-serverless.test.ts:376— 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 integration-tests/tests/pg/netlify-db.test.ts:362— 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 integration-tests/tests/pg/rls/rls.definition.test.ts:5— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Disabled test integration-tests/tests/relational/bettersqlite.test.ts:1959— 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 integration-tests/tests/relational/bettersqlite.test.ts:3235— 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 integration-tests/tests/relational/turso.test.ts:465— 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 integration-tests/tests/relational/turso.test.ts:1984— 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 integration-tests/tests/relational/turso.test.ts:3260— 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 integration-tests/tests/singlestore/singlestore-common.ts:3404— 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 integration-tests/tests/sqlite/sqlite-proxy-batch.test.ts:501— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
Outdated (npm): prisma drizzle-orm/package.json:160— prisma is pinned at 5.14.0; registry.npmjs.org publishes 8.0.0-rc.27 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): uuid REDACTED:110— uuid is pinned at 9.0.1; registry.npmjs.org publishes 14.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
R7 · Dead Code· Unused module-local declaration 'ENABLE_LOGGING' · ×2
Unused module-local declaration 'ENABLE_LOGGING' integration-tests/tests/mysql/mysql-common.ts:96— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
Unused module-local declaration 'ENABLE_LOGGING' integration-tests/tests/singlestore/singlestore-common.ts:89— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
Fat interface: DialectSuite (17 required operations) drizzle-kit/tests/push/common.ts:3— `DialectSuite` declares 17 required operations: `allTypes`, `addBasicIndexes`, `changeIndexFields`, `dropIndex`, `indexesToBeNotTriggered`, `indexesTestCase1`, `addNotNull`, `addNotNullWithDataNoRollback`, `addBasicSequences`, `addGeneratedColumn`, `addGeneratedToColumn`, `dropGeneratedConstraint`, `alterGeneratedConstraint`, `createTableWithGeneratedConstraint`, `createCompositePrimaryKey`, `renameTableWithCompositePrimaryKey`, `case1`. 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 1 significant file(s) lose their only recent owner: drizzle-seed/src/services/SeedService.ts. Pair on, review, or document these before any departure.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (2 single-owned of 274 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; 274 of the 618 production source files in this repository met that bar). They are anonymized user #2 (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: drizzle-orm/src/singlestore-core/columns/vector.ts.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 1 of 8 project(s) overshoot their size bounds, lowering Project Cohesion to 7.5/10. The most over is `drizzle-orm` (74121 LoC, 1362 module-visible types across 72 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
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 31 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: drizzle-zod/src/column.ts, drizzle-typebox/src/column.ts, drizzle-arktype/src/column.ts, drizzle-valibot/src/column.ts, drizzle-orm/type-tests/pg/set-operators.ts, drizzle-orm/type-tests/mysql/set-operators.ts, drizzle-orm/type-tests/sqlite/set-operators.ts, drizzle-orm/type-tests/pg/with.ts (and 23 more) (33 orphaned of 274 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; 274 of the 618 production source files in this repository met that bar). 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.
GD1 · Unfinished & placeholder code· Placeholder literal left in code · ×1
Placeholder literal left in code drizzle-seed/src/services/Generators.ts:2788— A placeholder string ("You can't use lorem ipsum generator with…") is still in shipped code — typical of generated boilerplate that was never filled in.
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body drizzle-orm/src/xata-http/driver.ts:38— `initMappers` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Blanket warning suppression eslint/eslint-plugin-drizzle-internal/index.js:1— A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No release approval gate — The release is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever the release trigger points at is published to users unreviewed, so a mistagged or unverified commit ships and the only remedy is a follow-up release.
R7 · Dead Code· Unused export 'GenerateTimestampInt' · ×1
Unused export 'GenerateTimestampInt' drizzle-seed/src/services/Generators.ts:944— Nothing imports this binding — it is safe to review for removal.
R7 · Dead Code· Unused export 'createSchemaFactory' · ×1
Unused export 'createSchemaFactory' drizzle-typebox/src/schema.ts:115— Nothing ultimately consumes this binding: its only referrer is the re-export in drizzle-typebox/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in drizzle-typebox/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
Unused export 'RemoveNever' drizzle-valibot/src/utils.ts:31— Nothing ultimately consumes this binding: its only referrer is the re-export in drizzle-valibot/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in drizzle-valibot/src/index.ts in the same commit, or the barrel will import a name that no longer exists.
R7 · Dead Code· Unused module-local declaration 'isGelView' · ×1
Unused module-local declaration 'isGelView' drizzle-orm/src/gel-core/view.ts:433— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration 'isGelMaterializedView' · ×1
Unused module-local declaration 'isGelMaterializedView' drizzle-orm/src/gel-core/view.ts:437— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R7 · Dead Code· Unused module-local declaration '__' · ×1
Unused module-local declaration '__' drizzle-orm/src/utils.ts:284— This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it.
R8 · Dependency Hygiene· Test-only dependency '@drizzle-team/brocli' in production deps · ×1
Test-only dependency '@drizzle-team/brocli' in production deps REDACTED:46— Only test files import it (first: drizzle-kit/tests/cli-export.test.ts:1) — move it to devDependencies.
Null assertions (`!`) reduce the strict null checking score — ~2.2 `!` null assertions per 1k TypeScript source lines — 455 assertion(s) across the 205053 source line(s) of the 520 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: drizzle-seed/src/services/SeedService.ts (92), drizzle-seed/src/services/Generators.ts (65), drizzle-seed/src/index.ts (25). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Silent fallback default in catch drizzle-kit/src/cli/utils.ts:109— `ormCoreVersions` 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.
Outdated (npm): @aws-sdk/client-rds-data — @aws-sdk/client-rds-data is pinned at 3.817.0; registry.npmjs.org publishes 3.1156.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @aws-sdk/credential-providers — @aws-sdk/credential-providers is pinned at 3.817.0; registry.npmjs.org publishes 3.1156.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @drizzle-team/brocli — @drizzle-team/brocli is pinned at 0.10.2; registry.npmjs.org publishes 0.12.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @electric-sql/pglite — @electric-sql/pglite is pinned at 0.2.12; registry.npmjs.org publishes 0.5.12 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @libsql/client — @libsql/client is pinned at 0.10.0; registry.npmjs.org publishes 0.18.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @planetscale/database — @planetscale/database is pinned at 1.19.0; registry.npmjs.org publishes 2.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @prisma/client — @prisma/client is pinned at 5.14.0; registry.npmjs.org publishes 7.10.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @tidbcloud/serverless — @tidbcloud/serverless is pinned at 0.1.1; registry.npmjs.org publishes 0.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @typescript/analyze-trace — @typescript/analyze-trace is pinned at 0.10.1; registry.npmjs.org publishes 0.11.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @vercel/postgres — @vercel/postgres is pinned at 0.8.0; registry.npmjs.org publishes 0.10.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @xata.io/client — @xata.io/client is pinned at 0.29.5; registry.npmjs.org publishes 0.30.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): better-sqlite3 — better-sqlite3 is pinned at 11.9.1; registry.npmjs.org publishes 13.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dockerode — dockerode is pinned at 4.0.6; registry.npmjs.org publishes 5.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): dotenv — dotenv is pinned at 16.5.0; registry.npmjs.org publishes 18.0.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): esbuild — esbuild is pinned at 0.25.5; registry.npmjs.org publishes 0.28.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): gel — gel is pinned at 2.1.0; registry.npmjs.org publishes 2.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): get-port — get-port is pinned at 7.1.0; registry.npmjs.org publishes 7.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): mysql2 — mysql2 is pinned at 3.14.1; registry.npmjs.org publishes 3.24.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): pg — pg is pinned at 8.16.0; registry.npmjs.org publishes 8.23.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): postgres — postgres is pinned at 3.4.7; registry.npmjs.org publishes 3.4.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): pure-rand — pure-rand is pinned at 6.1.0; registry.npmjs.org publishes 8.4.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): sql.js — sql.js is pinned at 1.13.0; registry.npmjs.org publishes 1.15.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): sqlite3 — sqlite3 is pinned at 5.1.7; registry.npmjs.org publishes 6.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): sst — sst is pinned at 3.17.0; registry.npmjs.org publishes 4.17.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): tsx — tsx is pinned at 4.21.0; registry.npmjs.org publishes 4.23.15 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Skipped (documented): build query insert with onConflict do update integration-tests/tests/gel/gel.test.ts:1630— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): build query insert with onConflict do update / multiple columns integration-tests/tests/gel/gel.test.ts:1647— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): build query insert with onConflict do nothing integration-tests/tests/gel/gel.test.ts:1664— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): build query insert with onConflict do nothing + target integration-tests/tests/gel/gel.test.ts:1681— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): insert with onConflict do update integration-tests/tests/gel/gel.test.ts:1698— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): insert with onConflict do nothing integration-tests/tests/gel/gel.test.ts:1716— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): insert with onConflict do nothing + target integration-tests/tests/gel/gel.test.ts:1731— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): having integration-tests/tests/gel/gel.test.ts:2337— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): mySchema :: build query insert with onConflict do update / multiple columns integration-tests/tests/gel/gel.test.ts:4075— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): mySchema :: build query insert with onConflict do nothing + target integration-tests/tests/gel/gel.test.ts:4092— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): update ... from integration-tests/tests/gel/gel.test.ts:4470— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): update ... from with alias integration-tests/tests/gel/gel.test.ts:4504— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): insert multiple rows into table with generated identity column integration-tests/tests/gel/gel.test.ts:5007— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): set json/jsonb fields with objects and retrieve with the ->> operator integration-tests/tests/bun/bun-sql.test.ts:4435— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): set json/jsonb fields with strings and retrieve with the ->> operator integration-tests/tests/bun/bun-sql.test.ts:4459— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): set json/jsonb fields with objects and retrieve with the -> operator integration-tests/tests/bun/bun-sql.test.ts:4483— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): set json/jsonb fields with strings and retrieve with the -> operator integration-tests/tests/bun/bun-sql.test.ts:4507— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Skipped (documented): basic policy with CURRENT_USER role drizzle-kit/tests/introspect/pg.test.ts:736— Skipped with a documented reason — a deferral, not lazy debt: declared with test.todo — a placeholder that registers a name and runs nothing
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 31 file(s) — `drizzle-arktype/benchmarks/types.ts`, `drizzle-arktype/src/column.ts`, `drizzle-arktype/src/column.types.ts`, `drizzle-arktype/src/schema.ts`, `drizzle-arktype/src/schema.types.internal.ts`, … (+26 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a17984-8717-7d3e-b8c4-0c6dc2854da4 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 112 · Warnings: 596 · Recommendations: 206 · Info: 46 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 26-10-2026 @ 18:41 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.