soybeanjs/soybean-admin-nestjs

Executive summary

soybeanjs/soybean-admin-nestjs scores 28 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 19 and is rated Critical. Its REDACTED Scanning dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 7 Deprecated finding(s) in Dependency Hygiene and to resolve the 5 Outdated (npm) finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 28 to about 35.

108 findings are critical: 57 in Dependency Vulnerabilities, 18 in Domain ↔ infrastructure boundary, 17 in REDACTED Scanning, five in Static Analysis (SAST), three in Secrets (history), two in Text alternatives, one in Circular Imports, one in Dependency Hygiene, one in Forms & labels, one in IaC & Container Security, one in Keyboard semantics and one in Page structure.

Watchdog couldn't measure 4 dimensions in this code, among them Test Reliability, Navigability and Platform End-of-Life, so they are left out of the score. The product code is 29,674 lines, which would take an estimated 0.3 person-years, around €39,000, to rebuild.

Code Health 56 Adequate, capped by Structured logging Architecture 70 Adequate, capped by Circular Imports Maturity 33 Weak, capped by Knowledge Freshness, Architecture documentation and Documentation accuracy Production Readiness 19 ⚠ Critical, capped by Test Distribution, REDACTED Scanning, Dependency Hygiene, CI/CD gates, Security & performance tooling and DR & Backup Security and Compliance 57 Adequate, capped by Static Analysis (SAST), Dependency Vulnerabilities and Data Protection Domain Modelling 40 Weak, capped by Rich vs anemic model, Encapsulated state and Strongly-typed ids Accessibility 26 Weak, capped by Text alternatives and Keyboard semantics Performance 60 Adequate

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

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

Production Readiness 19 · counts for 45%Accessibility 26 · counts for 25%Maturity 33 · counts for 14%Domain Modelling 40 · counts for 8%Code Health 56 · counts for 4%Security and Compliance 57 · counts for 2%Performance 60 · counts for 1%Architecture 70 · counts for 1%

If Production Readiness rose from 19 to 70, the lowest score rated Strong, the score would rise from 28 to about 35.

Code composition: what the lines of code are

Product code 100%Tests 0%

New since the last survey: 95 findings

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

Dependency Hygiene · Deprecated: crypto-js REDACTED
Dependency Hygiene · Deprecated: eslint REDACTED
Dependency Hygiene · Deprecated: supertest REDACTED
Dependency Hygiene · Deprecated: vue-i18n REDACTED
Dependency Hygiene · Deprecated: eslint REDACTED
Dependency Hygiene · Deprecated: crypto-js REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
REDACTED Scanning · REDACTED
Static Analysis (SAST) · REDACTED
Static Analysis (SAST) · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
Dependency Vulnerabilities · REDACTED
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
Large Files · frontend/packages/color/src/constant/name.ts: 1578 lines of code frontend/packages/color/src/constant/name.ts
Large Files · backend/libs/infra/casbin/src/services/authz.service.ts: 920 lines of code backend/libs/infra/casbin/src/services/authz.service.ts
Large Files · backend/libs/infra/casbin/src/services/authz-management.service.ts: 639 lines of code backend/libs/infra/casbin/src/services/authz-management.service.ts
Large Files · backend/libs/infra/casbin/src/services/authz-api.ts: 453 lines of code backend/libs/infra/casbin/src/services/authz-api.ts
Large Files · frontend/src/locales/langs/en-us.ts: 424 lines of code frontend/src/locales/langs/en-us.ts
Large Files · frontend/src/locales/langs/zh-cn.ts: 424 lines of code frontend/src/locales/langs/zh-cn.ts
Large Files · frontend/src/views/manage/menu/modules/menu-operate-modal.vue: 403 lines of code frontend/src/views/manage/menu/modules/menu-operate-modal.vue
Web-Security Posture · Weak hash algorithm backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts
Web-Security Posture · Weak hash algorithm backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts
Exception handling · Swallowed exception (empty catch) backend/apps/base-system/src/api/iam/rest/authentication.controller.ts
Exception handling · Swallowed exception (empty catch) backend/apps/base-system/src/api/iam/rest/authentication.controller.ts
Exception handling · Swallowed exception (empty catch) frontend/packages/utils/src/storage.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: access_key.model backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.model.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: access_key.read.model backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.read.model.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: access_key-created.event backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-created.event.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: access_key-deleted.event backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-deleted.event.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: user.read.model backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.read.model.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: user backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: domain-create.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: domain-create.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: domain-delete.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-delete.command.handler.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: domain-update.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: domain-update.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: domain.model backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.model.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: domain.read.model backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.read.model.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: page-domains.query backend/apps/base-system/src/lib/bounded-contexts/iam/domain/queries/page-domains.query.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: menu.model backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: menu.read.model backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.read.model.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: role.model backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.model.ts
Domain ↔ infrastructure boundary · Domain depends on infrastructure: role.read.model backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.read.model.ts
Constructible invalid state · Constructible in an invalid state: ApiEndpoint backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/domain/api-endpoint.model.ts
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/components/common/reload-button.vue
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/plugins/loading.ts
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/styles/css/nprogress.css
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/styles/css/transition.css
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/styles/css/transition.css
Visual & motion safety · Animation without a prefers-reduced-motion guard frontend/src/styles/css/transition.css
Async & latency hygiene · Sync-over-async blocking frontend/packages/scripts/src/commands/router.ts
Async & latency hygiene · Sync-over-async blocking frontend/packages/scripts/src/commands/router.ts

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 258 findings

These 258 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one. The first 100 are listed here.

Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: REDACTED REDACTED
Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Code Duplication · Duplicated block (15 lines × 6 locations) backend/apps/base-system/src/lib/bounded-contexts/access-key/application/command-handlers/access_key-delete.command.handler.ts
Code Duplication · Duplicated block (15 lines × 2 locations) backend/libs/infra/casbin/src/adapter/casbin-prisma.adapter.ts
Code Duplication · Duplicated block (15 lines × 3 locations) frontend/src/layouts/modules/global-menu/modules/reversed-horizontal-mix-menu.vue
Code Duplication · Duplicated block (15 lines × 3 locations) frontend/src/views/access-key/modules/access-key-operate-drawer.vue
Code Duplication · Duplicated block (14 lines × 2 locations) backend/apps/base-system/src/api/endpoint/dto/page-endpoint.dto.ts
Code Duplication · Duplicated block (14 lines × 2 locations) backend/apps/base-system/src/api/iam/dto/assign-permission.dto.ts
Code Duplication · Duplicated block (14 lines × 2 locations) backend/apps/base-system/src/api/iam/dto/domain.dto.ts
Code Duplication · Duplicated block (14 lines × 2 locations) backend/apps/base-system/src/api/log-audit/login-log/dto/page-login-log.dto.ts
Code Duplication · Duplicated block (14 lines × 2 locations) backend/libs/infra/crypto/src/services/crypto.service.ts
Code Duplication · Duplicated block (13 lines × 2 locations) backend/apps/base-system/src/infra/bounded-contexts/iam/menu/repository/menu.read.pg.repository.ts
Code Duplication · Duplicated block (13 lines × 6 locations) backend/apps/base-system/src/lib/bounded-contexts/access-key/access_key.module.ts
Code Duplication · Duplicated block (13 lines × 9 locations) backend/apps/base-system/src/lib/bounded-contexts/access-key/access_key.module.ts
Code Duplication · Duplicated block (13 lines × 2 locations) backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-created.event.handler.ts
Code Duplication · Duplicated block (13 lines × 3 locations) backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/command-handlers/user-create.command.handler.ts
Code Duplication · Duplicated block (13 lines × 2 locations) backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts
Code Duplication · Duplicated block (13 lines × 2 locations) backend/apps/base-system/src/lib/bounded-contexts/iam/role/application/command-handlers/role-create.command.handler.ts
Code Duplication · Duplicated block (13 lines × 2 locations) backend/libs/infra/casbin/src/guards/authz.guard.ts
Code Duplication · Duplicated block (13 lines × 2 locations) backend/libs/infra/casbin/src/services/authz-api.ts
Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) backend/libs/shared/ip2region/src/ip2region.ts
Code Duplication · Duplicated block (12 lines × 2 locations) backend/apps/base-demo/src/main.ts
Code Duplication · Duplicated block (12 lines × 2 locations) backend/apps/base-system/src/api/iam/rest/authentication.controller.ts
Code Duplication · Duplicated block (12 lines × 5 locations) backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts
Code Duplication · Duplicated block (12 lines × 5 locations) backend/libs/infra/casbin/src/services/authz-api.ts
Code Duplication · Duplicated block (12 lines × 3 locations) backend/libs/infra/casbin/src/services/authz-api.ts
Code Duplication · Duplicated block (12 lines × 2 locations) frontend/src/layouts/base-layout/index.vue
Code Duplication · Duplicated block (12 lines × 4 locations) frontend/src/views/access-key/modules/access-key-search.vue
Code Duplication · Duplicated block (11 lines × 7 locations) backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/application/query-handlers/endpoints.by-ids.query.handler.ts
Code Duplication · Duplicated block (11 lines × 2 locations) frontend/packages/materials/src/libs/page-tab/button-tab.vue
Code Duplication · Duplicated block (11 lines × 5 locations) frontend/src/views/access-key/modules/access-key-search.vue
Code Duplication · Duplicated block (10 lines × 2 locations) backend/apps/base-system/src/api/access-key/dto/access_key.dto.ts
Code Duplication · Duplicated block (10 lines × 2 locations) backend/apps/base-system/src/api/iam/dto/page-domains.dto.ts
Code Duplication · Duplicated block (10 lines × 5 locations) backend/apps/base-system/src/infra/bounded-contexts/access-key/repository/access_key.read.pg.repository.ts
Code Duplication · Duplicated block (10 lines × 5 locations) backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.write.pg.repository.ts
Code Duplication · Duplicated block (10 lines × 6 locations) backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/event-handlers/domain-deleted.event.handler.ts
Code Duplication · Duplicated block (10 lines × 2 locations) backend/libs/infra/crypto/src/services/crypto.service.ts
Code Duplication · Duplicated block (9 lines × 3 locations) backend/apps/base-system/src/api/endpoint/rest/endpoint.controller.ts
Code Duplication · Duplicated block (9 lines × 2 locations) backend/libs/infra/casbin/src/services/authz-management.service.ts
Code Duplication · Duplicated block (9 lines × 2 locations) frontend/src/views/home/modules/pie-chart.vue
Code Duplication · Duplicated block (8 lines × 3 locations) backend/apps/base-system/src/api/access-key/dto/page-access_key.dto.ts
Code Duplication · Duplicated block (8 lines × 10 locations) backend/apps/base-system/src/infra/bounded-contexts/access-key/repository/access_key.write.pg.repository.ts
Code Duplication · Duplicated block (8 lines × 4 locations) backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/application/query-handlers/endpoints.query.handler.ts
Code Duplication · Duplicated block (8 lines × 2 locations) frontend/packages/axios/src/index.ts
Code Duplication · Duplicated block (7 lines × 4 locations) backend/apps/base-system/src/api/access-key/dto/page-access_key.dto.ts
Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) backend/apps/base-system/src/api/iam/rest/authentication.controller.ts
Code Duplication · Duplicated block with local edits (6 matched lines × 2 locations) backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/service/authentication.service.ts
Code Duplication · Duplicated block with local edits (5 matched lines × 2 locations) backend/apps/base-system/src/infra/bounded-contexts/iam/menu/repository/menu.read.pg.repository.ts
Test Coverage · No test reaches this file frontend/src/layouts/base-layout/index.vue
Test Coverage · No test reaches this file frontend/src/views/home/modules/pie-chart.vue
Test Coverage · No test reaches this file frontend/src/hooks/common/form.ts
Test Coverage · No test reaches this file frontend/packages/hooks/src/use-context.ts
Test Coverage · No test reaches this file frontend/src/views/manage/role/modules/role-operate-drawer.vue
Test Coverage · No test reaches this file frontend/packages/color/src/shared/colord.ts
Test Coverage · No test reaches this file frontend/src/views/manage/role/modules/menu-auth-modal.vue
Test Coverage · No test reaches this file frontend/src/views/access-key/modules/access-key-operate-drawer.vue
Test Coverage · No test reaches this file frontend/packages/scripts/src/commands/router.ts
Test Coverage · No test reaches this file frontend/src/layouts/modules/global-search/components/search-modal.vue
Test Coverage · No test reaches this file frontend/src/views/log/login/index.vue
Test Coverage · No test reaches this file backend/libs/bootstrap/src/swagger/init-doc.swagger.ts
Test Coverage · No test reaches this file frontend/packages/scripts/src/commands/git-commit.ts
Test Coverage · No test reaches this file frontend/src/layouts/context/index.ts
Test Coverage · No test reaches this file backend/prisma/seeds/sys/casbinRule.ts
Test Coverage · No test reaches this file frontend/packages/scripts/src/locales/index.ts
Test Coverage · No test reaches this file frontend/src/components/custom/count-to.vue
Test Coverage · No test reaches this file frontend/packages/hooks/src/use-request.ts
Test Coverage · No test reaches this file frontend/src/views/manage/menu/modules/shared.ts

Rebuild cost: about €39,000 · Estimate

Cost to rebuild	€13,000 to €65,000, for 217 to 689 hours of work, about 0.3 person-years for one engineer
Difficulty of the problem	High, 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 28. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size	Medium: 29,674 lines of product code

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

Top priorities

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

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

Raises the score by about 5 points · Low effort · Dependency Hygiene

Resolve the 5 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (5).

Raises the score by about 4 points · Low effort · Dependency Hygiene

Resolve the 17 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (4), REDACTED (3).

Raises the score by about 7 points · Medium effort · REDACTED Scanning

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk

This code would cost about €39,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 19 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.

Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts

What to do: Start with the Production Readiness actions in Top priorities.

One cause behind 27 Domain Modelling findings · Common cause

27 findings in the Domain Modelling lens come from the same cause. The code models the business as objects, such as an order or a customer, and each object should guard its own rules: an order, for example, should refuse to be shipped before it has been paid. Here the objects don't do that. Other code can change an object's data directly, so it can put an order into a state the rules forbid. Some objects only hold data, while the rules that should keep that data valid sit elsewhere in the code. Identifiers, such as order numbers and customer numbers, are passed around as plain numbers or text, so nothing stops the code from using one kind where another belongs. Because all of these findings have the same cause, fixing it once, in the business objects themselves, deals with them together.

Based on: Encapsulated state (6 findings) · Rich vs anemic model (8 findings) · Strongly-typed ids (13 findings)

What to do: Give each business object the methods that enforce its rules, such as a method for shipping an order that first checks it has been paid, and let only those methods change its data. Give each kind of identifier a type of its own, so an order number can't be used where a customer number belongs.

If you do one thing first · First action

Resolve the 7 Deprecated finding(s) in Dependency Hygiene. Of all the actions in this report, it raises the score most for the work it takes: about 5 points for low effort, because it clears the 7 Dependency Hygiene findings. The next survey will show the change in the score.

Based on: the ranked actions in Top priorities, by score gain and effort

Architecture — module dependency graph

Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

