mbc-net/mbc-cqrs-serverless

Executive summary

mbc-net/mbc-cqrs-serverless scores 43 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 29 and is rated Weak. Its REDACTED Scanning 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 REDACTED Scanning and to resolve the 1 No ADRs found finding(s) in ADR Quality, and if Production Readiness rose to 70, the score would rise from 43 to about 55.

141 findings are critical: 61 in Dependency Vulnerabilities, 31 in Static Analysis (SAST), 25 in Dependency Hygiene, 11 in Secrets (history), seven in IaC & Container Security, three in Circular Imports, two in REDACTED Scanning and one in Test Quality.

Watchdog couldn't measure 4 dimensions in this code, among them Navigability, Structured logging and Schema migrations, so they are left out of the score. The product code is 29,847 lines, which would take an estimated 0.6 person-years, around €83,000, to rebuild.

Code Health 55 Adequate, capped by Nullable reference types Architecture 68 Adequate, capped by Circular Imports Maturity 50 Weak, capped by Documentation accuracy Production Readiness 29 Weak, capped by REDACTED Scanning, Dependency Freshness, Dependency Hygiene, DR & Backup and Outbound HTTP resilience Security and Compliance 67 Adequate, capped by Secrets (history), Static Analysis (SAST), Dependency Vulnerabilities and Supply-chain Provenance & Signing Performance 60 Adequate

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

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.

Production Readiness 29 · counts for 46%Maturity 50 · counts for 25%Code Health 55 · counts for 14%Performance 60 · counts for 8%Security and Compliance 67 · counts for 4%Architecture 68 · counts for 2%

If Production Readiness rose from 29 to 70, the lowest score rated Strong, the score would rise from 43 to about 55.

Code composition: what the lines of code are

Product code 31%Tests 69%

New since the last survey: 99 findings

These 99 critical or serious findings weren't in the previous survey, on 8 October 2026.

Cognitive Complexity · CsvImportSfnEventHandler.handleStepState::sendBatchToSqs (cognitive 17) packages/import/src/event/csv-import.sfn.event.handler.ts
Dependency Hygiene · Deprecated: @aws-sdk/signature-v4 package.json
Dependency Hygiene · Deprecated: eslint package.json
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
Boundary Type-Coupling · Cross-context type RotateByEnum (sequence → master) packages/master/src/helpers/index.ts
Boundary Type-Coupling · Cross-context type RotateByEnum (sequence → master) packages/master/src/templates/master/helpers/id.ts
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Supply-chain Provenance & Signing · REDACTED
Large Files · packages/cli/templates/infra/libs/infra-stack.ts: 1310 lines of code packages/cli/templates/infra/libs/infra-stack.ts
Large Files · packages/mcp-server/src/tools/analyze.ts: 1268 lines of code packages/mcp-server/src/tools/analyze.ts
Large Files · packages/directory/src/directory.service.ts: 758 lines of code packages/directory/src/directory.service.ts
Large Files · packages/core/src/integration/utilities/aws-error-factory.ts: 597 lines of code packages/core/src/integration/utilities/aws-error-factory.ts
Large Files · packages/core/src/commands/command.service.ts: 577 lines of code packages/core/src/commands/command.service.ts
Large Files · packages/import/src/import.service.ts: 574 lines of code packages/import/src/import.service.ts
Large Files · packages/master/src/services/master-setting.service.ts: 500 lines of code packages/master/src/services/master-setting.service.ts
Large Files · packages/core/src/commands/command.event.handler.ts: 460 lines of code packages/core/src/commands/command.event.handler.ts
Large Files · packages/import/src/event/csv-import.sfn.event.handler.ts: 441 lines of code packages/import/src/event/csv-import.sfn.event.handler.ts
Large Files · packages/core/src/integration/utilities/test-data-builders.ts: 429 lines of code packages/core/src/integration/utilities/test-data-builders.ts
Large Files · packages/mcp-server/src/prompts/cqrs-guide.ts: 421 lines of code packages/mcp-server/src/prompts/cqrs-guide.ts
Large Files · packages/core/src/data-store/dynamodb.service.ts: 412 lines of code packages/core/src/data-store/dynamodb.service.ts
Dependency Hygiene · Unused dependency '@nestjs/testing'
Dependency Hygiene · Unused dependency 'nestjs-spelunker'
Exception handling · Swallowed exception (empty catch) packages/cli/src/actions/install-skills.action.ts
Exception handling · Swallowed exception (empty catch) packages/cli/src/actions/install-skills.action.ts
Exception handling · Swallowed exception (empty catch) packages/core/src/commands/repository.ts
Exception handling · Swallowed exception (empty catch) packages/core/src/commands/repository.ts
Exception handling · Swallowed exception (empty catch) packages/core/src/commands/repository.ts
Exception handling · Swallowed exception (empty catch) packages/core/src/commands/repository.ts
Exception handling · Swallowed exception (caught, then discarded) packages/core/src/commands/command.service.ts
Exception handling · Swallowed exception (empty catch) packages/master/src/update-scheme.ts
Exception handling · Swallowed exception (empty catch) packages/master/src/update-scheme.ts
Exception handling · Swallowed exception (empty catch) packages/master/src/update-scheme.ts
Exception handling · Swallowed exception (empty catch) packages/tenant/src/update-scheme.ts
Outbound HTTP resilience · Outbound HTTP without resilience packages/core/src/notifications/appsync.service.ts
Async & latency hygiene · Sync-over-async blocking packages/cli/src/actions/install-skills.action.ts
Async & latency hygiene · Sync-over-async blocking packages/cli/src/actions/install-skills.action.ts
Async & latency hygiene · Sync-over-async blocking packages/cli/src/actions/install-skills.action.ts
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking REDACTED
Async & latency hygiene · Sync-over-async blocking packages/cli/src/actions/ui.action.ts
Async & latency hygiene · Sync-over-async blocking packages/cli/src/actions/ui.action.ts
Async & latency hygiene · Sync-over-async blocking packages/cli/src/actions/ui.action.ts
Async & latency hygiene · Sync-over-async blocking packages/cli/src/actions/ui.action.ts
Async & latency hygiene · Sync-over-async blocking packages/core/test/scripts/start.ts
Async & latency hygiene · Sync-over-async blocking packages/core/test/scripts/start.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/resources/project.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/resources/project.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/resources/project.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/tools/validate.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/utils/fs.ts
Async & latency hygiene · Sync-over-async blocking packages/mcp-server/src/utils/fs.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: 144 findings

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

Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Supply-chain Provenance & Signing REDACTED
Code Duplication · Duplicated block (19 lines × 6 locations) packages/core/src/integration/utilities/aws-mock-manager.ts
Code Duplication · Duplicated block (19 lines × 2 locations) packages/master/src/controllers/master-setting.controller.ts
Code Duplication · Duplicated block (19 lines × 2 locations) packages/mcp-server/src/tools/analyze.ts
Code Duplication · Duplicated block (19 lines × 2 locations) packages/tenant/src/dto/tenant-create.dto.ts
Code Duplication · Duplicated block (18 lines × 2 locations) packages/core/src/notifications/event/notification.event.ts
Code Duplication · Duplicated block (18 lines × 3 locations) packages/tenant/src/dto/tenant-create.dto.ts
Code Duplication · Duplicated block (18 lines × 2 locations) packages/tenant/src/services/tenant.service.ts
Code Duplication · Duplicated block (17 lines × 2 locations) packages/core/src/data-store/dynamodb.service.ts
Code Duplication · Duplicated block (17 lines × 2 locations) packages/survey-template/src/survey-template.service.ts
Code Duplication · Duplicated block with local edits (16 matched lines × 2 locations) packages/core/src/commands/data.service.ts
Code Duplication · Duplicated block (16 lines × 4 locations) packages/core/src/interfaces/command.entity.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/master/src/dto/master-bulk/master-bulk-item.dto.ts
Code Duplication · Duplicated block (16 lines × 2 locations) packages/master/src/services/master-data.service.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/cli/schematics/lib/module/files/async/__name@dasherize__.module.ts
Code Duplication · Duplicated block (15 lines × 2 locations) REDACTED
Code Duplication · Duplicated block with local edits (15 matched lines × 2 locations) packages/master/src/helpers/rds.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/master/src/services/master-setting.service.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/mcp-server/src/tools/analyze.ts
Code Duplication · Duplicated block (15 lines × 3 locations) packages/sequence/src/dto/generate-formatted-sequence-with-provided-setting.dto.ts
Code Duplication · Duplicated block (15 lines × 2 locations) packages/survey-template/src/survey-template.module.ts
Code Duplication · Duplicated block with local edits (14 matched lines × 2 locations) packages/core/src/commands/command.event.handler.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/directory/src/directory.module.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/master/src/dto/master-copy/master-data-search.dto.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/master/src/dto/master-setting/common-setting-create.dto.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/master/src/services/master-setting.service.ts
Code Duplication · Duplicated block (14 lines × 2 locations) packages/mcp-server/test-mcp.js
Code Duplication · Duplicated block (13 lines × 2 locations) REDACTED
Code Duplication · Duplicated block (13 lines × 2 locations) packages/core/src/queue/sqs.service.ts
Code Duplication · Duplicated block (13 lines × 3 locations) packages/import/src/import.service.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/mcp-server/src/resources/project.ts
Code Duplication · Duplicated block (13 lines × 4 locations) packages/mcp-server/src/tools/generator.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/sequence/src/sequences.controller.ts
Code Duplication · Duplicated block (13 lines × 2 locations) packages/tenant/src/services/tenant.service.ts
Code Duplication · Duplicated block (12 lines × 4 locations) packages/cli/schematics/lib/controller/units/__name@dasherize__.controller.__specFileSuffix__.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/core/src/commands/command.service.ts
Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/core/src/commands/command.service.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/directory/src/directory.service.ts
Code Duplication · Duplicated block (12 lines × 3 locations) packages/import/src/import.service.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/master/src/services/master-setting.service.ts
Code Duplication · Duplicated block (12 lines × 3 locations) packages/mcp-server/src/tools/analyze.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/sequence/src/sequence.module.ts
Code Duplication · Duplicated block (12 lines × 2 locations) packages/tenant/src/services/tenant.service.ts
Code Duplication · Duplicated block (11 lines × 3 locations) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-create.dto.ts
Code Duplication · Duplicated block (11 lines × 3 locations) packages/core/src/command-events/data-sync.new.event.ts
Code Duplication · Duplicated block (11 lines × 5 locations) packages/master/src/controllers/master-setting.controller.ts
Code Duplication · Duplicated block (11 lines × 3 locations) packages/master/src/services/master-data.service.ts
Code Duplication · Duplicated block (11 lines × 2 locations) packages/master/src/update-scheme.ts
Code Duplication · Duplicated block (10 lines × 4 locations) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/cli/templates/src/helpers/get-order.ts
Code Duplication · Duplicated block (10 lines × 6 locations) packages/cli/templates/src/helpers/id.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/directory/src/dynamodb.service.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/import/src/event/csv-import.sfn.event.handler.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/import/src/import.service.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/master/src/controllers/master-setting.controller.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/master/src/templates/master/helpers/id.ts
Code Duplication · Duplicated block with local edits (10 matched lines × 2 locations) packages/mcp-server/src/resources/errors.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/survey-template/src/handler/survey-answer-rds.handler.ts
Code Duplication · Duplicated block (10 lines × 2 locations) packages/task/src/event/task.queue.event.handler.ts
Code Duplication · Duplicated block (9 lines × 3 locations) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-command.dto.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/core/src/commands/repository.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/core/src/integration/utilities/test-assertions.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/master/src/helpers/index.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/master/src/services/master-data.service.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/mcp-server/src/tools/analyze.ts
Code Duplication · Duplicated block (9 lines × 2 locations) packages/survey-template/src/survey-answer.controller.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/core/src/command-events/data-sync.new.event.handler.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/core/src/data-store/dynamodb.service.ts
Code Duplication · Duplicated block (8 lines × 2 locations) packages/import/src/event/processor/single-import.processor.ts
Code Duplication · Duplicated block (7 lines × 3 locations) packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-command.entity.ts
Code Duplication · Duplicated block (7 lines × 3 locations) packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-data-list.entity.ts
Code Duplication · Duplicated block (7 lines × 3 locations) packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-data.entity.ts
Code Duplication · Duplicated block (7 lines × 3 locations) packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts
Code Duplication · Duplicated block (7 lines × 2 locations) packages/cli/schematics/lib/module/module.factory.ts
Code Duplication · Duplicated block (7 lines × 2 locations) packages/import/src/event/csv-import.sfn.event.handler.ts
Code Duplication · Duplicated block (6 lines × 3 locations) packages/import/src/event/processor/single-import.processor.ts
Code Duplication · Duplicated block (5 lines × 2 locations) packages/master/src/handler/master-sfn-task.handler.ts
Test Coverage · No test reaches this file packages/master/src/templates/master/entity/master-data-list.entity.ts
Test Coverage · No test reaches this file packages/mcp-server/bin/mcp-server.js
Test Coverage · No test reaches this file packages/survey-template/src/entity/survey-template-command.entity.ts
Test Coverage · No test reaches this file packages/ui-setting/src/entities/setting-command.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-command.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-data-list.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-data.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/module/files/async/entity/__name@dasherize__-command.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/module/files/async/entity/__name@dasherize__-data-list.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/module/files/async/entity/__name@dasherize__-data.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/module/files/sync/entity/__name@dasherize__-command.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/module/files/sync/entity/__name@dasherize__-data-list.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/module/files/sync/entity/__name@dasherize__-data.entity.ts
Test Coverage · No test reaches this file packages/cli/schematics/lib/service/files/__name@dasherize__.service.ts
Test Coverage · No test reaches this file packages/directory/src/entity/directory-command.entity.ts

Rebuild cost: about €83,000 · Estimate

Cost to rebuild	€28,000 to €140,000, for 461 to 1,464 hours of work, about 0.6 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 43. 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: 29,847 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.

Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2).

Raises the score by about 13 points · Low effort · REDACTED Scanning

Resolve the 1 No ADRs found finding(s) in ADR Quality.

Raises the score by about 3 points · Low effort · ADR Quality

Resolve the 101 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (101).

