Public report of reimagined/resolve, published 22 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, 22 October 2026, 15:04 UTC · Survey ID cd_2d46d2ba187642c588ecc3cf88e827fb
reimagined/resolve
Measured 22 October 2026, 14:59 UTC, at code version c4b4c05
Bus factor is not measured: No living knowledge left to concentrate.
CAI scoreAt riskDown 5 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 medium codebase: 76,280 lines of product code in 52 projects, tests not counted · Estimated rebuild effort: about 0.7 person-years · Weakest lens: Production Readiness, 33
Findings by how serious they are
221 critical724 serious544 minor
8 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
22 October 2026, 14:59 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 ▸
79of 83 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
1361of 1489 findings point to an exact file and line, so you can open each one in the code. The other 128 concern the repository as a whole, such as missing documentation.
83dimensions across 7 lenses, read from 76,280 lines of product code in 52 projects.
reimagined/resolve scores 40 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged. The project hasn't declared a stable release yet, so its lenses are rated against a lower bar than a released product's, while the score itself is worked out as for any repository.
The weakest lens counts most in the score, and here that is Production Readiness, which scores 33 and is rated Weak. Its Dependency Hygiene dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 2 Leaked secret finding(s) in Secret Scanning and to resolve the 78 Deprecated finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 40 to about 47.
221 findings are critical: 115 in Static Analysis (SAST), 95 in Dependency Vulnerabilities, five in Circular Imports, two in Secret Scanning, two in Test Quality, one in Secrets (history) and one in Test Reliability.
Watchdog couldn't measure 7 dimensions in this code, among them Navigability, Data Protection and Audit Trail, so they are left out of the score. The product code is 76,280 lines, which would take an estimated 0.7 person-years, around €99,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.
If Production Readiness rose from 33 to 70, the lowest score rated Strong, the score would rise from 40 to about 47.
Code composition: what the lines of code are
Product code 66%Tests 34%
New since the last survey: 192 findings
These 192 critical or serious findings weren't in the previous survey, on 8 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Test Quality · Skipped test: Test performance packages/runtime/adapters/eventstore-adapters/eventstore-base/test/thread-array-to-cursor.test.ts
Test Quality · Skipped test: Test performance packages/runtime/adapters/eventstore-adapters/eventstore-base/test/cursor-to-thread-array.test.ts
Test Quality · Races the wall clock: should pass security context to command handler packages/core/core/test/get-aggregates-interop-builder.unit.test.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: 623 findings
These 623 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one. The first 100 are listed here.
€33,000 to €160,000, for 547 to 1,735 hours of work, about 0.7 person-years for 1 to 2 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 40. 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
Medium: 76,280 lines of product code
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
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
Raises the score by about 6 points · Low effort · Secret Scanning
2
Resolve the 78 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (78).
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with index.test.js, custom-adapter.test.js.
Raises the score by about 2 points · Low effort · Test Quality
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €99,000 to build again, about 0.7 person-years of work. Its weakest lens is Production Readiness, at 33 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 6 points for low effort, because it clears the 2 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 5.9 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 5% to 12% on every change.
How this is estimated: It rests on an assumption 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. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Cohesion (LCOM4)
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 — a layering smell or cycle. A clean layered graph 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.
306 modules, with 75 dependencies between them. Every module uses only modules listed above it, so there are no loops.
The table shows the 40 modules with the most connections; 266 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.
examples.ts.personal-data.common.errors uses examples.js.personal-data.common.errors, so a change to examples.js.personal-data.common.errors can break examples.ts.personal-data.common.errors, while a change to examples.ts.personal-data.common.errors can't break examples.js.personal-data.common.errors.
Position
Below the diagonal: examples.ts.personal-data.common.errors uses a module listed above it, which is the healthy direction.
functional-tests.scripts uses functional-tests.scripts.run, so a change to functional-tests.scripts.run can break functional-tests.scripts, while a change to functional-tests.scripts can't break functional-tests.scripts.run.
Position
Below the diagonal: functional-tests.scripts uses a module listed above it, which is the healthy direction.
packages.core.client.src uses packages.core.client.src.client, so a change to packages.core.client.src.client can break packages.core.client.src, while a change to packages.core.client.src can't break packages.core.client.src.client.
Position
Below the diagonal: packages.core.client.src uses a module listed above it, which is the healthy direction.
packages.core.client.src uses packages.core.client.src.subscribe, so a change to packages.core.client.src.subscribe can break packages.core.client.src, while a change to packages.core.client.src can't break packages.core.client.src.subscribe.
Position
Below the diagonal: packages.core.client.src uses a module listed above it, which is the healthy direction.
packages.core.client.src uses packages.core.client.src.subscribe-adapter, so a change to packages.core.client.src.subscribe-adapter can break packages.core.client.src, while a change to packages.core.client.src can't break packages.core.client.src.subscribe-adapter.
Position
Below the diagonal: packages.core.client.src uses a module listed above it, which is the healthy direction.
packages.core.client.src uses packages.core.client.src.types, so a change to packages.core.client.src.types can break packages.core.client.src, while a change to packages.core.client.src can't break packages.core.client.src.types.
Position
Below the diagonal: packages.core.client.src uses a module listed above it, which is the healthy direction.
packages.core.core.src uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.core.core.src, while a change to packages.core.core.src can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.core.core.src uses a module listed above it, which is the healthy direction.
packages.core.core.src.errors uses packages.core.client.src.errors, so a change to packages.core.client.src.errors can break packages.core.core.src.errors, while a change to packages.core.core.src.errors can't break packages.core.client.src.errors.
Position
Below the diagonal: packages.core.core.src.errors uses a module listed above it, which is the healthy direction.
packages.core.redux.src.read-model uses packages.core.redux.src.types, so a change to packages.core.redux.src.types can break packages.core.redux.src.read-model, while a change to packages.core.redux.src.read-model can't break packages.core.redux.src.types.
Position
Below the diagonal: packages.core.redux.src.read-model uses a module listed above it, which is the healthy direction.
packages.core.redux.src.view-model uses packages.core.redux.src.types, so a change to packages.core.redux.src.types can break packages.core.redux.src.view-model, while a change to packages.core.redux.src.view-model can't break packages.core.redux.src.types.
Position
Below the diagonal: packages.core.redux.src.view-model uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types uses a type in packages.core.core.src.types.runtime.
packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types uses a type in packages.core.core.src.types.runtime.
packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types uses a module listed above it, which is the healthy direction.
6 pairs of types, where a type in packages.runtime.adapters.readmodel-adapters.readmodel-base.src uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types.
packages.runtime.adapters.readmodel-adapters.readmodel-base.src uses packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types can break packages.runtime.adapters.readmodel-adapters.readmodel-base.src, while a change to packages.runtime.adapters.readmodel-adapters.readmodel-base.src can't break packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types.
Position
Below the diagonal: packages.runtime.adapters.readmodel-adapters.readmodel-base.src uses a module listed above it, which is the healthy direction.
packages.runtime.adapters.readmodel-adapters.readmodel-postgresql.src uses packages.core.debug-levels.src, so a change to packages.core.debug-levels.src can break packages.runtime.adapters.readmodel-adapters.readmodel-postgresql.src, while a change to packages.runtime.adapters.readmodel-adapters.readmodel-postgresql.src can't break packages.core.debug-levels.src.
Position
Below the diagonal: packages.runtime.adapters.readmodel-adapters.readmodel-postgresql.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.readmodel-adapters.readmodel-postgresql.src uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types.
packages.runtime.adapters.readmodel-adapters.readmodel-postgresql.src uses packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types can break packages.runtime.adapters.readmodel-adapters.readmodel-postgresql.src, while a change to packages.runtime.adapters.readmodel-adapters.readmodel-postgresql.src can't break packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types.
Position
Below the diagonal: packages.runtime.adapters.readmodel-adapters.readmodel-postgresql.src uses a module listed above it, which is the healthy direction.
packages.runtime.runtimes.runtime-base.src uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.runtimes.runtime-base.src, while a change to packages.runtime.runtimes.runtime-base.src can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.runtimes.runtime-base.src uses a module listed above it, which is the healthy direction.
packages.runtime.runtimes.runtime-single-process.src uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.runtimes.runtime-single-process.src, while a change to packages.runtime.runtimes.runtime-single-process.src can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.runtimes.runtime-single-process.src uses a module listed above it, which is the healthy direction.
packages.tools.testing-tools.src.flow.aggregate uses packages.tools.testing-tools.src.types, so a change to packages.tools.testing-tools.src.types can break packages.tools.testing-tools.src.flow.aggregate, while a change to packages.tools.testing-tools.src.flow.aggregate can't break packages.tools.testing-tools.src.types.
Position
Below the diagonal: packages.tools.testing-tools.src.flow.aggregate uses a module listed above it, which is the healthy direction.
packages.tools.testing-tools.src.flow.read-model uses packages.tools.testing-tools.src.types, so a change to packages.tools.testing-tools.src.types can break packages.tools.testing-tools.src.flow.read-model, while a change to packages.tools.testing-tools.src.flow.read-model can't break packages.tools.testing-tools.src.types.
Position
Below the diagonal: packages.tools.testing-tools.src.flow.read-model uses a module listed above it, which is the healthy direction.
benchmarks.eventstore uses packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types can break benchmarks.eventstore, while a change to benchmarks.eventstore can't break packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
Position
Below the diagonal: benchmarks.eventstore uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-base.src uses a type in packages.core.core.src.types.runtime.
packages.runtime.adapters.eventstore-adapters.eventstore-base.src uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.adapters.eventstore-adapters.eventstore-base.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-base.src can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-base.src uses a module listed above it, which is the healthy direction.
9 pairs of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-base.src uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
packages.runtime.adapters.eventstore-adapters.eventstore-base.src uses packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types can break packages.runtime.adapters.eventstore-adapters.eventstore-base.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-base.src can't break packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-base.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types.
packages.runtime.adapters.eventstore-adapters.eventstore-lite uses packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types can break packages.runtime.adapters.eventstore-adapters.eventstore-lite, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite can't break packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-lite uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
packages.runtime.adapters.eventstore-adapters.eventstore-lite uses packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types can break packages.runtime.adapters.eventstore-adapters.eventstore-lite, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite can't break packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-lite uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite.src uses a type in packages.core.core.src.types.runtime.
packages.runtime.adapters.eventstore-adapters.eventstore-lite.src uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.adapters.eventstore-adapters.eventstore-lite.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite.src can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-lite.src uses a module listed above it, which is the healthy direction.
47 pairs of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite.src uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
packages.runtime.adapters.eventstore-adapters.eventstore-lite.src uses packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types can break packages.runtime.adapters.eventstore-adapters.eventstore-lite.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite.src can't break packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-lite.src uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite.src uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
packages.runtime.adapters.eventstore-adapters.eventstore-lite.src uses packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types can break packages.runtime.adapters.eventstore-adapters.eventstore-lite.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite.src can't break packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-lite.src uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src uses packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types can break packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src can't break packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src uses packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types can break packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src can't break packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-mysql.src uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src uses a type in packages.core.core.src.types.runtime.
packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src uses a module listed above it, which is the healthy direction.
51 pairs of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src uses packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types can break packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src can't break packages.runtime.adapters.eventstore-adapters.eventstore-lite.src.types.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src uses a type in packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src uses packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types, so a change to packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types can break packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src, while a change to packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src can't break packages.runtime.adapters.eventstore-adapters.eventstore-base.src.types.
Position
Below the diagonal: packages.runtime.adapters.eventstore-adapters.eventstore-postgresql.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch uses a type in packages.core.core.src.types.runtime.
packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch uses a type in packages.core.debug-levels.src.
packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch uses packages.core.debug-levels.src, so a change to packages.core.debug-levels.src can break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch can't break packages.core.debug-levels.src.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch uses a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch uses packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types, so a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types can break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch can't break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src uses a type in packages.core.core.src.types.runtime.
packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src uses a type in packages.core.debug-levels.src.
packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src uses packages.core.debug-levels.src, so a change to packages.core.debug-levels.src can break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src can't break packages.core.debug-levels.src.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src uses a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src uses packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types, so a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types can break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src can't break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src uses a module listed above it, which is the healthy direction.
packages.runtime.adapters.monitoring-adapters.monitoring-base uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.adapters.monitoring-adapters.monitoring-base, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-base can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-base uses a module listed above it, which is the healthy direction.
packages.runtime.adapters.monitoring-adapters.monitoring-base uses packages.core.debug-levels.src, so a change to packages.core.debug-levels.src can break packages.runtime.adapters.monitoring-adapters.monitoring-base, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-base can't break packages.core.debug-levels.src.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-base uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-base uses a type in packages.runtime.adapters.monitoring-adapters.monitoring-base.src.types.
packages.runtime.adapters.monitoring-adapters.monitoring-base uses packages.runtime.adapters.monitoring-adapters.monitoring-base.src.types, so a change to packages.runtime.adapters.monitoring-adapters.monitoring-base.src.types can break packages.runtime.adapters.monitoring-adapters.monitoring-base, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-base can't break packages.runtime.adapters.monitoring-adapters.monitoring-base.src.types.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-base uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-base uses a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
packages.runtime.adapters.monitoring-adapters.monitoring-base uses packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types, so a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types can break packages.runtime.adapters.monitoring-adapters.monitoring-base, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-base can't break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-base uses a module listed above it, which is the healthy direction.
packages.runtime.adapters.monitoring-adapters.monitoring-console uses packages.core.core.src.types.runtime, so a change to packages.core.core.src.types.runtime can break packages.runtime.adapters.monitoring-adapters.monitoring-console, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-console can't break packages.core.core.src.types.runtime.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-console uses a module listed above it, which is the healthy direction.
packages.runtime.adapters.monitoring-adapters.monitoring-console uses packages.core.debug-levels.src, so a change to packages.core.debug-levels.src can break packages.runtime.adapters.monitoring-adapters.monitoring-console, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-console can't break packages.core.debug-levels.src.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-console uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-console uses a type in packages.runtime.adapters.monitoring-adapters.monitoring-base.src.types.
packages.runtime.adapters.monitoring-adapters.monitoring-console uses packages.runtime.adapters.monitoring-adapters.monitoring-base.src.types, so a change to packages.runtime.adapters.monitoring-adapters.monitoring-base.src.types can break packages.runtime.adapters.monitoring-adapters.monitoring-console, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-console can't break packages.runtime.adapters.monitoring-adapters.monitoring-base.src.types.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-console uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-console uses a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
packages.runtime.adapters.monitoring-adapters.monitoring-console uses packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types, so a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types can break packages.runtime.adapters.monitoring-adapters.monitoring-console, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-console can't break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-console uses a module listed above it, which is the healthy direction.
packages.runtime.adapters.monitoring-adapters.monitoring-console.src uses packages.core.debug-levels.src, so a change to packages.core.debug-levels.src can break packages.runtime.adapters.monitoring-adapters.monitoring-console.src, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-console.src can't break packages.core.debug-levels.src.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-console.src uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in packages.runtime.adapters.monitoring-adapters.monitoring-console.src uses a type in packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
packages.runtime.adapters.monitoring-adapters.monitoring-console.src uses packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types, so a change to packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types can break packages.runtime.adapters.monitoring-adapters.monitoring-console.src, while a change to packages.runtime.adapters.monitoring-adapters.monitoring-console.src can't break packages.runtime.adapters.monitoring-adapters.monitoring-aws-cloudwatch.src.types.
Position
Below the diagonal: packages.runtime.adapters.monitoring-adapters.monitoring-console.src uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 55% · Adequate · gated by D2 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A03:2025 — Software Supply Chain Failures
166
High / Critical
A05:2025 — Injection
161
High / Critical
A07:2025 — Authentication Failures
4
High / Critical
Roadmap
Immediately resolve the 78 deprecated dependencies and 28 outdated npm packages to restore dependency hygiene, while explicitly removing unused imports and demoting test-only packages to devDependencies. Simultaneously, remediate the two leaked secrets found in REDACTED to eliminate immediate security risks. Finally, integrate a SAST step into the CI pipeline using tools like CodeQL or semgrep to ensure security regressions fail the build before they land.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2).
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
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 — 221
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 — 724
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 — 544
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 8
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
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. 79 of 83 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 1.0 — 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 — 83 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, 1361 of 1489 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.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 161 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 129 of the 1041 production source files in this repository: 880 are under the ~2,400-byte size floor this dimension measures over, and the remaining 32 have no attributable history left to measure.
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. `packages/runtime/runtimes/runtime-aws-serverless/external.d.ts` 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 DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — postgres Pulling nginx Pulling nginx Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: server Skipped - No image to be pulled nginx Pulling postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden nginx Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
C1 Data Protection — 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. 'better-sqlite3' is imported (packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/types.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C3 Audit Trail — 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. 'better-sqlite3' is imported (packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/types.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C4 Data Retention — 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. 'better-sqlite3' is imported (packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/types.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
C5 Data-Subject Rights — 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. 'better-sqlite3' is imported (packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/types.ts:1), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
P12 CI test-gate honesty — 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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
P2 Observability — 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. 13 further occurrence(s) are not listed individually; the score already reflects all 53.
PF3 Async & latency hygiene — 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. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
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. 237 further occurrence(s) are not listed individually; the score already reflects all 277.
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. 255 further occurrence(s) are not listed individually; the score already reflects all 295.
R7 Dead Code — 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. 158 further occurrence(s) are not listed individually; the score already reflects all 198.
X3 Exception handling — 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. 35 further occurrence(s) are not listed individually; the score already reflects all 75.
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 log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Repo exclusion declarations: 62 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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside Watchdog's isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D11 Test Reliability: Flakiness is inferred from history/markers — 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.
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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
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.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
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.
The LLM boundary
LLM-set scores this run (4): D19, D21, D22, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
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.
43 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was build.buildEvents at 90. A further 2 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 helpers.validatePath at 16 — they are counted neither in the figure above nor in this dimension's score. 2 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/core/core/src/helpers.ts (helpers.validatePath at 16), packages/runtime/runtimes/runtime-base/src/utils/validate-path.ts (validate-path.validatePath at 16). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 34 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 60 down to 60 or less in Cyclomatic Complexity — start with build.buildEvents (cyclomatic 90). — Refactoring it lifts Cyclomatic Complexity from 5.7 to about 6.2/10.
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 1 body over 120 down to 120 or less in Cognitive Complexity — start with build.buildEvents (cognitive 170). — Refactoring it lifts Cognitive Complexity from 2.1 to about 3.0/10.
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 Classes8.6 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 23 FunctionTooLong finding(s) in God Classes — start with event-subscriber-notifier-factory.ts (2), build.ts (2), get-aggregates-interop-builder.ts (2). — One of this dimension's main actionable groups (23 warning-level).
Resolve the 3 FileTooLong finding(s) in God Classes — start with build.ts (2), types.ts. — One of this dimension's main actionable groups (3 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.6 / 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.
51 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 9 module(s) off the main sequence, with abstractness counted on 29 of the 51 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: @resolve-js/debug-levels · ×9
What to do
Resolve the 9 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (9 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.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from coverlet runs or committed reports (Cobertura/OpenCover/lcov), computed per-file with structured exclusions for generated, trivial, and glue code. When the suite can't be built/run in-image AND no report is committed, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
Line coverage 76.8% — 1 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/js/hacker-news/; jest in examples/js/personal-data/: not run; jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/js/shopping-list/; jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/js/shopping-list-redux/; jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/js/shopping-list-redux-hoc/; jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/ts/hacker-news/; jest in examples/ts/personal-data/: not run; jest in examples/ts/shopping-list/: not run; jest in examples/ts/shopping-list-redux/: not run; jest in examples/ts/shopping-list-redux-hoc/: not run; jest in functional-tests/: not run; jest in functional-tests/app/: not run).
Resolve the 1 Low coverage finding(s) in Code Coverage — start with user.commands.js. — One of this dimension's main actionable groups (1 warning-level).
Enforce Code Coverage in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D9 · Test Distribution9.0 / 10Strong✓ 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.
1379 test methods: 1269 unit, 0 integration, 0 BDD, 110 e2e. The JavaScript/TypeScript suite contributes 1379 `it`/`test` case(s) across 233 test file(s) declaring at least one; its tier split is read from package names and paths only.
What to do
Improve Test Distribution — currently 9.0/10. — 1379 test methods: 1269 unit, 0 integration, 0 BDD, 110 e2e. The JavaScript/TypeScript suite contributes 1379 `it`/`test` case(s) across 233 test file(s) declaring at least one; its tier split is read from package names and paths only.
Detailed fixes: d9_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.4 / 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.
2 skipped, 48 zero-assertion, 1 racing the wall clock, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1379 tests.
No assertions (empty test): Add tests for @resolve-js/module-auth · ×2packages/modules/module-auth/test/index.test.js:1
No assertions: login · ×46examples/js/hacker-news/test/e2e-docker/check-application.js:8
Skipped test: Test performance · ×2packages/runtime/adapters/eventstore-adapters/eventstore-base/test/thread-array-to-cursor.test.ts:40
Test project verifies nothing: packages/runtime/adapters/replicators/replicator-via-api-handlerpackages/runtime/adapters/replicators/replicator-via-api-handler/test/index.test.ts:13
Races the wall clock: should pass security context to command handlerpackages/core/core/test/get-aggregates-interop-builder.unit.test.ts:250
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 2 No assertions (empty test) finding(s) in Test Quality — start with index.test.js, custom-adapter.test.js. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 46 No assertions finding(s) in Test Quality — start with saga.test.ts (8), aggregate.test.ts (7), index.test.ts (5). — One of this dimension's main actionable groups (46 warning-level).
Resolve the 2 Skipped test finding(s) in Test Quality — start with thread-array-to-cursor.test.ts, cursor-to-thread-array.test.ts. — One of this dimension's main actionable groups (2 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 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests pass reliably, with no flakiness.
Method: Suite re-run N times within tiered wall-clock budgets (unit to e2e); tests failing non-deterministically across runs flagged; guarded tests retried when #if guards detected.
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/js/hacker-news/ (28 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/js/personal-data/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/js/shopping-list/ (12 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/js/shopping-list-redux/ (12 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/js/shopping-list-redux-hoc/ (12 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/ts/hacker-news/ (9 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/ts/personal-data/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/ts/shopping-list/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/ts/shopping-list-redux/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in examples/ts/shopping-list-redux-hoc/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in functional-tests/ (0 tests); jest via `yarn install --frozen-lockfile --ignore-scripts` in functional-tests/app/ (0 tests)): measured (0 flaky).
Test suite declares a test script but contains no test files: functional-tests/app/
What to do
Resolve the 1 Test suite declares a test script but contains no test files finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d11_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
120 outdated direct production npm dependency(ies) of 155 graded, 0 pinning defect(s), across 68 REDACTED (43 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 14 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 78 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (78). — One of this dimension's main actionable groups (78 recommendation-level).
Resolve the 49 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (49). — One of this dimension's main actionable groups (49 warning-level).
Resolve the 28 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (28). — One of this dimension's main actionable groups (28 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.
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Enforce Secret Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 155 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 155 production dependency(ies) this repository's committed lockfile resolves, across 43 product REDACTED manifest(s). Its 747 `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. 2 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under 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: 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.
69 deducted task-comment markers across 51396 LoC (0.1/KLoC) → score 9.7. 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 62 TodoComment finding(s) in Explicit Debt — start with types.ts (8), lambda-worker.ts (6), create-runtime.ts (6). — One of this dimension's main actionable groups (62 warning-level).
Resolve the 6 FixmeComment finding(s) in Explicit Debt — start with validate-aggregate.ts, validate-read-model.ts, validate-saga.ts. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with index.test.ts. — One of this dimension's main actionable groups (1 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: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's root README and the docs/README are both excellent: the former is a clear overview of reSolve as a full-stack CQRS/DDD event-sourcing framework with links to prerequisites, getting started, examples, and an architecture section; the latter is a well-organized documentation directory that lists every visible section (Basics, Guides) and covers each one. The benchmarks/README documents its own tier without referencing the repository root, which is correct per-directory focus. All visible documents are present in the outline and show commands to type. The repository's READMEs and architecture/Docs markdown files are well organized: the READMEs for each subdirectory (e.g. 'hacker-news', 'personal-data') document their own directory rather than the root project, so they all fall under the per-directory scope; there is a strong tutorial/lesson-5 README with an overview, installation, and run commands, plus data-import examples, and a consistent navigation path to API references and the step-by-step tutorial. The architecture/Docs set provides detailed design docs (e.g. CQRS for the Hacker News clone).
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
0 naming inconsistencies across 0 sampled symbols.
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md.
Do you agree with this assessment?
D22 · Internal API ConsistencyExemplary◐ Sampled · advisory
What it measures: Whether the internal API surface is consistent and coherent.
Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.
What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.
Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.
Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.
What it measures: Whether 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).
161 finding(s): 0 critical, 115 high, 34 medium, 12 low. 73 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 1 file(s) — `packages/runtime/runtimes/runtime-aws-serverless/external.d.ts` (line 2) — 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 2 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
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 28 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (9), REDACTED (9), REDACTED (5). — One of this dimension's main actionable groups (28 issue-level).
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED. — One of this dimension's main actionable groups (5 issue-level).
No action in Static Analysis (SAST) — all 73 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 (73 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.
Resolve the 75 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (61), REDACTED (14). — One of this dimension's main actionable groups (75 issue-level).
Resolve the 19 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14), REDACTED (5). — One of this dimension's main actionable groups (19 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
161 of 161 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts. Counted over 161 of the 1041 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×2packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:1
Concentrated knowledge decay
What to do
Resolve the 159 Orphaned file finding(s) in Knowledge Freshness — start with types.ts (9), index.ts (8), save-event.ts (4). — One of this dimension's main actionable groups (159 recommendation-level).
Resolve the 2 Most significant orphaned file finding(s) in Knowledge Freshness — start with build.ts, types.ts. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Concentrated knowledge decay 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.
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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 6 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (6 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 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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 0 platform declaration(s) and 1 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 · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.
Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.
Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.
An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 25 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
What to do
Accessibility linting is already configured — assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.
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.
`Adapter` declares 25 required operations: `importEvents`, `exportEvents`, `getLatestEvent`, `init`, `drop`, `dispose`, `freeze`, `unfreeze`, `getSecretsManager`, `dropSnapshot`, `pushIncrementalImport`, `beginIncrementalImport`, `commitIncrementalImport`, `rollbackIncrementalImport`, `incrementalImport`, `loadSecrets`, `importSecrets`, `exportSecrets`, `gatherSecretsFromEvents`, `getCursorUntilEventTypes`, `establishTimeLimit`, `getEventLoader`, `runtimeInfo`, `setReconnectionMode`, `setMonitoring`. Counted over its REQUIRED operations — a method signature or a function-typed property with no `?`, once per signature; optional members and data properties are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts:488
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.
Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.
Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.
Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
Only 1 place(s) refuse an unauthorized caller — too few to demonstrate default-deny across handlers.
What to do
Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
Enforce authorization at every handler — a guard on each route, or a global authentication guard/middleware with explicit public opt-outs, so protected-by-default is demonstrable.
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. — packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/describe.ts:4
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.
`connect` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — packages/core/client/src/subscribe.ts:200, packages/runtime/adapters/replicators/replicator-via-api-handler/src/connect.ts:3
`checkApplicationName` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/core/create-resolve-app/src/check-application-name.ts:4
`installDependencies` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/core/create-resolve-app/src/install.ts:21
`moveExample` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/core/create-resolve-app/src/move-example.ts:12
`patchPackageJson` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/core/create-resolve-app/src/patch-package-json.ts:7
`printFinishOutput` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/core/create-resolve-app/src/print-finish-output.ts:6
`systemStatusHandler` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/modules/module-admin/src/api-handlers/system-status-handler.js:3
`logoutApiHandler` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/modules/module-auth/src/logout_api_handler.js:3
`sendAuthResponse` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/modules/module-auth/src/send_auth_response.js:1
`describe` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/describe.ts:4
`injectEvents` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/inject-events.ts:4
`adjustResolveConfig` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. (×2) — packages/runtime/runtimes/runtime-aws-serverless/src/compile-time/index.ts:14, packages/runtime/runtimes/runtime-single-process/src/compile-time/index.ts:3
`dispose` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/runtime/runtimes/runtime-base/src/command.ts:23
`initWebSocketServer` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — packages/runtime/runtimes/runtime-single-process/src/websocket-server-factory.ts:155
`verifyCommand` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/modules/module-comments/src/common/aggregates/verify-command.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. (×3) — packages/runtime/adapters/eventstore-adapters/eventstore-base/test/cursor-to-thread-array.test.ts:40, packages/runtime/adapters/eventstore-adapters/eventstore-base/test/thread-array-to-cursor.test.ts:40, packages/runtime/adapters/eventstore-adapters/eventstore-mysql/test/index.test.js:8
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. — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts:2
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
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 11 of 66 project(s) that lack one — worth up to 0.3 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.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
docs/Contributing.md runs `yarn test:functional`, but no REDACTED declares a `test:functional` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/Contributing.md:41
packages/core/README.md links to `@resolve-js/scripts`, but `packages/core/@resolve-js/scripts` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/README.md:7
packages/core/README.md links to `@resolve-js/testing-tools`, but `packages/core/@resolve-js/testing-tools` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/README.md:9
packages/core/README.md links to `@resolve-js/redux`, but `packages/core/@resolve-js/redux` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/README.md:14
packages/modules/README.md links to `@resolve-js/module-admin/`, but `packages/modules/@resolve-js/module-admin` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/modules/README.md:5
packages/modules/README.md links to `@resolve-js/module-auth/`, but `packages/modules/@resolve-js/module-auth` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/modules/README.md:6
packages/modules/README.md links to `@resolve-js/module-comments/`, but `packages/modules/@resolve-js/module-comments` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/modules/README.md:7
packages/modules/README.md links to `@resolve-js/module-uploader/`, but `packages/modules/@resolve-js/module-uploader` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/modules/README.md:8
packages/modules/README.md links to `@resolve-js/module-incremental-import/`, but `packages/modules/@resolve-js/module-incremental-import` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/modules/README.md:9
docs/api/client/entry-point.md links to `frontend.md`, but `docs/api/client/frontend.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/api/client/entry-point.md:20
packages/core/create-resolve-app/README.md runs `npm run test:functional`, but no REDACTED declares a `test:functional` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/create-resolve-app/README.md:92
packages/core/create-resolve-app/README.md links to `../../docs/API%20References.md/#project-structure-overview`, but `packages/docs/API References.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/create-resolve-app/README.md:96
packages/core/create-resolve-app/README.md links to `../../docs/Aggregate.md`, but `packages/docs/Aggregate.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/create-resolve-app/README.md:98
packages/core/create-resolve-app/README.md links to `../../docs/View%20Model.md`, but `packages/docs/View Model.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/create-resolve-app/README.md:99
packages/core/create-resolve-app/README.md links to `../../docs/Read%20Model.md`, but `packages/docs/Read Model.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/core/create-resolve-app/README.md:100
packages/modules/module-auth/README.md names `auth/route_register_callback.js`, but no file or folder `auth/route_register_callback.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/modules/module-auth/README.md:86
packages/runtime/adapters/readmodel-adapters/README.md links to `../../core/resolve-query`, but `packages/runtime/core/resolve-query` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — packages/runtime/adapters/readmodel-adapters/README.md:3
What to do
Reconcile the README with reality: docs/Contributing.md runs `yarn test:functional`, but no REDACTED declares a `test:functional` script; packages/core/README.md links to `@resolve-js/scripts`, but `packages/core/@resolve-js/scripts` does not exist; packages/core/README.md links to `@resolve-js/testing-tools`, but `packages/core/@resolve-js/testing-tools` does not exist; packages/core/README.md links to `@resolve-js/redux`, but `packages/core/@resolve-js/redux` does not exist; packages/modules/README.md links to `@resolve-js/module-admin/`, but `packages/modules/@resolve-js/module-admin` does not exist.
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 · Observability7.2 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 19/26 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `internal/babel-compile`, `internal/build-packages`, `internal/helpers`, `internal/local-registry`, `internal/root-yarn` and 2 more.
`packages/core/core/src/helpers.ts` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/core/src/helpers.ts:49
`packages/core/core/src/helpers.ts` reports through `console.*` at line 57 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/core/src/helpers.ts:57
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 10 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:10
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:11
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:12
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:14
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 15 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:15
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:16
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:18
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 19 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:19
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:20
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:22
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:23
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:24
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 26 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:26
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:27
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:28
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 30 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:30
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 31 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:31
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:32
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:37
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:38
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 39 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:39
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:40
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 41 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:41
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 42 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:42
`packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 43 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/print-finish-output.ts:43
`packages/core/create-resolve-app/src/prepare-options.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/prepare-options.ts:29
`packages/core/create-resolve-app/src/prepare-options.ts` reports through `console.*` at line 33 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/prepare-options.ts:33
`packages/core/create-resolve-app/src/prepare-options.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/prepare-options.ts:37
`packages/core/create-resolve-app/src/prepare-options.ts` reports through `console.*` at line 41 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/prepare-options.ts:41
`packages/core/create-resolve-app/src/prepare-options.ts` reports through `console.*` at line 81 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/prepare-options.ts:81
`packages/core/create-resolve-app/src/pipeline.ts` reports through `console.*` at line 29 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/pipeline.ts:29
`packages/core/create-resolve-app/src/patch-package-json.ts` reports through `console.*` at line 13 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/patch-package-json.ts:13
`packages/core/create-resolve-app/src/install.ts` reports through `console.*` at line 10 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/install.ts:10
`packages/core/create-resolve-app/src/install.ts` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/install.ts:23
`packages/core/create-resolve-app/src/download-resolve-repo.ts` reports through `console.*` at line 104 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/download-resolve-repo.ts:104
`packages/core/create-resolve-app/src/download-resolve-repo.ts` reports through `console.*` at line 108 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/download-resolve-repo.ts:108
`packages/core/create-resolve-app/src/create-application.ts` reports through `console.*` at line 19 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/core/create-resolve-app/src/create-application.ts:19
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 31953 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
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.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. (×2) — REDACTED:38, REDACTED:79
What to do
Bound every outbound call: pass `signal: AbortSignal.timeout(ms)` to `fetch`, set `timeout` on the axios instance (`axios.create({ timeout })`), and add retries with back-off (`axios-retry`, `p-retry`) and a breaker (`opossum`, `cockatiel`) around dependencies that fail.
Do you agree with this assessment?
P9 · Domain vs controller coverage7.4 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether test coverage concentrates on the domain (business rules) rather than the trivial web/controller layer — a focus check a generic tool can't make.
Method: Roslyn plus test-execution analysis: domain-layer versus trivial web/controller coverage ratio. Computed metric, deterministic.
What to do
Raise domain coverage toward 100% — cover the remaining aggregates / value objects / domain services where the business invariants and costly bugs live.
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.
`fs.readdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/create-resolve-app/src/download-resolve-repo.ts:29
`fs.readdirSync` in `downloadResolveRepo` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/create-resolve-app/src/download-resolve-repo.ts:126
`execSync` in `installDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/core/create-resolve-app/src/install.ts:28, packages/core/create-resolve-app/src/install.ts:36
`fs.readdirSync` in `moveExample` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/create-resolve-app/src/move-example.ts:27
`fs.writeFileSync` in `patchPackageJson` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/core/create-resolve-app/src/patch-package-json.ts:33, packages/core/create-resolve-app/src/patch-package-json.ts:84
`fs.readdirSync` in `patchPackageJson` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/core/create-resolve-app/src/patch-package-json.ts:39
`fs.existsSync` in `eventStoreExportHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:24
`fs.mkdirSync` in `eventStoreExportHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:25
`fs.existsSync` in `eventStoreImportHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — REDACTED:27, REDACTED:31, REDACTED:9
`fs.existsSync` in `removeCallback` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:43, packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:122
`fs.unlinkSync` in `removeCallback` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:44, packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:123
`fs.existsSync` in `connector` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:48
`fs.writeFileSync` in `connector` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:49
`fs.existsSync` in `CurrentConnectMethod` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:127
`fs.writeFileSync` in `CurrentConnectMethod` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:128
`fs.existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — packages/runtime/runtimes/runtime-aws-serverless/src/index.ts:16, packages/runtime/runtimes/runtime-single-process/src/index.ts:22
`fs.existsSync` in `uploaderHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:36, REDACTED:49
`fs.mkdirSync` in `uploaderHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:37, REDACTED:50
`fs.writeFileSync` in `uploaderHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — REDACTED:59, REDACTED:72, REDACTED:81
`fs.readFileSync` in `uploaderHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×2) — REDACTED:129, REDACTED:135
`fs.readFileSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/runtime/runtimes/runtime-base/src/load-read-model-procedure.ts:26
`fs.existsSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. (×3) — packages/runtime/runtimes/runtime-single-process/src/api-handlers/export-event-store-handler.ts:16, packages/runtime/runtimes/runtime-single-process/src/api-handlers/import-event-store-handler.ts:19, packages/runtime/runtimes/runtime-single-process/src/api-handlers/import-event-store-handler.ts:23
`fs.mkdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/runtime/runtimes/runtime-single-process/src/api-handlers/export-event-store-handler.ts:17
`fs.existsSync` in `buildMode` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/tools/scripts/src/build_mode.js:67
`fs.copyFileSync` in `buildMode` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — packages/tools/scripts/src/build_mode.js:68
`execSync` in `runAfterLaunch` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs. — REDACTED:82
What to do
TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.
Do you agree with this assessment?
R1 · Type Safety6.2 / 10Adequate✓ 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.
814 typed · 506 plain JS — the untyped files are functional-tests/app/auth/create-strategy.js, functional-tests/app/auth/jwt-secret.js, functional-tests/app/auth/route-login-callback.js, functional-tests/app/auth/route-register-callback.js, functional-tests/app/client/hoc/components/Routes.js, functional-tests/app/client/hoc/containers/App.js (+500 more). 1 production file(s) opt out entirely with @ts-nocheck · 15 @ts-ignore suppression(s); the opted-out files are packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts.
What to do
Migrate the remaining .js/.jsx files to TypeScript.
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.
tutorial/lesson-3/ and tutorial/lesson-4/ are near-verbatim copies of each other: 14 files are byte-identical under the same relative paths (~427 lines; the trees hold 27 and 30 files). That is one structural fact, not 14 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — tutorial/lesson-3/config.prod.js:1
tutorial/lesson-2/ and tutorial/lesson-3/ are near-verbatim copies of each other: 12 files are byte-identical under the same relative paths (~411 lines; the trees hold 21 and 27 files). That is one structural fact, not 12 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place. — tutorial/lesson-2/run.js:1
49 duplicated blocks under packages/runtime/adapters/readmodel-adapters/ have copies in at least two of the sibling directories readmodel-base, readmodel-lite, readmodel-mysql, readmodel-postgresql — 40 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 49 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 49 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 49 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:155
48 duplicated blocks under packages/runtime/adapters/eventstore-adapters/ have copies in at least two of the sibling directories eventstore-lite, eventstore-mysql, eventstore-postgresql — 34 of them are reported below, and 14 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 48 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 48 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 48 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/set-replication-status.ts:17
31 duplicated blocks under templates/ have copies in at least two of the sibling directories js, ts — 26 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 31 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 31 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 31 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — templates/js/postcss/run.js:18
19 duplicated blocks under tutorial/ have copies in at least two of the sibling directories lesson-1, lesson-2, lesson-3, lesson-4, lesson-5 — 14 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 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 19 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. — tutorial/lesson-4/run.js:20
10 duplicated blocks under packages/tools/testing-tools/src/flow/ have copies in at least two of the sibling directories aggregate, read-model, saga — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/tools/testing-tools/src/flow/read-model/make-test-environment.ts:29
9 duplicated blocks under templates/ts/ have copies in at least two of the sibling directories postcss, react, styled-components, vanilla, vue — 6 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — templates/ts/postcss/client/containers/Header.tsx:1
8 duplicated blocks under the repository root have copies in at least two of the sibling directories internal, packages, templates, tutorial — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — templates/js/react/run.js:19
7 duplicated blocks under packages/core/redux/src/ have copies in at least two of the sibling directories command, read-model, view-model — 4 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/core/redux/src/command/use-redux-command.ts:49
6 duplicated blocks under packages/runtime/adapters/ have copies in at least two of the sibling directories eventstore-adapters, readmodel-adapters, replicators — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/types.ts:148
5 duplicated blocks under packages/modules/module-admin/src/commands/ have copies in at least two of the sibling directories event-store, read-models, sagas — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/modules/module-admin/src/commands/read-models/list.js:6
packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:155 · packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:119 — the two spans are one implementation copied and then locally edited — 728 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:155
packages/runtime/runtimes/runtime-aws-serverless/src/wrap-api-handler.ts:194 · packages/runtime/runtimes/runtime-single-process/src/wrap-api-handler.ts:110 — 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. — packages/runtime/runtimes/runtime-aws-serverless/src/wrap-api-handler.ts:194
packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-events.ts:95 · packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-secrets.ts:40 — 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. — packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-events.ts:95
packages/tools/testing-tools/src/flow/read-model/make-test-environment.ts:29 · packages/tools/testing-tools/src/flow/saga/make-test-environment.ts:36 — the two spans are one implementation copied and then locally edited — 695 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/tools/testing-tools/src/flow/read-model/make-test-environment.ts:29
packages/core/react-hooks/src/use-command.ts:25 · packages/core/react-hooks/src/use-query.ts:24 — 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. — packages/core/react-hooks/src/use-command.ts:25
templates/js/postcss/run.js:18 · templates/ts/postcss/run.ts:20 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — templates/js/postcss/run.js:18
packages/core/redux/src/command/use-redux-command.ts:49 · packages/core/redux/src/read-model/use-redux-read-model.ts:68 — the two spans are one implementation copied and then locally edited — 512 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/redux/src/command/use-redux-command.ts:49
packages/runtime/runtimes/runtime-aws-serverless/src/uploader-factory.ts:81 · REDACTED:41 — the two spans are one implementation copied and then locally edited — 409 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/runtime/runtimes/runtime-aws-serverless/src/uploader-factory.ts:81
packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/update-to-set-expression.ts:16 · packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/update-to-set-expression.ts:17 — the two spans are one implementation copied and then locally edited — 351 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/update-to-set-expression.ts:16
packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/status.ts:13 · packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/status.ts:16 — the two spans are one implementation copied and then locally edited — 360 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/status.ts:13
templates/js/vue/run.js:17 · templates/ts/vue/run.ts:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — templates/js/vue/run.js:17
templates/js/vue/run.js:11 · templates/ts/angular/run.ts:10 · templates/ts/vue/run.ts:12 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — templates/js/vue/run.js:11
tutorial/lesson-4/run.js:20 · tutorial/lesson-5/run.js:20 — 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. — tutorial/lesson-4/run.js:20
packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/search-to-where-expression.ts:1 · packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/search-to-where-expression.ts:1 · packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/search-to-where-expression.ts:1 — these 3 files are line-for-line copies of one another — 69 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. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/search-to-where-expression.ts:1
templates/js/react/run.js:19 · templates/ts/react/run.ts:22 · tutorial/lesson-1/run.js:17 · tutorial/lesson-2/run.js:17 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — templates/js/react/run.js:19
templates/js/vanilla/run.js:15 · templates/ts/vanilla/run.ts:17 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — templates/js/vanilla/run.js:15
packages/modules/module-comments/src/client/containers/CommentsPaginateRenderless.js:14 · packages/modules/module-comments/src/client/containers/CommentsTreeRenderless.js:12 — the two spans are one implementation copied and then locally edited — 209 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/modules/module-comments/src/client/containers/CommentsPaginateRenderless.js:14
packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/resubscribe.ts:62 · packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/subscribe.ts:31 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/resubscribe.ts:62
templates/js/styled-components/client/ssr.js:10 · templates/ts/styled-components/client/ssr.tsx:12 — the two spans are one implementation copied and then locally edited — 336 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — templates/js/styled-components/client/ssr.js:10
templates/js/styled-components/run.js:12 · templates/ts/styled-components/run.ts:12 — these 2 files are line-for-line copies of one another — 56 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — templates/js/styled-components/run.js:12
packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/reset.ts:17 · packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/unsubscribe.ts:22 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/reset.ts:17
templates/js/react/client/components/MyAggregateList.js:6 · templates/ts/react/client/components/MyAggregateList.tsx:7 — the two spans are one implementation copied and then locally edited — 278 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — templates/js/react/client/components/MyAggregateList.js:6
packages/core/redux/src/read-model/actions.ts:19 · packages/core/redux/src/view-model/actions.ts:48 — the two spans are one implementation copied and then locally edited — 179 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/redux/src/read-model/actions.ts:19
packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/set-replication-status.ts:17 · packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/set-replication-status.ts:18 — the two spans are one implementation copied and then locally edited — 121 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/set-replication-status.ts:17
packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/index.ts:5 · packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/index.ts:1 — these 2 files are line-for-line copies of one another — 52 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. — packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/index.ts:5
templates/ts/postcss/client/containers/Header.tsx:1 · templates/ts/styled-components/client/containers/Header.tsx:1 — these 2 files are line-for-line copies of one another — 52 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — templates/ts/postcss/client/containers/Header.tsx:1
templates/js/postcss/client/containers/Header.js:6 · templates/js/styled-components/client/containers/Header.js:6 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — templates/js/postcss/client/containers/Header.js:6
packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/resubscribe.ts:6 · packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/unsubscribe.ts:4 — 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. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/resubscribe.ts:6
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).
Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.
internal/babel-compile/bin/index.js:7 imports @babel/cli/lib/babel/dir, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — internal/babel-compile/bin/index.js:7
internal/helpers/get-babel-config.js:10 reaches into another package with a relative path (../babel-compile/REDACTED) — import the package by name instead. — internal/helpers/get-babel-config.js:10
packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts:23 imports io-ts/lib/PathReporter, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts:23
templates/js/vue/config.adjust-webpack.js:1 imports vue-loader/lib/plugin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/js/vue/config.adjust-webpack.js:1
templates/ts/angular/client/main.ts:4 imports zone.js/dist/zone, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/ts/angular/client/main.ts:4
templates/ts/vue/config.adjust-webpack.ts:1 imports vue-loader/lib/plugin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — templates/ts/vue/config.adjust-webpack.ts:1
What to do
Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
buildEvents has cyclomatic complexity 76 and cognitive complexity 170; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:154
updateToSetExpression has cyclomatic complexity 48 and cognitive complexity 111; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/update-to-set-expression.ts:10
build has cyclomatic complexity 45 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. — packages/runtime/adapters/replicators/replicator-via-api-handler/src/build.ts:37
build has cyclomatic complexity 37 and cognitive complexity 55; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:459
build has cyclomatic complexity 36 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:764
(anonymous) has cyclomatic complexity 31 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:106
(anonymous) has cyclomatic complexity 29 and cognitive complexity 59; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/execute-statement.ts:24
(anonymous) has cyclomatic complexity 29 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 is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/runtimes/runtime-base/src/custom-read-model.ts:51
makeSqlQuery has cyclomatic complexity 29 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/make-sql-query.ts:10
ensureQueue has cyclomatic complexity 28 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:201
buildEvents has cyclomatic complexity 28 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. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:159
isRetryablePassthroughError has cyclomatic complexity 27 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/passthrough-error.ts:44
deleteQueue has cyclomatic complexity 26 and cognitive complexity 61; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:368
uploaderHandler has cyclomatic complexity 22 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:22
(anonymous) has cyclomatic complexity 21 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. — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/status.ts:23
(anonymous) has cyclomatic complexity 21 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/modules/module-comments/src/client/reducers/comments.js:17
execute has cyclomatic complexity 20 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/tools/testing-tools/src/flow/saga/make-test-environment.ts:135
updateToSetExpression has cyclomatic complexity 19 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. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/update-to-set-expression.ts:7
buildEvents has cyclomatic complexity 19 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:123
updateToSetExpression has cyclomatic complexity 18 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/update-to-set-expression.ts:7
What to do
Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
Do you agree with this assessment?
R3 · Large Files9.7 / 10Exemplary✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts has 948 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:1
packages/runtime/adapters/readmodel-adapters/readmodel-base/src/types.ts has 654 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runtime/adapters/readmodel-adapters/readmodel-base/src/types.ts:1
packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts has 618 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:1
packages/core/core/src/aggregate/get-aggregates-interop-builder.ts has 528 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:1
packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts has 484 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:1
packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts:1
packages/runtime/runtimes/runtime-base/src/event-subscriber.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/runtime/runtimes/runtime-base/src/event-subscriber.ts:1
packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.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. — packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:1
packages/core/core/src/types/runtime.ts has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/core/core/src/types/runtime.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 Coverage6.9 / 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) — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts:1, REDACTED:1, packages/modules/module-comments/src/common/read-models/comments.resolvers.js: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 Code6.4 / 10Adequate✓ 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.
20 file(s) (~2811 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. — packages/core/react-hooks
59 file(s) (~9329 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. — tests
Unreachable from the 125 application, 42 tooling and 384 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×19) — packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts, REDACTED, packages/tools/scripts/src/alias/$resolve.readModel.js, …
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-5/client/routes.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — tutorial/lesson-5/client/components/ShoppingList.js, tutorial/lesson-5/client/components/MyLists.js
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/modules/module-auth/src/api_handler_constructor.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/modules/module-auth/src/execute_strategy.js
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/react/client/components/MyAggregateList.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/ts/react/client/components/MyAggregateItems.tsx
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/react/client/containers/App.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/ts/react/client/components/MyAggregateList.tsx
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/postcss/client/components/App.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/ts/postcss/client/containers/Header.tsx
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/styled-components/client/components/App.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/ts/styled-components/client/containers/Header.tsx
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/runtime/runtimes/runtime-aws-serverless/compile-time.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/runtime/runtimes/runtime-aws-serverless/src/compile-time/index.ts
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/js/react/client/containers/App.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/js/react/client/components/MyAggregateList.js
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/js/react/client/components/MyAggregateList.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/js/react/client/components/MyAggregateItems.js
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-4/client/routes.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — tutorial/lesson-4/client/components/ShoppingList.js
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-5/client/components/MyLists.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it (×2) — tutorial/lesson-5/client/components/ShoppingListCreator.js, tutorial/lesson-5/client/components/ShoppingLists.js
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/react/client/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/ts/react/client/containers/App.tsx
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/vanilla/client/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/ts/vanilla/client/init-ui.ts
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/js/react/client/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/js/react/client/containers/App.js
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/js/vanilla/client/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — templates/js/vanilla/client/init-ui.js
no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-3/client/components/App.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — tutorial/lesson-3/client/components/Header.js
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
Declared in 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: functional-tests/api/benchmark.test.ts:6) — move it to devDependencies. — REDACTED:21
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. 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. Its Node HTTP listeners were read for HTTPS enforcement alone — TLS served, a redirect to https:// or HSTS, or a TLS-terminating proxy configuration committed beside the server — each judged per server package.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `default.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — examples/ts/hacker-news/docker/volumes/nginx/conf.d/default.conf:1
`http(…).listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — internal/local-registry/bin/index.js:41
`server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — packages/runtime/runtimes/runtime-single-process/src/start-express.ts:120
What to do
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it. (×6) — packages/runtime/runtimes/runtime-aws-serverless/src/uploader-factory.ts:75, packages/runtime/runtimes/runtime-aws-serverless/src/uploader-factory.ts:150, REDACTED:36, …
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 document10.0 / 10Exemplary○ Nothing flagged
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.
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 async functions that make a cancellable request accept or pass on an AbortSignal (adoption curve).
Method: Roslyn scan: every async method (excluding framework-fixed overrides/Blazor handlers) checked for CancellationToken parameter presence. Deterministic, adoption percentage. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same question: every named async function that itself makes a request an AbortSignal can cancel (global `fetch`, axios and its file-local instances, ky, ofetch) counts, and it is compliant when its parameters or body name a signal or it hands one of its own parameters to the request as options; signatures a framework fixes (JSX event handlers, route and lifecycle exports, request-first handlers, `override`, `'use server'` modules, TanStack `mutationFn`) are exempt unless they take a signal. Deterministic, adoption percentage.
Only 0/22 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`execFetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/core/client/src/middleware.ts:115
`handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. (×18) — packages/modules/module-admin/src/commands/event-store/unfreeze.js:3, packages/modules/module-admin/src/commands/event-store/incremental-import.js:3, packages/modules/module-admin/src/commands/event-store/import.js:5, …
`DropReadModelMethod` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/runtime/adapters/replicators/replicator-via-api-handler/src/drop-read-model.ts:7
`openBrowser` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/tools/scripts/src/open_browser.js:9
`waitForUrl` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — packages/tools/scripts/src/generate_custom_mode.js:18
What to do
Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
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.
`verbose` at line 48 is called with an argument built by `JSON.stringify(entry)` (line 48), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/core/core/src/saga/build-scheduler-projection.ts:48
`verbose` at line 66 is called with an argument built by `JSON.stringify(command)` (line 66), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/core/core/src/saga/build-scheduler-projection.ts:66
`verbose` at line 111 is called with an argument built by `JSON.stringify(metricData.metrics)` (line 111), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/adapters/monitoring-adapters/monitoring-aws-cloudwatch/src/publish.ts:111
`verbose` at line 16 is called with an argument built by `JSON.stringify(entry)` (line 16), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/scheduler-factory.ts:16
`verbose` at line 123 is called with an argument built by `JSON.stringify(data)` (line 123), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/scheduler-factory.ts:123
`verbose` at line 152 is called with an argument built by `JSON.stringify(data)` (line 152), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/scheduler-factory.ts:152
`verbose` at line 108 is called with an argument built by `JSON.stringify(lambdaEvent, null, 2)` (line 108), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:108
`verbose` at line 150 is called with an argument built by `JSON.stringify(executorResult)` (line 150), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:150
`verbose` at line 167 is called with an argument built by `JSON.stringify(executorResult)` (line 167), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:167
`verbose` at line 262 is called with an argument built by `JSON.stringify(executorResult)` (line 262), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:262
`verbose` at line 276 is called with an argument built by `JSON.stringify(executorResult)` (line 276), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:276
`verbose` at line 289 is called with an argument built by `JSON.stringify(executorResult)` (line 289), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:289
`verbose` at line 312 is called with an argument built by `JSON.stringify(lambdaEvent.httpMethod, null, 2)` (line 313), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:312
`verbose` at line 333 is called with an argument built by `JSON.stringify(executorResult)` (line 333), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:333
`verbose` at line 59 is called with an argument built by `JSON.stringify(result, null, 2)` (line 59), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/cloud-service-event-handler.ts:59
`verbose` at line 69 is called with an argument built by `JSON.stringify(result, null, 2)` (line 69), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/cloud-service-event-handler.ts:69
`verbose` at line 93 is called with an argument built by `JSON.stringify(listenerIds, null, 2)` (line 93), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/cloud-service-event-handler.ts:93
`verbose` at line 107 is called with an argument built by `JSON.stringify(result, null, 2)` (line 107), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-aws-serverless/src/cloud-service-event-handler.ts:107
`debug` at line 133 is called with an argument built by `Object.keys(readModelConnectors)` (line 133), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch. — packages/runtime/runtimes/runtime-base/src/create-runtime.ts:133
What to do
Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×40) — packages/core/client/src/subscribe.ts:174, packages/core/client/src/subscribe.ts:187, packages/core/core/src/helpers.ts:17, …
What to do
Swallowed exception (empty catch)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether strict null checking is enabled and not undermined by heavy `!` assertion — TypeScript's `strictNullChecks` (which `strict` turns on) is what makes `string` exclude `null` and `undefined`, and the postfix `!` is the operator that silences it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
24/51 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
~0.2 `!` null assertions per 1k TypeScript source lines — 9 assertion(s) across the 46114 source line(s) of the 651 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts (4), packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/connect.ts (2), packages/runtime/runtimes/runtime-base/src/create-runtime.ts (2). 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?
WCAG coverage — what static analysis assessed
Statically assessed 8 of 55 WCAG 2.2 Level A/AA success criteria (15%; ≈16% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 47 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
P12 CI test-gate honesty — 40 observation(s) recorded · Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
X10 Duplicated predicate — 25 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 — Not assessed: this repository stores data through 'better-sqlite3' (packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/types.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
C4 Data Retention — Not assessed: this repository stores data through 'better-sqlite3' (packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/types.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
C5 Data-Subject Rights — Not assessed: this repository stores data through 'better-sqlite3' (packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/types.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 43 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC2 Forms & labels — No form control/button found in the parsed markup — AC2 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — Not applicable: Angular's root injector cannot see a component-level provider, so a root service asking for one fails with NullInjectorError instead of capturing it.
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 — compose up failed (exit 18 — an image could not be pulled) — postgres Pulling nginx Pulling nginx Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: server Skipped - No image to be pulled nginx Pulling postgres Pulling postgres Error Get "https://registry-1.docker.io/v2/": Forbidden nginx Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: this repository stores data through 'better-sqlite3' (packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/types.ts:1) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
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.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
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,.tsx), 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) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 1 domain event(s); its domain events are published by services or handlers — no domain entity raises one; a Domain/Aggregates/ValueObjects layer; a domain structure with no aggregate, domain event or strongly-typed id in it: a CRUD / clean-architecture model, measured but not claimed as DDD; a top-level examples/ tree: a library or framework whose examples are its consumers — these types are building blocks, not a domain
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
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
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.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
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.
X7 Silent fallback defaults — 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.
Import cycle (2 files) packages/tools/testing-tools/src/flow/saga/allow-side-effects.ts:7— packages/tools/testing-tools/src/flow/saga/allow-side-effects.ts → packages/tools/testing-tools/src/flow/saga/start-side-effects-from.ts → packages/tools/testing-tools/src/flow/saga/allow-side-effects.ts (one verified cycle inside a mutually-dependent group of 5 files)
Import cycle (2 files) packages/tools/testing-tools/src/flow/saga/make-assertions.ts:3— packages/tools/testing-tools/src/flow/saga/make-assertions.ts → packages/tools/testing-tools/src/flow/saga/mock-command-implementation.ts → packages/tools/testing-tools/src/flow/saga/make-assertions.ts (one verified cycle inside a mutually-dependent group of 6 files)
D10 · Test Quality· No assertions (empty test) · ×2
No assertions (empty test): Add tests for @resolve-js/module-auth packages/modules/module-auth/test/index.test.js:1— Test method has an empty body — it asserts nothing and exercises no code.
No assertions (empty test): should work correctly packages/runtime/adapters/eventstore-adapters/eventstore-base/test/custom-adapter.test.js:4— Test method has an empty body — it asserts nothing and exercises no code.
D11 · Test Reliability· Test suite declares a test script but contains no test files · ×1
Test suite declares a test script but contains no test files: functional-tests/app/ — The jest suite in functional-tests/app/ was installed and launched successfully, and the runner then found no test files to run — No tests found, exiting with code 1. The package declares a test script, so it reads as a tested package to anyone who checks its manifest, but there is nothing behind the declaration: no test case exists, so it cannot detect a regression and its presence overstates how much of this repository is tested. The ask is the owner's: write the first test for this package, or remove the test script from a package that has none. This is not a report that the tests FAIL — there are none.
TodoComment packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:209— //TODO: check for null — 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 packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:283— // TODO: Restore (sealed) — 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 packages/core/core/src/types/core.ts:51— // TODO: move types from @resolve-js/client here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/set-secret.ts:32— // TODO: refactor — 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 packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/get-secret.ts:19— // TODO: refactor — 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 packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/delete-secret.ts:26— // TODO: refactor — 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 packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/set-secret.ts:60— // TODO: Improve calculation byteLength depend on codepage and wide-characters — 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 packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/save-event.ts:42— // TODO: Improve calculation byteLength depend on codepage and wide-characters — 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 packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/push-incremental-import.ts:59— // TODO: Improve calculation byteLength depend on codepage and wide-characters — 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 packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/delete-secret.ts:54— // TODO: Improve calculation byteLength depend on codepage and wide-characters — 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 packages/runtime/adapters/readmodel-adapters/readmodel-base/src/types.ts:143— // TODO brand type — 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 packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:89— // TODO Init via plv8 — 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 packages/runtime/runtimes/runtime-aws-serverless/src/websocket-event-handler.ts:12— //TODO: check in runtime that these environment variables are defined? — 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 packages/runtime/runtimes/runtime-aws-serverless/src/uploader-factory.ts:244— // TODO: provide support for custom uploader adapter — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:162— // TODO: provide support for custom uploader adapter — 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 packages/runtime/runtimes/runtime-aws-serverless/src/types.ts:37— // TODO: why we still need domain meta outside core? — 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 packages/runtime/runtimes/runtime-aws-serverless/src/types.ts:48— // TODO: do we really need this somewhere? — 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 packages/runtime/runtimes/runtime-aws-serverless/src/types.ts:86— // TODO: bad naming — 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 packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:91— // TODO: only remaining late binding, protected by guard — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:166— // TODO: only remaining late binding, protected by guard — 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 packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:126— // TODO: too complex — 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 packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:160— // TODO ??? — 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 packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:169— // TODO ??? — 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 packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:257— // TODO ??? — 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 packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:264— // TODO ??? — 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.
Deprecated: crypto-js REDACTED:27— crypto-js 4.0.0, declared in REDACTED, is marked deprecated by its publisher: "Active development of CryptoJS has been discontinued. This library is no longer maintained.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: redux-devtools-extension REDACTED:43— redux-devtools-extension 2.13.9, declared in REDACTED, is marked deprecated by its publisher: "Package moved to @redux-devtools/extension.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid REDACTED:46— uuid 8.3.2, 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: @babel/plugin-proposal-class-properties REDACTED:50— @babel/plugin-proposal-class-properties 7.13.0, declared in REDACTED, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:52— @babel/plugin-proposal-export-namespace-from 7.14.2, declared in REDACTED, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: aws-sdk REDACTED:57— aws-sdk 2.1001.0, declared in REDACTED, 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". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: glob internal/babel-compile/REDACTED:14— glob 7.1.6, declared in internal/babel-compile/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: rimraf internal/cra-test/REDACTED:14— rimraf 3.0.2, declared in internal/cra-test/REDACTED, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: glob internal/helpers/REDACTED:12— glob 7.1.6, declared in internal/helpers/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: rimraf REDACTED:15— rimraf 3.0.2, declared in REDACTED, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: @babel/plugin-proposal-class-properties REDACTED:60— @babel/plugin-proposal-class-properties 7.16.7, declared in REDACTED, is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: babel-eslint REDACTED:71— babel-eslint 10.1.0, declared in REDACTED, is marked deprecated by its publisher: "babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:74— eslint 8.9.0, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: glob REDACTED:80— glob 7.1.6, 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: rimraf REDACTED:84— rimraf 3.0.2, declared in REDACTED, is marked deprecated by its publisher: "Rimraf versions prior to v4 are no longer supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid REDACTED:47— uuid 8.3.2, 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: uuid packages/core/core/REDACTED:30— uuid 8.3.2, declared in packages/core/core/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: glob REDACTED:34— glob 7.1.6, 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 packages/core/debug-levels/REDACTED:34— uuid 8.3.2, declared in packages/core/debug-levels/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: lodash.get REDACTED:48— lodash.get 4.4.2, declared in REDACTED, is marked deprecated by its publisher: "This package is deprecated. Use the optional chaining (?.) operator instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: lodash.isequal REDACTED:49— lodash.isequal 4.5.0, declared in REDACTED, is marked deprecated by its publisher: "This package is deprecated. Use require('node:util').isDeepStrictEqual instead.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid REDACTED:54— uuid 8.3.2, 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: uuid packages/modules/module-auth/REDACTED:29— uuid 8.3.2, declared in packages/modules/module-auth/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: better-sqlite3 REDACTED:32— better-sqlite3 7.4.3, declared in REDACTED, is marked deprecated by its publisher: "ancient versions of better-sqlite3 are not supported". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: uuid packages/runtime/adapters/readmodel-adapters/readmodel-base/REDACTED:31— uuid 8.3.2, declared in packages/runtime/adapters/readmodel-adapters/readmodel-base/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.
No assertions: login examples/js/hacker-news/test/e2e-docker/check-application.js: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: login examples/ts/hacker-news/test/e2e-docker/check-application.ts:10— 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: read model Init handler failed functional-tests/api/monitoring.test.ts:601— 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: read model event handler functional-tests/api/monitoring.test.ts:617— 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: api handler failed functional-tests/api/monitoring.test.ts:976— 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: collects errors thrown in lambda worker functional-tests/api/monitoring.test.ts:1059— 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: execute read-model query and check the result functional-tests/api/resolve-client/basic.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: create scenarios functional-tests/testcafe/redux-hooks/array-within-query-string.test.ts:13— 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: value values packages/core/core/test/helpers.unit.test.ts:22— 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: should use snapshots for building state 2 packages/core/core/test/get-aggregates-interop-builder.unit.test.ts:786— 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: should create and invoke logger packages/core/debug-levels/test/index.test.ts:101— 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: variadic builder generic arguments (compile time) packages/core/react-hooks/test/use-query-builder.unit.test.ts:41— 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: variadic builder generic arguments (compile time) packages/core/react-hooks/test/use-command-builder.unit.test.ts:55— 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: does not reject on publish if putMetricData is failed packages/runtime/adapters/monitoring-adapters/monitoring-aws-cloudwatch/test/index.test.ts:422— 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: connect and disconnect should be successful packages/runtime/adapters/replicators/replicator-via-api-handler/test/index.test.ts:13— 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: shouldExecuteCommand assertion packages/tools/testing-tools/test/saga.test.ts:243— 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: shouldExecuteQuery assertion packages/tools/testing-tools/test/saga.test.ts:261— 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: shouldExecuteCommand & shouldExecuteQuery simultaneously packages/tools/testing-tools/test/saga.test.ts:277— 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: shouldExecuteSideEffect packages/tools/testing-tools/test/saga.test.ts:301— 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: shouldExecuteSideEffect & shouldExecuteCommand packages/tools/testing-tools/test/saga.test.ts:312— 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: shouldExecuteSideEffect & shouldExecuteQuery packages/tools/testing-tools/test/saga.test.ts:331— 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: shouldExecuteSideEffect, shouldExecuteCommand & shouldExecuteQuery packages/tools/testing-tools/test/saga.test.ts:348— 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: #2075: sometimes input events order broken with mocked Date.now packages/tools/testing-tools/test/saga.test.ts:597— 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: shouldReturn assertion packages/tools/testing-tools/test/read-model.test.ts:102— 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: negated shouldReturn assertion packages/tools/testing-tools/test/read-model.test.ts:111— 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.
+ 21 more in this group — see findings.md.
D30 · Dependency Vulnerabilities· Medium CVE · ×40
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 15 more in this group — see findings.md.
P12 · CI test-gate honesty· Workspace package's tests never run by CI · ×40
Workspace package's tests never run by CI REDACTED:22— `examples/js/hacker-news` is a workspace package with 35 test(s) in 5 file(s) (e.g. `examples/js/hacker-news/test/unit/sagas/story-create-saga.test.js`, `examples/js/hacker-news/test/unit/sagas/optimistic-voting-saga.test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI examples/js/personal-data/REDACTED:11— `examples/js/personal-data` is a workspace package with 7 test(s) in 1 file(s) (e.g. `examples/js/personal-data/test/e2e/index.test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI examples/js/shopping-list-redux-hoc/REDACTED:14— `examples/js/shopping-list-redux-hoc` is a workspace package with 28 test(s) in 4 file(s) (e.g. `examples/js/shopping-list-redux-hoc/test/unit/view-models.test.js`, `examples/js/shopping-list-redux-hoc/test/unit/read-models.test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI examples/js/shopping-list-redux/REDACTED:14— `examples/js/shopping-list-redux` is a workspace package with 28 test(s) in 4 file(s) (e.g. `examples/js/shopping-list-redux/test/unit/view-models.test.js`, `examples/js/shopping-list-redux/test/unit/read-models.test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI examples/js/shopping-list/REDACTED:14— `examples/js/shopping-list` is a workspace package with 28 test(s) in 4 file(s) (e.g. `examples/js/shopping-list/test/unit/view-models.test.js`, `examples/js/shopping-list/test/unit/read-models.test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI examples/ts/hacker-news/REDACTED:22— `examples/ts/hacker-news` is a workspace package with 35 test(s) in 5 file(s) (e.g. `examples/ts/hacker-news/test/unit/sagas/story-create-saga.test.ts`, `examples/ts/hacker-news/test/unit/sagas/optimistic-voting-saga.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI examples/ts/personal-data/REDACTED:11— `examples/ts/personal-data` is a workspace package with 7 test(s) in 1 file(s) (e.g. `examples/ts/personal-data/test/e2e/index.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI examples/ts/shopping-list-redux-hoc/REDACTED:14— `examples/ts/shopping-list-redux-hoc` is a workspace package with 28 test(s) in 4 file(s) (e.g. `examples/ts/shopping-list-redux-hoc/test/unit/view-models.test.ts`, `examples/ts/shopping-list-redux-hoc/test/unit/read-models.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI examples/ts/shopping-list-redux/REDACTED:14— `examples/ts/shopping-list-redux` is a workspace package with 28 test(s) in 4 file(s) (e.g. `examples/ts/shopping-list-redux/test/unit/view-models.test.ts`, `examples/ts/shopping-list-redux/test/unit/read-models.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI examples/ts/shopping-list/REDACTED:14— `examples/ts/shopping-list` is a workspace package with 28 test(s) in 4 file(s) (e.g. `examples/ts/shopping-list/test/unit/view-models.test.ts`, `examples/ts/shopping-list/test/unit/read-models.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI REDACTED:9— `functional-tests` is a workspace package with 41 test(s) in 18 file(s) (e.g. `functional-tests/api/scheduler.test.ts`, `functional-tests/api/saga.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI REDACTED:24— `packages/core/client` is a workspace package with 95 test(s) in 8 file(s) (e.g. `packages/core/client/test/unit/subscription-adapter.unit.test.ts`, `packages/core/client/test/unit/subscribe.unit.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/core/core/REDACTED:24— `packages/core/core` is a workspace package with 63 test(s) in 6 file(s) (e.g. `packages/core/core/test/utils.unit.test.ts`, `packages/core/core/test/helpers.unit.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI REDACTED:23— `packages/core/create-resolve-app` is a workspace package with 20 test(s) in 10 file(s) (e.g. `packages/core/create-resolve-app/test/send-analytics.test.ts`, `packages/core/create-resolve-app/test/safe-name.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/core/debug-levels/REDACTED:23— `packages/core/debug-levels` is a workspace package with 4 test(s) in 1 file(s) (e.g. `packages/core/debug-levels/test/index.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/core/react-hooks/REDACTED:24— `packages/core/react-hooks` is a workspace package with 95 test(s) in 9 file(s) (e.g. `packages/core/react-hooks/test/use-view-model.unit.test.tsx`, `packages/core/react-hooks/test/use-static-resolver.unit.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI REDACTED:23— `packages/core/redux` is a workspace package with 126 test(s) in 13 file(s) (e.g. `packages/core/redux/test/create-resolve-store.test.ts`, `packages/core/redux/test/view-model/view-model-reducer.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/modules/module-admin/REDACTED:23— `packages/modules/module-admin` is a workspace package with 25 test(s) in 2 file(s) (e.g. `packages/modules/module-admin/test/index.test.js`, `packages/modules/module-admin/test/api-handlers.test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/modules/module-auth/REDACTED:22— `packages/modules/module-auth` is a workspace package with 17 test(s) in 3 file(s) (e.g. `packages/modules/module-auth/test/wrap_auth_request.test.js`, `packages/modules/module-auth/test/index.test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/modules/module-comments/REDACTED:22— `packages/modules/module-comments` is a workspace package with 9 test(s) in 2 file(s) (e.g. `packages/modules/module-comments/test/reducers/comments.test.js`, `packages/modules/module-comments/test/aggregates/comments.commands.test.js`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/runtime/adapters/eventstore-adapters/eventstore-base/REDACTED:23— `packages/runtime/adapters/eventstore-adapters/eventstore-base` is a workspace package with 23 test(s) in 10 file(s) (e.g. `packages/runtime/adapters/eventstore-adapters/eventstore-base/test/wrap-event-filter.test.ts`, `packages/runtime/adapters/eventstore-adapters/eventstore-base/test/wrap-dispose.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI REDACTED:23— `packages/runtime/adapters/eventstore-adapters/eventstore-lite` is a workspace package with 3 test(s) in 2 file(s) (e.g. `packages/runtime/adapters/eventstore-adapters/eventstore-lite/test/drop.unit.test.ts`, `packages/runtime/adapters/eventstore-adapters/eventstore-lite/test/connect.unit.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI REDACTED:23— `packages/runtime/adapters/eventstore-adapters/eventstore-mysql` is a workspace package with 7 test(s) in 3 file(s) (e.g. `packages/runtime/adapters/eventstore-adapters/eventstore-mysql/test/index.test.js`, `packages/runtime/adapters/eventstore-adapters/eventstore-mysql/test/drop.unit.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/REDACTED:23— `packages/runtime/adapters/eventstore-adapters/eventstore-postgresql` is a workspace package with 6 test(s) in 3 file(s) (e.g. `packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/test/load-events-by-timestamp.test.ts`, `packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/test/drop.unit.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Workspace package's tests never run by CI packages/runtime/adapters/monitoring-adapters/monitoring-aws-cloudwatch/REDACTED:23— `packages/runtime/adapters/monitoring-adapters/monitoring-aws-cloudwatch` is a workspace package with 27 test(s) in 1 file(s) (e.g. `packages/runtime/adapters/monitoring-adapters/monitoring-aws-cloudwatch/test/index.test.ts`), but no CI command runs them — no step names the package and no workspace-wide command reaches it, so its tests gate nothing. Run its tests in CI, or delete them.
Sync-over-async blocking packages/core/create-resolve-app/src/download-resolve-repo.ts:29— `fs.readdirSync` in `anonymous function` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/create-resolve-app/src/download-resolve-repo.ts:126— `fs.readdirSync` in `downloadResolveRepo` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/create-resolve-app/src/install.ts:28— `execSync` in `installDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/create-resolve-app/src/install.ts:36— `execSync` in `installDependencies` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/create-resolve-app/src/move-example.ts:27— `fs.readdirSync` in `moveExample` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/create-resolve-app/src/patch-package-json.ts:33— `fs.writeFileSync` in `patchPackageJson` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/create-resolve-app/src/patch-package-json.ts:39— `fs.readdirSync` in `patchPackageJson` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/core/create-resolve-app/src/patch-package-json.ts:84— `fs.writeFileSync` in `patchPackageJson` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:24— `fs.existsSync` in `eventStoreExportHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:25— `fs.mkdirSync` in `eventStoreExportHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:27— `fs.existsSync` in `eventStoreImportHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:31— `fs.existsSync` in `eventStoreImportHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:9— `fs.existsSync` in `eventStoreImportHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:43— `fs.existsSync` in `removeCallback` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:44— `fs.unlinkSync` in `removeCallback` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:48— `fs.existsSync` in `connector` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:49— `fs.writeFileSync` in `connector` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:122— `fs.existsSync` in `removeCallback` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:123— `fs.unlinkSync` in `removeCallback` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:127— `fs.existsSync` in `CurrentConnectMethod` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:128— `fs.writeFileSync` in `CurrentConnectMethod` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking packages/runtime/runtimes/runtime-aws-serverless/src/index.ts:16— `fs.existsSync` in `main` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:36— `fs.existsSync` in `uploaderHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:37— `fs.mkdirSync` in `uploaderHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking REDACTED:49— `fs.existsSync` in `uploaderHandler` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
+ 15 more in this group — see findings.md.
R4 · Test Coverage· No test reaches this file · ×40
No test reaches this file packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/modules/module-comments/src/common/read-models/comments.resolvers.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file internal/workspaces/bin/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/modules/module-comments/src/common/read-models/comments.projection.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file internal/babel-compile/bin/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/ts/styled-components/run.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/tools/scripts/src/alias/$resolve.readModel.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/modules/module-comments/src/common/index.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/js/styled-components/run.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/modules/module-comments/src/client/components/CommentsNotificationRenderless.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/ts/postcss/run.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 tutorial/lesson-5/client/components/ShoppingList.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/core/create-resolve-app/src/prepare-options.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/ts/react/run.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/ts/vue/run.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/js/postcss/run.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file tutorial/lesson-4/run.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file tutorial/lesson-5/run.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/ts/angular/run.ts:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/js/react/run.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/js/vue/run.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/tools/scripts/src/alias/$resolve.clientEntry.js:1— No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file templates/ts/vanilla/run.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.
Swallowed exception (empty catch) packages/core/client/src/subscribe.ts:174— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/client/src/subscribe.ts:187— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/core/src/helpers.ts:17— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/create-resolve-app/src/download-resolve-repo.ts:36— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/create-resolve-app/src/download-resolve-repo.ts:40— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/core/debug-levels/src/index.ts:68— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:15— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/modules/module-admin/src/utils/getEventDate.js:7— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-secrets.ts:217— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-events.ts:245— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/set-secret.ts:108— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/replicate-secrets.ts:63— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/replicate-events.ts:92— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/push-incremental-import.ts:53— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/delete-secret.ts:111— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/commit-incremental-import.ts:116— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/save-event.ts:86— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/push-incremental-import.ts:59— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/inject-event.ts:64— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/ensure-event-subscriber.ts:83— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/commit-incremental-import.ts:216— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/replicate-secrets.ts:63— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/replicate-events.ts:205— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/monitoring-adapters/monitoring-aws-cloudwatch/src/publish.ts:120— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/maybe-init.ts:32— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
FunctionTooLong: event-subscriber-notifier-factory.eventSubscriberNotifierFactory packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:83— FunctionTooLong — eventSubscriberNotifierFactory runs 315 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 215 over it, 3.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: build.build packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:764— FunctionTooLong — build runs 220 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 120 over it, 2.20× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: create-runtime.createRuntime packages/runtime/runtimes/runtime-base/src/create-runtime.ts:110— FunctionTooLong — createRuntime runs 192 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 92 over it, 1.92× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: build.build packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:459— FunctionTooLong — build runs 170 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 70 over it, 1.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: replicate-events.replicateEvents packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/replicate-events.ts:16— FunctionTooLong — replicateEvents runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: replicate.handler REDACTED:35— FunctionTooLong — handler runs 134 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 34 over it, 1.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: get-read-models-interop-builder.makeReadModelInteropCreator packages/core/core/src/read-model/get-read-models-interop-builder.ts:36— FunctionTooLong — makeReadModelInteropCreator runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: get-aggregates-interop-builder.makeCommandExecutor packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:414— FunctionTooLong — makeCommandExecutor runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: save-event.saveEvent packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/save-event.ts:20— FunctionTooLong — saveEvent runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: websocket-event-handler.handleWebsocketEvent packages/runtime/runtimes/runtime-aws-serverless/src/websocket-event-handler.ts:37— FunctionTooLong — handleWebsocketEvent runs 126 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 26 over it, 1.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: comments.projection.createCommentsProjection packages/modules/module-comments/src/common/read-models/comments.projection.js:3— FunctionTooLong — createCommentsProjection runs 125 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 25 over it, 1.25× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: get-aggregates-interop-builder.getAggregateState packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:229— FunctionTooLong — getAggregateState runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: get_webpack_common_configs.getWebpackCommonConfigs packages/tools/scripts/src/get_webpack_common_configs.js:9— FunctionTooLong — getWebpackCommonConfigs runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: comments.resolvers.createCommentsProjection packages/modules/module-comments/src/common/read-models/comments.resolvers.js:3— FunctionTooLong — createCommentsProjection runs 118 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 18 over it, 1.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: event-subscriber-notifier-factory.eventSubscriberNotifierFactory.ensureQueue packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:201— FunctionTooLong — eventSubscriberNotifierFactory.ensureQueue runs 117 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 17 over it, 1.17× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wrap-api-handler.createResponse packages/runtime/runtimes/runtime-aws-serverless/src/wrap-api-handler.ts:194— FunctionTooLong — createResponse runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wrap-api-handler.createResponse packages/runtime/runtimes/runtime-single-process/src/wrap-api-handler.ts:110— FunctionTooLong — createResponse runs 115 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 15 over it, 1.15× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: use-view-model.useViewModel packages/core/react-hooks/src/use-view-model.ts:91— FunctionTooLong — useViewModel runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: delete-secret.deleteSecret packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/delete-secret.ts:10— FunctionTooLong — deleteSecret runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: set-secret.setSecret packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/set-secret.ts:12— FunctionTooLong — setSecret runs 114 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 14 over it, 1.14× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: save-event.saveEvent packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/save-event.ts:17— FunctionTooLong — saveEvent runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: $resolve.viewModels.importViewModels packages/tools/scripts/src/alias/$resolve.viewModels.js:11— FunctionTooLong — importViewModels runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: wrap-procedure.wrapProcedure packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts:216— FunctionTooLong — wrapProcedure runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× 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.
X2 · Cancellation propagation· Async function without AbortSignal · ×22
Async function without AbortSignal: execFetch packages/core/client/src/middleware.ts:115— `execFetch` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/event-store/unfreeze.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/event-store/incremental-import.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/event-store/import.js:5— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/event-store/freeze.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/event-store/export.js:5— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/read-models/resume.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/read-models/reset.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/read-models/pause.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/read-models/list.js:6— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/sagas/resume.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/sagas/reset.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/sagas/pause.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/sagas/list.js:6— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/sagas/properties/set.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/sagas/properties/remove.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/sagas/properties/list.js:4— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/sagas/properties/get.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: handler packages/modules/module-admin/src/commands/system/status.js:3— `handler` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: DropReadModelMethod packages/runtime/adapters/replicators/replicator-via-api-handler/src/drop-read-model.ts:7— `DropReadModelMethod` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: openBrowser packages/tools/scripts/src/open_browser.js:9— `openBrowser` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Async function without AbortSignal: waitForUrl packages/tools/scripts/src/generate_custom_mode.js:18— `waitForUrl` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.
Fake-async — async method never awaits packages/core/client/src/subscribe.ts:200— `connect` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/core/create-resolve-app/src/check-application-name.ts:4— `checkApplicationName` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/core/create-resolve-app/src/install.ts:21— `installDependencies` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/core/create-resolve-app/src/move-example.ts:12— `moveExample` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/core/create-resolve-app/src/patch-package-json.ts:7— `patchPackageJson` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/core/create-resolve-app/src/print-finish-output.ts:6— `printFinishOutput` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/modules/module-admin/src/api-handlers/system-status-handler.js:3— `systemStatusHandler` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/modules/module-auth/src/logout_api_handler.js:3— `logoutApiHandler` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/modules/module-auth/src/send_auth_response.js:1— `sendAuthResponse` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/inject-events.ts:4— `injectEvents` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/runtime/adapters/replicators/replicator-via-api-handler/src/connect.ts:3— `connect` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/runtime/runtimes/runtime-aws-serverless/src/compile-time/index.ts:14— `adjustResolveConfig` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/runtime/runtimes/runtime-base/src/command.ts:23— `dispose` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/runtime/runtimes/runtime-single-process/src/compile-time/index.ts:3— `adjustResolveConfig` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits packages/runtime/runtimes/runtime-single-process/src/websocket-server-factory.ts:155— `initWebSocketServer` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Off the main sequence: @resolve-js/debug-levels — @resolve-js/debug-levels: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 16 project(s), so it's rigid to change.
Off the main sequence: @resolve-js/readmodel-lite — @resolve-js/readmodel-lite: abstractness 0.00, instability 0.06, distance 0.94 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
Off the main sequence: @resolve-js/readmodel-postgresql — @resolve-js/readmodel-postgresql: abstractness 0.00, instability 0.11, distance 0.89 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
Off the main sequence: @resolve-js/react-hooks — @resolve-js/react-hooks: abstractness 0.00, instability 0.14, distance 0.86 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
Off the main sequence: @resolve-js/core — @resolve-js/core: abstractness 0.10, instability 0.05, distance 0.85 — zone of pain — concrete and depended on by 21 project(s), so it's rigid to change.
Off the main sequence: @resolve-js/eventstore-lite — @resolve-js/eventstore-lite: abstractness 0.00, instability 0.15, distance 0.85 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
Off the main sequence: @resolve-js/eventstore-postgresql — @resolve-js/eventstore-postgresql: abstractness 0.00, instability 0.15, distance 0.85 — zone of pain — concrete and depended on by 17 project(s), so it's rigid to change.
Off the main sequence: @resolve-js/readmodel-base — @resolve-js/readmodel-base: abstractness 0.00, instability 0.20, distance 0.80 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.
Off the main sequence: @resolve-js/eventstore-base — @resolve-js/eventstore-base: abstractness 0.06, instability 0.18, distance 0.75 — zone of pain — concrete and depended on by 9 project(s), so it's rigid to change.
FixmeComment packages/core/core/src/aggregate/validate-aggregate.ts:3— // FIXME: add validation (io-ts?) — 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.
FixmeComment packages/core/core/src/read-model/validate-read-model.ts:3— // FIXME: add validation (io-ts?) — 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.
FixmeComment packages/core/core/src/saga/validate-saga.ts:3— // FIXME: add validation (io-ts?) — 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.
FixmeComment packages/core/core/src/view-model/validate-view-model.ts:3— // FIXME: add validation (io-ts?) — 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.
FixmeComment packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:207— // FIXME: move snapshot business logic from runtime — 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.
FixmeComment packages/tools/testing-tools/test/aggregate.test.ts:205— // FIXME: something wrong with resolve-command, fix after its relocation — 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.
Boundary violation [package:third-party-deep-import] internal/babel-compile/bin/index.js:7— internal/babel-compile/bin/index.js:7 imports @babel/cli/lib/babel/dir, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:relative-cross-package] internal/helpers/get-babel-config.js:10— internal/helpers/get-babel-config.js:10 reaches into another package with a relative path (../babel-compile/REDACTED) — import the package by name instead.
Boundary violation [package:third-party-deep-import] packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts:23— packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts:23 imports io-ts/lib/PathReporter, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] templates/js/vue/config.adjust-webpack.js:1— templates/js/vue/config.adjust-webpack.js:1 imports vue-loader/lib/plugin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] templates/ts/angular/client/main.ts:4— templates/ts/angular/client/main.ts:4 imports zone.js/dist/zone, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] templates/ts/vue/config.adjust-webpack.ts:1— templates/ts/vue/config.adjust-webpack.ts:1 imports vue-loader/lib/plugin, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
`async` Promise executor packages/runtime/runtimes/runtime-aws-serverless/src/uploader-factory.ts:75— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/runtime/runtimes/runtime-aws-serverless/src/uploader-factory.ts:150— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor REDACTED:36— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor REDACTED:77— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/tools/scripts/src/start_mode.js:9— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
`async` Promise executor packages/tools/scripts/src/generate_custom_mode.js:49— The function passed to `new Promise(…)` is `async`. The constructor ignores what its executor returns, so anything this executor throws — every throw inside an `async` function, including after an `await` — rejects a Promise nobody holds instead of the one being constructed: the outer Promise never settles, whoever awaits it hangs, and the error is reported nowhere. If the body needs `await`, it does not need `new Promise` at all: make the enclosing function `async` and `return` the value (or `throw`) directly. If it wraps a callback API, keep the executor synchronous — call the API and `resolve`/`reject` from its callback — and do the awaiting outside it.
FileTooLong: src/build.ts packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts— FileTooLong — 791 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 291 over it, 1.58× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: src/types.ts packages/runtime/adapters/readmodel-adapters/readmodel-base/src/types.ts— FileTooLong — 589 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 89 over it, 1.18× 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/build.ts packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts— FileTooLong — 512 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 12 over it, 1.02× 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.
Dead file (~73 LoC) packages/modules/module-auth/src/execute_strategy.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/modules/module-auth/src/api_handler_constructor.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~73 LoC) templates/ts/react/client/components/MyAggregateItems.tsx— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/react/client/components/MyAggregateList.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~73 LoC) tutorial/lesson-5/common/aggregates/shopping_list.commands.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~50 LoC) templates/js/vanilla/client/index.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~50 LoC) templates/ts/react/client/containers/App.tsx— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/react/client/index.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~50 LoC) templates/ts/vanilla/client/init-ui.ts— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/vanilla/client/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
search-to-where-expression.searchToWhereExpression (cyclomatic 16) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/search-to-where-expression.ts:34— search-to-where-expression.searchToWhereExpression 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.
search-to-where-expression.searchToWhereExpression (cyclomatic 16) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/search-to-where-expression.ts:34— search-to-where-expression.searchToWhereExpression 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.
Skipped test: Test performance packages/runtime/adapters/eventstore-adapters/eventstore-base/test/thread-array-to-cursor.test.ts:40— Skipped — switched off by test.skip
Skipped test: Test performance packages/runtime/adapters/eventstore-adapters/eventstore-base/test/cursor-to-thread-array.test.ts:40— Skipped — switched off by test.skip
search-to-where-expression.searchToWhereExpression (cognitive 32) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/search-to-where-expression.ts:34— search-to-where-expression.searchToWhereExpression has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 3 (9 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
search-to-where-expression.searchToWhereExpression (cognitive 32) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/search-to-where-expression.ts:34— search-to-where-expression.searchToWhereExpression has cognitive complexity 32 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 3 (9 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Outbound HTTP without resilience REDACTED:38— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Outbound HTTP without resilience REDACTED:79— `fetch(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
R10 · Code Duplication· Duplicated block with local edits (75 matched lines × 2 locations) · ×2
Duplicated block with local edits (75 matched lines × 2 locations) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/update-to-set-expression.ts:16— packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/update-to-set-expression.ts:16 · packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/update-to-set-expression.ts:17 — the two spans are one implementation copied and then locally edited — 351 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (75 matched lines × 2 locations) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/status.ts:13— packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/status.ts:13 · packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/status.ts:16 — the two spans are one implementation copied and then locally edited — 360 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (52 matched lines × 2 locations) · ×2
Duplicated block with local edits (52 matched lines × 2 locations) packages/core/redux/src/read-model/actions.ts:19— packages/core/redux/src/read-model/actions.ts:19 · packages/core/redux/src/view-model/actions.ts:48 — the two spans are one implementation copied and then locally edited — 179 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block with local edits (52 matched lines × 2 locations) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/set-replication-status.ts:17— packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/set-replication-status.ts:17 · packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/set-replication-status.ts:18 — the two spans are one implementation copied and then locally edited — 121 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Wholesale file copy (52 identical lines × 2 files) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/index.ts:5— packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/index.ts:5 · packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/index.ts:1 — these 2 files are line-for-line copies of one another — 52 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.
Wholesale file copy (52 identical lines × 2 files) templates/ts/postcss/client/containers/Header.tsx:1— templates/ts/postcss/client/containers/Header.tsx:1 · templates/ts/styled-components/client/containers/Header.tsx:1 — these 2 files are line-for-line copies of one another — 52 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.
Dead file (~69 LoC) templates/ts/postcss/client/containers/Header.tsx— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/postcss/client/components/App.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~69 LoC) templates/ts/styled-components/client/containers/Header.tsx— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/styled-components/client/components/App.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~68 LoC) packages/runtime/runtimes/runtime-aws-serverless/src/compile-time/index.ts— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/runtime/runtimes/runtime-aws-serverless/compile-time.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~68 LoC) templates/js/styled-components/client/ssr.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~64 LoC) templates/js/react/client/components/MyAggregateItems.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/js/react/client/components/MyAggregateList.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~64 LoC) templates/ts/vanilla/client/index.ts— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~58 LoC) tutorial/lesson-4/client/components/ShoppingList.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-4/client/routes.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~58 LoC) tutorial/lesson-5/common/view-models/shopping_list.projection.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~46 LoC) packages/modules/module-auth/src/api_handler_constructor.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~46 LoC) templates/js/react/client/containers/App.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/js/react/client/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~40 LoC) templates/js/vanilla/client/init-ui.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/js/vanilla/client/index.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~40 LoC) tutorial/lesson-5/client/components/ShoppingLists.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-5/client/components/MyLists.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~38 LoC) packages/modules/module-replication/src/api-handlers/replication_state.ts— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~38 LoC) tutorial/lesson-3/client/components/Header.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-3/client/components/App.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
build.buildEvents (cyclomatic 90) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:154— build.buildEvents has cyclomatic complexity 90 (threshold 15). Of this number, 76 points are the body's own statements and 14 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
build.build (cyclomatic 50) packages/runtime/adapters/replicators/replicator-via-api-handler/src/build.ts:37— build.build has cyclomatic complexity 50 (threshold 15). Of this number, 44 points are the body's own statements and 6 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
update-to-set-expression.updateToSetExpression (cyclomatic 48) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/update-to-set-expression.ts:10— update-to-set-expression.updateToSetExpression has cyclomatic complexity 48 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
build.build (cyclomatic 38) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:459— build.build has cyclomatic complexity 38 (threshold 15). Of this number, 37 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
build.build (cyclomatic 37) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:764— build.build has cyclomatic complexity 37 (threshold 15). Of this number, 36 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
make-sql-query.makeSqlQuery (cyclomatic 36) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/make-sql-query.ts:10— make-sql-query.makeSqlQuery has cyclomatic complexity 36 (threshold 15). Of this number, 29 points are the body's own statements and 7 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.
lambda-worker.lambdaWorker (cyclomatic 33) packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:102— lambda-worker.lambdaWorker has cyclomatic complexity 33 (threshold 15). Of this number, 31 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
build.buildEvents (cyclomatic 31) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:159— build.buildEvents has cyclomatic complexity 31 (threshold 15). Of this number, 28 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
connect.connect (cyclomatic 29) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/connect.ts:11— connect.connect has cyclomatic complexity 29 (threshold 15). Most of this is not in the body itself: 12 of the 29 points are its own statements and the rest belongs to 5 function items inside it that branch (inlineLedgerRunQuery, maybeThrowConnectionErrors, ensureAffectedOperation, …). 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.
execute-statement.executeStatement (cyclomatic 28) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/execute-statement.ts:20— execute-statement.executeStatement has cyclomatic complexity 28 (threshold 15). Of this number, 27 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
event-subscriber-notifier-factory.eventSubscriberNotifierFactory.ensureQueue (cyclomatic 28) packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:201— event-subscriber-notifier-factory.eventSubscriberNotifierFactory.ensureQueue has cyclomatic complexity 28 (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.
event-subscriber-notifier-factory.eventSubscriberNotifierFactory.deleteQueue (cyclomatic 26) packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:368— event-subscriber-notifier-factory.eventSubscriberNotifierFactory.deleteQueue has cyclomatic complexity 26 (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.
get-aggregates-interop-builder.getAggregateState (cyclomatic 24) packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:229— get-aggregates-interop-builder.getAggregateState has cyclomatic complexity 24 (threshold 15). Of this number, 13 points are the body's own statements and 11 belong to 4 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
comments.createCommentsReducer (cyclomatic 22) packages/modules/module-comments/src/client/reducers/comments.js:12— comments.createCommentsReducer has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 2 function literals inside it that branch (lines 17, 111). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
comments.resolvers.createCommentsProjection (cyclomatic 22) packages/modules/module-comments/src/common/read-models/comments.resolvers.js:3— comments.resolvers.createCommentsProjection has cyclomatic complexity 22 (threshold 15). Most of this is not in the body itself: 1 of the 22 points is its own statement and the rest belongs to 3 function literals inside it that branch (lines 8, 91, 145). 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.
commit-incremental-import.commitIncrementalImport (cyclomatic 22) packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/commit-incremental-import.ts:4— commit-incremental-import.commitIncrementalImport has cyclomatic complexity 22 (threshold 15). Of this number, 18 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
use-redux-read-model.useReduxReadModel (cyclomatic 21) packages/core/redux/src/read-model/use-redux-read-model.ts:117— use-redux-read-model.useReduxReadModel has cyclomatic complexity 21 (threshold 15). Of this number, 14 points are the body's own statements and 7 belong to 3 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
replicate-events.replicateEvents (cyclomatic 21) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/replicate-events.ts:16— replicate-events.replicateEvents has cyclomatic complexity 21 (threshold 15). Of this number, 17 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
build.buildEvents (cyclomatic 21) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:123— build.buildEvents has cyclomatic complexity 21 (threshold 15). Of this number, 19 points are the body's own statements and 2 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
uploader-handler.uploaderHandler (cyclomatic 21) REDACTED:22— uploader-handler.uploaderHandler has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
commit-incremental-import.commitIncrementalImport (cyclomatic 20) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/commit-incremental-import.ts:3— commit-incremental-import.commitIncrementalImport has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
status.status (cyclomatic 20) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/status.ts:16— status.status has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
replicate.handler (cyclomatic 19) REDACTED:35— replicate.handler has cyclomatic complexity 19 (threshold 15). Of this number, 11 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
update-to-set-expression.updateToSetExpression (cyclomatic 19) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/update-to-set-expression.ts:7— update-to-set-expression.updateToSetExpression 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.
wrap-procedure.wrapProcedure (cyclomatic 19) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts:216— wrap-procedure.wrapProcedure 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 216, 255). 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.
middleware.requestWithMiddleware (cyclomatic 18) packages/core/client/src/middleware.ts:43— middleware.requestWithMiddleware 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 4 function items inside it that branch (execFetch::processRun, execFetch, execMiddleware, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
comments.commands.createCommentsCommands (cyclomatic 18) packages/modules/module-comments/src/common/aggregates/comments.commands.js:3— comments.commands.createCommentsCommands 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 3 function literals inside it that branch (lines 10, 57, 94). 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.
save-event.saveEvent (cyclomatic 18) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/save-event.ts:17— save-event.saveEvent 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.
update-to-set-expression.updateToSetExpression (cyclomatic 18) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/update-to-set-expression.ts:7— update-to-set-expression.updateToSetExpression 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.
get-aggregates-interop-builder.makeCommandExecutor (cyclomatic 17) packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:414— get-aggregates-interop-builder.makeCommandExecutor 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 3 function items inside it that branch (a function literal at line 452, commandHandler, a function literal at line 559). 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.
import-events.EventStream._write (cyclomatic 17) packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-events.ts:103— import-events.EventStream._write 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.
import-secrets.SecretsStream._write (cyclomatic 17) packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-secrets.ts:48— import-secrets.SecretsStream._write 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.
build.build (cyclomatic 17) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:348— build.build 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.
client.query (cyclomatic 16) packages/core/client/src/client.ts:125— client.query has cyclomatic complexity 16 (threshold 15). Of this number, 8 points are the body's own statements and 8 belong to one function item inside it that branches. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ensure-connect.ensureConnect (cyclomatic 16) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:17— ensure-connect.ensureConnect has cyclomatic complexity 16 (threshold 15). Of this number, 15 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
with-performance-tracer.withPerformanceTracerImpl (cyclomatic 16) packages/runtime/adapters/readmodel-adapters/readmodel-base/src/with-performance-tracer.ts:9— with-performance-tracer.withPerformanceTracerImpl 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.
resubscribe.resubscribe (cyclomatic 16) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/resubscribe.ts:3— resubscribe.resubscribe 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.
eventStoreImportHandler (cyclomatic 16) REDACTED:4— eventStoreImportHandler has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 35, a function literal at line 59, a function literal at line 29, …). 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.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: packages/runtime/adapters/replicators/replicator-via-api-handler packages/runtime/adapters/replicators/replicator-via-api-handler/test/index.test.ts:13— No conventional assertion call was detected in 1 of 1 tests in `packages/runtime/adapters/replicators/replicator-via-api-handler` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
Races the wall clock: should pass security context to command handler packages/core/core/test/get-aggregates-interop-builder.unit.test.ts:250— This test reads `Date.now()` and compares it against the value the code under test computed from its own clock read, compared exactly in `toEqual({ aggregateId: ' ', aggregateVersion: 1, type: ' ', payload: { id: ' ', }, timestamp: Date.now(), threadId: 0, threadCounter: 0, })`. Those are two independent clock reads, so the test passes only while no boundary falls between them — a second ticking over between the code's read and the test's, or, for a date, a day that differs between the machine's local zone and UTC. It passes or fails on the time of day and the build agent's time zone, and re-running the suite on one machine cannot reveal it. Read the clock once: give the code under test a clock the test controls (a fake time provider, fake timers with a fixed system time) and build the expectation from that same instant, or assert a range rather than an exact value.
HackComment tests/eventstore-save-load/index.test.ts:61— // hack for sqlite - it might save events too fast, but we want to ensure different timestamps — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
build.buildEvents (cognitive 170) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:154— build.buildEvents has cognitive complexity 170 (threshold 15). Drivers by points: if/else 41 (107 pts), boolean chains 25, ternaries 10 (21 pts), error handling 6 (13 pts), loops 2 (4 pts) (nesting depth added 86). Of this number, 158 points are the body's own statements and 12 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
update-to-set-expression.updateToSetExpression (cognitive 107) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/update-to-set-expression.ts:10— update-to-set-expression.updateToSetExpression has cognitive complexity 107 (threshold 15). Drivers by points: ternaries 11 (55 pts), if/else 18 (33 pts), loops 8 (13 pts), boolean chains 4, match/switch 1 (2 pts) (nesting depth added 65). 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.
build.build (cognitive 87) packages/runtime/adapters/replicators/replicator-via-api-handler/src/build.ts:37— build.build has cognitive complexity 87 (threshold 15). Drivers by points: if/else 39 (67 pts), error handling 6 (8 pts), boolean chains 4, loops 2 (4 pts), ternaries 3 (4 pts) (nesting depth added 33). Of this number, 80 points are the body's own statements and 7 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
update-to-set-expression.updateToSetExpression (cognitive 69) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/update-to-set-expression.ts:7— update-to-set-expression.updateToSetExpression has cognitive complexity 69 (threshold 15). Drivers by points: ternaries 11 (53 pts), if/else 4 (10 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 51). 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.
update-to-set-expression.updateToSetExpression (cognitive 65) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/update-to-set-expression.ts:7— update-to-set-expression.updateToSetExpression has cognitive complexity 65 (threshold 15). Drivers by points: ternaries 10 (49 pts), if/else 4 (10 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 48). 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.
build.build (cognitive 63) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:459— build.build has cognitive complexity 63 (threshold 15). Drivers by points: if/else 12 (25 pts), ternaries 10 (17 pts), error handling 5 (10 pts), boolean chains 6, loops 4 (5 pts) (nesting depth added 26). Of this number, 62 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
event-subscriber-notifier-factory.eventSubscriberNotifierFactory.deleteQueue (cognitive 61) packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:368— event-subscriber-notifier-factory.eventSubscriberNotifierFactory.deleteQueue has cognitive complexity 61 (threshold 15). Drivers by points: if/else 9 (27 pts), error handling 11 (26 pts), loops 3 (6 pts), boolean chains 2 (nesting depth added 36). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
execute-statement.executeStatement (cognitive 58) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/execute-statement.ts:20— execute-statement.executeStatement has cognitive complexity 58 (threshold 15). Drivers by points: if/else 22 (49 pts), boolean chains 4, error handling 2 (4 pts), loops 1 (nesting depth added 29). Of this number, 57 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.
build.buildEvents (cognitive 53) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:159— build.buildEvents has cognitive complexity 53 (threshold 15). Drivers by points: if/else 15 (28 pts), error handling 5 (10 pts), ternaries 5 (8 pts), boolean chains 4, loops 3 (nesting depth added 21). Of this number, 49 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
event-subscriber-notifier-factory.eventSubscriberNotifierFactory.ensureQueue (cognitive 51) packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:201— event-subscriber-notifier-factory.eventSubscriberNotifierFactory.ensureQueue has cognitive complexity 51 (threshold 15). Drivers by points: error handling 13 (24 pts), if/else 9 (22 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.buildEvents (cognitive 46) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:123— build.buildEvents has cognitive complexity 46 (threshold 15). Drivers by points: if/else 11 (26 pts), ternaries 4 (10 pts), error handling 2 (5 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 25). Of this number, 45 points are the body's own statements and 1 belongs to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.build (cognitive 46) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:764— build.build has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 7, error handling 4 (7 pts), loops 3 (4 pts), ternaries 4 (nesting depth added 13). Of this number, 45 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
make-sql-query.makeSqlQuery (cognitive 43) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/make-sql-query.ts:10— make-sql-query.makeSqlQuery has cognitive complexity 43 (threshold 15). Drivers by points: ternaries 18 (37 pts), boolean chains 3, if/else 1 (2 pts), match/switch 1 (nesting depth added 20). Of this number, 33 points are the body's own statements and 10 belong to 2 function literals inside it that branch. The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
lambda-worker.lambdaWorker (cognitive 41) packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:102— lambda-worker.lambdaWorker has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 8, error handling 2 (3 pts), loops 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 12). Of this number, 39 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.
commit-incremental-import.commitIncrementalImport (cognitive 38) packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/commit-incremental-import.ts:4— commit-incremental-import.commitIncrementalImport has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 5 (10 pts), loops 4 (8 pts), boolean chains 4, error handling 2 (3 pts) (nesting depth added 16). Of this number, 30 points are the body's own statements and 8 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.
ensure-connect.ensureConnect (cognitive 35) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-connect.ts:17— ensure-connect.ensureConnect has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (29 pts), loops 2 (3 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 16). Of this number, 32 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
status.status (cognitive 35) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/status.ts:16— status.status has cognitive complexity 35 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 6, error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
commit-incremental-import.commitIncrementalImport (cognitive 34) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/commit-incremental-import.ts:3— commit-incremental-import.commitIncrementalImport has cognitive complexity 34 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 4 (8 pts), ternaries 4 (8 pts), boolean chains 4, error handling 1 (nesting depth added 14). Of this number, 26 points are the body's own statements and 8 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.
replicate-events.replicateEvents (cognitive 32) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/replicate-events.ts:16— replicate-events.replicateEvents has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 3 (5 pts), loops 5, ternaries 3 (5 pts), boolean chains 1 (nesting depth added 10). Of this number, 24 points are the body's own statements and 8 belong to 2 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
uploader-handler.uploaderHandler (cognitive 32) REDACTED:22— uploader-handler.uploaderHandler has cognitive complexity 32 (threshold 15). Drivers by points: if/else 15 (24 pts), boolean chains 4, ternaries 1 (3 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
replicate.handler (cognitive 31) REDACTED:35— replicate.handler has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (20 pts), error handling 6 (10 pts), boolean chains 1 (nesting depth added 9). Of this number, 16 points are the body's own statements and 15 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resubscribe.resubscribe (cognitive 31) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/resubscribe.ts:3— resubscribe.resubscribe has cognitive complexity 31 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 4 (8 pts), error handling 3 (7 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resubscribe.resubscribe (cognitive 30) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/resubscribe.ts:3— resubscribe.resubscribe has cognitive complexity 30 (threshold 15). Drivers by points: if/else 4 (14 pts), error handling 4 (10 pts), ternaries 2 (4 pts), loops 2 (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.
search-to-where-expression.searchToWhereExpression (cognitive 29) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/search-to-where-expression.ts:34— search-to-where-expression.searchToWhereExpression has cognitive complexity 29 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 3 (6 pts), ternaries 2 (6 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
websocket-event-handler.handleWebsocketEvent (cognitive 29) packages/runtime/runtimes/runtime-aws-serverless/src/websocket-event-handler.ts:37— websocket-event-handler.handleWebsocketEvent has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 4 (12 pts), error handling 4 (11 pts), if/else 1 (3 pts), match/switch 2 (3 pts) (nesting depth added 18). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
import-secrets.SecretsStream._write (cognitive 27) packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-secrets.ts:48— import-secrets.SecretsStream._write has cognitive complexity 27 (threshold 15). Drivers by points: if/else 15 (22 pts), error handling 2 (3 pts), boolean chains 1, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
replicate-secrets.replicateSecrets (cognitive 27) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/replicate-secrets.ts:5— replicate-secrets.replicateSecrets has cognitive complexity 27 (threshold 15). Drivers by points: ternaries 5 (13 pts), if/else 4 (6 pts), error handling 2 (5 pts), boolean chains 3 (nesting depth added 13). Of this number, 24 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-redux-read-model.useReduxReadModel (cognitive 26) packages/core/redux/src/read-model/use-redux-read-model.ts:117— use-redux-read-model.useReduxReadModel has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (16 pts), boolean chains 7, ternaries 3 (nesting depth added 5). Of this number, 13 points are the body's own statements and 13 belong to 3 function items inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
build.buildInit (cognitive 26) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:24— build.buildInit has cognitive complexity 26 (threshold 15). Drivers by points: if/else 8 (15 pts), error handling 4 (8 pts), loops 2, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
connect.connect (cognitive 26) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:93— connect.connect has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (18 pts), error handling 2 (4 pts), loops 2, boolean chains 1, ternaries 1 (nesting depth added 11). Of this number, 23 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
unsubscribe.unsubscribe (cognitive 26) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/unsubscribe.ts:3— unsubscribe.unsubscribe has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (14 pts), error handling 4 (10 pts), loops 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
reset.reset (cognitive 26) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/reset.ts:3— reset.reset has cognitive complexity 26 (threshold 15). Drivers by points: if/else 4 (14 pts), error handling 4 (10 pts), loops 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
import-events.EventStream._write (cognitive 25) packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-events.ts:103— import-events.EventStream._write has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), error handling 2 (3 pts), boolean chains 2, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
subscribe.subscribe (cognitive 25) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/subscribe.ts:3— subscribe.subscribe has cognitive complexity 25 (threshold 15). Drivers by points: if/else 3 (8 pts), ternaries 4 (8 pts), error handling 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
get-aggregates-interop-builder.getAggregateState (cognitive 24) packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:229— get-aggregates-interop-builder.getAggregateState has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5, error handling 4, ternaries 3, loops 1 (nesting depth added 2). Most of this is not in the body itself: 11 of the 24 points are its own statements and the rest belongs to 4 function items inside it that branch (a function literal at line 296, a function literal at line 362, eventHandler, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
publish.monitoringPublish (cognitive 24) packages/runtime/adapters/monitoring-adapters/monitoring-aws-cloudwatch/src/publish.ts:105— publish.monitoringPublish has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (10 pts), loops 5 (10 pts), boolean chains 2, error handling 2 (nesting depth added 9). Most of this is not in the body itself: 3 of the 24 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 125, 139). 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.
comments.resolvers.createCommentsProjection (cognitive 23) packages/modules/module-comments/src/common/read-models/comments.resolvers.js:3— comments.resolvers.createCommentsProjection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5, loops 2 (3 pts), ternaries 2 (nesting depth added 4). None of this is in the body itself: all 23 points belong to 3 function literals inside it that branch (lines 8, 91, 145). 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.
save-event.saveEvent (cognitive 23) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/save-event.ts:17— save-event.saveEvent has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (5 pts), boolean chains 4, loops 2, error handling 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.
replicate-secrets.replicateSecrets (cognitive 23) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/replicate-secrets.ts:4— replicate-secrets.replicateSecrets has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 4 (6 pts), error handling 2 (5 pts), boolean chains 2 (nesting depth added 11). Of this number, 20 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
unsubscribe.unsubscribe (cognitive 23) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/unsubscribe.ts:3— unsubscribe.unsubscribe has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (11 pts), error handling 3 (7 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wrap-procedure.wrapProcedure (cognitive 23) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts:216— wrap-procedure.wrapProcedure has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6, error handling 3 (5 pts), loops 1 (nesting depth added 6). None of this is in the body itself: all 23 points belong to 2 function literals inside it that branch (lines 216, 255). 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.
connect.inlineLedgerRunQuery (cognitive 21) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/connect.ts:11— connect.inlineLedgerRunQuery has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), error handling 1 (2 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
status.status (cognitive 21) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/status.ts:13— status.status has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
middleware.requestWithMiddleware (cognitive 20) packages/core/client/src/middleware.ts:43— middleware.requestWithMiddleware has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), error handling 2 (3 pts), boolean chains 2, loops 1, match/switch 1 (nesting depth added 5). None of this is in the body itself: all 20 points belong to 4 function items inside it that branch (execMiddleware, execFetch::processRun, execFetch, …). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
build.build (cognitive 20) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:348— build.build has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (8 pts), boolean chains 5, ternaries 4, error handling 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
resubscribe.resubscribe (cognitive 20) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/resubscribe.ts:3— resubscribe.resubscribe has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (8 pts), if/else 2 (6 pts), error handling 2 (4 pts), loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
client.query (cognitive 19) packages/core/client/src/client.ts:125— client.query has cognitive complexity 19 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 3). Of this number, 10 points are the body's own statements and 9 belong to one function item inside it that branches. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, 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.
comments.projection.createCommentsProjection (cognitive 19) packages/modules/module-comments/src/common/read-models/comments.projection.js:3— comments.projection.createCommentsProjection has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (11 pts), ternaries 2 (4 pts), boolean chains 2, loops 2 (nesting depth added 7). None of this is in the body itself: all 19 points belong to one function literal inside it that branches (line 26). 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.
replicate-events.replicateEvents (cognitive 19) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/replicate-events.ts:7— replicate-events.replicateEvents has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 4 (7 pts), if/else 4 (5 pts), error handling 2 (3 pts), boolean chains 2, loops 2 (nesting depth added 5). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
connect.inlineLedgerRunQuery (cognitive 19) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/connect.ts:27— connect.inlineLedgerRunQuery has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (14 pts), error handling 1 (2 pts), ternaries 2, loops 1 (nesting depth added 9). Of this number, 18 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.
connect.connect::inlineLedgerRunQuery (cognitive 19) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/connect.ts:123— connect.connect::inlineLedgerRunQuery has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (15 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
$resolve.seedClientEnvs.seedClientEnvs (cognitive 19) packages/tools/scripts/src/alias/$resolve.seedClientEnvs.js:9— $resolve.seedClientEnvs.seedClientEnvs has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (12 pts), loops 3 (4 pts), ternaries 2, boolean chains 1 (nesting depth added 5). Of this number, 18 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
get-resolve-examples.getResolveExamples (cognitive 18) internal/helpers/get-resolve-examples.js:6— get-resolve-examples.getResolveExamples has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), boolean chains 3, ternaries 2 (3 pts), loops 1 (nesting depth added 6). Of this number, 15 points are the body's own statements and 3 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
subscribe.refreshSubscriptionAdapter (cognitive 18) packages/core/client/src/subscribe.ts:106— subscribe.refreshSubscriptionAdapter has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (13 pts), error handling 3 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
use-redux-command.useReduxCommand (cognitive 18) packages/core/redux/src/command/use-redux-command.ts:87— use-redux-command.useReduxCommand has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 4, ternaries 3 (nesting depth added 4). Most of this is not in the body itself: 5 of the 18 points are its own statements and the rest belongs to 3 function items inside it that branch (callback, a function literal at line 139, a function literal at line 138). 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.
export-events.generator (cognitive 18) packages/runtime/adapters/eventstore-adapters/eventstore-base/src/export-events.ts:78— export-events.generator has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (15 pts), loops 2 (3 pts) (nesting depth added 10). Of this number, 16 points are the body's own statements and 2 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
save-event.saveEvent (cognitive 18) packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/save-event.ts:14— save-event.saveEvent has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 5, if/else 4 (5 pts), ternaries 3 (5 pts), error handling 2 (3 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wrap-api-handler.createRequest (cognitive 18) packages/runtime/runtimes/runtime-aws-serverless/src/wrap-api-handler.ts:115— wrap-api-handler.createRequest has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), loops 2 (6 pts), boolean chains 1, 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.
get-aggregates-interop-builder.makeCommandExecutor (cognitive 17) packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:414— get-aggregates-interop-builder.makeCommandExecutor has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), error handling 3, ternaries 3, boolean chains 2 (nesting depth added 1). None of this is in the body itself: all 17 points belong to 3 function items inside it that branch (a function literal at line 452, commandHandler, a function literal at line 559). 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.
comments.createCommentsReducer (cognitive 17) packages/modules/module-comments/src/client/reducers/comments.js:12— comments.createCommentsReducer has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (8 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 2). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 17, 111). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
comments.commands.createCommentsCommands (cognitive 17) packages/modules/module-comments/src/common/aggregates/comments.commands.js:3— comments.commands.createCommentsCommands has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9, boolean chains 8. None of this is in the body itself: all 17 points belong to 3 function literals inside it that branch (lines 10, 57, 94). 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.
delete-secret.deleteSecret (cognitive 17) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/delete-secret.ts:11— delete-secret.deleteSecret has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (7 pts), ternaries 2 (4 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
subscribe.subscribe (cognitive 17) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/subscribe.ts:3— subscribe.subscribe has cognitive complexity 17 (threshold 15). Drivers by points: if/else 2 (7 pts), error handling 2 (5 pts), ternaries 2 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
extract-request-body.extractRequestBody (cognitive 17) packages/runtime/runtimes/runtime-base/src/utils/extract-request-body.ts:12— extract-request-body.extractRequestBody has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 2, loops 1 (2 pts), match/switch 1, ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
reset-domain-handler.resetDomainHandler (cognitive 17) packages/runtime/runtimes/runtime-single-process/src/api-handlers/reset-domain-handler.ts:9— reset-domain-handler.resetDomainHandler has cognitive complexity 17 (threshold 15). Drivers by points: error handling 3 (7 pts), if/else 5 (6 pts), loops 2 (4 pts) (nesting depth added 7). None of this is in the body itself: all 17 points belong to one function literal inside it that branches (line 9). 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.
getCompileConfigs (cognitive 17) internal/helpers/get-compile-configs.js:11— getCompileConfigs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (11 pts), ternaries 3 (5 pts), loops 1 (nesting depth added 6). None of this is in the body itself: all 17 points belong to 2 function literals inside it that branch (lines 12, 38). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
download-resolve-repo.downloadResolveRepo (cognitive 16) packages/core/create-resolve-app/src/download-resolve-repo.ts:14— download-resolve-repo.downloadResolveRepo has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), error handling 4, ternaries 2 (3 pts), boolean chains 2 (nesting depth added 2). Of this number, 8 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, 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.
patch-package-json.patchPackageJson (cognitive 16) packages/core/create-resolve-app/src/patch-package-json.ts:7— patch-package-json.patchPackageJson has cognitive complexity 16 (threshold 15). Drivers by points: if/else 2 (8 pts), loops 3 (7 pts), error handling 1 (nesting depth added 10). Of this number, 15 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
set-secret.setSecret (cognitive 16) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/set-secret.ts:11— set-secret.setSecret has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 2 (4 pts), boolean chains 3, error handling 2 (3 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ensure-event-subscriber.ensureEventSubscriber (cognitive 16) packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/ensure-event-subscriber.ts:4— ensure-event-subscriber.ensureEventSubscriber has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 5 (6 pts), boolean chains 4, error handling 2 (3 pts), if/else 2 (3 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
with-performance-tracer.withPerformanceTracerImpl (cognitive 16) packages/runtime/adapters/readmodel-adapters/readmodel-base/src/with-performance-tracer.ts:9— with-performance-tracer.withPerformanceTracerImpl has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (6 pts), ternaries 5 (6 pts), boolean chains 3, error handling 1 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bootstrap.bootstrap (cognitive 16) packages/runtime/runtimes/runtime-base/src/bootstrap.ts:20— bootstrap.bootstrap has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (7 pts), if/else 2 (5 pts), boolean chains 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
wrap-trie.wrapTrie (cognitive 16) packages/runtime/runtimes/runtime-base/src/wrap-trie.ts:14— wrap-trie.wrapTrie has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 4 (10 pts), loops 3 (4 pts), error handling 1, if/else 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fail (cognitive 16) packages/modules/module-auth/src/authenticate_wrapper.js:17— fail has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (8 pts), ternaries 2 (5 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Unfinished stub — throws a "not implemented" error packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/describe.ts:4— 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 packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/describe.ts:4— `describe` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.
Type Safety — 814 typed · 506 plain JS — the untyped files are functional-tests/app/auth/create-strategy.js, functional-tests/app/auth/jwt-secret.js, functional-tests/app/auth/route-login-callback.js, functional-tests/app/auth/route-register-callback.js, functional-tests/app/client/hoc/components/Routes.js, functional-tests/app/client/hoc/containers/App.js (+500 more). 1 production file(s) opt out entirely with @ts-nocheck · 15 @ts-ignore suppression(s); the opted-out files are packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts.
Forked directory tree (14 identical files, ~427 lines × 2 trees) tutorial/lesson-3/config.prod.js:1— tutorial/lesson-3/ and tutorial/lesson-4/ are near-verbatim copies of each other: 14 files are byte-identical under the same relative paths (~427 lines; the trees hold 27 and 30 files). That is one structural fact, not 14 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Forked directory tree (12 identical files, ~411 lines × 2 trees) tutorial/lesson-2/run.js:1— tutorial/lesson-2/ and tutorial/lesson-3/ are near-verbatim copies of each other: 12 files are byte-identical under the same relative paths (~411 lines; the trees hold 21 and 27 files). That is one structural fact, not 12 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.
Duplication concentrated across 4 sibling directories (49 clone groups) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:155— 49 duplicated blocks under packages/runtime/adapters/readmodel-adapters/ have copies in at least two of the sibling directories readmodel-base, readmodel-lite, readmodel-mysql, readmodel-postgresql — 40 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 49 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 49 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 49 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (48 clone groups) packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/set-replication-status.ts:17— 48 duplicated blocks under packages/runtime/adapters/eventstore-adapters/ have copies in at least two of the sibling directories eventstore-lite, eventstore-mysql, eventstore-postgresql — 34 of them are reported below, and 14 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 48 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 48 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 48 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 2 sibling directories (31 clone groups) templates/js/postcss/run.js:18— 31 duplicated blocks under templates/ have copies in at least two of the sibling directories js, ts — 26 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 31 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 31 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 31 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 5 sibling directories (19 clone groups) tutorial/lesson-4/run.js:20— 19 duplicated blocks under tutorial/ have copies in at least two of the sibling directories lesson-1, lesson-2, lesson-3, lesson-4, lesson-5 — 14 of them are reported below, and 5 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 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 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (10 clone groups) packages/tools/testing-tools/src/flow/read-model/make-test-environment.ts:29— 10 duplicated blocks under packages/tools/testing-tools/src/flow/ have copies in at least two of the sibling directories aggregate, read-model, saga — 8 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 10 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 5 sibling directories (9 clone groups) templates/ts/postcss/client/containers/Header.tsx:1— 9 duplicated blocks under templates/ts/ have copies in at least two of the sibling directories postcss, react, styled-components, vanilla, vue — 6 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 4 sibling directories (8 clone groups) templates/js/react/run.js:19— 8 duplicated blocks under the repository root have copies in at least two of the sibling directories internal, packages, templates, tutorial — 6 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 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 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (7 clone groups) packages/core/redux/src/command/use-redux-command.ts:49— 7 duplicated blocks under packages/core/redux/src/ have copies in at least two of the sibling directories command, read-model, view-model — 4 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 7 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 7 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 7 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (6 clone groups) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/types.ts:148— 6 duplicated blocks under packages/runtime/adapters/ have copies in at least two of the sibling directories eventstore-adapters, readmodel-adapters, replicators — 5 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Duplication concentrated across 3 sibling directories (5 clone groups) packages/modules/module-admin/src/commands/read-models/list.js:6— 5 duplicated blocks under packages/modules/module-admin/src/commands/ have copies in at least two of the sibling directories event-store, read-models, sagas — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
R10 · Code Duplication· Duplicated block with local edits (192 matched lines × 2 locations) · ×1
Duplicated block with local edits (192 matched lines × 2 locations) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:155— packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:155 · packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:119 — the two spans are one implementation copied and then locally edited — 728 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 (149 lines × 2 locations) packages/runtime/runtimes/runtime-aws-serverless/src/wrap-api-handler.ts:194— packages/runtime/runtimes/runtime-aws-serverless/src/wrap-api-handler.ts:194 · packages/runtime/runtimes/runtime-single-process/src/wrap-api-handler.ts:110 — 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 (138 matched lines × 2 locations) · ×1
Duplicated block with local edits (138 matched lines × 2 locations) packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-events.ts:95— packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-events.ts:95 · packages/runtime/adapters/eventstore-adapters/eventstore-base/src/import-secrets.ts:40 — 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.
R10 · Code Duplication· Duplicated block with local edits (135 matched lines × 2 locations) · ×1
Duplicated block with local edits (135 matched lines × 2 locations) packages/tools/testing-tools/src/flow/read-model/make-test-environment.ts:29— packages/tools/testing-tools/src/flow/read-model/make-test-environment.ts:29 · packages/tools/testing-tools/src/flow/saga/make-test-environment.ts:36 — the two spans are one implementation copied and then locally edited — 695 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 (91 lines × 2 locations) packages/core/react-hooks/src/use-command.ts:25— packages/core/react-hooks/src/use-command.ts:25 · packages/core/react-hooks/src/use-query.ts:24 — 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 (80 lines × 2 locations) templates/js/postcss/run.js:18— templates/js/postcss/run.js:18 · templates/ts/postcss/run.ts:20 — 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 (78 matched lines × 2 locations) · ×1
Duplicated block with local edits (78 matched lines × 2 locations) packages/core/redux/src/command/use-redux-command.ts:49— packages/core/redux/src/command/use-redux-command.ts:49 · packages/core/redux/src/read-model/use-redux-read-model.ts:68 — the two spans are one implementation copied and then locally edited — 512 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 (76 matched lines × 2 locations) · ×1
Duplicated block with local edits (76 matched lines × 2 locations) packages/runtime/runtimes/runtime-aws-serverless/src/uploader-factory.ts:81— packages/runtime/runtimes/runtime-aws-serverless/src/uploader-factory.ts:81 · REDACTED:41 — the two spans are one implementation copied and then locally edited — 409 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 (75 lines × 2 locations) templates/js/vue/run.js:17— templates/js/vue/run.js:17 · templates/ts/vue/run.ts:19 — 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 (74 lines × 3 locations) templates/js/vue/run.js:11— templates/js/vue/run.js:11 · templates/ts/angular/run.ts:10 · templates/ts/vue/run.ts:12 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (71 lines × 2 locations) tutorial/lesson-4/run.js:20— tutorial/lesson-4/run.js:20 · tutorial/lesson-5/run.js:20 — 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.
Wholesale file copy (69 identical lines × 3 files) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/search-to-where-expression.ts:1— packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/search-to-where-expression.ts:1 · packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/search-to-where-expression.ts:1 · packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/search-to-where-expression.ts:1 — these 3 files are line-for-line copies of one another — 69 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.
Duplicated block (68 lines × 5 locations) templates/js/react/run.js:19— templates/js/react/run.js:19 · templates/ts/react/run.ts:22 · tutorial/lesson-1/run.js:17 · tutorial/lesson-2/run.js:17 · +1 more site(s) not listed — the 5 copies are spread across 5 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 (66 lines × 2 locations) templates/js/vanilla/run.js:15— templates/js/vanilla/run.js:15 · templates/ts/vanilla/run.ts:17 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication· Duplicated block with local edits (63 matched lines × 2 locations) · ×1
Duplicated block with local edits (63 matched lines × 2 locations) packages/modules/module-comments/src/client/containers/CommentsPaginateRenderless.js:14— packages/modules/module-comments/src/client/containers/CommentsPaginateRenderless.js:14 · packages/modules/module-comments/src/client/containers/CommentsTreeRenderless.js:12 — the two spans are one implementation copied and then locally edited — 209 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 (56 lines × 2 locations) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/resubscribe.ts:62— packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/resubscribe.ts:62 · packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/subscribe.ts:31 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (56 matched lines × 2 locations) · ×1
Duplicated block with local edits (56 matched lines × 2 locations) templates/js/styled-components/client/ssr.js:10— templates/js/styled-components/client/ssr.js:10 · templates/ts/styled-components/client/ssr.tsx:12 — the two spans are one implementation copied and then locally edited — 336 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 (56 identical lines × 2 files) templates/js/styled-components/run.js:12— templates/js/styled-components/run.js:12 · templates/ts/styled-components/run.ts:12 — these 2 files are line-for-line copies of one another — 56 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.
Duplicated block (54 lines × 2 locations) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/reset.ts:17— packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/reset.ts:17 · packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/unsubscribe.ts:22 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication· Duplicated block with local edits (54 matched lines × 2 locations) · ×1
Duplicated block with local edits (54 matched lines × 2 locations) templates/js/react/client/components/MyAggregateList.js:6— templates/js/react/client/components/MyAggregateList.js:6 · templates/ts/react/client/components/MyAggregateList.tsx:7 — the two spans are one implementation copied and then locally edited — 278 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 (48 lines × 2 locations) templates/js/postcss/client/containers/Header.js:6— templates/js/postcss/client/containers/Header.js:6 · templates/js/styled-components/client/containers/Header.js:6 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (46 lines × 2 locations) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/resubscribe.ts:6— packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/resubscribe.ts:6 · packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/unsubscribe.ts:4 — 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.
Complex function buildEvents (cyclomatic 76, cognitive 170) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:154— buildEvents has cyclomatic complexity 76 and cognitive complexity 170; 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 updateToSetExpression (cyclomatic 48, cognitive 111) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/update-to-set-expression.ts:10— updateToSetExpression has cyclomatic complexity 48 and cognitive complexity 111; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function build (cyclomatic 45, cognitive 82) packages/runtime/adapters/replicators/replicator-via-api-handler/src/build.ts:37— build has cyclomatic complexity 45 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 build (cyclomatic 37, cognitive 55) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:459— build has cyclomatic complexity 37 and cognitive complexity 55; 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 build (cyclomatic 36, cognitive 45) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:764— build has cyclomatic complexity 36 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 31, cognitive 41) packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:106— (anonymous) has cyclomatic complexity 31 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 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 29, cognitive 59) packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/execute-statement.ts:24— (anonymous) has cyclomatic complexity 29 and cognitive complexity 59; 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 29, cognitive 54) packages/runtime/runtimes/runtime-base/src/custom-read-model.ts:51— (anonymous) has cyclomatic complexity 29 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 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 makeSqlQuery (cyclomatic 29, cognitive 34) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/make-sql-query.ts:10— makeSqlQuery has cyclomatic complexity 29 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ensureQueue (cyclomatic 28, cognitive 52) packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:201— ensureQueue has cyclomatic complexity 28 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 buildEvents (cyclomatic 28, cognitive 49) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:159— buildEvents has cyclomatic complexity 28 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 isRetryablePassthroughError (cyclomatic 27, cognitive 26) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/passthrough-error.ts:44— isRetryablePassthroughError has cyclomatic complexity 27 and cognitive complexity 26; 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 deleteQueue (cyclomatic 26, cognitive 61) packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:368— deleteQueue has cyclomatic complexity 26 and cognitive complexity 61; 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 uploaderHandler (cyclomatic 22, cognitive 33) REDACTED:22— uploaderHandler has cyclomatic complexity 22 and cognitive complexity 33; 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 21, cognitive 39) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/status.ts:23— (anonymous) has cyclomatic complexity 21 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 (anonymous) (cyclomatic 21, cognitive 15) packages/modules/module-comments/src/client/reducers/comments.js:17— (anonymous) has cyclomatic complexity 21 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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 execute (cyclomatic 20, cognitive 34) packages/tools/testing-tools/src/flow/saga/make-test-environment.ts:135— execute has cyclomatic complexity 20 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function updateToSetExpression (cyclomatic 19, cognitive 62) packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/update-to-set-expression.ts:7— updateToSetExpression has cyclomatic complexity 19 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 buildEvents (cyclomatic 19, cognitive 45) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:123— buildEvents has cyclomatic complexity 19 and cognitive complexity 45; 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 updateToSetExpression (cyclomatic 18, cognitive 58) packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/update-to-set-expression.ts:7— updateToSetExpression has cyclomatic complexity 18 and cognitive complexity 58; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts · ×1
packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts: 948 lines of code packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:1— packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts has 948 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/runtime/adapters/readmodel-adapters/readmodel-base/src/types.ts · ×1
packages/runtime/adapters/readmodel-adapters/readmodel-base/src/types.ts: 654 lines of code packages/runtime/adapters/readmodel-adapters/readmodel-base/src/types.ts:1— packages/runtime/adapters/readmodel-adapters/readmodel-base/src/types.ts has 654 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts · ×1
packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts: 618 lines of code packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:1— packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts has 618 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/core/core/src/aggregate/get-aggregates-interop-builder.ts · ×1
packages/core/core/src/aggregate/get-aggregates-interop-builder.ts: 528 lines of code packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:1— packages/core/core/src/aggregate/get-aggregates-interop-builder.ts has 528 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts · ×1
packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts: 484 lines of code packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:1— packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts has 484 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts · ×1
packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts: 460 lines of code packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts:1— packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts has 460 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/runtime/runtimes/runtime-base/src/event-subscriber.ts · ×1
packages/runtime/runtimes/runtime-base/src/event-subscriber.ts: 459 lines of code packages/runtime/runtimes/runtime-base/src/event-subscriber.ts:1— packages/runtime/runtimes/runtime-base/src/event-subscriber.ts has 459 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts · ×1
packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts: 426 lines of code packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts:1— packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.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· packages/core/core/src/types/runtime.ts · ×1
packages/core/core/src/types/runtime.ts: 410 lines of code packages/core/core/src/types/runtime.ts:1— packages/core/core/src/types/runtime.ts has 410 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
Dead file (~354 LoC) packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~225 LoC) REDACTED— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~122 LoC) packages/tools/scripts/src/alias/$resolve.readModel.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~109 LoC) tutorial/lesson-5/client/components/ShoppingList.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-5/client/routes.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~77 LoC) packages/tools/scripts/src/alias/$resolve.middlewares.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~76 LoC) templates/ts/styled-components/client/ssr.tsx— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~72 LoC) templates/ts/react/client/components/MyAggregateList.tsx— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/ts/react/client/containers/App.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~70 LoC) templates/ts/postcss/client/ssr.tsx— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~65 LoC) templates/js/react/client/components/MyAggregateList.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (templates/js/react/client/containers/App.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~62 LoC) templates/js/postcss/client/ssr.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~60 LoC) packages/tools/scripts/src/alias/$resolve.monitoringAdapters.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~57 LoC) tutorial/lesson-5/client/components/ShoppingListCreator.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-5/client/components/MyLists.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~55 LoC) packages/tools/scripts/src/alias/$resolve.guardOnlyServer.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~53 LoC) tutorial/lesson-5/client/components/MyLists.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (tutorial/lesson-5/client/routes.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~52 LoC) REDACTED— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~48 LoC) packages/modules/module-auth/src/logout_api_handler.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~44 LoC) packages/tools/scripts/src/alias/$resolve.uploadAdapter.js— no import path from any entry point (125 application, 42 tooling, 384 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Unused dependency '@resolve-js/runtime-aws-serverless' — Declared in 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-js/runtime-single-process' — Declared in 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 'aws-xray-sdk-core' — Declared in 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.
Orphaned file packages/core/core/src/aggregate/get-aggregates-interop-builder.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/runtimes/runtime-aws-serverless/src/event-subscriber-notifier-factory.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/runtimes/runtime-base/src/event-subscriber.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.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 .eslintrc.js:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/runtimes/runtime-base/src/types.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/core/core/src/types/runtime.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/runtimes/runtime-aws-serverless/src/wrap-api-handler.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 REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/update-to-set-expression.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/runtimes/runtime-base/src/custom-read-model.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/runtimes/runtime-base/src/create-runtime.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/replicators/replicator-via-api-handler/src/build.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/core/client/src/client.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/commit-incremental-import.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/tools/testing-tools/src/flow/saga/make-test-environment.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/make-sql-query.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/runtimes/runtime-single-process/src/wrap-api-handler.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/core/core/src/helpers.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/monitoring-adapters/monitoring-base/src/index.ts:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/commit-incremental-import.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.
Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:1306— @babel/plugin-proposal-async-generator-functions 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-async-generator-functions REDACTED:1316— @babel/plugin-proposal-async-generator-functions 7.18.10 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-async-generator-functions instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-properties REDACTED:1342— @babel/plugin-proposal-class-properties 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-properties instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-class-static-block REDACTED:1350— @babel/plugin-proposal-class-static-block 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-class-static-block instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-dynamic-import REDACTED:1381— @babel/plugin-proposal-dynamic-import 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-dynamic-import instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:1413— @babel/plugin-proposal-export-namespace-from 7.16.7 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-export-namespace-from REDACTED:1421— @babel/plugin-proposal-export-namespace-from 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-export-namespace-from instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-json-strings REDACTED:1429— @babel/plugin-proposal-json-strings 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-json-strings instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-logical-assignment-operators REDACTED:1437— @babel/plugin-proposal-logical-assignment-operators 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-logical-assignment-operators instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-nullish-coalescing-operator REDACTED:1445— @babel/plugin-proposal-nullish-coalescing-operator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-nullish-coalescing-operator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-numeric-separator REDACTED:1453— @babel/plugin-proposal-numeric-separator 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-numeric-separator instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:1461— @babel/plugin-proposal-object-rest-spread 7.12.1 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-object-rest-spread REDACTED:1470— @babel/plugin-proposal-object-rest-spread 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-object-rest-spread instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-catch-binding REDACTED:1481— @babel/plugin-proposal-optional-catch-binding 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-catch-binding instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-optional-chaining REDACTED:1489— @babel/plugin-proposal-optional-chaining 7.18.9 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-optional-chaining instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-methods REDACTED:1498— @babel/plugin-proposal-private-methods 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-methods instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-private-property-in-object REDACTED:1506— @babel/plugin-proposal-private-property-in-object 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-private-property-in-object instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @babel/plugin-proposal-unicode-property-regex REDACTED:1516— @babel/plugin-proposal-unicode-property-regex 7.18.6 is resolved in REDACTED and is marked deprecated by its publisher: "This proposal has been merged to the ECMAScript standard and thus this plugin is no longer maintained. Please use @babel/plugin-transform-unicode-property-regex 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/config-array REDACTED:3029— @humanwhocodes/config-array 0.9.5 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:3038— @humanwhocodes/object-schema 1.2.1 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: @npmcli/move-file REDACTED:3390— @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: @sinonjs/text-encoding REDACTED:3568— @sinonjs/text-encoding 0.7.1 is resolved in REDACTED and is marked deprecated by its publisher: "Deprecated: no longer maintained and no longer used by Sinon packages. See https://github.com/sinonjs/nise/issues/243 for replacement details.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @types/browserslist REDACTED:3863— @types/browserslist 4.15.0 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition. browserslist provides its own type definitions, so you do not need this installed.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @types/classnames REDACTED:3870— @types/classnames 2.3.1 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition. classnames provides its own type definitions, so you do not need this installed.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @types/error-stack-parser REDACTED:3958— @types/error-stack-parser 2.0.0 is resolved in REDACTED and is marked deprecated by its publisher: "This is a stub types definition for error-stack-parser (https://github.com/stacktracejs/error-stack-parser). error-stack-parser provides its own type definitions, so you don't need @types/error-stack-parser installed!". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
+ 53 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×39
Console output used as the logging channel packages/core/core/src/helpers.ts:49— `packages/core/core/src/helpers.ts` reports through `console.*` at line 49 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/core/src/helpers.ts:57— `packages/core/core/src/helpers.ts` reports through `console.*` at line 57 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:10— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 10 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:11— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 11 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:12— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 12 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:14— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 14 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:15— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 15 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:16— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:18— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:19— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 19 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:20— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:22— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 22 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:23— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:24— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:26— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 26 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:27— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:28— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:30— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 30 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:31— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 31 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:32— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 32 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:37— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 37 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:38— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:39— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 39 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:40— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 40 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/core/create-resolve-app/src/print-finish-output.ts:41— `packages/core/create-resolve-app/src/print-finish-output.ts` reports through `console.*` at line 41 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Outdated (npm): @angular/common REDACTED:15— @angular/common is pinned at 11.2.4; registry.npmjs.org publishes 22.2.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): @angular/compiler REDACTED:16— @angular/compiler is pinned at 11.2.4; registry.npmjs.org publishes 22.2.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): @angular/compiler-cli REDACTED:17— @angular/compiler-cli is pinned at 11.2.4; registry.npmjs.org publishes 22.2.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): @angular/core REDACTED:18— @angular/core is pinned at 11.2.4; registry.npmjs.org publishes 22.2.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): @angular/forms REDACTED:19— @angular/forms is pinned at 11.2.4; registry.npmjs.org publishes 22.2.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): @angular/platform-browser REDACTED:20— @angular/platform-browser is pinned at 11.2.4; registry.npmjs.org publishes 22.2.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): @angular/platform-browser-dynamic REDACTED:21— @angular/platform-browser-dynamic is pinned at 11.2.4; registry.npmjs.org publishes 22.2.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): @ngtools/webpack REDACTED:23— @ngtools/webpack is pinned at 11.2.3; registry.npmjs.org publishes 22.2.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): babel-jest REDACTED:84— babel-jest is pinned at 27.5.1; registry.npmjs.org publishes 30.5.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): better-sqlite3 REDACTED:32— better-sqlite3 is pinned at 7.4.3; 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): boxen REDACTED:30— boxen is pinned at 5.0.0; registry.npmjs.org publishes 9.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): commander REDACTED:18— commander is pinned at 6.1.0; registry.npmjs.org publishes 15.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): content-disposition REDACTED:37— content-disposition is pinned at 0.5.3; registry.npmjs.org publishes 3.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): copy-webpack-plugin REDACTED:24— copy-webpack-plugin is pinned at 6.0.0; registry.npmjs.org publishes 14.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): diff REDACTED:33— diff is pinned at 5.0.0; registry.npmjs.org publishes 9.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): file-type REDACTED:33— file-type is pinned at 16.5.4; registry.npmjs.org publishes 22.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): fs-extra REDACTED:20— fs-extra is pinned at 8.1.0; registry.npmjs.org publishes 11.4.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): glob internal/babel-compile/REDACTED:14— glob is pinned at 7.1.6; registry.npmjs.org publishes 13.0.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): jest REDACTED:22— jest is pinned at 27.5.1; registry.npmjs.org publishes 30.5.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): nanoid REDACTED:24— nanoid is pinned at 3.2.0; registry.npmjs.org publishes 6.0.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): open REDACTED:52— open is pinned at 8.0.2; registry.npmjs.org publishes 11.0.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): query-string REDACTED:56— query-string is pinned at 6.14.1; registry.npmjs.org publishes 10.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-markdown examples/js/personal-data/REDACTED:41— react-markdown is pinned at 5.0.3; registry.npmjs.org publishes 10.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): react-router REDACTED:61— react-router is pinned at 5.2.0; registry.npmjs.org publishes 8.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): rimraf internal/cra-test/REDACTED:14— rimraf is pinned at 3.0.2; registry.npmjs.org publishes 6.1.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.
Duplicated predicate packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:619— `!Array.isArray(eventTypes) && eventTypes != null` appears character-identically in 3 files — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts, packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts, packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/core/src/helpers.ts:218— `!allowAbsolutePath && (protocol || slashes || host || port || hostname)` appears character-identically in 2 files — packages/core/core/src/helpers.ts, packages/runtime/runtimes/runtime-base/src/utils/validate-path.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/delete-secret.ts:28— `!secretsTableName || !escapeId || !databaseName || !executeStatement || !escape` appears character-identically in 3 files — packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/delete-secret.ts, packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/get-secret.ts, packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/set-secret.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/client/src/assertions.ts:2— `!value || value === '' || value.trim() === ''` appears character-identically in 2 files — packages/core/client/src/assertions.ts, packages/core/core/src/helpers.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/search-to-where-expression.ts:43— `'$and' in expression || '$or' in expression || '$not' in expression` appears character-identically in 3 files — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/search-to-where-expression.ts, packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/search-to-where-expression.ts, packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/search-to-where-expression.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build-upsert-document.ts:9— `'$and' in searchExpression || '$or' in searchExpression || '$not' in searchExpression` appears character-identically in 3 files — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build-upsert-document.ts, packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build-upsert-document.ts, packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build-upsert-document.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-event-subscriber.ts:24— `(!!updateOnly && destination != null) || (!updateOnly && destination == null)` appears character-identically in 3 files — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/ensure-event-subscriber.ts, packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/ensure-event-subscriber.ts, packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/ensure-event-subscriber.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/modules/module-auth/src/api_handler_constructor.js:21— `(authRequest.body && authRequest.body.noredirect && String(authRequest.body.noredirect) === 'true') || (authRequest.query && authRequest.que…` appears character-identically in 2 files — packages/modules/module-auth/src/api_handler_constructor.js, packages/modules/module-auth/src/logout_api_handler.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/convert-binary-row.ts:47— `(inclusiveMode && fieldList.hasOwnProperty(key)) || (!inclusiveMode && !fieldList.hasOwnProperty(key))` appears character-identically in 4 files — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/convert-binary-row.ts, packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/convert-binary-row.ts, packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/convert-result-row.ts, packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/count.ts:34— `Array.isArray(rows) && rows.length > 0 && rows[0] != null && Number.isInteger(+rows[0].Count)` appears character-identically in 3 files — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/count.ts, packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/count.ts, packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/count.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/redux/src/command/use-redux-command.ts:96— `actualOptions.actions || internalActions` appears character-identically in 3 files — packages/core/redux/src/command/use-redux-command.ts, packages/core/redux/src/read-model/use-redux-read-model.ts, packages/core/redux/src/view-model/use-redux-view-model.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/redux/src/read-model/use-redux-read-model.ts:179— `actualOptions.queryOptions || defaultQueryOptions` appears character-identically in 2 files — packages/core/redux/src/read-model/use-redux-read-model.ts, packages/core/redux/src/view-model/use-redux-view-model.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/get-event-subscribers.ts:28— `applicationName != null || eventSubscriber != null` appears character-identically in 3 files — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/get-event-subscribers.ts, packages/runtime/adapters/eventstore-adapters/eventstore-mysql/src/get-event-subscribers.ts, packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/get-event-subscribers.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/core/src/helpers.ts:224— `auth || hash || search || query || /^\//.test(url) || /\/$/.test(url)` appears character-identically in 2 files — packages/core/core/src/helpers.ts, packages/runtime/runtimes/runtime-base/src/utils/validate-path.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/modules/module-auth/es/api_handler_constructor.js:15— `authRequest.body && authRequest.body.noredirect && String(authRequest.body.noredirect) === 'true' || authRequest.query && authRequest.query.…` appears character-identically in 4 files — packages/modules/module-auth/es/api_handler_constructor.js, packages/modules/module-auth/es/logout_api_handler.js, packages/modules/module-auth/lib/api_handler_constructor.js, packages/modules/module-auth/lib/logout_api_handler.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:623— `cursor != null && cursor.constructor !== String` appears character-identically in 3 files — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts, packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts, packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/tools/scripts/src/export_event_store_mode.js:9— `directory == null || directory.constructor !== String` appears character-identically in 2 files — packages/tools/scripts/src/export_event_store_mode.js, packages/tools/scripts/src/import_event_store_mode.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/redux/src/read-model/connect-read-model.tsx:106— `entry && entry.status === ResultStatus.Failed` appears character-identically in 2 files — packages/core/redux/src/read-model/connect-read-model.tsx, packages/core/redux/src/view-model/connect-view-model.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/redux/src/read-model/connect-read-model.tsx:104— `entry && entry.status === ResultStatus.Ready` appears character-identically in 2 files — packages/core/redux/src/read-model/connect-read-model.tsx, packages/core/redux/src/view-model/connect-view-model.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/core/redux/src/read-model/connect-read-model.tsx:111— `entry && entry.status === ResultStatus.Requested` appears character-identically in 2 files — packages/core/redux/src/read-model/connect-read-model.tsx, packages/core/redux/src/view-model/connect-view-model.tsx. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/modules/module-auth/es/authenticate_wrapper.js:22— `error != null && error.status || status || 401` appears character-identically in 2 files — packages/modules/module-auth/es/authenticate_wrapper.js, packages/modules/module-auth/lib/authenticate_wrapper.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts:649— `error == null || !( error instanceof PassthroughError || error.name === 'RequestTimeoutError' )` appears character-identically in 2 files — packages/runtime/adapters/readmodel-adapters/readmodel-lite/src/build.ts, packages/runtime/adapters/readmodel-adapters/readmodel-mysql/src/build.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/errors.ts:9— `error.name === value || error.code === value` appears character-identically in 2 files — packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/errors.ts, packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/passthrough-error.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/delete-secret.ts:118— `errorCode.startsWith('SQLITE_CONSTRAINT') && errorMessage.indexOf('PRIMARY') > -1` appears character-identically in 3 files — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/delete-secret.ts, packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/save-event.ts, packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/set-secret.ts. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/replicate-secrets.ts:24— `existingSecrets.length > 0 || deletedSecrets.length > 0` appears character-identically in 2 files — packages/runtime/adapters/eventstore-adapters/eventstore-lite/src/replicate-secrets.ts, packages/runtime/adapters/eventstore-adapters/eventstore-postgresql/src/replicate-secrets.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.
Mock-dominated test: is unsubscribed packages/core/client/test/unit/subscribe.unit.test.ts:128— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: close on disconnected packages/core/client/test/unit/subscribe.unit.test.ts:288— This test sets up 5 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 5 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: multiple callbacks added packages/core/client/test/unit/subscribe-callback.unit.test.ts:69— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 6 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: multiple callbacks removed packages/core/client/test/unit/subscribe-callback.unit.test.ts:89— This test sets up 3 test doubles (for example `jest.fn`) 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: jwt provider passed to middleware packages/core/client/test/unit/request.unit.test.ts:120— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: saga handlers should be called with correct arguments packages/core/core/test/get-sagas-interop-builder.unit.test.ts:69— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: interop methods should be called with correct arguments packages/core/core/test/get-read-models-interop-builder.unit.test.ts:92— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: calls execution without error if resolver executed without error packages/core/core/test/get-read-models-interop-builder.unit.test.ts:257— This test sets up 4 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 4 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: createApplication steps packages/core/create-resolve-app/test/create-application.test.ts:26— This test sets up 5 test doubles (for example `vi.mock/jest.mock of an imported module`) 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: should set DEBUG="resolve:*" and DEBUG_LEVEL="warn" if DEBUG env is not set packages/core/debug-levels/test/index.test.ts:64— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 8 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: state re-requested on resubscribe callback packages/core/react-hooks/test/use-view-model.unit.test.tsx:366— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: just a builder packages/core/react-hooks/test/use-query.unit.test.tsx:462— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: builder and options packages/core/react-hooks/test/use-query.unit.test.tsx:526— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useQuery hook called packages/core/react-hooks/test/use-query-builder.unit.test.ts:25— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: just a builder packages/core/react-hooks/test/use-command.unit.test.ts:479— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: builder and options packages/core/react-hooks/test/use-command.unit.test.ts:543— This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: useCommand hook called packages/core/react-hooks/test/use-command-builder.unit.test.ts:32— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: combined reducers are passed to store factory packages/core/redux/test/create-resolve-store.test.ts:64— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: prints correct metrics if metric name is Executions packages/runtime/adapters/monitoring-adapters/monitoring-console/test/index.test.ts:133— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: prints correct metrics if metric name is Duration packages/runtime/adapters/monitoring-adapters/monitoring-console/test/index.test.ts:193— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) 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: prints correct metrics if metric name is some custom value packages/runtime/adapters/monitoring-adapters/monitoring-console/test/index.test.ts:274— This test sets up 3 test doubles (for example `vi.mock/jest.mock of an imported module`) against 0 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: custom secrets manager packages/tools/testing-tools/test/read-model.test.ts:402— This test sets up 3 test doubles (for example `jest.fn`) against 0 real object(s) of its own, and its only verification is 3 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×19
Diagnostic log message is built whether or not it is wanted packages/core/core/src/saga/build-scheduler-projection.ts:48— `verbose` at line 48 is called with an argument built by `JSON.stringify(entry)` (line 48), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/core/core/src/saga/build-scheduler-projection.ts:66— `verbose` at line 66 is called with an argument built by `JSON.stringify(command)` (line 66), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/adapters/monitoring-adapters/monitoring-aws-cloudwatch/src/publish.ts:111— `verbose` at line 111 is called with an argument built by `JSON.stringify(metricData.metrics)` (line 111), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/scheduler-factory.ts:16— `verbose` at line 16 is called with an argument built by `JSON.stringify(entry)` (line 16), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/scheduler-factory.ts:123— `verbose` at line 123 is called with an argument built by `JSON.stringify(data)` (line 123), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/scheduler-factory.ts:152— `verbose` at line 152 is called with an argument built by `JSON.stringify(data)` (line 152), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:108— `verbose` at line 108 is called with an argument built by `JSON.stringify(lambdaEvent, null, 2)` (line 108), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:150— `verbose` at line 150 is called with an argument built by `JSON.stringify(executorResult)` (line 150), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:167— `verbose` at line 167 is called with an argument built by `JSON.stringify(executorResult)` (line 167), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:262— `verbose` at line 262 is called with an argument built by `JSON.stringify(executorResult)` (line 262), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:276— `verbose` at line 276 is called with an argument built by `JSON.stringify(executorResult)` (line 276), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:289— `verbose` at line 289 is called with an argument built by `JSON.stringify(executorResult)` (line 289), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:312— `verbose` at line 312 is called with an argument built by `JSON.stringify(lambdaEvent.httpMethod, null, 2)` (line 313), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/lambda-worker.ts:333— `verbose` at line 333 is called with an argument built by `JSON.stringify(executorResult)` (line 333), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/cloud-service-event-handler.ts:59— `verbose` at line 59 is called with an argument built by `JSON.stringify(result, null, 2)` (line 59), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/cloud-service-event-handler.ts:69— `verbose` at line 69 is called with an argument built by `JSON.stringify(result, null, 2)` (line 69), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/cloud-service-event-handler.ts:93— `verbose` at line 93 is called with an argument built by `JSON.stringify(listenerIds, null, 2)` (line 93), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-aws-serverless/src/cloud-service-event-handler.ts:107— `verbose` at line 107 is called with an argument built by `JSON.stringify(result, null, 2)` (line 107), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because verbose is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted packages/runtime/runtimes/runtime-base/src/create-runtime.ts:133— `debug` at line 133 is called with an argument built by `Object.keys(readModelConnectors)` (line 133), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
README/code drift docs/Contributing.md:41— docs/Contributing.md runs `yarn test:functional`, but no REDACTED declares a `test:functional` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/README.md:7— packages/core/README.md links to `@resolve-js/scripts`, but `packages/core/@resolve-js/scripts` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/README.md:9— packages/core/README.md links to `@resolve-js/testing-tools`, but `packages/core/@resolve-js/testing-tools` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/README.md:14— packages/core/README.md links to `@resolve-js/redux`, but `packages/core/@resolve-js/redux` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/modules/README.md:5— packages/modules/README.md links to `@resolve-js/module-admin/`, but `packages/modules/@resolve-js/module-admin` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/modules/README.md:6— packages/modules/README.md links to `@resolve-js/module-auth/`, but `packages/modules/@resolve-js/module-auth` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/modules/README.md:7— packages/modules/README.md links to `@resolve-js/module-comments/`, but `packages/modules/@resolve-js/module-comments` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/modules/README.md:8— packages/modules/README.md links to `@resolve-js/module-uploader/`, but `packages/modules/@resolve-js/module-uploader` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/modules/README.md:9— packages/modules/README.md links to `@resolve-js/module-incremental-import/`, but `packages/modules/@resolve-js/module-incremental-import` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/api/client/entry-point.md:20— docs/api/client/entry-point.md links to `frontend.md`, but `docs/api/client/frontend.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/create-resolve-app/README.md:92— packages/core/create-resolve-app/README.md runs `npm run test:functional`, but no REDACTED declares a `test:functional` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/create-resolve-app/README.md:96— packages/core/create-resolve-app/README.md links to `../../docs/API%20References.md/#project-structure-overview`, but `packages/docs/API References.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/create-resolve-app/README.md:98— packages/core/create-resolve-app/README.md links to `../../docs/Aggregate.md`, but `packages/docs/Aggregate.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/create-resolve-app/README.md:99— packages/core/create-resolve-app/README.md links to `../../docs/View%20Model.md`, but `packages/docs/View Model.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/core/create-resolve-app/README.md:100— packages/core/create-resolve-app/README.md links to `../../docs/Read%20Model.md`, but `packages/docs/Read Model.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/modules/module-auth/README.md:86— packages/modules/module-auth/README.md names `auth/route_register_callback.js`, but no file or folder `auth/route_register_callback.js` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift packages/runtime/adapters/readmodel-adapters/README.md:3— packages/runtime/adapters/readmodel-adapters/README.md links to `../../core/resolve-query`, but `packages/runtime/core/resolve-query` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
Disabled test packages/runtime/adapters/eventstore-adapters/eventstore-base/test/cursor-to-thread-array.test.ts:40— 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 packages/runtime/adapters/eventstore-adapters/eventstore-base/test/thread-array-to-cursor.test.ts:40— 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 packages/runtime/adapters/eventstore-adapters/eventstore-mysql/test/index.test.js:8— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
D34 · Knowledge Freshness· Most significant orphaned file · ×2
Most significant orphaned file packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file packages/runtime/adapters/readmodel-adapters/readmodel-base/src/types.ts:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
No app-layer HTTPS enforcement detected internal/local-registry/bin/index.js:41— `http(…).listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
No app-layer HTTPS enforcement detected packages/runtime/runtimes/runtime-single-process/src/start-express.ts:120— `server.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)
AC7 · A11y enforcement· Accessibility enforcement below the top rung · ×1
Accessibility enforcement below the top rung — An a11y linter is configured (Documented) but there's no automated a11y test or CI gate. Add jest-axe to verify at runtime, then gate it in CI. What was searched, so you can tell an absence from a miss: the 25 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.
Fat interface: Adapter (25 required operations) packages/runtime/adapters/eventstore-adapters/eventstore-base/src/types.ts:488— `Adapter` declares 25 required operations: `importEvents`, `exportEvents`, `getLatestEvent`, `init`, `drop`, `dispose`, `freeze`, `unfreeze`, `getSecretsManager`, `dropSnapshot`, `pushIncrementalImport`, `beginIncrementalImport`, `commitIncrementalImport`, `rollbackIncrementalImport`, `incrementalImport`, `loadSecrets`, `importSecrets`, `exportSecrets`, `gatherSecretsFromEvents`, `getCursorUntilEventTypes`, `establishTimeLimit`, `getEventLoader`, `runtimeInfo`, `setReconnectionMode`, `setMonitoring`. 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.
C2 · Access Controls· No named authorization policies · ×1
No named authorization policies — Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect.
Concentrated knowledge decay — 161 of 161 significant files have no living knowledge, while the repository is still being changed at a low rate (1 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 161 separate risks. Counted over 161 of the 1041 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
IC1 · Incompleteness & stubs· Empty method body · ×1
Empty method body packages/modules/module-comments/src/common/aggregates/verify-command.js:1— `verifyCommand` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Blanket warning suppression packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/wrap-procedure.ts:2— 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.
Logging is not universal — Only 19/26 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `internal/babel-compile`, `internal/build-packages`, `internal/helpers`, `internal/local-registry`, `internal/root-yarn` and 2 more.
No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 31953 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
R8 · Dependency Hygiene· Test-only dependency 'isomorphic-fetch' in production deps · ×1
Test-only dependency 'isomorphic-fetch' in production deps REDACTED:21— Only test files import it (first: functional-tests/api/benchmark.test.ts:6) — move it to devDependencies.
No security response headers detected examples/ts/hacker-news/docker/volumes/nginx/conf.d/default.conf:1— None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `default.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X2 · Cancellation propagation· Not all async functions that make a request accept an AbortSignal · ×1
Not all async functions that make a request accept an AbortSignal — Only 0/22 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
X5 · Nullable reference types· Strict null checking is not enabled everywhere the repository type-checks · ×1
Strict null checking is not enabled everywhere the repository type-checks — 24/51 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
Null assertions (`!`) reduce the strict null checking score — ~0.2 `!` null assertions per 1k TypeScript source lines — 9 assertion(s) across the 46114 source line(s) of the 651 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/build.ts (4), packages/runtime/adapters/readmodel-adapters/readmodel-postgresql/src/connect.ts (2), packages/runtime/runtimes/runtime-base/src/create-runtime.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
Outdated (npm): @babel/cli — @babel/cli is pinned at 7.16.0; registry.npmjs.org publishes 8.0.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): @babel/core — @babel/core is pinned at 7.17.2; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/node — @babel/node is pinned at 7.16.8; registry.npmjs.org publishes 8.0.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): @babel/plugin-proposal-class-properties — @babel/plugin-proposal-class-properties is pinned at 7.13.0; registry.npmjs.org publishes 7.18.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): @babel/plugin-proposal-export-default-from — @babel/plugin-proposal-export-default-from is pinned at 7.12.13; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/plugin-proposal-export-namespace-from — @babel/plugin-proposal-export-namespace-from is pinned at 7.14.2; registry.npmjs.org publishes 7.18.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): @babel/plugin-transform-runtime — @babel/plugin-transform-runtime is pinned at 7.14.3; registry.npmjs.org publishes 8.0.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): @babel/preset-env — @babel/preset-env is pinned at 7.14.4; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/preset-react — @babel/preset-react is pinned at 7.13.13; registry.npmjs.org publishes 8.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @babel/register — @babel/register is pinned at 7.13.16; registry.npmjs.org publishes 8.0.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): @babel/runtime — @babel/runtime is pinned at 7.17.2; registry.npmjs.org publishes 8.0.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @docusaurus/core — @docusaurus/core is pinned at 2.0.0-beta.20; registry.npmjs.org publishes 3.10.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): @docusaurus/preset-classic — @docusaurus/preset-classic is pinned at 2.0.0-beta.20; registry.npmjs.org publishes 3.10.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): @elastic/elasticsearch — @elastic/elasticsearch is pinned at 7.11.0; registry.npmjs.org publishes 9.5.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): @types/better-sqlite3 — @types/better-sqlite3 is pinned at 7.4.0; registry.npmjs.org publishes 9.6.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): address — address is pinned at 1.1.2; registry.npmjs.org publishes 2.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): adm-zip — adm-zip is pinned at 0.5.4; registry.npmjs.org publishes 0.6.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): ajv — ajv is pinned at 8.10.0; registry.npmjs.org publishes 8.20.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): babel-loader — babel-loader is pinned at 8.2.2; registry.npmjs.org publishes 10.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): babel-plugin-module-resolver — babel-plugin-module-resolver is pinned at 4.1.0; registry.npmjs.org publishes 5.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): bootstrap — bootstrap is pinned at 4.6.0; registry.npmjs.org publishes 5.3.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): bootstrap-vue — bootstrap-vue is pinned at 2.21.2; registry.npmjs.org publishes 2.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): chalk — chalk is pinned at 4.1.0; 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): clsx — clsx is pinned at 1.2.1; registry.npmjs.org publishes 2.1.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): columnify — columnify is pinned at 1.5.4; registry.npmjs.org publishes 1.6.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
TimestampFilter: 1 contract type(s) expose producer-owned ids/enums — In TimestampFilter, 1 contract type(s) (TimestampFilter) expose strong-typed ids/value objects (UnbrandProps); a serialized contract could expose the underlying primitive instead. Advisory — a deliberate strong-ID style is fine.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
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 1 file(s) — `packages/runtime/runtimes/runtime-aws-serverless/external.d.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a16420-255f-79d7-8d47-06a18c147e5e · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 221 · Warnings: 724 · Recommendations: 446 · Info: 98 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 14:59 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.