341 modules, with 337 dependencies between them. Every module uses only modules listed above it, so there are no loops.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →	2 apps.base-system.src.lib.bounded-contexts.api-endpoint.api-endpoint.domain.endpoint_read_model	4 apps.base-system.src.lib.bounded-contexts.iam.domain.domain.domain_read_model	9 apps.base-system.src.lib.bounded-contexts.log-audit.operation-log.domain.operation-log_read_model	11 libs.infra.rest.src.pagination-params	12 libs.infra.rest.src.res_response	13 libs.shared.prisma.src.pagination	14 libs.shared.prisma.src.prisma_service	22 apps.base-system.src.lib.bounded-contexts.access-key.queries.page-access_key_query	23 apps.base-system.src.lib.bounded-contexts.api-endpoint.api-endpoint.ports.api-endpoint_read_repo-port	24 apps.base-system.src.lib.bounded-contexts.iam.authentication.application.service.authorization_service	25 apps.base-system.src.lib.bounded-contexts.iam.authentication.ports.user_read_repo-port	26 apps.base-system.src.lib.bounded-contexts.iam.domain.ports.domain_read_repo-port	27 apps.base-system.src.lib.bounded-contexts.iam.role.ports.role_read_repo-port	28 apps.base-system.src.lib.bounded-contexts.log-audit.login-log.ports.login-log_read_repo-port	29 apps.base-system.src.lib.bounded-contexts.log-audit.operation-log.ports.operation-log_read_repo-port	37 apps.base-system.src.lib.bounded-contexts.access-key.ports.access_key_read_repo-port
1 apps.base-system.src.lib.bounded-contexts.access-key.ports.access_key_write_repo-port
2 apps.base-system.src.lib.bounded-contexts.api-endpoint.api-endpoint.domain.endpoint_read_model
3 apps.base-system.src.lib.bounded-contexts.iam.authentication.ports.user_write_repo-port
4 apps.base-system.src.lib.bounded-contexts.iam.domain.domain.domain_read_model
5 apps.base-system.src.lib.bounded-contexts.iam.domain.ports.domain_write_repo-port
6 apps.base-system.src.lib.bounded-contexts.iam.menu.ports.menu_read_repo-port
7 apps.base-system.src.lib.bounded-contexts.iam.menu.ports.menu_write_repo-port
8 apps.base-system.src.lib.bounded-contexts.iam.role.ports.role_write_repo-port
9 apps.base-system.src.lib.bounded-contexts.log-audit.operation-log.domain.operation-log_read_model
10 libs.infra.guard.src.api-key.services.api-key_interface
11 libs.infra.rest.src.pagination-params
12 libs.infra.rest.src.res_response
13 libs.shared.prisma.src.pagination
14 libs.shared.prisma.src.prisma_service
15 apps.base-system.src.api.access-key.rest.access_key_controller					1	1
16 apps.base-system.src.api.endpoint.rest.endpoint_controller	1				1	1
17 apps.base-system.src.api.iam.rest.domain_controller		1			1	1
18 apps.base-system.src.api.iam.rest.role_controller					1	1
19 apps.base-system.src.api.iam.rest.user_controller					1	1
20 apps.base-system.src.api.log-audit.login-log.rest.login-log_controller					1	1
21 apps.base-system.src.api.log-audit.operation-log.rest.operation-log_controller			1		1	1
22 apps.base-system.src.lib.bounded-contexts.access-key.queries.page-access_key_query				1
23 apps.base-system.src.lib.bounded-contexts.api-endpoint.api-endpoint.ports.api-endpoint_read_repo-port	1					1
24 apps.base-system.src.lib.bounded-contexts.iam.authentication.application.service.authorization_service							1
25 apps.base-system.src.lib.bounded-contexts.iam.authentication.ports.user_read_repo-port						1
26 apps.base-system.src.lib.bounded-contexts.iam.domain.ports.domain_read_repo-port		1				1
27 apps.base-system.src.lib.bounded-contexts.iam.role.ports.role_read_repo-port						1
28 apps.base-system.src.lib.bounded-contexts.log-audit.login-log.ports.login-log_read_repo-port						1
29 apps.base-system.src.lib.bounded-contexts.log-audit.operation-log.ports.operation-log_read_repo-port			1			1
30 apps.base-system.src.api.iam.rest.authorization_controller					1					1
31 apps.base-system.src.infra.bounded-contexts.api-endpoint.api-endpoint.repository.api-endpoint_read_pg_repository	1					1	1		1
32 apps.base-system.src.infra.bounded-contexts.iam.authentication.repository.user_read_pg_repository						1	1				1
33 apps.base-system.src.infra.bounded-contexts.iam.domain.repository.domain_read_pg_repository		1				1	1					1
34 apps.base-system.src.infra.bounded-contexts.iam.role.repository.role_read_pg_repository						1	1						1
35 apps.base-system.src.infra.bounded-contexts.log-audit.login-log.repository.login-log_read_pg_repository						1	1							1
36 apps.base-system.src.infra.bounded-contexts.log-audit.operation-log.repository.operation-log_read_pg_repository			1			1	1								1
37 apps.base-system.src.lib.bounded-contexts.access-key.ports.access_key_read_repo-port						1		1
38 apps.base-system.src.lib.bounded-contexts.api-endpoint.api-endpoint.application.query-handlers.page-endpoints_query_handler	1					1			1
39 apps.base-system.src.infra.bounded-contexts.access-key.repository.access_key_read_pg_repository						1	1	1								1
40 apps.base-system.src.lib.bounded-contexts.access-key.application.query-handlers.page-access_keys_query_handler						1		1								1

Uses a module listed above itPart of a loopThe module itself

At a glance — Code Health · 56% · Adequate · gated by X4 ·

The Good

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

The Bad

X3 · Repo Exception handling 5.2

The Ugly

X2 · Repo Cancellation propagation 4.0 X23 · Repo Unguarded diagnostic materialisation 4.7 X4 · Repo Structured logging 2.1

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

The Good

D5 · TypeScript Coupling 9.2 D6 · TypeScript Cohesion (LCOM4) 10.0 D22 · TypeScript Internal API Consistency 7.0 D26 · TypeScript Project Cohesion 8.2 D35 · TypeScript Change Coupling 10.0 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0 AX6 · Repo Interface segregation 10.0 AX9 · Repo CQS / query purity 10.0 R11 · React / TS Import Boundaries 9.4

The Bad

AX10 · Repo Code composition 6.8

The Ugly

R9 · React / TS Circular Imports 2.3

At a glance — Maturity · 33% · Weak · gated by D34, M2, M4 ·

The Good

D15 · TypeScript Churn × Complexity Hotspots 10.0 D19 · TypeScript Documentation Quality 7.0 D21 · TypeScript Naming Consistency 10.0 M3 · Repo Folder & project structure 10.0

The Bad

M1 · Repo Documentation (README) 6.2

The Ugly

D34 · TypeScript Knowledge Freshness 0.0 M2 · Repo Architecture documentation 2.0 M4 · Repo Documentation accuracy 0.0

At a glance — Readiness · 19% · Critical · gated by D9, D13, R8, P1, P3, P5 ·

The Good

D10 · TypeScript Test Quality 10.0 D14 · TypeScript License Compliance 10.0 ED5 · Repo Idempotency 10.0 P10 · Repo Library API & versioning 10.0 P2 · Repo Observability 7.0 P4 · Repo Deployment & Rollback 8.0 P8 · Repo Schema migrations 10.0 R6 · React / TS Tooling 10.0

The Bad

D12 · TypeScript Dependency Hygiene 6.0 R4 · React / TS Test Coverage 5.5

The Ugly

D9 · TypeScript Test Distribution 3.5 D13 · TypeScript REDACTED Scanning 0.0 P1 · Repo CI/CD gates 0.0 P3 · Repo Security & performance tooling 0.0 P5 · Repo DR & Backup 0.0 R8 · React / TS Dependency Hygiene 0.0

At a glance — Security · 57% · Adequate · gated by D29, D30, C1 ·

The Good

D28 · TypeScript Secrets (history) 7.0 D31 · TypeScript IaC & Container Security 8.9 D43 · TypeScript Malicious Dependencies 10.0 C2 · Repo Access Controls 10.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0

The Bad

S1 · Repo Web-Security Posture 6.0

The Ugly

D29 · TypeScript Static Analysis (SAST) 3.8 D30 · TypeScript Dependency Vulnerabilities 0.0 C1 · Repo Data Protection 3.5 X24 · Repo Document value interpolated into markup unescaped 3.1

At a glance — Domain Modelling · 40% · Weak · gated by DM4, DM5, DM2 ·

The Good

DM1 · Repo Aggregate boundaries 10.0 DM11 · Repo Constructible invalid state 9.1 DM9 · Repo Scattered domain decisions 10.0

The Ugly

DM2 · Repo Strongly-typed ids 3.0 DM4 · Repo Rich vs anemic model 3.0 DM5 · Repo Encapsulated state 2.2 DM6 · Repo Domain ↔ infrastructure boundary 4.1

At a glance — Accessibility · 26% · Weak · gated by AC1, AC4 ·

The Bad

AC3 · Repo Page structure 5.8

The Ugly

AC1 · Repo Text alternatives 1.0 AC2 · Repo Forms & labels 4.3 AC4 · Repo Keyboard semantics 1.0 AC6 · Repo Visual & motion safety 4.8 AC7 · Repo A11y enforcement 4.0

At a glance — Performance · 60% · Adequate ·

The Bad

PF3 · Repo Async & latency hygiene 6.0

Security & Compliance — OWASP Top-10 mapping

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

OWASP category	Findings	Severity
A03:2025 — Software Supply Chain Failures	85	High / Critical
A07:2025 — Authentication Failures	21	High / Critical
A02:2025 — Security Misconfiguration	10	High / Critical
A05:2025 — Injection	7	High / Critical

Roadmap

Immediately resolve the 17 leaked secrets, prioritizing fixes in REDACTED, REDACTED, and REDACTED, while cleaning up 7 deprecated and 5 outdated dependencies in REDACTED and REDACTED. Strengthen test coverage by addressing the low distribution score across unit, e2e, and other test types. Finally, establish a CI workflow to automatically build and run tests on every push and pull request.

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

Do this	Helps	Effort	Dimension
Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (7).	+5.2 pts	Low	Dependency Hygiene
Resolve the 5 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (5).	+4.3 pts	Low	Dependency Hygiene
Resolve the 17 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (4), REDACTED (3).	+7.4 pts	Medium	REDACTED Scanning
Improve Test Distribution — currently 3.5/10.	+6.8 pts	Medium	Test Distribution
Add a CI workflow that builds and runs the test suite on every push/PR.	+3.3 pts	Medium	CI/CD gates
Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.	+3.3 pts	Medium	Security & performance tooling
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.	+3.3 pts	Medium	DR & Backup
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.	+3.3 pts	Medium	Dependency Hygiene

File quality

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

File	Score	Band	Worst signal
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	0.0	Slop	Dependency Vulnerabilities: Critical CVE: REDACTED
REDACTED	0.1	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	0.4	Slop	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	1.1	Slop	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	1.7	Slop	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	2.3	Slop	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	3.4	Slop	IaC & Container Security: High IaC: REDACTED
REDACTED	4.4	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	5.1	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	5.7	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
REDACTED	5.8	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	6.2	Mixed	IaC & Container Security: Medium IaC: REDACTED
REDACTED	6.9	Mixed	Static Analysis (SAST): Medium: REDACTED
REDACTED	7.2	Mixed	REDACTED Scanning: Leaked secret: REDACTED
REDACTED	7.2	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	7.2	Mixed	Static Analysis (SAST): High: REDACTED
REDACTED	7.2	Mixed	Dependency Vulnerabilities: High CVE: REDACTED
frontend/src/service/api/system-manage.ts	7.3	Mixed	Explicit Debt: TodoComment
REDACTED	7.9	Mixed	Dependency Vulnerabilities: Medium CVE: REDACTED

How the grades work

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

Critical — 108

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 212

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 279

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

Could not be resolved — 8

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

Methodology & how to trust this report

Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 85 of 91 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 6 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 91 dimensions across the health lenses

D1D2D3D5D6D9D10D12D13D14D15D17D19D21D22D26D28D29D30D31D34D35D43AC1AC2AC3AC4AC6AC7AX10AX3AX4AX5AX6AX9C1C2DM1DM11DM2DM4DM5DM6DM9ED5GD1IC1M1M2M3M4P1P10P2P3P4P5P8PF3R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X2X21X22X23X24X25X28X29X3X30X4X5

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

How to trust any code-health report — three questions

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

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

Tools & methods

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

Method	Backs	Version	Evaluator
Roslyn static analysis	Complexity, cohesion, coupling, dead code, API surface, layering	5.3.0	✓ deterministic
Native secret scanner	Hardcoded secrets / credentials	1.0.0	✓ deterministic
Watchdog duplication detector (in-process)	Code duplication	1.0.0	✓ deterministic
Coverage (coverlet / dotnet-coverage)	Line & branch coverage	10.0.400	✓ deterministic
NuGet / dotnet	Outdated, vulnerable & deprecated dependencies	10.0.400	✓ deterministic
git / LibGit2Sharp	Churn hotspots, knowledge concentration, history	2.43.0 · 0.31.0	✓ deterministic
gitleaks · semgrep · trivy · checkov	Secrets in history, SAST, CVEs, IaC & container, PII / GDPR	1.86.0 · 0.69.3 · 3.2.533	✓ deterministic
LLM (sampled · advisory)	Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurement	Local LLM	◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16401-8e58-76e7-95ff-e81f5c981829.

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

Run transparency — what happened this run

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