Raises the score by about 10 points · High effort · Dependency Hygiene

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 €83,000 to build again, about 0.6 person-years of work. Its weakest lens is Production Readiness, at 29 (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 REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 13 points for low effort, because it clears the 2 REDACTED 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

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.

436 modules, with 670 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; 396 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	1 packages.core.src.context.invoke	2 packages.core.src.data-store.s3_service	3 packages.core.src.interfaces.aws.step-function_interface	4 packages.core.src.interfaces.command-model_interface	6 packages.core.src.interfaces.data-list_entity	7 packages.core.src.interfaces.detail-key_interface	8 packages.core.src.interfaces.event-handler_interface	9 packages.core.src.interfaces.event_interface	10 packages.core.src.interfaces.search_dto	11 examples.master.src.master.entity.master-data-list_entity	12 packages.core.src.command-events.data-sync_sfn_event	13 packages.core.src.data-store.dynamodb_service	15 packages.core.src.interfaces.data-sync-handler_interface	16 packages.core.src.interfaces.data_entity	17 packages.core.src.interfaces.detail_dto	18 packages.master.src.interfaces.master-setting_interface	19 packages.tenant.src.interfaces.tenant_service_interface	20 examples.master.src.master.entity.master-data_entity	21 packages.core.src.commands.data_service	23 packages.sequence.src.sequences_service	24 packages.task.src.task_service	25 packages.core.src.commands.history_service	26 packages.core.src.commands.command_service	32 packages.directory.src.directory_service	33 packages.master.src.services.master-data_service	34 packages.master.src.services.master-setting_service
1 packages.core.src.context.invoke
2 packages.core.src.data-store.s3_service
3 packages.core.src.interfaces.aws.step-function_interface
4 packages.core.src.interfaces.command-model_interface
5 packages.core.src.interfaces.command_dto
6 packages.core.src.interfaces.data-list_entity
7 packages.core.src.interfaces.detail-key_interface
8 packages.core.src.interfaces.event-handler_interface
9 packages.core.src.interfaces.event_interface
10 packages.core.src.interfaces.search_dto
11 examples.master.src.master.entity.master-data-list_entity					1
12 packages.core.src.command-events.data-sync_sfn_event		1	1	1		1		1
13 packages.core.src.data-store.dynamodb_service		1				1
14 packages.core.src.interfaces.command_entity				1		1
15 packages.core.src.interfaces.data-sync-handler_interface				1
16 packages.core.src.interfaces.data_entity						1
17 packages.core.src.interfaces.detail_dto						1
18 packages.master.src.interfaces.master-setting_interface				1		1			1
19 packages.tenant.src.interfaces.tenant_service_interface				1		1
20 examples.master.src.master.entity.master-data_entity														1
21 packages.core.src.commands.data_service				1	1	1						1
22 packages.import.src.import_service		1				1						1
23 packages.sequence.src.sequences_service						1						1		1
24 packages.task.src.task_service						1						1
25 packages.core.src.commands.history_service						1						1							1
26 packages.core.src.commands.command_service				1		1						1	1						1			1
27 examples.master.src.master.master_controller									1	1					1			1	1				1
28 examples.seq.src.master.master_controller									1	1					1			1	1	1			1
29 packages.cli.templates.src.sample.sample_controller	1								1						1				1				1
30 packages.core.src.commands.command_event_handler		1		1		1					2								1			1	1
31 packages.core.src.commands.repository					1	1													1				1
32 packages.directory.src.directory_service		1										1			1				1				1
33 packages.master.src.services.master-data_service	1														1			1	1				1
34 packages.master.src.services.master-setting_service	1			1		1			1			1			1	1			1		1		1
35 packages.survey-template.src.survey-template_service									1						1				1				1
36 packages.tenant.src.services.tenant_service				1		1											1		1				1
37 packages.directory.src.directory_controller	1														1									1
38 packages.master.src.controllers.master-data_controller	1														1										1
39 packages.master.src.controllers.master-setting_controller	1														1											1
40 packages.master.src.handler.master-sfn-task_handler	1						1					1							1	1					1	1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 55% · Adequate · gated by X5 ·

The Good

D1 · TypeScript Cyclomatic Complexity 8.2 D2 · TypeScript Cognitive Complexity 7.0 D3 · TypeScript God Classes 9.5 D17 · TypeScript Explicit Debt 10.0 GD1 · Repo Unfinished & placeholder code 10.0 R1 · React / TS Type Safety 8.0 R10 · React / TS Code Duplication 8.3 R2 · React / TS Cyclomatic Complexity 9.8 R3 · React / TS Large Files 9.1 R7 · React / TS Dead Code 8.1 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 7.5 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X30 · Repo Support guard that admits what it rejects 10.0

The Bad

IC1 · Repo Incompleteness & stubs 7.0 X3 · Repo Exception handling 5.4

The Ugly

X2 · Repo Cancellation propagation 4.0 X5 · Repo Nullable reference types 2.9

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

The Good

D5 · TypeScript Coupling 9.5 D6 · TypeScript Cohesion (LCOM4) 9.8 D23 · TypeScript Boundary Type-Coupling 9.9 D26 · TypeScript Project Cohesion 8.7 D35 · TypeScript Change Coupling 10.0 AX10 · Repo Code composition 9.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX6 · Repo Interface segregation 10.0 AX8 · Repo Test isolation 10.0

The Bad

D22 · TypeScript Internal API Consistency 6.0

The Ugly

R9 · React / TS Circular Imports 0.4

At a glance — Maturity · 50% · Weak · gated by M4 ·

The Good

D15 · TypeScript Churn × Complexity Hotspots 9.9 D19 · TypeScript Documentation Quality 9.0 D21 · TypeScript Naming Consistency 10.0 D34 · TypeScript Knowledge Freshness 9.5 M1 · Repo Documentation (README) 8.1 M3 · Repo Folder & project structure 10.0

The Bad

D16 · TypeScript Bus Factor 6.8 M2 · Repo Architecture documentation 5.0

The Ugly

D20 · TypeScript ADR Quality 0.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 29% · Weak · gated by D13, R5, R8, P5, P7 ·

The Good

D8 · TypeScript Code Coverage 9.5 D9 · TypeScript Test Distribution 9.9 D10 · TypeScript Test Quality 10.0 D11 · TypeScript Test Reliability 10.0 D12 · TypeScript Dependency Hygiene 7.6 D14 · TypeScript License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P10 · Repo Library API & versioning 10.0 P3 · Repo Security & performance tooling 7.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 10.0 R4 · React / TS Test Coverage 8.2 R6 · React / TS Tooling 10.0

The Bad

P2 · Repo Observability 6.8

The Ugly

D13 · TypeScript REDACTED Scanning 0.0 P5 · Repo DR & Backup 0.0 P7 · Repo Outbound HTTP resilience 3.0 R5 · React / TS Dependency Freshness 2.7 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 67% · Adequate · gated by D28, D29, D30, D36 ·

The Good

D31 · TypeScript IaC & Container Security 7.0 D43 · TypeScript Malicious Dependencies 10.0 D44 · TypeScript Platform End-of-Life 10.0 C2 · Repo Access Controls 10.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X24 · Repo Document value interpolated into markup unescaped 10.0

The Ugly

D28 · TypeScript Secrets (history) 0.0 D29 · TypeScript Static Analysis (SAST) 0.4 D30 · TypeScript Dependency Vulnerabilities 0.0 D36 · TypeScript Supply-chain Provenance & Signing 0.0 D37 · TypeScript Vulnerability-disclosure Policy 4.0 X17 · Repo Uncapped recursion over a caller-supplied document 3.5

At a glance — Domain Modelling · — · — ·

The Good

DM9 · Repo Scattered domain decisions 10.0

At a glance — Performance · 60% · Adequate ·

The Bad

PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A03:2025 — Software Supply Chain Failures	104	High / Critical
A05:2025 — Injection	57	High / Critical
A02:2025 — Security Misconfiguration	16	High / Critical
A07:2025 — Authentication Failures	14	High / Critical

Roadmap

Immediately resolve the two leaked secrets in the environment configuration and eliminate the extensive list of deprecated dependencies to secure the codebase. Strengthen operational resilience by codifying backup and geo-recovery procedures in infrastructure as code, while also cleaning up unused and misclassified packages. Finally, establish architectural decision records to document key technical choices and ensure long-term maintainability.

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 REDACTED Scanning — start with REDACTED (2).	+12.6 pts	Low	REDACTED Scanning
Resolve the 1 No ADRs found finding(s) in ADR Quality.	+3.0 pts	Low	ADR Quality
Resolve the 101 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (101).	+9.9 pts	High	Dependency Hygiene
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.	+4.7 pts	Medium	DR & Backup
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+4.7 pts	Medium	Dependency Hygiene
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with reflect-metadata-behavior.spec.ts.	+2.3 pts	Low	Test Quality
Resolve the 2 Off-boarding risk finding(s) in Bus Factor.	+1.6 pts	Low	Bus Factor
Reconcile the README with reality: docs/ERROR_CATALOG.md names the package `@mbc-cqrs-serverless/import@^0.1.75`, but no package.json of the workspace declares or depends on it; docs/ERROR_CATALOG.md runs `DEBUG=* npm run offline`, but no package.json declares a `offline` script; docs/testing/README.ja.md names `.e2e-spec.ts`, but no file or folder `.e2e-spec.ts` exists; docs/testing/README.ja.md names `REDACTED.test`, but no file or folder `REDACTED.test` exists; docs/testing/README.md names `REDACTED.test`, but no file or folder `REDACTED.test` exists.	+2.9 pts	Medium	Documentation accuracy

File quality

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

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	1.6	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	2.3	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.7	Slop	Static Analysis (SAST): High: REDACTED
REDACTED	3.7	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	4.1	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.4	Mixed	Secrets (history): REDACTED: REDACTED
REDACTED	4.4	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.4	Mixed	IaC & Container Security: High IaC: REDACTED
REDACTED	4.6	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.8	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.9	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.3	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.3	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.3	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.3	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	6.9	Mixed	Static Analysis (SAST): Medium: REDACTED
packages/mcp-server/src/tools/analyze.ts	7.0	Mixed	Cyclomatic Complexity: analyze.explainCode (cyclomatic 37)
packages/core/src/data-store/dynamodb.service.ts	7.0	Mixed	Cognitive Complexity: DynamoDbService.buildUpdateSetExpression (cognitive 33)

How the grades work

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

Critical — 141

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

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

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

Could not be resolved — 4

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 84 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 5 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 — 84 dimensions across the health lenses

D1D2D3D5D6D8D9D10D11D12D13D14D15D16D17D19D20D21D22D23D26D28D29D30D31D34D35D36D37D43D44AX10AX3AX4AX6AX8C2DM9GD1IC1M1M2M3M4P1P10P2P3P4P5P6P7PF3R1R10R2R3R4R5R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X5

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, 646 of 696 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	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16444-68b1-73de-b0ad-3d02a60babaf.

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

Run transparency — what happened this run

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

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/cli/schematics/lib/controller/files/__name@dasherize__.controller.ts`, `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-attributes.dto.ts`, `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-command.dto.ts`, `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-create.dto.ts`, `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-search.dto.ts`, … (+29 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence.
DM9 Scattered domain decisions — 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. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
P8 Schema migrations — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The schema may be created by a runner, a deploy script or a config file outside what this check reads, so an absence here is our blind spot rather than a missing migration strategy. The card abstains instead of scoring. You can widen what we reach: if the schema is created and evolved by a tool this check does not name, naming it lets us teach the detector to read it.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 76 further occurrence(s) are not listed individually; the score already reflects all 116.
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. 34 further occurrence(s) are not listed individually; the score already reflects all 74.
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. 42 further occurrence(s) are not listed individually; the score already reflects all 82.
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 (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

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 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality 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.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
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 REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
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 (5): D19, D21, D22, D26, 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.

Dimensions

D1 · Cyclomatic Complexity8.2 / 10Strong✓ Tool-verified

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

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

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

11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was analyze.explainCode at 37. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being aws-error-factory.createSFNError at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: packages/core/src/integration/utilities/aws-error-factory.ts (aws-error-factory.createSFNError at 18). 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.

analyze.explainCode (cyclomatic 37)packages/mcp-server/src/tools/analyze.ts:1190

Repository.listItems (cyclomatic 30)packages/core/src/commands/repository.ts:285

CsvImportSfnEventHandler.handleStepState (cyclomatic 23)packages/import/src/event/csv-import.sfn.event.handler.ts:61

analyze.healthCheck (cyclomatic 21)packages/mcp-server/src/tools/analyze.ts:1008

analyze.analyzeProject (cyclomatic 20)packages/mcp-server/src/tools/analyze.ts:196

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

What to do

Bring the 1 body over 30 down to 30 or less in Cyclomatic Complexity — start with analyze.explainCode (cyclomatic 37). — Refactoring it lifts Cyclomatic Complexity from 8.2 to about 8.4/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.

Do you agree with this assessment?

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

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

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

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

21 method(s) exceeded the cognitive complexity threshold of 15; the worst was analyze.explainCode at 52.

analyze.explainCode (cognitive 52)packages/mcp-server/src/tools/analyze.ts:1190

analyze.healthCheck (cognitive 45)packages/mcp-server/src/tools/analyze.ts:1008

Repository.listItems (cognitive 39)packages/core/src/commands/repository.ts:285

analyze.analyzeProject (cognitive 38)packages/mcp-server/src/tools/analyze.ts:196

DynamoDbService.buildUpdateSetExpression (cognitive 33)packages/core/src/data-store/dynamodb.service.ts:309

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

What to do

Bring the 21 bodies over 15 down to 15 or less in Cognitive Complexity — start with analyze.explainCode (cognitive 52), analyze.healthCheck (cognitive 45), Repository.listItems (cognitive 39). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 21 together lifts Cognitive Complexity from 7.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D3 · God Classes9.5 / 10Stronggated by 6 serious findings✓ Tool-verified

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

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

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

6 god class(es) detected.

FileTooLong: libs/infra-stack.ts · ×3packages/cli/templates/infra/libs/infra-stack.ts

ClassTooLong: InfraStack · ×2packages/cli/templates/infra/libs/infra-stack.ts:29

MethodTooLong: InfraStack.constructorpackages/cli/templates/infra/libs/infra-stack.ts:39

What to do

Resolve the 3 FileTooLong finding(s) in God Classes — start with infra-stack.ts, analyze.ts, directory.service.ts. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 ClassTooLong finding(s) in God Classes — start with infra-stack.ts, directory.service.ts. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 MethodTooLong finding(s) in God Classes — start with infra-stack.ts. — One of this dimension's main actionable groups (1 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D5 · Coupling9.5 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

16 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence, with abstractness counted on 14 of the 16 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

Off the main sequence: @mbc-cqrs-serverless/core

What to do

Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

1 of 64 classes have LCOM4 above 3.

Low cohesion: DynamoDbService (LCOM4 5)packages/core/src/data-store/dynamodb.service.ts:36

What to do

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

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

Do you agree with this assessment?

D8 · Code Coverage9.5 / 10Stronggated by 5 serious findings✓ Tool-verified

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

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

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

Line coverage 64.1% — 5 file(s) below 50%. Measured from the JavaScript/TypeScript suite (jest in the repository root: not run; jest in packages/cli/templates/: not run; jest in packages/cli/templates/infra/: not run; jest via `npm ci --ignore-scripts` in packages/mcp-server/).

Low coverage: packages/mcp-server/src/index.ts · ×5packages/mcp-server/src/index.ts:1

What to do

Resolve the 5 Low coverage finding(s) in Code Coverage — start with index.ts, server.ts, documentation.ts. — One of this dimension's main actionable groups (5 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.9 / 10Exemplary✓ Tool-verified

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

2 skipped (2 with a documented reason), 9 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3733 tests.

Assertions commented out: should preserve design:type for propertiespackages/core/src/integration/reflect-metadata-behavior.spec.ts:381

No assertions: lambda-api SendTaskSuccess is scoped to command-handler state machine · ×8packages/cli/templates/infra/test/infra.test.ts:110

Mock-dominated test: should resume next command when getNextCommand finds a taskToken · ×8packages/core/src/commands/command.event.handler.spec.ts:1013

Skipped (documented): (unnamed test) · ×2packages/core/src/integration/nestjs-platform-express-behavior.spec.ts:258

What to do

Resolve the 1 Assertions commented out finding(s) in Test Quality — start with reflect-metadata-behavior.spec.ts. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 8 No assertions finding(s) in Test Quality — start with rxjs-schedulers.spec.ts (6), infra.test.ts, utilities-demo.spec.ts. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 8 Mock-dominated test finding(s) in Test Quality — start with command.event.handler.spec.ts (6), roles.guard.spec.ts, sub-task.queue.event.handler.spec.ts. — One of this dimension's main actionable groups (8 recommendation-level).
Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in the repository root (3047 tests); jest via `npm ci --ignore-scripts` in packages/cli/templates/ (0 tests); jest via `npm ci --ignore-scripts` in packages/cli/templates/infra/ (0 tests); jest via `npm ci --ignore-scripts` in packages/mcp-server/ (280 tests)): measured (0 flaky).

✓ On the Gold path — maintain.

Detailed fixes: d11_recommendation.md.

Do you agree with this assessment?

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

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.

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

28 outdated direct production npm dependency(ies) of 36 graded, 0 pinning defect(s), across 21 package.json (12 of them the product) and 8 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Deprecated: @aws-sdk/signature-v4 · ×2package.json:53

Deprecated: @hapi/address · ×101REDACTED:3667

Outdated (npm): @angular-devkit/core · ×9package.json:157

Outdated (npm): @codegenie/serverless-express · ×19

What to do

Resolve the 101 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (101). — One of this dimension's main actionable groups (101 recommendation-level).
Resolve the 9 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (9). — One of this dimension's main actionable groups (9 recommendation-level).
Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with package.json (2). — One of this dimension's main actionable groups (2 warning-level).

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

Do you agree with this assessment?

D13 · REDACTED Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

2 secret(s) detected.

REDACTED

What to do

Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Enforce REDACTED 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.

Do you agree with this assessment?

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

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

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

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

0 of 36 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 36 production dependency(ies) this repository's committed lockfile resolves, across 12 product package.json manifest(s). Its 157 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

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

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

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

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

Top hotspots: packages/cli/templates/infra/libs/infra-stack.ts (5×18=90) Repeated repair below the complexity floor: packages/core/src/commands/command.event.handler.ts (10 of 11 changes were fixes); packages/core/src/commands/command.service.ts (5 of 6 changes were fixes); packages/core/src/commands/command-module.helper.ts (4 of 4 changes were fixes)

Repeated repair: packages/core/src/commands/command.event.handler.ts · ×4packages/core/src/commands/command.event.handler.ts:106

Hotspot: packages/cli/templates/infra/libs/infra-stack.tspackages/cli/templates/infra/libs/infra-stack.ts:39

What to do

Resolve the 4 Repeated repair finding(s) in Churn × Complexity Hotspots — start with command.event.handler.ts, command.service.ts, command-module.helper.ts. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 1 Hotspot finding(s) in Churn × Complexity Hotspots — start with infra-stack.ts. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D16 · Bus Factor6.8 / 10Adequate✓ Tool-verified

What it measures: Whether knowledge is concentrated in too few people (the "bus factor").

Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.

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

29 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/mcp-server/src/tools/analyze.ts. Counted over 92 of the 527 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1 · ×2

Further sole-owners (lower concentration)

What to do

Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

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

TodoComment · ×6packages/cli/src/actions/start.action.ts:4

What to do

Resolve the 6 TodoComment finding(s) in Explicit Debt — start with start.action.ts, data-sync.sfn.event.ts, tenant-normalization.spec.ts. — One of this dimension's main actionable groups (6 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.

Do you agree with this assessment?

D19 · Documentation QualityExemplary◐ Sampled · advisory

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.

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

The repository's root README and the docs/testing/README are both excellent at conveying what the MBC CQRS Serverless framework is (a serverless CLI for building enterprise-grade applications with event sourcing, multi-tenancy, and a comprehensive test suite), its features (zero-to-API in 5 minutes, unified subscription interface, bilingual dashboard), installation (global install, version-specific installs), and quick-start commands. The READMEs of the packages directories are also well written: each one explains what package it documents (e.g., directory management, flexible import module) and gives a clear overview plus configuration examples for its module. The documentation is comprehensive and well-structured: each README of a package (mcp-server, sequence, survey-template, task, tenant, ui-setting, cli templates) documents its directory with an overview, features list, installation, quick start, usage examples, API reference, configurable table name, and license. The architecture/Docs markdown files provide the full design documentation for the MBC CQRS Serverless framework (resources, tools, anti-pattern detection, migration guide), which is referenced by each package README as needed. All visible documents are complete and well-organized. The repository's documentation is comprehensive and well-organized: the READMEs cover dependency management (version pinning, adding new dependencies), an error catalog with detailed command-service, tenant-, and UI-setting error types plus solutions, serialization helpers for DynamoDB-to-flat structure conversion, a CQRS flow diagram, event-sourcing architecture including event lifecycle, DynamoDB schema, optimistic-locking example, and a dedicated test guide covering unit/integration/E2E testing. The architecture documents are especially strong (flow diagrams, version control implementation).

✓ On the Gold path — maintain.

Detailed fixes: d19_recommendation.md.

Do you agree with this assessment?

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

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

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

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

No architecture decision records were found.

No ADRs found

What to do

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

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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.

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

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

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

4 API inconsistencies across a 400-member sample of 321 exposed types.

Redundant naming and likely overlapping functionality. `toISOString` is a standard native method that produces ISO 8601 strings. The suffix `WithTimezone` implies a difference, but without seeing the implementation, it is unclear if this is a distinct operation or just a confusingly named wrapper. If they both produce ISO strings, the distinction is unclear. If one includes timezone offset and the other doesn't, the naming is non-standard (usually `toISOString` includes offset, while `toUTCString` or similar might not).

Redundant validation methods mirroring the conversion methods above. If the conversion methods are redundant or confusingly named, the validation methods are too. It creates a parallel set of ambiguous checks.

Interface and Implementation duplication. While common in some patterns, `ICommandService` exposes `publishSync` and `publishAsync`, and `CommandService` implements them. However, `CommandService` also exposes `publishItem`, `duplicate`, `reSyncData`, `updateStatus`, `getItem`, `getLatestItem`, `updateTtl`, `updateTaskToken`, `getNextCommand`. The interface `ICommandService` is significantly smaller than the implementation `CommandService`. This suggests `ICommandService` is not a true contract for `CommandService`, or `CommandService` is doing too much (violating Single Responsibility).

Confusingly similar operations with different signatures and likely different intents. `DataService.publish` takes a `CommandModel`. `CommandService.publishItem` takes a `DetailKey`. `CommandService.publishSync` takes a `CommandInputModel`. It is unclear why there are three different 'publish' entry points with different input types. `publishItem` returning `any` is also inconsistent with the typed returns of `publishSync`.

What to do

Resolve the 1 Redundant naming and likely overlapping functionality. `toISOString` is… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Redundant validation methods mirroring the conversion methods above. If… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Interface and Implementation duplication. While common in some patterns,… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D23 · Boundary Type-Coupling9.9 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

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

2 domain type(s) cross context boundaries across 11 contexts.

Cross-context type RotateByEnum (sequence → master) · ×2packages/master/src/helpers/index.ts:53

What to do

Resolve the 2 Cross-context type RotateByEnum (sequence → master) finding(s) in Boundary Type-Coupling — start with index.ts, id.ts. — One of this dimension's main actionable groups (2 warning-level).
Enforce Boundary Type-Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

1 of 15 build units (npm) flagged as possibly oversized/incoherent.

Split packages/core

What to do

Resolve the 1 Split packages/core finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

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

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

REDACTED

What to do

Resolve the 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (11). — One of this dimension's main actionable groups (11 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.

Do you agree with this assessment?

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

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

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

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

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

57 finding(s): 0 critical, 31 high, 24 medium, 2 low. 20 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 39 file(s) — `packages/cli/schematics/lib/controller/files/__name@dasherize__.controller.ts` (line 6, line 7), `packages/cli/schematics/lib/controller/units/__name@dasherize__.controller.__specFileSuffix__.ts` (line 3, line 6, line 10, …), `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-attributes.dto.ts` (lines 3–6), `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-command.dto.ts` (line 5, lines 7–10, line 10, …), `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-create.dto.ts` (line 4, line 6, lines 6–8, …), … (+34 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 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

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

What to do

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

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

Do you agree with this assessment?

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

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

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

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

97 finding(s): 17 critical, 44 high, 25 medium, 11 low.

REDACTED

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

What to do

Resolve the 39 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (39). — One of this dimension's main actionable groups (39 issue-level).
Resolve the 17 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (17). — One of this dimension's main actionable groups (17 issue-level).
Resolve the 5 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).

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

Do you agree with this assessment?

D31 · IaC & Container Security7.0 / 10Adequategated by 7 critical findings✓ Tool-verified

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

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

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

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

REDACTED

What to do

Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 6 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4), REDACTED (2). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).

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

Do you agree with this assessment?

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

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

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

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

4 of 92 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/tenant/src/interfaces/tenant.service.interface.ts. Counted over 92 of the 527 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×4packages/tenant/src/interfaces/tenant.service.interface.ts:1

Orphaned files with no living knowledge

✓ On the Gold path — maintain.

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

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

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

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

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

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

Strongest change-coupling: master-data.service.ts↔master-setting.service.ts 67%

Change coupling: master-data.service.ts ↔ master-setting.service.tspackages/master/src/services/master-data.service.ts:1

What to do

Resolve the 1 Change coupling finding(s) in Change Coupling — start with master-data.service.ts. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

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

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

REDACTED

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

What to do

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 — start with REDACTED. — 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.

Do you agree with this assessment?

D37 · Vulnerability-disclosure Policy4.0 / 10Weak✓ Tool-verified

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

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

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

A vulnerability-disclosure policy (SECURITY.md) is present but lists no reporting contact.

REDACTED

What to do

Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

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

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. 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.

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

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

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

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

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

0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 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.

✓ On the Gold path — maintain.

Detailed fixes: d44_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AX10 · Code composition9.0 / 10Strong✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX6 · Interface segregation10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

C2 · Access Controls10.0 / 10Exemplary○ Nothing flagged

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.

Do you agree with this assessment?

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary✓ Tool-verified

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/core/src/commands/command.service.ts:77

What to do

Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.

Do you agree with this assessment?

IC1 · Incompleteness & stubs7.0 / 10Adequate✓ Tool-verified

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

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

`generateAction` 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/cli/src/actions/generate.action.ts:9
`installSkillsAction` 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/cli/src/actions/install-skills.action.ts:257
`newAction` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — REDACTED:18
`startAction` 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/cli/src/actions/start.action.ts:2
`uiAction` 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/cli/src/actions/ui.action.ts:14
`generateCommand` 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/cli/src/commands/generate.command.ts:6
`publishItem` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it. — packages/core/src/commands/command.service.ts:77
`formatDynamo` 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/master/src/update-scheme.ts:15
`formatEventFactory` 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/master/src/update-scheme.ts:56

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.

Do you agree with this assessment?

M1 · Documentation (README)8.1 / 10Strong✓ Tool-verified

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

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

62 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

What to do

Add a README to the 4 of 18 project(s) that lack one — worth up to 0.4 pts.
Review the README against recent changes; refresh the parts that drifted.

Do you agree with this assessment?

M2 · Architecture documentation5.0 / 10Adequate✓ Tool-verified

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

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

No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

M4 · Documentation accuracy0.0 / 10Critical◐ Sampled · advisory

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/ERROR_CATALOG.md names the package `@mbc-cqrs-serverless/import@^0.1.75`, but no package.json of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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/ERROR_CATALOG.md:350
docs/ERROR_CATALOG.md runs `DEBUG=* npm run offline`, but no package.json declares a `offline` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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/ERROR_CATALOG.md:419
docs/testing/README.ja.md names `.e2e-spec.ts`, but no file or folder `.e2e-spec.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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/testing/README.ja.md:36
docs/testing/README.ja.md names `REDACTED.test`, but no file or folder `REDACTED.test` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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/testing/README.ja.md:38
docs/testing/README.md names `REDACTED.test`, but no file or folder `REDACTED.test` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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/testing/README.md:38

What to do

Reconcile the README with reality: docs/ERROR_CATALOG.md names the package `@mbc-cqrs-serverless/import@^0.1.75`, but no package.json of the workspace declares or depends on it; docs/ERROR_CATALOG.md runs `DEBUG=* npm run offline`, but no package.json declares a `offline` script; docs/testing/README.ja.md names `.e2e-spec.ts`, but no file or folder `.e2e-spec.ts` exists; docs/testing/README.ja.md names `REDACTED.test`, but no file or folder `REDACTED.test` exists; docs/testing/README.md names `REDACTED.test`, but no file or folder `REDACTED.test` exists.

Do you agree with this assessment?

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

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

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

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 · Observability6.8 / 10Adequate✓ Tool-verified

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

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

Only 12/13 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/cli/templates/infra`.
`packages/core/src/bootstrap.ts` reports through `console.*` at line 93 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/src/bootstrap.ts:93
`packages/core/src/bootstrap.ts` reports through `console.*` at line 98 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/src/bootstrap.ts:98
`packages/core/src/services/request-logger.service.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/src/services/request-logger.service.ts:30
`packages/mcp-server/src/server.ts` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/mcp-server/src/server.ts:64
`packages/mcp-server/src/server.ts` reports through `console.*` at line 76 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/mcp-server/src/server.ts:76
`packages/mcp-server/src/server.ts` reports through `console.*` at line 90 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/mcp-server/src/server.ts:90
`packages/mcp-server/src/server.ts` reports through `console.*` at line 106 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/mcp-server/src/server.ts:106
`packages/mcp-server/src/server.ts` reports through `console.*` at line 122 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/mcp-server/src/server.ts:122
`packages/mcp-server/src/server.ts` reports through `console.*` at line 137 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/mcp-server/src/server.ts:137
`packages/mcp-server/src/server.ts` reports through `console.*` at line 152 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/mcp-server/src/server.ts:152
`packages/mcp-server/src/server.ts` reports through `console.*` at line 164 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/mcp-server/src/server.ts:164
`packages/mcp-server/src/prompts/cqrs-guide.ts` reports through `console.*` at line 397 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/mcp-server/src/prompts/cqrs-guide.ts:397
`packages/mcp-server/src/prompts/cqrs-guide.ts` reports through `console.*` at line 403 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/mcp-server/src/prompts/cqrs-guide.ts:403
`packages/mcp-server/src/prompts/cqrs-guide.ts` reports through `console.*` at line 409 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/mcp-server/src/prompts/cqrs-guide.ts:409
`packages/mcp-server/src/prompts/cqrs-guide.ts` reports through `console.*` at line 411 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/mcp-server/src/prompts/cqrs-guide.ts:411
`packages/task/src/event/sub-task.queue.event.handler.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/task/src/event/sub-task.queue.event.handler.ts:27
`packages/task/src/event/sub-task.queue.event.handler.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/task/src/event/sub-task.queue.event.handler.ts:31

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.
Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.

Do you agree with this assessment?

P3 · Security & performance tooling7.0 / 10Strong✓ Tool-verified

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

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

What to do

Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

What to do

Add an approval/environment gate (required reviewers / protection rules) before production promotion.

Do you agree with this assessment?

P5 · DR & Backup0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.

What to do

Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.

Do you agree with this assessment?

P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

P7 · Outbound HTTP resilience3.0 / 10Weak✓ Tool-verified

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. (×3) — REDACTED:121, packages/core/src/notifications/appsync.service.ts:72, packages/core/src/notifications/appsync.service.ts:91

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?

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

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

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from 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.

`existsSync` in `installSkillsAction` 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/cli/src/actions/install-skills.action.ts:279, packages/cli/src/actions/install-skills.action.ts:331
`readdirSync` in `installSkillsAction` 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/cli/src/actions/install-skills.action.ts:332
`mkdirSync` in `newAction` 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:58
`copyFileSync` in `newAction` 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:65, REDACTED:69, REDACTED:78
`unlinkSync` in `newAction` 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:66, REDACTED:70
`execSync` in `newAction` 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:83, REDACTED:89, REDACTED:90
`existsSync` in `uiAction` 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/cli/src/actions/ui.action.ts:32
`readFileSync` in `uiAction` 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/cli/src/actions/ui.action.ts:39
`writeFileSync` in `uiAction` 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/cli/src/actions/ui.action.ts:71
`execSync` in `uiAction` 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/cli/src/actions/ui.action.ts:84
`fs.writeFileSync` in `callback to then` 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/src/bootstrap.ts:83
`readFileSync` in `callback to retry` 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/test/scripts/start.ts:63, packages/core/test/scripts/start.ts:79
`fs.existsSync` in `getProjectStructure` 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/mcp-server/src/resources/project.ts:106
`fs.existsSync` in `buildTree` 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/mcp-server/src/resources/project.ts:126
`fs.readdirSync` in `buildTree` 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/mcp-server/src/resources/project.ts:131
`fs.existsSync` in `analyzeProject` 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/mcp-server/src/tools/analyze.ts:219, packages/mcp-server/src/tools/analyze.ts:245
`fs.existsSync` in `lookupError` 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/mcp-server/src/tools/analyze.ts:341
`fs.existsSync` in `checkAntiPatterns` 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/mcp-server/src/tools/analyze.ts:888
`fs.existsSync` in `healthCheck` 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. (×6) — packages/mcp-server/src/tools/analyze.ts:1018, packages/mcp-server/src/tools/analyze.ts:1103, packages/mcp-server/src/tools/analyze.ts:1104, …
`fs.existsSync` in `explainCode` 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/mcp-server/src/tools/analyze.ts:1195
`fs.existsSync` in `validateCqrsPatterns` 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/mcp-server/src/tools/validate.ts:85, packages/mcp-server/src/tools/validate.ts:100
`fs.existsSync` in `findFiles` 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/mcp-server/src/utils/fs.ts:14
`fs.readdirSync` in `findFiles` 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/mcp-server/src/utils/fs.ts:18

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 Safety8.0 / 10Strong✓ Tool-verified

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

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

What to do

Migrate the remaining .js/.jsx files to TypeScript.

Do you agree with this assessment?

R10 · Code Duplication8.3 / 10Strong✓ Tool-verified

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

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

packages/cli/schematics/lib/module/files/async/ and packages/cli/schematics/lib/module/files/sync/ are near-verbatim copies of each other: 11 files are byte-identical under the same relative paths (~267 lines; the trees hold 12 and 12 files). That is one structural fact, not 11 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. — packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:1
53 duplicated blocks under packages/ have copies in at least two of the sibling directories cli, core, directory, import, master, sequence (+4 more sibling(s) not listed) — 30 of them are reported below, and 23 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 53 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 53 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 53 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/master/src/services/master-data.service.ts:186
10 of the duplicated blocks reported below have copies in at least two of the sibling directories controller, dto, entity, module, service under packages/cli/schematics/lib/. 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/cli/schematics/lib/controller/controller.factory.ts:16
packages/ui-setting/src/services/data-setting.service.ts:35 · packages/ui-setting/src/services/setting.service.ts:32 — the two spans are one implementation copied and then locally edited — 541 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/ui-setting/src/services/data-setting.service.ts:35
packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts:11 · packages/cli/schematics/lib/module/files/sync/__name@dasherize__.service.ts:11 — these 2 files are line-for-line copies of one another — 100 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/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts:11
packages/master/src/services/master-data.service.ts:186 · packages/ui-setting/src/services/data-setting.service.ts:79 — the two spans are one implementation copied and then locally edited — 400 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/master/src/services/master-data.service.ts:186
packages/master/src/controllers/master-data.controller.ts:61 · packages/master/src/controllers/master-setting.controller.ts:96 — the two spans are one implementation copied and then locally edited — 378 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/master/src/controllers/master-data.controller.ts:61
packages/sequence/src/sequences.service.ts:80 · packages/sequence/src/sequences.service.ts:165 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/sequence/src/sequences.service.ts:80
packages/core/src/data-store/dynamodb.service.ts:155 · packages/directory/src/dynamodb.service.ts:69 — the two spans are one implementation copied and then locally edited — 285 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/src/data-store/dynamodb.service.ts:155
packages/cli/schematics/lib/controller/controller.factory.ts:16 · packages/cli/schematics/lib/service/service.factory.ts:16 — 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/cli/schematics/lib/controller/controller.factory.ts:16
packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:26 · packages/cli/schematics/lib/module/files/sync/__name@dasherize__.controller.ts:26 — 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/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:26
packages/core/src/commands/repository.ts:171 · packages/core/src/commands/repository.ts:303 — the two spans are one implementation copied and then locally edited — 295 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/core/src/commands/repository.ts:171
packages/cli/schematics/lib/module/files/async/handler/__name@dasherize__-rds.handler.ts:17 · packages/cli/schematics/lib/module/files/sync/handler/__name@dasherize__-rds.handler.ts:17 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/cli/schematics/lib/module/files/async/handler/__name@dasherize__-rds.handler.ts:17
packages/core/src/interfaces/command.entity.ts:13 · packages/core/src/interfaces/data.entity.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/src/interfaces/command.entity.ts:13
packages/import/src/event/import.event.ts:14 · packages/task/src/event/task.event.ts:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/import/src/event/import.event.ts:14
packages/master/src/services/master-data.service.ts:299 · packages/master/src/services/master-setting.service.ts:332 — the two spans are one implementation copied and then locally edited — 210 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/master/src/services/master-data.service.ts:299
packages/task/src/task.service.ts:38 · packages/task/src/task.service.ts:77 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/task/src/task.service.ts:38
packages/master/src/dto/master-setting/group-setting-create.dto.ts:4 · packages/master/src/dto/master-setting/user-setting-create.dto.ts:4 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/master/src/dto/master-setting/group-setting-create.dto.ts:4
packages/directory/src/directory.service.ts:604 · packages/directory/src/directory.service.ts:669 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/directory/src/directory.service.ts:604
packages/master/src/dto/master-setting/group-setting-create.dto.ts:2 · packages/master/src/dto/master-setting/tenant-setting-create.dto.ts:2 · packages/master/src/dto/master-setting/user-setting-create.dto.ts:2 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — packages/master/src/dto/master-setting/group-setting-create.dto.ts:2
packages/master/src/services/master-setting.service.ts:231 · packages/master/src/services/master-setting.service.ts:260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/master/src/services/master-setting.service.ts:231
packages/ui-setting/src/controllers/data-setting.controller.ts:43 · packages/ui-setting/src/controllers/setting.controller.ts:43 — 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/ui-setting/src/controllers/data-setting.controller.ts:43
packages/directory/src/directory.service.ts:401 · packages/directory/src/directory.service.ts:435 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/directory/src/directory.service.ts:401
packages/cli/schematics/lib/dto/dto.factory.ts:17 · packages/cli/schematics/lib/entity/entity.factory.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. — packages/cli/schematics/lib/dto/dto.factory.ts:17
packages/import/src/import.service.ts:609 · packages/task/src/task.service.ts:289 — 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/import/src/import.service.ts:609
packages/core/src/commands/data.service.ts:17 · packages/core/src/commands/history.service.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/core/src/commands/data.service.ts:17
packages/directory/src/directory.module.ts:47 · packages/survey-template/src/survey-template.module.ts:53 — 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/directory/src/directory.module.ts:47
packages/directory/src/directory.service.ts:786 · packages/directory/src/directory.service.ts:829 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/directory/src/directory.service.ts:786
packages/master/src/helpers/index.ts:14 · packages/ui-setting/src/helpers/index.ts:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/master/src/helpers/index.ts:14
packages/import/src/event/processor/csv-batch.processor.ts:62 · packages/import/src/event/processor/single-import.processor.ts:153 — the two spans are one implementation copied and then locally edited — 77 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/import/src/event/processor/csv-batch.processor.ts:62
packages/master/src/master.module.ts:64 · packages/master/src/master.module.ts:112 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/master/src/master.module.ts:64
packages/ui-setting/src/setting.module.ts:26 · packages/ui-setting/src/setting.module.ts:65 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/ui-setting/src/setting.module.ts:26
packages/directory/src/directory.service.ts:234 · packages/directory/src/directory.service.ts:755 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/directory/src/directory.service.ts:234
packages/import/src/import.service.ts:118 · packages/import/src/import.service.ts:171 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/import/src/import.service.ts:118
packages/master/src/master.module.ts:94 · packages/survey-template/src/survey-template.module.ts:70 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/master/src/master.module.ts:94
packages/task/src/event/sub-task.queue.event.ts:10 · packages/task/src/event/task.queue.event.ts:10 — 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/task/src/event/sub-task.queue.event.ts:10
packages/task/src/event/task.queue.event.handler.ts:36 · packages/task/src/event/task.sfn.event.handler.ts:28 — the two spans are one implementation copied and then locally edited — 147 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/task/src/event/task.queue.event.handler.ts:36
packages/task/src/task.service.ts:185 · packages/task/src/task.service.ts:211 · packages/task/src/task.service.ts:232 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — packages/task/src/task.service.ts:185
packages/task/src/task.service.ts:211 · packages/task/src/task.service.ts:232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/task/src/task.service.ts:211
packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts:12 · packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-update.dto.ts:12 · packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-update.dto.ts:12 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts:12

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.

Do you agree with this assessment?

R2 · Cyclomatic Complexity9.8 / 10Exemplary✓ Tool-verified

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

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

explainCode has cyclomatic complexity 37 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/mcp-server/src/tools/analyze.ts:1190
healthCheck has cyclomatic complexity 21 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/mcp-server/src/tools/analyze.ts:1008
analyzeProject has cyclomatic complexity 20 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mcp-server/src/tools/analyze.ts:196
checkAntiPatterns has cyclomatic complexity 19 and cognitive complexity 30; 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/mcp-server/src/tools/analyze.ts:884
validateCqrsPatterns has cyclomatic complexity 19 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/mcp-server/src/tools/validate.ts:78
listItemsByPk has cyclomatic complexity 17 and cognitive complexity 27; 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/core/src/commands/repository.ts:141
installSkillsAction has cyclomatic complexity 17 and cognitive complexity 21; 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/cli/src/actions/install-skills.action.ts:257
publishSync has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/commands/command.service.ts:239
(anonymous) has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/commands/repository.ts:325
buildUpdateSetExpression has cyclomatic complexity 15 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. — packages/core/src/data-store/dynamodb.service.ts:309
listItems has cyclomatic complexity 15 and cognitive complexity 21; 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/core/src/commands/repository.ts:285
(top-level) has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/import/src/event/import-status.queue.event.handler.ts:1
sendInlineTemplateEmail has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/core/src/notifications/email.service.ts:115
process has cyclomatic complexity 12 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/import/src/event/processor/csv-batch.processor.ts:29
checkDuplicateDataSyncHandlerRegistrations has cyclomatic complexity 12 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/mcp-server/src/tools/analyze.ts:806
sendBatchToSqs has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/import/src/event/csv-import.sfn.event.handler.ts:134

What to do

Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.

Do you agree with this assessment?

R3 · Large Files9.1 / 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/cli/templates/infra/libs/infra-stack.ts has 1310 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/cli/templates/infra/libs/infra-stack.ts:1
packages/mcp-server/src/tools/analyze.ts has 1268 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/mcp-server/src/tools/analyze.ts:1
packages/directory/src/directory.service.ts has 758 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/directory/src/directory.service.ts:1
packages/core/src/integration/utilities/aws-error-factory.ts has 597 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/src/integration/utilities/aws-error-factory.ts:1
packages/core/src/commands/command.service.ts has 577 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/src/commands/command.service.ts:1
packages/import/src/import.service.ts has 574 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/import/src/import.service.ts:1
packages/master/src/services/master-setting.service.ts has 500 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/master/src/services/master-setting.service.ts:1
packages/core/src/commands/command.event.handler.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/core/src/commands/command.event.handler.ts:1
packages/import/src/event/csv-import.sfn.event.handler.ts has 441 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/import/src/event/csv-import.sfn.event.handler.ts:1
packages/core/src/integration/utilities/test-data-builders.ts has 429 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/src/integration/utilities/test-data-builders.ts:1
packages/mcp-server/src/prompts/cqrs-guide.ts has 421 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/mcp-server/src/prompts/cqrs-guide.ts:1
packages/core/src/data-store/dynamodb.service.ts has 412 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/src/data-store/dynamodb.service.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 Coverage8.2 / 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/master/src/update-scheme.ts:1, packages/cli/schematics/lib/module/module.factory.ts:1, packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts:1, …

What to do

Add tests that import the unreached modules (directly or through their public entry).

Do you agree with this assessment?

R5 · Dependency Freshness2.7 / 10Weak✓ Tool-verified

React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).

Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.

