Executive summary
mbc-net/mbc-cqrs-serverless is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back in part because two passwords or keys sit in the current code. It scores 46 out of 100, which the At risk rating leaves unchanged.
Production Readiness, at 30, is the weakest lens and counts most in the score. The best first step is replacing the two exposed passwords or keys and switching the old ones off, worth about 15 points. Replacing the 101 deprecated dependencies comes next, worth about 10 points. Raising Production Readiness to 70 would lift the score to about 60.
Ninety known security holes in the packages the code depends on can be used by attackers. Twenty pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and eleven passwords or keys in the code's history and two in the code are open to anyone who can read the repository. Updating the vulnerable packages, pinning each tool to an exact version and replacing each exposed password or key would close these risks. Fixing the weaknesses the scanner points to would fix the four security weaknesses in the code, and the seven unsafe settings in infrastructure or container files need changing to safe values. The 25 uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 30,612 lines, about €89,000 to rebuild.
If Production Readiness rose from 30 to 70, the lowest score rated Strong, the score would rise from 46 to about 60.
New since the last survey: 82 findings
- Cyclomatic Complexity · DynamoDbService.validateAdmissionConditions (cyclomatic 22) packages/core/src/data-store/dynamodb.service.ts
- Cognitive Complexity · DynamoDbService.validateAdmissionConditions (cognitive 20) packages/core/src/data-store/dynamodb.service.ts
- God Classes · ClassTooLong: DynamoDbService packages/core/src/data-store/dynamodb.service.ts
- Test Quality · No assertions: accepts %s without making a request examples/command-admission/local-dynamodb.spec.ts
- Test Reliability · Flaky test: the repository rootpackages/master/src/integration/ulid.spec.ts::ulid Integration Tests Performance Characteristics should generate ULIDs quickly
- 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
- 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
- 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
- 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
- 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
- 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
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Cyclomatic Complexity · Complex function validateAdmissionConditions (cyclomatic 21, cognitive 15) packages/core/src/data-store/dynamodb.service.ts
- Cyclomatic Complexity · Complex function satisfies (cyclomatic 17, cognitive 15) packages/cli/src/actions/new.action.template-integrity.spec.ts
- Large Files · packages/cli/templates/infra/libs/infra-stack.ts: 1311 lines of code packages/cli/templates/infra/libs/infra-stack.ts
- Large Files · packages/core/src/commands/command.service.ts: 590 lines of code packages/core/src/commands/command.service.ts
- Large Files · packages/core/src/data-store/dynamodb.service.ts: 567 lines of code packages/core/src/data-store/dynamodb.service.ts
- Large Files · packages/mcp-server/src/prompts/cqrs-guide.ts: 426 lines of code packages/mcp-server/src/prompts/cqrs-guide.ts
- Dependency Hygiene · Unused dependency 'serverless-dynamodb'
- 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/cli/src/actions/install-skills.action.ts
- Exception handling · Swallowed exception (empty catch) packages/cli/src/actions/install-skills.action.ts
Fixed since the last survey: 159 findings
- Cyclomatic Complexity · InfraStack.constructor (cyclomatic 18) packages/cli/templates/infra/libs/infra-stack.ts
- Cognitive Complexity · InfraStack.constructor (cognitive 21) packages/cli/templates/infra/libs/infra-stack.ts
- God Classes · MethodTooLong: InfraStack.constructor packages/cli/templates/infra/libs/infra-stack.ts
- God Classes · ClassTooLong: InfraStack packages/cli/templates/infra/libs/infra-stack.ts
- God Classes · FileTooLong: libs/infra-stack.ts packages/cli/templates/infra/libs/infra-stack.ts
- Churn × Complexity Hotspots · Repeated repair: packages/core/src/commands/command.event.handler.ts packages/core/src/commands/command.event.handler.ts
- Churn × Complexity Hotspots · Repeated repair: packages/core/src/commands/command.service.ts packages/core/src/commands/command.service.ts
- Churn × Complexity Hotspots · Repeated repair: packages/core/src/commands/command-module.helper.ts packages/core/src/commands/command-module.helper.ts
- Churn × Complexity Hotspots · Repeated repair: packages/core/src/commands/command.module.ts packages/core/src/commands/command.module.ts
- 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
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [CVE redacted] 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
Rebuild cost: about €89,000 · Estimate
| Cost to rebuild | €29,000 to €150,000, for 490 to 1,554 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 46. 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: 30,612 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 core.src.context.invoke | 2 core.src.data-store.s3_service | 3 core.src.interfaces.aws.step-function_interface | 4 core.src.interfaces.command-model_interface | 5 core.src.interfaces.command_dto | 6 core.src.interfaces.data-list_entity | 7 core.src.interfaces.data-model_interface | 8 core.src.interfaces.detail-key_interface | 9 core.src.interfaces.event-handler_interface | 10 core.src.interfaces.event_interface | 11 core.src.interfaces.search_dto | 12 core.src.command-events.data-sync_sfn_event | 13 core.src.data-store.dynamodb_service | 14 core.src.interfaces.command_entity | 15 core.src.interfaces.data_entity | 16 core.src.interfaces.detail_dto | 17 master.src.interfaces.master-setting_interface | 18 task.src.event.task_sfn_event | 19 tenant.src.interfaces.tenant_service_interface | 20 core.src.commands.data_service | 21 import.src.import_service | 22 sequence.src.sequences_service | 23 task.src.event.task_queue_event-factory_interface | 24 task.src.task_service | 25 core.src.commands.history_service | 26 import.src.event.csv-import_sfn_event_handler | 27 core.src.commands.command_service | 28 core.src.commands.command_event_handler | 29 core.src.commands.repository | 30 directory.src.directory_service | 31 master.src.services.master-data_service | 32 master.src.services.master-setting_service | 33 survey-template.src.survey-template_service | 34 tenant.src.services.tenant_service | 35 directory.src.directory_controller | 36 master.src.controllers.master-data_controller | 37 master.src.controllers.master-setting_controller | 38 master.src.handler.master-sfn-task_handler | 39 survey-template.src.survey-template_controller | 40 tenant.src.controllers.tenant_controller |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 core.src.context.invoke | ||||||||||||||||||||||||||||||||||||||||
| 2 core.src.data-store.s3_service | ||||||||||||||||||||||||||||||||||||||||
| 3 core.src.interfaces.aws.step-function_interface | ||||||||||||||||||||||||||||||||||||||||
| 4 core.src.interfaces.command-model_interface | ||||||||||||||||||||||||||||||||||||||||
| 5 core.src.interfaces.command_dto | ||||||||||||||||||||||||||||||||||||||||
| 6 core.src.interfaces.data-list_entity | ||||||||||||||||||||||||||||||||||||||||
| 7 core.src.interfaces.data-model_interface | ||||||||||||||||||||||||||||||||||||||||
| 8 core.src.interfaces.detail-key_interface | ||||||||||||||||||||||||||||||||||||||||
| 9 core.src.interfaces.event-handler_interface | ||||||||||||||||||||||||||||||||||||||||
| 10 core.src.interfaces.event_interface | ||||||||||||||||||||||||||||||||||||||||
| 11 core.src.interfaces.search_dto | ||||||||||||||||||||||||||||||||||||||||
| 12 core.src.command-events.data-sync_sfn_event | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 13 core.src.data-store.dynamodb_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 core.src.interfaces.command_entity | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 core.src.interfaces.data_entity | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 16 core.src.interfaces.detail_dto | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 master.src.interfaces.master-setting_interface | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 18 task.src.event.task_sfn_event | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 tenant.src.interfaces.tenant_service_interface | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 20 core.src.commands.data_service | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 21 import.src.import_service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 22 sequence.src.sequences_service | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 23 task.src.event.task_queue_event-factory_interface | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 task.src.task_service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 core.src.commands.history_service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 26 import.src.event.csv-import_sfn_event_handler | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 core.src.commands.command_service | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 28 core.src.commands.command_event_handler | 1 | 1 | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 29 core.src.commands.repository | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 30 directory.src.directory_service | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 master.src.services.master-data_service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 master.src.services.master-setting_service | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||
| 33 survey-template.src.survey-template_service | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 34 tenant.src.services.tenant_service | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 35 directory.src.directory_controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 master.src.controllers.master-data_controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 master.src.controllers.master-setting_controller | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 38 master.src.handler.master-sfn-task_handler | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||
| 39 survey-template.src.survey-template_controller | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 tenant.src.controllers.tenant_controller | 1 | 1 | 1 |
12→2 core.src.command-events.data-sync_sfn_event uses core.src.data-store.s3_service✕
- Connections
- 1 pair of types, where a type in core.src.command-events.data-sync_sfn_event uses a type in core.src.data-store.s3_service.
- The types involved
packages.core.src.command-events.data-sync_sfn_event.DataSyncCommandSfnEvent→packages.core.src.data-store.s3_service.S3Service
- Direction
- core.src.command-events.data-sync_sfn_event uses core.src.data-store.s3_service, so a change to core.src.data-store.s3_service can break core.src.command-events.data-sync_sfn_event, while a change to core.src.command-events.data-sync_sfn_event can't break core.src.data-store.s3_service.
- Position
- Below the diagonal: core.src.command-events.data-sync_sfn_event uses a module listed above it, which is the healthy direction.
12→3 core.src.command-events.data-sync_sfn_event uses core.src.interfaces.aws.step-function_interface✕
- Connections
- 1 pair of types, where a type in core.src.command-events.data-sync_sfn_event uses a type in core.src.interfaces.aws.step-function_interface.
- The types involved
packages.core.src.command-events.data-sync_sfn_event.DataSyncCommandSfnEvent→packages.core.src.interfaces.aws.step-function_interface.StepFunctionsContext
- Direction
- core.src.command-events.data-sync_sfn_event uses core.src.interfaces.aws.step-function_interface, so a change to core.src.interfaces.aws.step-function_interface can break core.src.command-events.data-sync_sfn_event, while a change to core.src.command-events.data-sync_sfn_event can't break core.src.interfaces.aws.step-function_interface.
- Position
- Below the diagonal: core.src.command-events.data-sync_sfn_event uses a module listed above it, which is the healthy direction.
12→4 core.src.command-events.data-sync_sfn_event uses core.src.interfaces.command-model_interface✕
- Connections
- 1 pair of types, where a type in core.src.command-events.data-sync_sfn_event uses a type in core.src.interfaces.command-model_interface.
- The types involved
packages.core.src.command-events.data-sync_sfn_event.DataSyncCommandSfnEvent→packages.core.src.interfaces.command-model_interface.CommandModel
- Direction
- core.src.command-events.data-sync_sfn_event uses core.src.interfaces.command-model_interface, so a change to core.src.interfaces.command-model_interface can break core.src.command-events.data-sync_sfn_event, while a change to core.src.command-events.data-sync_sfn_event can't break core.src.interfaces.command-model_interface.
- Position
- Below the diagonal: core.src.command-events.data-sync_sfn_event uses a module listed above it, which is the healthy direction.
12→8 core.src.command-events.data-sync_sfn_event uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.command-events.data-sync_sfn_event uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.command-events.data-sync_sfn_event.DataSyncCommandSfnEvent→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.command-events.data-sync_sfn_event uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.command-events.data-sync_sfn_event, while a change to core.src.command-events.data-sync_sfn_event can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.command-events.data-sync_sfn_event uses a module listed above it, which is the healthy direction.
12→10 core.src.command-events.data-sync_sfn_event uses core.src.interfaces.event_interface✕
- Connections
- 1 pair of types, where a type in core.src.command-events.data-sync_sfn_event uses a type in core.src.interfaces.event_interface.
- The types involved
packages.core.src.command-events.data-sync_sfn_event.DataSyncCommandSfnEvent→packages.core.src.interfaces.event_interface.IEvent
- Direction
- core.src.command-events.data-sync_sfn_event uses core.src.interfaces.event_interface, so a change to core.src.interfaces.event_interface can break core.src.command-events.data-sync_sfn_event, while a change to core.src.command-events.data-sync_sfn_event can't break core.src.interfaces.event_interface.
- Position
- Below the diagonal: core.src.command-events.data-sync_sfn_event uses a module listed above it, which is the healthy direction.
13→2 core.src.data-store.dynamodb_service uses core.src.data-store.s3_service✕
- Connections
- 1 pair of types, where a type in core.src.data-store.dynamodb_service uses a type in core.src.data-store.s3_service.
- The types involved
packages.core.src.data-store.dynamodb_service.DynamoDbService→packages.core.src.data-store.s3_service.S3Service
- Direction
- core.src.data-store.dynamodb_service uses core.src.data-store.s3_service, so a change to core.src.data-store.s3_service can break core.src.data-store.dynamodb_service, while a change to core.src.data-store.dynamodb_service can't break core.src.data-store.s3_service.
- Position
- Below the diagonal: core.src.data-store.dynamodb_service uses a module listed above it, which is the healthy direction.
13→8 core.src.data-store.dynamodb_service uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.data-store.dynamodb_service uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.data-store.dynamodb_service.DynamoDbService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.data-store.dynamodb_service uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.data-store.dynamodb_service, while a change to core.src.data-store.dynamodb_service can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.data-store.dynamodb_service uses a module listed above it, which is the healthy direction.
14→4 core.src.interfaces.command_entity uses core.src.interfaces.command-model_interface✕
- Connections
- 1 pair of types, where a type in core.src.interfaces.command_entity uses a type in core.src.interfaces.command-model_interface.
- The types involved
packages.core.src.interfaces.command_entity.CommandEntity→packages.core.src.interfaces.command-model_interface.CommandModel
- Direction
- core.src.interfaces.command_entity uses core.src.interfaces.command-model_interface, so a change to core.src.interfaces.command-model_interface can break core.src.interfaces.command_entity, while a change to core.src.interfaces.command_entity can't break core.src.interfaces.command-model_interface.
- Position
- Below the diagonal: core.src.interfaces.command_entity uses a module listed above it, which is the healthy direction.
14→8 core.src.interfaces.command_entity uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.interfaces.command_entity uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.interfaces.command_entity.CommandEntity→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.interfaces.command_entity uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.interfaces.command_entity, while a change to core.src.interfaces.command_entity can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.interfaces.command_entity uses a module listed above it, which is the healthy direction.
15→7 core.src.interfaces.data_entity uses core.src.interfaces.data-model_interface✕
- Connections
- 1 pair of types, where a type in core.src.interfaces.data_entity uses a type in core.src.interfaces.data-model_interface.
- The types involved
packages.core.src.interfaces.data_entity.DataEntity→packages.core.src.interfaces.data-model_interface.DataModel
- Direction
- core.src.interfaces.data_entity uses core.src.interfaces.data-model_interface, so a change to core.src.interfaces.data-model_interface can break core.src.interfaces.data_entity, while a change to core.src.interfaces.data_entity can't break core.src.interfaces.data-model_interface.
- Position
- Below the diagonal: core.src.interfaces.data_entity uses a module listed above it, which is the healthy direction.
15→8 core.src.interfaces.data_entity uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.interfaces.data_entity uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.interfaces.data_entity.DataEntity→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.interfaces.data_entity uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.interfaces.data_entity, while a change to core.src.interfaces.data_entity can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.interfaces.data_entity uses a module listed above it, which is the healthy direction.
16→8 core.src.interfaces.detail_dto uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.interfaces.detail_dto uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.interfaces.detail_dto.DetailDto→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.interfaces.detail_dto uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.interfaces.detail_dto, while a change to core.src.interfaces.detail_dto can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.interfaces.detail_dto uses a module listed above it, which is the healthy direction.
17→4 master.src.interfaces.master-setting_interface uses core.src.interfaces.command-model_interface✕
- Connections
- 1 pair of types, where a type in master.src.interfaces.master-setting_interface uses a type in core.src.interfaces.command-model_interface.
- The types involved
packages.master.src.interfaces.master-setting_interface.IMasterSettingService→packages.core.src.interfaces.command-model_interface.CommandModel
- Direction
- master.src.interfaces.master-setting_interface uses core.src.interfaces.command-model_interface, so a change to core.src.interfaces.command-model_interface can break master.src.interfaces.master-setting_interface, while a change to master.src.interfaces.master-setting_interface can't break core.src.interfaces.command-model_interface.
- Position
- Below the diagonal: master.src.interfaces.master-setting_interface uses a module listed above it, which is the healthy direction.
17→8 master.src.interfaces.master-setting_interface uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in master.src.interfaces.master-setting_interface uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.master.src.interfaces.master-setting_interface.IMasterSettingService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- master.src.interfaces.master-setting_interface uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break master.src.interfaces.master-setting_interface, while a change to master.src.interfaces.master-setting_interface can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: master.src.interfaces.master-setting_interface uses a module listed above it, which is the healthy direction.
17→11 master.src.interfaces.master-setting_interface uses core.src.interfaces.search_dto✕
- Connections
- 1 pair of types, where a type in master.src.interfaces.master-setting_interface uses a type in core.src.interfaces.search_dto.
- The types involved
packages.master.src.interfaces.master-setting_interface.IMasterSettingService→packages.core.src.interfaces.search_dto.SearchDto
- Direction
- master.src.interfaces.master-setting_interface uses core.src.interfaces.search_dto, so a change to core.src.interfaces.search_dto can break master.src.interfaces.master-setting_interface, while a change to master.src.interfaces.master-setting_interface can't break core.src.interfaces.search_dto.
- Position
- Below the diagonal: master.src.interfaces.master-setting_interface uses a module listed above it, which is the healthy direction.
18→3 task.src.event.task_sfn_event uses core.src.interfaces.aws.step-function_interface✕
- Connections
- 1 pair of types, where a type in task.src.event.task_sfn_event uses a type in core.src.interfaces.aws.step-function_interface.
- The types involved
packages.task.src.event.task_sfn_event.StepFunctionTaskEvent→packages.core.src.interfaces.aws.step-function_interface.StepFunctionsContext
- Direction
- task.src.event.task_sfn_event uses core.src.interfaces.aws.step-function_interface, so a change to core.src.interfaces.aws.step-function_interface can break task.src.event.task_sfn_event, while a change to task.src.event.task_sfn_event can't break core.src.interfaces.aws.step-function_interface.
- Position
- Below the diagonal: task.src.event.task_sfn_event uses a module listed above it, which is the healthy direction.
18→8 task.src.event.task_sfn_event uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in task.src.event.task_sfn_event uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.task.src.event.task_sfn_event.StepFunctionTaskEvent→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- task.src.event.task_sfn_event uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break task.src.event.task_sfn_event, while a change to task.src.event.task_sfn_event can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: task.src.event.task_sfn_event uses a module listed above it, which is the healthy direction.
18→10 task.src.event.task_sfn_event uses core.src.interfaces.event_interface✕
- Connections
- 1 pair of types, where a type in task.src.event.task_sfn_event uses a type in core.src.interfaces.event_interface.
- The types involved
packages.task.src.event.task_sfn_event.StepFunctionTaskEvent→packages.core.src.interfaces.event_interface.IEvent
- Direction
- task.src.event.task_sfn_event uses core.src.interfaces.event_interface, so a change to core.src.interfaces.event_interface can break task.src.event.task_sfn_event, while a change to task.src.event.task_sfn_event can't break core.src.interfaces.event_interface.
- Position
- Below the diagonal: task.src.event.task_sfn_event uses a module listed above it, which is the healthy direction.
19→4 tenant.src.interfaces.tenant_service_interface uses core.src.interfaces.command-model_interface✕
- Connections
- 1 pair of types, where a type in tenant.src.interfaces.tenant_service_interface uses a type in core.src.interfaces.command-model_interface.
- The types involved
packages.tenant.src.interfaces.tenant_service_interface.ITenantService→packages.core.src.interfaces.command-model_interface.CommandModel
- Direction
- tenant.src.interfaces.tenant_service_interface uses core.src.interfaces.command-model_interface, so a change to core.src.interfaces.command-model_interface can break tenant.src.interfaces.tenant_service_interface, while a change to tenant.src.interfaces.tenant_service_interface can't break core.src.interfaces.command-model_interface.
- Position
- Below the diagonal: tenant.src.interfaces.tenant_service_interface uses a module listed above it, which is the healthy direction.
19→7 tenant.src.interfaces.tenant_service_interface uses core.src.interfaces.data-model_interface✕
- Connections
- 1 pair of types, where a type in tenant.src.interfaces.tenant_service_interface uses a type in core.src.interfaces.data-model_interface.
- The types involved
packages.tenant.src.interfaces.tenant_service_interface.ITenantService→packages.core.src.interfaces.data-model_interface.DataModel
- Direction
- tenant.src.interfaces.tenant_service_interface uses core.src.interfaces.data-model_interface, so a change to core.src.interfaces.data-model_interface can break tenant.src.interfaces.tenant_service_interface, while a change to tenant.src.interfaces.tenant_service_interface can't break core.src.interfaces.data-model_interface.
- Position
- Below the diagonal: tenant.src.interfaces.tenant_service_interface uses a module listed above it, which is the healthy direction.
19→8 tenant.src.interfaces.tenant_service_interface uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in tenant.src.interfaces.tenant_service_interface uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.tenant.src.interfaces.tenant_service_interface.ITenantService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- tenant.src.interfaces.tenant_service_interface uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break tenant.src.interfaces.tenant_service_interface, while a change to tenant.src.interfaces.tenant_service_interface can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: tenant.src.interfaces.tenant_service_interface uses a module listed above it, which is the healthy direction.
20→4 core.src.commands.data_service uses core.src.interfaces.command-model_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.data_service uses a type in core.src.interfaces.command-model_interface.
- The types involved
packages.core.src.commands.data_service.DataService→packages.core.src.interfaces.command-model_interface.CommandModel
- Direction
- core.src.commands.data_service uses core.src.interfaces.command-model_interface, so a change to core.src.interfaces.command-model_interface can break core.src.commands.data_service, while a change to core.src.commands.data_service can't break core.src.interfaces.command-model_interface.
- Position
- Below the diagonal: core.src.commands.data_service uses a module listed above it, which is the healthy direction.
20→6 core.src.commands.data_service uses core.src.interfaces.data-list_entity✕
- Connections
- 1 pair of types, where a type in core.src.commands.data_service uses a type in core.src.interfaces.data-list_entity.
- The types involved
packages.core.src.commands.data_service.DataService→packages.core.src.interfaces.data-list_entity.DataListEntity
- Direction
- core.src.commands.data_service uses core.src.interfaces.data-list_entity, so a change to core.src.interfaces.data-list_entity can break core.src.commands.data_service, while a change to core.src.commands.data_service can't break core.src.interfaces.data-list_entity.
- Position
- Below the diagonal: core.src.commands.data_service uses a module listed above it, which is the healthy direction.
20→7 core.src.commands.data_service uses core.src.interfaces.data-model_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.data_service uses a type in core.src.interfaces.data-model_interface.
- The types involved
packages.core.src.commands.data_service.DataService→packages.core.src.interfaces.data-model_interface.DataModel
- Direction
- core.src.commands.data_service uses core.src.interfaces.data-model_interface, so a change to core.src.interfaces.data-model_interface can break core.src.commands.data_service, while a change to core.src.commands.data_service can't break core.src.interfaces.data-model_interface.
- Position
- Below the diagonal: core.src.commands.data_service uses a module listed above it, which is the healthy direction.
20→8 core.src.commands.data_service uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.data_service uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.commands.data_service.DataService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.commands.data_service uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.commands.data_service, while a change to core.src.commands.data_service can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.commands.data_service uses a module listed above it, which is the healthy direction.
20→13 core.src.commands.data_service uses core.src.data-store.dynamodb_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.data_service uses a type in core.src.data-store.dynamodb_service.
- The types involved
packages.core.src.commands.data_service.DataService→packages.core.src.data-store.dynamodb_service.DynamoDbService
- Direction
- core.src.commands.data_service uses core.src.data-store.dynamodb_service, so a change to core.src.data-store.dynamodb_service can break core.src.commands.data_service, while a change to core.src.commands.data_service can't break core.src.data-store.dynamodb_service.
- Position
- Below the diagonal: core.src.commands.data_service uses a module listed above it, which is the healthy direction.
21→2 import.src.import_service uses core.src.data-store.s3_service✕
- Connections
- 1 pair of types, where a type in import.src.import_service uses a type in core.src.data-store.s3_service.
- The types involved
packages.import.src.import_service.ImportService→packages.core.src.data-store.s3_service.S3Service
- Direction
- import.src.import_service uses core.src.data-store.s3_service, so a change to core.src.data-store.s3_service can break import.src.import_service, while a change to import.src.import_service can't break core.src.data-store.s3_service.
- Position
- Below the diagonal: import.src.import_service uses a module listed above it, which is the healthy direction.
21→8 import.src.import_service uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in import.src.import_service uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.import.src.import_service.ImportService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- import.src.import_service uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break import.src.import_service, while a change to import.src.import_service can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: import.src.import_service uses a module listed above it, which is the healthy direction.
21→13 import.src.import_service uses core.src.data-store.dynamodb_service✕
- Connections
- 1 pair of types, where a type in import.src.import_service uses a type in core.src.data-store.dynamodb_service.
- The types involved
packages.import.src.import_service.ImportService→packages.core.src.data-store.dynamodb_service.DynamoDbService
- Direction
- import.src.import_service uses core.src.data-store.dynamodb_service, so a change to core.src.data-store.dynamodb_service can break import.src.import_service, while a change to import.src.import_service can't break core.src.data-store.dynamodb_service.
- Position
- Below the diagonal: import.src.import_service uses a module listed above it, which is the healthy direction.
22→8 sequence.src.sequences_service uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in sequence.src.sequences_service uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.sequence.src.sequences_service.SequencesService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- sequence.src.sequences_service uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break sequence.src.sequences_service, while a change to sequence.src.sequences_service can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: sequence.src.sequences_service uses a module listed above it, which is the healthy direction.
22→13 sequence.src.sequences_service uses core.src.data-store.dynamodb_service✕
- Connections
- 1 pair of types, where a type in sequence.src.sequences_service uses a type in core.src.data-store.dynamodb_service.
- The types involved
packages.sequence.src.sequences_service.SequencesService→packages.core.src.data-store.dynamodb_service.DynamoDbService
- Direction
- sequence.src.sequences_service uses core.src.data-store.dynamodb_service, so a change to core.src.data-store.dynamodb_service can break sequence.src.sequences_service, while a change to sequence.src.sequences_service can't break core.src.data-store.dynamodb_service.
- Position
- Below the diagonal: sequence.src.sequences_service uses a module listed above it, which is the healthy direction.
22→15 sequence.src.sequences_service uses core.src.interfaces.data_entity✕
- Connections
- 1 pair of types, where a type in sequence.src.sequences_service uses a type in core.src.interfaces.data_entity.
- The types involved
packages.sequence.src.sequences_service.SequencesService→packages.core.src.interfaces.data_entity.DataEntity
- Direction
- sequence.src.sequences_service uses core.src.interfaces.data_entity, so a change to core.src.interfaces.data_entity can break sequence.src.sequences_service, while a change to sequence.src.sequences_service can't break core.src.interfaces.data_entity.
- Position
- Below the diagonal: sequence.src.sequences_service uses a module listed above it, which is the healthy direction.
23→3 task.src.event.task_queue_event-factory_interface uses core.src.interfaces.aws.step-function_interface✕
- Connections
- 1 pair of types, where a type in task.src.event.task_queue_event-factory_interface uses a type in core.src.interfaces.aws.step-function_interface.
- The types involved
packages.task.src.event.task_queue_event-factory_interface.EventFactoryAddedTask→packages.core.src.interfaces.aws.step-function_interface.StepFunctionsEvent
- Direction
- task.src.event.task_queue_event-factory_interface uses core.src.interfaces.aws.step-function_interface, so a change to core.src.interfaces.aws.step-function_interface can break task.src.event.task_queue_event-factory_interface, while a change to task.src.event.task_queue_event-factory_interface can't break core.src.interfaces.aws.step-function_interface.
- Position
- Below the diagonal: task.src.event.task_queue_event-factory_interface uses a module listed above it, which is the healthy direction.
23→18 task.src.event.task_queue_event-factory_interface uses task.src.event.task_sfn_event✕
- Connections
- 1 pair of types, where a type in task.src.event.task_queue_event-factory_interface uses a type in task.src.event.task_sfn_event.
- The types involved
packages.task.src.event.task_queue_event-factory_interface.ITaskQueueEventFactory→packages.task.src.event.task_sfn_event.StepFunctionTaskEvent
- Direction
- task.src.event.task_queue_event-factory_interface uses task.src.event.task_sfn_event, so a change to task.src.event.task_sfn_event can break task.src.event.task_queue_event-factory_interface, while a change to task.src.event.task_queue_event-factory_interface can't break task.src.event.task_sfn_event.
- Position
- Below the diagonal: task.src.event.task_queue_event-factory_interface uses a module listed above it, which is the healthy direction.
24→8 task.src.task_service uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in task.src.task_service uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.task.src.task_service.TaskService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- task.src.task_service uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break task.src.task_service, while a change to task.src.task_service can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: task.src.task_service uses a module listed above it, which is the healthy direction.
24→13 task.src.task_service uses core.src.data-store.dynamodb_service✕
- Connections
- 1 pair of types, where a type in task.src.task_service uses a type in core.src.data-store.dynamodb_service.
- The types involved
packages.task.src.task_service.TaskService→packages.core.src.data-store.dynamodb_service.DynamoDbService
- Direction
- task.src.task_service uses core.src.data-store.dynamodb_service, so a change to core.src.data-store.dynamodb_service can break task.src.task_service, while a change to task.src.task_service can't break core.src.data-store.dynamodb_service.
- Position
- Below the diagonal: task.src.task_service uses a module listed above it, which is the healthy direction.
25→7 core.src.commands.history_service uses core.src.interfaces.data-model_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.history_service uses a type in core.src.interfaces.data-model_interface.
- The types involved
packages.core.src.commands.history_service.HistoryService→packages.core.src.interfaces.data-model_interface.DataModel
- Direction
- core.src.commands.history_service uses core.src.interfaces.data-model_interface, so a change to core.src.interfaces.data-model_interface can break core.src.commands.history_service, while a change to core.src.commands.history_service can't break core.src.interfaces.data-model_interface.
- Position
- Below the diagonal: core.src.commands.history_service uses a module listed above it, which is the healthy direction.
25→8 core.src.commands.history_service uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.history_service uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.commands.history_service.HistoryService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.commands.history_service uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.commands.history_service, while a change to core.src.commands.history_service can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.commands.history_service uses a module listed above it, which is the healthy direction.
25→13 core.src.commands.history_service uses core.src.data-store.dynamodb_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.history_service uses a type in core.src.data-store.dynamodb_service.
- The types involved
packages.core.src.commands.history_service.HistoryService→packages.core.src.data-store.dynamodb_service.DynamoDbService
- Direction
- core.src.commands.history_service uses core.src.data-store.dynamodb_service, so a change to core.src.data-store.dynamodb_service can break core.src.commands.history_service, while a change to core.src.commands.history_service can't break core.src.data-store.dynamodb_service.
- Position
- Below the diagonal: core.src.commands.history_service uses a module listed above it, which is the healthy direction.
25→20 core.src.commands.history_service uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.history_service uses a type in core.src.commands.data_service.
- The types involved
packages.core.src.commands.history_service.HistoryService→packages.core.src.commands.data_service.DataService
- Direction
- core.src.commands.history_service uses core.src.commands.data_service, so a change to core.src.commands.data_service can break core.src.commands.history_service, while a change to core.src.commands.history_service can't break core.src.commands.data_service.
- Position
- Below the diagonal: core.src.commands.history_service uses a module listed above it, which is the healthy direction.
26→2 import.src.event.csv-import_sfn_event_handler uses core.src.data-store.s3_service✕
- Connections
- 1 pair of types, where a type in import.src.event.csv-import_sfn_event_handler uses a type in core.src.data-store.s3_service.
- The types involved
packages.import.src.event.csv-import_sfn_event_handler.CsvImportSfnEventHandler→packages.core.src.data-store.s3_service.S3Service
- Direction
- import.src.event.csv-import_sfn_event_handler uses core.src.data-store.s3_service, so a change to core.src.data-store.s3_service can break import.src.event.csv-import_sfn_event_handler, while a change to import.src.event.csv-import_sfn_event_handler can't break core.src.data-store.s3_service.
- Position
- Below the diagonal: import.src.event.csv-import_sfn_event_handler uses a module listed above it, which is the healthy direction.
26→9 import.src.event.csv-import_sfn_event_handler uses core.src.interfaces.event-handler_interface✕
- Connections
- 1 pair of types, where a type in import.src.event.csv-import_sfn_event_handler uses a type in core.src.interfaces.event-handler_interface.
- The types involved
packages.import.src.event.csv-import_sfn_event_handler.CsvImportSfnEventHandler→packages.core.src.interfaces.event-handler_interface.IEventHandler
- Direction
- import.src.event.csv-import_sfn_event_handler uses core.src.interfaces.event-handler_interface, so a change to core.src.interfaces.event-handler_interface can break import.src.event.csv-import_sfn_event_handler, while a change to import.src.event.csv-import_sfn_event_handler can't break core.src.interfaces.event-handler_interface.
- Position
- Below the diagonal: import.src.event.csv-import_sfn_event_handler uses a module listed above it, which is the healthy direction.
26→21 import.src.event.csv-import_sfn_event_handler uses import.src.import_service✕
- Connections
- 1 pair of types, where a type in import.src.event.csv-import_sfn_event_handler uses a type in import.src.import_service.
- The types involved
packages.import.src.event.csv-import_sfn_event_handler.CsvImportSfnEventHandler→packages.import.src.import_service.ImportService
- Direction
- import.src.event.csv-import_sfn_event_handler uses import.src.import_service, so a change to import.src.import_service can break import.src.event.csv-import_sfn_event_handler, while a change to import.src.event.csv-import_sfn_event_handler can't break import.src.import_service.
- Position
- Below the diagonal: import.src.event.csv-import_sfn_event_handler uses a module listed above it, which is the healthy direction.
27→4 core.src.commands.command_service uses core.src.interfaces.command-model_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_service uses a type in core.src.interfaces.command-model_interface.
- The types involved
packages.core.src.commands.command_service.CommandService→packages.core.src.interfaces.command-model_interface.CommandModel
- Direction
- core.src.commands.command_service uses core.src.interfaces.command-model_interface, so a change to core.src.interfaces.command-model_interface can break core.src.commands.command_service, while a change to core.src.commands.command_service can't break core.src.interfaces.command-model_interface.
- Position
- Below the diagonal: core.src.commands.command_service uses a module listed above it, which is the healthy direction.
27→8 core.src.commands.command_service uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_service uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.commands.command_service.CommandService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.commands.command_service uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.commands.command_service, while a change to core.src.commands.command_service can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.commands.command_service uses a module listed above it, which is the healthy direction.
27→13 core.src.commands.command_service uses core.src.data-store.dynamodb_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_service uses a type in core.src.data-store.dynamodb_service.
- The types involved
packages.core.src.commands.command_service.CommandService→packages.core.src.data-store.dynamodb_service.DynamoDbService
- Direction
- core.src.commands.command_service uses core.src.data-store.dynamodb_service, so a change to core.src.data-store.dynamodb_service can break core.src.commands.command_service, while a change to core.src.commands.command_service can't break core.src.data-store.dynamodb_service.
- Position
- Below the diagonal: core.src.commands.command_service uses a module listed above it, which is the healthy direction.
27→20 core.src.commands.command_service uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_service uses a type in core.src.commands.data_service.
- The types involved
packages.core.src.commands.command_service.CommandService→packages.core.src.commands.data_service.DataService
- Direction
- core.src.commands.command_service uses core.src.commands.data_service, so a change to core.src.commands.data_service can break core.src.commands.command_service, while a change to core.src.commands.command_service can't break core.src.commands.data_service.
- Position
- Below the diagonal: core.src.commands.command_service uses a module listed above it, which is the healthy direction.
27→25 core.src.commands.command_service uses core.src.commands.history_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_service uses a type in core.src.commands.history_service.
- The types involved
packages.core.src.commands.command_service.CommandService→packages.core.src.commands.history_service.HistoryService
- Direction
- core.src.commands.command_service uses core.src.commands.history_service, so a change to core.src.commands.history_service can break core.src.commands.command_service, while a change to core.src.commands.command_service can't break core.src.commands.history_service.
- Position
- Below the diagonal: core.src.commands.command_service uses a module listed above it, which is the healthy direction.
28→2 core.src.commands.command_event_handler uses core.src.data-store.s3_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_event_handler uses a type in core.src.data-store.s3_service.
- The types involved
packages.core.src.commands.command_event_handler.CommandEventHandler→packages.core.src.data-store.s3_service.S3Service
- Direction
- core.src.commands.command_event_handler uses core.src.data-store.s3_service, so a change to core.src.data-store.s3_service can break core.src.commands.command_event_handler, while a change to core.src.commands.command_event_handler can't break core.src.data-store.s3_service.
- Position
- Below the diagonal: core.src.commands.command_event_handler uses a module listed above it, which is the healthy direction.
28→4 core.src.commands.command_event_handler uses core.src.interfaces.command-model_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_event_handler uses a type in core.src.interfaces.command-model_interface.
- The types involved
packages.core.src.commands.command_event_handler.CommandEventHandler→packages.core.src.interfaces.command-model_interface.CommandModel
- Direction
- core.src.commands.command_event_handler uses core.src.interfaces.command-model_interface, so a change to core.src.interfaces.command-model_interface can break core.src.commands.command_event_handler, while a change to core.src.commands.command_event_handler can't break core.src.interfaces.command-model_interface.
- Position
- Below the diagonal: core.src.commands.command_event_handler uses a module listed above it, which is the healthy direction.
28→8 core.src.commands.command_event_handler uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_event_handler uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.commands.command_event_handler.CommandEventHandler→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.commands.command_event_handler uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.commands.command_event_handler, while a change to core.src.commands.command_event_handler can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.commands.command_event_handler uses a module listed above it, which is the healthy direction.
28→12 core.src.commands.command_event_handler uses core.src.command-events.data-sync_sfn_event✕
- Connections
- 2 pairs of types, where a type in core.src.commands.command_event_handler uses a type in core.src.command-events.data-sync_sfn_event.
- The types involved
packages.core.src.commands.command_event_handler.CommandEventHandler→packages.core.src.command-events.data-sync_sfn_event.DataSyncCommandSfnEventpackages.core.src.commands.command_event_handler.CommandEventHandler→packages.core.src.command-events.data-sync_sfn_event.StepFunctionStateInput
- Direction
- core.src.commands.command_event_handler uses core.src.command-events.data-sync_sfn_event, so a change to core.src.command-events.data-sync_sfn_event can break core.src.commands.command_event_handler, while a change to core.src.commands.command_event_handler can't break core.src.command-events.data-sync_sfn_event.
- Position
- Below the diagonal: core.src.commands.command_event_handler uses a module listed above it, which is the healthy direction.
28→20 core.src.commands.command_event_handler uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_event_handler uses a type in core.src.commands.data_service.
- The types involved
packages.core.src.commands.command_event_handler.CommandEventHandler→packages.core.src.commands.data_service.DataService
- Direction
- core.src.commands.command_event_handler uses core.src.commands.data_service, so a change to core.src.commands.data_service can break core.src.commands.command_event_handler, while a change to core.src.commands.command_event_handler can't break core.src.commands.data_service.
- Position
- Below the diagonal: core.src.commands.command_event_handler uses a module listed above it, which is the healthy direction.
28→25 core.src.commands.command_event_handler uses core.src.commands.history_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_event_handler uses a type in core.src.commands.history_service.
- The types involved
packages.core.src.commands.command_event_handler.CommandEventHandler→packages.core.src.commands.history_service.HistoryService
- Direction
- core.src.commands.command_event_handler uses core.src.commands.history_service, so a change to core.src.commands.history_service can break core.src.commands.command_event_handler, while a change to core.src.commands.command_event_handler can't break core.src.commands.history_service.
- Position
- Below the diagonal: core.src.commands.command_event_handler uses a module listed above it, which is the healthy direction.
28→27 core.src.commands.command_event_handler uses core.src.commands.command_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.command_event_handler uses a type in core.src.commands.command_service.
- The types involved
packages.core.src.commands.command_event_handler.CommandEventHandler→packages.core.src.commands.command_service.CommandService
- Direction
- core.src.commands.command_event_handler uses core.src.commands.command_service, so a change to core.src.commands.command_service can break core.src.commands.command_event_handler, while a change to core.src.commands.command_event_handler can't break core.src.commands.command_service.
- Position
- Below the diagonal: core.src.commands.command_event_handler uses a module listed above it, which is the healthy direction.
29→6 core.src.commands.repository uses core.src.interfaces.data-list_entity✕
- Connections
- 1 pair of types, where a type in core.src.commands.repository uses a type in core.src.interfaces.data-list_entity.
- The types involved
packages.core.src.commands.repository.Repository→packages.core.src.interfaces.data-list_entity.DataListEntity
- Direction
- core.src.commands.repository uses core.src.interfaces.data-list_entity, so a change to core.src.interfaces.data-list_entity can break core.src.commands.repository, while a change to core.src.commands.repository can't break core.src.interfaces.data-list_entity.
- Position
- Below the diagonal: core.src.commands.repository uses a module listed above it, which is the healthy direction.
29→7 core.src.commands.repository uses core.src.interfaces.data-model_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.repository uses a type in core.src.interfaces.data-model_interface.
- The types involved
packages.core.src.commands.repository.Repository→packages.core.src.interfaces.data-model_interface.DataModel
- Direction
- core.src.commands.repository uses core.src.interfaces.data-model_interface, so a change to core.src.interfaces.data-model_interface can break core.src.commands.repository, while a change to core.src.commands.repository can't break core.src.interfaces.data-model_interface.
- Position
- Below the diagonal: core.src.commands.repository uses a module listed above it, which is the healthy direction.
29→8 core.src.commands.repository uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in core.src.commands.repository uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.core.src.commands.repository.Repository→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- core.src.commands.repository uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break core.src.commands.repository, while a change to core.src.commands.repository can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: core.src.commands.repository uses a module listed above it, which is the healthy direction.
29→20 core.src.commands.repository uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.repository uses a type in core.src.commands.data_service.
- The types involved
packages.core.src.commands.repository.Repository→packages.core.src.commands.data_service.DataService
- Direction
- core.src.commands.repository uses core.src.commands.data_service, so a change to core.src.commands.data_service can break core.src.commands.repository, while a change to core.src.commands.repository can't break core.src.commands.data_service.
- Position
- Below the diagonal: core.src.commands.repository uses a module listed above it, which is the healthy direction.
29→27 core.src.commands.repository uses core.src.commands.command_service✕
- Connections
- 1 pair of types, where a type in core.src.commands.repository uses a type in core.src.commands.command_service.
- The types involved
packages.core.src.commands.repository.Repository→packages.core.src.commands.command_service.CommandService
- Direction
- core.src.commands.repository uses core.src.commands.command_service, so a change to core.src.commands.command_service can break core.src.commands.repository, while a change to core.src.commands.repository can't break core.src.commands.command_service.
- Position
- Below the diagonal: core.src.commands.repository uses a module listed above it, which is the healthy direction.
30→2 directory.src.directory_service uses core.src.data-store.s3_service✕
- Connections
- 1 pair of types, where a type in directory.src.directory_service uses a type in core.src.data-store.s3_service.
- The types involved
packages.directory.src.directory_service.DirectoryService→packages.core.src.data-store.s3_service.S3Service
- Direction
- directory.src.directory_service uses core.src.data-store.s3_service, so a change to core.src.data-store.s3_service can break directory.src.directory_service, while a change to directory.src.directory_service can't break core.src.data-store.s3_service.
- Position
- Below the diagonal: directory.src.directory_service uses a module listed above it, which is the healthy direction.
30→13 directory.src.directory_service uses core.src.data-store.dynamodb_service✕
- Connections
- 1 pair of types, where a type in directory.src.directory_service uses a type in core.src.data-store.dynamodb_service.
- The types involved
packages.directory.src.directory_service.DirectoryService→packages.core.src.data-store.dynamodb_service.DynamoDbService
- Direction
- directory.src.directory_service uses core.src.data-store.dynamodb_service, so a change to core.src.data-store.dynamodb_service can break directory.src.directory_service, while a change to directory.src.directory_service can't break core.src.data-store.dynamodb_service.
- Position
- Below the diagonal: directory.src.directory_service uses a module listed above it, which is the healthy direction.
30→16 directory.src.directory_service uses core.src.interfaces.detail_dto✕
- Connections
- 1 pair of types, where a type in directory.src.directory_service uses a type in core.src.interfaces.detail_dto.
- The types involved
packages.directory.src.directory_service.DirectoryService→packages.core.src.interfaces.detail_dto.DetailDto
- Direction
- directory.src.directory_service uses core.src.interfaces.detail_dto, so a change to core.src.interfaces.detail_dto can break directory.src.directory_service, while a change to directory.src.directory_service can't break core.src.interfaces.detail_dto.
- Position
- Below the diagonal: directory.src.directory_service uses a module listed above it, which is the healthy direction.
30→20 directory.src.directory_service uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in directory.src.directory_service uses a type in core.src.commands.data_service.
- The types involved
packages.directory.src.directory_service.DirectoryService→packages.core.src.commands.data_service.DataService
- Direction
- directory.src.directory_service uses core.src.commands.data_service, so a change to core.src.commands.data_service can break directory.src.directory_service, while a change to directory.src.directory_service can't break core.src.commands.data_service.
- Position
- Below the diagonal: directory.src.directory_service uses a module listed above it, which is the healthy direction.
30→27 directory.src.directory_service uses core.src.commands.command_service✕
- Connections
- 1 pair of types, where a type in directory.src.directory_service uses a type in core.src.commands.command_service.
- The types involved
packages.directory.src.directory_service.DirectoryService→packages.core.src.commands.command_service.CommandService
- Direction
- directory.src.directory_service uses core.src.commands.command_service, so a change to core.src.commands.command_service can break directory.src.directory_service, while a change to directory.src.directory_service can't break core.src.commands.command_service.
- Position
- Below the diagonal: directory.src.directory_service uses a module listed above it, which is the healthy direction.
31→1 master.src.services.master-data_service uses core.src.context.invoke✕
- Connections
- 1 pair of types, where a type in master.src.services.master-data_service uses a type in core.src.context.invoke.
- The types involved
packages.master.src.services.master-data_service.MasterDataService→packages.core.src.context.invoke.IInvoke
- Direction
- master.src.services.master-data_service uses core.src.context.invoke, so a change to core.src.context.invoke can break master.src.services.master-data_service, while a change to master.src.services.master-data_service can't break core.src.context.invoke.
- Position
- Below the diagonal: master.src.services.master-data_service uses a module listed above it, which is the healthy direction.
31→16 master.src.services.master-data_service uses core.src.interfaces.detail_dto✕
- Connections
- 1 pair of types, where a type in master.src.services.master-data_service uses a type in core.src.interfaces.detail_dto.
- The types involved
packages.master.src.services.master-data_service.MasterDataService→packages.core.src.interfaces.detail_dto.DetailDto
- Direction
- master.src.services.master-data_service uses core.src.interfaces.detail_dto, so a change to core.src.interfaces.detail_dto can break master.src.services.master-data_service, while a change to master.src.services.master-data_service can't break core.src.interfaces.detail_dto.
- Position
- Below the diagonal: master.src.services.master-data_service uses a module listed above it, which is the healthy direction.
31→20 master.src.services.master-data_service uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in master.src.services.master-data_service uses a type in core.src.commands.data_service.
- The types involved
packages.master.src.services.master-data_service.MasterDataService→packages.core.src.commands.data_service.DataService
- Direction
- master.src.services.master-data_service uses core.src.commands.data_service, so a change to core.src.commands.data_service can break master.src.services.master-data_service, while a change to master.src.services.master-data_service can't break core.src.commands.data_service.
- Position
- Below the diagonal: master.src.services.master-data_service uses a module listed above it, which is the healthy direction.
31→27 master.src.services.master-data_service uses core.src.commands.command_service✕
- Connections
- 1 pair of types, where a type in master.src.services.master-data_service uses a type in core.src.commands.command_service.
- The types involved
packages.master.src.services.master-data_service.MasterDataService→packages.core.src.commands.command_service.CommandService
- Direction
- master.src.services.master-data_service uses core.src.commands.command_service, so a change to core.src.commands.command_service can break master.src.services.master-data_service, while a change to master.src.services.master-data_service can't break core.src.commands.command_service.
- Position
- Below the diagonal: master.src.services.master-data_service uses a module listed above it, which is the healthy direction.
32→1 master.src.services.master-setting_service uses core.src.context.invoke✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in core.src.context.invoke.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.core.src.context.invoke.IInvoke
- Direction
- master.src.services.master-setting_service uses core.src.context.invoke, so a change to core.src.context.invoke can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break core.src.context.invoke.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
32→4 master.src.services.master-setting_service uses core.src.interfaces.command-model_interface✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in core.src.interfaces.command-model_interface.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.core.src.interfaces.command-model_interface.CommandModel
- Direction
- master.src.services.master-setting_service uses core.src.interfaces.command-model_interface, so a change to core.src.interfaces.command-model_interface can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break core.src.interfaces.command-model_interface.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
32→8 master.src.services.master-setting_service uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- master.src.services.master-setting_service uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
32→11 master.src.services.master-setting_service uses core.src.interfaces.search_dto✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in core.src.interfaces.search_dto.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.core.src.interfaces.search_dto.SearchDto
- Direction
- master.src.services.master-setting_service uses core.src.interfaces.search_dto, so a change to core.src.interfaces.search_dto can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break core.src.interfaces.search_dto.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
32→13 master.src.services.master-setting_service uses core.src.data-store.dynamodb_service✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in core.src.data-store.dynamodb_service.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.core.src.data-store.dynamodb_service.DynamoDbService
- Direction
- master.src.services.master-setting_service uses core.src.data-store.dynamodb_service, so a change to core.src.data-store.dynamodb_service can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break core.src.data-store.dynamodb_service.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
32→16 master.src.services.master-setting_service uses core.src.interfaces.detail_dto✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in core.src.interfaces.detail_dto.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.core.src.interfaces.detail_dto.DetailDto
- Direction
- master.src.services.master-setting_service uses core.src.interfaces.detail_dto, so a change to core.src.interfaces.detail_dto can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break core.src.interfaces.detail_dto.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
32→17 master.src.services.master-setting_service uses master.src.interfaces.master-setting_interface✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in master.src.interfaces.master-setting_interface.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.master.src.interfaces.master-setting_interface.IMasterSettingService
- Direction
- master.src.services.master-setting_service uses master.src.interfaces.master-setting_interface, so a change to master.src.interfaces.master-setting_interface can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break master.src.interfaces.master-setting_interface.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
32→20 master.src.services.master-setting_service uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in core.src.commands.data_service.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.core.src.commands.data_service.DataService
- Direction
- master.src.services.master-setting_service uses core.src.commands.data_service, so a change to core.src.commands.data_service can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break core.src.commands.data_service.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
32→24 master.src.services.master-setting_service uses task.src.task_service✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in task.src.task_service.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.task.src.task_service.TaskService
- Direction
- master.src.services.master-setting_service uses task.src.task_service, so a change to task.src.task_service can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break task.src.task_service.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
32→27 master.src.services.master-setting_service uses core.src.commands.command_service✕
- Connections
- 1 pair of types, where a type in master.src.services.master-setting_service uses a type in core.src.commands.command_service.
- The types involved
packages.master.src.services.master-setting_service.MasterSettingService→packages.core.src.commands.command_service.CommandService
- Direction
- master.src.services.master-setting_service uses core.src.commands.command_service, so a change to core.src.commands.command_service can break master.src.services.master-setting_service, while a change to master.src.services.master-setting_service can't break core.src.commands.command_service.
- Position
- Below the diagonal: master.src.services.master-setting_service uses a module listed above it, which is the healthy direction.
33→11 survey-template.src.survey-template_service uses core.src.interfaces.search_dto✕
- Connections
- 1 pair of types, where a type in survey-template.src.survey-template_service uses a type in core.src.interfaces.search_dto.
- The types involved
packages.survey-template.src.survey-template_service.SurveyTemplateService→packages.core.src.interfaces.search_dto.SearchDto
- Direction
- survey-template.src.survey-template_service uses core.src.interfaces.search_dto, so a change to core.src.interfaces.search_dto can break survey-template.src.survey-template_service, while a change to survey-template.src.survey-template_service can't break core.src.interfaces.search_dto.
- Position
- Below the diagonal: survey-template.src.survey-template_service uses a module listed above it, which is the healthy direction.
33→16 survey-template.src.survey-template_service uses core.src.interfaces.detail_dto✕
- Connections
- 1 pair of types, where a type in survey-template.src.survey-template_service uses a type in core.src.interfaces.detail_dto.
- The types involved
packages.survey-template.src.survey-template_service.SurveyTemplateService→packages.core.src.interfaces.detail_dto.DetailDto
- Direction
- survey-template.src.survey-template_service uses core.src.interfaces.detail_dto, so a change to core.src.interfaces.detail_dto can break survey-template.src.survey-template_service, while a change to survey-template.src.survey-template_service can't break core.src.interfaces.detail_dto.
- Position
- Below the diagonal: survey-template.src.survey-template_service uses a module listed above it, which is the healthy direction.
33→20 survey-template.src.survey-template_service uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in survey-template.src.survey-template_service uses a type in core.src.commands.data_service.
- The types involved
packages.survey-template.src.survey-template_service.SurveyTemplateService→packages.core.src.commands.data_service.DataService
- Direction
- survey-template.src.survey-template_service uses core.src.commands.data_service, so a change to core.src.commands.data_service can break survey-template.src.survey-template_service, while a change to survey-template.src.survey-template_service can't break core.src.commands.data_service.
- Position
- Below the diagonal: survey-template.src.survey-template_service uses a module listed above it, which is the healthy direction.
33→27 survey-template.src.survey-template_service uses core.src.commands.command_service✕
- Connections
- 1 pair of types, where a type in survey-template.src.survey-template_service uses a type in core.src.commands.command_service.
- The types involved
packages.survey-template.src.survey-template_service.SurveyTemplateService→packages.core.src.commands.command_service.CommandService
- Direction
- survey-template.src.survey-template_service uses core.src.commands.command_service, so a change to core.src.commands.command_service can break survey-template.src.survey-template_service, while a change to survey-template.src.survey-template_service can't break core.src.commands.command_service.
- Position
- Below the diagonal: survey-template.src.survey-template_service uses a module listed above it, which is the healthy direction.
34→4 tenant.src.services.tenant_service uses core.src.interfaces.command-model_interface✕
- Connections
- 1 pair of types, where a type in tenant.src.services.tenant_service uses a type in core.src.interfaces.command-model_interface.
- The types involved
packages.tenant.src.services.tenant_service.TenantService→packages.core.src.interfaces.command-model_interface.CommandModel
- Direction
- tenant.src.services.tenant_service uses core.src.interfaces.command-model_interface, so a change to core.src.interfaces.command-model_interface can break tenant.src.services.tenant_service, while a change to tenant.src.services.tenant_service can't break core.src.interfaces.command-model_interface.
- Position
- Below the diagonal: tenant.src.services.tenant_service uses a module listed above it, which is the healthy direction.
34→7 tenant.src.services.tenant_service uses core.src.interfaces.data-model_interface✕
- Connections
- 1 pair of types, where a type in tenant.src.services.tenant_service uses a type in core.src.interfaces.data-model_interface.
- The types involved
packages.tenant.src.services.tenant_service.TenantService→packages.core.src.interfaces.data-model_interface.DataModel
- Direction
- tenant.src.services.tenant_service uses core.src.interfaces.data-model_interface, so a change to core.src.interfaces.data-model_interface can break tenant.src.services.tenant_service, while a change to tenant.src.services.tenant_service can't break core.src.interfaces.data-model_interface.
- Position
- Below the diagonal: tenant.src.services.tenant_service uses a module listed above it, which is the healthy direction.
34→8 tenant.src.services.tenant_service uses core.src.interfaces.detail-key_interface✕
- Connections
- 1 pair of types, where a type in tenant.src.services.tenant_service uses a type in core.src.interfaces.detail-key_interface.
- The types involved
packages.tenant.src.services.tenant_service.TenantService→packages.core.src.interfaces.detail-key_interface.DetailKey
- Direction
- tenant.src.services.tenant_service uses core.src.interfaces.detail-key_interface, so a change to core.src.interfaces.detail-key_interface can break tenant.src.services.tenant_service, while a change to tenant.src.services.tenant_service can't break core.src.interfaces.detail-key_interface.
- Position
- Below the diagonal: tenant.src.services.tenant_service uses a module listed above it, which is the healthy direction.
34→19 tenant.src.services.tenant_service uses tenant.src.interfaces.tenant_service_interface✕
- Connections
- 1 pair of types, where a type in tenant.src.services.tenant_service uses a type in tenant.src.interfaces.tenant_service_interface.
- The types involved
packages.tenant.src.services.tenant_service.TenantService→packages.tenant.src.interfaces.tenant_service_interface.ITenantService
- Direction
- tenant.src.services.tenant_service uses tenant.src.interfaces.tenant_service_interface, so a change to tenant.src.interfaces.tenant_service_interface can break tenant.src.services.tenant_service, while a change to tenant.src.services.tenant_service can't break tenant.src.interfaces.tenant_service_interface.
- Position
- Below the diagonal: tenant.src.services.tenant_service uses a module listed above it, which is the healthy direction.
34→20 tenant.src.services.tenant_service uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in tenant.src.services.tenant_service uses a type in core.src.commands.data_service.
- The types involved
packages.tenant.src.services.tenant_service.TenantService→packages.core.src.commands.data_service.DataService
- Direction
- tenant.src.services.tenant_service uses core.src.commands.data_service, so a change to core.src.commands.data_service can break tenant.src.services.tenant_service, while a change to tenant.src.services.tenant_service can't break core.src.commands.data_service.
- Position
- Below the diagonal: tenant.src.services.tenant_service uses a module listed above it, which is the healthy direction.
34→27 tenant.src.services.tenant_service uses core.src.commands.command_service✕
- Connections
- 1 pair of types, where a type in tenant.src.services.tenant_service uses a type in core.src.commands.command_service.
- The types involved
packages.tenant.src.services.tenant_service.TenantService→packages.core.src.commands.command_service.CommandService
- Direction
- tenant.src.services.tenant_service uses core.src.commands.command_service, so a change to core.src.commands.command_service can break tenant.src.services.tenant_service, while a change to tenant.src.services.tenant_service can't break core.src.commands.command_service.
- Position
- Below the diagonal: tenant.src.services.tenant_service uses a module listed above it, which is the healthy direction.
35→1 directory.src.directory_controller uses core.src.context.invoke✕
- Connections
- 1 pair of types, where a type in directory.src.directory_controller uses a type in core.src.context.invoke.
- The types involved
packages.directory.src.directory_controller.DirectoryController→packages.core.src.context.invoke.IInvoke
- Direction
- directory.src.directory_controller uses core.src.context.invoke, so a change to core.src.context.invoke can break directory.src.directory_controller, while a change to directory.src.directory_controller can't break core.src.context.invoke.
- Position
- Below the diagonal: directory.src.directory_controller uses a module listed above it, which is the healthy direction.
35→16 directory.src.directory_controller uses core.src.interfaces.detail_dto✕
- Connections
- 1 pair of types, where a type in directory.src.directory_controller uses a type in core.src.interfaces.detail_dto.
- The types involved
packages.directory.src.directory_controller.DirectoryController→packages.core.src.interfaces.detail_dto.DetailDto
- Direction
- directory.src.directory_controller uses core.src.interfaces.detail_dto, so a change to core.src.interfaces.detail_dto can break directory.src.directory_controller, while a change to directory.src.directory_controller can't break core.src.interfaces.detail_dto.
- Position
- Below the diagonal: directory.src.directory_controller uses a module listed above it, which is the healthy direction.
35→30 directory.src.directory_controller uses directory.src.directory_service✕
- Connections
- 1 pair of types, where a type in directory.src.directory_controller uses a type in directory.src.directory_service.
- The types involved
packages.directory.src.directory_controller.DirectoryController→packages.directory.src.directory_service.DirectoryService
- Direction
- directory.src.directory_controller uses directory.src.directory_service, so a change to directory.src.directory_service can break directory.src.directory_controller, while a change to directory.src.directory_controller can't break directory.src.directory_service.
- Position
- Below the diagonal: directory.src.directory_controller uses a module listed above it, which is the healthy direction.
36→1 master.src.controllers.master-data_controller uses core.src.context.invoke✕
- Connections
- 1 pair of types, where a type in master.src.controllers.master-data_controller uses a type in core.src.context.invoke.
- The types involved
packages.master.src.controllers.master-data_controller.MasterDataController→packages.core.src.context.invoke.IInvoke
- Direction
- master.src.controllers.master-data_controller uses core.src.context.invoke, so a change to core.src.context.invoke can break master.src.controllers.master-data_controller, while a change to master.src.controllers.master-data_controller can't break core.src.context.invoke.
- Position
- Below the diagonal: master.src.controllers.master-data_controller uses a module listed above it, which is the healthy direction.
36→16 master.src.controllers.master-data_controller uses core.src.interfaces.detail_dto✕
- Connections
- 1 pair of types, where a type in master.src.controllers.master-data_controller uses a type in core.src.interfaces.detail_dto.
- The types involved
packages.master.src.controllers.master-data_controller.MasterDataController→packages.core.src.interfaces.detail_dto.DetailDto
- Direction
- master.src.controllers.master-data_controller uses core.src.interfaces.detail_dto, so a change to core.src.interfaces.detail_dto can break master.src.controllers.master-data_controller, while a change to master.src.controllers.master-data_controller can't break core.src.interfaces.detail_dto.
- Position
- Below the diagonal: master.src.controllers.master-data_controller uses a module listed above it, which is the healthy direction.
36→31 master.src.controllers.master-data_controller uses master.src.services.master-data_service✕
- Connections
- 1 pair of types, where a type in master.src.controllers.master-data_controller uses a type in master.src.services.master-data_service.
- The types involved
packages.master.src.controllers.master-data_controller.MasterDataController→packages.master.src.services.master-data_service.MasterDataService
- Direction
- master.src.controllers.master-data_controller uses master.src.services.master-data_service, so a change to master.src.services.master-data_service can break master.src.controllers.master-data_controller, while a change to master.src.controllers.master-data_controller can't break master.src.services.master-data_service.
- Position
- Below the diagonal: master.src.controllers.master-data_controller uses a module listed above it, which is the healthy direction.
37→1 master.src.controllers.master-setting_controller uses core.src.context.invoke✕
- Connections
- 1 pair of types, where a type in master.src.controllers.master-setting_controller uses a type in core.src.context.invoke.
- The types involved
packages.master.src.controllers.master-setting_controller.MasterSettingController→packages.core.src.context.invoke.IInvoke
- Direction
- master.src.controllers.master-setting_controller uses core.src.context.invoke, so a change to core.src.context.invoke can break master.src.controllers.master-setting_controller, while a change to master.src.controllers.master-setting_controller can't break core.src.context.invoke.
- Position
- Below the diagonal: master.src.controllers.master-setting_controller uses a module listed above it, which is the healthy direction.
37→16 master.src.controllers.master-setting_controller uses core.src.interfaces.detail_dto✕
- Connections
- 1 pair of types, where a type in master.src.controllers.master-setting_controller uses a type in core.src.interfaces.detail_dto.
- The types involved
packages.master.src.controllers.master-setting_controller.MasterSettingController→packages.core.src.interfaces.detail_dto.DetailDto
- Direction
- master.src.controllers.master-setting_controller uses core.src.interfaces.detail_dto, so a change to core.src.interfaces.detail_dto can break master.src.controllers.master-setting_controller, while a change to master.src.controllers.master-setting_controller can't break core.src.interfaces.detail_dto.
- Position
- Below the diagonal: master.src.controllers.master-setting_controller uses a module listed above it, which is the healthy direction.
37→32 master.src.controllers.master-setting_controller uses master.src.services.master-setting_service✕
- Connections
- 1 pair of types, where a type in master.src.controllers.master-setting_controller uses a type in master.src.services.master-setting_service.
- The types involved
packages.master.src.controllers.master-setting_controller.MasterSettingController→packages.master.src.services.master-setting_service.MasterSettingService
- Direction
- master.src.controllers.master-setting_controller uses master.src.services.master-setting_service, so a change to master.src.services.master-setting_service can break master.src.controllers.master-setting_controller, while a change to master.src.controllers.master-setting_controller can't break master.src.services.master-setting_service.
- Position
- Below the diagonal: master.src.controllers.master-setting_controller uses a module listed above it, which is the healthy direction.
38→1 master.src.handler.master-sfn-task_handler uses core.src.context.invoke✕
- Connections
- 1 pair of types, where a type in master.src.handler.master-sfn-task_handler uses a type in core.src.context.invoke.
- The types involved
packages.master.src.handler.master-sfn-task_handler.MasterSfnTaskEventHandler→packages.core.src.context.invoke.IInvoke
- Direction
- master.src.handler.master-sfn-task_handler uses core.src.context.invoke, so a change to core.src.context.invoke can break master.src.handler.master-sfn-task_handler, while a change to master.src.handler.master-sfn-task_handler can't break core.src.context.invoke.
- Position
- Below the diagonal: master.src.handler.master-sfn-task_handler uses a module listed above it, which is the healthy direction.
38→7 master.src.handler.master-sfn-task_handler uses core.src.interfaces.data-model_interface✕
- Connections
- 1 pair of types, where a type in master.src.handler.master-sfn-task_handler uses a type in core.src.interfaces.data-model_interface.
- The types involved
packages.master.src.handler.master-sfn-task_handler.MasterSfnTaskEventHandler→packages.core.src.interfaces.data-model_interface.DataModel
- Direction
- master.src.handler.master-sfn-task_handler uses core.src.interfaces.data-model_interface, so a change to core.src.interfaces.data-model_interface can break master.src.handler.master-sfn-task_handler, while a change to master.src.handler.master-sfn-task_handler can't break core.src.interfaces.data-model_interface.
- Position
- Below the diagonal: master.src.handler.master-sfn-task_handler uses a module listed above it, which is the healthy direction.
38→9 master.src.handler.master-sfn-task_handler uses core.src.interfaces.event-handler_interface✕
- Connections
- 1 pair of types, where a type in master.src.handler.master-sfn-task_handler uses a type in core.src.interfaces.event-handler_interface.
- The types involved
packages.master.src.handler.master-sfn-task_handler.MasterSfnTaskEventHandler→packages.core.src.interfaces.event-handler_interface.IEventHandler
- Direction
- master.src.handler.master-sfn-task_handler uses core.src.interfaces.event-handler_interface, so a change to core.src.interfaces.event-handler_interface can break master.src.handler.master-sfn-task_handler, while a change to master.src.handler.master-sfn-task_handler can't break core.src.interfaces.event-handler_interface.
- Position
- Below the diagonal: master.src.handler.master-sfn-task_handler uses a module listed above it, which is the healthy direction.
38→13 master.src.handler.master-sfn-task_handler uses core.src.data-store.dynamodb_service✕
- Connections
- 1 pair of types, where a type in master.src.handler.master-sfn-task_handler uses a type in core.src.data-store.dynamodb_service.
- The types involved
packages.master.src.handler.master-sfn-task_handler.MasterSfnTaskEventHandler→packages.core.src.data-store.dynamodb_service.DynamoDbService
- Direction
- master.src.handler.master-sfn-task_handler uses core.src.data-store.dynamodb_service, so a change to core.src.data-store.dynamodb_service can break master.src.handler.master-sfn-task_handler, while a change to master.src.handler.master-sfn-task_handler can't break core.src.data-store.dynamodb_service.
- Position
- Below the diagonal: master.src.handler.master-sfn-task_handler uses a module listed above it, which is the healthy direction.
38→20 master.src.handler.master-sfn-task_handler uses core.src.commands.data_service✕
- Connections
- 1 pair of types, where a type in master.src.handler.master-sfn-task_handler uses a type in core.src.commands.data_service.
- The types involved
packages.master.src.handler.master-sfn-task_handler.MasterSfnTaskEventHandler→packages.core.src.commands.data_service.DataService
- Direction
- master.src.handler.master-sfn-task_handler uses core.src.commands.data_service, so a change to core.src.commands.data_service can break master.src.handler.master-sfn-task_handler, while a change to master.src.handler.master-sfn-task_handler can't break core.src.commands.data_service.
- Position
- Below the diagonal: master.src.handler.master-sfn-task_handler uses a module listed above it, which is the healthy direction.
38→22 master.src.handler.master-sfn-task_handler uses sequence.src.sequences_service✕
- Connections
- 1 pair of types, where a type in master.src.handler.master-sfn-task_handler uses a type in sequence.src.sequences_service.
- The types involved
packages.master.src.handler.master-sfn-task_handler.MasterSfnTaskEventHandler→packages.sequence.src.sequences_service.SequencesService
- Direction
- master.src.handler.master-sfn-task_handler uses sequence.src.sequences_service, so a change to sequence.src.sequences_service can break master.src.handler.master-sfn-task_handler, while a change to master.src.handler.master-sfn-task_handler can't break sequence.src.sequences_service.
- Position
- Below the diagonal: master.src.handler.master-sfn-task_handler uses a module listed above it, which is the healthy direction.
38→31 master.src.handler.master-sfn-task_handler uses master.src.services.master-data_service✕
- Connections
- 1 pair of types, where a type in master.src.handler.master-sfn-task_handler uses a type in master.src.services.master-data_service.
- The types involved
packages.master.src.handler.master-sfn-task_handler.MasterSfnTaskEventHandler→packages.master.src.services.master-data_service.MasterDataService
- Direction
- master.src.handler.master-sfn-task_handler uses master.src.services.master-data_service, so a change to master.src.services.master-data_service can break master.src.handler.master-sfn-task_handler, while a change to master.src.handler.master-sfn-task_handler can't break master.src.services.master-data_service.
- Position
- Below the diagonal: master.src.handler.master-sfn-task_handler uses a module listed above it, which is the healthy direction.
38→32 master.src.handler.master-sfn-task_handler uses master.src.services.master-setting_service✕
- Connections
- 1 pair of types, where a type in master.src.handler.master-sfn-task_handler uses a type in master.src.services.master-setting_service.
- The types involved
packages.master.src.handler.master-sfn-task_handler.MasterSfnTaskEventHandler→packages.master.src.services.master-setting_service.MasterSettingService
- Direction
- master.src.handler.master-sfn-task_handler uses master.src.services.master-setting_service, so a change to master.src.services.master-setting_service can break master.src.handler.master-sfn-task_handler, while a change to master.src.handler.master-sfn-task_handler can't break master.src.services.master-setting_service.
- Position
- Below the diagonal: master.src.handler.master-sfn-task_handler uses a module listed above it, which is the healthy direction.
39→1 survey-template.src.survey-template_controller uses core.src.context.invoke✕
- Connections
- 1 pair of types, where a type in survey-template.src.survey-template_controller uses a type in core.src.context.invoke.
- The types involved
packages.survey-template.src.survey-template_controller.SurveyTemplateController→packages.core.src.context.invoke.IInvoke
- Direction
- survey-template.src.survey-template_controller uses core.src.context.invoke, so a change to core.src.context.invoke can break survey-template.src.survey-template_controller, while a change to survey-template.src.survey-template_controller can't break core.src.context.invoke.
- Position
- Below the diagonal: survey-template.src.survey-template_controller uses a module listed above it, which is the healthy direction.
39→11 survey-template.src.survey-template_controller uses core.src.interfaces.search_dto✕
- Connections
- 1 pair of types, where a type in survey-template.src.survey-template_controller uses a type in core.src.interfaces.search_dto.
- The types involved
packages.survey-template.src.survey-template_controller.SurveyTemplateController→packages.core.src.interfaces.search_dto.SearchDto
- Direction
- survey-template.src.survey-template_controller uses core.src.interfaces.search_dto, so a change to core.src.interfaces.search_dto can break survey-template.src.survey-template_controller, while a change to survey-template.src.survey-template_controller can't break core.src.interfaces.search_dto.
- Position
- Below the diagonal: survey-template.src.survey-template_controller uses a module listed above it, which is the healthy direction.
39→16 survey-template.src.survey-template_controller uses core.src.interfaces.detail_dto✕
- Connections
- 1 pair of types, where a type in survey-template.src.survey-template_controller uses a type in core.src.interfaces.detail_dto.
- The types involved
packages.survey-template.src.survey-template_controller.SurveyTemplateController→packages.core.src.interfaces.detail_dto.DetailDto
- Direction
- survey-template.src.survey-template_controller uses core.src.interfaces.detail_dto, so a change to core.src.interfaces.detail_dto can break survey-template.src.survey-template_controller, while a change to survey-template.src.survey-template_controller can't break core.src.interfaces.detail_dto.
- Position
- Below the diagonal: survey-template.src.survey-template_controller uses a module listed above it, which is the healthy direction.
39→33 survey-template.src.survey-template_controller uses survey-template.src.survey-template_service✕
- Connections
- 1 pair of types, where a type in survey-template.src.survey-template_controller uses a type in survey-template.src.survey-template_service.
- The types involved
packages.survey-template.src.survey-template_controller.SurveyTemplateController→packages.survey-template.src.survey-template_service.SurveyTemplateService
- Direction
- survey-template.src.survey-template_controller uses survey-template.src.survey-template_service, so a change to survey-template.src.survey-template_service can break survey-template.src.survey-template_controller, while a change to survey-template.src.survey-template_controller can't break survey-template.src.survey-template_service.
- Position
- Below the diagonal: survey-template.src.survey-template_controller uses a module listed above it, which is the healthy direction.
40→1 tenant.src.controllers.tenant_controller uses core.src.context.invoke✕
- Connections
- 1 pair of types, where a type in tenant.src.controllers.tenant_controller uses a type in core.src.context.invoke.
- The types involved
packages.tenant.src.controllers.tenant_controller.TenantController→packages.core.src.context.invoke.IInvoke
- Direction
- tenant.src.controllers.tenant_controller uses core.src.context.invoke, so a change to core.src.context.invoke can break tenant.src.controllers.tenant_controller, while a change to tenant.src.controllers.tenant_controller can't break core.src.context.invoke.
- Position
- Below the diagonal: tenant.src.controllers.tenant_controller uses a module listed above it, which is the healthy direction.
40→16 tenant.src.controllers.tenant_controller uses core.src.interfaces.detail_dto✕
- Connections
- 1 pair of types, where a type in tenant.src.controllers.tenant_controller uses a type in core.src.interfaces.detail_dto.
- The types involved
packages.tenant.src.controllers.tenant_controller.TenantController→packages.core.src.interfaces.detail_dto.DetailDto
- Direction
- tenant.src.controllers.tenant_controller uses core.src.interfaces.detail_dto, so a change to core.src.interfaces.detail_dto can break tenant.src.controllers.tenant_controller, while a change to tenant.src.controllers.tenant_controller can't break core.src.interfaces.detail_dto.
- Position
- Below the diagonal: tenant.src.controllers.tenant_controller uses a module listed above it, which is the healthy direction.
40→34 tenant.src.controllers.tenant_controller uses tenant.src.services.tenant_service✕
- Connections
- 1 pair of types, where a type in tenant.src.controllers.tenant_controller uses a type in tenant.src.services.tenant_service.
- The types involved
packages.tenant.src.controllers.tenant_controller.TenantController→packages.tenant.src.services.tenant_service.TenantService
- Direction
- tenant.src.controllers.tenant_controller uses tenant.src.services.tenant_service, so a change to tenant.src.services.tenant_service can break tenant.src.controllers.tenant_controller, while a change to tenant.src.controllers.tenant_controller can't break tenant.src.services.tenant_service.
- Position
- Below the diagonal: tenant.src.controllers.tenant_controller uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Event-Driven
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 154 | High / Critical |
| A05:2025 — Injection | 58 | High / Critical |
| A02:2025 — Security Misconfiguration | 16 | High / Critical |
| A07:2025 — Authentication Failures | 14 | High / Critical |
Roadmap
Top priorities: Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2); Resolve the 101 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (101); Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 2 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2). | +14.6 pts | Low | REDACTED Scanning |
| Resolve the 101 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (101). | +9.6 pts | High | Dependency Hygiene |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +4.8 pts | Medium | 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.8 pts | Medium | DR & Backup |
| 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 1 Flaky test finding(s) in Test Reliability. | +2.3 pts | Low | Test Reliability |
| 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. | +2.1 pts | Medium | Outbound HTTP resilience |
| Bump outdated dependencies to current versions to limit upgrade debt. | +2.1 pts | Medium | Dependency Freshness |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.7 | 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.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 3.2 | Slop | Static Analysis (SAST): High: 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 |
| packages/core/src/data-store/dynamodb.service.ts | 5.7 | Mixed | Cyclomatic Complexity: DynamoDbService.validateAdmissionConditions (cyclomatic 22) |
| 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.5 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
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.
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.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 85 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 85 dimensions across the health lenses
- 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, 751 of 793 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| 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 |
| Canine Code Analyzer 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 |
Run transparency — what happened this run
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `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 — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P8 Schema migrations — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 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 — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 41 further occurrence(s) are not listed individually; the score already reflects all 81.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- 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 our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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.
Dimensions
D1 · Cyclomatic Complexity
11 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was analyze.explainCode at 37. A further 2 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being DynamoDbService.validateAdmissionConditions::isAttribute at 19 — 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.
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.
D2 · Cognitive Complexity
21 method(s) exceeded the cognitive complexity threshold of 15; the worst was analyze.explainCode at 52.
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.
D3 · God Classes
4 god class(es) detected.
What to do
- Resolve the 2 FileTooLong finding(s) in God Classes — start with analyze.ts, directory.service.ts. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 ClassTooLong finding(s) in God Classes — start with directory.service.ts, dynamodb.service.ts. — One of this dimension's main actionable groups (2 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.
D5 · Coupling
13 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.
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.
D6 · Cohesion (LCOM4)
1 of 66 classes have LCOM4 above 3.
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.
D8 · Code Coverage
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/).
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.
D9 · Test Distribution
3809 test methods: 1699 unit, 2088 integration, 0 BDD, 22 e2e. The JavaScript/TypeScript suite contributes 3809 `it`/`test` case(s) across 184 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
2 skipped (2 with a documented reason), 10 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 3809 tests.
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 9 No assertions finding(s) in Test Quality — start with rxjs-schedulers.spec.ts (6), utilities-demo.spec.ts, infra.test.ts. — One of this dimension's main actionable groups (9 warning-level).
- Resolve the 8 Mock-dominated test finding(s) in Test Quality — start with command.event.handler.spec.ts (6), sub-task.queue.event.handler.spec.ts, roles.guard.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.
D11 · Test Reliability
1 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `npm ci --ignore-scripts` in the repository root (3128 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/ (282 tests)): measured (1 flaky).
What to do
- Resolve the 1 Flaky test finding(s) in Test Reliability. — One of this dimension's main actionable groups (1 issue-level).
D12 · Dependency Hygiene
26 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.
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).
D13 · REDACTED Scanning
2 secret(s) detected.
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.
D14 · License Compliance
0 of 639 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 639 package(s) this repository's committed lockfile installs for a consumer — its 49 production, optional and peer dependency(ies), across 12 product package.json manifest(s), and everything those install in turn. Its 156 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ 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.
D15 · Churn × Complexity Hotspots
Top hotspots: packages/cli/templates/infra/libs/infra-stack.ts (2×18=36)
What to do
- 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).
D16 · Bus Factor
27 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 88 of the 511 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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).
D17 · Explicit Debt
6 deducted task-comment markers across 30389 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.
What to do
- Resolve the 6 TodoComment finding(s) in Explicit Debt — start with master-setting.service.ts, publish-async.e2e-spec.ts, event.services.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.
D19 · Documentation Quality
2 of 2 documentation facets pass in full. 23 document(s) read across 12 unit(s).
D20 · ADR Quality
No architecture decision records were 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).
D23 · Boundary Type-Coupling
2 domain type(s) cross context boundaries across 11 contexts; they are measured and withheld (not published, not scored). Contexts: cli, core, directory, import, master, mcp-server, sequence, survey-template, task, tenant, ui-setting.
D24 · Comment Value
57 of 1360 judged comments only repeat the code they sit on (4.2 %). 115 comment(s) in another language or script were not judged.
What to do
- Resolve the 46 redundant comment finding(s) in Comment Value — start with update-scheme.ts (5), module.factory.spec.ts (4), ddb.ts (4). — One of this dimension's main actionable groups (46 recommendation-level).
D26 · Project Cohesion
1 of 13 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
50 % of calls cross a namespace and 3 % go through an interface, but 79 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
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.
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).
D29 · Static Analysis (SAST)
58 finding(s): 0 critical, 31 high, 25 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 40 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, …), … (+35 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.
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).
D30 · Dependency Vulnerabilities
147 finding(s): 27 critical, 63 high, 45 medium, 12 low.
What to do
- Resolve the 53 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (53). — One of this dimension's main actionable groups (53 issue-level).
- Resolve the 27 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (27). — One of this dimension's main actionable groups (27 issue-level).
- Resolve the 10 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
D31 · IaC & Container Security
15 finding(s): 0 critical, 7 high, 6 medium, 2 low.
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).
D34 · Knowledge Freshness
4 of 88 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 88 of the 511 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: master-data.service.ts↔master-setting.service.ts 67%
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).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
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).
D37 · Vulnerability-disclosure Policy
A vulnerability-disclosure policy (REDACTED) is present but lists no reporting contact.
What to do
- Resolve the 1 REDACTED finding(s) in Vulnerability-disclosure Policy — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
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.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
AX8 · Test isolation
C2 · Access Controls
DM9 · Scattered domain decisions
ED3 · Event naming
- `DataSyncNewCommandEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/core/src/command-events/data-sync.new.event.ts:6
- `DataSyncCommandSfnEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/core/src/command-events/data-sync.sfn.event.ts:22
- `NotificationEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/core/src/notifications/event/notification.event.ts:9
- `IMockClassEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. (×2) — packages/core/src/events/mocks/event-handler.mock.ts:4, packages/core/src/services/mocks/event-handler.mock.ts:4
- `IMockOtherClassEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/core/src/events/mocks/other-event-handler.mock.ts:4
- `ImportEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/import/src/event/import.event.ts:14
- `ZipImportSfnEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/import/src/event/zip-import.sfn.event.ts:3
- `ImportQueueEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/import/src/event/import.queue.event.ts:11
- `CsvImportSfnEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/import/src/event/csv-import.sfn.event.ts:22
- `ImportStatusQueueEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/import/src/event/import-status.queue.event.ts:8
- `SubTaskQueueEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/task/src/event/sub-task.queue.event.ts:10
- `StepFunctionTaskEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/task/src/event/task.sfn.event.ts:16
- `TaskEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/task/src/event/task.event.ts:14
- `TaskQueueEvent` reads as an instruction, not a fact that happened. Events describe something that already occurred — name them in the past tense (e.g. `OrderPlaced`, `PaymentCaptured`) so the ubiquitous language stays clear. — packages/task/src/event/task.queue.event.ts:10
What to do
- Name events in the past tense — they record facts that already happened.
GD1 · Unfinished & placeholder code
- 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:78
What to do
- Finish or delete the functions that still throw "not implemented", and replace placeholder text before shipping.
IC1 · Incompleteness & stubs
- `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:78
- `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.
M1 · Documentation (README)
What to do
- Add a README to the 4 of 18 project(s) that lack one — worth up to 0.4 pts.
M2 · Architecture documentation
- 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.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- 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.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P5 · DR & Backup
- 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.
P6 · Release Hygiene
P7 · Outbound HTTP resilience
- `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.
PF3 · Async & latency hygiene
- `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:64, packages/core/test/scripts/start.ts:80
- `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.
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 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:313 · 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:313
- 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.
R2 · Cyclomatic Complexity
- 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
- validateAdmissionConditions has cyclomatic complexity 21 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/core/src/data-store/dynamodb.service.ts:156
- 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
- satisfies has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/cli/src/actions/new.action.template-integrity.spec.ts:8
- 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:266
- (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:467
- 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:114
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
R3 · Large Files
- packages/cli/templates/infra/libs/infra-stack.ts has 1311 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 590 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/core/src/data-store/dynamodb.service.ts has 567 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
- 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 426 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/mcp-server/src/prompts/cqrs-guide.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
- 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).
R5 · Dependency Freshness
- 70 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Unreachable from the 41 application, 15 tooling and 200 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 (41 application, 15 tooling, 200 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 (41 application, 15 tooling, 200 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 (41 application, 15 tooling, 200 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 (41 application, 15 tooling, 200 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
- no import path from any entry point (41 application, 15 tooling, 200 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (packages/master/src/templates/master/helpers/id.ts, 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 — packages/master/src/templates/master/helpers/key.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- 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.
R9 · Circular Imports
- 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.
S1 · Web-Security Posture
- `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`.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `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.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
- Only 0/2 async functions that make a cancellable request (fetch, axios, ky, ofetch, got, undici, node:http) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
- `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
- `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
What to do
- Thread an AbortSignal through async functions that make requests, so the work stops when its caller gives up.
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
- `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
- `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
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.
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- 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/tenant/src/update-scheme.ts:28, packages/master/src/update-scheme.ts:33, packages/master/src/update-scheme.ts:144, …
- `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:444
- `.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, …
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 2/19 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 31958 source line(s) of the 512 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 `?`).
Reference — by lens
| 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 | 80% | Strong | Strongest area. |
| Readiness | 30% | Weak — gated by D13, R5, R8, P5, P7 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 66% | Adequate — gated by D28, D29, D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 60% | Adequate | Acceptable, with room to improve. |
Unscored — 3 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- 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 — 52 check(s) not relevant to this codebase
- 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 (`npm run dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. 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.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D25 ADR Conformance — no ADRs to check
- 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
- ED5 Idempotency — 18 mutating command handler(s)/consumer(s) detected and 26 handler method(s) walked, but no persistent write was recognised in any of them — idempotency not assessed
- 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 scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- 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)
Critical — 171 finding(s)
- 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
- 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
- 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
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@nestjs/common' packages/cli/schematics/lib/controller/files/__name@dasherize__.controller.ts:1
- Unlisted import '@nestjs/common' packages/directory/src/directory-file.service.ts:9
- Unlisted import '@nestjs/common' packages/import/src/event/command-finished.queue.event.handler.ts:9
- Unlisted import '@nestjs/common' packages/master/src/controllers/master-bulk.controller.spec.ts:2
- Unlisted import '@nestjs/common' packages/sequence/src/sequence-master-factory.ts:7
- Unlisted import '@nestjs/swagger' packages/cli/schematics/lib/controller/files/__name@dasherize__.controller.ts:2
- Unlisted import '@nestjs/swagger' packages/directory/src/directory.controller.ts:15
- Unlisted import '@nestjs/swagger' packages/import/src/import.controller.ts:12
- Unlisted import '@nestjs/swagger' packages/master/src/controllers/master-bulk.controller.ts:7
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@nestjs/config' packages/directory/src/directory.module.spec.ts:3
- Unlisted import '@nestjs/config' packages/import/src/event/csv-import.queue.event.handler.spec.ts:3
- Unlisted import '@nestjs/config' packages/master/src/master.module.spec.ts:4
- Unlisted import 'class-validator' packages/directory/src/dto/directory-attributes.dto.ts:3
- Unlisted import 'class-validator' packages/import/src/dto/create-csv-import.dto.ts:1
- Unlisted import 'class-validator' packages/master/src/decorators/key.ts:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'class-transformer' packages/directory/src/dto/directory-attributes.dto.ts:2
- Unlisted import 'class-transformer' packages/master/src/decorators/key.ts:7
- Import cycle (3 files) packages/import/src/event/command-finished.queue.event.handler.ts:14
- Import cycle (3 files) packages/task/src/event/index.ts:2
- Assertions commented out: should preserve design:type for properties packages/core/src/integration/reflect-metadata-behavior.spec.ts:381
- Flaky test: the repository rootpackages/master/src/integration/ulid.spec.ts::ulid Integration Tests Performance Characteristics should generate ULIDs quickly
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@aws-sdk/credential-provider-env' packages/core/src/integration/aws-credential-provider-behavior.spec.ts:12
- Unlisted import '@smithy/protocol-http' packages/core/src/integration/aws-signature-v4-behavior.spec.ts:13
- Unlisted import '@smithy/signature-v4' REDACTED:8
- Unlisted import 'dotenv' packages/core/test/e2e/config.ts:1
- Unlisted import 'express' packages/core/src/bootstrap.ts:9
- Unlisted import 'rxjs' packages/core/src/bootstrap.ts:10
- Unlisted import 'ulid' packages/import/src/import.service.ts:23
- Unlisted import 'lodash' packages/master/src/handler/master-sfn-task.handler.ts:13
- Import cycle (2 files) packages/core/src/interfaces/index.ts:9
Serious — 356 finding(s)
- 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
- No test reaches this file packages/master/src/update-scheme.ts:1
- No test reaches this file packages/cli/schematics/lib/module/module.factory.ts:1
- No test reaches this file packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts:1
- No test reaches this file packages/cli/schematics/lib/module/files/sync/__name@dasherize__.service.ts:1
- No test reaches this file packages/import/src/import.module.ts:1
- No test reaches this file packages/import/src/import.controller.ts:1
- No test reaches this file packages/mcp-server/test-mcp.js:1
- No test reaches this file REDACTED:1
- No test reaches this file packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:1
- No test reaches this file packages/cli/schematics/lib/module/files/sync/__name@dasherize__.controller.ts:1
- No test reaches this file packages/master/src/templates/master/handler/master-rds.handler.ts:1
- No test reaches this file packages/cli/schematics/lib/controller/controller.factory.ts:1
- No test reaches this file packages/cli/schematics/lib/module/files/async/handler/__name@dasherize__-rds.handler.ts:1
- No test reaches this file packages/cli/schematics/lib/module/files/sync/handler/__name@dasherize__-rds.handler.ts:1
- No test reaches this file packages/cli/schematics/lib/service/service.factory.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file packages/cli/schematics/lib/dto/dto.factory.ts:1
- No test reaches this file packages/cli/schematics/lib/entity/entity.factory.ts:1
- No test reaches this file packages/sequence/src/sequence.module.ts:1
- No test reaches this file packages/master/src/templates/master/helpers/id.ts:1
- No test reaches this file packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts:1
- No test reaches this file packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-update.dto.ts:1
- No test reaches this file packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-update.dto.ts:1
- No test reaches this file packages/tenant/src/update-scheme.ts:1
- No test reaches this file packages/cli/schematics/lib/controller/units/__name@dasherize__.controller.__specFileSuffix__.ts:1
- Sync-over-async blocking packages/cli/src/actions/install-skills.action.ts:279
- Sync-over-async blocking packages/cli/src/actions/install-skills.action.ts:331
- Sync-over-async blocking packages/cli/src/actions/install-skills.action.ts:332
- Sync-over-async blocking REDACTED:58
- Sync-over-async blocking REDACTED:65
- Sync-over-async blocking REDACTED:66
- Sync-over-async blocking REDACTED:69
- Sync-over-async blocking REDACTED:70
- Sync-over-async blocking REDACTED:78
- Sync-over-async blocking REDACTED:83
- Sync-over-async blocking REDACTED:89
- Sync-over-async blocking REDACTED:90
- Sync-over-async blocking packages/cli/src/actions/ui.action.ts:32
- Sync-over-async blocking packages/cli/src/actions/ui.action.ts:39
- Sync-over-async blocking packages/cli/src/actions/ui.action.ts:71
- Sync-over-async blocking packages/cli/src/actions/ui.action.ts:84
- Sync-over-async blocking packages/core/src/bootstrap.ts:83
- Sync-over-async blocking packages/core/test/scripts/start.ts:64
- Sync-over-async blocking packages/core/test/scripts/start.ts:80
- Sync-over-async blocking packages/mcp-server/src/resources/project.ts:106
- Sync-over-async blocking packages/mcp-server/src/resources/project.ts:126
- Sync-over-async blocking packages/mcp-server/src/resources/project.ts:131
- Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts:219
- Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts:245
- Sync-over-async blocking packages/mcp-server/src/tools/analyze.ts:341
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Dead file (~12 LoC) packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-command.entity.ts
- Dead file (~12 LoC) packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-data-list.entity.ts
- Dead file (~12 LoC) packages/cli/schematics/lib/entity/files/entity/__name@dasherize__-data.entity.ts
- Dead file (~12 LoC) packages/cli/schematics/lib/module/files/async/entity/__name@dasherize__-command.entity.ts
- Dead file (~12 LoC) packages/cli/schematics/lib/module/files/async/entity/__name@dasherize__-data-list.entity.ts
- Dead file (~12 LoC) packages/cli/schematics/lib/module/files/async/entity/__name@dasherize__-data.entity.ts
- Dead file (~12 LoC) packages/cli/schematics/lib/module/files/sync/entity/__name@dasherize__-command.entity.ts
- Dead file (~12 LoC) packages/cli/schematics/lib/module/files/sync/entity/__name@dasherize__-data-list.entity.ts
- Dead file (~12 LoC) packages/cli/schematics/lib/module/files/sync/entity/__name@dasherize__-data.entity.ts
- Dead file (~12 LoC) packages/directory/src/entity/directory-command.entity.ts
- Swallowed exception (empty catch) packages/tenant/src/update-scheme.ts:28
- Swallowed exception (empty catch) packages/master/src/update-scheme.ts:33
- Swallowed exception (empty catch) packages/master/src/update-scheme.ts:144
- Swallowed exception (empty catch) packages/master/src/update-scheme.ts:329
- Swallowed exception (empty catch) packages/core/src/commands/repository.ts:104
- Swallowed exception (empty catch) packages/core/src/commands/repository.ts:203
- Swallowed exception (empty catch) packages/core/src/commands/repository.ts:356
- Swallowed exception (empty catch) packages/core/src/commands/repository.ts:368
- Swallowed exception (empty catch) packages/cli/src/actions/install-skills.action.ts:74
- Swallowed exception (empty catch) packages/cli/src/actions/install-skills.action.ts:205
- No assertions: should support marble testing packages/core/src/integration/rxjs-schedulers.spec.ts:358
- No assertions: should test delays with virtual time packages/core/src/integration/rxjs-schedulers.spec.ts:367
- No assertions: should test interval with take packages/core/src/integration/rxjs-schedulers.spec.ts:378
- No assertions: should test error scenarios packages/core/src/integration/rxjs-schedulers.spec.ts:387
- No assertions: should test hot observables packages/core/src/integration/rxjs-schedulers.spec.ts:396
- No assertions: should test subscription timing packages/core/src/integration/rxjs-schedulers.spec.ts:406
- No assertions: should classify ${name} as ${retriable ? 'retriable' : 'non-retriable'} packages/core/src/integration/utilities-demo.spec.ts:211
- No assertions: lambda-api SendTaskSuccess is scoped to command-handler state machine packages/cli/templates/infra/test/infra.test.ts:111
- No assertions: accepts %s without making a request examples/command-admission/local-dynamodb.spec.ts:18
- Fake-async — async method never awaits packages/cli/src/actions/generate.action.ts:9
- Fake-async — async method never awaits packages/cli/src/actions/install-skills.action.ts:257
- Fake-async — async method never awaits REDACTED:18
- Fake-async — async method never awaits packages/cli/src/actions/start.action.ts:2
- Fake-async — async method never awaits packages/cli/src/actions/ui.action.ts:14
- Fake-async — async method never awaits packages/cli/src/commands/generate.command.ts:6
- Fake-async — async method never awaits packages/master/src/update-scheme.ts:15
- Fake-async — async method never awaits packages/master/src/update-scheme.ts:56
- TodoComment packages/master/src/services/master-setting.service.ts:108
- TodoComment packages/core/test/e2e/publish-async.e2e-spec.ts:218
- TodoComment packages/core/src/events/event.services.ts:45
- TodoComment packages/core/src/commands/tenant-normalization.spec.ts:197
- TodoComment packages/core/src/command-events/data-sync.sfn.event.ts:69
- TodoComment packages/cli/src/actions/start.action.ts:4
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Low coverage: packages/mcp-server/src/index.ts packages/mcp-server/src/index.ts:1
- Low coverage: packages/mcp-server/src/server.ts packages/mcp-server/src/server.ts:1
- Low coverage: packages/mcp-server/src/resources/documentation.ts packages/mcp-server/src/resources/documentation.ts:1
- Low coverage: packages/mcp-server/src/tools/generate.ts packages/mcp-server/src/tools/generate.ts:1
- Low coverage: packages/mcp-server/src/tools/generator.ts packages/mcp-server/src/tools/generator.ts:1
- Duplicated block (20 lines × 2 locations) packages/directory/src/directory.service.ts:234
- Duplicated block (20 lines × 2 locations) packages/import/src/import.service.ts:118
- Duplicated block (20 lines × 2 locations) packages/master/src/master.module.ts:94
- Duplicated block (20 lines × 2 locations) packages/task/src/event/sub-task.queue.event.ts:10
- Duplicated block (20 lines × 2 locations) packages/task/src/task.service.ts:211
- Dead file (~62 LoC) packages/cli/schematics/lib/controller/controller.factory.ts
- Dead file (~62 LoC) packages/cli/schematics/lib/module/files/async/handler/__name@dasherize__-rds.handler.ts
- Dead file (~62 LoC) packages/cli/schematics/lib/module/files/sync/handler/__name@dasherize__-rds.handler.ts
- Dead file (~62 LoC) packages/cli/schematics/lib/service/service.factory.ts
- REDACTED
- REDACTED
- REDACTED
- Outbound HTTP without resilience REDACTED:121
- Outbound HTTP without resilience packages/core/src/notifications/appsync.service.ts:72
- Outbound HTTP without resilience packages/core/src/notifications/appsync.service.ts:91
- Duplicated block (23 lines × 2 locations) packages/directory/src/directory.module.ts:47
- Duplicated block (23 lines × 2 locations) packages/directory/src/directory.service.ts:786
- Duplicated block (23 lines × 2 locations) packages/master/src/helpers/index.ts:14
- Dead file (~34 LoC) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts
- Dead file (~34 LoC) packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-update.dto.ts
- Dead file (~34 LoC) packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-update.dto.ts
- Dead file (~19 LoC) packages/cli/schematics/lib/module/files/async/__name@dasherize__.module.ts
- Dead file (~19 LoC) packages/cli/schematics/lib/module/files/sync/__name@dasherize__.module.ts
- Dead file (~19 LoC) packages/master/src/templates/master/helpers/get-order.ts
- Dead file (~18 LoC) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-create.dto.ts
- Dead file (~18 LoC) packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-create.dto.ts
- Dead file (~18 LoC) packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-create.dto.ts
- Dead file (~16 LoC) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-command.dto.ts
- Dead file (~16 LoC) packages/cli/schematics/lib/module/files/async/dto/__name@dasherize__-command.dto.ts
- Dead file (~16 LoC) packages/cli/schematics/lib/module/files/sync/dto/__name@dasherize__-command.dto.ts
- Dead file (~11 LoC) packages/cli/schematics/utils/check-files-exist.ts
- Dead file (~11 LoC) packages/master/src/templates/master/entity/master-data.entity.ts
- Dead file (~11 LoC) packages/master/src/templates/master/helpers/key.ts
- Deprecated: @aws-sdk/signature-v4 package.json:53
- Deprecated: eslint package.json:71
- REDACTED
- REDACTED
- FileTooLong: tools/analyze.ts packages/mcp-server/src/tools/analyze.ts
- FileTooLong: src/directory.service.ts packages/directory/src/directory.service.ts
- ClassTooLong: DirectoryService packages/directory/src/directory.service.ts:57
- ClassTooLong: DynamoDbService packages/core/src/data-store/dynamodb.service.ts:44
- Duplicated block (43 lines × 2 locations) packages/cli/schematics/lib/controller/controller.factory.ts:16
- Duplicated block (43 lines × 2 locations) packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:26
- Duplicated block (41 lines × 2 locations) packages/core/src/interfaces/command.entity.ts:13
- Duplicated block (41 lines × 2 locations) packages/import/src/event/import.event.ts:14
- Duplicated block (29 lines × 2 locations) packages/master/src/services/master-setting.service.ts:231
- Duplicated block (29 lines × 2 locations) packages/ui-setting/src/controllers/data-setting.controller.ts:43
- Duplicated block (21 lines × 2 locations) packages/master/src/master.module.ts:64
- Duplicated block (21 lines × 2 locations) packages/ui-setting/src/setting.module.ts:26
- Dead file (~164 LoC) packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts
- Dead file (~164 LoC) packages/cli/schematics/lib/module/files/sync/__name@dasherize__.service.ts
- Dead file (~74 LoC) packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts
- Dead file (~74 LoC) packages/cli/schematics/lib/module/files/sync/__name@dasherize__.controller.ts
- Async function without AbortSignal: postToChannel REDACTED:115
- Async function without AbortSignal: sendMessage packages/core/src/notifications/appsync.service.ts:52
- 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
- DynamoDbService.validateAdmissionConditions (cyclomatic 22) packages/core/src/data-store/dynamodb.service.ts:156
- analyze.healthCheck (cyclomatic 21) packages/mcp-server/src/tools/analyze.ts:1008
- analyze.analyzeProject (cyclomatic 20) packages/mcp-server/src/tools/analyze.ts:196
- analyze.checkAntiPatterns (cyclomatic 19) packages/mcp-server/src/tools/analyze.ts:884
- validate.validateCqrsPatterns (cyclomatic 19) packages/mcp-server/src/tools/validate.ts:78
- Repository.listItemsByPk (cyclomatic 18) packages/core/src/commands/repository.ts:141
- install-skills.action.installSkillsAction (cyclomatic 17) packages/cli/src/actions/install-skills.action.ts:257
- EmailService.sendInlineTemplateEmail (cyclomatic 17) packages/core/src/notifications/email.service.ts:114
- Hotspot: packages/cli/templates/infra/libs/infra-stack.ts packages/cli/templates/infra/libs/infra-stack.ts:39
- 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:467
- analyze.checkAntiPatterns (cognitive 33) packages/mcp-server/src/tools/analyze.ts:884
- Repository.listItemsByPk (cognitive 28) packages/core/src/commands/repository.ts:141
- validate.validateCqrsPatterns (cognitive 23) packages/mcp-server/src/tools/validate.ts:78
- CsvImportSfnEventHandler.getResultsFromS3Writer (cognitive 22) packages/import/src/event/csv-import.sfn.event.handler.ts:313
- CsvBatchProcessor.process (cognitive 22) packages/import/src/event/processor/csv-batch.processor.ts:29
- install-skills.action.installSkillsAction (cognitive 21) packages/cli/src/actions/install-skills.action.ts:257
- analyze.checkDuplicateDataSyncHandlerRegistrations (cognitive 21) packages/mcp-server/src/tools/analyze.ts:806
- validate.formatValidationResult (cognitive 21) packages/mcp-server/src/tools/validate.ts:191
- DynamoDbService.validateAdmissionConditions (cognitive 20) packages/core/src/data-store/dynamodb.service.ts:156
- ui.action.getModifyPackage (cognitive 18) packages/cli/src/actions/ui.action.ts:160
- CommandEventHandler.waitConfirmToken (cognitive 18) packages/core/src/commands/command.event.handler.ts:106
- update-scheme.formatTemplate (cognitive 18) packages/master/src/update-scheme.ts:181
- EmailService.sendInlineTemplateEmail (cognitive 17) packages/core/src/notifications/email.service.ts:114
- CsvImportSfnEventHandler.handleStepState::sendBatchToSqs (cognitive 17) packages/import/src/event/csv-import.sfn.event.handler.ts:134
- CsvImportSfnEventHandler.handleStepState (cognitive 17) packages/import/src/event/csv-import.sfn.event.handler.ts:61
- analyze.formatAnalysisResult (cognitive 16) packages/mcp-server/src/tools/analyze.ts:388
- REDACTED
- Change coupling: master-data.service.ts ↔ master-setting.service.ts packages/master/src/services/master-data.service.ts:1
- REDACTED
- REDACTED
- Off the main sequence: @mbc-cqrs-serverless/core
- Low cohesion: DynamoDbService (LCOM4 5) packages/core/src/data-store/dynamodb.service.ts:44
- Unfinished stub — throws a "not implemented" error packages/core/src/commands/command.service.ts:78
- Unfinished stub — throws a "not implemented" exception packages/core/src/commands/command.service.ts:78
- No DR/backup evidence
- Forked directory tree (11 identical files, ~267 lines × 2 trees) packages/cli/schematics/lib/module/files/async/__name@dasherize__.controller.ts:1
- Duplication concentrated across 10 sibling directories (53 clone groups) packages/master/src/services/master-data.service.ts:186
- Duplication concentrated across 5 sibling directories (10 clone groups) packages/cli/schematics/lib/controller/controller.factory.ts:16
- Duplicated block with local edits (105 matched lines × 2 locations) packages/ui-setting/src/services/data-setting.service.ts:35
- Wholesale file copy (100 identical lines × 2 files) packages/cli/schematics/lib/module/files/async/__name@dasherize__.service.ts:11
- Duplicated block with local edits (71 matched lines × 2 locations) packages/master/src/services/master-data.service.ts:186
- Duplicated block with local edits (65 matched lines × 2 locations) packages/master/src/controllers/master-data.controller.ts:61
- Duplicated block (63 lines × 2 locations) packages/sequence/src/sequences.service.ts:80
- Duplicated block with local edits (57 matched lines × 2 locations) packages/core/src/data-store/dynamodb.service.ts:313
- Duplicated block with local edits (43 matched lines × 2 locations) packages/core/src/commands/repository.ts:171
- Duplicated block (42 lines × 2 locations) packages/cli/schematics/lib/module/files/async/handler/__name@dasherize__-rds.handler.ts:17
- Duplicated block with local edits (40 matched lines × 2 locations) packages/master/src/services/master-data.service.ts:299
- Duplicated block (38 lines × 2 locations) packages/task/src/task.service.ts:38
- Duplicated block (33 lines × 2 locations) packages/master/src/dto/master-setting/group-setting-create.dto.ts:4
- Duplicated block (32 lines × 2 locations) packages/directory/src/directory.service.ts:604
- Duplicated block (29 lines × 3 locations) packages/master/src/dto/master-setting/group-setting-create.dto.ts:2
- Duplicated block (27 lines × 2 locations) packages/directory/src/directory.service.ts:401
- Duplicated block (26 lines × 2 locations) packages/cli/schematics/lib/dto/dto.factory.ts:17
- Duplicated block (25 lines × 2 locations) packages/import/src/import.service.ts:609
- Duplicated block (24 lines × 2 locations) packages/core/src/commands/data.service.ts:17
- Duplicated block with local edits (21 matched lines × 2 locations) packages/import/src/event/processor/csv-batch.processor.ts:62
- Duplicated block with local edits (20 matched lines × 2 locations) packages/task/src/event/task.queue.event.handler.ts:36
- Duplicated block (20 lines × 3 locations) packages/task/src/task.service.ts:185
- Duplicated block (19 lines × 3 locations) packages/cli/schematics/lib/dto/files/dto/__name@dasherize__-update.dto.ts:12
- Complex function explainCode (cyclomatic 37, cognitive 52) packages/mcp-server/src/tools/analyze.ts:1190
- Complex function healthCheck (cyclomatic 21, cognitive 43) packages/mcp-server/src/tools/analyze.ts:1008
- Complex function validateAdmissionConditions (cyclomatic 21, cognitive 15) packages/core/src/data-store/dynamodb.service.ts:156
- Complex function analyzeProject (cyclomatic 20, cognitive 37) packages/mcp-server/src/tools/analyze.ts:196
- Complex function checkAntiPatterns (cyclomatic 19, cognitive 30) packages/mcp-server/src/tools/analyze.ts:884
- Complex function validateCqrsPatterns (cyclomatic 19, cognitive 23) packages/mcp-server/src/tools/validate.ts:78
- Complex function listItemsByPk (cyclomatic 17, cognitive 27) packages/core/src/commands/repository.ts:141
- Complex function installSkillsAction (cyclomatic 17, cognitive 21) packages/cli/src/actions/install-skills.action.ts:257
- Complex function satisfies (cyclomatic 17, cognitive 15) packages/cli/src/actions/new.action.template-integrity.spec.ts:8
- Complex function publishSync (cyclomatic 16, cognitive 18) packages/core/src/commands/command.service.ts:266
- Complex function (anonymous) (cyclomatic 16, cognitive 18) packages/core/src/commands/repository.ts:325
- Complex function buildUpdateSetExpression (cyclomatic 15, cognitive 33) packages/core/src/data-store/dynamodb.service.ts:467
- Complex function listItems (cyclomatic 15, cognitive 21) packages/core/src/commands/repository.ts:285
- Complex function (top-level) (cyclomatic 13, cognitive 15) packages/import/src/event/import-status.queue.event.handler.ts:1
- Complex function sendInlineTemplateEmail (cyclomatic 13, cognitive 13) packages/core/src/notifications/email.service.ts:114
- packages/cli/templates/infra/libs/infra-stack.ts: 1311 lines of code packages/cli/templates/infra/libs/infra-stack.ts:1
- packages/mcp-server/src/tools/analyze.ts: 1268 lines of code packages/mcp-server/src/tools/analyze.ts:1
- packages/directory/src/directory.service.ts: 758 lines of code packages/directory/src/directory.service.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/commands/command.service.ts: 590 lines of code packages/core/src/commands/command.service.ts:1
- packages/import/src/import.service.ts: 574 lines of code packages/import/src/import.service.ts:1
- packages/core/src/data-store/dynamodb.service.ts: 567 lines of code packages/core/src/data-store/dynamodb.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/core/src/commands/command.event.handler.ts: 460 lines of code packages/core/src/commands/command.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/core/src/integration/utilities/test-data-builders.ts: 429 lines of code packages/core/src/integration/utilities/test-data-builders.ts:1
- packages/mcp-server/src/prompts/cqrs-guide.ts: 426 lines of code packages/mcp-server/src/prompts/cqrs-guide.ts:1
- Dependency Freshness
- Dead file (~238 LoC) packages/cli/schematics/lib/module/module.factory.ts
- Dead file (~47 LoC) packages/cli/schematics/lib/dto/dto.factory.ts
- Dead file (~45 LoC) packages/cli/schematics/lib/entity/entity.factory.ts
- Dead file (~42 LoC) packages/master/src/templates/master/helpers/id.ts
- Dead file (~14 LoC) packages/tenant/src/entities/setting-list.entity.ts
- Dead file (~13 LoC) packages/master/src/templates/master/entity/master-data-list.entity.ts
- Unused dependency '@schematics/angular'
- Unused dependency 'nestjs-spelunker'
- Unused dependency 'serverless-dynamodb'
- JavaScript dependencies are not locked examples/appsync-event-client/package.json:11
- Recursive walk over a caller-supplied document has no depth cap packages/core/src/helpers/object.ts:14
- Swallowed exception (caught, then discarded) packages/core/src/commands/command.service.ts:444
Minor — 244 finding(s)
- Deprecated: @hapi/address REDACTED:3667
- Deprecated: @humanwhocodes/config-array REDACTED:4012
- Deprecated: @humanwhocodes/object-schema REDACTED:4063
- Deprecated: glob REDACTED:4878
- Deprecated: @koa/router REDACTED:5090
- Deprecated: glob REDACTED:6829
- Deprecated: accept REDACTED:10134
- Deprecated: boom REDACTED:10148
- Deprecated: hoek REDACTED:10161
- Deprecated: ammo REDACTED:10393
- Deprecated: boom REDACTED:10407
- Deprecated: hoek REDACTED:10420
- Deprecated: glob REDACTED:10624
- Deprecated: querystring REDACTED:11087
- Deprecated: b64 REDACTED:11191
- Deprecated: boom REDACTED:11523
- Deprecated: bourne REDACTED:11533
- Deprecated: call REDACTED:12042
- Deprecated: boom REDACTED:12100
- Deprecated: hoek REDACTED:12113
- Deprecated: catbox REDACTED:12180
- Deprecated: catbox-memory REDACTED:12195
- Deprecated: hoek REDACTED:12208
- Deprecated: boom REDACTED:12218
- Deprecated: hoek REDACTED:12231
- redundant comment packages/cli/schematics/lib/module/module.factory.spec.ts:87
- redundant comment packages/cli/schematics/lib/module/module.factory.spec.ts:175
- redundant comment packages/cli/schematics/lib/module/module.factory.spec.ts:263
- redundant comment packages/cli/schematics/lib/module/module.factory.spec.ts:351
- redundant comment packages/cli/src/actions/new.action.spec.ts:25
- redundant comment REDACTED:71
- redundant comment REDACTED:41
- redundant comment REDACTED:45
- redundant comment packages/cli/templates/infra/libs/infra-stack.ts:59
- redundant comment packages/cli/templates/prisma/ddb.ts:41
- redundant comment packages/cli/templates/prisma/ddb.ts:43
- redundant comment packages/core/src/commands/repository.ts:236
- redundant comment packages/core/src/config/service-config.spec.ts:208
- redundant comment packages/core/src/context/backward-compatibility.spec.ts:334
- redundant comment packages/core/src/guard/roles.guard.spec.ts:682
- redundant comment packages/core/src/guard/roles.guard.ts:96
- redundant comment packages/core/src/integration/aws-s3-advanced.spec.ts:92
- redundant comment packages/core/src/integration/breaking-change-detection.spec.ts:150
- redundant comment REDACTED:798
- redundant comment packages/core/src/integration/large-data-handling.spec.ts:128
- redundant comment packages/core/src/integration/smithy-stream.spec.ts:349
- redundant comment packages/core/src/integration/utilities/index.ts:46
- redundant comment packages/core/src/notifications/email.service.spec.ts:52
- redundant comment packages/core/test/prisma/ddb.ts:40
- redundant comment packages/core/test/prisma/ddb.ts:42
- Console output used as the logging channel packages/core/src/bootstrap.ts:93
- Console output used as the logging channel packages/core/src/bootstrap.ts:98
- Console output used as the logging channel packages/core/src/services/request-logger.service.ts:30
- Console output used as the logging channel packages/mcp-server/src/server.ts:64
- Console output used as the logging channel packages/mcp-server/src/server.ts:76
- Console output used as the logging channel packages/mcp-server/src/server.ts:90
- Console output used as the logging channel packages/mcp-server/src/server.ts:106
- Console output used as the logging channel packages/mcp-server/src/server.ts:122
- Console output used as the logging channel packages/mcp-server/src/server.ts:137
- Console output used as the logging channel packages/mcp-server/src/server.ts:152
- Console output used as the logging channel packages/mcp-server/src/server.ts:164
- Console output used as the logging channel packages/mcp-server/src/prompts/cqrs-guide.ts:397
- Console output used as the logging channel packages/mcp-server/src/prompts/cqrs-guide.ts:403
- Console output used as the logging channel packages/mcp-server/src/prompts/cqrs-guide.ts:409
- Console output used as the logging channel packages/mcp-server/src/prompts/cqrs-guide.ts:411
- Console output used as the logging channel packages/task/src/event/sub-task.queue.event.handler.ts:27
- Console output used as the logging channel packages/task/src/event/sub-task.queue.event.handler.ts:31
- Event not named in past tense: DataSyncNewCommandEvent packages/core/src/command-events/data-sync.new.event.ts:6
- Event not named in past tense: DataSyncCommandSfnEvent packages/core/src/command-events/data-sync.sfn.event.ts:22
- Event not named in past tense: NotificationEvent packages/core/src/notifications/event/notification.event.ts:9
- Event not named in past tense: IMockClassEvent packages/core/src/events/mocks/event-handler.mock.ts:4
- Event not named in past tense: IMockOtherClassEvent packages/core/src/events/mocks/other-event-handler.mock.ts:4
- Event not named in past tense: IMockClassEvent packages/core/src/services/mocks/event-handler.mock.ts:4
- Event not named in past tense: ImportEvent packages/import/src/event/import.event.ts:14
- Event not named in past tense: ZipImportSfnEvent packages/import/src/event/zip-import.sfn.event.ts:3
- Event not named in past tense: ImportQueueEvent packages/import/src/event/import.queue.event.ts:11
- Event not named in past tense: CsvImportSfnEvent packages/import/src/event/csv-import.sfn.event.ts:22
- Event not named in past tense: ImportStatusQueueEvent packages/import/src/event/import-status.queue.event.ts:8
- Event not named in past tense: SubTaskQueueEvent packages/task/src/event/sub-task.queue.event.ts:10
- Event not named in past tense: StepFunctionTaskEvent packages/task/src/event/task.sfn.event.ts:16
- Event not named in past tense: TaskEvent packages/task/src/event/task.event.ts:14
- Event not named in past tense: TaskQueueEvent packages/task/src/event/task.queue.event.ts:10
- Outdated (npm): @angular-devkit/core package.json:157
- Outdated (npm): @angular-devkit/schematics packages/cli/package.json:48
- Outdated (npm): @angular-devkit/schematics-cli packages/cli/package.json:49
- Outdated (npm): @nestjs/config packages/core/package.json:57
- Outdated (npm): @nestjs/mapped-types packages/core/package.json:59
- Outdated (npm): @nestjs/swagger packages/cli/templates/package.json:54
- Outdated (npm): @schematics/angular packages/cli/package.json:50
- Outdated (npm): commander packages/cli/package.json:53
- Outdated (npm): prisma packages/cli/templates/package.json:45
- Mock-dominated test: should execute the sub task queue event handler packages/task/src/event/sub-task.queue.event.handler.spec.ts:100
- Mock-dominated test: should pass JWT claims to resolveRoles packages/core/src/guard/roles.guard.spec.ts:1199
- Mock-dominated test: should resume next command when getNextCommand finds a taskToken packages/core/src/commands/command.event.handler.spec.ts:1013
- Mock-dominated test: should retry getNextCommand and resume when a later attempt succeeds packages/core/src/commands/command.event.handler.spec.ts:1140
- Mock-dominated test: should not resume when predecessor is finish:FAILED packages/core/src/commands/command.event.handler.spec.ts:1283
- Mock-dominated test: should not resume when predecessor is not finish:FINISHED packages/core/src/commands/command.event.handler.spec.ts:1312
- 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
- Mock-dominated test: should not lookup predecessor when version is 1 packages/core/src/commands/command.event.handler.spec.ts:1398
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Orphaned file packages/tenant/src/interfaces/tenant.service.interface.ts:1
- Orphaned file packages/core/src/services/request-logger.service.ts:1
- Orphaned file packages/core/src/events/event-bus.ts:1
- Orphaned file packages/core/src/command-events/data-sync.sfn.event.ts:1
- Duplicated predicate packages/master/src/controllers/master-bulk.controller.ts:38
- Duplicated predicate packages/master/src/helpers/index.ts:43
- Duplicated predicate packages/core/src/command-events/data-sync.new.event.handler.ts:58
- Duplicated predicate packages/master/src/services/master-data.service.ts:92
- Diagnostic log message is built whether or not it is wanted packages/master/src/services/master-setting.service.ts:534
- Diagnostic log message is built whether or not it is wanted REDACTED:17
- Diagnostic log message is built whether or not it is wanted packages/core/src/notifications/event/notification.event.handler.ts:57
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Further sole-owners (lower concentration)
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- Logging is not universal
- Test-only dependency '@nestjs/mapped-types' in production deps packages/core/package.json:59
- No app-layer HTTPS enforcement detected packages/core/src/bootstrap.ts:102
- Not all async functions that make a request accept an AbortSignal
- Strict null checking is not enabled everywhere the repository type-checks
- Null assertions (`!`) reduce the strict null checking score
- Silent fallback default in catch packages/core/src/context/user.ts:37
Minor — 22 finding(s)
- Outdated (npm): @codegenie/serverless-express
- Outdated (npm): @mbc-cqrs-serverless/core
- Outdated (npm): @mbc-cqrs-serverless/sequence
- Outdated (npm): @nestjs/common
- Outdated (npm): @nestjs/core
- Outdated (npm): @nestjs/platform-express
- Outdated (npm): @prisma/client
- Outdated (npm): chalk
- Outdated (npm): class-validator
- Outdated (npm): cognito-local
- Outdated (npm): csv-parser
- Outdated (npm): js-yaml
- Outdated (npm): jszip
- Outdated (npm): node-fetch
- Outdated (npm): nodemailer
- Outdated (npm): rimraf
- Outdated (npm): ulid
- doc comments repeat the names packages/cli/src/runners/abstract.runner.ts:48
- doc comments repeat the names packages/core/src/integration/nestjs-decorators.spec.ts:202
- doc comments repeat the names packages/mcp-server/src/tools/analyze.ts:69
- Skipped (documented): (unnamed test) packages/core/src/integration/nestjs-platform-express-behavior.spec.ts:258
- Skipped (documented): (unnamed test) packages/core/src/integration/nestjs-platform-express-behavior.spec.ts:511
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4267345a6fb0480f8a8dd006a1a58388/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/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-4267345a6fb0480f8a8dd006a1a58388/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/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 58 | 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 | 147 | 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 |