Executive summary
leal32b/webapi-nodejs is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no access checks on the code's endpoints or handlers and it has packages with a known security hole. It scores 39 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 30, is the weakest lens and counts most in the score. The best first step is replacing the eight exposed passwords or keys and switching the old ones off, worth about 7 points. Adding access checks would lift Security and Compliance itself, worth about 6 points. Raising Security and Compliance to 70 would lift the score to about 46.
Forty-three known security holes in the packages the code depends on can be used by attackers. Eight passwords or keys in the code and four in the code's history are open to anyone who can read the repository, and one automatic update takes new releases before a bad one can be spotted. Updating the vulnerable packages, replacing each exposed password or key and setting a waiting period for automatic updates would close these risks. Pinning each tool to an exact version would fix the pipeline tool referenced by a changeable name. Referring to the other business object by its identifier would take care of the two business objects holding another business object directly.
The product code is 4,683 lines, about €13,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Security and Compliance rose from 30 to 70, the lowest score rated Strong, the score would rise from 39 to about 46.
New since the last survey: 7 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Aggregate boundaries · Aggregate holds a reference to another aggregate: UserAggregate.groups src/modules/identity/0.domain/aggregates/user.aggregate.ts
- Aggregate boundaries · Aggregate holds a reference to another aggregate: UserAggregate.groups src/modules/identity/0.domain/aggregates/user.aggregate.ts
Fixed since the last survey: 6 findings
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- DR & Backup · No DR/backup evidence
Rebuild cost: about €13,000 · Estimate
| Cost to rebuild | €4,400 to €22,000, for 74 to 235 hours of work, under 0.1 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 39. 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 | Small: 4,683 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 common.0_domain.base.domain-error | 2 common.0_domain.utils.either | 3 common.1_application.middleware.middleware | 4 common.2_presentation.base.controller | 5 common.3_infra.webapp.web-app | 6 modules.identity.4_main.factories.controllers | 7 common.0_domain.base.entity | 8 common.0_domain.base.validator | 9 common.1_application.base.use-case | 10 common.2_presentation.errors.server_error | 11 common.3_infra.compilation.handlebars.handlebars_adapter | 12 common.3_infra.cryptography.argon.argon_adapter | 13 common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter | 14 common.0_domain.base.value-object | 15 common.0_domain.validators.date_validator | 16 common.0_domain.validators.email_validator | 17 common.0_domain.validators.html_validator | 18 common.0_domain.validators.locale_validator | 19 common.0_domain.validators.max-length_validator | 20 common.0_domain.validators.min-length_validator | 21 common.0_domain.validators.not-empty_validator | 22 common.0_domain.validators.not-null_validator | 23 common.3_infra.events.amqplib.amqplib_adapter | 24 common.3_infra.webapp.express.express_adapter | 25 modules.identity.0_domain.entities.group_entity | 26 modules.communication.0_domain.value-objects.email_from_value-object | 27 modules.communication.0_domain.value-objects.email_html_value-object | 28 modules.communication.0_domain.value-objects.email_subject_value-object | 29 modules.communication.0_domain.value-objects.email_text_value-object | 30 modules.communication.0_domain.value-objects.email_to_value-object | 31 modules.identity.0_domain.value-objects.user_email-confirmed_value-object | 32 modules.identity.0_domain.value-objects.user_password_value-object | 33 modules.identity.0_domain.value-objects.user_token_value-object | 34 modules.communication.0_domain.entities.email_entity | 35 modules.identity.0_domain.entities.user_entity | 36 modules.communication.3_infra.communication.nodemailer.nodemailer_adapter | 37 modules.identity.0_domain.aggregates.user_aggregate | 38 modules.identity.1_application.use-cases.change-password_use-case | 39 modules.identity.1_application.use-cases.confirm-email_use-case | 40 modules.identity.1_application.use-cases.sign-in_use-case |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 common.0_domain.base.domain-error | ||||||||||||||||||||||||||||||||||||||||
| 2 common.0_domain.utils.either | ||||||||||||||||||||||||||||||||||||||||
| 3 common.1_application.middleware.middleware | ||||||||||||||||||||||||||||||||||||||||
| 4 common.2_presentation.base.controller | ||||||||||||||||||||||||||||||||||||||||
| 5 common.3_infra.webapp.web-app | ||||||||||||||||||||||||||||||||||||||||
| 6 modules.identity.4_main.factories.controllers | ||||||||||||||||||||||||||||||||||||||||
| 7 common.0_domain.base.entity | 1 | |||||||||||||||||||||||||||||||||||||||
| 8 common.0_domain.base.validator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 9 common.1_application.base.use-case | 1 | |||||||||||||||||||||||||||||||||||||||
| 10 common.2_presentation.errors.server_error | 1 | |||||||||||||||||||||||||||||||||||||||
| 11 common.3_infra.compilation.handlebars.handlebars_adapter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 12 common.3_infra.cryptography.argon.argon_adapter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 13 common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 common.0_domain.base.value-object | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 15 common.0_domain.validators.date_validator | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 16 common.0_domain.validators.email_validator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 common.0_domain.validators.html_validator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 common.0_domain.validators.locale_validator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 19 common.0_domain.validators.max-length_validator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 20 common.0_domain.validators.min-length_validator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 21 common.0_domain.validators.not-empty_validator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 common.0_domain.validators.not-null_validator | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 23 common.3_infra.events.amqplib.amqplib_adapter | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 common.3_infra.webapp.express.express_adapter | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 25 modules.identity.0_domain.entities.group_entity | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 modules.communication.0_domain.value-objects.email_from_value-object | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 27 modules.communication.0_domain.value-objects.email_html_value-object | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 modules.communication.0_domain.value-objects.email_subject_value-object | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 modules.communication.0_domain.value-objects.email_text_value-object | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 modules.communication.0_domain.value-objects.email_to_value-object | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 31 modules.identity.0_domain.value-objects.user_email-confirmed_value-object | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 32 modules.identity.0_domain.value-objects.user_password_value-object | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 modules.identity.0_domain.value-objects.user_token_value-object | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 modules.communication.0_domain.entities.email_entity | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 35 modules.identity.0_domain.entities.user_entity | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 36 modules.communication.3_infra.communication.nodemailer.nodemailer_adapter | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 modules.identity.0_domain.aggregates.user_aggregate | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 38 modules.identity.1_application.use-cases.change-password_use-case | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 39 modules.identity.1_application.use-cases.confirm-email_use-case | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 40 modules.identity.1_application.use-cases.sign-in_use-case | 1 | 1 | 1 | 1 |
7→2 common.0_domain.base.entity uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.base.entity uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.base.entity.Entity→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.base.entity uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.base.entity, while a change to common.0_domain.base.entity can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.base.entity uses a module listed above it, which is the healthy direction.
8→1 common.0_domain.base.validator uses common.0_domain.base.domain-error✕
- Connections
- 1 pair of types, where a type in common.0_domain.base.validator uses a type in common.0_domain.base.domain-error.
- The types involved
src.common.0_domain.base.validator.Validator→src.common.0_domain.base.domain-error.DomainError
- Direction
- common.0_domain.base.validator uses common.0_domain.base.domain-error, so a change to common.0_domain.base.domain-error can break common.0_domain.base.validator, while a change to common.0_domain.base.validator can't break common.0_domain.base.domain-error.
- Position
- Below the diagonal: common.0_domain.base.validator uses a module listed above it, which is the healthy direction.
8→2 common.0_domain.base.validator uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.base.validator uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.base.validator.Validator→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.base.validator uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.base.validator, while a change to common.0_domain.base.validator can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.base.validator uses a module listed above it, which is the healthy direction.
9→2 common.1_application.base.use-case uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.1_application.base.use-case uses a type in common.0_domain.utils.either.
- The types involved
src.common.1_application.base.use-case.UseCase→src.common.0_domain.utils.either.Either
- Direction
- common.1_application.base.use-case uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.1_application.base.use-case, while a change to common.1_application.base.use-case can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.1_application.base.use-case uses a module listed above it, which is the healthy direction.
10→1 common.2_presentation.errors.server_error uses common.0_domain.base.domain-error✕
- Connections
- 1 pair of types, where a type in common.2_presentation.errors.server_error uses a type in common.0_domain.base.domain-error.
- The types involved
src.common.2_presentation.errors.server_error.ServerError→src.common.0_domain.base.domain-error.DomainError
- Direction
- common.2_presentation.errors.server_error uses common.0_domain.base.domain-error, so a change to common.0_domain.base.domain-error can break common.2_presentation.errors.server_error, while a change to common.2_presentation.errors.server_error can't break common.0_domain.base.domain-error.
- Position
- Below the diagonal: common.2_presentation.errors.server_error uses a module listed above it, which is the healthy direction.
11→1 common.3_infra.compilation.handlebars.handlebars_adapter uses common.0_domain.base.domain-error✕
- Connections
- 1 pair of types, where a type in common.3_infra.compilation.handlebars.handlebars_adapter uses a type in common.0_domain.base.domain-error.
- The types involved
src.common.3_infra.compilation.handlebars.handlebars_adapter.HandlebarsAdapter→src.common.0_domain.base.domain-error.DomainError
- Direction
- common.3_infra.compilation.handlebars.handlebars_adapter uses common.0_domain.base.domain-error, so a change to common.0_domain.base.domain-error can break common.3_infra.compilation.handlebars.handlebars_adapter, while a change to common.3_infra.compilation.handlebars.handlebars_adapter can't break common.0_domain.base.domain-error.
- Position
- Below the diagonal: common.3_infra.compilation.handlebars.handlebars_adapter uses a module listed above it, which is the healthy direction.
11→2 common.3_infra.compilation.handlebars.handlebars_adapter uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.3_infra.compilation.handlebars.handlebars_adapter uses a type in common.0_domain.utils.either.
- The types involved
src.common.3_infra.compilation.handlebars.handlebars_adapter.HandlebarsAdapter→src.common.0_domain.utils.either.Either
- Direction
- common.3_infra.compilation.handlebars.handlebars_adapter uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.3_infra.compilation.handlebars.handlebars_adapter, while a change to common.3_infra.compilation.handlebars.handlebars_adapter can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.3_infra.compilation.handlebars.handlebars_adapter uses a module listed above it, which is the healthy direction.
12→1 common.3_infra.cryptography.argon.argon_adapter uses common.0_domain.base.domain-error✕
- Connections
- 1 pair of types, where a type in common.3_infra.cryptography.argon.argon_adapter uses a type in common.0_domain.base.domain-error.
- The types involved
src.common.3_infra.cryptography.argon.argon_adapter.ArgonAdapter→src.common.0_domain.base.domain-error.DomainError
- Direction
- common.3_infra.cryptography.argon.argon_adapter uses common.0_domain.base.domain-error, so a change to common.0_domain.base.domain-error can break common.3_infra.cryptography.argon.argon_adapter, while a change to common.3_infra.cryptography.argon.argon_adapter can't break common.0_domain.base.domain-error.
- Position
- Below the diagonal: common.3_infra.cryptography.argon.argon_adapter uses a module listed above it, which is the healthy direction.
12→2 common.3_infra.cryptography.argon.argon_adapter uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.3_infra.cryptography.argon.argon_adapter uses a type in common.0_domain.utils.either.
- The types involved
src.common.3_infra.cryptography.argon.argon_adapter.ArgonAdapter→src.common.0_domain.utils.either.Either
- Direction
- common.3_infra.cryptography.argon.argon_adapter uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.3_infra.cryptography.argon.argon_adapter, while a change to common.3_infra.cryptography.argon.argon_adapter can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.3_infra.cryptography.argon.argon_adapter uses a module listed above it, which is the healthy direction.
13→1 common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter uses common.0_domain.base.domain-error✕
- Connections
- 1 pair of types, where a type in common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter uses a type in common.0_domain.base.domain-error.
- The types involved
src.common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter.JsonwebtokenAdapter→src.common.0_domain.base.domain-error.DomainError
- Direction
- common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter uses common.0_domain.base.domain-error, so a change to common.0_domain.base.domain-error can break common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter, while a change to common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter can't break common.0_domain.base.domain-error.
- Position
- Below the diagonal: common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter uses a module listed above it, which is the healthy direction.
13→2 common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter uses a type in common.0_domain.utils.either.
- The types involved
src.common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter.JsonwebtokenAdapter→src.common.0_domain.utils.either.Either
- Direction
- common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter, while a change to common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.3_infra.cryptography.jsonwebtoken.jsonwebtoken_adapter uses a module listed above it, which is the healthy direction.
14→2 common.0_domain.base.value-object uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.base.value-object uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.base.value-object.ValueObject→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.base.value-object uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.base.value-object, while a change to common.0_domain.base.value-object can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.base.value-object uses a module listed above it, which is the healthy direction.
14→8 common.0_domain.base.value-object uses common.0_domain.base.validator✕
- Connections
- 1 pair of types, where a type in common.0_domain.base.value-object uses a type in common.0_domain.base.validator.
- The types involved
src.common.0_domain.base.value-object.ValueObject→src.common.0_domain.base.validator.Validator
- Direction
- common.0_domain.base.value-object uses common.0_domain.base.validator, so a change to common.0_domain.base.validator can break common.0_domain.base.value-object, while a change to common.0_domain.base.value-object can't break common.0_domain.base.validator.
- Position
- Below the diagonal: common.0_domain.base.value-object uses a module listed above it, which is the healthy direction.
15→1 common.0_domain.validators.date_validator uses common.0_domain.base.domain-error✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.date_validator uses a type in common.0_domain.base.domain-error.
- The types involved
src.common.0_domain.validators.date_validator.DateValidator→src.common.0_domain.base.domain-error.DomainError
- Direction
- common.0_domain.validators.date_validator uses common.0_domain.base.domain-error, so a change to common.0_domain.base.domain-error can break common.0_domain.validators.date_validator, while a change to common.0_domain.validators.date_validator can't break common.0_domain.base.domain-error.
- Position
- Below the diagonal: common.0_domain.validators.date_validator uses a module listed above it, which is the healthy direction.
15→2 common.0_domain.validators.date_validator uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.date_validator uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.validators.date_validator.DateValidator→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.validators.date_validator uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.validators.date_validator, while a change to common.0_domain.validators.date_validator can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.validators.date_validator uses a module listed above it, which is the healthy direction.
15→8 common.0_domain.validators.date_validator uses common.0_domain.base.validator✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.date_validator uses a type in common.0_domain.base.validator.
- The types involved
src.common.0_domain.validators.date_validator.DateValidator→src.common.0_domain.base.validator.Validator
- Direction
- common.0_domain.validators.date_validator uses common.0_domain.base.validator, so a change to common.0_domain.base.validator can break common.0_domain.validators.date_validator, while a change to common.0_domain.validators.date_validator can't break common.0_domain.base.validator.
- Position
- Below the diagonal: common.0_domain.validators.date_validator uses a module listed above it, which is the healthy direction.
16→2 common.0_domain.validators.email_validator uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.email_validator uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.validators.email_validator.EmailValidator→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.validators.email_validator uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.validators.email_validator, while a change to common.0_domain.validators.email_validator can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.validators.email_validator uses a module listed above it, which is the healthy direction.
16→8 common.0_domain.validators.email_validator uses common.0_domain.base.validator✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.email_validator uses a type in common.0_domain.base.validator.
- The types involved
src.common.0_domain.validators.email_validator.EmailValidator→src.common.0_domain.base.validator.Validator
- Direction
- common.0_domain.validators.email_validator uses common.0_domain.base.validator, so a change to common.0_domain.base.validator can break common.0_domain.validators.email_validator, while a change to common.0_domain.validators.email_validator can't break common.0_domain.base.validator.
- Position
- Below the diagonal: common.0_domain.validators.email_validator uses a module listed above it, which is the healthy direction.
17→2 common.0_domain.validators.html_validator uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.html_validator uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.validators.html_validator.HtmlValidator→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.validators.html_validator uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.validators.html_validator, while a change to common.0_domain.validators.html_validator can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.validators.html_validator uses a module listed above it, which is the healthy direction.
17→8 common.0_domain.validators.html_validator uses common.0_domain.base.validator✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.html_validator uses a type in common.0_domain.base.validator.
- The types involved
src.common.0_domain.validators.html_validator.HtmlValidator→src.common.0_domain.base.validator.Validator
- Direction
- common.0_domain.validators.html_validator uses common.0_domain.base.validator, so a change to common.0_domain.base.validator can break common.0_domain.validators.html_validator, while a change to common.0_domain.validators.html_validator can't break common.0_domain.base.validator.
- Position
- Below the diagonal: common.0_domain.validators.html_validator uses a module listed above it, which is the healthy direction.
18→2 common.0_domain.validators.locale_validator uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.locale_validator uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.validators.locale_validator.LocaleValidator→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.validators.locale_validator uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.validators.locale_validator, while a change to common.0_domain.validators.locale_validator can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.validators.locale_validator uses a module listed above it, which is the healthy direction.
18→8 common.0_domain.validators.locale_validator uses common.0_domain.base.validator✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.locale_validator uses a type in common.0_domain.base.validator.
- The types involved
src.common.0_domain.validators.locale_validator.LocaleValidator→src.common.0_domain.base.validator.Validator
- Direction
- common.0_domain.validators.locale_validator uses common.0_domain.base.validator, so a change to common.0_domain.base.validator can break common.0_domain.validators.locale_validator, while a change to common.0_domain.validators.locale_validator can't break common.0_domain.base.validator.
- Position
- Below the diagonal: common.0_domain.validators.locale_validator uses a module listed above it, which is the healthy direction.
19→2 common.0_domain.validators.max-length_validator uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.max-length_validator uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.validators.max-length_validator.MaxLengthValidator→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.validators.max-length_validator uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.validators.max-length_validator, while a change to common.0_domain.validators.max-length_validator can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.validators.max-length_validator uses a module listed above it, which is the healthy direction.
19→8 common.0_domain.validators.max-length_validator uses common.0_domain.base.validator✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.max-length_validator uses a type in common.0_domain.base.validator.
- The types involved
src.common.0_domain.validators.max-length_validator.MaxLengthValidator→src.common.0_domain.base.validator.Validator
- Direction
- common.0_domain.validators.max-length_validator uses common.0_domain.base.validator, so a change to common.0_domain.base.validator can break common.0_domain.validators.max-length_validator, while a change to common.0_domain.validators.max-length_validator can't break common.0_domain.base.validator.
- Position
- Below the diagonal: common.0_domain.validators.max-length_validator uses a module listed above it, which is the healthy direction.
20→2 common.0_domain.validators.min-length_validator uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.min-length_validator uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.validators.min-length_validator.MinLengthValidator→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.validators.min-length_validator uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.validators.min-length_validator, while a change to common.0_domain.validators.min-length_validator can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.validators.min-length_validator uses a module listed above it, which is the healthy direction.
20→8 common.0_domain.validators.min-length_validator uses common.0_domain.base.validator✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.min-length_validator uses a type in common.0_domain.base.validator.
- The types involved
src.common.0_domain.validators.min-length_validator.MinLengthValidator→src.common.0_domain.base.validator.Validator
- Direction
- common.0_domain.validators.min-length_validator uses common.0_domain.base.validator, so a change to common.0_domain.base.validator can break common.0_domain.validators.min-length_validator, while a change to common.0_domain.validators.min-length_validator can't break common.0_domain.base.validator.
- Position
- Below the diagonal: common.0_domain.validators.min-length_validator uses a module listed above it, which is the healthy direction.
21→2 common.0_domain.validators.not-empty_validator uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.not-empty_validator uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.validators.not-empty_validator.NotEmptyValidator→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.validators.not-empty_validator uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.validators.not-empty_validator, while a change to common.0_domain.validators.not-empty_validator can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.validators.not-empty_validator uses a module listed above it, which is the healthy direction.
21→8 common.0_domain.validators.not-empty_validator uses common.0_domain.base.validator✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.not-empty_validator uses a type in common.0_domain.base.validator.
- The types involved
src.common.0_domain.validators.not-empty_validator.NotEmptyValidator→src.common.0_domain.base.validator.Validator
- Direction
- common.0_domain.validators.not-empty_validator uses common.0_domain.base.validator, so a change to common.0_domain.base.validator can break common.0_domain.validators.not-empty_validator, while a change to common.0_domain.validators.not-empty_validator can't break common.0_domain.base.validator.
- Position
- Below the diagonal: common.0_domain.validators.not-empty_validator uses a module listed above it, which is the healthy direction.
22→2 common.0_domain.validators.not-null_validator uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.not-null_validator uses a type in common.0_domain.utils.either.
- The types involved
src.common.0_domain.validators.not-null_validator.NotNullValidator→src.common.0_domain.utils.either.Either
- Direction
- common.0_domain.validators.not-null_validator uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.0_domain.validators.not-null_validator, while a change to common.0_domain.validators.not-null_validator can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.0_domain.validators.not-null_validator uses a module listed above it, which is the healthy direction.
22→8 common.0_domain.validators.not-null_validator uses common.0_domain.base.validator✕
- Connections
- 1 pair of types, where a type in common.0_domain.validators.not-null_validator uses a type in common.0_domain.base.validator.
- The types involved
src.common.0_domain.validators.not-null_validator.NotNullValidator→src.common.0_domain.base.validator.Validator
- Direction
- common.0_domain.validators.not-null_validator uses common.0_domain.base.validator, so a change to common.0_domain.base.validator can break common.0_domain.validators.not-null_validator, while a change to common.0_domain.validators.not-null_validator can't break common.0_domain.base.validator.
- Position
- Below the diagonal: common.0_domain.validators.not-null_validator uses a module listed above it, which is the healthy direction.
23→2 common.3_infra.events.amqplib.amqplib_adapter uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.3_infra.events.amqplib.amqplib_adapter uses a type in common.0_domain.utils.either.
- The types involved
src.common.3_infra.events.amqplib.amqplib_adapter.AmqplibAdapter→src.common.0_domain.utils.either.Either
- Direction
- common.3_infra.events.amqplib.amqplib_adapter uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.3_infra.events.amqplib.amqplib_adapter, while a change to common.3_infra.events.amqplib.amqplib_adapter can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.3_infra.events.amqplib.amqplib_adapter uses a module listed above it, which is the healthy direction.
23→10 common.3_infra.events.amqplib.amqplib_adapter uses common.2_presentation.errors.server_error✕
- Connections
- 1 pair of types, where a type in common.3_infra.events.amqplib.amqplib_adapter uses a type in common.2_presentation.errors.server_error.
- The types involved
src.common.3_infra.events.amqplib.amqplib_adapter.AmqplibAdapter→src.common.2_presentation.errors.server_error.ServerError
- Direction
- common.3_infra.events.amqplib.amqplib_adapter uses common.2_presentation.errors.server_error, so a change to common.2_presentation.errors.server_error can break common.3_infra.events.amqplib.amqplib_adapter, while a change to common.3_infra.events.amqplib.amqplib_adapter can't break common.2_presentation.errors.server_error.
- Position
- Below the diagonal: common.3_infra.events.amqplib.amqplib_adapter uses a module listed above it, which is the healthy direction.
24→2 common.3_infra.webapp.express.express_adapter uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in common.3_infra.webapp.express.express_adapter uses a type in common.0_domain.utils.either.
- The types involved
src.common.3_infra.webapp.express.express_adapter.ExpressAdapter→src.common.0_domain.utils.either.Either
- Direction
- common.3_infra.webapp.express.express_adapter uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break common.3_infra.webapp.express.express_adapter, while a change to common.3_infra.webapp.express.express_adapter can't break common.0_domain.utils.either.
- Position
- Below the diagonal: common.3_infra.webapp.express.express_adapter uses a module listed above it, which is the healthy direction.
24→3 common.3_infra.webapp.express.express_adapter uses common.1_application.middleware.middleware✕
- Connections
- 1 pair of types, where a type in common.3_infra.webapp.express.express_adapter uses a type in common.1_application.middleware.middleware.
- The types involved
src.common.3_infra.webapp.express.express_adapter.ExpressAdapter→src.common.1_application.middleware.middleware.Middleware
- Direction
- common.3_infra.webapp.express.express_adapter uses common.1_application.middleware.middleware, so a change to common.1_application.middleware.middleware can break common.3_infra.webapp.express.express_adapter, while a change to common.3_infra.webapp.express.express_adapter can't break common.1_application.middleware.middleware.
- Position
- Below the diagonal: common.3_infra.webapp.express.express_adapter uses a module listed above it, which is the healthy direction.
24→4 common.3_infra.webapp.express.express_adapter uses common.2_presentation.base.controller✕
- Connections
- 1 pair of types, where a type in common.3_infra.webapp.express.express_adapter uses a type in common.2_presentation.base.controller.
- The types involved
src.common.3_infra.webapp.express.express_adapter.ExpressAdapter→src.common.2_presentation.base.controller.Controller
- Direction
- common.3_infra.webapp.express.express_adapter uses common.2_presentation.base.controller, so a change to common.2_presentation.base.controller can break common.3_infra.webapp.express.express_adapter, while a change to common.3_infra.webapp.express.express_adapter can't break common.2_presentation.base.controller.
- Position
- Below the diagonal: common.3_infra.webapp.express.express_adapter uses a module listed above it, which is the healthy direction.
24→5 common.3_infra.webapp.express.express_adapter uses common.3_infra.webapp.web-app✕
- Connections
- 1 pair of types, where a type in common.3_infra.webapp.express.express_adapter uses a type in common.3_infra.webapp.web-app.
- The types involved
src.common.3_infra.webapp.express.express_adapter.ExpressAdapter→src.common.3_infra.webapp.web-app.WebApp
- Direction
- common.3_infra.webapp.express.express_adapter uses common.3_infra.webapp.web-app, so a change to common.3_infra.webapp.web-app can break common.3_infra.webapp.express.express_adapter, while a change to common.3_infra.webapp.express.express_adapter can't break common.3_infra.webapp.web-app.
- Position
- Below the diagonal: common.3_infra.webapp.express.express_adapter uses a module listed above it, which is the healthy direction.
24→10 common.3_infra.webapp.express.express_adapter uses common.2_presentation.errors.server_error✕
- Connections
- 1 pair of types, where a type in common.3_infra.webapp.express.express_adapter uses a type in common.2_presentation.errors.server_error.
- The types involved
src.common.3_infra.webapp.express.express_adapter.ExpressAdapter→src.common.2_presentation.errors.server_error.ServerError
- Direction
- common.3_infra.webapp.express.express_adapter uses common.2_presentation.errors.server_error, so a change to common.2_presentation.errors.server_error can break common.3_infra.webapp.express.express_adapter, while a change to common.3_infra.webapp.express.express_adapter can't break common.2_presentation.errors.server_error.
- Position
- Below the diagonal: common.3_infra.webapp.express.express_adapter uses a module listed above it, which is the healthy direction.
25→2 modules.identity.0_domain.entities.group_entity uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.entities.group_entity uses a type in common.0_domain.utils.either.
- The types involved
src.modules.identity.0_domain.entities.group_entity.GroupEntity→src.common.0_domain.utils.either.Either
- Direction
- modules.identity.0_domain.entities.group_entity uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.identity.0_domain.entities.group_entity, while a change to modules.identity.0_domain.entities.group_entity can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.identity.0_domain.entities.group_entity uses a module listed above it, which is the healthy direction.
25→7 modules.identity.0_domain.entities.group_entity uses common.0_domain.base.entity✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.entities.group_entity uses a type in common.0_domain.base.entity.
- The types involved
src.modules.identity.0_domain.entities.group_entity.GroupEntity→src.common.0_domain.base.entity.Entity
- Direction
- modules.identity.0_domain.entities.group_entity uses common.0_domain.base.entity, so a change to common.0_domain.base.entity can break modules.identity.0_domain.entities.group_entity, while a change to modules.identity.0_domain.entities.group_entity can't break common.0_domain.base.entity.
- Position
- Below the diagonal: modules.identity.0_domain.entities.group_entity uses a module listed above it, which is the healthy direction.
26→2 modules.communication.0_domain.value-objects.email_from_value-object uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_from_value-object uses a type in common.0_domain.utils.either.
- The types involved
src.modules.communication.0_domain.value-objects.email_from_value-object.EmailFrom→src.common.0_domain.utils.either.Either
- Direction
- modules.communication.0_domain.value-objects.email_from_value-object uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.communication.0_domain.value-objects.email_from_value-object, while a change to modules.communication.0_domain.value-objects.email_from_value-object can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_from_value-object uses a module listed above it, which is the healthy direction.
26→14 modules.communication.0_domain.value-objects.email_from_value-object uses common.0_domain.base.value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_from_value-object uses a type in common.0_domain.base.value-object.
- The types involved
src.modules.communication.0_domain.value-objects.email_from_value-object.EmailFrom→src.common.0_domain.base.value-object.ValueObject
- Direction
- modules.communication.0_domain.value-objects.email_from_value-object uses common.0_domain.base.value-object, so a change to common.0_domain.base.value-object can break modules.communication.0_domain.value-objects.email_from_value-object, while a change to modules.communication.0_domain.value-objects.email_from_value-object can't break common.0_domain.base.value-object.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_from_value-object uses a module listed above it, which is the healthy direction.
27→2 modules.communication.0_domain.value-objects.email_html_value-object uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_html_value-object uses a type in common.0_domain.utils.either.
- The types involved
src.modules.communication.0_domain.value-objects.email_html_value-object.EmailHtml→src.common.0_domain.utils.either.Either
- Direction
- modules.communication.0_domain.value-objects.email_html_value-object uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.communication.0_domain.value-objects.email_html_value-object, while a change to modules.communication.0_domain.value-objects.email_html_value-object can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_html_value-object uses a module listed above it, which is the healthy direction.
27→14 modules.communication.0_domain.value-objects.email_html_value-object uses common.0_domain.base.value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_html_value-object uses a type in common.0_domain.base.value-object.
- The types involved
src.modules.communication.0_domain.value-objects.email_html_value-object.EmailHtml→src.common.0_domain.base.value-object.ValueObject
- Direction
- modules.communication.0_domain.value-objects.email_html_value-object uses common.0_domain.base.value-object, so a change to common.0_domain.base.value-object can break modules.communication.0_domain.value-objects.email_html_value-object, while a change to modules.communication.0_domain.value-objects.email_html_value-object can't break common.0_domain.base.value-object.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_html_value-object uses a module listed above it, which is the healthy direction.
28→2 modules.communication.0_domain.value-objects.email_subject_value-object uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_subject_value-object uses a type in common.0_domain.utils.either.
- The types involved
src.modules.communication.0_domain.value-objects.email_subject_value-object.EmailSubject→src.common.0_domain.utils.either.Either
- Direction
- modules.communication.0_domain.value-objects.email_subject_value-object uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.communication.0_domain.value-objects.email_subject_value-object, while a change to modules.communication.0_domain.value-objects.email_subject_value-object can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_subject_value-object uses a module listed above it, which is the healthy direction.
28→14 modules.communication.0_domain.value-objects.email_subject_value-object uses common.0_domain.base.value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_subject_value-object uses a type in common.0_domain.base.value-object.
- The types involved
src.modules.communication.0_domain.value-objects.email_subject_value-object.EmailSubject→src.common.0_domain.base.value-object.ValueObject
- Direction
- modules.communication.0_domain.value-objects.email_subject_value-object uses common.0_domain.base.value-object, so a change to common.0_domain.base.value-object can break modules.communication.0_domain.value-objects.email_subject_value-object, while a change to modules.communication.0_domain.value-objects.email_subject_value-object can't break common.0_domain.base.value-object.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_subject_value-object uses a module listed above it, which is the healthy direction.
29→2 modules.communication.0_domain.value-objects.email_text_value-object uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_text_value-object uses a type in common.0_domain.utils.either.
- The types involved
src.modules.communication.0_domain.value-objects.email_text_value-object.EmailText→src.common.0_domain.utils.either.Either
- Direction
- modules.communication.0_domain.value-objects.email_text_value-object uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.communication.0_domain.value-objects.email_text_value-object, while a change to modules.communication.0_domain.value-objects.email_text_value-object can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_text_value-object uses a module listed above it, which is the healthy direction.
29→14 modules.communication.0_domain.value-objects.email_text_value-object uses common.0_domain.base.value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_text_value-object uses a type in common.0_domain.base.value-object.
- The types involved
src.modules.communication.0_domain.value-objects.email_text_value-object.EmailText→src.common.0_domain.base.value-object.ValueObject
- Direction
- modules.communication.0_domain.value-objects.email_text_value-object uses common.0_domain.base.value-object, so a change to common.0_domain.base.value-object can break modules.communication.0_domain.value-objects.email_text_value-object, while a change to modules.communication.0_domain.value-objects.email_text_value-object can't break common.0_domain.base.value-object.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_text_value-object uses a module listed above it, which is the healthy direction.
30→2 modules.communication.0_domain.value-objects.email_to_value-object uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_to_value-object uses a type in common.0_domain.utils.either.
- The types involved
src.modules.communication.0_domain.value-objects.email_to_value-object.EmailTo→src.common.0_domain.utils.either.Either
- Direction
- modules.communication.0_domain.value-objects.email_to_value-object uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.communication.0_domain.value-objects.email_to_value-object, while a change to modules.communication.0_domain.value-objects.email_to_value-object can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_to_value-object uses a module listed above it, which is the healthy direction.
30→14 modules.communication.0_domain.value-objects.email_to_value-object uses common.0_domain.base.value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.value-objects.email_to_value-object uses a type in common.0_domain.base.value-object.
- The types involved
src.modules.communication.0_domain.value-objects.email_to_value-object.EmailTo→src.common.0_domain.base.value-object.ValueObject
- Direction
- modules.communication.0_domain.value-objects.email_to_value-object uses common.0_domain.base.value-object, so a change to common.0_domain.base.value-object can break modules.communication.0_domain.value-objects.email_to_value-object, while a change to modules.communication.0_domain.value-objects.email_to_value-object can't break common.0_domain.base.value-object.
- Position
- Below the diagonal: modules.communication.0_domain.value-objects.email_to_value-object uses a module listed above it, which is the healthy direction.
31→2 modules.identity.0_domain.value-objects.user_email-confirmed_value-object uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.value-objects.user_email-confirmed_value-object uses a type in common.0_domain.utils.either.
- The types involved
src.modules.identity.0_domain.value-objects.user_email-confirmed_value-object.UserEmailConfirmed→src.common.0_domain.utils.either.Either
- Direction
- modules.identity.0_domain.value-objects.user_email-confirmed_value-object uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.identity.0_domain.value-objects.user_email-confirmed_value-object, while a change to modules.identity.0_domain.value-objects.user_email-confirmed_value-object can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.identity.0_domain.value-objects.user_email-confirmed_value-object uses a module listed above it, which is the healthy direction.
31→14 modules.identity.0_domain.value-objects.user_email-confirmed_value-object uses common.0_domain.base.value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.value-objects.user_email-confirmed_value-object uses a type in common.0_domain.base.value-object.
- The types involved
src.modules.identity.0_domain.value-objects.user_email-confirmed_value-object.UserEmailConfirmed→src.common.0_domain.base.value-object.ValueObject
- Direction
- modules.identity.0_domain.value-objects.user_email-confirmed_value-object uses common.0_domain.base.value-object, so a change to common.0_domain.base.value-object can break modules.identity.0_domain.value-objects.user_email-confirmed_value-object, while a change to modules.identity.0_domain.value-objects.user_email-confirmed_value-object can't break common.0_domain.base.value-object.
- Position
- Below the diagonal: modules.identity.0_domain.value-objects.user_email-confirmed_value-object uses a module listed above it, which is the healthy direction.
32→2 modules.identity.0_domain.value-objects.user_password_value-object uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.value-objects.user_password_value-object uses a type in common.0_domain.utils.either.
- The types involved
src.modules.identity.0_domain.value-objects.user_password_value-object.UserPassword→src.common.0_domain.utils.either.Either
- Direction
- modules.identity.0_domain.value-objects.user_password_value-object uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.identity.0_domain.value-objects.user_password_value-object, while a change to modules.identity.0_domain.value-objects.user_password_value-object can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.identity.0_domain.value-objects.user_password_value-object uses a module listed above it, which is the healthy direction.
32→14 modules.identity.0_domain.value-objects.user_password_value-object uses common.0_domain.base.value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.value-objects.user_password_value-object uses a type in common.0_domain.base.value-object.
- The types involved
src.modules.identity.0_domain.value-objects.user_password_value-object.UserPassword→src.common.0_domain.base.value-object.ValueObject
- Direction
- modules.identity.0_domain.value-objects.user_password_value-object uses common.0_domain.base.value-object, so a change to common.0_domain.base.value-object can break modules.identity.0_domain.value-objects.user_password_value-object, while a change to modules.identity.0_domain.value-objects.user_password_value-object can't break common.0_domain.base.value-object.
- Position
- Below the diagonal: modules.identity.0_domain.value-objects.user_password_value-object uses a module listed above it, which is the healthy direction.
33→2 modules.identity.0_domain.value-objects.user_token_value-object uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.value-objects.user_token_value-object uses a type in common.0_domain.utils.either.
- The types involved
src.modules.identity.0_domain.value-objects.user_token_value-object.UserToken→src.common.0_domain.utils.either.Either
- Direction
- modules.identity.0_domain.value-objects.user_token_value-object uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.identity.0_domain.value-objects.user_token_value-object, while a change to modules.identity.0_domain.value-objects.user_token_value-object can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.identity.0_domain.value-objects.user_token_value-object uses a module listed above it, which is the healthy direction.
33→14 modules.identity.0_domain.value-objects.user_token_value-object uses common.0_domain.base.value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.value-objects.user_token_value-object uses a type in common.0_domain.base.value-object.
- The types involved
src.modules.identity.0_domain.value-objects.user_token_value-object.UserToken→src.common.0_domain.base.value-object.ValueObject
- Direction
- modules.identity.0_domain.value-objects.user_token_value-object uses common.0_domain.base.value-object, so a change to common.0_domain.base.value-object can break modules.identity.0_domain.value-objects.user_token_value-object, while a change to modules.identity.0_domain.value-objects.user_token_value-object can't break common.0_domain.base.value-object.
- Position
- Below the diagonal: modules.identity.0_domain.value-objects.user_token_value-object uses a module listed above it, which is the healthy direction.
34→2 modules.communication.0_domain.entities.email_entity uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.entities.email_entity uses a type in common.0_domain.utils.either.
- The types involved
src.modules.communication.0_domain.entities.email_entity.EmailEntity→src.common.0_domain.utils.either.Either
- Direction
- modules.communication.0_domain.entities.email_entity uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.communication.0_domain.entities.email_entity, while a change to modules.communication.0_domain.entities.email_entity can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.communication.0_domain.entities.email_entity uses a module listed above it, which is the healthy direction.
34→7 modules.communication.0_domain.entities.email_entity uses common.0_domain.base.entity✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.entities.email_entity uses a type in common.0_domain.base.entity.
- The types involved
src.modules.communication.0_domain.entities.email_entity.EmailEntity→src.common.0_domain.base.entity.Entity
- Direction
- modules.communication.0_domain.entities.email_entity uses common.0_domain.base.entity, so a change to common.0_domain.base.entity can break modules.communication.0_domain.entities.email_entity, while a change to modules.communication.0_domain.entities.email_entity can't break common.0_domain.base.entity.
- Position
- Below the diagonal: modules.communication.0_domain.entities.email_entity uses a module listed above it, which is the healthy direction.
34→26 modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_from_value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.entities.email_entity uses a type in modules.communication.0_domain.value-objects.email_from_value-object.
- The types involved
src.modules.communication.0_domain.entities.email_entity.EmailEntity→src.modules.communication.0_domain.value-objects.email_from_value-object.EmailFrom
- Direction
- modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_from_value-object, so a change to modules.communication.0_domain.value-objects.email_from_value-object can break modules.communication.0_domain.entities.email_entity, while a change to modules.communication.0_domain.entities.email_entity can't break modules.communication.0_domain.value-objects.email_from_value-object.
- Position
- Below the diagonal: modules.communication.0_domain.entities.email_entity uses a module listed above it, which is the healthy direction.
34→27 modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_html_value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.entities.email_entity uses a type in modules.communication.0_domain.value-objects.email_html_value-object.
- The types involved
src.modules.communication.0_domain.entities.email_entity.EmailEntity→src.modules.communication.0_domain.value-objects.email_html_value-object.EmailHtml
- Direction
- modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_html_value-object, so a change to modules.communication.0_domain.value-objects.email_html_value-object can break modules.communication.0_domain.entities.email_entity, while a change to modules.communication.0_domain.entities.email_entity can't break modules.communication.0_domain.value-objects.email_html_value-object.
- Position
- Below the diagonal: modules.communication.0_domain.entities.email_entity uses a module listed above it, which is the healthy direction.
34→28 modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_subject_value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.entities.email_entity uses a type in modules.communication.0_domain.value-objects.email_subject_value-object.
- The types involved
src.modules.communication.0_domain.entities.email_entity.EmailEntity→src.modules.communication.0_domain.value-objects.email_subject_value-object.EmailSubject
- Direction
- modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_subject_value-object, so a change to modules.communication.0_domain.value-objects.email_subject_value-object can break modules.communication.0_domain.entities.email_entity, while a change to modules.communication.0_domain.entities.email_entity can't break modules.communication.0_domain.value-objects.email_subject_value-object.
- Position
- Below the diagonal: modules.communication.0_domain.entities.email_entity uses a module listed above it, which is the healthy direction.
34→29 modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_text_value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.entities.email_entity uses a type in modules.communication.0_domain.value-objects.email_text_value-object.
- The types involved
src.modules.communication.0_domain.entities.email_entity.EmailEntity→src.modules.communication.0_domain.value-objects.email_text_value-object.EmailText
- Direction
- modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_text_value-object, so a change to modules.communication.0_domain.value-objects.email_text_value-object can break modules.communication.0_domain.entities.email_entity, while a change to modules.communication.0_domain.entities.email_entity can't break modules.communication.0_domain.value-objects.email_text_value-object.
- Position
- Below the diagonal: modules.communication.0_domain.entities.email_entity uses a module listed above it, which is the healthy direction.
34→30 modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_to_value-object✕
- Connections
- 1 pair of types, where a type in modules.communication.0_domain.entities.email_entity uses a type in modules.communication.0_domain.value-objects.email_to_value-object.
- The types involved
src.modules.communication.0_domain.entities.email_entity.EmailEntity→src.modules.communication.0_domain.value-objects.email_to_value-object.EmailTo
- Direction
- modules.communication.0_domain.entities.email_entity uses modules.communication.0_domain.value-objects.email_to_value-object, so a change to modules.communication.0_domain.value-objects.email_to_value-object can break modules.communication.0_domain.entities.email_entity, while a change to modules.communication.0_domain.entities.email_entity can't break modules.communication.0_domain.value-objects.email_to_value-object.
- Position
- Below the diagonal: modules.communication.0_domain.entities.email_entity uses a module listed above it, which is the healthy direction.
35→2 modules.identity.0_domain.entities.user_entity uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.entities.user_entity uses a type in common.0_domain.utils.either.
- The types involved
src.modules.identity.0_domain.entities.user_entity.UserEntity→src.common.0_domain.utils.either.Either
- Direction
- modules.identity.0_domain.entities.user_entity uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.identity.0_domain.entities.user_entity, while a change to modules.identity.0_domain.entities.user_entity can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.identity.0_domain.entities.user_entity uses a module listed above it, which is the healthy direction.
35→7 modules.identity.0_domain.entities.user_entity uses common.0_domain.base.entity✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.entities.user_entity uses a type in common.0_domain.base.entity.
- The types involved
src.modules.identity.0_domain.entities.user_entity.UserEntity→src.common.0_domain.base.entity.Entity
- Direction
- modules.identity.0_domain.entities.user_entity uses common.0_domain.base.entity, so a change to common.0_domain.base.entity can break modules.identity.0_domain.entities.user_entity, while a change to modules.identity.0_domain.entities.user_entity can't break common.0_domain.base.entity.
- Position
- Below the diagonal: modules.identity.0_domain.entities.user_entity uses a module listed above it, which is the healthy direction.
35→31 modules.identity.0_domain.entities.user_entity uses modules.identity.0_domain.value-objects.user_email-confirmed_value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.entities.user_entity uses a type in modules.identity.0_domain.value-objects.user_email-confirmed_value-object.
- The types involved
src.modules.identity.0_domain.entities.user_entity.UserEntity→src.modules.identity.0_domain.value-objects.user_email-confirmed_value-object.UserEmailConfirmed
- Direction
- modules.identity.0_domain.entities.user_entity uses modules.identity.0_domain.value-objects.user_email-confirmed_value-object, so a change to modules.identity.0_domain.value-objects.user_email-confirmed_value-object can break modules.identity.0_domain.entities.user_entity, while a change to modules.identity.0_domain.entities.user_entity can't break modules.identity.0_domain.value-objects.user_email-confirmed_value-object.
- Position
- Below the diagonal: modules.identity.0_domain.entities.user_entity uses a module listed above it, which is the healthy direction.
35→32 modules.identity.0_domain.entities.user_entity uses modules.identity.0_domain.value-objects.user_password_value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.entities.user_entity uses a type in modules.identity.0_domain.value-objects.user_password_value-object.
- The types involved
src.modules.identity.0_domain.entities.user_entity.UserEntity→src.modules.identity.0_domain.value-objects.user_password_value-object.UserPassword
- Direction
- modules.identity.0_domain.entities.user_entity uses modules.identity.0_domain.value-objects.user_password_value-object, so a change to modules.identity.0_domain.value-objects.user_password_value-object can break modules.identity.0_domain.entities.user_entity, while a change to modules.identity.0_domain.entities.user_entity can't break modules.identity.0_domain.value-objects.user_password_value-object.
- Position
- Below the diagonal: modules.identity.0_domain.entities.user_entity uses a module listed above it, which is the healthy direction.
35→33 modules.identity.0_domain.entities.user_entity uses modules.identity.0_domain.value-objects.user_token_value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.entities.user_entity uses a type in modules.identity.0_domain.value-objects.user_token_value-object.
- The types involved
src.modules.identity.0_domain.entities.user_entity.UserEntity→src.modules.identity.0_domain.value-objects.user_token_value-object.UserToken
- Direction
- modules.identity.0_domain.entities.user_entity uses modules.identity.0_domain.value-objects.user_token_value-object, so a change to modules.identity.0_domain.value-objects.user_token_value-object can break modules.identity.0_domain.entities.user_entity, while a change to modules.identity.0_domain.entities.user_entity can't break modules.identity.0_domain.value-objects.user_token_value-object.
- Position
- Below the diagonal: modules.identity.0_domain.entities.user_entity uses a module listed above it, which is the healthy direction.
36→1 modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses common.0_domain.base.domain-error✕
- Connections
- 1 pair of types, where a type in modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses a type in common.0_domain.base.domain-error.
- The types involved
src.modules.communication.3_infra.communication.nodemailer.nodemailer_adapter.NodemailerAdapter→src.common.0_domain.base.domain-error.DomainError
- Direction
- modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses common.0_domain.base.domain-error, so a change to common.0_domain.base.domain-error can break modules.communication.3_infra.communication.nodemailer.nodemailer_adapter, while a change to modules.communication.3_infra.communication.nodemailer.nodemailer_adapter can't break common.0_domain.base.domain-error.
- Position
- Below the diagonal: modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses a module listed above it, which is the healthy direction.
36→2 modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses a type in common.0_domain.utils.either.
- The types involved
src.modules.communication.3_infra.communication.nodemailer.nodemailer_adapter.NodemailerAdapter→src.common.0_domain.utils.either.Either
- Direction
- modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.communication.3_infra.communication.nodemailer.nodemailer_adapter, while a change to modules.communication.3_infra.communication.nodemailer.nodemailer_adapter can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses a module listed above it, which is the healthy direction.
36→34 modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses modules.communication.0_domain.entities.email_entity✕
- Connections
- 1 pair of types, where a type in modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses a type in modules.communication.0_domain.entities.email_entity.
- The types involved
src.modules.communication.3_infra.communication.nodemailer.nodemailer_adapter.NodemailerAdapter→src.modules.communication.0_domain.entities.email_entity.EmailEntity
- Direction
- modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses modules.communication.0_domain.entities.email_entity, so a change to modules.communication.0_domain.entities.email_entity can break modules.communication.3_infra.communication.nodemailer.nodemailer_adapter, while a change to modules.communication.3_infra.communication.nodemailer.nodemailer_adapter can't break modules.communication.0_domain.entities.email_entity.
- Position
- Below the diagonal: modules.communication.3_infra.communication.nodemailer.nodemailer_adapter uses a module listed above it, which is the healthy direction.
37→31 modules.identity.0_domain.aggregates.user_aggregate uses modules.identity.0_domain.value-objects.user_email-confirmed_value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.aggregates.user_aggregate uses a type in modules.identity.0_domain.value-objects.user_email-confirmed_value-object.
- The types involved
src.modules.identity.0_domain.aggregates.user_aggregate.UserAggregate→src.modules.identity.0_domain.value-objects.user_email-confirmed_value-object.UserEmailConfirmed
- Direction
- modules.identity.0_domain.aggregates.user_aggregate uses modules.identity.0_domain.value-objects.user_email-confirmed_value-object, so a change to modules.identity.0_domain.value-objects.user_email-confirmed_value-object can break modules.identity.0_domain.aggregates.user_aggregate, while a change to modules.identity.0_domain.aggregates.user_aggregate can't break modules.identity.0_domain.value-objects.user_email-confirmed_value-object.
- Position
- Below the diagonal: modules.identity.0_domain.aggregates.user_aggregate uses a module listed above it, which is the healthy direction.
37→32 modules.identity.0_domain.aggregates.user_aggregate uses modules.identity.0_domain.value-objects.user_password_value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.aggregates.user_aggregate uses a type in modules.identity.0_domain.value-objects.user_password_value-object.
- The types involved
src.modules.identity.0_domain.aggregates.user_aggregate.UserAggregate→src.modules.identity.0_domain.value-objects.user_password_value-object.UserPassword
- Direction
- modules.identity.0_domain.aggregates.user_aggregate uses modules.identity.0_domain.value-objects.user_password_value-object, so a change to modules.identity.0_domain.value-objects.user_password_value-object can break modules.identity.0_domain.aggregates.user_aggregate, while a change to modules.identity.0_domain.aggregates.user_aggregate can't break modules.identity.0_domain.value-objects.user_password_value-object.
- Position
- Below the diagonal: modules.identity.0_domain.aggregates.user_aggregate uses a module listed above it, which is the healthy direction.
37→33 modules.identity.0_domain.aggregates.user_aggregate uses modules.identity.0_domain.value-objects.user_token_value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.aggregates.user_aggregate uses a type in modules.identity.0_domain.value-objects.user_token_value-object.
- The types involved
src.modules.identity.0_domain.aggregates.user_aggregate.UserAggregate→src.modules.identity.0_domain.value-objects.user_token_value-object.UserToken
- Direction
- modules.identity.0_domain.aggregates.user_aggregate uses modules.identity.0_domain.value-objects.user_token_value-object, so a change to modules.identity.0_domain.value-objects.user_token_value-object can break modules.identity.0_domain.aggregates.user_aggregate, while a change to modules.identity.0_domain.aggregates.user_aggregate can't break modules.identity.0_domain.value-objects.user_token_value-object.
- Position
- Below the diagonal: modules.identity.0_domain.aggregates.user_aggregate uses a module listed above it, which is the healthy direction.
37→35 modules.identity.0_domain.aggregates.user_aggregate uses modules.identity.0_domain.entities.user_entity✕
- Connections
- 1 pair of types, where a type in modules.identity.0_domain.aggregates.user_aggregate uses a type in modules.identity.0_domain.entities.user_entity.
- The types involved
src.modules.identity.0_domain.aggregates.user_aggregate.UserAggregate→src.modules.identity.0_domain.entities.user_entity.UserEntity
- Direction
- modules.identity.0_domain.aggregates.user_aggregate uses modules.identity.0_domain.entities.user_entity, so a change to modules.identity.0_domain.entities.user_entity can break modules.identity.0_domain.aggregates.user_aggregate, while a change to modules.identity.0_domain.aggregates.user_aggregate can't break modules.identity.0_domain.entities.user_entity.
- Position
- Below the diagonal: modules.identity.0_domain.aggregates.user_aggregate uses a module listed above it, which is the healthy direction.
38→2 modules.identity.1_application.use-cases.change-password_use-case uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.change-password_use-case uses a type in common.0_domain.utils.either.
- The types involved
src.modules.identity.1_application.use-cases.change-password_use-case.ChangePasswordUseCase→src.common.0_domain.utils.either.Either
- Direction
- modules.identity.1_application.use-cases.change-password_use-case uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.identity.1_application.use-cases.change-password_use-case, while a change to modules.identity.1_application.use-cases.change-password_use-case can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.change-password_use-case uses a module listed above it, which is the healthy direction.
38→9 modules.identity.1_application.use-cases.change-password_use-case uses common.1_application.base.use-case✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.change-password_use-case uses a type in common.1_application.base.use-case.
- The types involved
src.modules.identity.1_application.use-cases.change-password_use-case.ChangePasswordUseCase→src.common.1_application.base.use-case.UseCase
- Direction
- modules.identity.1_application.use-cases.change-password_use-case uses common.1_application.base.use-case, so a change to common.1_application.base.use-case can break modules.identity.1_application.use-cases.change-password_use-case, while a change to modules.identity.1_application.use-cases.change-password_use-case can't break common.1_application.base.use-case.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.change-password_use-case uses a module listed above it, which is the healthy direction.
38→32 modules.identity.1_application.use-cases.change-password_use-case uses modules.identity.0_domain.value-objects.user_password_value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.change-password_use-case uses a type in modules.identity.0_domain.value-objects.user_password_value-object.
- The types involved
src.modules.identity.1_application.use-cases.change-password_use-case.ChangePasswordUseCase→src.modules.identity.0_domain.value-objects.user_password_value-object.UserPassword
- Direction
- modules.identity.1_application.use-cases.change-password_use-case uses modules.identity.0_domain.value-objects.user_password_value-object, so a change to modules.identity.0_domain.value-objects.user_password_value-object can break modules.identity.1_application.use-cases.change-password_use-case, while a change to modules.identity.1_application.use-cases.change-password_use-case can't break modules.identity.0_domain.value-objects.user_password_value-object.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.change-password_use-case uses a module listed above it, which is the healthy direction.
38→37 modules.identity.1_application.use-cases.change-password_use-case uses modules.identity.0_domain.aggregates.user_aggregate✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.change-password_use-case uses a type in modules.identity.0_domain.aggregates.user_aggregate.
- The types involved
src.modules.identity.1_application.use-cases.change-password_use-case.ChangePasswordUseCase→src.modules.identity.0_domain.aggregates.user_aggregate.UserAggregate
- Direction
- modules.identity.1_application.use-cases.change-password_use-case uses modules.identity.0_domain.aggregates.user_aggregate, so a change to modules.identity.0_domain.aggregates.user_aggregate can break modules.identity.1_application.use-cases.change-password_use-case, while a change to modules.identity.1_application.use-cases.change-password_use-case can't break modules.identity.0_domain.aggregates.user_aggregate.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.change-password_use-case uses a module listed above it, which is the healthy direction.
39→2 modules.identity.1_application.use-cases.confirm-email_use-case uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.confirm-email_use-case uses a type in common.0_domain.utils.either.
- The types involved
src.modules.identity.1_application.use-cases.confirm-email_use-case.ConfirmEmailUseCase→src.common.0_domain.utils.either.Either
- Direction
- modules.identity.1_application.use-cases.confirm-email_use-case uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.identity.1_application.use-cases.confirm-email_use-case, while a change to modules.identity.1_application.use-cases.confirm-email_use-case can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.confirm-email_use-case uses a module listed above it, which is the healthy direction.
39→9 modules.identity.1_application.use-cases.confirm-email_use-case uses common.1_application.base.use-case✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.confirm-email_use-case uses a type in common.1_application.base.use-case.
- The types involved
src.modules.identity.1_application.use-cases.confirm-email_use-case.ConfirmEmailUseCase→src.common.1_application.base.use-case.UseCase
- Direction
- modules.identity.1_application.use-cases.confirm-email_use-case uses common.1_application.base.use-case, so a change to common.1_application.base.use-case can break modules.identity.1_application.use-cases.confirm-email_use-case, while a change to modules.identity.1_application.use-cases.confirm-email_use-case can't break common.1_application.base.use-case.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.confirm-email_use-case uses a module listed above it, which is the healthy direction.
39→31 modules.identity.1_application.use-cases.confirm-email_use-case uses modules.identity.0_domain.value-objects.user_email-confirmed_value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.confirm-email_use-case uses a type in modules.identity.0_domain.value-objects.user_email-confirmed_value-object.
- The types involved
src.modules.identity.1_application.use-cases.confirm-email_use-case.ConfirmEmailUseCase→src.modules.identity.0_domain.value-objects.user_email-confirmed_value-object.UserEmailConfirmed
- Direction
- modules.identity.1_application.use-cases.confirm-email_use-case uses modules.identity.0_domain.value-objects.user_email-confirmed_value-object, so a change to modules.identity.0_domain.value-objects.user_email-confirmed_value-object can break modules.identity.1_application.use-cases.confirm-email_use-case, while a change to modules.identity.1_application.use-cases.confirm-email_use-case can't break modules.identity.0_domain.value-objects.user_email-confirmed_value-object.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.confirm-email_use-case uses a module listed above it, which is the healthy direction.
39→37 modules.identity.1_application.use-cases.confirm-email_use-case uses modules.identity.0_domain.aggregates.user_aggregate✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.confirm-email_use-case uses a type in modules.identity.0_domain.aggregates.user_aggregate.
- The types involved
src.modules.identity.1_application.use-cases.confirm-email_use-case.ConfirmEmailUseCase→src.modules.identity.0_domain.aggregates.user_aggregate.UserAggregate
- Direction
- modules.identity.1_application.use-cases.confirm-email_use-case uses modules.identity.0_domain.aggregates.user_aggregate, so a change to modules.identity.0_domain.aggregates.user_aggregate can break modules.identity.1_application.use-cases.confirm-email_use-case, while a change to modules.identity.1_application.use-cases.confirm-email_use-case can't break modules.identity.0_domain.aggregates.user_aggregate.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.confirm-email_use-case uses a module listed above it, which is the healthy direction.
40→2 modules.identity.1_application.use-cases.sign-in_use-case uses common.0_domain.utils.either✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.sign-in_use-case uses a type in common.0_domain.utils.either.
- The types involved
src.modules.identity.1_application.use-cases.sign-in_use-case.SignInUseCase→src.common.0_domain.utils.either.Either
- Direction
- modules.identity.1_application.use-cases.sign-in_use-case uses common.0_domain.utils.either, so a change to common.0_domain.utils.either can break modules.identity.1_application.use-cases.sign-in_use-case, while a change to modules.identity.1_application.use-cases.sign-in_use-case can't break common.0_domain.utils.either.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.sign-in_use-case uses a module listed above it, which is the healthy direction.
40→9 modules.identity.1_application.use-cases.sign-in_use-case uses common.1_application.base.use-case✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.sign-in_use-case uses a type in common.1_application.base.use-case.
- The types involved
src.modules.identity.1_application.use-cases.sign-in_use-case.SignInUseCase→src.common.1_application.base.use-case.UseCase
- Direction
- modules.identity.1_application.use-cases.sign-in_use-case uses common.1_application.base.use-case, so a change to common.1_application.base.use-case can break modules.identity.1_application.use-cases.sign-in_use-case, while a change to modules.identity.1_application.use-cases.sign-in_use-case can't break common.1_application.base.use-case.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.sign-in_use-case uses a module listed above it, which is the healthy direction.
40→33 modules.identity.1_application.use-cases.sign-in_use-case uses modules.identity.0_domain.value-objects.user_token_value-object✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.sign-in_use-case uses a type in modules.identity.0_domain.value-objects.user_token_value-object.
- The types involved
src.modules.identity.1_application.use-cases.sign-in_use-case.SignInUseCase→src.modules.identity.0_domain.value-objects.user_token_value-object.UserToken
- Direction
- modules.identity.1_application.use-cases.sign-in_use-case uses modules.identity.0_domain.value-objects.user_token_value-object, so a change to modules.identity.0_domain.value-objects.user_token_value-object can break modules.identity.1_application.use-cases.sign-in_use-case, while a change to modules.identity.1_application.use-cases.sign-in_use-case can't break modules.identity.0_domain.value-objects.user_token_value-object.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.sign-in_use-case uses a module listed above it, which is the healthy direction.
40→37 modules.identity.1_application.use-cases.sign-in_use-case uses modules.identity.0_domain.aggregates.user_aggregate✕
- Connections
- 1 pair of types, where a type in modules.identity.1_application.use-cases.sign-in_use-case uses a type in modules.identity.0_domain.aggregates.user_aggregate.
- The types involved
src.modules.identity.1_application.use-cases.sign-in_use-case.SignInUseCase→src.modules.identity.0_domain.aggregates.user_aggregate.UserAggregate
- Direction
- modules.identity.1_application.use-cases.sign-in_use-case uses modules.identity.0_domain.aggregates.user_aggregate, so a change to modules.identity.0_domain.aggregates.user_aggregate can break modules.identity.1_application.use-cases.sign-in_use-case, while a change to modules.identity.1_application.use-cases.sign-in_use-case can't break modules.identity.0_domain.aggregates.user_aggregate.
- Position
- Below the diagonal: modules.identity.1_application.use-cases.sign-in_use-case uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 65 | High / Critical |
| A07:2025 — Authentication Failures | 13 | High / Critical |
| A02:2025 — Security Misconfiguration | 4 | Medium |
| A05:2025 — Injection | 3 | High / Critical |
Roadmap
Top priorities: Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED; Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may 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.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED. | +6.6 pts | Low | REDACTED Scanning |
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +6.1 pts | Medium | Access Controls |
| 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. | +5.7 pts | Medium | Data Protection |
| Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. | +2.4 pts | Low | Platform End-of-Life |
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +2.2 pts | Low | ADR Quality |
| Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. | +2.1 pts | Low | Secrets (history) |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +3.1 pts | Medium | Security & performance tooling |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.5 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 3.0 | Slop | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 5.8 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 6.1 | Mixed | IaC & Container Security: Medium IaC: REDACTED |
| package.json | 7.1 | Mixed | Dependency Hygiene: Deprecated: @faker-js/faker |
| REDACTED | 7.2 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| .nvmrc | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: Node.js 18 |
| test/common/3.infra/events/amqplib/amqplib.adapter.unit-test.ts | 9.0 | Near-clean | Test Quality: Mock-dominated test: calls connection.createChannel with correct params |
| test/common/3.infra/webapp/express/express.adapter.unit-test.ts | 9.3 | Near-clean | Test Quality: Mock-dominated test: calls app.listen with correct params |
| test/modules/communication/3.infra/communication/nodemailer/nodemailer.adapter.unit-test.ts | 9.5 | Near-clean | Test Quality: Mock-dominated test: calls nodemailer.sendMail with correct params |
| test/common/3.infra/validation/ajv/ajv.adapter.unit-test.ts | 9.5 | Near-clean | Test Quality: Mock-dominated test: calls ajv.validate with correct params |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 77 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.
What we checked — 77 dimensions across the health lenses
- Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 176 of 188 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy · checkov | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 · 3.2.533 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the vitest suite in the repository root ran and not one test passed (Starting the MongoMemoryServer Instance failed, enable debug log for more information. Error:), so the coverage would describe the failed run, not the code — but the repository pins Node v18.16.1 in .nvmrc and the analyzer image ran it on Node 22, so the failure describes our runtime, not the suite. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo. In the meantime, commit (or publish into the working tree) the lcov/Cobertura report your CI produces and the real number is read on the next scan. You can widen what we reach: optional: commit the lcov/Cobertura report your CI produces, and the real number is read on the next scan.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability NOT MEASURED: the JavaScript/TypeScript suite could not be re-run in the analyzer sandbox — the vitest run in the repository root produced no per-test report (Starting the MongoMemoryServer Instance failed, enable debug log for more information. Error:). This is OUR limitation, not a defect in the repo — it is excluded from the score.
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability for the vitest suite in the repository root was NOT MEASURED: the vitest run in the repository root produced no per-test report (Starting the MongoMemoryServer Instance failed, enable debug log for more information. Error:). This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository's dependency manifests WERE read and their pinning discipline assessed; what went unanswered is the currency half, because registry.npmjs.org — the registry that answers it — was asked and did not reply (registry returned 429). This is OUR side and it is an ENVIRONMENT fault, not a missing collector: the collector exists and ran. An HTTP 403 here is what this scan's egress allowlist returns for a host that is not on it, so the remedy is to add registry.npmjs.org to the allowlist and re-run — not to build anything.
- 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-contributor repository — bus factor is not applicable (1 contributor(s) across 291 commit(s) sampled, automation and bot accounts excluded). Concentration needs a team to concentrate: with one contributor there is nobody to spread the knowledge to, so there is nothing here for the owner to act on.
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/common/2.presentation/documentation/api-documenter.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 15 — the compose project is invalid) — time="2026-11-09T04:46:12Z" level=warning msg="The \"DEBUG_PORT\" variable is not set. Defaulting to a blank string." time="2026-11-09T04:46:12Z" level=warning msg="The \"DEBUG_PORT\" variable is not set. Defaulting to a blank string." time="2026-11-09T04:46:12Z" level=warning msg="The \"PERSISTENCE\" variable is not set. Defaulting to a blank string." no port specified: :<empty>; runtime evidence skipped.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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.
- 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").
- 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 publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- 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.
- 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".
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
0 method(s) exceeded the cognitive complexity threshold of 15.
D3 · God Classes
0 god class(es) detected.
D6 · Cohesion (LCOM4)
0 of 17 classes have LCOM4 above 3.
D9 · Test Distribution
447 test methods: 447 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 447 `it`/`test` case(s) across 93 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 447 tests.
D13 · REDACTED Scanning
7 secret(s) detected.
What to do
- Resolve the 8 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (2), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (8 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 4683 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 5 document(s) read across 1 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D26 · Project Cohesion
1 of 1 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 4 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
3 finding(s): 0 critical, 2 high, 1 medium, 0 low. semgrep hit a parse error in 2 file(s) — `src/common/2.presentation/documentation/api-documenter.ts` (lines 23–24), `src/common/3.infra/persistence/persistence.fixture.ts` (lines 6–7) — 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.
What to do
- 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).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
65 finding(s): 11 critical, 32 high, 15 medium, 7 low.
What to do
- Resolve the 32 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (32). — One of this dimension's main actionable groups (32 issue-level).
- Resolve the 14 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (14). — One of this dimension's main actionable groups (14 warning-level).
- Resolve the 11 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (11). — One of this dimension's main actionable groups (11 issue-level).
D31 · IaC & Container Security
4 finding(s): 0 critical, 0 high, 4 medium, 0 low.
What to do
- Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
D34 · Knowledge Freshness
12 of 12 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/modules/identity/3.infra/persistence/postgres/repositories/postgres-user.repository.ts. Counted over 12 of the 187 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 12 Orphaned file finding(s) in Knowledge Freshness — start with postgres-user.repository.ts, amqplib.adapter.ts, express.adapter.ts. — One of this dimension's main actionable groups (12 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 20 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
AX3 · Project dependency cycles
AX4 · Dependency direction
AX5 · Architecture & structure
AX6 · Interface segregation
C1 · Data Protection
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.
C2 · Access Controls
- This repository serves requests — express() (src/common/3.infra/webapp/express/express.adapter.ts:22) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — src/common/3.infra/webapp/express/express.adapter.ts:22
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
DM1 · Aggregate boundaries
- `UserAggregate` references the aggregate root `GroupEntity` directly (via `groups`) — hold its `GroupEntityId` instead. (×2) — src/modules/identity/0.domain/aggregates/user.aggregate.ts:45, src/modules/identity/0.domain/aggregates/user.aggregate.ts:10
What to do
- Reference other aggregates by their strongly-typed id, never by object reference, so each aggregate stays an independent consistency boundary.
DM11 · Constructible invalid state
DM4 · Rich vs anemic model
- `UserAggregate` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/identity/0.domain/aggregates/user.aggregate.ts:13
- `GroupEntity` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/identity/0.domain/entities/group.entity.ts:15
- `UserEntity` is an aggregate/entity with 6 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — src/modules/identity/0.domain/entities/user.entity.ts:30
- `AggregateStub` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — test/common/_doubles/stubs/aggregate.stub.ts:6
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `GroupEntity` exposes publicly writable state (name). — src/modules/identity/0.domain/entities/group.entity.ts:15
- `UserEntity` exposes publicly writable state (emailConfirmed, password, token). — src/modules/identity/0.domain/entities/user.entity.ts:30
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).
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- `src/common/2.presentation/factories/server-error.factory.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. — src/common/2.presentation/factories/server-error.factory.ts:9
- `src/common/0.domain/utils/var.ts` reports through `console.*` at line 3 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/common/0.domain/utils/var.ts:3
- `src/common/0.domain/utils/var.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. — src/common/0.domain/utils/var.ts:9
- `src/common/0.domain/utils/var.ts` reports through `console.*` at line 21 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/common/0.domain/utils/var.ts:21
- `src/common/0.domain/utils/var.ts` reports through `console.*` at line 33 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/common/0.domain/utils/var.ts:33
- `src/common/0.domain/utils/var.ts` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/common/0.domain/utils/var.ts:45
- `src/common/0.domain/utils/var.ts` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — src/common/0.domain/utils/var.ts:53
What to do
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1017 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.
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:42
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
- Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
What to do
- Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
- Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P8 · Schema migrations
- This repository versions its schema (TypeORM migrations), but TypeORM synchronize: true here builds or alters the schema from the model as well, outside that history — the two paths can disagree about the shape, and a change made this way is never a reviewed migration. Turn it off and let TypeORM migrations own the schema. — src/common/3.infra/persistence/postgres/data-sources/postgres-test.data-source.ts:20
What to do
- Turn off TypeORM synchronize: true in production and let the versioned migrations own the schema.
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 6 duplicated blocks under src/modules/ have copies in at least two of the sibling directories communication, identity — 3 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 6 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 6 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 6 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — src/modules/communication/1.application/use-cases/send-email-confirmation.use-case.ts:12
- src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-user.repository.ts:17 · src/modules/identity/3.infra/persistence/postgres/repositories/postgres-user.repository.ts:14 — the two spans are one implementation copied and then locally edited — 460 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. — src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-user.repository.ts:17
- src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-group.repository.ts:10 · src/modules/identity/3.infra/persistence/postgres/repositories/postgres-group.repository.ts:10 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-group.repository.ts:10
- src/modules/identity/3.infra/persistence/mongodb/mappers/mongodb-user.mapper.ts:6 · src/modules/identity/3.infra/persistence/postgres/mappers/postgres-user.mapper.ts:4 — the two spans are one implementation copied and then locally edited — 196 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. — src/modules/identity/3.infra/persistence/mongodb/mappers/mongodb-user.mapper.ts:6
- src/common/3.infra/events/amqplib/amqplib.adapter.ts:85 · src/common/3.infra/events/amqplib/amqplib.adapter.ts:114 — 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. — src/common/3.infra/events/amqplib/amqplib.adapter.ts:85
- src/modules/identity/2.presentation/controllers/change-password.controller.ts:9 · src/modules/identity/2.presentation/controllers/create-group.controller.ts:9 · src/modules/identity/2.presentation/controllers/sign-in.controller.ts:9 · src/modules/identity/2.presentation/controllers/sign-up.controller.ts:9 — the 4 copies are spread across 4 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — src/modules/identity/2.presentation/controllers/change-password.controller.ts:9
- src/modules/identity/1.application/use-cases/change-password.use-case.ts:87 · src/modules/identity/1.application/use-cases/confirm-email.use-case.ts:50 · src/modules/identity/1.application/use-cases/sign-in.use-case.ts:104 — 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. — src/modules/identity/1.application/use-cases/change-password.use-case.ts:87
- src/common/3.infra/persistence/mongodb/client/mongodb.client.ts:44 · src/common/3.infra/persistence/postgres/client/postgres.client.ts:42 — 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. — src/common/3.infra/persistence/mongodb/client/mongodb.client.ts:44
- src/common/3.infra/webapp/express/express.adapter.ts:30 · src/common/3.infra/webapp/express/express.adapter.ts:46 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/common/3.infra/webapp/express/express.adapter.ts:30
- src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-group.repository.ts:57 · src/modules/identity/3.infra/persistence/postgres/repositories/postgres-group.repository.ts:50 — 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. — src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-group.repository.ts:57
- src/modules/identity/2.presentation/controllers/change-password.controller.ts:18 · src/modules/identity/2.presentation/controllers/confirm-email.controller.ts:18 · src/modules/identity/2.presentation/controllers/create-group.controller.ts:18 · src/modules/identity/2.presentation/controllers/sign-in.controller.ts:18 · +1 more site(s) not listed — the 5 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 5 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. — src/modules/identity/2.presentation/controllers/change-password.controller.ts:18
- src/common/0.domain/utils/either.ts:3 · src/common/0.domain/utils/either.ts:19 — the two spans are one implementation copied and then locally edited — 66 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/common/0.domain/utils/either.ts:3
- src/common/3.infra/webapp/express/express.adapter.ts:67 · src/common/3.infra/webapp/express/express.adapter.ts:86 — 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. — src/common/3.infra/webapp/express/express.adapter.ts:67
- src/common/4.main/container/persistence/make-mongodb.ts:12 · src/common/4.main/container/persistence/make-postgres.ts:12 — 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. — src/common/4.main/container/persistence/make-mongodb.ts:12
- src/modules/communication/0.domain/value-objects/email.from.value-object.ts:8 · src/modules/identity/0.domain/value-objects/user.email.value-object.ts:8 — 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. — src/modules/communication/0.domain/value-objects/email.from.value-object.ts:8
- src/common/2.presentation/middlewares/auth.middleware.ts:11 · src/common/2.presentation/middlewares/schema-validator.middleware.ts:8 · src/common/3.infra/cryptography/argon/argon.adapter.ts:8 · src/modules/communication/3.infra/communication/nodemailer/nodemailer.adapter.ts:11 · +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. — src/common/2.presentation/middlewares/auth.middleware.ts:11
- src/common/3.infra/events/amqplib/amqplib.adapter.ts:32 · src/common/3.infra/events/amqplib/amqplib.adapter.ts:56 — 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. — src/common/3.infra/events/amqplib/amqplib.adapter.ts:32
- src/common/3.infra/webapp/express/express.adapter.ts:52 · src/common/3.infra/webapp/express/express.adapter.ts:88 — 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. — src/common/3.infra/webapp/express/express.adapter.ts:52
- src/modules/communication/0.domain/value-objects/email.from.value-object.ts:9 · src/modules/communication/0.domain/value-objects/email.to.value-object.ts:9 · src/modules/identity/0.domain/value-objects/user.email.value-object.ts:9 — the 3 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. 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. — src/modules/communication/0.domain/value-objects/email.from.value-object.ts:9
- src/modules/identity/0.domain/value-objects/group.name.value-object.ts:7 · src/modules/identity/0.domain/value-objects/user.name.value-object.ts:7 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/modules/identity/0.domain/value-objects/group.name.value-object.ts:7
- src/modules/identity/0.domain/value-objects/user.password.value-object.ts:7 · src/modules/identity/0.domain/value-objects/user.token.value-object.ts:7 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — src/modules/identity/0.domain/value-objects/user.password.value-object.ts:7
- src/common/3.infra/persistence/mongodb/base/mongodb.fixture.ts:7 · src/common/3.infra/persistence/postgres/base/postgres.fixture.ts:5 — 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. — src/common/3.infra/persistence/mongodb/base/mongodb.fixture.ts:7
- src/modules/communication/0.domain/value-objects/email.subject.value-object.ts:8 · src/modules/identity/0.domain/value-objects/group.name.value-object.ts:8 · src/modules/identity/0.domain/value-objects/user.name.value-object.ts:8 — the 3 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. 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. — src/modules/communication/0.domain/value-objects/email.subject.value-object.ts:8
- src/common/0.domain/validators/date.validator.ts:4 · src/common/0.domain/validators/not-empty.validator.ts:3 · src/common/0.domain/validators/not-null.validator.ts:3 — 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. — src/common/0.domain/validators/date.validator.ts:4
- src/common/3.infra/persistence/mongodb/base/mongodb.fixture.ts:18 · src/common/3.infra/persistence/postgres/base/postgres.fixture.ts:16 — 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. — src/common/3.infra/persistence/mongodb/base/mongodb.fixture.ts:18
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.
R11 · Import Boundaries
- vitest.setup.ts:1 imports @shelf/jest-mongodb/lib/setup, 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. — vitest.setup.ts:1
- vitest.setup.ts:2 imports @shelf/jest-mongodb/lib/teardown, 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. — vitest.setup.ts:2
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×10) — src/modules/identity/2.presentation/routes/confirm-email/confirm-email.path.ts:1, src/common/4.main/scripts/init-persistence.ts:1, src/common/4.main/server.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
- 45 outdated package(s); JS/npm CVEs scored in D30
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
R6 · Tooling
R7 · Dead Code
- Unreachable from the 3 application, 4 tooling and 111 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 (3 application, 4 tooling, 111 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (src/modules/identity/4.main/setup/webapp/identity.api-specification.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 (×5) — src/modules/identity/2.presentation/routes/change-password/change-password.path.ts, src/modules/identity/2.presentation/routes/sign-in/sign-in.path.ts, src/modules/identity/2.presentation/routes/sign-up/sign-up.path.ts, …
- no import path from any entry point (3 application, 4 tooling, 111 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 — src/modules/identity/4.main/setup/webapp/identity.api-specification.ts
- Nothing imports this binding — it is safe to review for removal. (×3) — src/common/2.presentation/factories/client-error.factory.ts:4, src/common/2.presentation/factories/server-error.factory.ts:3, src/modules/identity/3.infra/persistence/mongodb/entities/mongodb-group.entity.ts:22
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Declared in the root package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- src/common/4.main/container/index.ts → src/common/4.main/container/persistence/make-mongodb.ts → src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-group.repository.ts → src/common/4.main/container/index.ts (one verified cycle inside a mutually-dependent group of 7 files) — src/common/4.main/container/index.ts:20
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — src/common/3.infra/webapp/express/express.adapter.ts:34
What to do
- Enforce HTTPS on each listed server: serve TLS itself, or redirect plain requests to `https://` and send `Strict-Transport-Security` (`helmet()` does by default) behind the TLS-terminating proxy — and commit that proxy's configuration beside the service. A server only this machine reaches should bind `127.0.0.1`.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X4 · Structured logging
X5 · Nullable reference types
- 0/2 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.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 73% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 79% | Adequate — gated by D26 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 54% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 33% | Weak — gated by D13, P3, P8 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 30% | Weak — gated by C1, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 47% | Weak — gated by DM4, DM5, DM1 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 3 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 9 observation(s) recorded · Dependency currency not established — registry.npmjs.org did not answer
- P12 CI test-gate honesty — 1 observation(s) recorded · Reported, not scored — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
- X10 Duplicated predicate — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 5 control(s) we could not find positive evidence for
- C3 Audit Trail — Repo shows no audit-logging mechanism (an audit-log table or model, an ORM write hook that records changes — a TypeORM/MikroORM subscriber, a Sequelize or Mongoose hook, Prisma middleware — or a change-history plugin such as mongoose-history or sequelize-paper-trail) for sensitive changes — absence of evidence is not evidence of a working control. Record an audit trail in code (or document where it lives) so this dimension can be scored.
- C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
- C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
- P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 56 check(s) not relevant to this codebase
- AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
- AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
- AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
- AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
- AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
- AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
- AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
- AX1 Captive dependencies — Not applicable: this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — time="2026-11-09T04:46:12Z" level=warning msg="The \"DEBUG_PORT\" variable is not set. Defaulting to a blank string." time="2026-11-09T04:46:12Z" level=warning msg="The \"DEBUG_PORT\" variable is not set. Defaulting to a blank string." time="2026-11-09T04:46:12Z" level=warning msg="The \"PERSISTENCE\" variable is not set. Defaulting to a blank string." no port specified: :<empty>; 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 — Test reliability not measured — JavaScript/TypeScript suite did not run
- D14 License Compliance — Not scored — this repository's 428 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 18 of them (registry returned 429), and a licence verdict over part of a dependency graph is not a licence verdict. Nothing is asserted about this repository's licensing in either direction.
- D16 Bus Factor — single-contributor 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.
- D21 Naming Consistency — D21 withholds its sibling role token rows: 3 candidate(s) found and not reported.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- 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+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (identity), 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 — Too few judgeable comments (0 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- 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.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- 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 — JavaScript/TypeScript suite
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- 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 none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 4 current-state document(s) make no claim of a kind M4 checks. 3 claim(s) of kinds M4 does not check were not checked (command argument 3); M4 checks only links and versions and artefact counts.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: src/common/3.infra/webapp/express/express.adapter.ts:22 (express()))
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `vitest --coverage --coverage.reporter=lcovonly`) 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 package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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)
Critical — 60 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Aggregate holds a reference to another aggregate: UserAggregate.groups src/modules/identity/0.domain/aggregates/user.aggregate.ts:45
- Aggregate holds a reference to another aggregate: UserAggregate.groups src/modules/identity/0.domain/aggregates/user.aggregate.ts:10
- REDACTED
- REDACTED
- Import cycle (3 files) src/common/4.main/container/index.ts:20
Serious — 75 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No test reaches this file src/modules/identity/2.presentation/routes/confirm-email/confirm-email.path.ts:1
- No test reaches this file src/common/4.main/scripts/init-persistence.ts:1
- No test reaches this file src/common/4.main/server.ts:1
- No test reaches this file src/modules/communication/4.main/factories/handlers/user-send-email-confirmation.handler.factory.ts:1
- No test reaches this file src/modules/identity/4.main/factories/handlers/user-set-group.handler.factory.ts:1
- No test reaches this file src/modules/communication/1.application/events/queues/user-send-email-confirmation.queue.ts:1
- No test reaches this file src/common/4.main/setup/events/index.ts:1
- No test reaches this file src/modules/communication/4.main/setup/handlers/communication.handlers.ts:1
- No test reaches this file src/modules/identity/4.main/setup/handlers/identity.handlers.ts:1
- No test reaches this file src/common/4.main/setup/handlers/index.ts:1
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Anemic entity: UserAggregate src/modules/identity/0.domain/aggregates/user.aggregate.ts:13
- Anemic entity: GroupEntity src/modules/identity/0.domain/entities/group.entity.ts:15
- Anemic entity: UserEntity src/modules/identity/0.domain/entities/user.entity.ts:30
- Anemic entity: AggregateStub test/common/_doubles/stubs/aggregate.stub.ts:6
- Duplicated block (9 lines × 2 locations) src/common/3.infra/events/amqplib/amqplib.adapter.ts:32
- Duplicated block (9 lines × 2 locations) src/common/3.infra/webapp/express/express.adapter.ts:52
- Duplicated block (9 lines × 2 locations) src/modules/identity/0.domain/value-objects/group.name.value-object.ts:7
- Duplicated block (9 lines × 2 locations) src/modules/identity/0.domain/value-objects/user.password.value-object.ts:7
- Duplicated block (10 lines × 2 locations) src/common/3.infra/webapp/express/express.adapter.ts:67
- Duplicated block (10 lines × 2 locations) src/common/4.main/container/persistence/make-mongodb.ts:12
- Duplicated block (10 lines × 2 locations) src/modules/communication/0.domain/value-objects/email.from.value-object.ts:8
- Mutable entity: GroupEntity src/modules/identity/0.domain/entities/group.entity.ts:15
- Mutable entity: UserEntity src/modules/identity/0.domain/entities/user.entity.ts:30
- Duplicated block (15 lines × 2 locations) src/common/3.infra/persistence/mongodb/client/mongodb.client.ts:44
- Duplicated block (15 lines × 2 locations) src/common/3.infra/webapp/express/express.adapter.ts:30
- Boundary violation [package:third-party-deep-import] vitest.setup.ts:1
- Boundary violation [package:third-party-deep-import] vitest.setup.ts:2
- Dead file (~70 LoC) src/modules/identity/2.presentation/routes/sign-in/sign-in.path.ts
- Dead file (~70 LoC) src/modules/identity/2.presentation/routes/sign-up/sign-up.path.ts
- No authorization src/common/3.infra/webapp/express/express.adapter.ts:22
- REDACTED
- REDACTED
- End-of-life runtime: Node.js 18 .nvmrc:1
- Coverage collected but not gated
- Schema created by TypeORM synchronize: true outside the migrations src/common/3.infra/persistence/postgres/data-sources/postgres-test.data-source.ts:20
- Duplication concentrated across 2 sibling directories (6 clone groups) src/modules/communication/1.application/use-cases/send-email-confirmation.use-case.ts:12
- Duplicated block with local edits (63 matched lines × 2 locations) src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-user.repository.ts:17
- Duplicated block (32 lines × 2 locations) src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-group.repository.ts:10
- Duplicated block with local edits (30 matched lines × 2 locations) src/modules/identity/3.infra/persistence/mongodb/mappers/mongodb-user.mapper.ts:6
- Duplicated block (22 lines × 2 locations) src/common/3.infra/events/amqplib/amqplib.adapter.ts:85
- Duplicated block (20 lines × 4 locations) src/modules/identity/2.presentation/controllers/change-password.controller.ts:9
- Duplicated block (19 lines × 3 locations) src/modules/identity/1.application/use-cases/change-password.use-case.ts:87
- Duplicated block (14 lines × 2 locations) src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-group.repository.ts:57
- Duplicated block (13 lines × 5 locations) src/modules/identity/2.presentation/controllers/change-password.controller.ts:18
- Duplicated block with local edits (10 matched lines × 2 locations) src/common/0.domain/utils/either.ts:3
- Duplicated block (9 lines × 5 locations) src/common/2.presentation/middlewares/auth.middleware.ts:11
- Duplicated block (9 lines × 3 locations) src/modules/communication/0.domain/value-objects/email.from.value-object.ts:9
- Duplicated block (8 lines × 2 locations) src/common/3.infra/persistence/mongodb/base/mongodb.fixture.ts:7
- Duplicated block (8 lines × 3 locations) src/modules/communication/0.domain/value-objects/email.subject.value-object.ts:8
- Duplicated block (7 lines × 3 locations) src/common/0.domain/validators/date.validator.ts:4
- Duplicated block (7 lines × 2 locations) src/common/3.infra/persistence/mongodb/base/mongodb.fixture.ts:18
- Dependency Freshness
- Dead file (~85 LoC) src/modules/identity/2.presentation/routes/change-password/change-password.path.ts
- Dead file (~64 LoC) src/modules/identity/2.presentation/routes/group/create-group/create-group.path.ts
- Dead file (~60 LoC) src/modules/identity/2.presentation/routes/confirm-email/confirm-email.path.ts
- Dead file (~31 LoC) src/modules/identity/4.main/setup/webapp/identity.api-specification.ts
- Unused dependency 'git-commit-msg-linter'
Minor — 53 finding(s)
- Mock-dominated test: calls nodemailer.sendMail with correct params test/modules/communication/3.infra/communication/nodemailer/nodemailer.adapter.unit-test.ts:63
- Mock-dominated test: calls app.listen with correct params test/common/3.infra/webapp/express/express.adapter.unit-test.ts:68
- Mock-dominated test: calls app.<routeType> with correct params test/common/3.infra/webapp/express/express.adapter.unit-test.ts:100
- Mock-dominated test: calls ajv.validate with correct params test/common/3.infra/validation/ajv/ajv.adapter.unit-test.ts:55
- Mock-dominated test: calls connection.createChannel with correct params test/common/3.infra/events/amqplib/amqplib.adapter.unit-test.ts:79
- Mock-dominated test: calls channel.assertQueue with correct params test/common/3.infra/events/amqplib/amqplib.adapter.unit-test.ts:89
- Mock-dominated test: calls channel.bindQueue with correct params test/common/3.infra/events/amqplib/amqplib.adapter.unit-test.ts:106
- Mock-dominated test: calls channel.assertExchange with correct params test/common/3.infra/events/amqplib/amqplib.adapter.unit-test.ts:135
- Mock-dominated test: calls channel.sendToQueue with correct params test/common/3.infra/events/amqplib/amqplib.adapter.unit-test.ts:161
- Mock-dominated test: calls channel.publish with correct params test/common/3.infra/events/amqplib/amqplib.adapter.unit-test.ts:204
- Mock-dominated test: calls channel.consume with correct params test/common/3.infra/events/amqplib/amqplib.adapter.unit-test.ts:247
- Mock-dominated test: does not call channel.ack when handlerFn returns Left test/common/3.infra/events/amqplib/amqplib.adapter.unit-test.ts:440
- Orphaned file src/modules/identity/3.infra/persistence/postgres/repositories/postgres-user.repository.ts:1
- Orphaned file src/common/3.infra/events/amqplib/amqplib.adapter.ts:1
- Orphaned file src/common/3.infra/webapp/express/express.adapter.ts:1
- Orphaned file src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-user.repository.ts:1
- Orphaned file src/modules/identity/1.application/use-cases/sign-in.use-case.ts:1
- Orphaned file src/modules/identity/1.application/use-cases/change-password.use-case.ts:1
- Orphaned file src/modules/identity/1.application/use-cases/sign-up.use-case.ts:1
- Orphaned file src/modules/identity/0.domain/entities/user.entity.ts:1
- Orphaned file src/common/2.presentation/middlewares/auth.middleware.ts:1
- Orphaned file src/modules/identity/3.infra/persistence/mongodb/repositories/mongodb-group.repository.ts:1
- Orphaned file src/modules/identity/1.application/use-cases/confirm-email.use-case.ts:1
- Orphaned file src/modules/identity/2.presentation/routes/change-password/change-password.path.ts:1
- Console output used as the logging channel src/common/2.presentation/factories/server-error.factory.ts:9
- Console output used as the logging channel src/common/0.domain/utils/var.ts:3
- Console output used as the logging channel src/common/0.domain/utils/var.ts:9
- Console output used as the logging channel src/common/0.domain/utils/var.ts:21
- Console output used as the logging channel src/common/0.domain/utils/var.ts:33
- Console output used as the logging channel src/common/0.domain/utils/var.ts:45
- Console output used as the logging channel src/common/0.domain/utils/var.ts:53
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- No ADRs
- No SAST
- No dependency-update automation package.json:42
- No rollback/health safety
- Unused export 'ClientErrorStatus' src/common/2.presentation/factories/client-error.factory.ts:4
- Unused export 'ServerErrorStatus' src/common/2.presentation/factories/server-error.factory.ts:3
- Unused export 'MongodbGroupModel' src/modules/identity/3.infra/persistence/mongodb/entities/mongodb-group.entity.ts:22
- No app-layer HTTPS enforcement detected src/common/3.infra/webapp/express/express.adapter.ts:34
- Duplicated predicate src/common/3.infra/persistence/mongodb/base/mongodb.fixture.ts:34
- Strict null checking is not enabled everywhere the repository type-checks
Appendix B — Reproduction & audit trail
| Dimension | Tool | Version | Command | Findings | Raw output |
|---|---|---|---|---|---|
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aca4d255c72347849557c04b0ad1752a/history.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-aca4d255c72347849557c04b0ad1752a/tree.json --exit-code 0 --source . | 2 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 3 | 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 | 65 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy config --format json --quiet . | 4 | 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 1 file(s) — `src/common/2.presentation/documentation/api-documenter.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 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 |