73 outdated package(s); JS/npm CVEs scored in D30

What to do

Bump outdated dependencies to current versions to limit upgrade debt.

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 package.json 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: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

Do you agree with this assessment?

R7 · Dead Code8.1 / 10Strong✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

1 file(s) (~54 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.
Unreachable from the 36 application, 15 tooling and 196 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×34) — packages/cli/schematics/lib/module/module.factory.ts, packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts, packages/cli/schematics/lib/module/files/sync/__name@dasherize__.service.ts, …
no import path from any entry point (36 application, 15 tooling, 196 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/master/src/templates/master/helpers/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 (×2) — packages/master/src/templates/master/helpers/id.ts, packages/master/src/templates/master/helpers/get-order.ts
no import path from any entry point (36 application, 15 tooling, 196 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/cli/schematics/utils/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 — packages/cli/schematics/utils/check-files-exist.ts
no import path from any entry point (36 application, 15 tooling, 196 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/master/src/templates/master/entity/master-data-list.entity.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 — packages/master/src/templates/master/entity/master-data.entity.ts

What to do

Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.

Do you agree with this assessment?

R8 · Dependency Hygiene0.0 / 10Critical✓ Tool-verified

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

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

Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×25) — packages/cli/schematics/lib/controller/files/__name@dasherize__.controller.ts:1, packages/cli/schematics/lib/controller/files/__name@dasherize__.controller.ts:2, packages/core/src/integration/aws-credential-provider-behavior.spec.ts:12, …
Declared in packages/cli/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
Declared in packages/cli/templates/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×2)
Only test files import it (first: packages/core/src/integration/nestjs-mapped-types-behavior.spec.ts:23) — move it to devDependencies. — packages/core/package.json:59

What to do

Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.

Do you agree with this assessment?

R9 · Circular Imports0.4 / 10Critical✓ Tool-verified

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

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

packages/core/src/interfaces/index.ts → packages/core/src/interfaces/command-service.interface.ts → packages/core/src/interfaces/index.ts (one verified cycle inside a mutually-dependent group of 35 files) — packages/core/src/interfaces/index.ts:9
packages/import/src/event/command-finished.queue.event.handler.ts → packages/import/src/import.service.ts → packages/import/src/event/index.ts → packages/import/src/event/command-finished.queue.event.handler.ts (one verified cycle inside a mutually-dependent group of 10 files) — packages/import/src/event/command-finished.queue.event.handler.ts:14
packages/task/src/event/index.ts → packages/task/src/event/sub-task.queue.event.handler.ts → packages/task/src/task.service.ts → packages/task/src/event/index.ts (one verified cycle inside a mutually-dependent group of 6 files) — packages/task/src/event/index.ts:2

What to do

Break each cycle by extracting the shared piece into a module both sides can import.

Do you agree with this assessment?

S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. 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.

`app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — packages/core/src/bootstrap.ts:102

What to do

Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.

Do you agree with this assessment?

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

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.

Do you agree with this assessment?

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

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

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

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.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document3.5 / 10Weak✓ Tool-verified

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

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

`mergeDeep` is exported and takes `target: any` from its caller, and it calls itself at line 14 (`mergeDeep`) with a piece of `target` — and nowhere in `mergeDeep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mergeDeep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/core/src/helpers/object.ts:14

What to do

Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.

Do you agree with this assessment?

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Only 0/2 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.
`sendMessage` 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/src/notifications/appsync.service.ts:52
`postToChannel` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`. — REDACTED:115

What to do

Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.

Do you agree with this assessment?

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

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.

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation7.5 / 10Strong✓ Tool-verified

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.

`debug` at line 17 is called with an argument built by `JSON.stringify(ctx, null, 2)` (line 17), 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. — REDACTED:17
`debug` at line 57 is called with an argument built by `join(', ')` (line 58), 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/core/src/notifications/event/notification.event.handler.ts:57
`debug` at line 534 is called with an argument built by `JSON.stringify(masterCopyDto)` (line 534), 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/master/src/services/master-setting.service.ts:534

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.

Do you agree with this assessment?

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

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

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

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.

Do you agree with this assessment?

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

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

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

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×6) — packages/cli/src/actions/install-skills.action.ts:74, packages/cli/src/actions/install-skills.action.ts:205, packages/master/src/update-scheme.ts:33, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. (×4) — packages/core/src/commands/repository.ts:104, packages/core/src/commands/repository.ts:203, packages/core/src/commands/repository.ts:356, …
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — packages/core/src/commands/command.service.ts:425

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.

Do you agree with this assessment?

X5 · Nullable reference types2.9 / 10Weak✓ Tool-verified

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

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

2/18 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.3 `!` null assertions per 1k TypeScript source lines — 10 assertion(s) across the 31741 source line(s) of the 511 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: REDACTED (5), packages/mcp-server/src/tools/analyze.ts (2), packages/cli/src/runners/abstract.runner.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).

Do you agree with this assessment?

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	55%	Adequate — gated by X5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	68%	Adequate — gated by R9	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	50%	Weak — gated by M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	29%	Weak — gated by D13, R5, R8, P5, P7	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	67%	Adequate — gated by D28, D29, D30, D36	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	60%	Adequate	Strongest area.

Unscored — 2 check(s) recorded observations but carry no score

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

X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.

Not included — 54 check(s) not relevant to this codebase

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

AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: NestJS makes a provider that injects a request-scoped one request-scoped itself (scope bubbles up the injection chain), and gives every consumer its own transient instance by contract.
AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server did not expose a crawlable HTTP endpoint in time — no runtime evidence This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
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.
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 (.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) — 34 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
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 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
P8 Schema migrations — Prisma is declared, but the schema-migration mechanism could not be identified. Our limit, not a verdict on this repository.
P9 Domain vs controller coverage — coverage data present for 14 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
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.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 141 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×39

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
+ 14 more in this group — see findings.md.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×17

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D28 · Secrets (history) · REDACTED · ×11

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D31 · IaC & Container Security · High IaC · ×7

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×5

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

R8 · Dependency Hygiene · Unlisted import '@nestjs/common' · ×5

Unlisted import '@nestjs/common' packages/cli/schematics/lib/controller/files/__name@dasherize__.controller.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nestjs/common' packages/directory/src/directory-file.service.ts:9 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nestjs/common' packages/import/src/event/command-finished.queue.event.handler.ts:9 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nestjs/common' packages/master/src/controllers/master-bulk.controller.spec.ts:2 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nestjs/common' packages/sequence/src/sequence-master-factory.ts:7 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@nestjs/swagger' · ×4

Unlisted import '@nestjs/swagger' packages/cli/schematics/lib/controller/files/__name@dasherize__.controller.ts:2 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nestjs/swagger' packages/directory/src/directory.controller.ts:15 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nestjs/swagger' packages/import/src/import.controller.ts:12 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nestjs/swagger' packages/master/src/controllers/master-bulk.controller.ts:7 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED
REDACTED

R8 · Dependency Hygiene · Unlisted import '@nestjs/config' · ×3

Unlisted import '@nestjs/config' packages/directory/src/directory.module.spec.ts:3 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nestjs/config' packages/import/src/event/csv-import.queue.event.handler.spec.ts:3 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import '@nestjs/config' packages/master/src/master.module.spec.ts:4 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'class-validator' · ×3

Unlisted import 'class-validator' packages/directory/src/dto/directory-attributes.dto.ts:3 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'class-validator' packages/import/src/dto/create-csv-import.dto.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'class-validator' packages/master/src/decorators/key.ts:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

D13 · REDACTED Scanning · Leaked secret · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

R8 · Dependency Hygiene · Unlisted import 'class-transformer' · ×2

Unlisted import 'class-transformer' packages/directory/src/dto/directory-attributes.dto.ts:2 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
Unlisted import 'class-transformer' packages/master/src/decorators/key.ts:7 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R9 · Circular Imports · Import cycle (3 files) · ×2

Import cycle (3 files) packages/import/src/event/command-finished.queue.event.handler.ts:14 — packages/import/src/event/command-finished.queue.event.handler.ts → packages/import/src/import.service.ts → packages/import/src/event/index.ts → packages/import/src/event/command-finished.queue.event.handler.ts (one verified cycle inside a mutually-dependent group of 10 files)
Import cycle (3 files) packages/task/src/event/index.ts:2 — packages/task/src/event/index.ts → packages/task/src/event/sub-task.queue.event.handler.ts → packages/task/src/task.service.ts → packages/task/src/event/index.ts (one verified cycle inside a mutually-dependent group of 6 files)

D10 · Test Quality · Assertions commented out · ×1

Assertions commented out: should preserve design:type for properties packages/core/src/integration/reflect-metadata-behavior.spec.ts:381 — The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

R8 · Dependency Hygiene · Unlisted import '@aws-sdk/credential-provider-env' · ×1

Unlisted import '@aws-sdk/credential-provider-env' packages/core/src/integration/aws-credential-provider-behavior.spec.ts:12 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@smithy/protocol-http' · ×1

Unlisted import '@smithy/protocol-http' packages/core/src/integration/aws-signature-v4-behavior.spec.ts:13 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import '@smithy/signature-v4' · ×1

Unlisted import '@smithy/signature-v4' REDACTED:8 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'dotenv' · ×1

Unlisted import 'dotenv' packages/core/test/e2e/config.ts:1 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'express' · ×1

Unlisted import 'express' packages/core/src/bootstrap.ts:9 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'rxjs' · ×1

Unlisted import 'rxjs' packages/core/src/bootstrap.ts:10 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'ulid' · ×1

Unlisted import 'ulid' packages/import/src/import.service.ts:23 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R8 · Dependency Hygiene · Unlisted import 'lodash' · ×1

Unlisted import 'lodash' packages/master/src/handler/master-sfn-task.handler.ts:13 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.

R9 · Circular Imports · Import cycle (2 files) · ×1

Import cycle (2 files) packages/core/src/interfaces/index.ts:9 — packages/core/src/interfaces/index.ts → packages/core/src/interfaces/command-service.interface.ts → packages/core/src/interfaces/index.ts (one verified cycle inside a mutually-dependent group of 35 files)

Serious — 346 finding(s)

R4 · Test Coverage · No test reaches this file · ×40

No test reaches this file packages/master/src/update-scheme.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/module/module.factory.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/module/files/sync/__name@dasherize__.service.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/import/src/import.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/import/src/import.controller.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/mcp-server/test-mcp.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 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/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/module/files/sync/__name@dasherize__.controller.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/master/src/templates/master/handler/master-rds.handler.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/controller/controller.factory.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/module/files/async/handler/__name@dasherize__-rds.handler.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/module/files/sync/handler/__name@dasherize__-rds.handler.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/service/service.factory.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/cli/schematics/lib/dto/dto.factory.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/entity/entity.factory.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/sequence/src/sequence.module.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/master/src/templates/master/helpers/id.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-update.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-update.dto.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/tenant/src/update-scheme.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file packages/cli/schematics/lib/controller/units/__name@dasherize__.controller.__specFileSuffix__.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.
+ 15 more in this group — see findings.md.

PF3 · Async & latency hygiene · Sync-over-async blocking · ×37

Sync-over-async blocking packages/cli/src/actions/install-skills.action.ts:279 — `existsSync` in `installSkillsAction` 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/cli/src/actions/install-skills.action.ts:331 — `existsSync` in `installSkillsAction` 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/cli/src/actions/install-skills.action.ts:332 — `readdirSync` in `installSkillsAction` 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:58 — `mkdirSync` in `newAction` 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:65 — `copyFileSync` in `newAction` 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:66 — `unlinkSync` in `newAction` 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:69 — `copyFileSync` in `newAction` 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:70 — `unlinkSync` in `newAction` 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:78 — `copyFileSync` in `newAction` 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:83 — `execSync` in `newAction` 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:89 — `execSync` in `newAction` 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:90 — `execSync` in `newAction` 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/cli/src/actions/ui.action.ts:32 — `existsSync` in `uiAction` 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/cli/src/actions/ui.action.ts:39 — `readFileSync` in `uiAction` 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/cli/src/actions/ui.action.ts:71 — `writeFileSync` in `uiAction` 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/cli/src/actions/ui.action.ts:84 — `execSync` in `uiAction` 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/src/bootstrap.ts:83 — `fs.writeFileSync` in `callback to then` 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/test/scripts/start.ts:63 — `readFileSync` in `callback to retry` 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/test/scripts/start.ts:79 — `readFileSync` in `callback to retry` 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/mcp-server/src/resources/project.ts:106 — `fs.existsSync` in `getProjectStructure` 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/mcp-server/src/resources/project.ts:126 — `fs.existsSync` in `buildTree` 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/mcp-server/src/resources/project.ts:131 — `fs.readdirSync` in `buildTree` 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/mcp-server/src/tools/analyze.ts:219 — `fs.existsSync` in `analyzeProject` 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/mcp-server/src/tools/analyze.ts:245 — `fs.existsSync` in `analyzeProject` 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/mcp-server/src/tools/analyze.ts:341 — `fs.existsSync` in `lookupError` 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.
+ 12 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · Medium CVE · ×25

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

D29 · Static Analysis (SAST) · REDACTED · ×19

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

R7 · Dead Code · Dead file (~12 LoC) · ×10

Dead file (~12 LoC) packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-command.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~12 LoC) packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-data-list.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~12 LoC) packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-data.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~12 LoC) packages/cli/schematics/lib/module/files/async/entity/__name@dasherize__-command.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~12 LoC) packages/cli/schematics/lib/module/files/async/entity/__name@dasherize__-data-list.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~12 LoC) packages/cli/schematics/lib/module/files/async/entity/__name@dasherize__-data.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~12 LoC) packages/cli/schematics/lib/module/files/sync/entity/__name@dasherize__-command.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~12 LoC) packages/cli/schematics/lib/module/files/sync/entity/__name@dasherize__-data-list.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~12 LoC) packages/cli/schematics/lib/module/files/sync/entity/__name@dasherize__-data.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~12 LoC) packages/directory/src/entity/directory-command.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 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

X3 · Exception handling · Swallowed exception (empty catch) · ×10

Swallowed exception (empty catch) packages/cli/src/actions/install-skills.action.ts:74 — 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/cli/src/actions/install-skills.action.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/core/src/commands/repository.ts:104 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/core/src/commands/repository.ts:203 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/core/src/commands/repository.ts:356 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/core/src/commands/repository.ts:368 — `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
Swallowed exception (empty catch) packages/master/src/update-scheme.ts:33 — 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/master/src/update-scheme.ts:144 — 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/master/src/update-scheme.ts:329 — 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/tenant/src/update-scheme.ts:28 — 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.

D10 · Test Quality · No assertions · ×8

No assertions: lambda-api SendTaskSuccess is scoped to command-handler state machine packages/cli/templates/infra/test/infra.test.ts:110 — 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 classify ${name} as ${retriable ? 'retriable' : 'non-retriable'} packages/core/src/integration/utilities-demo.spec.ts:211 — 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 support marble testing packages/core/src/integration/rxjs-schedulers.spec.ts:358 — 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 test delays with virtual time packages/core/src/integration/rxjs-schedulers.spec.ts:367 — 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 test interval with take packages/core/src/integration/rxjs-schedulers.spec.ts:378 — This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure* — 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 test error scenarios packages/core/src/integration/rxjs-schedulers.spec.ts:387 — 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 test hot observables packages/core/src/integration/rxjs-schedulers.spec.ts:396 — 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 test subscription timing packages/core/src/integration/rxjs-schedulers.spec.ts:406 — 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.

IC1 · Incompleteness & stubs · Fake-async · ×8

Fake-async — async method never awaits packages/cli/src/actions/generate.action.ts:9 — `generateAction` 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/cli/src/actions/install-skills.action.ts:257 — `installSkillsAction` 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 REDACTED:18 — `newAction` 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/cli/src/actions/start.action.ts:2 — `startAction` 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/cli/src/actions/ui.action.ts:14 — `uiAction` 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/cli/src/commands/generate.command.ts:6 — `generateCommand` 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/master/src/update-scheme.ts:15 — `formatDynamo` 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/master/src/update-scheme.ts:56 — `formatEventFactory` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

D17 · Explicit Debt · TodoComment · ×6

TodoComment packages/cli/src/actions/start.action.ts:4 — // 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/core/src/command-events/data-sync.sfn.event.ts:69 — // TODO convert S3 attributes — 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/src/commands/tenant-normalization.spec.ts:197 — // - Old data was written with uppercase: pk = 'TODO#MY_TENANT' — 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/src/events/event.services.ts:45 — // TODO Implementing partial batch responses — 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/test/e2e/publish-async.e2e-spec.ts:218 — // 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/master/src/services/master-setting.service.ts:108 — // TODO: Implement RDS logic 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.

D31 · IaC & Container Security · Medium IaC · ×6

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

D8 · Code Coverage · Low coverage · ×5

Low coverage: packages/mcp-server/src/index.ts packages/mcp-server/src/index.ts:1 — 0.0% line coverage (0/12).
Low coverage: packages/mcp-server/src/server.ts packages/mcp-server/src/server.ts:1 — 0.0% line coverage (0/53).
Low coverage: packages/mcp-server/src/resources/documentation.ts packages/mcp-server/src/resources/documentation.ts:1 — 17.2% line coverage (5/29).
Low coverage: packages/mcp-server/src/tools/generate.ts packages/mcp-server/src/tools/generate.ts:1 — 43.8% line coverage (14/32).
Low coverage: packages/mcp-server/src/tools/generator.ts packages/mcp-server/src/tools/generator.ts:1 — 22.2% line coverage (16/72).

R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×5

Duplicated block (20 lines × 2 locations) packages/directory/src/directory.service.ts:234 — packages/directory/src/directory.service.ts:234 · packages/directory/src/directory.service.ts:755 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 2 locations) packages/import/src/import.service.ts:118 — packages/import/src/import.service.ts:118 · packages/import/src/import.service.ts:171 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (20 lines × 2 locations) packages/master/src/master.module.ts:94 — packages/master/src/master.module.ts:94 · packages/survey-template/src/survey-template.module.ts:70 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.
Duplicated block (20 lines × 2 locations) packages/task/src/event/sub-task.queue.event.ts:10 — packages/task/src/event/sub-task.queue.event.ts:10 · packages/task/src/event/task.queue.event.ts:10 — 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 (20 lines × 2 locations) packages/task/src/task.service.ts:211 — packages/task/src/task.service.ts:211 · packages/task/src/task.service.ts:232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.