D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the JavaScript/TypeScript suite (jest via `pnpm install --frozen-lockfile --ignore-scripts` in backend/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Single-maintainer repository — bus factor is not applicable (5 contributor(s) across 247 commit(s) sampled, automation and bot accounts excluded). One of them holds 96% of the history; the other 4 hold 1% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
D32 Data Compliance (PII/GDPR) — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `backend/apps/base-demo/src/main.ts`, `backend/apps/base-system/src/main.ts`, `frontend/packages/alova/src/index.ts`, `frontend/packages/axios/src/index.ts`, `frontend/packages/scripts/src/locales/index.ts`, … (+8 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.
D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — redis Pulling postgres Pulling pgbouncer Pulling pgbouncer Error Get "https://registry-1.docker.io/v2/": Forbidden redis Error context canceled postgres Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: backend Skipped - No image to be pulled db-init Skipped - No image to be pulled redis Pulling postgres Pulling pgbouncer Pulling redis Error Get "https://registry-1.docker.io/v2/": Forbidden pgbouncer Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
M3 Folder & project structure — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 46 further occurrence(s) are not listed individually; the score already reflects all 86.
R4 Test Coverage — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 176 further occurrence(s) are not listed individually; the score already reflects all 216.
R7 Dead Code — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 4 further occurrence(s) are not listed individually; the score already reflects all 44.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

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

Per-dimension blind spots

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

D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
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.
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.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D22 Internal API Consistency: API-surface coherence is an LLM judgement over a sample of the public surface — consistency of intent across the whole API is approximated, not exhaustively verified.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
ED5 Idempotency: Idempotency is judged from the handler body's visible writes and guards — a guard enforced by a database unique constraint, a broker's exactly-once delivery, or a domain method whose no-op-when-applied logic the scan can't follow may read as at-risk; the at-risk candidates are confirmed by a SAMPLED LLM verdict (advisory, not exhaustive) and degrade to heuristic-only when no model is configured. It flags the at-least-once double-apply SHAPE, not a runtime proof of a duplicate effect.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.

The LLM boundary

LLM-set scores this run (6): D19, D21, D22, D26, ED5, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 method(s) exceeded the cyclomatic complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d1_recommendation.md.

Do you agree with this assessment?

D2 · Cognitive Complexity10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 method(s) exceeded the cognitive complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

Do you agree with this assessment?

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

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

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

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

5 god class(es) detected.

FunctionTooLong: index.useRouteStore · ×3frontend/src/store/modules/route/index.ts:26

TooManyMethods: AuthZService · ×2backend/libs/infra/casbin/src/services/authz.service.ts:13

What to do

Resolve the 3 FunctionTooLong finding(s) in God Classes — start with REDACTED (2), table.ts. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 TooManyMethods finding(s) in God Classes — start with authz.service.ts, authz-management.service.ts. — One of this dimension's main actionable groups (2 warning-level).
Stand up a CI pipeline, then gate God Classes in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

10 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.

Off the main sequence: @sa/utils

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).
Stand up a CI pipeline, then gate Coupling in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

0 of 36 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

Do you agree with this assessment?

D9 · Test Distribution3.5 / 10Weak✓ Tool-verified

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

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

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

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

What to do

Improve Test Distribution — currently 3.5/10. — 4 test methods: 2 unit, 0 integration, 0 BDD, 2 e2e. The JavaScript/TypeScript suite contributes 4 `it`/`test` case(s) across 4 test file(s) declaring at least one; its tier split is read from package names and paths only.

Detailed fixes: d9_recommendation.md.

Do you agree with this assessment?

D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified

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

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

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

0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 4 tests.

✓ On the Gold path — maintain.

Detailed fixes: d10_recommendation.md.

Do you agree with this assessment?

D12 · Dependency Hygiene6.0 / 10Adequate✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

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

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

Deprecated: crypto-js · ×6REDACTED:62

Deprecated: glob · ×7REDACTED:2702

Outdated (npm): @nestjs/axios · ×5REDACTED:40

Outdated (npm): @alova/mock · ×51

What to do

Resolve the 7 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (7). — One of this dimension's main actionable groups (7 recommendation-level).
Resolve the 6 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (6). — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 Outdated (npm) finding(s) in Dependency Hygiene — start with REDACTED (5). — One of this dimension's main actionable groups (5 recommendation-level).
Stand up a CI pipeline, then gate Dependency Hygiene in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

8 secret(s) detected.

REDACTED

What to do

Resolve the 17 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (6), REDACTED (4), REDACTED (3). — One of this dimension's main actionable groups (17 issue-level).
Stand up a CI pipeline, then gate REDACTED Scanning in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

Do you agree with this assessment?

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

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

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

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

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

Do you agree with this assessment?

D17 · Explicit Debt9.9 / 10Stronggated by 9 serious findings✓ Tool-verified

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

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

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

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

TodoComment · ×9backend/local-route.migrate.ts:202

What to do

Resolve the 9 TodoComment finding(s) in Explicit Debt — start with system-manage.ts (2), local-route.migrate.ts, base-demo.module.ts. — One of this dimension's main actionable groups (9 warning-level).
Stand up a CI pipeline, then gate Explicit Debt in it to reach Verified (currently Documented). — This repository has no CI pipeline, so there is nothing to add a gate to yet — the pipeline comes first. Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

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

Do you agree with this assessment?

D19 · Documentation QualityStrong◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

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

The repository's root README is clear and complete for a monorepo project: it opens with an online preview link, a one-line overview of SoybeanAdmin NestJS (a backend scaffolding), and a full outline listing every document in the set. The backend/README.md is a directory README documenting that directory rather than the repository as a whole, so its presence does not affect the root's quality.

Documentation: no architecture or design documentationREADME.md

What to do

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

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

Do you agree with this assessment?

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

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

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

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

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

Do you agree with this assessment?

D22 · Internal API ConsistencyStrong◐ Sampled · advisory

What it measures: Whether the internal API surface is consistent and coherent.

Method: Judged by language model at low temperature over a sample of the public API surface (IsPackable or .Contracts types). Sampled, advisory; confidence discounted by model uncertainty.

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

3 API inconsistencies across 40 exposed types.

Inconsistent return type for success validation. Alova's `isBackendSuccess` returns a `Promise<boolean>`, while Axios's `isBackendSuccess` returns a synchronous `boolean`. This forces consumers to handle async/sync differences inconsistently when abstracting over multiple HTTP clients.

Inconsistent error handler signature. Alova's `onError` receives the original response (which may be null) and the method instance, whereas Axios's `onError` only receives the error object. This makes it difficult to write a unified error handling strategy across both HTTP clients.

Divergent failure handling patterns. Axios uses a dedicated `onBackendFail` hook that can return a new response (allowing for retry/interception logic), while Alova relies on `isBackendSuccess` to determine flow. This creates two different mental models for handling business logic errors (e.g., 401/403) vs network errors.

What to do

Resolve the 1 Inconsistent return type for success validation. Alova's… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Inconsistent error handler signature. Alova's `onError` receives the… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Divergent failure handling patterns. Axios uses a dedicated… finding(s) in Internal API Consistency. — One of this dimension's main actionable groups (1 warning-level).

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

Do you agree with this assessment?

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

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

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

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

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

Split backend

What to do

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

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

Do you agree with this assessment?

D28 · Secrets (history)7.0 / 10Adequategated by 3 critical findings✓ Tool-verified

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

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

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

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

REDACTED

What to do

Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D29 · Static Analysis (SAST)3.8 / 10Weak✓ Tool-verified

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

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

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

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

7 finding(s): 0 critical, 5 high, 2 medium, 0 low. semgrep hit a parse error in 13 file(s) — `backend/apps/base-demo/src/main.ts` (line 27), `backend/apps/base-system/src/main.ts` (line 78), `frontend/packages/alova/src/index.ts` (line 76, line 77), `frontend/packages/axios/src/index.ts` (line 189), `frontend/packages/scripts/src/locales/index.ts` (line 82), … (+8 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.

REDACTED

What to do

Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).

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

Do you agree with this assessment?

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

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

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

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

85 finding(s): 3 critical, 54 high, 22 medium, 6 low.

REDACTED

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

What to do

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

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

Do you agree with this assessment?

D31 · IaC & Container Security8.9 / 10Adequategated by 1 critical finding✓ Tool-verified

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

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

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

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

REDACTED

What to do

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

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

Do you agree with this assessment?

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

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

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

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

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

Orphaned file · ×95frontend/src/views/manage/menu/modules/menu-operate-modal.vue:1

Most significant orphaned file · ×3frontend/packages/color/src/constant/name.ts:1

Concentrated knowledge decay

What to do

Resolve the 95 Orphaned file finding(s) in Knowledge Freshness — start with REDACTED (11), index.vue (10), shared.ts (3). — One of this dimension's main actionable groups (95 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with name.ts, authz.service.ts, authz-management.service.ts. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

Do you agree with this assessment?

D35 · Change Coupling10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

No strong hidden change-coupling between production files.

✓ On the Gold path — maintain.

Detailed fixes: d35_recommendation.md.

Do you agree with this assessment?

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Do you agree with this assessment?

Frontend & cross-cutting dimensions

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

AC1 · Text alternatives1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.

An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative. (×2) — frontend/src/components/custom/soybean-avatar.vue:9, frontend/src/views/home/modules/header-banner.vue:47

What to do

Add a text alternative — alt on images (alt="" for purely decorative ones), a title or aria-label on meaningful svg, an aria-label or inner fallback content on canvas, and a captions <track> on video.

Do you agree with this assessment?

AC2 · Forms & labels4.3 / 10Weak✓ Tool-verified

Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.

Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. — frontend/src/layouts/modules/theme-drawer/modules/config-operation.vue:50

What to do

Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.

Do you agree with this assessment?

AC3 · Page structure5.8 / 10Adequate✓ Tool-verified

Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.

Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — frontend/src/views/_builtin/iframe-page/[url].vue:21

What to do

Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.

Do you agree with this assessment?

AC4 · Keyboard semantics1.0 / 10Critical✓ Tool-verified

Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.

Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.

Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".

A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler. — frontend/src/layouts/modules/theme-drawer/components/layout-mode-card.vue:72

What to do

Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.

Do you agree with this assessment?

AC6 · Visual & motion safety4.8 / 10Weak✓ Tool-verified

Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.

Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.

Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.

<icon-ant-design-reload-outlined> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — frontend/src/components/common/reload-button.vue:17
<div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:. — frontend/src/plugins/loading.ts:39
`#nprogress .spinner-icon` moves (`animation: nprogress-spinner 400ms linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/styles/css/nprogress.css:55
`.fade-bottom-enter-active` moves (`transition: opacity 0.25s, transform 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/styles/css/transition.css:28
`.zoom-fade-enter-active` moves (`transition: transform 0.2s, opacity 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/styles/css/transition.css:58
`.zoom-out-enter-active` moves (`transition: opacity 0.1s ease-in-out, transform 0.15s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce. — frontend/src/styles/css/transition.css:74

What to do

Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.

Do you agree with this assessment?

AC7 · A11y enforcement4.0 / 10Weak✓ Tool-verified

Other · Accessibility — Whether accessibility is ENFORCED in the toolchain — an accessibility checker configured over the markup (an a11y lint rule set, e.g. eslint-plugin-jsx-a11y or vuejs-accessibility where the project lints JavaScript) and an automated accessibility assertion wired into tests or CI (axe/pa11y/Lighthouse or an equivalent) — on the Documented→Verified→Prevented ladder.

Method: Repo config/CI scan: an accessibility checker configured over the markup (an a11y lint rule set such as eslint-plugin-jsx-a11y / vuejs-accessibility where JavaScript is linted) and an automated accessibility assertion in tests or CI (axe/pa11y/Lighthouse or equivalent), graded on the Documented→Verified→Prevented rungs. Deterministic, presence/rung detection.

Coverage: Population: the repository's own tooling configuration — lint config, test and CI files — NOT the markup. It is read for a configured accessibility checker and an automated accessibility assertion (axe/pa11y/Lighthouse, or a native-toolkit equivalent), and it credits an INVOCATION, never a mention: a licence filename, an import comment or a doc reference earns no rung. Enforcement configured entirely outside the repository leaves no evidence here and cannot be credited.

No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 95 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

What to do

Enforce accessibility in the toolchain: add eslint-plugin-vuejs-accessibility, then assert with jest-axe in tests, then gate axe/pa11y/Lighthouse in CI.

Do you agree with this assessment?

AX10 · Code composition6.8 / 10Adequate✓ Tool-verified

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.

Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.

Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.

Do you agree with this assessment?

C1 · Data Protection3.5 / 10Weak✓ Tool-verified

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

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

What to do

Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, Azure Key Vault, GCP KMS / REDACTED Manager, HashiCorp Vault) and encrypt the most sensitive columns (typeorm-encrypted, prisma-field-encryption, mongoose-field-encryption or MongoDB CSFLE) — partial coverage still leaves gaps.
Enforce HTTPS (serve through https.createServer / NestJS httpsOptions, or redirect plain HTTP with express-sslify behind your TLS terminator) so data in transit is always encrypted.

Do you agree with this assessment?

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

Other · Security — Whether access is authorized by default — a framework authorization attribute/decorator or policy, or imperative guard methods (throw-on-violation) called from handlers.

Method: Roslyn scan: [Authorize] usage and authorization policies, plus imperative throw-on-violation guard methods detected via syntax. Deterministic.

Do you agree with this assessment?

DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

Do you agree with this assessment?

DM11 · Constructible invalid state9.1 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

`ApiEndpoint`'s public constructor takes `id`, `path`, `method`, `action`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was checked for any branch (`if`, ternary, `switch`) or any call — it has neither, only assignments; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ApiEndpoint` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/domain/api-endpoint.model.ts:12

What to do

Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.

Do you agree with this assessment?

DM2 · Strongly-typed ids3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — How much of the domain uses strongly-typed ids vs raw Guid/string/int — adoption curve, not all-or-nothing.

Method: Roslyn (DDD-gated): strongly-typed id adoption on domain entities/events; raw Guid/int/string ids counted versus wrapped types. An id wrapper is recognised by VALUE SEMANTICS, not by being a struct — a record struct, a record class (`record ApartmentId(Guid Value)`) or a class declared by a typed-id base (`class MemberId : TypedIdValueBase`) all count, while a plain mutable class (reference equality) and a verb-phrase query record (`GetCustomerById`) do not. Deterministic, adoption percentage.

Coverage: Population: id-like members by *Id/*Key NAME suffix; strongly-typed-ID shape then checked semantically — non-suffixed identifiers are not seen.

`UserCreatedEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/events/user-created.event.ts:5
`UserDeletedEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/events/user-deleted.event.ts:5
`RoleDeletedEvent.roleId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/events/role-deleted.event.ts:5
`TokenGeneratedEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/events/token-generated.event.ts:7
`TokenGeneratedEvent.requestId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/events/token-generated.event.ts:13
`TokensEntity.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.entity.ts:16
`TokensEntity.requestId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.entity.ts:22
`UserLoggedInEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:5
`UserLoggedInEvent.requestId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:11
`MenuDeletedEvent.menuId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/events/menu-deleted.event.ts:5
`Menu.i18nKey` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts:32
`OperationLog.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/log-audit/operation-log/domain/operation-log.model.ts:6
`OperationLog.requestId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that. — backend/apps/base-system/src/lib/bounded-contexts/log-audit/operation-log/domain/operation-log.model.ts:11

What to do

Adopt strongly-typed ids across the domain — finish the migration or document the boundary; primitive ids invite transposed-argument bugs.

Do you agree with this assessment?

DM4 · Rich vs anemic model3.0 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

`AccessKey` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.model.ts:12
`ApiEndpoint` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/domain/api-endpoint.model.ts:3
`User` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.ts:20
`TokensEntity` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.entity.ts:12
`Domain` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.model.ts:15
`Menu` is an aggregate/entity with 22 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts:15
`Role` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.model.ts:15
`OperationLog` is an aggregate/entity with 16 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — backend/apps/base-system/src/lib/bounded-contexts/log-audit/operation-log/domain/operation-log.model.ts:5

What to do

Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.

Do you agree with this assessment?

DM5 · Encapsulated state2.2 / 10Critical✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

`AccessKey` exposes publicly writable state (id, domain, AccessKeyID, AccessKeySecret, status, createdAt, and 1 more). — backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.model.ts:12
`User` exposes publicly writable state (createdAt, createdBy). — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.ts:20
`TokensEntity` exposes publicly writable state (status). — backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.entity.ts:12
`Domain` exposes publicly writable state (id, code, name, description, status, createdAt, and 1 more). — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.model.ts:15
`Menu` exposes publicly writable state (id, menuName, menuType, routeName, routePath, component, and 16 more). — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts:15
`Role` exposes publicly writable state (id, code, name, description, pid, status, and 2 more). — backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.model.ts:15

What to do

Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).

Do you agree with this assessment?

DM6 · Domain ↔ infrastructure boundary4.1 / 10Weak✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain aggregate fused to a persistence ORM (TypeORM/Prisma/MikroORM/Sequelize/Mongoose) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

`backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.model.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.read.model.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-created.event.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-created.event.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-deleted.event.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-deleted.event.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.read.model.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts` (domain layer) depends on `@nestjs/common` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts:1
`backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts:3
`backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-delete.command.handler.ts` (domain layer) depends on `@nestjs/common` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-delete.command.handler.ts:1
`backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts` (domain layer) depends on `@nestjs/common` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts:1
`backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts:3
`backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.model.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.read.model.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/iam/domain/queries/page-domains.query.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/domain/queries/page-domains.query.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.read.model.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.model.ts:2
`backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.read.model.ts:2

What to do

Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

ED5 · Idempotency10.0 / 10Exemplary◐ Sampled · advisory

Other · Readiness — Whether retry-prone mutations (command handlers + message/event consumers) are idempotent so an at-least-once redelivery or client retry doesn't double-apply the effect — heuristic at-risk detection confirmed by language model, advisory.

Method: Roslyn heuristic (any mutation, ungated): command handlers and message/event consumers that mutate persistent state without a visible idempotency guard (exists/dedup check, upsert, idempotency-key/inbox, conditional/versioned write, fixed-value set) flagged as at-risk; each at-risk candidate then confirmed or cleared by a language model as genuinely non-idempotent versus naturally-idempotent. Advisory without a model (heuristic-only, degraded), per-candidate judged with one.

Coverage: Population: retry-prone mutations — command handlers (CQRS write side) + message/event consumers (IConsumer/I*EventHandler) — that mutate persistent state; runs on any repo with mutations, not only event-driven ones. The at-risk subset (no obvious guard) is a HEURISTIC candidate set, each then LLM-JUDGED non-idempotent vs safe; a handler outside those conventions, or a guard the LLM can't confirm, is bounded by the sample. Degrades to heuristic-only when no model is configured.

Do you agree with this assessment?

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

IC1 · Incompleteness & stubs8.1 / 10Strong✓ Tool-verified

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

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

`handle` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-validation.event.handler.ts:14
`defaultIsOwn` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — backend/libs/infra/casbin/src/decorators/use-permissions.decorator.ts:6
`updatePkg` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work. — frontend/packages/scripts/src/commands/update-pkg.ts:3
A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead. (×3) — frontend/src/router/elegant/imports.ts:1, frontend/src/router/elegant/routes.ts:1, frontend/src/router/elegant/transform.ts:1

What to do

Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.

Do you agree with this assessment?

M1 · Documentation (README)6.2 / 10Adequate✓ Tool-verified

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

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

What to do

Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 10 of 11 project(s) that lack one — worth up to 1.8 pts.

Do you agree with this assessment?

M2 · Architecture documentation2.0 / 10Critical✓ Tool-verified

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

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

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

What to do

Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

README.md names `database.config.ts`, but no file or folder `database.config.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:200
README.md names `jwt.config.ts`, but no file or folder `jwt.config.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:202
README.md names `.env.production`, but no file or folder `.env.production` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — README.md:207
backend/README.md links to `LICENSE`, but `backend/LICENSE` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — backend/README.md:75
frontend/README.en_US.md links to `./LICENSE`, but `frontend/LICENSE` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — frontend/README.en_US.md:9

What to do

Reconcile the README with reality: README.md names `database.config.ts`, but no file or folder `database.config.ts` exists; README.md names `jwt.config.ts`, but no file or folder `jwt.config.ts` exists; README.md names `.env.production`, but no file or folder `.env.production` exists; backend/README.md links to `LICENSE`, but `backend/LICENSE` does not exist; frontend/README.en_US.md links to `./LICENSE`, but `frontend/LICENSE` does not exist.

Do you agree with this assessment?

P1 · CI/CD gates0.0 / 10Critical✓ Tool-verified

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

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

No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

What to do

Add a CI workflow that builds and runs the test suite on every push/PR.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

P2 · Observability7.0 / 10Strong✓ Tool-verified

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

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

Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `frontend/packages/scripts`.
`backend/local-route.migrate.ts` reports through `console.*` at line 67 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/local-route.migrate.ts:67
`backend/local-route.migrate.ts` reports through `console.*` at line 194 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/local-route.migrate.ts:194
`backend/local-route.migrate.ts` reports through `console.*` at line 200 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/local-route.migrate.ts:200
`backend/local-route.migrate.ts` reports through `console.*` at line 203 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/local-route.migrate.ts:203
`backend/local-route.migrate.ts` reports through `console.*` at line 204 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/local-route.migrate.ts:204
`backend/apps/base-demo/src/base-demo.controller.ts` reports through `console.*` at line 116 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/apps/base-demo/src/base-demo.controller.ts:116
`backend/apps/base-system/src/lib/bounded-contexts/access-key/application/query-handlers/access_keys.bootstrap.handler.ts` reports through `console.*` at line 25 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/apps/base-system/src/lib/bounded-contexts/access-key/application/query-handlers/access_keys.bootstrap.handler.ts:25
`backend/libs/infra/casbin/src/guards/authz.guard.ts` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/libs/infra/casbin/src/guards/authz.guard.ts:66
`backend/libs/logger/src/logger.module.ts` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/libs/logger/src/logger.module.ts:52
`backend/libs/logger/src/logger.module.ts` reports through `console.*` at line 129 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/libs/logger/src/logger.module.ts:129
`backend/libs/shared/prisma/src/prisma.service.ts` reports through `console.*` at line 26 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/libs/shared/prisma/src/prisma.service.ts:26
`backend/libs/shared/prisma/src/prisma.service.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. — backend/libs/shared/prisma/src/prisma.service.ts:27
`backend/libs/shared/prisma/src/prisma.service.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/libs/shared/prisma/src/prisma.service.ts:28
`backend/libs/utils/src/tree.util.ts` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — backend/libs/utils/src/tree.util.ts:44
`frontend/src/plugins/app.ts` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — frontend/src/plugins/app.ts:9
`frontend/src/router/elegant/transform.ts` reports through `console.*` at line 134 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — frontend/src/router/elegant/transform.ts:134
`frontend/src/utils/service.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — frontend/src/utils/service.ts:16

What to do

Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Add OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) so requests are traceable across the system, not just health-probable.

Do you agree with this assessment?

P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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

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

No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

Run what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — locally for now, since there is no CI pipeline here yet, and as a step of the first workflow you add so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.

Do you agree with this assessment?

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

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

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

`readFileSync` in `gitCommitVerify` 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. — frontend/packages/scripts/src/commands/git-commit.ts:73
`existsSync` in `generateRoute` 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. — frontend/packages/scripts/src/commands/router.ts:70
`mkdirSync` in `generateRoute` 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. — frontend/packages/scripts/src/commands/router.ts:71

What to do

TypeScript/JavaScript: use the promise APIs (fs/promises, a promisified child_process.execFile, the async zlib/crypto functions) and await them instead of the *Sync variants.

Do you agree with this assessment?

R1 · Type Safety10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

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

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

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

19 duplicated blocks under backend/apps/base-system/src/lib/bounded-contexts/ have copies in at least two of the sibling directories access-key, api-endpoint, iam, log-audit — 6 of them are reported below, and 13 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.read.model.ts:38
13 duplicated blocks under backend/apps/base-system/src/lib/bounded-contexts/iam/ have copies in at least two of the sibling directories authentication, domain, menu, role, tokens — 6 of them are reported below, and 7 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 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. — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/command-handlers/user-update.command.handler.ts:12
11 duplicated blocks under backend/apps/base-system/src/infra/bounded-contexts/ have copies in at least two of the sibling directories access-key, api-endpoint, iam, log-audit — 5 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 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. — backend/apps/base-system/src/infra/bounded-contexts/iam/domain/repository/domain.read.pg.repository.ts:26
9 duplicated blocks under backend/apps/base-system/src/api/ have copies in at least two of the sibling directories access-key, endpoint, iam, log-audit — 7 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — backend/apps/base-system/src/api/endpoint/rest/endpoint.controller.ts:35
8 duplicated blocks under frontend/src/views/ have copies in at least two of the sibling directories access-key, log, manage — 7 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — frontend/src/views/access-key/index.vue:65
5 duplicated blocks under backend/apps/base-system/src/infra/bounded-contexts/iam/ have copies in at least two of the sibling directories authentication, domain, menu, role — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:69
backend/libs/infra/casbin/src/services/authz-rbac.service.ts:14 · backend/libs/infra/casbin/src/services/authz.service.ts:13 — 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. — backend/libs/infra/casbin/src/services/authz-rbac.service.ts:14
backend/apps/base-demo/src/base-demo.module.ts:1 · backend/apps/base-system/src/app.module.ts:1 — these 2 files are line-for-line copies of one another — 84 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. — backend/apps/base-demo/src/base-demo.module.ts:1
backend/apps/base-system/src/api/iam/rest/role.controller.ts:31 · backend/apps/base-system/src/api/iam/rest/user.controller.ts:31 — the two spans are one implementation copied and then locally edited — 332 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. — backend/apps/base-system/src/api/iam/rest/role.controller.ts:31
frontend/src/views/access-key/index.vue:65 · frontend/src/views/manage/user/index.vue:90 — 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. — frontend/src/views/access-key/index.vue:65
frontend/src/views/manage/role/modules/api-endpoint-auth-modal.vue:15 · frontend/src/views/manage/role/modules/menu-auth-modal.vue:13 — the two spans are one implementation copied and then locally edited — 326 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. — frontend/src/views/manage/role/modules/api-endpoint-auth-modal.vue:15
backend/libs/infra/casbin/src/services/authz-management.service.ts:17 · backend/libs/infra/casbin/src/services/authz.service.ts:313 — 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. — backend/libs/infra/casbin/src/services/authz-management.service.ts:17
backend/libs/infra/casbin/src/services/authz-management.service.ts:558 · backend/libs/infra/casbin/src/services/authz.service.ts:858 — 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. — backend/libs/infra/casbin/src/services/authz-management.service.ts:558
backend/apps/base-system/src/infra/bounded-contexts/log-audit/login-log/repository/login-log.read.pg.repository.ts:15 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/operation-log/repository/operation-log.read.pg.repository.ts:15 — 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. — backend/apps/base-system/src/infra/bounded-contexts/log-audit/login-log/repository/login-log.read.pg.repository.ts:15
backend/libs/infra/casbin/src/services/authz-management.service.ts:378 · backend/libs/infra/casbin/src/services/authz-management.service.ts:521 · backend/libs/infra/casbin/src/services/authz.service.ts:678 · backend/libs/infra/casbin/src/services/authz.service.ts:821 — the 4 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. — backend/libs/infra/casbin/src/services/authz-management.service.ts:378
backend/apps/base-system/src/api/iam/rest/domain.controller.ts:31 · backend/apps/base-system/src/api/iam/rest/role.controller.ts:31 · backend/apps/base-system/src/api/iam/rest/user.controller.ts:31 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — backend/apps/base-system/src/api/iam/rest/domain.controller.ts:31
backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:69 · backend/apps/base-system/src/infra/bounded-contexts/iam/role/repository/role.read.pg.repository.ts:38 — 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. — backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:69
backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.read.model.ts:38 · backend/apps/base-system/src/lib/bounded-contexts/log-audit/login-log/domain/login-log.read.model.ts:21 — 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. — backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.read.model.ts:38
frontend/src/views/access-key/modules/access-key-operate-drawer.vue:55 · frontend/src/views/manage/role/modules/role-operate-drawer.vue:59 · frontend/src/views/manage/user/modules/user-operate-drawer.vue:61 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — frontend/src/views/access-key/modules/access-key-operate-drawer.vue:55
backend/apps/base-system/src/infra/bounded-contexts/iam/domain/repository/domain.read.pg.repository.ts:26 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/login-log/repository/login-log.read.pg.repository.ts:30 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/operation-log/repository/operation-log.read.pg.repository.ts:30 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — backend/apps/base-system/src/infra/bounded-contexts/iam/domain/repository/domain.read.pg.repository.ts:26
backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:118 · backend/apps/base-system/src/infra/bounded-contexts/iam/role/repository/role.read.pg.repository.ts:15 — 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. — backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:118
backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/command-handlers/user-update.command.handler.ts:12 · backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts:15 — 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. — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/command-handlers/user-update.command.handler.ts:12
backend/libs/infra/casbin/src/services/authz-api.ts:229 · backend/libs/infra/casbin/src/services/authz-api.ts:259 — 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. — backend/libs/infra/casbin/src/services/authz-api.ts:229
frontend/src/views/_builtin/login/modules/code-login.vue:10 · frontend/src/views/_builtin/login/modules/register.vue:10 — the two spans are one implementation copied and then locally edited — 142 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. — frontend/src/views/_builtin/login/modules/code-login.vue:10
backend/apps/base-system/src/api/iam/rest/menu.controller.ts:136 · backend/apps/base-system/src/api/iam/rest/role.controller.ts:98 · backend/apps/base-system/src/api/iam/rest/user.controller.ts:100 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — backend/apps/base-system/src/api/iam/rest/menu.controller.ts:136
frontend/src/views/log/login/index.vue:10 · frontend/src/views/log/operation/index.vue:10 — 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. — frontend/src/views/log/login/index.vue:10
backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-update.command.handler.ts:23 · backend/apps/base-system/src/lib/bounded-contexts/iam/role/application/command-handlers/role-update.command.handler.ts:33 — 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. — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-update.command.handler.ts:23
backend/apps/base-system/src/api/iam/rest/domain.controller.ts:95 · backend/apps/base-system/src/api/iam/rest/menu.controller.ts:138 · backend/apps/base-system/src/api/iam/rest/role.controller.ts:100 · backend/apps/base-system/src/api/iam/rest/user.controller.ts:102 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — backend/apps/base-system/src/api/iam/rest/domain.controller.ts:95
backend/libs/infra/casbin/src/services/authz-api.ts:303 · backend/libs/infra/casbin/src/services/authz-api.ts:350 · backend/libs/infra/casbin/src/services/authz-api.ts:412 · backend/libs/infra/casbin/src/services/authz-api.ts:438 — all 4 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. — backend/libs/infra/casbin/src/services/authz-api.ts:303
frontend/src/views/manage/role/modules/role-operate-drawer.vue:9 · frontend/src/views/manage/user/modules/user-operate-drawer.vue:9 — 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. — frontend/src/views/manage/role/modules/role-operate-drawer.vue:9
backend/apps/base-system/src/api/endpoint/rest/endpoint.controller.ts:57 · backend/apps/base-system/src/api/iam/rest/menu.controller.ts:49 — 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. — backend/apps/base-system/src/api/endpoint/rest/endpoint.controller.ts:57
backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-create.command.handler.ts:23 · backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-update.command.handler.ts:29 — 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. — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-create.command.handler.ts:23
backend/apps/base-system/src/api/access-key/rest/access_key.controller.ts:73 · backend/apps/base-system/src/api/iam/rest/domain.controller.ts:97 · backend/apps/base-system/src/api/iam/rest/menu.controller.ts:140 · backend/apps/base-system/src/api/iam/rest/role.controller.ts:102 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — backend/apps/base-system/src/api/access-key/rest/access_key.controller.ts:73
frontend/src/layouts/modules/global-menu/modules/reversed-horizontal-mix-menu.vue:35 · frontend/src/layouts/modules/global-menu/modules/vertical-mix-menu.vue:56 — 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. — frontend/src/layouts/modules/global-menu/modules/reversed-horizontal-mix-menu.vue:35
frontend/src/views/access-key/modules/access-key-search.vue:7 · frontend/src/views/log/login/modules/login-log-search.vue:5 · frontend/src/views/log/operation/modules/operation-log-search.vue:5 — 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. — frontend/src/views/access-key/modules/access-key-search.vue:7
backend/apps/base-demo/src/main.ts:18 · backend/apps/base-system/src/main.ts:69 — 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. — backend/apps/base-demo/src/main.ts:18
backend/libs/infra/casbin/src/services/authz-api.ts:65 · backend/libs/infra/casbin/src/services/authz-api.ts:288 · backend/libs/infra/casbin/src/services/authz-api.ts:397 — all 3 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. — backend/libs/infra/casbin/src/services/authz-api.ts:65
frontend/src/views/manage/menu/index.vue:90 · frontend/src/views/manage/role/index.vue:68 · frontend/src/views/manage/user/index.vue:86 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — frontend/src/views/manage/menu/index.vue:90
frontend/src/views/access-key/modules/access-key-operate-drawer.vue:73 · frontend/src/views/manage/menu/modules/menu-operate-modal.vue:239 · frontend/src/views/manage/role/modules/role-operate-drawer.vue:77 · frontend/src/views/manage/user/modules/user-operate-drawer.vue:103 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — frontend/src/views/access-key/modules/access-key-operate-drawer.vue:73
backend/apps/base-system/src/infra/bounded-contexts/access-key/repository/access_key.read.pg.repository.ts:14 · backend/apps/base-system/src/infra/bounded-contexts/api-endpoint/api-endpoint/repository/api-endpoint.read.pg.repository.ts:11 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/login-log/repository/login-log.read.pg.repository.ts:11 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/operation-log/repository/operation-log.read.pg.repository.ts:11 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — backend/apps/base-system/src/infra/bounded-contexts/access-key/repository/access_key.read.pg.repository.ts:14

What to do

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

Do you agree with this assessment?

R11 · Import Boundaries9.4 / 10Exemplary✓ Tool-verified

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

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

backend/apps/base-demo/src/base-demo.module.ts:11 imports @nestjs/throttler/dist/throttler-storage-record.interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — backend/apps/base-demo/src/base-demo.module.ts:11
backend/apps/base-system/src/app.module.ts:7 imports @nestjs/throttler/dist/throttler-storage-record.interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — backend/apps/base-system/src/app.module.ts:7
frontend/packages/materials/src/libs/page-tab/shared.ts:1 imports @sa/color, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies. — frontend/packages/materials/src/libs/page-tab/shared.ts:1

What to do

Fix the listed violations: import through the target package's declared public entry rather than a deep path into its internals or a relative path into its directory (2 rows); declare the workspace packages these files import in the importing package's own REDACTED dependencies (1 row) — those imports are already bare package specifiers, so the import statements do not change, only the manifest.

Do you agree with this assessment?

R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

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

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

transformRouteToSysMenu has cyclomatic complexity 14 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 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. — backend/local-route.migrate.ts:77
removeFilteredPolicy has cyclomatic complexity 13 and cognitive complexity 12; 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. — backend/libs/infra/casbin/src/adapter/casbin-prisma.adapter.ts:154
validateKey has cyclomatic complexity 12 and cognitive complexity 10; 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. — backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts:56

Do you agree with this assessment?

R3 · Large Files9.5 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

frontend/packages/color/src/constant/name.ts has 1578 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/packages/color/src/constant/name.ts:1
backend/libs/infra/casbin/src/services/authz.service.ts has 920 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend/libs/infra/casbin/src/services/authz.service.ts:1
backend/libs/infra/casbin/src/services/authz-management.service.ts has 639 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend/libs/infra/casbin/src/services/authz-management.service.ts:1
backend/libs/infra/casbin/src/services/authz-api.ts has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — backend/libs/infra/casbin/src/services/authz-api.ts:1
frontend/src/locales/langs/en-us.ts has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/locales/langs/en-us.ts:1
frontend/src/locales/langs/zh-cn.ts has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/locales/langs/zh-cn.ts:1
frontend/src/views/manage/menu/modules/menu-operate-modal.vue has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — frontend/src/views/manage/menu/modules/menu-operate-modal.vue:1

What to do

Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.

Do you agree with this assessment?

R4 · Test Coverage5.5 / 10Adequate✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×40) — frontend/packages/color/src/constant/name.ts:1, frontend/src/locales/langs/en-us.ts:1, frontend/src/locales/langs/zh-cn.ts:1, …

What to do

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

Do you agree with this assessment?

R6 · Tooling10.0 / 10Exemplary✓ Tool-verified

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

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

Do you agree with this assessment?

R7 · Dead Code7.4 / 10Strong✓ Tool-verified

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

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

Unreachable from the 27 application, 31 tooling and 4 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 (27 application, 31 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (backend/prisma/seeds/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 (×7) — backend/prisma/seeds/sys/sysMenu.ts, backend/prisma/seeds/sys/casbinRule.ts, backend/prisma/seeds/sys/sysRoleMenu.ts, …
no import path from any entry point (27 application, 31 tooling, 4 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 (×9) — backend/local-route.migrate.ts, frontend/packages/hooks/src/use-request.ts, backend/libs/infra/interceptors/src/transform.interceptor.ts, …
no import path from any entry point (27 application, 31 tooling, 4 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (backend/prisma/seeds/index.ts, backend/prisma/seeds/sys/casbinRule.ts, backend/prisma/seeds/sys/sysDomain.ts and 5 more) — 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 — backend/prisma/seeds/helper.ts
Nothing imports this binding — it is safe to review for removal. (×15) — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.read.model.ts:50, backend/libs/constants/src/rest.constant.ts:5, frontend/packages/axios/src/shared.ts:3, …
Nothing ultimately consumes this binding: its only referrer is the re-export in backend/libs/infra/crypto/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in backend/libs/infra/crypto/src/index.ts in the same commit, or the barrel will import a name that no longer exists. (×3) — backend/libs/infra/crypto/src/decorators/crypto.decorator.ts:47, backend/libs/infra/crypto/src/decorators/crypto.decorator.ts:58, backend/libs/infra/crypto/src/decorators/crypto.decorator.ts:68
Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/packages/color/src/constant/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/packages/color/src/constant/index.ts in the same commit, or the barrel will import a name that no longer exists. — frontend/packages/color/src/constant/name.ts:1576
Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/src/plugins/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/src/plugins/index.ts in the same commit, or the barrel will import a name that no longer exists. — frontend/src/plugins/app.ts:6
Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/src/service/api/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/src/service/api/index.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — frontend/src/service/api/auth.ts:46, frontend/src/service/api/system-manage.ts:59

What to do

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

Do you agree with this assessment?

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

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

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

Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. — frontend/uno.config.ts:4
Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED. (×2) — REDACTED:1, frontend/packages/uno-preset/src/index.ts:3
Declared in REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

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

Do you agree with this assessment?

R9 · Circular Imports2.3 / 10Critical✓ Tool-verified

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

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

frontend/src/hooks/common/router.ts → frontend/src/router/index.ts → frontend/src/router/guard/index.ts → frontend/src/router/guard/route.ts → frontend/src/store/modules/auth/index.ts → frontend/src/hooks/common/router.ts (one verified cycle inside a mutually-dependent group of 62 files) — frontend/src/hooks/common/router.ts:4

What to do

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

Do you agree with this assessment?

S1 · Web-Security Posture6.0 / 10Adequate✓ Tool-verified

Other · Security — Read from this repository's JavaScript/TypeScript source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS (certificate validation, protocol version) — facts about code that hold whether or not it serves anything itself. This repository commits the configuration that serves its own HTTP surface, so that configuration was read in full for the security response headers it sets. The server controls — HTTPS enforcement, HSTS, cookie flags, input validation — are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. (×3) — backend/libs/bootstrap/src/api/collect-api-data.ts:125, backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts:47, backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts:49
None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — frontend/nginx.conf:42

What to do

Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key. This repository constructs a collision-broken hash (MD5/SHA1) at 3 sites, not one: `backend/libs/bootstrap/src/api/collect-api-data.ts:125` (createHash("md5")), `backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts:47` (crypto-js MD5), `backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts:49` (crypto-js SHA1). Each is a separate decision — fixing only the line this row cites leaves the others in place.
Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.
`getHtmlBuildTime` 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 })`. — frontend/src/plugins/app.ts:91

What to do

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X23 · Unguarded diagnostic materialisation4.7 / 10Weak✓ Tool-verified

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

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

`debug` at line 105 is called with an argument built by `JSON.stringify(options)` (line 108), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because 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. — backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:105
`debug` at line 164 is called with an argument built by `JSON.stringify(data.data,)` (line 165), 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. — backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:164
`debug` at line 177 is called with an argument built by `JSON.stringify(data,)` (line 178), 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. — backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:177
`debug` at line 76 is called with an argument built by `JSON.stringify(deserialized)` (line 76), 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. — backend/libs/infra/crypto/src/services/crypto.service.ts:76

What to do

Each finding names the diagnostic call and the expression inside its argument whose cost scales with a collection. Confirm from the two that the argument is built before the call — that is JavaScript's evaluation order, not a guess — then put the construction behind the level check the logger offers (`if (logger.isLevelEnabled('debug'))` for pino and winston, `isDebugEnabled()` for log4js, the repository's own debug flag where it has one), or hand the logger the object and a format string (`logger.debug({ payload }, 'raw request')`) so the serialising happens only when the line is written. Moving the call is not the fix: it is the join/projection/stringify in the argument that is paid, wherever the call sits.

Do you agree with this assessment?

X24 · Document value interpolated into markup unescaped3.1 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

`item` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — frontend/src/plugins/loading.ts:31
`primaryColor` is text this program did not author, and it is written into a script or style context through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute. — frontend/src/plugins/loading.ts:36
`logoWithClass` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — frontend/src/plugins/loading.ts:37
`$t('system.title')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — frontend/src/plugins/loading.ts:43

What to do

Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

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

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

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

Do you agree with this assessment?

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

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

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

An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×3) — backend/apps/base-system/src/api/iam/rest/authentication.controller.ts:42, backend/apps/base-system/src/api/iam/rest/authentication.controller.ts:70, frontend/packages/utils/src/storage.ts:33

What to do

Swallowed exception (empty catch)

Do you agree with this assessment?

X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

Do you agree with this assessment?

X4 · Structured logging2.1 / 10Critical✓ Tool-verified

Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.

Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `REDACTED` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.

`log` at line 129 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/apps/base-system/src/main.ts:129
`log` at line 16 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. (×5) — backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-validation.event.handler.ts:16, backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/event-handlers/role-deleted.event.handler.ts:16, backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/event-handlers/domain-deleted.event.handler.ts:16, …
`log` at line 26 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. (×2) — backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-deleted.event.handler.ts:26, backend/libs/infra/adapter/src/fastify.adapter.ts:26
`log` at line 29 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-created.event.handler.ts:29
`log` at line 35 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/application/event-handlers/api-endpoint.event.handler.ts:35
`log` at line 41 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. (×2) — backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/application/event-handlers/api-endpoint.event.handler.ts:41, backend/libs/shared/ip2region/src/ip2region.service.ts:41
`log` at line 11 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. (×2) — backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/event-handlers/user-created.event.handler.ts:11, backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/event-handlers/menu-deleted.event.handler.ts:11
`log` at line 21 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/apps/base-system/src/lib/bounded-contexts/iam/role/application/event-handlers/role-deleted.event.handler.ts:21
`log` at line 47 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/bootstrap/src/api/collect-api-data.ts:47
`debug` at line 105 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:105
`debug` at line 146 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:146
`error` at line 148 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:148
`debug` at line 164 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:164
`debug` at line 177 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:177
`error` at line 184 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:184
`debug` at line 47 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:47
`debug` at line 51 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:51
`debug` at line 55 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:55
`debug` at line 68 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:68
`debug` at line 72 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:72
`debug` at line 76 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:76
`debug` at line 148 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:148
`debug` at line 155 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:155
`debug` at line 188 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:188
`debug` at line 210 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/infra/crypto/src/services/crypto.service.ts:210
`log` at line 30 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/shared/ip2region/src/ip2region.service.ts:30
`log` at line 49 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/shared/ip2region/src/ip2region.service.ts:49
`warn` at line 55 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.warn({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.warn('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way. — backend/libs/shared/ip2region/src/ip2region.service.ts:55

What to do

Interpolated log message defeats structured logging

Do you agree with this assessment?

X5 · Nullable reference types9.6 / 10Exemplary✓ Tool-verified

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

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

34/35 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.6 `!` null assertions per 1k TypeScript source lines — 15 assertion(s) across the 26627 source line(s) of the 475 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: frontend/packages/color/src/palette/recommend.ts (3), frontend/src/hooks/common/table.ts (3), frontend/src/hooks/common/echarts.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

What to do

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

Do you agree with this assessment?

WCAG coverage — what static analysis assessed

Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).

Dimension	WCAG 2.2 A/AA criteria	Coverage
AC1 · Text alternatives	1.1.1, 1.2.2, 1.2.5	Partial signal
AC2 · Forms & labels	1.3.1, 3.3.2, 4.1.2	Partial signal
AC3 · Page structure	1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2	Partial signal
AC4 · Keyboard semantics	2.1.1, 2.4.3	Partial signal
AC6 · Visual & motion safety	1.4.3, 2.4.7	Partial — literal CSS only
AC7 · A11y enforcement	enforcement — no page criterion	Enforcement posture (process)

Not statically assessed — these 40 Level A/AA criteria need runtime or manual evaluation (WCAG-EM): 1.2.1, 1.2.3, 1.2.4, 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.4.1, 1.4.2, 1.4.5, 1.4.10, 1.4.11, 1.4.12, 1.4.13, 2.1.2, 2.1.4, 2.2.2, 2.3.1, 2.4.4, 2.4.5, 2.4.6, 2.4.11, 2.5.1, 2.5.2, 2.5.3, 2.5.4, 2.5.7, 2.5.8, 3.1.2, 3.2.1, 3.2.2, 3.2.3, 3.2.4, 3.2.6, 3.3.1, 3.3.3, 3.3.4, 3.3.7, 3.3.8, 4.1.3.

Reference — by lens

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

Lens	Score	Rating	Impact
Code Health	56%	Adequate — gated by X4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture	70%	Adequate — gated by R9	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity	33%	Weak — gated by D34, M2, M4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness	19%	Critical — gated by D9, D13, R8, P1, P3, P5	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security	57%	Adequate — gated by D29, D30, C1	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling	40%	Weak — gated by DM4, DM5, DM2	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Accessibility	26%	Weak — gated by AC1, AC4	Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance	60%	Adequate	Strongest area.

Not evidenced — 4 control(s) we could not find positive evidence for

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

C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo

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

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

AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
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).
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — redis Pulling postgres Pulling pgbouncer Pulling pgbouncer Error Get "https://registry-1.docker.io/v2/": Forbidden redis Error context canceled postgres Error context canceled Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: backend Skipped - No image to be pulled db-init Skipped - No image to be pulled redis Pulling postgres Pulling pgbouncer Pulling redis Error Get "https://registry-1.docker.io/v2/": Forbidden pgbouncer Error Get "https://registry-1.docker.io/v2/": Forbidden postgres Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
D11 Test Reliability — No tests discovered
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ projects each declaring an entity of their own. Aggregate roots were found in only one source directory (base-system), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.ts), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — 13 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D4 Code Duplication — This repository's production source (.ts) 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.
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in backend/ ran and not one test passed (FAIL apps/base-demo/src/base-demo.controller.spec.ts), so the coverage report describes the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
DM3 Integration-event coupling — no integration events detected — coupling check not applicable
DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (36 CQRS handler(s))
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — no CI workflow found
P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: backend/apps/base-system/src/main.ts:72 (NestFactory.create))
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not applicable: TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
R5 Dependency Freshness — uses a bun lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 108 finding(s)

D30 · Dependency Vulnerabilities · High CVE · ×52

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

DM6 · Domain ↔ infrastructure boundary · Domain depends on infrastructure · ×18

Domain depends on infrastructure: access_key.model backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.model.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: access_key.read.model backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.read.model.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: access_key-created.event backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-created.event.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-created.event.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: access_key-deleted.event backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-deleted.event.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/events/access_key-deleted.event.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: user.read.model backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.read.model.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: user backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: domain-create.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts:1 — `backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts` (domain layer) depends on `@nestjs/common` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: domain-create.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts:3 — `backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-create.command.handler.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: domain-delete.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-delete.command.handler.ts:1 — `backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-delete.command.handler.ts` (domain layer) depends on `@nestjs/common` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: domain-update.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts:1 — `backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts` (domain layer) depends on `@nestjs/common` (import) — a HTTP module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: domain-update.command.handler backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts:3 — `backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/command-handlers/domain-update.command.handler.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: domain.model backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.model.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: domain.read.model backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.read.model.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: page-domains.query backend/apps/base-system/src/lib/bounded-contexts/iam/domain/queries/page-domains.query.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/iam/domain/queries/page-domains.query.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: menu.model backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: menu.read.model backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.read.model.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: role.model backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.model.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.
Domain depends on infrastructure: role.read.model backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.read.model.ts:2 — `backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.read.model.ts` (domain layer) depends on `@prisma/client` (import) — a persistence module; the domain should own a port and let an infrastructure adapter implement it.

D13 · REDACTED Scanning · Leaked secret · ×17

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

D28 · Secrets (history) · REDACTED · ×3

REDACTED
REDACTED
REDACTED

D30 · Dependency Vulnerabilities · Critical CVE · ×3

REDACTED
REDACTED
REDACTED

AC1 · Text alternatives · <img> without a text alternative · ×2

<img> without a text alternative frontend/src/components/custom/soybean-avatar.vue:9 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.
<img> without a text alternative frontend/src/views/home/modules/header-banner.vue:47 — An image with no alt (and no aria-label/aria-labelledby) is unreadable to assistive tech. Add alt — alt="" if it's purely decorative.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D30 · Dependency Vulnerabilities · High vulnerability · ×2

REDACTED
REDACTED

AC2 · Forms & labels · <textarea> without a programmatic label · ×1

<textarea> without a programmatic label frontend/src/layouts/modules/theme-drawer/modules/config-operation.vue:50 — This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.

AC3 · Page structure · <iframe> without a title · ×1

<iframe> without a title frontend/src/views/_builtin/iframe-page/[url].vue:21 — An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.

AC4 · Keyboard semantics · Click handler on a non-interactive <div> · ×1

Click handler on a non-interactive <div> frontend/src/layouts/modules/theme-drawer/components/layout-mode-card.vue:72 — A click handler on a plain element isn't keyboard-operable. Use a <button>, or add role + tabindex="0" + a key handler.

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

REDACTED

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

REDACTED

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

REDACTED

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

REDACTED

R8 · Dependency Hygiene · Unlisted import '@unocss/preset-wind3' · ×1

Unlisted import '@unocss/preset-wind3' frontend/uno.config.ts:4 — Imported but not declared in any reachable REDACTED — installs work only by hoisting accident.

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

Import cycle (5 files) frontend/src/hooks/common/router.ts:4 — frontend/src/hooks/common/router.ts → frontend/src/router/index.ts → frontend/src/router/guard/index.ts → frontend/src/router/guard/route.ts → frontend/src/store/modules/auth/index.ts → frontend/src/hooks/common/router.ts (one verified cycle inside a mutually-dependent group of 62 files)

Serious — 212 finding(s)

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

No test reaches this file frontend/packages/color/src/constant/name.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/locales/langs/en-us.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/locales/langs/zh-cn.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file backend/prisma/seeds/sys/sysMenu.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/store/modules/route/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/store/modules/route/shared.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/store/modules/tab/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/service/api/system-manage.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/hooks/common/table.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/views/manage/menu/modules/menu-operate-modal.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/store/modules/theme/shared.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/store/modules/tab/shared.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/hooks/common/echarts.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/store/modules/theme/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/views/manage/menu/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file backend/local-route.migrate.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/router/guard/route.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/packages/axios/src/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/packages/color/src/palette/antd.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/store/modules/app/index.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/views/manage/role/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/layouts/modules/global-tab/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file REDACTED:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/src/views/manage/user/index.vue:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
No test reaches this file frontend/packages/hooks/src/use-table.ts:1 — No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one.
+ 15 more in this group — see findings.md.

D30 · Dependency Vulnerabilities · Medium CVE · ×21

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

D17 · Explicit Debt · TodoComment · ×9

TodoComment backend/local-route.migrate.ts:202 — //TODO 更新删除还涉及业务待定 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment backend/apps/base-demo/src/base-demo.module.ts:166 — //TODO 拦截器极度影响性能有需要自行开启对性能有要求使用decorator形式每个接口手动加虽然麻烦点或者app.use指定路由统一使用相对代码量少 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment backend/apps/base-system/src/app.module.ts:168 — //TODO 拦截器极度影响性能有需要自行开启对性能有要求使用decorator形式每个接口手动加虽然麻烦点或者app.use指定路由统一使用相对代码量少 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment backend/apps/base-system/src/main.ts:98 — // TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-validation.event.handler.ts:15 — //TODO — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment backend/apps/base-system/src/lib/bounded-contexts/iam/role/application/event-handlers/user-logged-in.event.handler.ts:24 — //TODO means? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment backend/libs/infra/strategies/src/jwt.passport-strategy.ts:26 — //TODO 此处可用class-validator验证处理 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment frontend/src/service/api/system-manage.ts:146 — // TODO 超级管理员主动选择 domain管理员默认自身 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment frontend/src/service/api/system-manage.ts:165 — // TODO 超级管理员主动选择 domain管理员默认自身 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.

DM4 · Rich vs anemic model · Anemic entity · ×8

Anemic entity: AccessKey backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.model.ts:12 — `AccessKey` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: ApiEndpoint backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/domain/api-endpoint.model.ts:3 — `ApiEndpoint` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: User backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.ts:20 — `User` is an aggregate/entity with 11 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: TokensEntity backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.entity.ts:12 — `TokensEntity` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Domain backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.model.ts:15 — `Domain` is an aggregate/entity with 7 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Menu backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts:15 — `Menu` is an aggregate/entity with 22 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: Role backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.model.ts:15 — `Role` is an aggregate/entity with 8 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
Anemic entity: OperationLog backend/apps/base-system/src/lib/bounded-contexts/log-audit/operation-log/domain/operation-log.model.ts:5 — `OperationLog` is an aggregate/entity with 16 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.

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

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

AC6 · Visual & motion safety · Animation without a prefers-reduced-motion guard · ×6

Animation without a prefers-reduced-motion guard frontend/src/components/common/reload-button.vue:17 — <icon-ant-design-reload-outlined> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/plugins/loading.ts:39 — <div> moves — its `animate-spin` utility runs with no motion-safe:/motion-reduce: variant — and nothing reads prefers-reduced-motion for it, so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Gate it on @media (prefers-reduced-motion: no-preference) or motion-safe:.
Animation without a prefers-reduced-motion guard frontend/src/styles/css/nprogress.css:55 — `#nprogress .spinner-icon` moves (`animation: nprogress-spinner 400ms linear infinite`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/styles/css/transition.css:28 — `.fade-bottom-enter-active` moves (`transition: opacity 0.25s, transform 0.3s`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/styles/css/transition.css:58 — `.zoom-fade-enter-active` moves (`transition: transform 0.2s, opacity 0.3s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.
Animation without a prefers-reduced-motion guard frontend/src/styles/css/transition.css:74 — `.zoom-out-enter-active` moves (`transition: opacity 0.1s ease-in-out, transform 0.15s ease-out`) and nothing reads prefers-reduced-motion for it — no @media (prefers-reduced-motion) rule for this element, no reset this project loads — so a motion-sensitive user cannot turn it off (WCAG 2.3.3). Declare it under @media (prefers-reduced-motion: no-preference), or neutralise it under reduce.

D12 · Dependency Hygiene · Deprecated · ×6

Deprecated: crypto-js REDACTED:62 — crypto-js 4.2.0, declared in REDACTED, is marked deprecated by its publisher: "Active development of CryptoJS has been discontinued. This library is no longer maintained.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:95 — eslint 9.29.0, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: supertest REDACTED:105 — supertest 7.1.1, declared in REDACTED, is marked deprecated by its publisher: "Please upgrade to supertest v7.1.3+, see release notes at https://github.com/forwardemail/supertest/releases/tag/v7.1.3 - maintenance is supported by Forward Email @ https://forwardemail.net". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: vue-i18n REDACTED:69 — vue-i18n 11.1.2, declared in REDACTED, is marked deprecated by its publisher: "This version is NOT deprecated. Previous deprecation was a mistake.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: eslint REDACTED:89 — eslint 9.22.0, declared in REDACTED, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
Deprecated: crypto-js REDACTED:14 — crypto-js 4.2.0, declared in REDACTED, is marked deprecated by its publisher: "Active development of CryptoJS has been discontinued. This library is no longer maintained.". Replace it with the package or version that message names, or record why this one must stay.

DM5 · Encapsulated state · Mutable entity · ×6

Mutable entity: AccessKey backend/apps/base-system/src/lib/bounded-contexts/access-key/domain/access_key.model.ts:12 — `AccessKey` exposes publicly writable state (id, domain, AccessKeyID, AccessKeySecret, status, createdAt, and 1 more).
Mutable entity: User backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/user.ts:20 — `User` exposes publicly writable state (createdAt, createdBy).
Mutable entity: TokensEntity backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.entity.ts:12 — `TokensEntity` exposes publicly writable state (status).
Mutable entity: Domain backend/apps/base-system/src/lib/bounded-contexts/iam/domain/domain/domain.model.ts:15 — `Domain` exposes publicly writable state (id, code, name, description, status, createdAt, and 1 more).
Mutable entity: Menu backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts:15 — `Menu` exposes publicly writable state (id, menuName, menuType, routeName, routePath, component, and 16 more).
Mutable entity: Role backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/role.model.ts:15 — `Role` exposes publicly writable state (id, code, name, description, pid, status, and 2 more).

X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×4

Untrusted text written into markup unescaped frontend/src/plugins/loading.ts:31 — `item` is text this program did not author, and it is written into a quoted attribute value through markup built here with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped frontend/src/plugins/loading.ts:36 — `primaryColor` is text this program did not author, and it is written into a script or style context through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. A script or style context needs its own escaping (or a JSON serialiser that escapes `<`); better, pass the value through a data attribute.
Untrusted text written into markup unescaped frontend/src/plugins/loading.ts:37 — `logoWithClass` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
Untrusted text written into markup unescaped frontend/src/plugins/loading.ts:43 — `$t('system.title')` is text this program did not author, and it is written into the text of an element through `innerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.

D3 · God Classes · FunctionTooLong · ×3

FunctionTooLong: index.useRouteStore frontend/src/store/modules/route/index.ts:26 — FunctionTooLong — useRouteStore runs 142 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 42 over it, 1.42× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: table.useTable frontend/src/hooks/common/table.ts:13 — FunctionTooLong — useTable runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: index.useTabStore frontend/src/store/modules/tab/index.ts:25 — FunctionTooLong — useTabStore runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.

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

Sync-over-async blocking frontend/packages/scripts/src/commands/git-commit.ts:73 — `readFileSync` in `gitCommitVerify` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking frontend/packages/scripts/src/commands/router.ts:70 — `existsSync` in `generateRoute` blocks the event loop until it finishes — a blocking call inside async code stalls the event loop — every other request waits for as long as it runs.
Sync-over-async blocking frontend/packages/scripts/src/commands/router.ts:71 — `mkdirSync` in `generateRoute` 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.

R11 · Import Boundaries · Boundary violation [package · ×3

Boundary violation [package:third-party-deep-import] backend/apps/base-demo/src/base-demo.module.ts:11 — backend/apps/base-demo/src/base-demo.module.ts:11 imports @nestjs/throttler/dist/throttler-storage-record.interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:third-party-deep-import] backend/apps/base-system/src/app.module.ts:7 — backend/apps/base-system/src/app.module.ts:7 imports @nestjs/throttler/dist/throttler-storage-record.interface, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
Boundary violation [package:undeclared-workspace-dep] frontend/packages/materials/src/libs/page-tab/shared.ts:1 — frontend/packages/materials/src/libs/page-tab/shared.ts:1 imports @sa/color, a package this repository publishes, but this package's own REDACTED does not list it in dependencies (or peer/optional dependencies) — it resolves only through the workspace link, so an installed copy of this package is missing it. Add it to this package's dependencies.

S1 · Web-Security Posture · Weak hash algorithm · ×3

Weak hash algorithm backend/libs/bootstrap/src/api/collect-api-data.ts:125 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts:47 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
Weak hash algorithm backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts:49 — MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.

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

Swallowed exception (empty catch) backend/apps/base-system/src/api/iam/rest/authentication.controller.ts:42 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) backend/apps/base-system/src/api/iam/rest/authentication.controller.ts:70 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) frontend/packages/utils/src/storage.ts:33 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.

D29 · Static Analysis (SAST) · REDACTED

REDACTED
REDACTED

D3 · God Classes · TooManyMethods · ×2

TooManyMethods: AuthZService backend/libs/infra/casbin/src/services/authz.service.ts:13 — TooManyMethods — 70 methods. The bar is 30 methods; this is 40 over it, 2.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AuthZManagementService backend/libs/infra/casbin/src/services/authz-management.service.ts:12 — TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.

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

Fake-async — async method never awaits backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-validation.event.handler.ts:14 — `handle` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.
Fake-async — async method never awaits frontend/packages/scripts/src/commands/update-pkg.ts:3 — `updatePkg` is declared `async` but never awaits anything, so it runs synchronously while pretending to be asynchronous. Drop `async` or do the real async work.

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

Duplicated block (33 lines × 2 locations) backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:69 — backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:69 · backend/apps/base-system/src/infra/bounded-contexts/iam/role/repository/role.read.pg.repository.ts:38 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (33 lines × 2 locations) backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.read.model.ts:38 — backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.read.model.ts:38 · backend/apps/base-system/src/lib/bounded-contexts/log-audit/login-log/domain/login-log.read.model.ts:21 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.

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

Duplicated block (20 lines × 4 locations) backend/apps/base-system/src/api/iam/rest/domain.controller.ts:95 — backend/apps/base-system/src/api/iam/rest/domain.controller.ts:95 · backend/apps/base-system/src/api/iam/rest/menu.controller.ts:138 · backend/apps/base-system/src/api/iam/rest/role.controller.ts:100 · backend/apps/base-system/src/api/iam/rest/user.controller.ts:102 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (20 lines × 4 locations) backend/libs/infra/casbin/src/services/authz-api.ts:303 — backend/libs/infra/casbin/src/services/authz-api.ts:303 · backend/libs/infra/casbin/src/services/authz-api.ts:350 · backend/libs/infra/casbin/src/services/authz-api.ts:412 · backend/libs/infra/casbin/src/services/authz-api.ts:438 — all 4 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

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

Duplicated block (19 lines × 2 locations) backend/apps/base-system/src/api/endpoint/rest/endpoint.controller.ts:57 — backend/apps/base-system/src/api/endpoint/rest/endpoint.controller.ts:57 · backend/apps/base-system/src/api/iam/rest/menu.controller.ts:49 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (19 lines × 2 locations) backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-create.command.handler.ts:23 — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-create.command.handler.ts:23 · backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-update.command.handler.ts:29 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are.

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

Duplicated block (17 lines × 3 locations) backend/libs/infra/casbin/src/services/authz-api.ts:65 — backend/libs/infra/casbin/src/services/authz-api.ts:65 · backend/libs/infra/casbin/src/services/authz-api.ts:288 · backend/libs/infra/casbin/src/services/authz-api.ts:397 — all 3 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 3 locations) frontend/src/views/manage/menu/index.vue:90 — frontend/src/views/manage/menu/index.vue:90 · frontend/src/views/manage/role/index.vue:68 · frontend/src/views/manage/user/index.vue:86 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

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

Dead file (~0 LoC) backend/libs/global/src/keyv-cache-store.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~0 LoC) backend/libs/shared/redis/src/redis.service.ts — no import path from any entry point (27 application, 31 tooling, 4 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

AC7 · A11y enforcement · Accessibility enforcement below the top rung · ×1

Accessibility enforcement below the top rung — No accessibility enforcement found — no a11y linter (eslint-plugin-vuejs-accessibility) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 95 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here.

D22 · Internal API Consistency · Inconsistent return type for success validation. Alova's `isBackendSuccess` returns a `Promise<boolean>`, while Axios's `isBackendSuccess` returns a synchronous `boolean`. This forces consumers to handle async/sync differences inconsistently when abstracting over multiple HTTP clients. · ×1

Inconsistent return type for success validation. Alova's `isBackendSuccess` returns a `Promise<boolean>`, while Axios's `isBackendSuccess` returns a synchronous `boolean`. This forces consumers to handle async/sync differences inconsistently when abstracting over multiple HTTP clients. — Standardize `isBackendSuccess` to return `boolean` (synchronous) in both packages, or `Promise<boolean>` in both. Given that backend status checks are usually immediate, synchronous is preferred. (signatures: frontend.packages.alova.src.type.RequestOptions.isBackendSuccess: (response: AG['Response']) => Promise<boolean> | frontend.packages.axios.src.type.RequestOption.isBackendSuccess: (response: AxiosResponse<ResponseData>) => boolean)

D22 · Internal API Consistency · Inconsistent error handler signature. Alova's `onError` receives the original response (which may be null) and the method instance, whereas Axios's `onError` only receives the error object. This makes it difficult to write a unified error handling strategy across both HTTP clients. · ×1

Inconsistent error handler signature. Alova's `onError` receives the original response (which may be null) and the method instance, whereas Axios's `onError` only receives the error object. This makes it difficult to write a unified error handling strategy across both HTTP clients. — Align signatures. Ideally, both should provide the error and the response context. If Axios's signature is fixed, consider wrapping the error to include response context, or accept that this is a library-specific constraint but document it clearly. (signatures: frontend.packages.alova.src.type.RequestOptions.onError: (error: any, response: AG['Response'] | null, methodInstance: Method<AG>) => any | Promise<any> | frontend.packages.axios.src.type.RequestOption.onError: (error: AxiosError<ResponseData>) => void | Promise<void>)

D22 · Internal API Consistency · Divergent failure handling patterns. Axios uses a dedicated `onBackendFail` hook that can return a new response (allowing for retry/interception logic), while Alova relies on `isBackendSuccess` to determine flow. This creates two different mental models for handling business logic errors (e.g., 401/403) vs network errors. · ×1

Divergent failure handling patterns. Axios uses a dedicated `onBackendFail` hook that can return a new response (allowing for retry/interception logic), while Alova relies on `isBackendSuccess` to determine flow. This creates two different mental models for handling business logic errors (e.g., 401/403) vs network errors. — Introduce a unified `onBusinessError` or `onResponseFail` hook in both packages that receives the response and allows for transformation or cancellation, rather than mixing success predicates with failure handlers. (signatures: frontend.packages.axios.src.type.RequestOption.onBackendFail: ( response: AxiosResponse<ResponseData>, instance: AxiosInstance ) => Promise<AxiosResponse | null> | Promise<void> | frontend.packages.alova.src.type.RequestOptions.isBackendSuccess: (response: AG['Response']) => Promise<boolean>)

D30 · Dependency Vulnerabilities · Medium vulnerability · ×1

REDACTED

D5 · Coupling · Off the main sequence · ×1

Off the main sequence: @sa/utils — @sa/utils: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 5 project(s), so it's rigid to change.

D8 · Code Coverage · Coverage not measured · ×1

Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in backend/ ran and not one test passed (FAIL apps/base-demo/src/base-demo.controller.spec.ts), so the coverage report describes the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.

DM11 · Constructible invalid state · Constructible in an invalid state · ×1

Constructible in an invalid state: ApiEndpoint backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/domain/api-endpoint.model.ts:12 — `ApiEndpoint`'s public constructor takes `id`, `path`, `method`, `action`, … as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was checked for any branch (`if`, ternary, `switch`) or any call — it has neither, only assignments; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `ApiEndpoint` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.

IC1 · Incompleteness & stubs · Hollow method · ×1

Hollow method — returns a constant without doing the work backend/libs/infra/casbin/src/decorators/use-permissions.decorator.ts:6 — `defaultIsOwn` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.

P1 · CI/CD gates · No CI pipeline · ×1

No CI pipeline — No CI workflow found (.github/workflows, azure-pipelines.yml, .gitlab-ci.yml, …) — changes aren't gated by an automated build/test.

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

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

R10 · Code Duplication · Duplication concentrated across 4 sibling directories (19 clone groups) · ×1

Duplication concentrated across 4 sibling directories (19 clone groups) backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.read.model.ts:38 — 19 duplicated blocks under backend/apps/base-system/src/lib/bounded-contexts/ have copies in at least two of the sibling directories access-key, api-endpoint, iam, log-audit — 6 of them are reported below, and 13 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 19 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 19 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 19 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

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

Duplication concentrated across 5 sibling directories (13 clone groups) backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/command-handlers/user-update.command.handler.ts:12 — 13 duplicated blocks under backend/apps/base-system/src/lib/bounded-contexts/iam/ have copies in at least two of the sibling directories authentication, domain, menu, role, tokens — 6 of them are reported below, and 7 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 13 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 13 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 13 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 4 sibling directories (11 clone groups) · ×1

Duplication concentrated across 4 sibling directories (11 clone groups) backend/apps/base-system/src/infra/bounded-contexts/iam/domain/repository/domain.read.pg.repository.ts:26 — 11 duplicated blocks under backend/apps/base-system/src/infra/bounded-contexts/ have copies in at least two of the sibling directories access-key, api-endpoint, iam, log-audit — 5 of them are reported below, and 6 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 11 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 11 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 11 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 4 sibling directories (9 clone groups) · ×1

Duplication concentrated across 4 sibling directories (9 clone groups) backend/apps/base-system/src/api/endpoint/rest/endpoint.controller.ts:35 — 9 duplicated blocks under backend/apps/base-system/src/api/ have copies in at least two of the sibling directories access-key, endpoint, iam, log-audit — 7 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 9 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 9 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 9 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

R10 · Code Duplication · Duplication concentrated across 3 sibling directories (8 clone groups) · ×1

Duplication concentrated across 3 sibling directories (8 clone groups) frontend/src/views/access-key/index.vue:65 — 8 duplicated blocks under frontend/src/views/ have copies in at least two of the sibling directories access-key, log, manage — 7 of them are reported below, and 1 is counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 8 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 8 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 8 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

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

Duplication concentrated across 4 sibling directories (5 clone groups) backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:69 — 5 duplicated blocks under backend/apps/base-system/src/infra/bounded-contexts/iam/ have copies in at least two of the sibling directories authentication, domain, menu, role — 2 of them are reported below, and 3 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Duplicated block (45 lines × 2 locations) backend/apps/base-system/src/infra/bounded-contexts/log-audit/login-log/repository/login-log.read.pg.repository.ts:15 — backend/apps/base-system/src/infra/bounded-contexts/log-audit/login-log/repository/login-log.read.pg.repository.ts:15 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/operation-log/repository/operation-log.read.pg.repository.ts:15 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

R10 · Code Duplication · Duplicated block (37 lines × 4 locations) · ×1

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

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

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

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

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

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

Duplicated block (26 lines × 3 locations) backend/apps/base-system/src/infra/bounded-contexts/iam/domain/repository/domain.read.pg.repository.ts:26 — backend/apps/base-system/src/infra/bounded-contexts/iam/domain/repository/domain.read.pg.repository.ts:26 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/login-log/repository/login-log.read.pg.repository.ts:30 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/operation-log/repository/operation-log.read.pg.repository.ts:30 — the 3 copies are spread across 3 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.

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

Duplicated block (25 lines × 2 locations) backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:118 — backend/apps/base-system/src/infra/bounded-contexts/iam/authentication/repository/user.read.pg.repository.ts:118 · backend/apps/base-system/src/infra/bounded-contexts/iam/role/repository/role.read.pg.repository.ts:15 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

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

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

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

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

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

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

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

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

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

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

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

Duplicated block (21 lines × 2 locations) backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-update.command.handler.ts:23 — backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/command-handlers/menu-update.command.handler.ts:23 · backend/apps/base-system/src/lib/bounded-contexts/iam/role/application/command-handlers/role-update.command.handler.ts:33 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.

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

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

R10 · Code Duplication · Duplicated block (18 lines × 5 locations) · ×1

Duplicated block (18 lines × 5 locations) backend/apps/base-system/src/api/access-key/rest/access_key.controller.ts:73 — backend/apps/base-system/src/api/access-key/rest/access_key.controller.ts:73 · backend/apps/base-system/src/api/iam/rest/domain.controller.ts:97 · backend/apps/base-system/src/api/iam/rest/menu.controller.ts:140 · backend/apps/base-system/src/api/iam/rest/role.controller.ts:102 · +1 more site(s) not listed — the 5 copies are spread across 5 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

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

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

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

Duplicated block (18 lines × 3 locations) frontend/src/views/access-key/modules/access-key-search.vue:7 — frontend/src/views/access-key/modules/access-key-search.vue:7 · frontend/src/views/log/login/modules/login-log-search.vue:5 · frontend/src/views/log/operation/modules/operation-log-search.vue:5 — 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.

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

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

R10 · Code Duplication · Duplicated block (16 lines × 4 locations) · ×1

Duplicated block (16 lines × 4 locations) frontend/src/views/access-key/modules/access-key-operate-drawer.vue:73 — frontend/src/views/access-key/modules/access-key-operate-drawer.vue:73 · frontend/src/views/manage/menu/modules/menu-operate-modal.vue:239 · frontend/src/views/manage/role/modules/role-operate-drawer.vue:77 · frontend/src/views/manage/user/modules/user-operate-drawer.vue:103 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.

R10 · Code Duplication · Duplicated block (15 lines × 4 locations) · ×1

Duplicated block (15 lines × 4 locations) backend/apps/base-system/src/infra/bounded-contexts/access-key/repository/access_key.read.pg.repository.ts:14 — backend/apps/base-system/src/infra/bounded-contexts/access-key/repository/access_key.read.pg.repository.ts:14 · backend/apps/base-system/src/infra/bounded-contexts/api-endpoint/api-endpoint/repository/api-endpoint.read.pg.repository.ts:11 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/login-log/repository/login-log.read.pg.repository.ts:11 · backend/apps/base-system/src/infra/bounded-contexts/log-audit/operation-log/repository/operation-log.read.pg.repository.ts:11 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.

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

Complex function transformRouteToSysMenu (cyclomatic 14, cognitive 13) backend/local-route.migrate.ts:77 — transformRouteToSysMenu has cyclomatic complexity 14 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 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.

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

Complex function removeFilteredPolicy (cyclomatic 13, cognitive 12) backend/libs/infra/casbin/src/adapter/casbin-prisma.adapter.ts:154 — removeFilteredPolicy has cyclomatic complexity 13 and cognitive complexity 12; 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.

R2 · Cyclomatic Complexity · Complex function validateKey (cyclomatic 12, cognitive 10) · ×1

Complex function validateKey (cyclomatic 12, cognitive 10) backend/libs/infra/guard/src/api-key/services/complex-api-key.service.ts:56 — validateKey has cyclomatic complexity 12 and cognitive complexity 10; 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.

R3 · Large Files · frontend/packages/color/src/constant/name.ts · ×1

frontend/packages/color/src/constant/name.ts: 1578 lines of code frontend/packages/color/src/constant/name.ts:1 — frontend/packages/color/src/constant/name.ts has 1578 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · backend/libs/infra/casbin/src/services/authz.service.ts · ×1

backend/libs/infra/casbin/src/services/authz.service.ts: 920 lines of code backend/libs/infra/casbin/src/services/authz.service.ts:1 — backend/libs/infra/casbin/src/services/authz.service.ts has 920 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · backend/libs/infra/casbin/src/services/authz-management.service.ts · ×1

backend/libs/infra/casbin/src/services/authz-management.service.ts: 639 lines of code backend/libs/infra/casbin/src/services/authz-management.service.ts:1 — backend/libs/infra/casbin/src/services/authz-management.service.ts has 639 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · backend/libs/infra/casbin/src/services/authz-api.ts · ×1

backend/libs/infra/casbin/src/services/authz-api.ts: 453 lines of code backend/libs/infra/casbin/src/services/authz-api.ts:1 — backend/libs/infra/casbin/src/services/authz-api.ts has 453 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · frontend/src/locales/langs/en-us.ts · ×1

frontend/src/locales/langs/en-us.ts: 424 lines of code frontend/src/locales/langs/en-us.ts:1 — frontend/src/locales/langs/en-us.ts has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · frontend/src/locales/langs/zh-cn.ts · ×1

frontend/src/locales/langs/zh-cn.ts: 424 lines of code frontend/src/locales/langs/zh-cn.ts:1 — frontend/src/locales/langs/zh-cn.ts has 424 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

R3 · Large Files · frontend/src/views/manage/menu/modules/menu-operate-modal.vue · ×1

frontend/src/views/manage/menu/modules/menu-operate-modal.vue: 403 lines of code frontend/src/views/manage/menu/modules/menu-operate-modal.vue:1 — frontend/src/views/manage/menu/modules/menu-operate-modal.vue has 403 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.

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

Dead file (~374 LoC) backend/prisma/seeds/sys/sysMenu.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (backend/prisma/seeds/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

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

Dead file (~207 LoC) backend/local-route.migrate.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~82 LoC) backend/prisma/seeds/sys/casbinRule.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (backend/prisma/seeds/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

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

Dead file (~79 LoC) frontend/packages/hooks/src/use-request.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~75 LoC) backend/prisma/seeds/sys/sysRoleMenu.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (backend/prisma/seeds/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

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

Dead file (~56 LoC) REDACTED — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (backend/prisma/seeds/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

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

Dead file (~54 LoC) backend/libs/infra/interceptors/src/transform.interceptor.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~43 LoC) backend/prisma/seeds/sys/sysRole.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (backend/prisma/seeds/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

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

Dead file (~28 LoC) backend/prisma/seeds/index.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~22 LoC) backend/prisma/seeds/sys/sysUserRole.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (backend/prisma/seeds/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

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

Dead file (~21 LoC) frontend/src/hooks/business/auth.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~20 LoC) backend/prisma/seeds/sys/sysDomain.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (backend/prisma/seeds/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it

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

Dead file (~6 LoC) backend/apps/base-system/src/lib/bounded-contexts/iam/role/application/dto/role-create.dto.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~5 LoC) backend/apps/base-system/src/lib/bounded-contexts/iam/role/queries/get-roles.query-result.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make

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

Dead file (~3 LoC) backend/prisma/seeds/helper.ts — no import path from any entry point (27 application, 31 tooling, 4 test roots considered), but 8 in-repo import(s) from 8 other file(s) do name it (backend/prisma/seeds/index.ts, backend/prisma/seeds/sys/casbinRule.ts, backend/prisma/seeds/sys/sysDomain.ts and 5 more) — 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

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

Unlisted import 'axios' REDACTED:1 — Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.

R8 · Dependency Hygiene · Unlisted import '@unocss/core' · ×1

Unlisted import '@unocss/core' frontend/packages/uno-preset/src/index.ts:3 — Imported only as a TYPE and declared in no reachable REDACTED. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning REDACTED.

R8 · Dependency Hygiene · Unused dependency 'dotenv' · ×1

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

R8 · Dependency Hygiene · Unused dependency 'source-map-support' · ×1

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

R8 · Dependency Hygiene · Unused dependency 'tsconfig-paths' · ×1

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

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

Async function without AbortSignal: getHtmlBuildTime frontend/src/plugins/app.ts:91 — `getHtmlBuildTime` awaits `fetch(…)` but neither accepts an AbortSignal nor passes one on, so its caller cannot stop the request once it has started. Accept `{ signal }` and pass it through: `fetch(url, { signal })`.

Minor — 228 finding(s)

D34 · Knowledge Freshness · Orphaned file · ×95

Orphaned file frontend/src/views/manage/menu/modules/menu-operate-modal.vue:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/locales/langs/en-us.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/locales/langs/zh-cn.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/libs/infra/casbin/src/services/authz-api.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/packages/color/src/constant/palette.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/store/modules/route/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/prisma/seeds/sys/sysMenu.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/libs/infra/casbin/src/services/authz-rbac.service.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/store/modules/route/shared.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/service/authorization.service.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/libs/infra/crypto/src/services/crypto.service.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/store/modules/tab/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/views/manage/menu/index.vue:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/store/modules/theme/shared.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/hooks/common/table.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/packages/materials/src/libs/admin-layout/index.vue:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/libs/infra/casbin/src/adapter/casbin-prisma.adapter.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/layouts/modules/theme-drawer/modules/page-fun.vue:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/local-route.migrate.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/libs/shared/ip2region/src/ip2region.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file backend/apps/base-system/src/app.module.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/views/manage/role/index.vue:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/packages/materials/src/types/index.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file frontend/src/store/modules/tab/shared.ts:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 70 more in this group — see findings.md.

X4 · Structured logging · Interpolated log message defeats structured logging · ×35

Interpolated log message defeats structured logging backend/apps/base-system/src/main.ts:129 — `log` at line 129 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-validation.event.handler.ts:16 — `log` at line 16 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-deleted.event.handler.ts:26 — `log` at line 26 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/access-key/application/event-handlers/access_key-created.event.handler.ts:29 — `log` at line 29 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/application/event-handlers/api-endpoint.event.handler.ts:35 — `log` at line 35 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/api-endpoint/api-endpoint/application/event-handlers/api-endpoint.event.handler.ts:41 — `log` at line 41 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/event-handlers/user-created.event.handler.ts:11 — `log` at line 11 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/event-handlers/role-deleted.event.handler.ts:16 — `log` at line 16 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/application/event-handlers/domain-deleted.event.handler.ts:16 — `log` at line 16 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/iam/domain/application/event-handlers/domain-deleted.event.handler.ts:16 — `log` at line 16 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/iam/menu/application/event-handlers/menu-deleted.event.handler.ts:11 — `log` at line 11 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/iam/role/application/event-handlers/role-deleted.event.handler.ts:21 — `log` at line 21 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/apps/base-system/src/lib/bounded-contexts/iam/role/application/event-handlers/domain-deleted.event.handler.ts:16 — `log` at line 16 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/bootstrap/src/api/collect-api-data.ts:47 — `log` at line 47 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/adapter/src/fastify.adapter.ts:26 — `log` at line 26 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.log({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.log('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:105 — `debug` at line 105 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:146 — `debug` at line 146 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:148 — `error` at line 148 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:164 — `debug` at line 164 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:177 — `debug` at line 177 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:184 — `error` at line 184 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.error({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.error('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/services/crypto.service.ts:47 — `debug` at line 47 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/services/crypto.service.ts:51 — `debug` at line 51 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/services/crypto.service.ts:55 — `debug` at line 55 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
Interpolated log message defeats structured logging backend/libs/infra/crypto/src/services/crypto.service.ts:68 — `debug` at line 68 is handed a template literal with `${…}` substitutions as its message, so the logger receives one finished string — the values in it cannot be queried, filtered or aggregated as fields, and every occurrence reads as a different message. Pass the values beside a constant message instead: `logger.debug({ orderId, status }, 'order status updated')` for pino and bunyan, `logger.debug('order status updated', { orderId, status })` for winston. If these calls go through a NestJS `Logger` routed into pino, nestjs-pino forwards an object first argument as fields in the same way.
+ 10 more in this group — see findings.md.

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

Console output used as the logging channel backend/local-route.migrate.ts:67 — `backend/local-route.migrate.ts` reports through `console.*` at line 67 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/local-route.migrate.ts:194 — `backend/local-route.migrate.ts` reports through `console.*` at line 194 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/local-route.migrate.ts:200 — `backend/local-route.migrate.ts` reports through `console.*` at line 200 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/local-route.migrate.ts:203 — `backend/local-route.migrate.ts` reports through `console.*` at line 203 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/local-route.migrate.ts:204 — `backend/local-route.migrate.ts` reports through `console.*` at line 204 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/apps/base-demo/src/base-demo.controller.ts:116 — `backend/apps/base-demo/src/base-demo.controller.ts` reports through `console.*` at line 116 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/apps/base-system/src/lib/bounded-contexts/access-key/application/query-handlers/access_keys.bootstrap.handler.ts:25 — `backend/apps/base-system/src/lib/bounded-contexts/access-key/application/query-handlers/access_keys.bootstrap.handler.ts` reports through `console.*` at line 25 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/libs/infra/casbin/src/guards/authz.guard.ts:66 — `backend/libs/infra/casbin/src/guards/authz.guard.ts` reports through `console.*` at line 66 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/libs/logger/src/logger.module.ts:52 — `backend/libs/logger/src/logger.module.ts` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/libs/logger/src/logger.module.ts:129 — `backend/libs/logger/src/logger.module.ts` reports through `console.*` at line 129 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/libs/shared/prisma/src/prisma.service.ts:26 — `backend/libs/shared/prisma/src/prisma.service.ts` reports through `console.*` at line 26 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/libs/shared/prisma/src/prisma.service.ts:27 — `backend/libs/shared/prisma/src/prisma.service.ts` reports through `console.*` at line 27 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/libs/shared/prisma/src/prisma.service.ts:28 — `backend/libs/shared/prisma/src/prisma.service.ts` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel backend/libs/utils/src/tree.util.ts:44 — `backend/libs/utils/src/tree.util.ts` reports through `console.*` at line 44 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel frontend/src/plugins/app.ts:9 — `frontend/src/plugins/app.ts` reports through `console.*` at line 9 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel frontend/src/router/elegant/transform.ts:134 — `frontend/src/router/elegant/transform.ts` reports through `console.*` at line 134 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel frontend/src/utils/service.ts:16 — `frontend/src/utils/service.ts` reports through `console.*` at line 16 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.

DM2 · Strongly-typed ids · Primitive id on a domain type · ×13

Primitive id on a domain type: UserCreatedEvent.userId backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/events/user-created.event.ts:5 — `UserCreatedEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: UserDeletedEvent.userId backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/events/user-deleted.event.ts:5 — `UserDeletedEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: RoleDeletedEvent.roleId backend/apps/base-system/src/lib/bounded-contexts/iam/role/domain/events/role-deleted.event.ts:5 — `RoleDeletedEvent.roleId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: TokenGeneratedEvent.userId backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/events/token-generated.event.ts:7 — `TokenGeneratedEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: TokenGeneratedEvent.requestId backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/events/token-generated.event.ts:13 — `TokenGeneratedEvent.requestId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: TokensEntity.userId backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.entity.ts:16 — `TokensEntity.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: TokensEntity.requestId backend/apps/base-system/src/lib/bounded-contexts/iam/tokens/domain/tokens.entity.ts:22 — `TokensEntity.requestId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: UserLoggedInEvent.userId backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:5 — `UserLoggedInEvent.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: UserLoggedInEvent.requestId backend/apps/base-system/src/lib/bounded-contexts/iam/authentication/domain/events/user-logged-in.event.ts:11 — `UserLoggedInEvent.requestId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: MenuDeletedEvent.menuId backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/events/menu-deleted.event.ts:5 — `MenuDeletedEvent.menuId` is a raw `number` — give it a strongly-typed id: a dedicated single-field type wrapping the `number`, in whatever form your language spells that.
Primitive id on a domain type: Menu.i18nKey backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.model.ts:32 — `Menu.i18nKey` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: OperationLog.userId backend/apps/base-system/src/lib/bounded-contexts/log-audit/operation-log/domain/operation-log.model.ts:6 — `OperationLog.userId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.
Primitive id on a domain type: OperationLog.requestId backend/apps/base-system/src/lib/bounded-contexts/log-audit/operation-log/domain/operation-log.model.ts:11 — `OperationLog.requestId` is a raw `string` — give it a strongly-typed id: a dedicated single-field type wrapping the `string`, in whatever form your language spells that.

D12 · Dependency Hygiene · Deprecated · ×7

Deprecated: glob REDACTED:2702 — glob 7.2.3 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: inflight REDACTED:2813 — inflight 1.0.6 is resolved in REDACTED and is marked deprecated by its publisher: "This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: resolve-url REDACTED:3425 — resolve-url 0.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "https://github.com/lydell/resolve-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-resolve REDACTED:3596 — source-map-resolve 0.5.3 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-resolve#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: source-map-url REDACTED:3600 — source-map-url 0.4.1 is resolved in REDACTED and is marked deprecated by its publisher: "See https://github.com/lydell/source-map-url#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: stable REDACTED:3635 — stable 0.1.8 is resolved in REDACTED and is marked deprecated by its publisher: "Modern JS already guarantees Array#sort() is a stable sort, so this library is deprecated. See the compatibility table on MDN: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Array/sort#browser_compatibility". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
Deprecated: urix REDACTED:3933 — urix 0.1.0 is resolved in REDACTED and is marked deprecated by its publisher: "Please see https://github.com/lydell/urix#deprecated". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.

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

Outdated (npm): @nestjs/axios REDACTED:40 — @nestjs/axios is pinned at 4.0.0; registry.npmjs.org publishes 12.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/cache-manager REDACTED:41 — @nestjs/cache-manager is pinned at 3.0.1; registry.npmjs.org publishes 12.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/config REDACTED:43 — @nestjs/config is pinned at 4.0.2; registry.npmjs.org publishes 12.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/event-emitter REDACTED:46 — @nestjs/event-emitter is pinned at 3.0.1; registry.npmjs.org publishes 12.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/schedule REDACTED:51 — @nestjs/schedule is pinned at 6.0.0; registry.npmjs.org publishes 12.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

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

README/code drift README.md:200 — README.md names `database.config.ts`, but no file or folder `database.config.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:202 — README.md names `jwt.config.ts`, but no file or folder `jwt.config.ts` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift README.md:207 — README.md names `.env.production`, but no file or folder `.env.production` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift backend/README.md:75 — backend/README.md links to `LICENSE`, but `backend/LICENSE` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift frontend/README.en_US.md:9 — frontend/README.en_US.md links to `./LICENSE`, but `frontend/LICENSE` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every REDACTED, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.

D30 · Dependency Vulnerabilities · Low CVE · ×4

REDACTED
REDACTED
REDACTED
REDACTED

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

Diagnostic log message is built whether or not it is wanted backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:105 — `debug` at line 105 is called with an argument built by `JSON.stringify(options)` (line 108), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:164 — `debug` at line 164 is called with an argument built by `JSON.stringify(data.data,)` (line 165), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted backend/libs/infra/crypto/src/interceptors/crypto.interceptor.ts:177 — `debug` at line 177 is called with an argument built by `JSON.stringify(data,)` (line 178), whose cost grows with the collection it walks. JavaScript evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isLevelEnabled`/`isDebugEnabled` test, no debug flag, no `NODE_ENV` build switch.
Diagnostic log message is built whether or not it is wanted backend/libs/infra/crypto/src/services/crypto.service.ts:76 — `debug` at line 76 is called with an argument built by `JSON.stringify(deserialized)` (line 76), 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.

D34 · Knowledge Freshness · Most significant orphaned file · ×3

Most significant orphaned file frontend/packages/color/src/constant/name.ts:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file backend/libs/infra/casbin/src/services/authz.service.ts:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file backend/libs/infra/casbin/src/services/authz-management.service.ts:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.

IC1 · Incompleteness & stubs · Blanket warning suppression · ×3

Blanket warning suppression frontend/src/router/elegant/imports.ts:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression frontend/src/router/elegant/routes.ts:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.
Blanket warning suppression frontend/src/router/elegant/transform.ts:1 — A bare `eslint-disable` or `@ts-nocheck` with no rule list switches every lint rule or the whole type checker off for the rest of the file — hidden debt. Disable the specific rule on the specific line, with a justification, instead.

D30 · Dependency Vulnerabilities · Low vulnerability · ×2

REDACTED
REDACTED

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

REDACTED
REDACTED

D19 · Documentation Quality · Documentation · ×1

Documentation: no architecture or design documentation README.md — The outline lists architecture/design docs but there are no such documents in the set. Add an architecture or design doc describing the monorepo structure, services, and data-flow model.

D26 · Project Cohesion · Split backend · ×1

Split backend — A generic catch-all name that is huge (13k LoC) and sprawls across 143 namespaces with no coherent theme. Suggested:

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

REDACTED

D34 · Knowledge Freshness · Concentrated knowledge decay · ×1

Concentrated knowledge decay — 98 of 98 significant files have no living knowledge, while the repository is still being changed at a low rate (2 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 98 separate risks. Counted over 98 of the 579 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.

M2 · Architecture documentation · No ADRs · ×1

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

P2 · Observability · Logging is not universal · ×1

Logging is not universal — Only 2/3 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `frontend/packages/scripts`.

P3 · Security & performance tooling · No SAST · ×1

No SAST — No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — this repository has no CI pipeline yet, so run it locally to clear the existing findings, then make it a step of the first workflow you add so a regression fails the build. What was searched, so you can tell an absence from a miss: the 0 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

R7 · Dead Code · Unused export 'MenuReadModel' · ×1

Unused export 'MenuReadModel' backend/apps/base-system/src/lib/bounded-contexts/iam/menu/domain/menu.read.model.ts:50 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'X_REQUEST_ID' · ×1

Unused export 'X_REQUEST_ID' backend/libs/constants/src/rest.constant.ts:5 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'AESCrypto' · ×1

Unused export 'AESCrypto' backend/libs/infra/crypto/src/decorators/crypto.decorator.ts:47 — Nothing ultimately consumes this binding: its only referrer is the re-export in backend/libs/infra/crypto/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in backend/libs/infra/crypto/src/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export 'RSACrypto' · ×1

Unused export 'RSACrypto' backend/libs/infra/crypto/src/decorators/crypto.decorator.ts:58 — Nothing ultimately consumes this binding: its only referrer is the re-export in backend/libs/infra/crypto/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in backend/libs/infra/crypto/src/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export 'WithCryptoConfig' · ×1

Unused export 'WithCryptoConfig' backend/libs/infra/crypto/src/decorators/crypto.decorator.ts:68 — Nothing ultimately consumes this binding: its only referrer is the re-export in backend/libs/infra/crypto/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in backend/libs/infra/crypto/src/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export 'getContentType' · ×1

Unused export 'getContentType' frontend/packages/axios/src/shared.ts:3 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'isResponseJson' · ×1

Unused export 'isResponseJson' frontend/packages/axios/src/shared.ts:24 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'colorNameMap' · ×1

Unused export 'colorNameMap' frontend/packages/color/src/constant/name.ts:1576 — Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/packages/color/src/constant/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/packages/color/src/constant/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export 'getRecommendedPaletteColorByNumber' · ×1

Unused export 'getRecommendedPaletteColorByNumber' frontend/packages/color/src/palette/recommend.ts:44 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'themeSchemaOptions' · ×1

Unused export 'themeSchemaOptions' frontend/src/constants/app.ts:13 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'themeLayoutModeOptions' · ×1

Unused export 'themeLayoutModeOptions' frontend/src/constants/app.ts:30 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'userGenderOptions' · ×1

Unused export 'userGenderOptions' frontend/src/constants/business.ts:15 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'yesOrNoOptions' · ×1

Unused export 'yesOrNoOptions' frontend/src/constants/common.ts:8 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'REG_CODE_FOUR' · ×1

Unused export 'REG_CODE_FOUR' frontend/src/constants/reg.ts:21 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'REG_URL' · ×1

Unused export 'REG_URL' frontend/src/constants/reg.ts:24 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'setupAppErrorHandle' · ×1

Unused export 'setupAppErrorHandle' frontend/src/plugins/app.ts:6 — Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/src/plugins/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/src/plugins/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export 'fetchCustomBackendError' · ×1

Unused export 'fetchCustomBackendError' frontend/src/service/api/auth.ts:46 — Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/src/service/api/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/src/service/api/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export 'fetchGetAllPages' · ×1

Unused export 'fetchGetAllPages' frontend/src/service/api/system-manage.ts:59 — Nothing ultimately consumes this binding: its only referrer is the re-export in frontend/src/service/api/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in frontend/src/service/api/index.ts in the same commit, or the barrel will import a name that no longer exists.

R7 · Dead Code · Unused export 'demoRequest' · ×1

Unused export 'demoRequest' REDACTED:126 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'filterTabsById' · ×1

Unused export 'filterTabsById' frontend/src/store/modules/tab/shared.ts:153 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'sessionStg' · ×1

Unused export 'sessionStg' frontend/src/utils/storage.ts:7 — Nothing imports this binding — it is safe to review for removal.

R7 · Dead Code · Unused export 'localforage' · ×1

Unused export 'localforage' frontend/src/utils/storage.ts:9 — Nothing imports this binding — it is safe to review for removal.

S1 · Web-Security Posture · No security response headers detected · ×1

No security response headers detected frontend/nginx.conf:42 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `nginx.conf` is committed to this repository and declares the server that serves it, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)

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

Not all async functions that make a request accept an AbortSignal — Only 0/1 async functions that make a cancellable request (fetch, axios, ky, ofetch) accept an AbortSignal or pass one on, so a request keeps running after whatever wanted it has given up — a page navigated away from, an unmounted component, a timed-out job. Take a `signal` (or an options object that carries one) and hand it to the request; where nothing could ever cancel the call, omitting it is a deliberate choice — judge against how the function is used.

X5 · Nullable reference types · Strict null checking is not enabled everywhere the repository type-checks · ×1

Strict null checking is not enabled everywhere the repository type-checks — 34/35 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.

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

Null assertions (`!`) reduce the strict null checking score — ~0.6 `!` null assertions per 1k TypeScript source lines — 15 assertion(s) across the 26627 source line(s) of the 475 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: frontend/packages/color/src/palette/recommend.ts (3), frontend/src/hooks/common/table.ts (3), frontend/src/hooks/common/echarts.ts (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.

Minor — 51 finding(s)

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

Outdated (npm): @alova/mock — @alova/mock is pinned at 2.0.12; registry.npmjs.org publishes 2.0.22 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fastify/compress — @fastify/compress is pinned at 8.0.3; registry.npmjs.org publishes 9.2.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fastify/csrf-protection — @fastify/csrf-protection is pinned at 7.1.0; registry.npmjs.org publishes 8.0.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fastify/helmet — @fastify/helmet is pinned at 13.0.1; registry.npmjs.org publishes 13.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fastify/multipart — @fastify/multipart is pinned at 9.0.3; registry.npmjs.org publishes 10.1.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @fastify/static — @fastify/static is pinned at 8.2.0; registry.npmjs.org publishes 10.1.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @iconify/vue — @iconify/vue is pinned at 4.3.0; registry.npmjs.org publishes 5.0.4 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @keyv/redis — @keyv/redis is pinned at 4.4.1; registry.npmjs.org publishes 6.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nest-lab/throttler-storage-redis — @nest-lab/throttler-storage-redis is pinned at 1.1.0; registry.npmjs.org publishes 1.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/common — @nestjs/common is pinned at 11.1.3; registry.npmjs.org publishes 12.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/core — @nestjs/core is pinned at 11.1.3; registry.npmjs.org publishes 12.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/cqrs — @nestjs/cqrs is pinned at 11.0.3; registry.npmjs.org publishes 12.1.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/jwt — @nestjs/jwt is pinned at 11.0.0; registry.npmjs.org publishes 12.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/microservices — @nestjs/microservices is pinned at 11.1.3; registry.npmjs.org publishes 12.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/passport — @nestjs/passport is pinned at 11.0.5; registry.npmjs.org publishes 12.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/platform-fastify — @nestjs/platform-fastify is pinned at 11.1.3; registry.npmjs.org publishes 12.2.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/swagger — @nestjs/swagger is pinned at 11.2.0; registry.npmjs.org publishes 12.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/terminus — @nestjs/terminus is pinned at 11.0.0; registry.npmjs.org publishes 12.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @nestjs/throttler — @nestjs/throttler is pinned at 6.4.0; registry.npmjs.org publishes 6.7.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @prisma/client — @prisma/client is pinned at 6.10.1; registry.npmjs.org publishes 7.10.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): @vueuse/core — @vueuse/core is pinned at 13.0.0; registry.npmjs.org publishes 15.0.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): alova — alova is pinned at 3.2.10; registry.npmjs.org publishes 3.5.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): axios — axios is pinned at 1.8.3; registry.npmjs.org publishes 1.20.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): bcryptjs — bcryptjs is pinned at 3.0.2; registry.npmjs.org publishes 3.0.3 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
Outdated (npm): cache-manager — cache-manager is pinned at 7.0.0; registry.npmjs.org publishes 7.2.9 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
+ 26 more in this group — see findings.md.

Appendix B — Reproduction & audit trail

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

Dimension	Tool	Version	Command	Findings	Raw output
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3cb6e28f6bf44ec4933561148d7f281b/history.json --exit-code 0 --source .	7	artifacts/raw/gitleaks-history.json
D28 · Secrets (history)	gitleaks	—	gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-3cb6e28f6bf44ec4933561148d7f281b/tree.json --exit-code 0 --source .	7	artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)	semgrep	—	semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .	7	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	85	artifacts/raw/trivy-fs.json
D31 · IaC & Container Security	trivy	—	trivy config --format json --quiet .	10	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 13 file(s) — `backend/apps/base-demo/src/main.ts`, `backend/apps/base-system/src/main.ts`, `frontend/packages/alova/src/index.ts`, `frontend/packages/axios/src/index.ts`, `frontend/packages/scripts/src/locales/index.ts`, … (+8 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.	0	—
D36 · Supply-chain Provenance & Signing	provenance	—	provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .circleci, .buildkite, .woodpecker, .teamcity, .gitlab-ci.yml, .travis.yml, bitbucket-pipelines.yml, .drone.yml, .cirrus.yml, .woodpecker.yml, appveyor.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, .azuredevops/, Jenkinsfile); there is no build to attest provenance for.	0	—
D37 · Vulnerability-disclosure Policy	disclosure	—	disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.	0	—
D40 · Network Egress Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.	0	—
D41 · Kernel & Syscall Confinement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.	0	—
D42 · Runtime Threat Enforcement	runtime-hardening	—	runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.	0	—
D43 · Malicious Dependencies	trivy	—	trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs /bin/ --skip-dirs /obj/ . --skip-db-update	0	artifacts/raw/trivy-fs.json

Run 01a16401-8e58-76e7-95ff-e81f5c981829 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Findings by how serious they are

This survey was produced by

Executive summary

Top priorities

Diagnosis: what the measurements show together

Architecture — module dependency graph

Architecture: which parts of the code depend on which

At a glance — Code Health · 56% · Adequate · gated by X4 ·

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

At a glance — Maturity · 33% · Weak · gated by D34, M2, M4 ·

At a glance — Readiness · 19% · Critical · gated by D9, D13, R8, P1, P3, P5 ·

At a glance — Security · 57% · Adequate · gated by D29, D30, C1 ·

At a glance — Domain Modelling · 40% · Weak · gated by DM4, DM5, DM2 ·

At a glance — Accessibility · 26% · Weak · gated by AC1, AC4 ·

At a glance — Performance · 60% · Adequate ·

Security & Compliance — OWASP Top-10 mapping

Roadmap

File quality

How the grades work

Methodology & how to trust this report

Tools & methods

Run transparency — what happened this run

Limitations & what we did not check

Per-dimension blind spots

The LLM boundary

Dimensions

Frontend & cross-cutting dimensions

WCAG coverage — what static analysis assessed

Reference — by lens

Appendix A — Findings (grouped)

Appendix B — Reproduction & audit trail

Downloadable artifacts