D15 · Churn × Complexity Hotspots · Repeated repair · ×4

Repeated repair: packages/core/src/commands/command.event.handler.ts packages/core/src/commands/command.event.handler.ts:106 — packages/core/src/commands/command.event.handler.ts changed 11 times in last 90 days and 10 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 11 (its worst body is CommandEventHandler.waitConfirmToken at line 106), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): close predecessor-read gaps on both sides of the handshake”; “fix(core): guard remaining publishAlarm sites against SNS failure”; “fix(core): classify checkNextToken resume failures and alarm”; “fix(core): alarm on degraded waitConfirmToken self-resume failures”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 15:14:08 +09:00' --until='2026-09-24 15:14:08 +09:00' --full-history --no-merges -- packages/core/src/commands/command.event.handler.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/core/src/commands/command.service.ts packages/core/src/commands/command.service.ts:81 — packages/core/src/commands/command.service.ts changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is CommandService.onModuleInit at line 81), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): correct async PRISMA resolution + soften duplicate-alias guard to warn”; “fix(core): guard registerEventHandlerAlias misuse (orphan alias + dropped handlers)”; “fix(core): resolve data-sync handler PRISMA across module boundary + guard duplicate table alias”; “fix: command.service publishSync bugs and add AP028 anti-pattern detection”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 15:14:08 +09:00' --until='2026-09-24 15:14:08 +09:00' --full-history --no-merges -- packages/core/src/commands/command.service.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/core/src/commands/command-module.helper.ts packages/core/src/commands/command-module.helper.ts:98 — packages/core/src/commands/command-module.helper.ts changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 3 (its worst body is command-module.helper.buildPrismaProviderAsync.useFactory at line 98), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core)+docs: non-empty tableName guard, shared-table & constant-coupling notes”; “fix(core): reject Prisma class in async factory + guard CommandModule.registerAsync”; “fix(core): correct async PRISMA resolution + soften duplicate-alias guard to warn”; “fix(core): resolve data-sync handler PRISMA across module boundary + guard duplicate table alias”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 15:14:08 +09:00' --until='2026-09-24 15:14:08 +09:00' --full-history --no-merges -- packages/core/src/commands/command-module.helper.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: packages/core/src/commands/command.module.ts packages/core/src/commands/command.module.ts:38 — packages/core/src/commands/command.module.ts changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is CommandModule.register at line 38), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix(core): reject Prisma class in async factory + guard CommandModule.registerAsync”; “fix(core): guard registerEventHandlerAlias misuse (orphan alias + dropped handlers)”; “fix(core): resolve data-sync handler PRISMA across module boundary + guard duplicate table alias”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 15:14:08 +09:00' --until='2026-09-24 15:14:08 +09:00' --full-history --no-merges -- packages/core/src/commands/command.module.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

R7 · Dead Code · Dead file (~62 LoC) · ×4

Dead file (~62 LoC) packages/cli/schematics/lib/controller/controller.factory.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~62 LoC) packages/cli/schematics/lib/module/files/async/handler/__name@dasherize__-rds.handler.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~62 LoC) packages/cli/schematics/lib/module/files/sync/handler/__name@dasherize__-rds.handler.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~62 LoC) packages/cli/schematics/lib/service/service.factory.ts — no import path from any entry point (36 application, 15 tooling, 196 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

D3 · God Classes · FileTooLong · ×3

FileTooLong: libs/infra-stack.ts packages/cli/templates/infra/libs/infra-stack.ts — FileTooLong — 922 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: InfraStack (29-1401). The bar is 500 significant lines; this is 422 over it, 1.84× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: tools/analyze.ts packages/mcp-server/src/tools/analyze.ts — FileTooLong — 875 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 375 over it, 1.75× 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/directory.service.ts packages/directory/src/directory.service.ts — FileTooLong — 617 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: DirectoryService (58-897). The bar is 500 significant lines; this is 117 over it, 1.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.

P7 · Outbound HTTP resilience · Outbound HTTP without resilience · ×3

Outbound HTTP without resilience REDACTED:121 — `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 packages/core/src/notifications/appsync.service.ts:72 — `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 packages/core/src/notifications/appsync.service.ts:91 — `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 (23 lines × 2 locations) · ×3

Duplicated block (23 lines × 2 locations) packages/directory/src/directory.module.ts:47 — packages/directory/src/directory.module.ts:47 · packages/survey-template/src/survey-template.module.ts:53 — 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 (23 lines × 2 locations) packages/directory/src/directory.service.ts:786 — packages/directory/src/directory.service.ts:786 · packages/directory/src/directory.service.ts:829 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2 locations) packages/master/src/helpers/index.ts:14 — packages/master/src/helpers/index.ts:14 · packages/ui-setting/src/helpers/index.ts:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R7 · Dead Code · Dead file (~34 LoC) · ×3

Dead file (~34 LoC) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~34 LoC) packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-update.dto.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~34 LoC) packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-update.dto.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~19 LoC) · ×3

Dead file (~19 LoC) packages/cli/schematics/lib/module/files/async/__name@dasherize__.module.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~19 LoC) packages/cli/schematics/lib/module/files/sync/__name@dasherize__.module.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~19 LoC) packages/master/src/templates/master/helpers/get-order.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/master/src/templates/master/helpers/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

R7 · Dead Code · Dead file (~18 LoC) · ×3

Dead file (~18 LoC) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-create.dto.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~18 LoC) packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-create.dto.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~18 LoC) packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-create.dto.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~16 LoC) · ×3

Dead file (~16 LoC) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-command.dto.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~16 LoC) packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-command.dto.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~16 LoC) packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-command.dto.ts — no import path from any entry point (36 application, 15 tooling, 196 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

D12 · Dependency Hygiene · Deprecated · ×2

Deprecated: @aws-sdk/signature-v4 package.json:53 — @aws-sdk/signature-v4 3.374.0, declared in package.json, is marked deprecated by its publisher: "This package has moved to @smithy/signature-v4". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint package.json:71 — eslint 8.57.1, declared in package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.

D23 · Boundary Type-Coupling · Cross-context type RotateByEnum (sequence → master) · ×2

Cross-context type RotateByEnum (sequence → master) packages/master/src/helpers/index.ts:53 — RotateByEnum (context sequence) is exposed in master's public surface via index.genSequenceSk — couples the contexts.
Cross-context type RotateByEnum (sequence → master) packages/master/src/templates/master/helpers/id.ts:6 — RotateByEnum (context sequence) is exposed in master's public surface via id.genSequenceSk — couples the contexts.

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D3 · God Classes · ClassTooLong · ×2

ClassTooLong: InfraStack packages/cli/templates/infra/libs/infra-stack.ts:29 — ClassTooLong — 898 significant lines (blank, comment-only and punctuation-only lines excluded), 1 methods. The bar is 400 significant lines; this is 498 over it, 2.25× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DirectoryService packages/directory/src/directory.service.ts:57 — ClassTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 162 over it, 1.41× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

R10 · Code Duplication · Duplicated block (43 lines × 2 locations) · ×2

Duplicated block (43 lines × 2 locations) packages/cli/schematics/lib/controller/controller.factory.ts:16 — packages/cli/schematics/lib/controller/controller.factory.ts:16 · packages/cli/schematics/lib/service/service.factory.ts:16 — 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 (43 lines × 2 locations) packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:26 — packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:26 · packages/cli/schematics/lib/module/files/sync/__name@dasherize__.controller.ts:26 — 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 (41 lines × 2 locations) · ×2

Duplicated block (41 lines × 2 locations) packages/core/src/interfaces/command.entity.ts:13 — packages/core/src/interfaces/command.entity.ts:13 · packages/core/src/interfaces/data.entity.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 (41 lines × 2 locations) packages/import/src/event/import.event.ts:14 — packages/import/src/event/import.event.ts:14 · packages/task/src/event/task.event.ts:14 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×2

Duplicated block (29 lines × 2 locations) packages/master/src/services/master-setting.service.ts:231 — packages/master/src/services/master-setting.service.ts:231 · packages/master/src/services/master-setting.service.ts:260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (29 lines × 2 locations) packages/ui-setting/src/controllers/data-setting.controller.ts:43 — packages/ui-setting/src/controllers/data-setting.controller.ts:43 · packages/ui-setting/src/controllers/setting.controller.ts:43 — 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 (21 lines × 2 locations) · ×2

Duplicated block (21 lines × 2 locations) packages/master/src/master.module.ts:64 — packages/master/src/master.module.ts:64 · packages/master/src/master.module.ts:112 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (21 lines × 2 locations) packages/ui-setting/src/setting.module.ts:26 — packages/ui-setting/src/setting.module.ts:26 · packages/ui-setting/src/setting.module.ts:65 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R7 · Dead Code · Dead file (~164 LoC) · ×2

Dead file (~164 LoC) packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~164 LoC) packages/cli/schematics/lib/module/files/sync/__name@dasherize__.service.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~74 LoC) · ×2

Dead file (~74 LoC) packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts — no import path from any entry point (36 application, 15 tooling, 196 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 (~74 LoC) packages/cli/schematics/lib/module/files/sync/__name@dasherize__.controller.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~11 LoC) · ×2

Dead file (~11 LoC) packages/cli/schematics/utils/check-files-exist.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/cli/schematics/utils/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~11 LoC) packages/master/src/templates/master/entity/master-data.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/master/src/templates/master/entity/master-data-list.entity.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

X2 · Cancellation propagation · Async function without AbortSignal · ×2

Async function without AbortSignal: sendMessage packages/core/src/notifications/appsync.service.ts:52 — `sendMessage` 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: postToChannel REDACTED:115 — `postToChannel` 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 })`.

D1 · Cyclomatic Complexity · analyze.explainCode (cyclomatic 37) · ×1

analyze.explainCode (cyclomatic 37) packages/mcp-server/src/tools/analyze.ts:1190 — analyze.explainCode has cyclomatic complexity 37 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 4 of the 11 methods over the threshold — including the worst — and 37 of the 74 points over it (50%), 2.1× the next-largest file (packages/core/src/commands/repository.ts at 18). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · Repository.listItems (cyclomatic 30) · ×1

Repository.listItems (cyclomatic 30) packages/core/src/commands/repository.ts:285 — Repository.listItems has cyclomatic complexity 30 (threshold 15). Of this number, 15 points are the body's own statements and 15 belong to 2 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · CsvImportSfnEventHandler.handleStepState (cyclomatic 23) · ×1

CsvImportSfnEventHandler.handleStepState (cyclomatic 23) packages/import/src/event/csv-import.sfn.event.handler.ts:61 — CsvImportSfnEventHandler.handleStepState has cyclomatic complexity 23 (threshold 15). Most of this is not in the body itself: 11 of the 23 points are its own statements and the rest belongs to 2 function items inside it that branch (sendBatchToSqs, packChunkToEntry). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D1 · Cyclomatic Complexity · analyze.healthCheck (cyclomatic 21) · ×1

analyze.healthCheck (cyclomatic 21) packages/mcp-server/src/tools/analyze.ts:1008 — analyze.healthCheck 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. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 4 of the 11 methods over the threshold — including the worst — and 37 of the 74 points over it (50%), 2.1× the next-largest file (packages/core/src/commands/repository.ts at 18). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · analyze.analyzeProject (cyclomatic 20) · ×1

analyze.analyzeProject (cyclomatic 20) packages/mcp-server/src/tools/analyze.ts:196 — analyze.analyzeProject 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. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 4 of the 11 methods over the threshold — including the worst — and 37 of the 74 points over it (50%), 2.1× the next-largest file (packages/core/src/commands/repository.ts at 18). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · analyze.checkAntiPatterns (cyclomatic 19) · ×1

analyze.checkAntiPatterns (cyclomatic 19) packages/mcp-server/src/tools/analyze.ts:884 — analyze.checkAntiPatterns 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. This file is where this pass's cyclomatic complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 4 of the 11 methods over the threshold — including the worst — and 37 of the 74 points over it (50%), 2.1× the next-largest file (packages/core/src/commands/repository.ts at 18). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D1 · Cyclomatic Complexity · validate.validateCqrsPatterns (cyclomatic 19) · ×1

validate.validateCqrsPatterns (cyclomatic 19) packages/mcp-server/src/tools/validate.ts:78 — validate.validateCqrsPatterns has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · InfraStack.constructor (cyclomatic 18) · ×1

InfraStack.constructor (cyclomatic 18) packages/cli/templates/infra/libs/infra-stack.ts:39 — InfraStack.constructor has cyclomatic complexity 18 (threshold 15). Of this number, 14 points are the body's own statements and 4 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.

D1 · Cyclomatic Complexity · Repository.listItemsByPk (cyclomatic 18) · ×1

Repository.listItemsByPk (cyclomatic 18) packages/core/src/commands/repository.ts:141 — Repository.listItemsByPk has cyclomatic complexity 18 (threshold 15). Of this number, 16 points are the body's own statements and 2 belong to one function literal inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.

D1 · Cyclomatic Complexity · install-skills.action.installSkillsAction (cyclomatic 17) · ×1

install-skills.action.installSkillsAction (cyclomatic 17) packages/cli/src/actions/install-skills.action.ts:257 — install-skills.action.installSkillsAction has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.

D1 · Cyclomatic Complexity · EmailService.sendInlineTemplateEmail (cyclomatic 17) · ×1

EmailService.sendInlineTemplateEmail (cyclomatic 17) packages/core/src/notifications/email.service.ts:115 — EmailService.sendInlineTemplateEmail has cyclomatic complexity 17 (threshold 15). Of this number, 13 points are the body's own statements and 4 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D15 · Churn × Complexity Hotspots · Hotspot · ×1

Hotspot: packages/cli/templates/infra/libs/infra-stack.ts packages/cli/templates/infra/libs/infra-stack.ts:39 — packages/cli/templates/infra/libs/infra-stack.ts changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in InfraStack.constructor at line 39. 2 of those changes were fix/bug commits, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-06-26..2026-09-24, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-06-26 15:14:08 +09:00' --until='2026-09-24 15:14:08 +09:00' --full-history --no-merges -- packages/cli/templates/infra/libs/infra-stack.ts`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.

D2 · Cognitive Complexity · analyze.explainCode (cognitive 52) · ×1

analyze.explainCode (cognitive 52) packages/mcp-server/src/tools/analyze.ts:1190 — analyze.explainCode has cognitive complexity 52 (threshold 15). Drivers by points: if/else 29 (42 pts), boolean chains 6, loops 2 (4 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 6 of the 21 methods over the threshold — including the worst — and 115 of the 225 points over it (51%), 3.1× the next-largest file (packages/core/src/commands/repository.ts at 37). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · analyze.healthCheck (cognitive 45) · ×1

analyze.healthCheck (cognitive 45) packages/mcp-server/src/tools/analyze.ts:1008 — analyze.healthCheck has cognitive complexity 45 (threshold 15). Drivers by points: if/else 20 (31 pts), ternaries 5 (10 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 6 of the 21 methods over the threshold — including the worst — and 115 of the 225 points over it (51%), 3.1× the next-largest file (packages/core/src/commands/repository.ts at 37). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · Repository.listItems (cognitive 39) · ×1

Repository.listItems (cognitive 39) packages/core/src/commands/repository.ts:285 — Repository.listItems has cognitive complexity 39 (threshold 15). Drivers by points: if/else 18 (25 pts), boolean chains 7, ternaries 4 (6 pts), loops 1 (nesting depth added 9). Of this number, 21 points are the body's own statements and 18 belong to 2 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · analyze.analyzeProject (cognitive 38) · ×1

analyze.analyzeProject (cognitive 38) packages/mcp-server/src/tools/analyze.ts:196 — analyze.analyzeProject has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (18 pts), loops 5 (9 pts), ternaries 2 (7 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 6 of the 21 methods over the threshold — including the worst — and 115 of the 225 points over it (51%), 3.1× the next-largest file (packages/core/src/commands/repository.ts at 37). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · DynamoDbService.buildUpdateSetExpression (cognitive 33) · ×1

DynamoDbService.buildUpdateSetExpression (cognitive 33) packages/core/src/data-store/dynamodb.service.ts:309 — DynamoDbService.buildUpdateSetExpression has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (28 pts), boolean chains 4, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · analyze.checkAntiPatterns (cognitive 33) · ×1

analyze.checkAntiPatterns (cognitive 33) packages/mcp-server/src/tools/analyze.ts:884 — analyze.checkAntiPatterns has cognitive complexity 33 (threshold 15). Drivers by points: ternaries 5 (15 pts), if/else 6 (9 pts), loops 4 (7 pts), boolean chains 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. This file is where this pass's cognitive complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 6 of the 21 methods over the threshold — including the worst — and 115 of the 225 points over it (51%), 3.1× the next-largest file (packages/core/src/commands/repository.ts at 37). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · Repository.listItemsByPk (cognitive 28) · ×1

Repository.listItemsByPk (cognitive 28) packages/core/src/commands/repository.ts:141 — Repository.listItemsByPk has cognitive complexity 28 (threshold 15). Drivers by points: if/else 14 (21 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (nesting depth added 9). Of this number, 24 points are the body's own statements and 4 belong to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · validate.validateCqrsPatterns (cognitive 23) · ×1

validate.validateCqrsPatterns (cognitive 23) packages/mcp-server/src/tools/validate.ts:78 — validate.validateCqrsPatterns has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 5, loops 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CsvImportSfnEventHandler.getResultsFromS3Writer (cognitive 22) · ×1

CsvImportSfnEventHandler.getResultsFromS3Writer (cognitive 22) packages/import/src/event/csv-import.sfn.event.handler.ts:313 — CsvImportSfnEventHandler.getResultsFromS3Writer has cognitive complexity 22 (threshold 15). Drivers by points: error handling 2 (6 pts), if/else 3 (6 pts), boolean chains 5, ternaries 1 (4 pts), loops 1 (nesting depth added 10). Most of this is not in the body itself: 3 of the 22 points are its own statements and the rest belongs to one function literal inside it that branches (line 348). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.

D2 · Cognitive Complexity · CsvBatchProcessor.process (cognitive 22) · ×1

CsvBatchProcessor.process (cognitive 22) packages/import/src/event/processor/csv-batch.processor.ts:29 — CsvBatchProcessor.process has cognitive complexity 22 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 5 (7 pts), error handling 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · install-skills.action.installSkillsAction (cognitive 21) · ×1

install-skills.action.installSkillsAction (cognitive 21) packages/cli/src/actions/install-skills.action.ts:257 — install-skills.action.installSkillsAction has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 3, error handling 1, ternaries 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.

D2 · Cognitive Complexity · InfraStack.constructor (cognitive 21) · ×1

InfraStack.constructor (cognitive 21) packages/cli/templates/infra/libs/infra-stack.ts:39 — InfraStack.constructor has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 4 (5 pts), boolean chains 4, loops 1 (nesting depth added 2). Of this number, 17 points are the body's own statements and 4 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.

D2 · Cognitive Complexity · analyze.checkDuplicateDataSyncHandlerRegistrations (cognitive 21) · ×1

analyze.checkDuplicateDataSyncHandlerRegistrations (cognitive 21) packages/mcp-server/src/tools/analyze.ts:806 — analyze.checkDuplicateDataSyncHandlerRegistrations has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 5 (7 pts), boolean chains 2 (nesting depth added 9). Of this number, 20 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 6 of the 21 methods over the threshold — including the worst — and 115 of the 225 points over it (51%), 3.1× the next-largest file (packages/core/src/commands/repository.ts at 37). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D2 · Cognitive Complexity · validate.formatValidationResult (cognitive 21) · ×1

validate.formatValidationResult (cognitive 21) packages/mcp-server/src/tools/validate.ts:191 — validate.formatValidationResult has cognitive complexity 21 (threshold 15). Drivers by points: ternaries 5 (15 pts), loops 2 (4 pts), if/else 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · ui.action.getModifyPackage (cognitive 18) · ×1

ui.action.getModifyPackage (cognitive 18) packages/cli/src/actions/ui.action.ts:160 — ui.action.getModifyPackage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (14 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · CommandEventHandler.waitConfirmToken (cognitive 18) · ×1

CommandEventHandler.waitConfirmToken (cognitive 18) packages/core/src/commands/command.event.handler.ts:106 — CommandEventHandler.waitConfirmToken has cognitive complexity 18 (threshold 15). Drivers by points: ternaries 2 (6 pts), error handling 2 (5 pts), if/else 3 (5 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.

D2 · Cognitive Complexity · update-scheme.formatTemplate (cognitive 18) · ×1

update-scheme.formatTemplate (cognitive 18) packages/master/src/update-scheme.ts:181 — update-scheme.formatTemplate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 pts), loops 1 (nesting depth added 6). Most of this is not in the body itself: 7 of the 18 points are its own statements and the rest belongs to one function item inside it that branches (mergeDirectories). Those helpers are already separate functions, so extracting the branching again is not available. To reduce it, move them out of the body to the enclosing scope, where each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.

D2 · Cognitive Complexity · EmailService.sendInlineTemplateEmail (cognitive 17) · ×1

EmailService.sendInlineTemplateEmail (cognitive 17) packages/core/src/notifications/email.service.ts:115 — EmailService.sendInlineTemplateEmail has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 8, if/else 4 (5 pts), ternaries 2 (3 pts), error handling 1 (nesting depth added 2). Of this number, 11 points are the body's own statements and 6 belong to 3 function items inside it that branch. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.

D2 · Cognitive Complexity · CsvImportSfnEventHandler.handleStepState · ×1

CsvImportSfnEventHandler.handleStepState::sendBatchToSqs (cognitive 17) packages/import/src/event/csv-import.sfn.event.handler.ts:134 — CsvImportSfnEventHandler.handleStepState::sendBatchToSqs has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (8 pts), loops 3 (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. This shape REPEATS in the file: one other method here (CsvImportSfnEventHandler.handleStepState) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · CsvImportSfnEventHandler.handleStepState (cognitive 17) · ×1

CsvImportSfnEventHandler.handleStepState (cognitive 17) packages/import/src/event/csv-import.sfn.event.handler.ts:61 — CsvImportSfnEventHandler.handleStepState has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 4 (6 pts), ternaries 2 (5 pts), boolean chains 4, error handling 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (CsvImportSfnEventHandler.handleStepState::sendBatchToSqs) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.

D2 · Cognitive Complexity · analyze.formatAnalysisResult (cognitive 16) · ×1

analyze.formatAnalysisResult (cognitive 16) packages/mcp-server/src/tools/analyze.ts:388 — analyze.formatAnalysisResult has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), loops 2 (4 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: packages/mcp-server/src/tools/analyze.ts holds 6 of the 21 methods over the threshold — including the worst — and 115 of the 225 points over it (51%), 3.1× the next-largest file (packages/core/src/commands/repository.ts at 37). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.

D22 · Internal API Consistency · Redundant naming and likely overlapping functionality. `toISOString` is a standard native method that produces ISO 8601 strings. The suffix `WithTimezone` implies a difference, but without seeing the implementation, it is unclear if this is a distinct operation or just a confusingly named wrapper. If they both produce ISO strings, the distinction is unclear. If one includes timezone offset and the other doesn't, the naming is non-standard (usually `toISOString` includes offset, while `toUTCString` or similar might not). · ×1

Redundant naming and likely overlapping functionality. `toISOString` is a standard native method that produces ISO 8601 strings. The suffix `WithTimezone` implies a difference, but without seeing the implementation, it is unclear if this is a distinct operation or just a confusingly named wrapper. If they both produce ISO strings, the distinction is unclear. If one includes timezone offset and the other doesn't, the naming is non-standard (usually `toISOString` includes offset, while `toUTCString` or similar might not). — Rename `toISOStringWithTimezone` to `toISOStringWithOffset` or `toISOStringLocal` to clearly distinguish the output format, or remove one if they are functionally identical. (signatures: datetime.toISOString(date: Date) | datetime.toISOStringWithTimezone(date: Date))

D22 · Internal API Consistency · Redundant validation methods mirroring the conversion methods above. If the conversion methods are redundant or confusingly named, the validation methods are too. It creates a parallel set of ambiguous checks. · ×1

Redundant validation methods mirroring the conversion methods above. If the conversion methods are redundant or confusingly named, the validation methods are too. It creates a parallel set of ambiguous checks. — Align with the recommendation for the conversion methods. If `toISOStringWithTimezone` is removed/renamed, do the same here. (signatures: datetime.isISOString(val: string) | datetime.isISOStringWithTimezone(val: string))

D22 · Internal API Consistency · Interface and Implementation duplication. While common in some patterns, `ICommandService` exposes `publishSync` and `publishAsync`, and `CommandService` implements them. However, `CommandService` also exposes `publishItem`, `duplicate`, `reSyncData`, `updateStatus`, `getItem`, `getLatestItem`, `updateTtl`, `updateTaskToken`, `getNextCommand`. The interface `ICommandService` is significantly smaller than the implementation `CommandService`. This suggests `ICommandService` is not a true contract for `CommandService`, or `CommandService` is doing too much (violating Single Responsibility). · ×1

Interface and Implementation duplication. While common in some patterns, `ICommandService` exposes `publishSync` and `publishAsync`, and `CommandService` implements them. However, `CommandService` also exposes `publishItem`, `duplicate`, `reSyncData`, `updateStatus`, `getItem`, `getLatestItem`, `updateTtl`, `updateTaskToken`, `getNextCommand`. The interface `ICommandService` is significantly smaller than the implementation `CommandService`. This suggests `ICommandService` is not a true contract for `CommandService`, or `CommandService` is doing too much (violating Single Responsibility). — Either expand `ICommandService` to include all public methods of `CommandService` to ensure the interface is a true contract, or split `CommandService` into smaller, focused services/interfaces (e.g., `ICommandPublisher`, `ICommandQueryService`). (signatures: ICommandService.publishSync(input: CommandInputModel, options: ICommandOptions): Promise<CommandModel | null> | CommandService.publishSync(input: CommandInputModel, options: ICommandOptions): Promise<CommandModel | null>)

D22 · Internal API Consistency · Confusingly similar operations with different signatures and likely different intents. `DataService.publish` takes a `CommandModel`. `CommandService.publishItem` takes a `DetailKey`. `CommandService.publishSync` takes a `CommandInputModel`. It is unclear why there are three different 'publish' entry points with different input types. `publishItem` returning `any` is also inconsistent with the typed returns of `publishSync`. · ×1

Confusingly similar operations with different signatures and likely different intents. `DataService.publish` takes a `CommandModel`. `CommandService.publishItem` takes a `DetailKey`. `CommandService.publishSync` takes a `CommandInputModel`. It is unclear why there are three different 'publish' entry points with different input types. `publishItem` returning `any` is also inconsistent with the typed returns of `publishSync`. — Clarify the domain boundaries. If `DataService` is for low-level storage, it shouldn't necessarily have a 'publish' method for commands. If `CommandService` is the facade, it should be the only entry point for publishing commands. Unify the input types or rename methods to reflect their specific scope (e.g., `CommandService.publishCommand`, `DataService.storeCommand`). (signatures: DataService.publish(cmd: CommandModel) | CommandService.publishItem(key: DetailKey): Promise<any | null> | CommandService.publishSync(input: CommandInputModel, options: ICommandOptions): Promise<CommandModel | null>)

D29 · Static Analysis (SAST) · REDACTED · ×1

REDACTED

D3 · God Classes · MethodTooLong · ×1

MethodTooLong: InfraStack.constructor packages/cli/templates/infra/libs/infra-stack.ts:39 — MethodTooLong — constructor runs 889 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 789 over it, 8.89× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

D35 · Change Coupling · Change coupling · ×1

Change coupling: master-data.service.ts ↔ master-setting.service.ts packages/master/src/services/master-data.service.ts:1 — `packages/master/src/services/master-data.service.ts` and `packages/master/src/services/master-setting.service.ts` change together 67% of the time (10 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `74a175e7` fix(master): address review issues - DTO mutation, ordering, seq race…; `5eda4474` fix(master): throw error instead of returning empty object, add Maste…; `976e4e14` fix(master): address PR review issues - tenant validation, seq=0 bug,… — run `git show` on any of them.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing REDACTED · ×1

REDACTED

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: @mbc-cqrs-serverless/core — @mbc-cqrs-serverless/core: abstractness 0.09, instability 0.00, distance 0.91 — zone of pain — concrete and depended on by 8 project(s), so it's rigid to change.

D6 · Cohesion (LCOM4) · Low cohesion · ×1

Low cohesion: DynamoDbService (LCOM4 5) packages/core/src/data-store/dynamodb.service.ts:36 — DynamoDbService's methods fall into 5 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 5 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.

GD1 · Unfinished & placeholder code · Unfinished stub · ×1

Unfinished stub — throws a "not implemented" error packages/core/src/commands/command.service.ts:77 — 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.

IC1 · Incompleteness & stubs · Unfinished stub · ×1

Unfinished stub — throws a "not implemented" exception packages/core/src/commands/command.service.ts:77 — `publishItem` throws an exception whose message says it isn't finished — a not-implemented stub wearing an ordinary exception. Implement it or remove it.

M1 · Documentation (README) · README may be stale · ×1

README may be stale — 62 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.

P5 · DR & Backup · No DR/backup evidence · ×1

No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.

R10 · Code Duplication · Forked directory tree (11 identical files, ~267 lines × 2 trees) · ×1

Forked directory tree (11 identical files, ~267 lines × 2 trees) packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:1 — packages/cli/schematics/lib/module/files/async/ and packages/cli/schematics/lib/module/files/sync/ are near-verbatim copies of each other: 11 files are byte-identical under the same relative paths (~267 lines; the trees hold 12 and 12 files). That is one structural fact, not 11 local ones: every edit made to one tree and not the other drifts silently, which is the failure whole-tree forks guarantee. Pick one tree as the single source and produce the other from it (generated, copied at build or release time, or re-exported) — or, if the copy is a stale snapshot nothing produces any more, delete it. Check first whether the copy is a deliberately published deliverable (a template consumers copy verbatim, a released sample frozen at a version); where it is, keep it produced from the source tree rather than edited in place.

R10 · Code Duplication · Duplication concentrated across 10 sibling directories (53 clone groups) · ×1

Duplication concentrated across 10 sibling directories (53 clone groups) packages/master/src/services/master-data.service.ts:186 — 53 duplicated blocks under packages/ have copies in at least two of the sibling directories cli, core, directory, import, master, sequence (+4 more sibling(s) not listed) — 30 of them are reported below, and 23 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 53 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 53 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 53 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 5 sibling directories (10 clone groups) · ×1

Duplication concentrated across 5 sibling directories (10 clone groups) packages/cli/schematics/lib/controller/controller.factory.ts:16 — 10 of the duplicated blocks reported below have copies in at least two of the sibling directories controller, dto, entity, module, service under packages/cli/schematics/lib/. That concentration is one structural fact, not 10 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 10 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplicated block with local edits (105 matched lines × 2 locations) · ×1

Duplicated block with local edits (105 matched lines × 2 locations) packages/ui-setting/src/services/data-setting.service.ts:35 — packages/ui-setting/src/services/data-setting.service.ts:35 · packages/ui-setting/src/services/setting.service.ts:32 — the two spans are one implementation copied and then locally edited — 541 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Wholesale file copy (100 identical lines × 2 files) · ×1

Wholesale file copy (100 identical lines × 2 files) packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts:11 — packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts:11 · packages/cli/schematics/lib/module/files/sync/__name@dasherize__.service.ts:11 — these 2 files are line-for-line copies of one another — 100 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.

R10 · Code Duplication · Duplicated block with local edits (71 matched lines × 2 locations) · ×1

Duplicated block with local edits (71 matched lines × 2 locations) packages/master/src/services/master-data.service.ts:186 — packages/master/src/services/master-data.service.ts:186 · packages/ui-setting/src/services/data-setting.service.ts:79 — the two spans are one implementation copied and then locally edited — 400 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 (65 matched lines × 2 locations) · ×1

Duplicated block with local edits (65 matched lines × 2 locations) packages/master/src/controllers/master-data.controller.ts:61 — packages/master/src/controllers/master-data.controller.ts:61 · packages/master/src/controllers/master-setting.controller.ts:96 — the two spans are one implementation copied and then locally edited — 378 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 (63 lines × 2 locations) · ×1

Duplicated block (63 lines × 2 locations) packages/sequence/src/sequences.service.ts:80 — packages/sequence/src/sequences.service.ts:80 · packages/sequence/src/sequences.service.ts:165 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (57 matched lines × 2 locations) · ×1

Duplicated block with local edits (57 matched lines × 2 locations) packages/core/src/data-store/dynamodb.service.ts:155 — packages/core/src/data-store/dynamodb.service.ts:155 · packages/directory/src/dynamodb.service.ts:69 — the two spans are one implementation copied and then locally edited — 285 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block with local edits (43 matched lines × 2 locations) · ×1

Duplicated block with local edits (43 matched lines × 2 locations) packages/core/src/commands/repository.ts:171 — packages/core/src/commands/repository.ts:171 · packages/core/src/commands/repository.ts:303 — the two spans are one implementation copied and then locally edited — 295 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.

R10 · Code Duplication · Duplicated block (42 lines × 2 locations) · ×1

Duplicated block (42 lines × 2 locations) packages/cli/schematics/lib/module/files/async/handler/__name@dasherize__-rds.handler.ts:17 — packages/cli/schematics/lib/module/files/async/handler/__name@dasherize__-rds.handler.ts:17 · packages/cli/schematics/lib/module/files/sync/handler/__name@dasherize__-rds.handler.ts:17 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R10 · Code Duplication · Duplicated block with local edits (40 matched lines × 2 locations) · ×1

Duplicated block with local edits (40 matched lines × 2 locations) packages/master/src/services/master-data.service.ts:299 — packages/master/src/services/master-data.service.ts:299 · packages/master/src/services/master-setting.service.ts:332 — the two spans are one implementation copied and then locally edited — 210 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 (38 lines × 2 locations) · ×1

Duplicated block (38 lines × 2 locations) packages/task/src/task.service.ts:38 — packages/task/src/task.service.ts:38 · packages/task/src/task.service.ts:77 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R10 · Code Duplication · Duplicated block (33 lines × 2 locations) · ×1

Duplicated block (33 lines × 2 locations) packages/master/src/dto/master-setting/group-setting-create.dto.ts:4 — packages/master/src/dto/master-setting/group-setting-create.dto.ts:4 · packages/master/src/dto/master-setting/user-setting-create.dto.ts:4 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.

R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×1

Duplicated block (32 lines × 2 locations) packages/directory/src/directory.service.ts:604 — packages/directory/src/directory.service.ts:604 · packages/directory/src/directory.service.ts:669 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (29 lines × 3 locations) · ×1

Duplicated block (29 lines × 3 locations) packages/master/src/dto/master-setting/group-setting-create.dto.ts:2 — packages/master/src/dto/master-setting/group-setting-create.dto.ts:2 · packages/master/src/dto/master-setting/tenant-setting-create.dto.ts:2 · packages/master/src/dto/master-setting/user-setting-create.dto.ts:2 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.

R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1

Duplicated block (27 lines × 2 locations) packages/directory/src/directory.service.ts:401 — packages/directory/src/directory.service.ts:401 · packages/directory/src/directory.service.ts:435 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block (26 lines × 2 locations) · ×1

Duplicated block (26 lines × 2 locations) packages/cli/schematics/lib/dto/dto.factory.ts:17 — packages/cli/schematics/lib/dto/dto.factory.ts:17 · packages/cli/schematics/lib/entity/entity.factory.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 (25 lines × 2 locations) · ×1

Duplicated block (25 lines × 2 locations) packages/import/src/import.service.ts:609 — packages/import/src/import.service.ts:609 · packages/task/src/task.service.ts:289 — 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 (24 lines × 2 locations) · ×1

Duplicated block (24 lines × 2 locations) packages/core/src/commands/data.service.ts:17 — packages/core/src/commands/data.service.ts:17 · packages/core/src/commands/history.service.ts:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

R10 · Code Duplication · Duplicated block with local edits (21 matched lines × 2 locations) · ×1

Duplicated block with local edits (21 matched lines × 2 locations) packages/import/src/event/processor/csv-batch.processor.ts:62 — packages/import/src/event/processor/csv-batch.processor.ts:62 · packages/import/src/event/processor/single-import.processor.ts:153 — the two spans are one implementation copied and then locally edited — 77 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 (20 matched lines × 2 locations) · ×1

Duplicated block with local edits (20 matched lines × 2 locations) packages/task/src/event/task.queue.event.handler.ts:36 — packages/task/src/event/task.queue.event.handler.ts:36 · packages/task/src/event/task.sfn.event.handler.ts:28 — the two spans are one implementation copied and then locally edited — 147 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 (20 lines × 3 locations) · ×1

Duplicated block (20 lines × 3 locations) packages/task/src/task.service.ts:185 — packages/task/src/task.service.ts:185 · packages/task/src/task.service.ts:211 · packages/task/src/task.service.ts:232 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.

R10 · Code Duplication · Duplicated block (19 lines × 3 locations) · ×1

Duplicated block (19 lines × 3 locations) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts:12 — packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts:12 · packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-update.dto.ts:12 · packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-update.dto.ts:12 — the 3 copies are spread across 3 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

R2 · Cyclomatic Complexity · Complex function explainCode (cyclomatic 37, cognitive 52) · ×1

Complex function explainCode (cyclomatic 37, cognitive 52) packages/mcp-server/src/tools/analyze.ts:1190 — explainCode has cyclomatic complexity 37 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.

R2 · Cyclomatic Complexity · Complex function healthCheck (cyclomatic 21, cognitive 43) · ×1

Complex function healthCheck (cyclomatic 21, cognitive 43) packages/mcp-server/src/tools/analyze.ts:1008 — healthCheck has cyclomatic complexity 21 and cognitive complexity 43; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function analyzeProject (cyclomatic 20, cognitive 37) · ×1

Complex function analyzeProject (cyclomatic 20, cognitive 37) packages/mcp-server/src/tools/analyze.ts:196 — analyzeProject has cyclomatic complexity 20 and cognitive complexity 37; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function checkAntiPatterns (cyclomatic 19, cognitive 30) · ×1

Complex function checkAntiPatterns (cyclomatic 19, cognitive 30) packages/mcp-server/src/tools/analyze.ts:884 — checkAntiPatterns has cyclomatic complexity 19 and cognitive complexity 30; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function validateCqrsPatterns (cyclomatic 19, cognitive 23) · ×1

Complex function validateCqrsPatterns (cyclomatic 19, cognitive 23) packages/mcp-server/src/tools/validate.ts:78 — validateCqrsPatterns has cyclomatic complexity 19 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function listItemsByPk (cyclomatic 17, cognitive 27) · ×1

Complex function listItemsByPk (cyclomatic 17, cognitive 27) packages/core/src/commands/repository.ts:141 — listItemsByPk has cyclomatic complexity 17 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function installSkillsAction (cyclomatic 17, cognitive 21) · ×1

Complex function installSkillsAction (cyclomatic 17, cognitive 21) packages/cli/src/actions/install-skills.action.ts:257 — installSkillsAction has cyclomatic complexity 17 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function publishSync (cyclomatic 16, cognitive 18) · ×1

Complex function publishSync (cyclomatic 16, cognitive 18) packages/core/src/commands/command.service.ts:239 — publishSync has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 18) · ×1

Complex function (anonymous) (cyclomatic 16, cognitive 18) packages/core/src/commands/repository.ts:325 — (anonymous) has cyclomatic complexity 16 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function buildUpdateSetExpression (cyclomatic 15, cognitive 33) · ×1

Complex function buildUpdateSetExpression (cyclomatic 15, cognitive 33) packages/core/src/data-store/dynamodb.service.ts:309 — buildUpdateSetExpression has cyclomatic complexity 15 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.

R2 · Cyclomatic Complexity · Complex function listItems (cyclomatic 15, cognitive 21) · ×1

Complex function listItems (cyclomatic 15, cognitive 21) packages/core/src/commands/repository.ts:285 — listItems has cyclomatic complexity 15 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function (top-level) (cyclomatic 13, cognitive 15) · ×1

Complex function (top-level) (cyclomatic 13, cognitive 15) packages/import/src/event/import-status.queue.event.handler.ts:1 — (top-level) has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function sendInlineTemplateEmail (cyclomatic 13, cognitive 13) · ×1

Complex function sendInlineTemplateEmail (cyclomatic 13, cognitive 13) packages/core/src/notifications/email.service.ts:115 — sendInlineTemplateEmail has cyclomatic complexity 13 and cognitive complexity 13; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function process (cyclomatic 12, cognitive 23) · ×1

Complex function process (cyclomatic 12, cognitive 23) packages/import/src/event/processor/csv-batch.processor.ts:29 — process has cyclomatic complexity 12 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function checkDuplicateDataSyncHandlerRegistrations (cyclomatic 12, cognitive 20) · ×1

Complex function checkDuplicateDataSyncHandlerRegistrations (cyclomatic 12, cognitive 20) packages/mcp-server/src/tools/analyze.ts:806 — checkDuplicateDataSyncHandlerRegistrations has cyclomatic complexity 12 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.

R2 · Cyclomatic Complexity · Complex function sendBatchToSqs (cyclomatic 12, cognitive 17) · ×1

Complex function sendBatchToSqs (cyclomatic 12, cognitive 17) packages/import/src/event/csv-import.sfn.event.handler.ts:134 — sendBatchToSqs has cyclomatic complexity 12 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive 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/cli/templates/infra/libs/infra-stack.ts · ×1

packages/cli/templates/infra/libs/infra-stack.ts: 1310 lines of code packages/cli/templates/infra/libs/infra-stack.ts:1 — packages/cli/templates/infra/libs/infra-stack.ts has 1310 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/mcp-server/src/tools/analyze.ts · ×1

packages/mcp-server/src/tools/analyze.ts: 1268 lines of code packages/mcp-server/src/tools/analyze.ts:1 — packages/mcp-server/src/tools/analyze.ts has 1268 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/directory/src/directory.service.ts · ×1

packages/directory/src/directory.service.ts: 758 lines of code packages/directory/src/directory.service.ts:1 — packages/directory/src/directory.service.ts has 758 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/src/integration/utilities/aws-error-factory.ts · ×1

packages/core/src/integration/utilities/aws-error-factory.ts: 597 lines of code packages/core/src/integration/utilities/aws-error-factory.ts:1 — packages/core/src/integration/utilities/aws-error-factory.ts has 597 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/src/commands/command.service.ts · ×1

packages/core/src/commands/command.service.ts: 577 lines of code packages/core/src/commands/command.service.ts:1 — packages/core/src/commands/command.service.ts has 577 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/import/src/import.service.ts · ×1

packages/import/src/import.service.ts: 574 lines of code packages/import/src/import.service.ts:1 — packages/import/src/import.service.ts has 574 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/master/src/services/master-setting.service.ts · ×1

packages/master/src/services/master-setting.service.ts: 500 lines of code packages/master/src/services/master-setting.service.ts:1 — packages/master/src/services/master-setting.service.ts has 500 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/src/commands/command.event.handler.ts · ×1

packages/core/src/commands/command.event.handler.ts: 460 lines of code packages/core/src/commands/command.event.handler.ts:1 — packages/core/src/commands/command.event.handler.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/import/src/event/csv-import.sfn.event.handler.ts · ×1

packages/import/src/event/csv-import.sfn.event.handler.ts: 441 lines of code packages/import/src/event/csv-import.sfn.event.handler.ts:1 — packages/import/src/event/csv-import.sfn.event.handler.ts has 441 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/src/integration/utilities/test-data-builders.ts · ×1

packages/core/src/integration/utilities/test-data-builders.ts: 429 lines of code packages/core/src/integration/utilities/test-data-builders.ts:1 — packages/core/src/integration/utilities/test-data-builders.ts has 429 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/mcp-server/src/prompts/cqrs-guide.ts · ×1

packages/mcp-server/src/prompts/cqrs-guide.ts: 421 lines of code packages/mcp-server/src/prompts/cqrs-guide.ts:1 — packages/mcp-server/src/prompts/cqrs-guide.ts has 421 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/src/data-store/dynamodb.service.ts · ×1

packages/core/src/data-store/dynamodb.service.ts: 412 lines of code packages/core/src/data-store/dynamodb.service.ts:1 — packages/core/src/data-store/dynamodb.service.ts has 412 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R5 · Dependency Freshness · Dependency Freshness · ×1

Dependency Freshness — 73 outdated package(s); JS/npm CVEs scored in D30

R7 · Dead Code · Dead file (~238 LoC) · ×1

Dead file (~238 LoC) packages/cli/schematics/lib/module/module.factory.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~47 LoC) · ×1

Dead file (~47 LoC) packages/cli/schematics/lib/dto/dto.factory.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~45 LoC) · ×1

Dead file (~45 LoC) packages/cli/schematics/lib/entity/entity.factory.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~42 LoC) · ×1

Dead file (~42 LoC) packages/master/src/templates/master/helpers/id.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/master/src/templates/master/helpers/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

R7 · Dead Code · Dead file (~14 LoC) · ×1

Dead file (~14 LoC) packages/tenant/src/entities/setting-list.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R7 · Dead Code · Dead file (~13 LoC) · ×1

Dead file (~13 LoC) packages/master/src/templates/master/entity/master-data-list.entity.ts — no import path from any entry point (36 application, 15 tooling, 196 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

R8 · Dependency Hygiene · Unused dependency '@schematics/angular' · ×1

Unused dependency '@schematics/angular' — Declared in packages/cli/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency '@nestjs/testing' · ×1

Unused dependency '@nestjs/testing' — Declared in packages/cli/templates/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

R8 · Dependency Hygiene · Unused dependency 'nestjs-spelunker' · ×1

Unused dependency 'nestjs-spelunker' — Declared in packages/cli/templates/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.

X17 · Uncapped recursion over a caller-supplied document · Recursive walk over a caller-supplied document has no depth cap · ×1

Recursive walk over a caller-supplied document has no depth cap packages/core/src/helpers/object.ts:14 — `mergeDeep` is exported and takes `target: any` from its caller, and it calls itself at line 14 (`mergeDeep`) with a piece of `target` — and nowhere in `mergeDeep` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `mergeDeep` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack.

X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1

Swallowed exception (caught, then discarded) packages/core/src/commands/command.service.ts:425 — `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.

Minor — 188 finding(s)

D12 · Dependency Hygiene · Deprecated · ×101

Deprecated: @hapi/address REDACTED:3667 — @hapi/address 1.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". 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:4012 — @humanwhocodes/config-array 0.13.0 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/config-array instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @humanwhocodes/object-schema REDACTED:4063 — @humanwhocodes/object-schema 2.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use @eslint/object-schema instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:4878 — glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: @koa/router REDACTED:5090 — @koa/router 9.4.0 is resolved in REDACTED and is marked deprecated by its publisher: "**IMPORTANT 10x+ PERFORMANCE UPGRADE**: Please upgrade to v12.0.1+ as we have fixed an issue with debuglog causing 10x slower router benchmark performance, see https://github.com/koajs/router/pull/173". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:6782 — glob 11.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: accept REDACTED:10096 — accept 2.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/accept. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: boom REDACTED:10110 — boom 5.3.3 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: hoek REDACTED:10123 — hoek 4.3.1 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: ammo REDACTED:10355 — ammo 2.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/ammo. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: boom REDACTED:10369 — boom 5.3.3 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: hoek REDACTED:10382 — hoek 4.3.1 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: glob REDACTED:10586 — glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: querystring REDACTED:11049 — querystring 0.2.0 is resolved in REDACTED and is marked deprecated by its publisher: "The querystring API is considered Legacy. new code should use the URLSearchParams API instead.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: b64 REDACTED:11153 — b64 3.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/b64. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: boom REDACTED:11482 — boom 7.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: bourne REDACTED:11492 — bourne 1.3.3 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/bourne. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: call REDACTED:12001 — call 4.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/call. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: boom REDACTED:12059 — boom 5.3.3 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: hoek REDACTED:12072 — hoek 4.3.1 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: catbox REDACTED:12139 — catbox 7.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/catbox. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: catbox-memory REDACTED:12154 — catbox-memory 2.1.1 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/catbox-memory. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: hoek REDACTED:12167 — hoek 4.3.1 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: boom REDACTED:12177 — boom 5.3.3 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/boom. Please update your dependencies as this version is no longer maintained and may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: hoek REDACTED:12190 — hoek 4.3.1 is resolved in REDACTED and is marked deprecated by its publisher: "This module has moved and is now available at @hapi/hoek. Please update your dependencies as this version is no longer maintained an may contain bugs and security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
+ 76 more in this group — see findings.md.

P2 · Observability · Console output used as the logging channel · ×17

Console output used as the logging channel packages/core/src/bootstrap.ts:93 — `packages/core/src/bootstrap.ts` reports through `console.*` at line 93 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/src/bootstrap.ts:98 — `packages/core/src/bootstrap.ts` reports through `console.*` at line 98 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/src/services/request-logger.service.ts:30 — `packages/core/src/services/request-logger.service.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/mcp-server/src/server.ts:64 — `packages/mcp-server/src/server.ts` reports through `console.*` at line 64 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel packages/mcp-server/src/server.ts:76 — `packages/mcp-server/src/server.ts` reports through `console.*` at line 76 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/mcp-server/src/server.ts:90 — `packages/mcp-server/src/server.ts` reports through `console.*` at line 90 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/mcp-server/src/server.ts:106 — `packages/mcp-server/src/server.ts` reports through `console.*` at line 106 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/mcp-server/src/server.ts:122 — `packages/mcp-server/src/server.ts` reports through `console.*` at line 122 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/mcp-server/src/server.ts:137 — `packages/mcp-server/src/server.ts` reports through `console.*` at line 137 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/mcp-server/src/server.ts:152 — `packages/mcp-server/src/server.ts` reports through `console.*` at line 152 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/mcp-server/src/server.ts:164 — `packages/mcp-server/src/server.ts` reports through `console.*` at line 164 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/mcp-server/src/prompts/cqrs-guide.ts:397 — `packages/mcp-server/src/prompts/cqrs-guide.ts` reports through `console.*` at line 397 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/mcp-server/src/prompts/cqrs-guide.ts:403 — `packages/mcp-server/src/prompts/cqrs-guide.ts` reports through `console.*` at line 403 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/mcp-server/src/prompts/cqrs-guide.ts:409 — `packages/mcp-server/src/prompts/cqrs-guide.ts` reports through `console.*` at line 409 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/mcp-server/src/prompts/cqrs-guide.ts:411 — `packages/mcp-server/src/prompts/cqrs-guide.ts` reports through `console.*` at line 411 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/task/src/event/sub-task.queue.event.handler.ts:27 — `packages/task/src/event/sub-task.queue.event.handler.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/task/src/event/sub-task.queue.event.handler.ts:31 — `packages/task/src/event/sub-task.queue.event.handler.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.

D12 · Dependency Hygiene · Outdated (npm) · ×9

Outdated (npm): @angular-devkit/core package.json:157 — @angular-devkit/core is pinned at 17.3.11; 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): @angular-devkit/schematics packages/cli/package.json:48 — @angular-devkit/schematics is pinned at 17.3.11; 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): @angular-devkit/schematics-cli packages/cli/package.json:49 — @angular-devkit/schematics-cli is pinned at 17.3.17; 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): @nestjs/config packages/core/package.json:57 — @nestjs/config is pinned at 4.0.4; registry.npmjs.org publishes 12.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): @nestjs/mapped-types packages/core/package.json:59 — @nestjs/mapped-types is pinned at 2.1.0; registry.npmjs.org publishes 12.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): @nestjs/swagger packages/cli/templates/package.json:54 — @nestjs/swagger is pinned at 7.4.2; registry.npmjs.org publishes 12.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): @schematics/angular packages/cli/package.json:50 — @schematics/angular is pinned at 17.3.17; 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): commander packages/cli/package.json:53 — commander is pinned at 11.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): prisma packages/cli/templates/package.json:45 — prisma is pinned at 5.20.0; registry.npmjs.org publishes 8.0.0-rc.25 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.

D10 · Test Quality · Mock-dominated test · ×8

Mock-dominated test: should resume next command when getNextCommand finds a taskToken packages/core/src/commands/command.event.handler.spec.ts:1013 — 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: should retry getNextCommand and resume when a later attempt succeeds packages/core/src/commands/command.event.handler.spec.ts:1140 — This test sets up 3 test doubles (for example `a double assigned in a shared setup`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not resume when predecessor is finish:FAILED packages/core/src/commands/command.event.handler.spec.ts:1283 — This test sets up 4 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: should not resume when predecessor is not finish:FINISHED packages/core/src/commands/command.event.handler.spec.ts:1312 — This test sets up 4 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: should not warn about a missing predecessor when the read itself failed packages/core/src/commands/command.event.handler.spec.ts:1371 — This test sets up 5 test doubles (for example `jest.fn`) against 1 real object(s) of its own, and its only verification is 1 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.
Mock-dominated test: should not lookup predecessor when version is 1 packages/core/src/commands/command.event.handler.spec.ts:1398 — This test sets up 4 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: should pass JWT claims to resolveRoles packages/core/src/guard/roles.guard.spec.ts:1199 — This test sets up 3 test doubles (for example `jest.spyOn`) 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: should execute the sub task queue event handler packages/task/src/event/sub-task.queue.event.handler.spec.ts:100 — This test sets up 3 test doubles (for example `jest.spyOn`) against 1 real object(s) of its own, and its only verification is 2 check(s) that the doubles were called. It pins how the code is wired, not what it does: it passes with a wrong result and fails when a call is harmlessly reordered or merged. Assert the outcome instead (the value returned, the state left behind), build collaborators and value objects for real or with a small hand-written fake, and keep doubles for the boundaries the test cannot own — the network, the clock, the file system.

D30 · Dependency Vulnerabilities · Low CVE · ×7

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

M4 · Documentation accuracy · README/code drift · ×5

README/code drift docs/ERROR_CATALOG.md:350 — docs/ERROR_CATALOG.md names the package `@mbc-cqrs-serverless/import@^0.1.75`, but no package.json of the workspace declares or depends on it. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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/ERROR_CATALOG.md:419 — docs/ERROR_CATALOG.md runs `DEBUG=* npm run offline`, but no package.json declares a `offline` script. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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/testing/README.ja.md:36 — docs/testing/README.ja.md names `.e2e-spec.ts`, but no file or folder `.e2e-spec.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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/testing/README.ja.md:38 — docs/testing/README.ja.md names `REDACTED.test`, but no file or folder `REDACTED.test` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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/testing/README.md:38 — docs/testing/README.md names `REDACTED.test`, but no file or folder `REDACTED.test` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, 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.

D30 · Dependency Vulnerabilities · Low vulnerability · ×4

REDACTED
REDACTED
REDACTED
REDACTED

D34 · Knowledge Freshness · Orphaned file · ×4

Orphaned file packages/tenant/src/interfaces/tenant.service.interface.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/src/services/request-logger.service.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/src/events/event-bus.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/src/command-events/data-sync.sfn.event.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.

X10 · Duplicated predicate · Duplicated predicate · ×4

Duplicated predicate packages/master/src/controllers/master-bulk.controller.ts:38 — `item.tenantCode && item.tenantCode !== userContext.tenantCode` appears character-identically in 3 files — packages/master/src/controllers/master-bulk.controller.ts, packages/master/src/controllers/master-data.controller.ts, packages/master/src/controllers/master-setting.controller.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/master/src/helpers/index.ts:43 — `parts.length < 4 || parts[0] !== 'MASTER'` appears character-identically in 2 files — packages/master/src/helpers/index.ts, packages/master/src/templates/master/helpers/id.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/src/command-events/data-sync.new.event.handler.ts:58 — `process.env.IS_OFFLINE === 'true' || process.env.IS_OFFLINE === '1'` appears character-identically in 2 files — packages/core/src/command-events/data-sync.new.event.handler.ts, packages/core/src/notifications/email.service.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/master/src/services/master-data.service.ts:92 — `searchDto.isDeleted === false || searchDto.isDeleted === undefined` appears character-identically in 2 files — packages/master/src/services/master-data.service.ts, packages/master/src/services/master-setting.service.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.

X23 · Unguarded diagnostic materialisation · Diagnostic log message is built whether or not it is wanted · ×3

Diagnostic log message is built whether or not it is wanted REDACTED:17 — `debug` at line 17 is called with an argument built by `JSON.stringify(ctx, null, 2)` (line 17), 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.
Diagnostic log message is built whether or not it is wanted packages/core/src/notifications/event/notification.event.handler.ts:57 — `debug` at line 57 is called with an argument built by `join(', ')` (line 58), 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.
Diagnostic log message is built whether or not it is wanted packages/master/src/services/master-setting.service.ts:534 — `debug` at line 534 is called with an argument built by `JSON.stringify(masterCopyDto)` (line 534), 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.

D16 · Bus Factor · Off-boarding risk · ×2

Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 15 significant file(s) lose their only recent owner: packages/cli/templates/infra/libs/infra-stack.ts, packages/import/src/event/csv-import.sfn.event.handler.ts, packages/core/src/commands/repository.ts, packages/import/src/event/processor/single-import.processor.ts, packages/core/src/data-store/session.service.ts, REDACTED, packages/task/src/event/task.queue.event.handler.ts, packages/import/src/import.controller.ts (+7 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 12 significant file(s) lose their only recent owner: packages/mcp-server/src/tools/analyze.ts, packages/mcp-server/src/prompts/cqrs-guide.ts, packages/cli/src/actions/install-skills.action.ts, packages/mcp-server/src/tools/generator.ts, packages/mcp-server/src/tools/validate.ts, packages/ui-setting/src/services/setting.service.ts, packages/mcp-server/src/server.ts, packages/core/src/commands/command-module.helper.ts (+4 more). Pair on, review, or document these before any departure.

D29 · Static Analysis (SAST) · REDACTED · ×2

REDACTED
REDACTED

D31 · IaC & Container Security · Low IaC · ×2

REDACTED
REDACTED

D16 · Bus Factor · Further sole-owners (lower concentration) · ×1

Further sole-owners (lower concentration) — 1 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (29 single-owned of 92 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 92 of the 527 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: packages/master/src/update-scheme.ts, packages/directory/src/directory.controller.ts.

D20 · ADR Quality · No ADRs found · ×1

No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.

D26 · Project Cohesion · Split packages/core · ×1

Split packages/core — A generic catch-all name that is huge (8k LoC) and sprawls across 28 namespaces. Suggested:

D28 · Secrets (history) · Rotate the exposed credentials · ×1

REDACTED

D34 · Knowledge Freshness · Orphaned files with no living knowledge · ×1

Orphaned files with no living knowledge — 4 of 92 analysed file(s) have no living knowledge left — their last meaningful change has decayed away, so if one breaks, no one currently understands it (counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 92 of the 527 production source files in this repository met that bar). None is large enough to earn a read-through of its own, so this row stands in for the per-file rows rather than raising one each — most significant first: packages/tenant/src/interfaces/tenant.service.interface.ts, packages/core/src/services/request-logger.service.ts, packages/core/src/events/event-bus.ts, packages/core/src/command-events/data-sync.sfn.event.ts. Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D36 · Supply-chain Provenance & Signing · REDACTED · ×1

REDACTED

D37 · Vulnerability-disclosure Policy · REDACTED · ×1

REDACTED

M2 · Architecture documentation · No ADRs · ×1

No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 12/13 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `packages/cli/templates/infra`.

P4 · Deployment & Rollback · No release approval gate · ×1

No release approval gate — Deployment is automated and no gate that pauses it for a human is DECLARED IN THIS REPOSITORY'S PIPELINE FILES. What was read: every file under `.github/workflows/`, `.forgejo/workflows/`, `.gitea/workflows/`, `.azuredevops/` and `.azure-pipelines/`, plus `.gitlab-ci*` and `azure-pipelines*` — with comment text stripped, so documenting a gate is not declaring one. What would have counted: GitLab's `when: manual`, CircleCI's `type: approval`, an Azure `ManualValidation@` task or an `approvals:` block, a Jenkins `input` step, a `uses:` step naming an approval action, an `environment:` paired with `reviewers` / `required_reviewers` / `protection` / `wait-timer` / `deployment_branch_policy`, a draft-release step, a `workflow_dispatch` promotion, or a release-event gate. ★ What this cannot see, because none of it is a file: a GitHub environment whose required reviewers are configured in repo SETTINGS, a branch protection rule, or an organisation deployment policy — all of them real, enforced gates that live outside the repository. If yours is one of those, this row is wrong and nothing in the tree could have told us. Otherwise: whatever reaches the release trigger goes to production unreviewed, so a mistaken merge or tag is live before anyone can stop it.

R8 · Dependency Hygiene · Test-only dependency '@nestjs/mapped-types' in production deps · ×1

Test-only dependency '@nestjs/mapped-types' in production deps packages/core/package.json:59 — Only test files import it (first: packages/core/src/integration/nestjs-mapped-types-behavior.spec.ts:23) — move it to devDependencies.

S1 · Web-Security Posture · No app-layer HTTPS enforcement detected · ×1

No app-layer HTTPS enforcement detected packages/core/src/bootstrap.ts:102 — `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.)

X2 · Cancellation propagation · Not all async functions that make a request accept an AbortSignal · ×1

Not all async functions that make a request accept an AbortSignal — Only 0/2 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 — 2/18 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.

X5 · Nullable reference types · Null assertions (`!`) reduce the strict null checking score · ×1

Null assertions (`!`) reduce the strict null checking score — ~0.3 `!` null assertions per 1k TypeScript source lines — 10 assertion(s) across the 31741 source line(s) of the 511 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: REDACTED (5), packages/mcp-server/src/tools/analyze.ts (2), packages/cli/src/runners/abstract.runner.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

X7 · Silent fallback defaults · Silent fallback default in catch · ×1

Silent fallback default in catch packages/core/src/context/user.ts:37 — `parseTenantGroups` swallows every exception into `return []` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.

Minor — 21 finding(s)

D12 · Dependency Hygiene · Outdated (npm) · ×19

Outdated (npm): @codegenie/serverless-express — @codegenie/serverless-express is pinned at 4.17.0; registry.npmjs.org publishes 5.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): @mbc-cqrs-serverless/core — @mbc-cqrs-serverless/core is pinned at 0.1.6-beta.0; registry.npmjs.org publishes 1.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): @mbc-cqrs-serverless/sequence — @mbc-cqrs-serverless/sequence is pinned at 0.1.5-beta.0; registry.npmjs.org publishes 1.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): @modelcontextprotocol/sdk — @modelcontextprotocol/sdk is pinned at 1.29.0; registry.npmjs.org publishes 1.32.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): @nestjs/common — @nestjs/common is pinned at 10.4.20; registry.npmjs.org publishes 12.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): @nestjs/core — @nestjs/core is pinned at 10.4.22; registry.npmjs.org publishes 12.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): @nestjs/platform-express — @nestjs/platform-express is pinned at 10.4.22; registry.npmjs.org publishes 12.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): @prisma/client — @prisma/client is pinned at 5.20.0; registry.npmjs.org publishes 7.10.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): chalk — chalk is pinned at 4.1.2; 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): class-validator — class-validator is pinned at 0.14.2; registry.npmjs.org publishes 0.15.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): cognito-local — cognito-local is pinned at 3.23.3; registry.npmjs.org publishes 5.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): csv-parser — csv-parser is pinned at 3.2.0; registry.npmjs.org publishes 3.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): js-yaml — js-yaml is pinned at 4.3.2; registry.npmjs.org publishes 5.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): jszip — jszip is pinned at 3.10.1; 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): node-fetch — node-fetch is pinned at 2.7.0; registry.npmjs.org publishes 3.3.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): nodemailer — nodemailer is pinned at 9.1.1; registry.npmjs.org publishes 10.2.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): rimraf — rimraf is pinned at 5.0.10; 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.
Outdated (npm): ulid — ulid is pinned at 2.4.0; registry.npmjs.org publishes 3.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): zod — zod is pinned at 4.3.6; registry.npmjs.org publishes 4.6.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.

D10 · Test Quality · Skipped (documented) · ×2

Skipped (documented): (unnamed test) packages/core/src/integration/nestjs-platform-express-behavior.spec.ts:258 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs
Skipped (documented): (unnamed test) packages/core/src/integration/nestjs-platform-express-behavior.spec.ts:511 — Skipped with a documented reason — a deferral, not lazy debt: declared with no body — a pending test the runner lists but never runs

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.

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5790170412c74aec9386280250719f95/history.json --exit-code 0 --source .	11	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-5790170412c74aec9386280250719f95/tree.json --exit-code 0 --source .	0	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	57	artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilities	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	97	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	15	artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)	semgrep	—	semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 34 file(s) — `packages/cli/schematics/lib/controller/files/__name@dasherize__.controller.ts`, `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-attributes.dto.ts`, `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-command.dto.ts`, `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-create.dto.ts`, `packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-search.dto.ts`, … (+29 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a16444-68b1-73de-b0ad-3d02a60babaf · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 55% · Adequate · gated by X5 ·

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

At a glance — Maturity · 50% · Weak · gated by M4 ·

At a glance — Readiness · 29% · Weak · gated by D13, R5, R8, P5, P7 ·

At a glance — Security · 67% · Adequate · gated by D28, D29, D30, D36 ·

At a glance — Domain Modelling · — · — ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts