Executive summary
thisisagile/easy falls short of our standard for production because we found no logging, tracing or health checks in the code, and it has uses of packages that aren't listed. It scores 55 out of 100 and is rated Adequate, and 24 of its 36 critical findings are security problems.
Production Readiness, at 40, is the weakest lens and counts most in the score. The best first steps are adopting a logging library and tidying the declared packages, each worth about 7 points. Raising Production Readiness to 70 would lift the score to about 66.
Sixteen pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four known security holes in the packages the code depends on can be used by attackers, and two secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. Setting a waiting period for automatic updates would fix the automatic dependency update that takes a new release at once, and fixing the weaknesses the scanner points to would deal with the security weakness in the code. The six uses of packages that aren't listed need adding to the project's list of dependencies.
The product code is 10,096 lines, about €33,000 to rebuild. The check for the health of its packages couldn't finish, so that result is missing, not a clean pass.
If Production Readiness rose from 40 to 70, the lowest score rated Strong, the score would rise from 55 to about 66.
New since the last survey: 25 findings
- God Classes · FunctionTooLong: Locale.registry packages/easy-domain/src/enums/Locale.ts
- God Classes · FunctionTooLong: Country.registry packages/easy-domain/src/enums/Country.ts
- God Classes · FunctionTooLong: Currency.registry packages/easy-domain/src/enums/Currency.ts
- God Classes · FileTooLong: enums/Country.ts packages/easy-domain/src/enums/Country.ts
- Dependency Hygiene · Deprecated: @types/uuid packages/easy-express/package.json
- Dependency Hygiene · Deprecated: @types/uuid packages/easy/package.json
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Code Duplication · Duplication concentrated across 6 sibling directories (14 clone groups) packages/easy-playwright/src/PlaywrightTester.ts
- Code Duplication · Duplicated block (34 lines × 2 locations) packages/easy-playwright/src/PlaywrightTester.ts
- Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) packages/easy/src/http/HttpVerb.ts
- Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) packages/easy/src/data/Database.ts
- Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) packages/easy-domain/src/enums/UnitOfWeight.ts
- Cyclomatic Complexity · Complex function render (cyclomatic 13, cognitive 12) REDACTED
- Large Files · packages/easy-domain/src/enums/Locale.ts: 1153 lines of code packages/easy-domain/src/enums/Locale.ts
- Large Files · packages/easy-domain/src/enums/Country.ts: 529 lines of code packages/easy-domain/src/enums/Country.ts
- Large Files · REDACTED: 502 lines of code REDACTED
- Circular Imports · Import cycle (2 files) packages/easy/src/types/List.ts
- Circular Imports · Import cycle (2 files) packages/easy/src/types/Template.ts
- Circular Imports · Import cycle (2 files) packages/easy/src/validation/Validate.ts
- Domain ↔ infrastructure boundary · Domain depends on infrastructure: jest.config packages/easy-domain/jest.config.cjs
Fixed since the last survey: 77 findings
- God Classes · ClassTooLong: Locale packages/easy-domain/src/enums/Locale.ts
- Code Coverage · Low coverage: packages/easy-test/src/matchers/toBeRoutedTo.ts packages/easy-test/src/matchers/toBeRoutedTo.ts
- Code Coverage · Low coverage: packages/easy/src/data/InMemoryGateway.ts packages/easy/src/data/InMemoryGateway.ts
- Code Coverage · Low coverage: packages/easy/src/domain/Repo.ts packages/easy/src/domain/Repo.ts
- Code Coverage · Low coverage: packages/easy/src/domain/Struct.ts packages/easy/src/domain/Struct.ts
- Code Coverage · Low coverage: packages/easy/src/domain/Typo.ts packages/easy/src/domain/Typo.ts
- Code Coverage · Low coverage: packages/easy/src/http/RequestOptions.ts packages/easy/src/http/RequestOptions.ts
- Code Coverage · Low coverage: packages/easy/src/process/Manage.ts packages/easy/src/process/Manage.ts
- Code Coverage · Low coverage: packages/easy/src/process/Search.ts packages/easy/src/process/Search.ts
- Code Coverage · Low coverage: packages/easy/src/resources/Req.ts packages/easy/src/resources/Req.ts
- Code Coverage · Low coverage: packages/easy/src/services/Api.ts packages/easy/src/services/Api.ts
- Code Coverage · Low coverage: packages/easy/src/services/ApiGateway.ts packages/easy/src/services/ApiGateway.ts
- Code Coverage · Low coverage: packages/easy/src/services/FetchProvider.ts packages/easy/src/services/FetchProvider.ts
- Code Coverage · Low coverage: packages/easy/src/services/MappedRouteGateway.ts packages/easy/src/services/MappedRouteGateway.ts
- Code Coverage · Low coverage: packages/easy/src/services/RouteGateway.ts packages/easy/src/services/RouteGateway.ts
- Code Coverage · Low coverage: packages/easy/src/services/ViewRouteGateway.ts packages/easy/src/services/ViewRouteGateway.ts
- Code Coverage · Low coverage: packages/easy/src/sql/Column.ts packages/easy/src/sql/Column.ts
- Code Coverage · Low coverage: packages/easy/src/sql/Insert.ts packages/easy/src/sql/Insert.ts
- Code Coverage · Low coverage: packages/easy/src/sql/Join.ts packages/easy/src/sql/Join.ts
- Code Coverage · Low coverage: packages/easy/src/sql/Select.ts packages/easy/src/sql/Select.ts
- Code Coverage · Low coverage: packages/easy/src/sql/SqlQuery.ts packages/easy/src/sql/SqlQuery.ts
- Code Coverage · Low coverage: packages/easy/src/sql/TableGateway.ts packages/easy/src/sql/TableGateway.ts
- Code Coverage · Low coverage: packages/easy/src/sql/Update.ts packages/easy/src/sql/Update.ts
- Code Coverage · Low coverage: packages/easy/src/types/Array.ts packages/easy/src/types/Array.ts
- Code Coverage · Low coverage: packages/easy/src/types/Case.ts packages/easy/src/types/Case.ts
- Code Coverage · Low coverage: packages/easy/src/types/IsEqual.ts packages/easy/src/types/IsEqual.ts
- Code Coverage · Low coverage: packages/easy/src/types/List.ts packages/easy/src/types/List.ts
- Code Coverage · Low coverage: packages/easy/src/types/PageList.ts packages/easy/src/types/PageList.ts
- Code Coverage · Low coverage: packages/easy/src/types/Parser.ts packages/easy/src/types/Parser.ts
- Code Coverage · Low coverage: packages/easy/src/types/Template.ts packages/easy/src/types/Template.ts
- Code Coverage · Low coverage: packages/easy/src/types/Uri.ts packages/easy/src/types/Uri.ts
- Code Coverage · Low coverage: packages/easy/src/utils/Log.ts packages/easy/src/utils/Log.ts
- Code Coverage · Low coverage: packages/easy/src/utils/Traverse.ts packages/easy/src/utils/Traverse.ts
- Code Coverage · Low coverage: packages/easy/src/utils/View.ts packages/easy/src/utils/View.ts
- Code Coverage · Low coverage: packages/easy/src/validation/Validate.ts packages/easy/src/validation/Validate.ts
- Code Coverage · Low coverage: packages/easy/src/validation/When.ts packages/easy/src/validation/When.ts
- Dependency Hygiene · Deprecated: eslint package.json
- Dependency Hygiene · Deprecated: uuid packages/easy/package.json
- Boundary Type-Coupling · Cross-context type Optional (easy → easy-domain) packages/easy-domain/src/enums/Country.ts
- Boundary Type-Coupling · Cross-context type Optional (easy → easy-domain) packages/easy-domain/src/enums/Locale.ts
- Boundary Type-Coupling · Cross-context type Optional (easy → easy-domain) packages/easy-domain/src/structs/Money.ts
- Boundary Type-Coupling · Cross-context type SortDirection (easy → easy-mongo) packages/easy-mongo/src/Collection.ts
- Boundary Type-Coupling · Cross-context type Optional (easy → easy-mongo) packages/easy-mongo/src/Stages.ts
- Boundary Type-Coupling · Cross-context type Optional (easy → easy-mongo) packages/easy-mongo/src/Stages.ts
- Boundary Type-Coupling · Cross-context type Optional (easy → easy-mongo) packages/easy-mongo/src/MongoGateway.ts
- Boundary Type-Coupling · Cross-context type Optional (easy → easy-mongo) packages/easy-mongo/src/MongoGateway.ts
- Boundary Type-Coupling · Cross-context type Optional (easy → easy-react) packages/easy-react/src/utils/toClasses.ts
- Boundary Type-Coupling · Cross-context type Optional (easy → easy-react) packages/easy-react/src/utils/Hooks.ts
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Knowledge Freshness · Orphaned knowledge packages/easy-domain/src/enums/Locale.ts
- Code Duplication · Duplication concentrated across 5 sibling directories (10 clone groups) packages/easy-playwright/src/PlaywrightTester.ts
- Code Duplication · Duplicated block with local edits (52 matched lines × 2 locations) packages/easy-playwright/src/PlaywrightTester.ts
- Code Duplication · Duplicated block (5 lines × 2 locations) packages/easy/src/types/Case.ts
- Cyclomatic Complexity · Complex function render (cyclomatic 15, cognitive 15) REDACTED
- Large Files · packages/easy-domain/src/enums/Locale.ts: 580 lines of code packages/easy-domain/src/enums/Locale.ts
- Large Files · REDACTED: 453 lines of code REDACTED
- Dependency Hygiene · Unlisted import 'detect-indent' scripts/release-it-workspace-fix.mjs
- Dependency Hygiene · Unlisted import 'detect-newline' scripts/release-it-workspace-fix.mjs
- Dependency Hygiene · Unlisted import 'walk-sync' scripts/release-it-workspace-fix.mjs
- Circular Imports · Import cycle (3 files) packages/easy/src/types/Case.ts
- Documentation (README) · README may be stale
- Domain vs controller coverage · Low domain coverage
Rebuild cost: about €33,000 · Estimate
| Cost to rebuild | €11,000 to €55,000, for 181 to 574 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 55. 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: 10,096 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture — module dependency graph
Architecture: which parts of the code depend on which
| uses → | 1 easy-domain.src.enums.Country | 2 easy-domain.src.values | 3 easy.src.types.Array | 4 easy.src.types.Constructor | 5 easy.src.types.Get | 6 easy.src.types.Id | 7 easy.src.types.Json | 8 easy.src.types.Types | 9 easy.src.types.Validatable | 10 easy-domain.src.structs | 11 easy.src.domain.Struct | 12 easy.src.http | 13 easy.src.sql.Table | 14 easy.src.types.PageList | 15 easy.src.types.ToText | 16 easy.src.types.Value | 17 easy-mongo.src.MongoProvider | 18 easy.src.domain.DateTime | 19 easy.src.types | 20 easy-mongo.src.Collection | 21 easy.src.http.RequestOptions | 22 easy.src.resources.Req | 23 easy.src.sql.Column | 24 easy.src.types.List | 25 easy.src.types.Try | 26 easy.src.utils | 27 easy-service.src.resources.Service | 28 easy.src.services.Api | 29 easy.src.sql.SqlQuery | 30 easy.src.types.Gateway | 31 easy.src.types.Repository | 32 easy-express.src.express | 33 easy-mongo.src.MongoGateway | 34 easy.src.data.InMemoryGateway | 35 easy.src.domain.Repo | 36 easy.src.process.Search | 37 easy.src.services.RouteGateway | 38 easy.src.domain.Typo | 39 easy.src.services.MappedRouteGateway | 40 easy.src.services.ViewRouteGateway |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 easy-domain.src.enums.Country | ||||||||||||||||||||||||||||||||||||||||
| 2 easy-domain.src.values | ||||||||||||||||||||||||||||||||||||||||
| 3 easy.src.types.Array | ||||||||||||||||||||||||||||||||||||||||
| 4 easy.src.types.Constructor | ||||||||||||||||||||||||||||||||||||||||
| 5 easy.src.types.Get | ||||||||||||||||||||||||||||||||||||||||
| 6 easy.src.types.Id | ||||||||||||||||||||||||||||||||||||||||
| 7 easy.src.types.Json | ||||||||||||||||||||||||||||||||||||||||
| 8 easy.src.types.Types | ||||||||||||||||||||||||||||||||||||||||
| 9 easy.src.types.Validatable | ||||||||||||||||||||||||||||||||||||||||
| 10 easy-domain.src.structs | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 11 easy.src.domain.Struct | 1 | |||||||||||||||||||||||||||||||||||||||
| 12 easy.src.http | 3 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 13 easy.src.sql.Table | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 14 easy.src.types.PageList | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 15 easy.src.types.ToText | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 16 easy.src.types.Value | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 easy-mongo.src.MongoProvider | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 18 easy.src.domain.DateTime | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 19 easy.src.types | 2 | 2 | 6 | 2 | 1 | 2 | 1 | 1 | 3 | |||||||||||||||||||||||||||||||
| 20 easy-mongo.src.Collection | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 21 easy.src.http.RequestOptions | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 22 easy.src.resources.Req | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 23 easy.src.sql.Column | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 24 easy.src.types.List | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 25 easy.src.types.Try | 3 | 3 | 3 | 1 | 6 | |||||||||||||||||||||||||||||||||||
| 26 easy.src.utils | 1 | 2 | 1 | 3 | 1 | |||||||||||||||||||||||||||||||||||
| 27 easy-service.src.resources.Service | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 easy.src.services.Api | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 easy.src.sql.SqlQuery | 1 | |||||||||||||||||||||||||||||||||||||||
| 30 easy.src.types.Gateway | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||
| 31 easy.src.types.Repository | 2 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 easy-express.src.express | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 easy-mongo.src.MongoGateway | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 34 easy.src.data.InMemoryGateway | 1 | 1 | 1 | 1 | 2 | |||||||||||||||||||||||||||||||||||
| 35 easy.src.domain.Repo | 2 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 36 easy.src.process.Search | 2 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 37 easy.src.services.RouteGateway | 1 | 1 | 1 | 1 | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||
| 38 easy.src.domain.Typo | 4 | 2 | 2 | 2 | 1 | 2 | 1 | |||||||||||||||||||||||||||||||||
| 39 easy.src.services.MappedRouteGateway | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||
| 40 easy.src.services.ViewRouteGateway | 1 | 1 | 1 | 1 | 1 | 1 |
10→1 easy-domain.src.structs uses easy-domain.src.enums.Country✕
- Connections
- 2 pairs of types, where a type in easy-domain.src.structs uses a type in easy-domain.src.enums.Country.
- The types involved
packages.easy-domain.src.structs.Money→packages.easy-domain.src.enums.Country.Enumpackages.easy-domain.src.structs.Weight→packages.easy-domain.src.enums.Country.Enum
- Direction
- easy-domain.src.structs uses easy-domain.src.enums.Country, so a change to easy-domain.src.enums.Country can break easy-domain.src.structs, while a change to easy-domain.src.structs can't break easy-domain.src.enums.Country.
- Position
- Below the diagonal: easy-domain.src.structs uses a module listed above it, which is the healthy direction.
10→8 easy-domain.src.structs uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy-domain.src.structs uses a type in easy.src.types.Types.
- The types involved
packages.easy-domain.src.structs.Money→packages.easy.src.types.Types.Optional
- Direction
- easy-domain.src.structs uses easy.src.types.Types, so a change to easy.src.types.Types can break easy-domain.src.structs, while a change to easy-domain.src.structs can't break easy.src.types.Types.
- Position
- Below the diagonal: easy-domain.src.structs uses a module listed above it, which is the healthy direction.
11→9 easy.src.domain.Struct uses easy.src.types.Validatable✕
- Connections
- 1 pair of types, where a type in easy.src.domain.Struct uses a type in easy.src.types.Validatable.
- The types involved
packages.easy.src.domain.Struct.Struct→packages.easy.src.types.Validatable.Validatable
- Direction
- easy.src.domain.Struct uses easy.src.types.Validatable, so a change to easy.src.types.Validatable can break easy.src.domain.Struct, while a change to easy.src.domain.Struct can't break easy.src.types.Validatable.
- Position
- Below the diagonal: easy.src.domain.Struct uses a module listed above it, which is the healthy direction.
12→1 easy.src.http uses easy-domain.src.enums.Country✕
- Connections
- 3 pairs of types, where a type in easy.src.http uses a type in easy-domain.src.enums.Country.
- The types involved
packages.easy.src.http.ContentType→packages.easy-domain.src.enums.Country.Enumpackages.easy.src.http.HttpStatus→packages.easy-domain.src.enums.Country.Enumpackages.easy.src.http.HttpVerb→packages.easy-domain.src.enums.Country.Enum
- Direction
- easy.src.http uses easy-domain.src.enums.Country, so a change to easy-domain.src.enums.Country can break easy.src.http, while a change to easy.src.http can't break easy-domain.src.enums.Country.
- Position
- Below the diagonal: easy.src.http uses a module listed above it, which is the healthy direction.
12→5 easy.src.http uses easy.src.types.Get✕
- Connections
- 1 pair of types, where a type in easy.src.http uses a type in easy.src.types.Get.
- The types involved
packages.easy.src.http.ContentType→packages.easy.src.types.Get.Get
- Direction
- easy.src.http uses easy.src.types.Get, so a change to easy.src.types.Get can break easy.src.http, while a change to easy.src.http can't break easy.src.types.Get.
- Position
- Below the diagonal: easy.src.http uses a module listed above it, which is the healthy direction.
12→6 easy.src.http uses easy.src.types.Id✕
- Connections
- 1 pair of types, where a type in easy.src.http uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.http.HttpStatus→packages.easy.src.types.Id.Code
- Direction
- easy.src.http uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.http, while a change to easy.src.http can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.http uses a module listed above it, which is the healthy direction.
12→8 easy.src.http uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.http uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.http.RequestOptions→packages.easy.src.types.Types.Optional
- Direction
- easy.src.http uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.http, while a change to easy.src.http can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.http uses a module listed above it, which is the healthy direction.
13→1 easy.src.sql.Table uses easy-domain.src.enums.Country✕
- Connections
- 1 pair of types, where a type in easy.src.sql.Table uses a type in easy-domain.src.enums.Country.
- The types involved
packages.easy.src.sql.Table.Table→packages.easy-domain.src.enums.Country.Enum
- Direction
- easy.src.sql.Table uses easy-domain.src.enums.Country, so a change to easy-domain.src.enums.Country can break easy.src.sql.Table, while a change to easy.src.sql.Table can't break easy-domain.src.enums.Country.
- Position
- Below the diagonal: easy.src.sql.Table uses a module listed above it, which is the healthy direction.
13→23 easy.src.sql.Table uses easy.src.sql.Column part of a loop✕
- Connections
- 1 pair of types, where a type in easy.src.sql.Table uses a type in easy.src.sql.Column.
- The types involved
packages.easy.src.sql.Table.Table→packages.easy.src.sql.Column.Column
- Direction
- easy.src.sql.Table uses easy.src.sql.Column, so a change to easy.src.sql.Column can break easy.src.sql.Table, while a change to easy.src.sql.Table can't break easy.src.sql.Column.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→5 easy.src.types.PageList uses easy.src.types.Get✕
- Connections
- 1 pair of types, where a type in easy.src.types.PageList uses a type in easy.src.types.Get.
- The types involved
packages.easy.src.types.PageList.PageList→packages.easy.src.types.Get.GetProperty
- Direction
- easy.src.types.PageList uses easy.src.types.Get, so a change to easy.src.types.Get can break easy.src.types.PageList, while a change to easy.src.types.PageList can't break easy.src.types.Get.
- Position
- Below the diagonal: easy.src.types.PageList uses a module listed above it, which is the healthy direction.
14→6 easy.src.types.PageList uses easy.src.types.Id✕
- Connections
- 1 pair of types, where a type in easy.src.types.PageList uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.types.PageList.PageList→packages.easy.src.types.Id.Id
- Direction
- easy.src.types.PageList uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.types.PageList, while a change to easy.src.types.PageList can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.types.PageList uses a module listed above it, which is the healthy direction.
14→8 easy.src.types.PageList uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.types.PageList uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.types.PageList.PageList→packages.easy.src.types.Types.Optional
- Direction
- easy.src.types.PageList uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.types.PageList, while a change to easy.src.types.PageList can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.types.PageList uses a module listed above it, which is the healthy direction.
14→24 easy.src.types.PageList uses easy.src.types.List part of a loop✕
- Connections
- 1 pair of types, where a type in easy.src.types.PageList uses a type in easy.src.types.List.
- The types involved
packages.easy.src.types.PageList.PageList→packages.easy.src.types.List.List
- Direction
- easy.src.types.PageList uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.types.PageList, while a change to easy.src.types.PageList can't break easy.src.types.List.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→5 easy.src.types.ToText uses easy.src.types.Get✕
- Connections
- 1 pair of types, where a type in easy.src.types.ToText uses a type in easy.src.types.Get.
- The types involved
packages.easy.src.types.ToText.ToText→packages.easy.src.types.Get.Get
- Direction
- easy.src.types.ToText uses easy.src.types.Get, so a change to easy.src.types.Get can break easy.src.types.ToText, while a change to easy.src.types.ToText can't break easy.src.types.Get.
- Position
- Below the diagonal: easy.src.types.ToText uses a module listed above it, which is the healthy direction.
15→7 easy.src.types.ToText uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.types.ToText uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.types.ToText.ToText→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.types.ToText uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.types.ToText, while a change to easy.src.types.ToText can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.types.ToText uses a module listed above it, which is the healthy direction.
15→8 easy.src.types.ToText uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.types.ToText uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.types.ToText.ToText→packages.easy.src.types.Types.Optional
- Direction
- easy.src.types.ToText uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.types.ToText, while a change to easy.src.types.ToText can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.types.ToText uses a module listed above it, which is the healthy direction.
15→19 easy.src.types.ToText uses easy.src.types part of a loop✕
- Connections
- 1 pair of types, where a type in easy.src.types.ToText uses a type in easy.src.types.
- The types involved
packages.easy.src.types.ToText.ToText→packages.easy.src.types.Text
- Direction
- easy.src.types.ToText uses easy.src.types, so a change to easy.src.types can break easy.src.types.ToText, while a change to easy.src.types.ToText can't break easy.src.types.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→24 easy.src.types.ToText uses easy.src.types.List part of a loop✕
- Connections
- 1 pair of types, where a type in easy.src.types.ToText uses a type in easy.src.types.List.
- The types involved
packages.easy.src.types.ToText.ToText→packages.easy.src.types.List.List
- Direction
- easy.src.types.ToText uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.types.ToText, while a change to easy.src.types.ToText can't break easy.src.types.List.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→7 easy.src.types.Value uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.types.Value uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.types.Value.Value→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.types.Value uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.types.Value, while a change to easy.src.types.Value can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.types.Value uses a module listed above it, which is the healthy direction.
16→9 easy.src.types.Value uses easy.src.types.Validatable✕
- Connections
- 1 pair of types, where a type in easy.src.types.Value uses a type in easy.src.types.Validatable.
- The types involved
packages.easy.src.types.Value.Value→packages.easy.src.types.Validatable.Validatable
- Direction
- easy.src.types.Value uses easy.src.types.Validatable, so a change to easy.src.types.Validatable can break easy.src.types.Value, while a change to easy.src.types.Value can't break easy.src.types.Validatable.
- Position
- Below the diagonal: easy.src.types.Value uses a module listed above it, which is the healthy direction.
17→3 easy-mongo.src.MongoProvider uses easy.src.types.Array✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoProvider uses a type in easy.src.types.Array.
- The types involved
packages.easy-mongo.src.MongoProvider.MongoProvider→packages.easy.src.types.Array.OneOrMore
- Direction
- easy-mongo.src.MongoProvider uses easy.src.types.Array, so a change to easy.src.types.Array can break easy-mongo.src.MongoProvider, while a change to easy-mongo.src.MongoProvider can't break easy.src.types.Array.
- Position
- Below the diagonal: easy-mongo.src.MongoProvider uses a module listed above it, which is the healthy direction.
17→6 easy-mongo.src.MongoProvider uses easy.src.types.Id✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoProvider uses a type in easy.src.types.Id.
- The types involved
packages.easy-mongo.src.MongoProvider.MongoProvider→packages.easy.src.types.Id.Id
- Direction
- easy-mongo.src.MongoProvider uses easy.src.types.Id, so a change to easy.src.types.Id can break easy-mongo.src.MongoProvider, while a change to easy-mongo.src.MongoProvider can't break easy.src.types.Id.
- Position
- Below the diagonal: easy-mongo.src.MongoProvider uses a module listed above it, which is the healthy direction.
17→7 easy-mongo.src.MongoProvider uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoProvider uses a type in easy.src.types.Json.
- The types involved
packages.easy-mongo.src.MongoProvider.MongoProvider→packages.easy.src.types.Json.JsonValue
- Direction
- easy-mongo.src.MongoProvider uses easy.src.types.Json, so a change to easy.src.types.Json can break easy-mongo.src.MongoProvider, while a change to easy-mongo.src.MongoProvider can't break easy.src.types.Json.
- Position
- Below the diagonal: easy-mongo.src.MongoProvider uses a module listed above it, which is the healthy direction.
17→14 easy-mongo.src.MongoProvider uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoProvider uses a type in easy.src.types.PageList.
- The types involved
packages.easy-mongo.src.MongoProvider.MongoProvider→packages.easy.src.types.PageList.PageList
- Direction
- easy-mongo.src.MongoProvider uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy-mongo.src.MongoProvider, while a change to easy-mongo.src.MongoProvider can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy-mongo.src.MongoProvider uses a module listed above it, which is the healthy direction.
17→20 easy-mongo.src.MongoProvider uses easy-mongo.src.Collection part of a loop✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoProvider uses a type in easy-mongo.src.Collection.
- The types involved
packages.easy-mongo.src.MongoProvider.MongoProvider→packages.easy-mongo.src.Collection.Collection
- Direction
- easy-mongo.src.MongoProvider uses easy-mongo.src.Collection, so a change to easy-mongo.src.Collection can break easy-mongo.src.MongoProvider, while a change to easy-mongo.src.MongoProvider can't break easy-mongo.src.Collection.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
18→7 easy.src.domain.DateTime uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.domain.DateTime uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.domain.DateTime.DateTime→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.domain.DateTime uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.domain.DateTime, while a change to easy.src.domain.DateTime can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.domain.DateTime uses a module listed above it, which is the healthy direction.
18→8 easy.src.domain.DateTime uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.domain.DateTime uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.domain.DateTime.DateTime→packages.easy.src.types.Types.Optional
- Direction
- easy.src.domain.DateTime uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.domain.DateTime, while a change to easy.src.domain.DateTime can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.domain.DateTime uses a module listed above it, which is the healthy direction.
18→16 easy.src.domain.DateTime uses easy.src.types.Value✕
- Connections
- 1 pair of types, where a type in easy.src.domain.DateTime uses a type in easy.src.types.Value.
- The types involved
packages.easy.src.domain.DateTime.DateTime→packages.easy.src.types.Value.Value
- Direction
- easy.src.domain.DateTime uses easy.src.types.Value, so a change to easy.src.types.Value can break easy.src.domain.DateTime, while a change to easy.src.domain.DateTime can't break easy.src.types.Value.
- Position
- Below the diagonal: easy.src.domain.DateTime uses a module listed above it, which is the healthy direction.
19→1 easy.src.types uses easy-domain.src.enums.Country✕
- Connections
- 2 pairs of types, where a type in easy.src.types uses a type in easy-domain.src.enums.Country.
- The types involved
packages.easy.src.types.Environment→packages.easy-domain.src.enums.Country.Enumpackages.easy.src.types.Exception→packages.easy-domain.src.enums.Country.Enum
- Direction
- easy.src.types uses easy-domain.src.enums.Country, so a change to easy-domain.src.enums.Country can break easy.src.types, while a change to easy.src.types can't break easy-domain.src.enums.Country.
- Position
- Below the diagonal: easy.src.types uses a module listed above it, which is the healthy direction.
19→4 easy.src.types uses easy.src.types.Constructor✕
- Connections
- 2 pairs of types, where a type in easy.src.types uses a type in easy.src.types.Constructor.
- The types involved
packages.easy.src.types.Constructor→packages.easy.src.types.Constructor.Constructpackages.easy.src.types.PageList→packages.easy.src.types.Constructor.Construct
- Direction
- easy.src.types uses easy.src.types.Constructor, so a change to easy.src.types.Constructor can break easy.src.types, while a change to easy.src.types can't break easy.src.types.Constructor.
- Position
- Below the diagonal: easy.src.types uses a module listed above it, which is the healthy direction.
19→5 easy.src.types uses easy.src.types.Get✕
- Connections
- 6 pairs of types, where a type in easy.src.types uses a type in easy.src.types.Get.
- The types involved
packages.easy.src.types.Get→packages.easy.src.types.Get.Getpackages.easy.src.types.Get→packages.easy.src.types.Get.GetPropertypackages.easy.src.types.Json→packages.easy.src.types.Get.Getpackages.easy.src.types.Number→packages.easy.src.types.Get.Getpackages.easy.src.types.Text→packages.easy.src.types.Get.Getpackages.easy.src.types.Try→packages.easy.src.types.Get.Get
- Direction
- easy.src.types uses easy.src.types.Get, so a change to easy.src.types.Get can break easy.src.types, while a change to easy.src.types can't break easy.src.types.Get.
- Position
- Below the diagonal: easy.src.types uses a module listed above it, which is the healthy direction.
19→6 easy.src.types uses easy.src.types.Id✕
- Connections
- 2 pairs of types, where a type in easy.src.types uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.types.Exception→packages.easy.src.types.Id.Idpackages.easy.src.types.Id→packages.easy.src.types.Id.Id
- Direction
- easy.src.types uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.types, while a change to easy.src.types can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.types uses a module listed above it, which is the healthy direction.
19→7 easy.src.types uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.types uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.types.Json→packages.easy.src.types.Json.Any
- Direction
- easy.src.types uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.types, while a change to easy.src.types can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.types uses a module listed above it, which is the healthy direction.
19→8 easy.src.types uses easy.src.types.Types✕
- Connections
- 2 pairs of types, where a type in easy.src.types uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.types.Constructor→packages.easy.src.types.Types.Optionalpackages.easy.src.types.ErrorOrigin→packages.easy.src.types.Types.Optional
- Direction
- easy.src.types uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.types, while a change to easy.src.types can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.types uses a module listed above it, which is the healthy direction.
19→14 easy.src.types uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy.src.types uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.types.PageList→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.types uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.types, while a change to easy.src.types can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.types uses a module listed above it, which is the healthy direction.
19→15 easy.src.types uses easy.src.types.ToText✕
- Connections
- 1 pair of types, where a type in easy.src.types uses a type in easy.src.types.ToText.
- The types involved
packages.easy.src.types.ToText→packages.easy.src.types.ToText.ToText
- Direction
- easy.src.types uses easy.src.types.ToText, so a change to easy.src.types.ToText can break easy.src.types, while a change to easy.src.types can't break easy.src.types.ToText.
- Position
- Below the diagonal: easy.src.types uses a module listed above it, which is the healthy direction.
19→24 easy.src.types uses easy.src.types.List part of a loop✕
- Connections
- 3 pairs of types, where a type in easy.src.types uses a type in easy.src.types.List.
- The types involved
packages.easy.src.types.List→packages.easy.src.types.List.Listpackages.easy.src.types.Object→packages.easy.src.types.List.Listpackages.easy.src.types.Registry→packages.easy.src.types.List.List
- Direction
- easy.src.types uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.types, while a change to easy.src.types can't break easy.src.types.List.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→1 easy-mongo.src.Collection uses easy-domain.src.enums.Country✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.Collection uses a type in easy-domain.src.enums.Country.
- The types involved
packages.easy-mongo.src.Collection.Collection→packages.easy-domain.src.enums.Country.Enum
- Direction
- easy-mongo.src.Collection uses easy-domain.src.enums.Country, so a change to easy-domain.src.enums.Country can break easy-mongo.src.Collection, while a change to easy-mongo.src.Collection can't break easy-domain.src.enums.Country.
- Position
- Below the diagonal: easy-mongo.src.Collection uses a module listed above it, which is the healthy direction.
20→5 easy-mongo.src.Collection uses easy.src.types.Get✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.Collection uses a type in easy.src.types.Get.
- The types involved
packages.easy-mongo.src.Collection.Collection→packages.easy.src.types.Get.Get
- Direction
- easy-mongo.src.Collection uses easy.src.types.Get, so a change to easy.src.types.Get can break easy-mongo.src.Collection, while a change to easy-mongo.src.Collection can't break easy.src.types.Get.
- Position
- Below the diagonal: easy-mongo.src.Collection uses a module listed above it, which is the healthy direction.
20→17 easy-mongo.src.Collection uses easy-mongo.src.MongoProvider✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.Collection uses a type in easy-mongo.src.MongoProvider.
- The types involved
packages.easy-mongo.src.Collection.Collection→packages.easy-mongo.src.MongoProvider.MongoProvider
- Direction
- easy-mongo.src.Collection uses easy-mongo.src.MongoProvider, so a change to easy-mongo.src.MongoProvider can break easy-mongo.src.Collection, while a change to easy-mongo.src.Collection can't break easy-mongo.src.MongoProvider.
- Position
- Below the diagonal: easy-mongo.src.Collection uses a module listed above it, which is the healthy direction.
20→19 easy-mongo.src.Collection uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.Collection uses a type in easy.src.types.
- The types involved
packages.easy-mongo.src.Collection.Collection→packages.easy.src.types.Text
- Direction
- easy-mongo.src.Collection uses easy.src.types, so a change to easy.src.types can break easy-mongo.src.Collection, while a change to easy-mongo.src.Collection can't break easy.src.types.
- Position
- Below the diagonal: easy-mongo.src.Collection uses a module listed above it, which is the healthy direction.
21→1 easy.src.http.RequestOptions uses easy-domain.src.enums.Country✕
- Connections
- 1 pair of types, where a type in easy.src.http.RequestOptions uses a type in easy-domain.src.enums.Country.
- The types involved
packages.easy.src.http.RequestOptions.RequestOptions→packages.easy-domain.src.enums.Country.Enum
- Direction
- easy.src.http.RequestOptions uses easy-domain.src.enums.Country, so a change to easy-domain.src.enums.Country can break easy.src.http.RequestOptions, while a change to easy.src.http.RequestOptions can't break easy-domain.src.enums.Country.
- Position
- Below the diagonal: easy.src.http.RequestOptions uses a module listed above it, which is the healthy direction.
21→19 easy.src.http.RequestOptions uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy.src.http.RequestOptions uses a type in easy.src.types.
- The types involved
packages.easy.src.http.RequestOptions.RequestOptions→packages.easy.src.types.Text
- Direction
- easy.src.http.RequestOptions uses easy.src.types, so a change to easy.src.types can break easy.src.http.RequestOptions, while a change to easy.src.http.RequestOptions can't break easy.src.types.
- Position
- Below the diagonal: easy.src.http.RequestOptions uses a module listed above it, which is the healthy direction.
22→3 easy.src.resources.Req uses easy.src.types.Array✕
- Connections
- 1 pair of types, where a type in easy.src.resources.Req uses a type in easy.src.types.Array.
- The types involved
packages.easy.src.resources.Req.Req→packages.easy.src.types.Array.OneOrMore
- Direction
- easy.src.resources.Req uses easy.src.types.Array, so a change to easy.src.types.Array can break easy.src.resources.Req, while a change to easy.src.resources.Req can't break easy.src.types.Array.
- Position
- Below the diagonal: easy.src.resources.Req uses a module listed above it, which is the healthy direction.
22→6 easy.src.resources.Req uses easy.src.types.Id✕
- Connections
- 1 pair of types, where a type in easy.src.resources.Req uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.resources.Req.Req→packages.easy.src.types.Id.Id
- Direction
- easy.src.resources.Req uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.resources.Req, while a change to easy.src.resources.Req can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.resources.Req uses a module listed above it, which is the healthy direction.
22→7 easy.src.resources.Req uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.resources.Req uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.resources.Req.Req→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.resources.Req uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.resources.Req, while a change to easy.src.resources.Req can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.resources.Req uses a module listed above it, which is the healthy direction.
22→8 easy.src.resources.Req uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.resources.Req uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.resources.Req.Req→packages.easy.src.types.Types.Optional
- Direction
- easy.src.resources.Req uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.resources.Req, while a change to easy.src.resources.Req can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.resources.Req uses a module listed above it, which is the healthy direction.
22→19 easy.src.resources.Req uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy.src.resources.Req uses a type in easy.src.types.
- The types involved
packages.easy.src.resources.Req.Req→packages.easy.src.types.Text
- Direction
- easy.src.resources.Req uses easy.src.types, so a change to easy.src.types can break easy.src.resources.Req, while a change to easy.src.resources.Req can't break easy.src.types.
- Position
- Below the diagonal: easy.src.resources.Req uses a module listed above it, which is the healthy direction.
23→7 easy.src.sql.Column uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.sql.Column uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.sql.Column.Column→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.sql.Column uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.sql.Column, while a change to easy.src.sql.Column can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.sql.Column uses a module listed above it, which is the healthy direction.
23→13 easy.src.sql.Column uses easy.src.sql.Table✕
- Connections
- 1 pair of types, where a type in easy.src.sql.Column uses a type in easy.src.sql.Table.
- The types involved
packages.easy.src.sql.Column.Column→packages.easy.src.sql.Table.Table
- Direction
- easy.src.sql.Column uses easy.src.sql.Table, so a change to easy.src.sql.Table can break easy.src.sql.Column, while a change to easy.src.sql.Column can't break easy.src.sql.Table.
- Position
- Below the diagonal: easy.src.sql.Column uses a module listed above it, which is the healthy direction.
23→19 easy.src.sql.Column uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy.src.sql.Column uses a type in easy.src.types.
- The types involved
packages.easy.src.sql.Column.Column→packages.easy.src.types.Text
- Direction
- easy.src.sql.Column uses easy.src.types, so a change to easy.src.types can break easy.src.sql.Column, while a change to easy.src.sql.Column can't break easy.src.types.
- Position
- Below the diagonal: easy.src.sql.Column uses a module listed above it, which is the healthy direction.
24→5 easy.src.types.List uses easy.src.types.Get✕
- Connections
- 2 pairs of types, where a type in easy.src.types.List uses a type in easy.src.types.Get.
- The types involved
packages.easy.src.types.List.List→packages.easy.src.types.Get.Getpackages.easy.src.types.List.List→packages.easy.src.types.Get.GetProperty
- Direction
- easy.src.types.List uses easy.src.types.Get, so a change to easy.src.types.Get can break easy.src.types.List, while a change to easy.src.types.List can't break easy.src.types.Get.
- Position
- Below the diagonal: easy.src.types.List uses a module listed above it, which is the healthy direction.
24→6 easy.src.types.List uses easy.src.types.Id✕
- Connections
- 1 pair of types, where a type in easy.src.types.List uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.types.List.List→packages.easy.src.types.Id.Id
- Direction
- easy.src.types.List uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.types.List, while a change to easy.src.types.List can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.types.List uses a module listed above it, which is the healthy direction.
24→8 easy.src.types.List uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.types.List uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.types.List.List→packages.easy.src.types.Types.Optional
- Direction
- easy.src.types.List uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.types.List, while a change to easy.src.types.List can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.types.List uses a module listed above it, which is the healthy direction.
24→19 easy.src.types.List uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy.src.types.List uses a type in easy.src.types.
- The types involved
packages.easy.src.types.List.List→packages.easy.src.types.Indexed
- Direction
- easy.src.types.List uses easy.src.types, so a change to easy.src.types can break easy.src.types.List, while a change to easy.src.types.List can't break easy.src.types.
- Position
- Below the diagonal: easy.src.types.List uses a module listed above it, which is the healthy direction.
25→4 easy.src.types.Try uses easy.src.types.Constructor✕
- Connections
- 3 pairs of types, where a type in easy.src.types.Try uses a type in easy.src.types.Constructor.
- The types involved
packages.easy.src.types.Try.Failure→packages.easy.src.types.Constructor.Constructpackages.easy.src.types.Try.Success→packages.easy.src.types.Constructor.Constructpackages.easy.src.types.Try.Try→packages.easy.src.types.Constructor.Construct
- Direction
- easy.src.types.Try uses easy.src.types.Constructor, so a change to easy.src.types.Constructor can break easy.src.types.Try, while a change to easy.src.types.Try can't break easy.src.types.Constructor.
- Position
- Below the diagonal: easy.src.types.Try uses a module listed above it, which is the healthy direction.
25→5 easy.src.types.Try uses easy.src.types.Get✕
- Connections
- 3 pairs of types, where a type in easy.src.types.Try uses a type in easy.src.types.Get.
- The types involved
packages.easy.src.types.Try.Failure→packages.easy.src.types.Get.Getpackages.easy.src.types.Try.Success→packages.easy.src.types.Get.Getpackages.easy.src.types.Try.Try→packages.easy.src.types.Get.Get
- Direction
- easy.src.types.Try uses easy.src.types.Get, so a change to easy.src.types.Get can break easy.src.types.Try, while a change to easy.src.types.Try can't break easy.src.types.Get.
- Position
- Below the diagonal: easy.src.types.Try uses a module listed above it, which is the healthy direction.
25→8 easy.src.types.Try uses easy.src.types.Types✕
- Connections
- 3 pairs of types, where a type in easy.src.types.Try uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.types.Try.Failure→packages.easy.src.types.Types.Optionalpackages.easy.src.types.Try.Success→packages.easy.src.types.Types.Optionalpackages.easy.src.types.Try.Try→packages.easy.src.types.Types.Optional
- Direction
- easy.src.types.Try uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.types.Try, while a change to easy.src.types.Try can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.types.Try uses a module listed above it, which is the healthy direction.
25→9 easy.src.types.Try uses easy.src.types.Validatable✕
- Connections
- 1 pair of types, where a type in easy.src.types.Try uses a type in easy.src.types.Validatable.
- The types involved
packages.easy.src.types.Try.Try→packages.easy.src.types.Validatable.Validatable
- Direction
- easy.src.types.Try uses easy.src.types.Validatable, so a change to easy.src.types.Validatable can break easy.src.types.Try, while a change to easy.src.types.Try can't break easy.src.types.Validatable.
- Position
- Below the diagonal: easy.src.types.Try uses a module listed above it, which is the healthy direction.
25→19 easy.src.types.Try uses easy.src.types✕
- Connections
- 6 pairs of types, where a type in easy.src.types.Try uses a type in easy.src.types.
- The types involved
packages.easy.src.types.Try.Failure→packages.easy.src.types.Constructorpackages.easy.src.types.Try.Failure→packages.easy.src.types.Funcpackages.easy.src.types.Try.Success→packages.easy.src.types.Constructorpackages.easy.src.types.Try.Success→packages.easy.src.types.Funcpackages.easy.src.types.Try.Try→packages.easy.src.types.Constructorpackages.easy.src.types.Try.Try→packages.easy.src.types.Func
- Direction
- easy.src.types.Try uses easy.src.types, so a change to easy.src.types can break easy.src.types.Try, while a change to easy.src.types.Try can't break easy.src.types.
- Position
- Below the diagonal: easy.src.types.Try uses a module listed above it, which is the healthy direction.
26→3 easy.src.utils uses easy.src.types.Array✕
- Connections
- 1 pair of types, where a type in easy.src.utils uses a type in easy.src.types.Array.
- The types involved
packages.easy.src.utils.If→packages.easy.src.types.Array.OneOrMore
- Direction
- easy.src.utils uses easy.src.types.Array, so a change to easy.src.types.Array can break easy.src.utils, while a change to easy.src.utils can't break easy.src.types.Array.
- Position
- Below the diagonal: easy.src.utils uses a module listed above it, which is the healthy direction.
26→4 easy.src.utils uses easy.src.types.Constructor✕
- Connections
- 2 pairs of types, where a type in easy.src.utils uses a type in easy.src.types.Constructor.
- The types involved
packages.easy.src.utils.If→packages.easy.src.types.Constructor.Constructpackages.easy.src.utils.IfType→packages.easy.src.types.Constructor.Construct
- Direction
- easy.src.utils uses easy.src.types.Constructor, so a change to easy.src.types.Constructor can break easy.src.utils, while a change to easy.src.utils can't break easy.src.types.Constructor.
- Position
- Below the diagonal: easy.src.utils uses a module listed above it, which is the healthy direction.
26→5 easy.src.utils uses easy.src.types.Get✕
- Connections
- 1 pair of types, where a type in easy.src.utils uses a type in easy.src.types.Get.
- The types involved
packages.easy.src.utils.If→packages.easy.src.types.Get.Get
- Direction
- easy.src.utils uses easy.src.types.Get, so a change to easy.src.types.Get can break easy.src.utils, while a change to easy.src.utils can't break easy.src.types.Get.
- Position
- Below the diagonal: easy.src.utils uses a module listed above it, which is the healthy direction.
26→8 easy.src.utils uses easy.src.types.Types✕
- Connections
- 3 pairs of types, where a type in easy.src.utils uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.utils.If→packages.easy.src.types.Types.Optionalpackages.easy.src.utils.IfType→packages.easy.src.types.Types.Optionalpackages.easy.src.utils.Log→packages.easy.src.types.Types.Optional
- Direction
- easy.src.utils uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.utils, while a change to easy.src.utils can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.utils uses a module listed above it, which is the healthy direction.
26→19 easy.src.utils uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy.src.utils uses a type in easy.src.types.
- The types involved
packages.easy.src.utils.View→packages.easy.src.types.Constructor
- Direction
- easy.src.utils uses easy.src.types, so a change to easy.src.types can break easy.src.utils, while a change to easy.src.utils can't break easy.src.types.
- Position
- Below the diagonal: easy.src.utils uses a module listed above it, which is the healthy direction.
27→1 easy-service.src.resources.Service uses easy-domain.src.enums.Country✕
- Connections
- 1 pair of types, where a type in easy-service.src.resources.Service uses a type in easy-domain.src.enums.Country.
- The types involved
packages.easy-service.src.resources.Service.Service→packages.easy-domain.src.enums.Country.Enum
- Direction
- easy-service.src.resources.Service uses easy-domain.src.enums.Country, so a change to easy-domain.src.enums.Country can break easy-service.src.resources.Service, while a change to easy-service.src.resources.Service can't break easy-domain.src.enums.Country.
- Position
- Below the diagonal: easy-service.src.resources.Service uses a module listed above it, which is the healthy direction.
27→24 easy-service.src.resources.Service uses easy.src.types.List✕
- Connections
- 1 pair of types, where a type in easy-service.src.resources.Service uses a type in easy.src.types.List.
- The types involved
packages.easy-service.src.resources.Service.Service→packages.easy.src.types.List.List
- Direction
- easy-service.src.resources.Service uses easy.src.types.List, so a change to easy.src.types.List can break easy-service.src.resources.Service, while a change to easy-service.src.resources.Service can't break easy.src.types.List.
- Position
- Below the diagonal: easy-service.src.resources.Service uses a module listed above it, which is the healthy direction.
28→1 easy.src.services.Api uses easy-domain.src.enums.Country✕
- Connections
- 1 pair of types, where a type in easy.src.services.Api uses a type in easy-domain.src.enums.Country.
- The types involved
packages.easy.src.services.Api.Api→packages.easy-domain.src.enums.Country.Enum
- Direction
- easy.src.services.Api uses easy-domain.src.enums.Country, so a change to easy-domain.src.enums.Country can break easy.src.services.Api, while a change to easy.src.services.Api can't break easy-domain.src.enums.Country.
- Position
- Below the diagonal: easy.src.services.Api uses a module listed above it, which is the healthy direction.
28→21 easy.src.services.Api uses easy.src.http.RequestOptions✕
- Connections
- 1 pair of types, where a type in easy.src.services.Api uses a type in easy.src.http.RequestOptions.
- The types involved
packages.easy.src.services.Api.Api→packages.easy.src.http.RequestOptions.RequestOptions
- Direction
- easy.src.services.Api uses easy.src.http.RequestOptions, so a change to easy.src.http.RequestOptions can break easy.src.services.Api, while a change to easy.src.services.Api can't break easy.src.http.RequestOptions.
- Position
- Below the diagonal: easy.src.services.Api uses a module listed above it, which is the healthy direction.
29→24 easy.src.sql.SqlQuery uses easy.src.types.List✕
- Connections
- 1 pair of types, where a type in easy.src.sql.SqlQuery uses a type in easy.src.types.List.
- The types involved
packages.easy.src.sql.SqlQuery.SqlQuery→packages.easy.src.types.List.List
- Direction
- easy.src.sql.SqlQuery uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.sql.SqlQuery, while a change to easy.src.sql.SqlQuery can't break easy.src.types.List.
- Position
- Below the diagonal: easy.src.sql.SqlQuery uses a module listed above it, which is the healthy direction.
30→6 easy.src.types.Gateway uses easy.src.types.Id✕
- Connections
- 1 pair of types, where a type in easy.src.types.Gateway uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.types.Gateway.Gateway→packages.easy.src.types.Id.Id
- Direction
- easy.src.types.Gateway uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.types.Gateway, while a change to easy.src.types.Gateway can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.types.Gateway uses a module listed above it, which is the healthy direction.
30→7 easy.src.types.Gateway uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.types.Gateway uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.types.Gateway.Gateway→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.types.Gateway uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.types.Gateway, while a change to easy.src.types.Gateway can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.types.Gateway uses a module listed above it, which is the healthy direction.
30→8 easy.src.types.Gateway uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.types.Gateway uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.types.Gateway.Gateway→packages.easy.src.types.Types.Optional
- Direction
- easy.src.types.Gateway uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.types.Gateway, while a change to easy.src.types.Gateway can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.types.Gateway uses a module listed above it, which is the healthy direction.
30→14 easy.src.types.Gateway uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy.src.types.Gateway uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.types.Gateway.Gateway→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.types.Gateway uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.types.Gateway, while a change to easy.src.types.Gateway can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.types.Gateway uses a module listed above it, which is the healthy direction.
30→24 easy.src.types.Gateway uses easy.src.types.List✕
- Connections
- 1 pair of types, where a type in easy.src.types.Gateway uses a type in easy.src.types.List.
- The types involved
packages.easy.src.types.Gateway.Gateway→packages.easy.src.types.List.List
- Direction
- easy.src.types.Gateway uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.types.Gateway, while a change to easy.src.types.Gateway can't break easy.src.types.List.
- Position
- Below the diagonal: easy.src.types.Gateway uses a module listed above it, which is the healthy direction.
31→6 easy.src.types.Repository uses easy.src.types.Id✕
- Connections
- 2 pairs of types, where a type in easy.src.types.Repository uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.types.Repository.Repository→packages.easy.src.types.Id.Idpackages.easy.src.types.Repository.Repository→packages.easy.src.types.Id.Key
- Direction
- easy.src.types.Repository uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.types.Repository, while a change to easy.src.types.Repository can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.types.Repository uses a module listed above it, which is the healthy direction.
31→7 easy.src.types.Repository uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.types.Repository uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.types.Repository.Repository→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.types.Repository uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.types.Repository, while a change to easy.src.types.Repository can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.types.Repository uses a module listed above it, which is the healthy direction.
31→14 easy.src.types.Repository uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy.src.types.Repository uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.types.Repository.Repository→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.types.Repository uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.types.Repository, while a change to easy.src.types.Repository can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.types.Repository uses a module listed above it, which is the healthy direction.
31→24 easy.src.types.Repository uses easy.src.types.List✕
- Connections
- 1 pair of types, where a type in easy.src.types.Repository uses a type in easy.src.types.List.
- The types involved
packages.easy.src.types.Repository.Repository→packages.easy.src.types.List.List
- Direction
- easy.src.types.Repository uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.types.Repository, while a change to easy.src.types.Repository can't break easy.src.types.List.
- Position
- Below the diagonal: easy.src.types.Repository uses a module listed above it, which is the healthy direction.
32→1 easy-express.src.express uses easy-domain.src.enums.Country✕
- Connections
- 1 pair of types, where a type in easy-express.src.express uses a type in easy-domain.src.enums.Country.
- The types involved
packages.easy-express.src.express.ErrorHandler→packages.easy-domain.src.enums.Country.Enum
- Direction
- easy-express.src.express uses easy-domain.src.enums.Country, so a change to easy-domain.src.enums.Country can break easy-express.src.express, while a change to easy-express.src.express can't break easy-domain.src.enums.Country.
- Position
- Below the diagonal: easy-express.src.express uses a module listed above it, which is the healthy direction.
32→27 easy-express.src.express uses easy-service.src.resources.Service✕
- Connections
- 1 pair of types, where a type in easy-express.src.express uses a type in easy-service.src.resources.Service.
- The types involved
packages.easy-express.src.express.ExpressProvider→packages.easy-service.src.resources.Service.Service
- Direction
- easy-express.src.express uses easy-service.src.resources.Service, so a change to easy-service.src.resources.Service can break easy-express.src.express, while a change to easy-express.src.express can't break easy-service.src.resources.Service.
- Position
- Below the diagonal: easy-express.src.express uses a module listed above it, which is the healthy direction.
33→6 easy-mongo.src.MongoGateway uses easy.src.types.Id✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoGateway uses a type in easy.src.types.Id.
- The types involved
packages.easy-mongo.src.MongoGateway.MongoGateway→packages.easy.src.types.Id.Id
- Direction
- easy-mongo.src.MongoGateway uses easy.src.types.Id, so a change to easy.src.types.Id can break easy-mongo.src.MongoGateway, while a change to easy-mongo.src.MongoGateway can't break easy.src.types.Id.
- Position
- Below the diagonal: easy-mongo.src.MongoGateway uses a module listed above it, which is the healthy direction.
33→7 easy-mongo.src.MongoGateway uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoGateway uses a type in easy.src.types.Json.
- The types involved
packages.easy-mongo.src.MongoGateway.MongoGateway→packages.easy.src.types.Json.JsonValue
- Direction
- easy-mongo.src.MongoGateway uses easy.src.types.Json, so a change to easy.src.types.Json can break easy-mongo.src.MongoGateway, while a change to easy-mongo.src.MongoGateway can't break easy.src.types.Json.
- Position
- Below the diagonal: easy-mongo.src.MongoGateway uses a module listed above it, which is the healthy direction.
33→14 easy-mongo.src.MongoGateway uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoGateway uses a type in easy.src.types.PageList.
- The types involved
packages.easy-mongo.src.MongoGateway.MongoGateway→packages.easy.src.types.PageList.PageList
- Direction
- easy-mongo.src.MongoGateway uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy-mongo.src.MongoGateway, while a change to easy-mongo.src.MongoGateway can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy-mongo.src.MongoGateway uses a module listed above it, which is the healthy direction.
33→17 easy-mongo.src.MongoGateway uses easy-mongo.src.MongoProvider✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoGateway uses a type in easy-mongo.src.MongoProvider.
- The types involved
packages.easy-mongo.src.MongoGateway.MongoGateway→packages.easy-mongo.src.MongoProvider.MongoProvider
- Direction
- easy-mongo.src.MongoGateway uses easy-mongo.src.MongoProvider, so a change to easy-mongo.src.MongoProvider can break easy-mongo.src.MongoGateway, while a change to easy-mongo.src.MongoGateway can't break easy-mongo.src.MongoProvider.
- Position
- Below the diagonal: easy-mongo.src.MongoGateway uses a module listed above it, which is the healthy direction.
33→20 easy-mongo.src.MongoGateway uses easy-mongo.src.Collection✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoGateway uses a type in easy-mongo.src.Collection.
- The types involved
packages.easy-mongo.src.MongoGateway.MongoGateway→packages.easy-mongo.src.Collection.Collection
- Direction
- easy-mongo.src.MongoGateway uses easy-mongo.src.Collection, so a change to easy-mongo.src.Collection can break easy-mongo.src.MongoGateway, while a change to easy-mongo.src.MongoGateway can't break easy-mongo.src.Collection.
- Position
- Below the diagonal: easy-mongo.src.MongoGateway uses a module listed above it, which is the healthy direction.
33→24 easy-mongo.src.MongoGateway uses easy.src.types.List✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoGateway uses a type in easy.src.types.List.
- The types involved
packages.easy-mongo.src.MongoGateway.MongoGateway→packages.easy.src.types.List.List
- Direction
- easy-mongo.src.MongoGateway uses easy.src.types.List, so a change to easy.src.types.List can break easy-mongo.src.MongoGateway, while a change to easy-mongo.src.MongoGateway can't break easy.src.types.List.
- Position
- Below the diagonal: easy-mongo.src.MongoGateway uses a module listed above it, which is the healthy direction.
33→30 easy-mongo.src.MongoGateway uses easy.src.types.Gateway✕
- Connections
- 1 pair of types, where a type in easy-mongo.src.MongoGateway uses a type in easy.src.types.Gateway.
- The types involved
packages.easy-mongo.src.MongoGateway.MongoGateway→packages.easy.src.types.Gateway.Gateway
- Direction
- easy-mongo.src.MongoGateway uses easy.src.types.Gateway, so a change to easy.src.types.Gateway can break easy-mongo.src.MongoGateway, while a change to easy-mongo.src.MongoGateway can't break easy.src.types.Gateway.
- Position
- Below the diagonal: easy-mongo.src.MongoGateway uses a module listed above it, which is the healthy direction.
34→6 easy.src.data.InMemoryGateway uses easy.src.types.Id✕
- Connections
- 1 pair of types, where a type in easy.src.data.InMemoryGateway uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.data.InMemoryGateway.InMemoryGateway→packages.easy.src.types.Id.Id
- Direction
- easy.src.data.InMemoryGateway uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.data.InMemoryGateway, while a change to easy.src.data.InMemoryGateway can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.data.InMemoryGateway uses a module listed above it, which is the healthy direction.
34→7 easy.src.data.InMemoryGateway uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.data.InMemoryGateway uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.data.InMemoryGateway.InMemoryGateway→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.data.InMemoryGateway uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.data.InMemoryGateway, while a change to easy.src.data.InMemoryGateway can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.data.InMemoryGateway uses a module listed above it, which is the healthy direction.
34→8 easy.src.data.InMemoryGateway uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.data.InMemoryGateway uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.data.InMemoryGateway.InMemoryGateway→packages.easy.src.types.Types.Optional
- Direction
- easy.src.data.InMemoryGateway uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.data.InMemoryGateway, while a change to easy.src.data.InMemoryGateway can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.data.InMemoryGateway uses a module listed above it, which is the healthy direction.
34→14 easy.src.data.InMemoryGateway uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy.src.data.InMemoryGateway uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.data.InMemoryGateway.InMemoryGateway→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.data.InMemoryGateway uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.data.InMemoryGateway, while a change to easy.src.data.InMemoryGateway can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.data.InMemoryGateway uses a module listed above it, which is the healthy direction.
34→30 easy.src.data.InMemoryGateway uses easy.src.types.Gateway✕
- Connections
- 2 pairs of types, where a type in easy.src.data.InMemoryGateway uses a type in easy.src.types.Gateway.
- The types involved
packages.easy.src.data.InMemoryGateway.InMemoryGateway→packages.easy.src.types.Gateway.FetchOptionspackages.easy.src.data.InMemoryGateway.InMemoryGateway→packages.easy.src.types.Gateway.Gateway
- Direction
- easy.src.data.InMemoryGateway uses easy.src.types.Gateway, so a change to easy.src.types.Gateway can break easy.src.data.InMemoryGateway, while a change to easy.src.data.InMemoryGateway can't break easy.src.types.Gateway.
- Position
- Below the diagonal: easy.src.data.InMemoryGateway uses a module listed above it, which is the healthy direction.
35→6 easy.src.domain.Repo uses easy.src.types.Id✕
- Connections
- 2 pairs of types, where a type in easy.src.domain.Repo uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.domain.Repo.Repo→packages.easy.src.types.Id.Idpackages.easy.src.domain.Repo.Repo→packages.easy.src.types.Id.Key
- Direction
- easy.src.domain.Repo uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.domain.Repo, while a change to easy.src.domain.Repo can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.domain.Repo uses a module listed above it, which is the healthy direction.
35→7 easy.src.domain.Repo uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.domain.Repo uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.domain.Repo.Repo→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.domain.Repo uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.domain.Repo, while a change to easy.src.domain.Repo can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.domain.Repo uses a module listed above it, which is the healthy direction.
35→14 easy.src.domain.Repo uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy.src.domain.Repo uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.domain.Repo.Repo→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.domain.Repo uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.domain.Repo, while a change to easy.src.domain.Repo can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.domain.Repo uses a module listed above it, which is the healthy direction.
35→19 easy.src.domain.Repo uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy.src.domain.Repo uses a type in easy.src.types.
- The types involved
packages.easy.src.domain.Repo.Repo→packages.easy.src.types.Constructor
- Direction
- easy.src.domain.Repo uses easy.src.types, so a change to easy.src.types can break easy.src.domain.Repo, while a change to easy.src.domain.Repo can't break easy.src.types.
- Position
- Below the diagonal: easy.src.domain.Repo uses a module listed above it, which is the healthy direction.
35→24 easy.src.domain.Repo uses easy.src.types.List✕
- Connections
- 1 pair of types, where a type in easy.src.domain.Repo uses a type in easy.src.types.List.
- The types involved
packages.easy.src.domain.Repo.Repo→packages.easy.src.types.List.List
- Direction
- easy.src.domain.Repo uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.domain.Repo, while a change to easy.src.domain.Repo can't break easy.src.types.List.
- Position
- Below the diagonal: easy.src.domain.Repo uses a module listed above it, which is the healthy direction.
35→30 easy.src.domain.Repo uses easy.src.types.Gateway✕
- Connections
- 1 pair of types, where a type in easy.src.domain.Repo uses a type in easy.src.types.Gateway.
- The types involved
packages.easy.src.domain.Repo.Repo→packages.easy.src.types.Gateway.Gateway
- Direction
- easy.src.domain.Repo uses easy.src.types.Gateway, so a change to easy.src.types.Gateway can break easy.src.domain.Repo, while a change to easy.src.domain.Repo can't break easy.src.types.Gateway.
- Position
- Below the diagonal: easy.src.domain.Repo uses a module listed above it, which is the healthy direction.
35→31 easy.src.domain.Repo uses easy.src.types.Repository✕
- Connections
- 1 pair of types, where a type in easy.src.domain.Repo uses a type in easy.src.types.Repository.
- The types involved
packages.easy.src.domain.Repo.Repo→packages.easy.src.types.Repository.Repository
- Direction
- easy.src.domain.Repo uses easy.src.types.Repository, so a change to easy.src.types.Repository can break easy.src.domain.Repo, while a change to easy.src.domain.Repo can't break easy.src.types.Repository.
- Position
- Below the diagonal: easy.src.domain.Repo uses a module listed above it, which is the healthy direction.
36→6 easy.src.process.Search uses easy.src.types.Id✕
- Connections
- 2 pairs of types, where a type in easy.src.process.Search uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.process.Search.Search→packages.easy.src.types.Id.Idpackages.easy.src.process.Search.Search→packages.easy.src.types.Id.Key
- Direction
- easy.src.process.Search uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.process.Search, while a change to easy.src.process.Search can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.process.Search uses a module listed above it, which is the healthy direction.
36→7 easy.src.process.Search uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.process.Search uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.process.Search.Search→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.process.Search uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.process.Search, while a change to easy.src.process.Search can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.process.Search uses a module listed above it, which is the healthy direction.
36→14 easy.src.process.Search uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy.src.process.Search uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.process.Search.Search→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.process.Search uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.process.Search, while a change to easy.src.process.Search can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.process.Search uses a module listed above it, which is the healthy direction.
36→22 easy.src.process.Search uses easy.src.resources.Req✕
- Connections
- 1 pair of types, where a type in easy.src.process.Search uses a type in easy.src.resources.Req.
- The types involved
packages.easy.src.process.Search.Search→packages.easy.src.resources.Req.Req
- Direction
- easy.src.process.Search uses easy.src.resources.Req, so a change to easy.src.resources.Req can break easy.src.process.Search, while a change to easy.src.process.Search can't break easy.src.resources.Req.
- Position
- Below the diagonal: easy.src.process.Search uses a module listed above it, which is the healthy direction.
36→24 easy.src.process.Search uses easy.src.types.List✕
- Connections
- 1 pair of types, where a type in easy.src.process.Search uses a type in easy.src.types.List.
- The types involved
packages.easy.src.process.Search.Search→packages.easy.src.types.List.List
- Direction
- easy.src.process.Search uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.process.Search, while a change to easy.src.process.Search can't break easy.src.types.List.
- Position
- Below the diagonal: easy.src.process.Search uses a module listed above it, which is the healthy direction.
36→31 easy.src.process.Search uses easy.src.types.Repository✕
- Connections
- 1 pair of types, where a type in easy.src.process.Search uses a type in easy.src.types.Repository.
- The types involved
packages.easy.src.process.Search.Search→packages.easy.src.types.Repository.Repository
- Direction
- easy.src.process.Search uses easy.src.types.Repository, so a change to easy.src.types.Repository can break easy.src.process.Search, while a change to easy.src.process.Search can't break easy.src.types.Repository.
- Position
- Below the diagonal: easy.src.process.Search uses a module listed above it, which is the healthy direction.
37→6 easy.src.services.RouteGateway uses easy.src.types.Id✕
- Connections
- 1 pair of types, where a type in easy.src.services.RouteGateway uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.services.RouteGateway.RouteGateway→packages.easy.src.types.Id.Id
- Direction
- easy.src.services.RouteGateway uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.services.RouteGateway, while a change to easy.src.services.RouteGateway can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.services.RouteGateway uses a module listed above it, which is the healthy direction.
37→7 easy.src.services.RouteGateway uses easy.src.types.Json✕
- Connections
- 1 pair of types, where a type in easy.src.services.RouteGateway uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.services.RouteGateway.RouteGateway→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.services.RouteGateway uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.services.RouteGateway, while a change to easy.src.services.RouteGateway can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.services.RouteGateway uses a module listed above it, which is the healthy direction.
37→8 easy.src.services.RouteGateway uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.services.RouteGateway uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.services.RouteGateway.RouteGateway→packages.easy.src.types.Types.Optional
- Direction
- easy.src.services.RouteGateway uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.services.RouteGateway, while a change to easy.src.services.RouteGateway can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.services.RouteGateway uses a module listed above it, which is the healthy direction.
37→14 easy.src.services.RouteGateway uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy.src.services.RouteGateway uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.services.RouteGateway.RouteGateway→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.services.RouteGateway uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.services.RouteGateway, while a change to easy.src.services.RouteGateway can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.services.RouteGateway uses a module listed above it, which is the healthy direction.
37→19 easy.src.services.RouteGateway uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy.src.services.RouteGateway uses a type in easy.src.types.
- The types involved
packages.easy.src.services.RouteGateway.RouteGateway→packages.easy.src.types.Func
- Direction
- easy.src.services.RouteGateway uses easy.src.types, so a change to easy.src.types can break easy.src.services.RouteGateway, while a change to easy.src.services.RouteGateway can't break easy.src.types.
- Position
- Below the diagonal: easy.src.services.RouteGateway uses a module listed above it, which is the healthy direction.
37→24 easy.src.services.RouteGateway uses easy.src.types.List✕
- Connections
- 1 pair of types, where a type in easy.src.services.RouteGateway uses a type in easy.src.types.List.
- The types involved
packages.easy.src.services.RouteGateway.RouteGateway→packages.easy.src.types.List.List
- Direction
- easy.src.services.RouteGateway uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.services.RouteGateway, while a change to easy.src.services.RouteGateway can't break easy.src.types.List.
- Position
- Below the diagonal: easy.src.services.RouteGateway uses a module listed above it, which is the healthy direction.
37→28 easy.src.services.RouteGateway uses easy.src.services.Api✕
- Connections
- 1 pair of types, where a type in easy.src.services.RouteGateway uses a type in easy.src.services.Api.
- The types involved
packages.easy.src.services.RouteGateway.RouteGateway→packages.easy.src.services.Api.Api
- Direction
- easy.src.services.RouteGateway uses easy.src.services.Api, so a change to easy.src.services.Api can break easy.src.services.RouteGateway, while a change to easy.src.services.RouteGateway can't break easy.src.services.Api.
- Position
- Below the diagonal: easy.src.services.RouteGateway uses a module listed above it, which is the healthy direction.
38→6 easy.src.domain.Typo uses easy.src.types.Id✕
- Connections
- 4 pairs of types, where a type in easy.src.domain.Typo uses a type in easy.src.types.Id.
- The types involved
packages.easy.src.domain.Typo.Agent→packages.easy.src.types.Id.Idpackages.easy.src.domain.Typo.Agent→packages.easy.src.types.Id.Keypackages.easy.src.domain.Typo.Typo→packages.easy.src.types.Id.Idpackages.easy.src.domain.Typo.Typo→packages.easy.src.types.Id.Key
- Direction
- easy.src.domain.Typo uses easy.src.types.Id, so a change to easy.src.types.Id can break easy.src.domain.Typo, while a change to easy.src.domain.Typo can't break easy.src.types.Id.
- Position
- Below the diagonal: easy.src.domain.Typo uses a module listed above it, which is the healthy direction.
38→7 easy.src.domain.Typo uses easy.src.types.Json✕
- Connections
- 2 pairs of types, where a type in easy.src.domain.Typo uses a type in easy.src.types.Json.
- The types involved
packages.easy.src.domain.Typo.Agent→packages.easy.src.types.Json.JsonValuepackages.easy.src.domain.Typo.Typo→packages.easy.src.types.Json.JsonValue
- Direction
- easy.src.domain.Typo uses easy.src.types.Json, so a change to easy.src.types.Json can break easy.src.domain.Typo, while a change to easy.src.domain.Typo can't break easy.src.types.Json.
- Position
- Below the diagonal: easy.src.domain.Typo uses a module listed above it, which is the healthy direction.
38→14 easy.src.domain.Typo uses easy.src.types.PageList✕
- Connections
- 2 pairs of types, where a type in easy.src.domain.Typo uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.domain.Typo.Agent→packages.easy.src.types.PageList.PageListpackages.easy.src.domain.Typo.Typo→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.domain.Typo uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.domain.Typo, while a change to easy.src.domain.Typo can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.domain.Typo uses a module listed above it, which is the healthy direction.
38→24 easy.src.domain.Typo uses easy.src.types.List✕
- Connections
- 2 pairs of types, where a type in easy.src.domain.Typo uses a type in easy.src.types.List.
- The types involved
packages.easy.src.domain.Typo.Agent→packages.easy.src.types.List.Listpackages.easy.src.domain.Typo.Typo→packages.easy.src.types.List.List
- Direction
- easy.src.domain.Typo uses easy.src.types.List, so a change to easy.src.types.List can break easy.src.domain.Typo, while a change to easy.src.domain.Typo can't break easy.src.types.List.
- Position
- Below the diagonal: easy.src.domain.Typo uses a module listed above it, which is the healthy direction.
38→30 easy.src.domain.Typo uses easy.src.types.Gateway✕
- Connections
- 1 pair of types, where a type in easy.src.domain.Typo uses a type in easy.src.types.Gateway.
- The types involved
packages.easy.src.domain.Typo.Typo→packages.easy.src.types.Gateway.Gateway
- Direction
- easy.src.domain.Typo uses easy.src.types.Gateway, so a change to easy.src.types.Gateway can break easy.src.domain.Typo, while a change to easy.src.domain.Typo can't break easy.src.types.Gateway.
- Position
- Below the diagonal: easy.src.domain.Typo uses a module listed above it, which is the healthy direction.
38→31 easy.src.domain.Typo uses easy.src.types.Repository✕
- Connections
- 2 pairs of types, where a type in easy.src.domain.Typo uses a type in easy.src.types.Repository.
- The types involved
packages.easy.src.domain.Typo.Agent→packages.easy.src.types.Repository.Repositorypackages.easy.src.domain.Typo.Typo→packages.easy.src.types.Repository.Repository
- Direction
- easy.src.domain.Typo uses easy.src.types.Repository, so a change to easy.src.types.Repository can break easy.src.domain.Typo, while a change to easy.src.domain.Typo can't break easy.src.types.Repository.
- Position
- Below the diagonal: easy.src.domain.Typo uses a module listed above it, which is the healthy direction.
38→37 easy.src.domain.Typo uses easy.src.services.RouteGateway✕
- Connections
- 1 pair of types, where a type in easy.src.domain.Typo uses a type in easy.src.services.RouteGateway.
- The types involved
packages.easy.src.domain.Typo.Agent→packages.easy.src.services.RouteGateway.RouteGateway
- Direction
- easy.src.domain.Typo uses easy.src.services.RouteGateway, so a change to easy.src.services.RouteGateway can break easy.src.domain.Typo, while a change to easy.src.domain.Typo can't break easy.src.services.RouteGateway.
- Position
- Below the diagonal: easy.src.domain.Typo uses a module listed above it, which is the healthy direction.
39→8 easy.src.services.MappedRouteGateway uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.services.MappedRouteGateway uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.services.MappedRouteGateway.MappedRouteGateway→packages.easy.src.types.Types.Optional
- Direction
- easy.src.services.MappedRouteGateway uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.services.MappedRouteGateway, while a change to easy.src.services.MappedRouteGateway can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.services.MappedRouteGateway uses a module listed above it, which is the healthy direction.
39→14 easy.src.services.MappedRouteGateway uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy.src.services.MappedRouteGateway uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.services.MappedRouteGateway.MappedRouteGateway→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.services.MappedRouteGateway uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.services.MappedRouteGateway, while a change to easy.src.services.MappedRouteGateway can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.services.MappedRouteGateway uses a module listed above it, which is the healthy direction.
39→19 easy.src.services.MappedRouteGateway uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy.src.services.MappedRouteGateway uses a type in easy.src.types.
- The types involved
packages.easy.src.services.MappedRouteGateway.MappedRouteGateway→packages.easy.src.types.Func
- Direction
- easy.src.services.MappedRouteGateway uses easy.src.types, so a change to easy.src.types can break easy.src.services.MappedRouteGateway, while a change to easy.src.services.MappedRouteGateway can't break easy.src.types.
- Position
- Below the diagonal: easy.src.services.MappedRouteGateway uses a module listed above it, which is the healthy direction.
39→21 easy.src.services.MappedRouteGateway uses easy.src.http.RequestOptions✕
- Connections
- 1 pair of types, where a type in easy.src.services.MappedRouteGateway uses a type in easy.src.http.RequestOptions.
- The types involved
packages.easy.src.services.MappedRouteGateway.MappedRouteGateway→packages.easy.src.http.RequestOptions.RequestOptions
- Direction
- easy.src.services.MappedRouteGateway uses easy.src.http.RequestOptions, so a change to easy.src.http.RequestOptions can break easy.src.services.MappedRouteGateway, while a change to easy.src.services.MappedRouteGateway can't break easy.src.http.RequestOptions.
- Position
- Below the diagonal: easy.src.services.MappedRouteGateway uses a module listed above it, which is the healthy direction.
39→28 easy.src.services.MappedRouteGateway uses easy.src.services.Api✕
- Connections
- 1 pair of types, where a type in easy.src.services.MappedRouteGateway uses a type in easy.src.services.Api.
- The types involved
packages.easy.src.services.MappedRouteGateway.MappedRouteGateway→packages.easy.src.services.Api.Api
- Direction
- easy.src.services.MappedRouteGateway uses easy.src.services.Api, so a change to easy.src.services.Api can break easy.src.services.MappedRouteGateway, while a change to easy.src.services.MappedRouteGateway can't break easy.src.services.Api.
- Position
- Below the diagonal: easy.src.services.MappedRouteGateway uses a module listed above it, which is the healthy direction.
39→37 easy.src.services.MappedRouteGateway uses easy.src.services.RouteGateway✕
- Connections
- 1 pair of types, where a type in easy.src.services.MappedRouteGateway uses a type in easy.src.services.RouteGateway.
- The types involved
packages.easy.src.services.MappedRouteGateway.MappedRouteGateway→packages.easy.src.services.RouteGateway.RouteGateway
- Direction
- easy.src.services.MappedRouteGateway uses easy.src.services.RouteGateway, so a change to easy.src.services.RouteGateway can break easy.src.services.MappedRouteGateway, while a change to easy.src.services.MappedRouteGateway can't break easy.src.services.RouteGateway.
- Position
- Below the diagonal: easy.src.services.MappedRouteGateway uses a module listed above it, which is the healthy direction.
40→8 easy.src.services.ViewRouteGateway uses easy.src.types.Types✕
- Connections
- 1 pair of types, where a type in easy.src.services.ViewRouteGateway uses a type in easy.src.types.Types.
- The types involved
packages.easy.src.services.ViewRouteGateway.ViewRouteGateway→packages.easy.src.types.Types.Optional
- Direction
- easy.src.services.ViewRouteGateway uses easy.src.types.Types, so a change to easy.src.types.Types can break easy.src.services.ViewRouteGateway, while a change to easy.src.services.ViewRouteGateway can't break easy.src.types.Types.
- Position
- Below the diagonal: easy.src.services.ViewRouteGateway uses a module listed above it, which is the healthy direction.
40→14 easy.src.services.ViewRouteGateway uses easy.src.types.PageList✕
- Connections
- 1 pair of types, where a type in easy.src.services.ViewRouteGateway uses a type in easy.src.types.PageList.
- The types involved
packages.easy.src.services.ViewRouteGateway.ViewRouteGateway→packages.easy.src.types.PageList.PageList
- Direction
- easy.src.services.ViewRouteGateway uses easy.src.types.PageList, so a change to easy.src.types.PageList can break easy.src.services.ViewRouteGateway, while a change to easy.src.services.ViewRouteGateway can't break easy.src.types.PageList.
- Position
- Below the diagonal: easy.src.services.ViewRouteGateway uses a module listed above it, which is the healthy direction.
40→19 easy.src.services.ViewRouteGateway uses easy.src.types✕
- Connections
- 1 pair of types, where a type in easy.src.services.ViewRouteGateway uses a type in easy.src.types.
- The types involved
packages.easy.src.services.ViewRouteGateway.ViewRouteGateway→packages.easy.src.types.Func
- Direction
- easy.src.services.ViewRouteGateway uses easy.src.types, so a change to easy.src.types can break easy.src.services.ViewRouteGateway, while a change to easy.src.services.ViewRouteGateway can't break easy.src.types.
- Position
- Below the diagonal: easy.src.services.ViewRouteGateway uses a module listed above it, which is the healthy direction.
40→21 easy.src.services.ViewRouteGateway uses easy.src.http.RequestOptions✕
- Connections
- 1 pair of types, where a type in easy.src.services.ViewRouteGateway uses a type in easy.src.http.RequestOptions.
- The types involved
packages.easy.src.services.ViewRouteGateway.ViewRouteGateway→packages.easy.src.http.RequestOptions.RequestOptions
- Direction
- easy.src.services.ViewRouteGateway uses easy.src.http.RequestOptions, so a change to easy.src.http.RequestOptions can break easy.src.services.ViewRouteGateway, while a change to easy.src.services.ViewRouteGateway can't break easy.src.http.RequestOptions.
- Position
- Below the diagonal: easy.src.services.ViewRouteGateway uses a module listed above it, which is the healthy direction.
40→28 easy.src.services.ViewRouteGateway uses easy.src.services.Api✕
- Connections
- 1 pair of types, where a type in easy.src.services.ViewRouteGateway uses a type in easy.src.services.Api.
- The types involved
packages.easy.src.services.ViewRouteGateway.ViewRouteGateway→packages.easy.src.services.Api.Api
- Direction
- easy.src.services.ViewRouteGateway uses easy.src.services.Api, so a change to easy.src.services.Api can break easy.src.services.ViewRouteGateway, while a change to easy.src.services.ViewRouteGateway can't break easy.src.services.Api.
- Position
- Below the diagonal: easy.src.services.ViewRouteGateway uses a module listed above it, which is the healthy direction.
40→37 easy.src.services.ViewRouteGateway uses easy.src.services.RouteGateway✕
- Connections
- 1 pair of types, where a type in easy.src.services.ViewRouteGateway uses a type in easy.src.services.RouteGateway.
- The types involved
packages.easy.src.services.ViewRouteGateway.ViewRouteGateway→packages.easy.src.services.RouteGateway.RouteGateway
- Direction
- easy.src.services.ViewRouteGateway uses easy.src.services.RouteGateway, so a change to easy.src.services.RouteGateway can break easy.src.services.ViewRouteGateway, while a change to easy.src.services.ViewRouteGateway can't break easy.src.services.RouteGateway.
- Position
- Below the diagonal: easy.src.services.ViewRouteGateway 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 |
|---|---|---|
| A05:2025 — Injection | 21 | High / Critical |
| A03:2025 — Software Supply Chain Failures | 17 | High / Critical |
Roadmap
Top priorities: Adopt pino (or winston) and log at meaningful points in the services you run; Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies; Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Adopt pino (or winston) and log at meaningful points in the services you run. | +7.0 pts | Medium | Observability |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +7.0 pts | Medium | Dependency Hygiene |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.5 pts | Medium | Release Hygiene |
| Resolve the 2 Off-boarding risk finding(s) in Bus Factor. | +0.9 pts | Low | Bus Factor |
| 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. | +1.4 pts | Medium | Architecture documentation |
| Add `tsc --noEmit` as package.json scripts and run them in CI. | +1.3 pts | Medium | Tooling |
| Break each cycle by extracting the shared piece into a module both sides can import. | +1.2 pts | Medium | Circular Imports |
| Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. | +0.6 pts | Low | Bus Factor |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 3.7 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 4.8 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
| packages/easy-domain/src/enums/Locale.ts | 7.8 | Mixed | God Classes: FunctionTooLong: Locale.registry |
| packages/easy-domain/src/enums/Country.ts | 7.8 | Mixed | God Classes: FunctionTooLong: Country.registry |
| packages/easy-express/package.json | 7.8 | Mixed | Dependency Hygiene: Deprecated: @types/form-urlencoded |
| packages/easy/package.json | 7.8 | Mixed | Dependency Hygiene: Deprecated: @types/form-urlencoded |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| packages/easy/src/types/List.ts | 8.5 | Near-clean | God Classes: TooManyMethods: List |
| packages/easy-domain/src/enums/Currency.ts | 8.5 | Near-clean | God Classes: FunctionTooLong: Currency.registry |
| packages/easy/src/types/PageList.ts | 8.5 | Near-clean | God Classes: TooManyMethods: PageList |
| package.json | 8.5 | Near-clean | Dependency Hygiene: Deprecated: eslint-plugin-standard |
| packages/easy-test-web/test/Tester.test.ts | 9.5 | Near-clean | Test Quality: Mock-dominated test: closable browser testers close their browser |
| packages/easy/test/services/RequestProvider.test.ts | 9.5 | Near-clean | Test Quality: Mock-dominated test: interceptors see the outgoing request and the raw response before transform |
| packages/easy/src/process/Manage.ts | 9.5 | Near-clean | Navigability: Pass-through layer |
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 80 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
What we checked — 80 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, 105 of 122 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 | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D8 Code Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 161 test file(s) failed while being loaded here, so none of their cases ran (typically a native addon or generated module the package's install scripts build, which the analyzer's scripts-off install does not run). The 13 production file(s) those files import that read under half covered are unmeasured in this run, not untested, so their figures are left out of the per-file rows and the 95.6% rather than published as low coverage. You can widen what we reach: optional: commit the lcov report of a run where those test files load, and their modules are read from 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.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D23 Boundary Type-Coupling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind measured 0/40 valid on a seeded held-out sample of its rows on 98 C# repositories (docs/plans/deterministic-engine/adjudication/P5c-D23-units.md, "Version 1 ON MAIN"): the noise rows were dependencies on layer folders, shared cores and grouping folders read as contexts. By the pre-registered fallback (PREREGISTRATION v37) it publishes no row until version 4 passes its gate. The candidates are counted here, not reported as findings, and the score does not include them.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `packages/easy/src/utils/View.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.
- AXB1 Runtime evidence locked — no reproducible boot — 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. Subject: a UI framework dependency ('react'). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- C1 Data Protection — 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. 'mssql' is imported (packages/easy-mssql/src/SqlServerProvider.ts:4), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C3 Audit Trail — not measured this run — 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. 'mssql' is imported (packages/easy-mssql/src/SqlServerProvider.ts:4), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C4 Data Retention — not measured this run — 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. 'mssql' is imported (packages/easy-mssql/src/SqlServerProvider.ts:4), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- C5 Data-Subject Rights — not measured this run — 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. 'mssql' is imported (packages/easy-mssql/src/SqlServerProvider.ts:4), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- 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.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- 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.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
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
7 god class(es) detected.
What to do
- Resolve the 3 FunctionTooLong finding(s) in God Classes — start with Locale.ts, Country.ts, Currency.ts. — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 FileTooLong finding(s) in God Classes — start with Locale.ts, Country.ts. — One of this dimension's main actionable groups (2 warning-level).
- Resolve the 2 TooManyMethods finding(s) in God Classes — start with List.ts, PageList.ts. — One of this dimension's main actionable groups (2 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D5 · Coupling
13 production modules (npm), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 1 module(s) off the main sequence.
What to do
- Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
- Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 12 classes have LCOM4 above 3.
D8 · Code Coverage
Line coverage 95.6%. Measured from the JavaScript/TypeScript suite (jest via `yarn install --immutable --mode=skip-build` in the repository root; jest via `yarn install --immutable --mode=skip-build` in packages/easy-test/).
D9 · Test Distribution
2225 test methods: 2225 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 2225 `it`/`test` case(s) across 191 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 2225 tests.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `yarn install --immutable --mode=skip-build` in the repository root (152 tests); jest via `yarn install --immutable --mode=skip-build` in packages/easy-test/ (130 tests)): measured (0 flaky).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window. Repeated repair below the complexity floor: packages/easy-domain/src/values/VAT.ts (4 of 4 changes were fixes)
What to do
- Resolve the 1 Repeated repair finding(s) in Churn × Complexity Hotspots — start with VAT.ts. — One of this dimension's main actionable groups (1 warning-level).
D16 · Bus Factor
12 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/easy-domain/src/enums/Locale.ts. Counted over 41 of the 253 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
What to do
- Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Further sole-owners (lower concentration) finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
0 deducted task-comment markers across 10036 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
2 of 2 documentation facets pass in full. 2 document(s) read across 14 unit(s).
D23 · Boundary Type-Coupling
10 domain type(s) cross context boundaries across 13 contexts; they are measured and withheld (not published, not scored). Contexts: easy, easy-bq, easy-domain, easy-express, easy-mongo, easy-mssql, easy-playwright, easy-puppeteer, easy-react, easy-service, easy-test, easy-test-react and 1 more.
D24 · Comment Value
0 of 43 judged comments only repeat the code they sit on (0.0 %). 2 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 11 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D27 · Navigability
49 % of calls cross a namespace and 0 % go through an interface, but 83 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
21 finding(s): 0 critical, 20 high, 1 medium, 0 low. 16 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `packages/easy/src/utils/View.ts` (line 42) — 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 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 16 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (16 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
11 finding(s): 0 critical, 4 high, 5 medium, 2 low.
What to do
- Resolve the 4 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 issue-level).
- Resolve the 5 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (5). — One of this dimension's main actionable groups (5 warning-level).
- Resolve the 2 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
D34 · Knowledge Freshness
Every significant source file has living knowledge — recently and meaningfully worked. Counted over 41 of the 253 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
C2 · Access Controls
- Authorization IS enforced here (by route guards, auth middleware or checks that refuse a caller) — this is NOT a claim that endpoints are unprotected. What's missing is a NAMED rule set: who may do what is encoded inline where it is checked, so the rules can't be listed, reviewed or tested apart from the code that applies them. Recommendation, not a defect. — packages/easy-express/src/express/SecurityHandler.ts:41
What to do
- Name the access rules — roles/permissions declared once (a @Roles/@Permissions decorator with its guard, a CASL ability, a casbin model, or Supabase CREATE POLICY) and consulted where access is checked, so the rule set is reviewable and testable on its own.
DM1 · Aggregate boundaries
DM10 · One transaction, one aggregate
DM11 · Constructible invalid state
DM4 · Rich vs anemic model
- `Dev` is an aggregate/entity with 9 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/easy-express/test/ref/Dev.ts:3
- `Dev` is an aggregate/entity with 13 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/easy-mongo/test/ref/Dev.ts:3
- `Dev` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/easy-service/test/ref/Dev.ts:3
- `Dev` is an aggregate/entity with 15 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — packages/easy/test/ref/Dev.ts:14
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
DM6 · Domain ↔ infrastructure boundary
- `packages/easy-domain/jest.config.cjs` (domain layer) depends on `../../jest.config.base` (require of `jest.config.base.js`) — a persistence module; the domain should own a port and let an infrastructure adapter implement it. — packages/easy-domain/jest.config.cjs:1
What to do
- Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add a README to the 13 of 13 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 239 JavaScript/TypeScript production file(s) this check read across 13 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
What to do
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- 14 duplicated blocks under packages/ have copies in at least two of the sibling directories easy, easy-domain, easy-express, easy-mongo, easy-playwright, easy-puppeteer — 5 of them are reported below, and 9 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 14 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 14 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 14 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — packages/easy-playwright/src/PlaywrightTester.ts:39
- packages/easy-playwright/src/PlaywrightTester.ts:39 · packages/easy-puppeteer/src/PuppeteerTester.ts:17 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/easy-playwright/src/PlaywrightTester.ts:39
- packages/easy-mongo/src/Collection.ts:26 · packages/easy/src/sql/Table.ts:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/easy-mongo/src/Collection.ts:26
- packages/easy/src/http/HttpVerb.ts:4 · packages/easy/src/process/Apps.ts:4 — the two spans are one implementation copied and then locally edited — 174 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/easy/src/http/HttpVerb.ts:4
- packages/easy/src/services/MappedRouteGateway.ts:15 · packages/easy/src/services/ViewRouteGateway.ts:18 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/easy/src/services/MappedRouteGateway.ts:15
- packages/easy/src/types/List.ts:204 · packages/easy/src/types/PageList.ts:136 — the two spans are one implementation copied and then locally edited — 154 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/easy/src/types/List.ts:204
- packages/easy/src/data/Database.ts:30 · packages/easy/src/process/Apps.ts:5 — the two spans are one implementation copied and then locally edited — 164 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/easy/src/data/Database.ts:30
- packages/easy-domain/src/enums/UnitOfWeight.ts:10 · packages/easy/src/process/Apps.ts:6 — the two spans are one implementation copied and then locally edited — 159 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/easy-domain/src/enums/UnitOfWeight.ts:10
- packages/easy-mongo/src/Stages.ts:44 · packages/easy-mongo/src/Stages.ts:59 — all 2 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/easy-mongo/src/Stages.ts:44
- packages/easy-playwright/src/PlaywrightElement.ts:5 · packages/easy-puppeteer/src/PuppeteerElement.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. — packages/easy-playwright/src/PlaywrightElement.ts:5
- packages/easy/src/services/Api.ts:29 · packages/easy/src/services/Api.ts:40 · packages/easy/src/services/Api.ts:51 — all 3 copies are in the same file, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/easy/src/services/Api.ts:29
- packages/easy/src/validation/Contraints.ts:60 · packages/easy/src/validation/Contraints.ts:70 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/easy/src/validation/Contraints.ts:60
- packages/easy-express/src/types/NamespaceContext.ts:7 · packages/easy/src/types/Context.ts:87 — the two spans are one implementation copied and then locally edited — 57 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/easy-express/src/types/NamespaceContext.ts:7
- packages/easy/src/data/InMemoryGateway.ts:28 · packages/easy/src/data/InMemoryGateway.ts:49 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/easy/src/data/InMemoryGateway.ts:28
- packages/easy/src/domain/Repo.ts:27 · packages/easy/src/domain/Typo.ts:24 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/easy/src/domain/Repo.ts:27
- packages/easy-service/src/resources/Requires.ts:16 · packages/easy-service/src/resources/Requires.ts:23 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/easy-service/src/resources/Requires.ts:16
- packages/easy/src/domain/Repo.ts:63 · packages/easy/src/domain/Repo.ts:75 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/easy/src/domain/Repo.ts:63
- packages/easy/src/sql/Count.ts:5 · packages/easy/src/sql/Select.ts:52 — the two spans are one implementation copied and then locally edited — 60 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/easy/src/sql/Count.ts:5
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
- packages/easy-domain/src/values/DunsNumber.ts:2 imports validator/lib/isLength.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/easy-domain/src/values/DunsNumber.ts:2
- packages/easy-domain/src/values/DunsNumber.ts:3 imports validator/lib/isNumeric.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/easy-domain/src/values/DunsNumber.ts:3
- packages/easy-domain/src/values/EAN.ts:1 imports validator/lib/isEAN.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/easy-domain/src/values/EAN.ts:1
- packages/easy-domain/src/values/Email.ts:1 imports validator/lib/isEmail.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/easy-domain/src/values/Email.ts:1
- packages/easy-domain/src/values/IBAN.ts:1 imports validator/lib/isIBAN.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/easy-domain/src/values/IBAN.ts:1
- packages/easy-domain/src/values/PostalCode.ts:3 imports validator/lib/isPostalCode.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/easy-domain/src/values/PostalCode.ts:3
- packages/easy-domain/src/values/Slug.ts:2 imports validator/lib/isSlug.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/easy-domain/src/values/Slug.ts:2
- packages/easy-domain/src/values/Url.ts:1 imports validator/lib/isURL.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/easy-domain/src/values/Url.ts:1
- packages/easy-domain/src/values/VAT.ts:2 imports validator/lib/isVAT.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — packages/easy-domain/src/values/VAT.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
- parseCalendar has cyclomatic complexity 18 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:522
- parseToken has cyclomatic complexity 13 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:497
- macro has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:360
- render has cyclomatic complexity 13 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:404
- parseIso has cyclomatic complexity 12 and cognitive complexity 9; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:297
R3 · Large Files
- packages/easy-domain/src/enums/Locale.ts has 1153 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/easy-domain/src/enums/Locale.ts:1
- packages/easy-domain/src/enums/Country.ts has 529 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — packages/easy-domain/src/enums/Country.ts:1
- REDACTED has 502 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
R6 · Tooling
- test ✓ · lint ✓ · typecheck ✗ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add `tsc --noEmit` as package.json scripts and run them in CI.
R7 · Dead Code
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. (×6) — test/bundle/check.mjs:133, tsup.config.ts:1, packages/easy-react/test/utils/useRev.test.ts:1, …
- 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.
- Declared in packages/easy-express/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
- Declared in packages/easy-test/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.
- Every import is type-only — move it to devDependencies. — packages/easy-express/src/express/SecurityHandler.ts:9
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- packages/easy-mongo/src/Collection.ts → packages/easy-mongo/src/MongoProvider.ts → packages/easy-mongo/src/Collection.ts — packages/easy-mongo/src/Collection.ts:21
- packages/easy/src/sql/Column.ts → packages/easy/src/sql/Table.ts → packages/easy/src/sql/Column.ts (one verified cycle inside a mutually-dependent group of 9 files) — packages/easy/src/sql/Column.ts:2
- packages/easy/src/types/List.ts → packages/easy/src/utils/If.ts → packages/easy/src/types/List.ts — packages/easy/src/types/List.ts:10
- packages/easy/src/types/Template.ts → packages/easy/src/types/ToText.ts → packages/easy/src/types/Template.ts — packages/easy/src/types/Template.ts:5
- packages/easy/src/validation/Validate.ts → packages/easy/src/validation/When.ts → packages/easy/src/validation/Validate.ts — packages/easy/src/validation/Validate.ts:2
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- `app.listen(…)` serves plain HTTP on a network address, and nothing in its package enforces HTTPS: no TLS served (`https.createServer`, Fastify `https`, Nest `httpsOptions`), no redirect of plain requests to `https://`, no `Strict-Transport-Security` (helmet sends it by default), and no TLS-terminating proxy configuration committed beside it — so a browser may talk to it in clear text. (−2.0 on this card.) — packages/easy-express/src/express/ExpressProvider.ts:49
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
- `toMongoType` is exported and takes `input: unknown` from its caller, and it calls itself at line 7 (`toMongoType`) with a piece of `input` (and at line 13) — and nowhere in `toMongoType` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `toMongoType` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/easy-mongo/src/Utils.ts:7
- `isValid` is exported and takes `subject: unknown` from its caller, and it calls itself at line 34 (`isValid`) with a piece of `subject` — and nowhere in `isValid` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `isValid` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/easy/src/validation/IsValid.ts:34
- `validate` is exported and takes `subject: unknown` from its caller, and it calls itself at line 53 (`validate`) with a piece of `subject` — and nowhere in `validate` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `validate` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/easy/src/validation/Validate.ts:53
- `traverse` is exported and takes `subject: unknown` from its caller, and it calls itself at line 7 (`traverse`) with a piece of `subject` — and nowhere in `traverse` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `traverse` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/easy/src/utils/Traverse.ts:7
- `traverseSet` is exported and takes `property: AnyKey<T>` from its caller, and it calls itself at line 15 (`traverseSet`) with a piece of `property` — and nowhere in `traverseSet` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `traverseSet` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/easy/src/utils/Traverse.ts:15
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
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
X5 · Nullable reference types
- 0/14 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 | 76% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 65% | Adequate — gated by R9 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Maturity | 64% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 40% | Weak — gated by R8, P2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 69% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 71% | Adequate — gated by DM4 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- D12 Dependency Hygiene — 10 observation(s) recorded · Dependency currency not established — registry.npmjs.org did not answer
- 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 — Not assessed: this repository stores data through 'mssql' (packages/easy-mssql/src/SqlServerProvider.ts:4) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
- C4 Data Retention — Not assessed: this repository stores data through 'mssql' (packages/easy-mssql/src/SqlServerProvider.ts:4) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
- C5 Data-Subject Rights — Not assessed: this repository stores data through 'mssql' (packages/easy-mssql/src/SqlServerProvider.ts:4) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 54 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).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- 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
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — Not assessed: this repository stores data through 'mssql' (packages/easy-mssql/src/SqlServerProvider.ts:4) but declares no persisted model this check reads (TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entities, Mongoose schemas, Sequelize or Drizzle tables, Knex migrations, Prisma models). Personal data may be written through raw SQL or a hosted backend, so the absence of a personal-data field here is not evidence that none is stored, and encryption at rest is not scored over a subject that could not be established.
- D14 License Compliance — Not scored — this repository's 567 shipped npm package(s) were resolved from its committed lockfile, but registry.npmjs.org could not be asked for the licence of 17 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.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- 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
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: packages/easy-express/src/express/ExpressProvider.ts:22 (express()))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage data present for 58 file(s), but no domain-layer files were identified: no covered file's path contains any of the markers this check keys on (/domain/, /aggregates/, /valueobjects/, /domainmodel/, .domain/, /entities/), which are matched case-insensitively anywhere in the path. With no domain partition there is nothing to compare the web/controller layer against — if this repository keeps its business rules under a folder named none of those, that naming is what the check cannot see, not the domain logic.
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- 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.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 36 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Import cycle (2 files) packages/easy-mongo/src/Collection.ts:21
- Import cycle (2 files) packages/easy/src/sql/Column.ts:2
- Import cycle (2 files) packages/easy/src/types/List.ts:10
- Import cycle (2 files) packages/easy/src/types/Template.ts:5
- Import cycle (2 files) packages/easy/src/validation/Validate.ts:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'uuid' packages/easy-react/jest.config.cjs:11
- Unlisted import 'uuid' packages/easy-test-react/jest.config.cjs:9
- REDACTED
- REDACTED
- Domain depends on infrastructure: jest.config packages/easy-domain/jest.config.cjs:1
- Unlisted import 'esbuild' test/bundle/check.mjs:133
- Unlisted import 'tsup' tsup.config.ts:1
- Unlisted import '@testing-library/react' packages/easy-react/test/utils/useRev.test.ts:1
- Unlisted import 'express' packages/easy-service/src/resources/Route.ts:5
Serious — 67 finding(s)
- Boundary violation [package:third-party-deep-import] packages/easy-domain/src/values/DunsNumber.ts:2
- Boundary violation [package:third-party-deep-import] packages/easy-domain/src/values/DunsNumber.ts:3
- Boundary violation [package:third-party-deep-import] packages/easy-domain/src/values/EAN.ts:1
- Boundary violation [package:third-party-deep-import] packages/easy-domain/src/values/Email.ts:1
- Boundary violation [package:third-party-deep-import] packages/easy-domain/src/values/IBAN.ts:1
- Boundary violation [package:third-party-deep-import] packages/easy-domain/src/values/PostalCode.ts:3
- Boundary violation [package:third-party-deep-import] packages/easy-domain/src/values/Slug.ts:2
- Boundary violation [package:third-party-deep-import] packages/easy-domain/src/values/Url.ts:1
- Boundary violation [package:third-party-deep-import] packages/easy-domain/src/values/VAT.ts:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Recursive walk over a caller-supplied document has no depth cap packages/easy-mongo/src/Utils.ts:7
- Recursive walk over a caller-supplied document has no depth cap packages/easy/src/validation/IsValid.ts:34
- Recursive walk over a caller-supplied document has no depth cap packages/easy/src/validation/Validate.ts:53
- Recursive walk over a caller-supplied document has no depth cap packages/easy/src/utils/Traverse.ts:7
- Recursive walk over a caller-supplied document has no depth cap packages/easy/src/utils/Traverse.ts:15
- Anemic entity: Dev packages/easy-express/test/ref/Dev.ts:3
- Anemic entity: Dev packages/easy-mongo/test/ref/Dev.ts:3
- Anemic entity: Dev packages/easy-service/test/ref/Dev.ts:3
- Anemic entity: Dev packages/easy/test/ref/Dev.ts:14
- FunctionTooLong: Locale.registry packages/easy-domain/src/enums/Locale.ts:588
- FunctionTooLong: Country.registry packages/easy-domain/src/enums/Country.ts:270
- FunctionTooLong: Currency.registry packages/easy-domain/src/enums/Currency.ts:137
- FileTooLong: enums/Locale.ts packages/easy-domain/src/enums/Locale.ts
- FileTooLong: enums/Country.ts packages/easy-domain/src/enums/Country.ts
- TooManyMethods: List packages/easy/src/types/List.ts:17
- TooManyMethods: PageList packages/easy/src/types/PageList.ts:25
- Duplicated block (13 lines × 2 locations) packages/easy-mongo/src/Collection.ts:26
- Duplicated block (13 lines × 2 locations) packages/easy/src/services/MappedRouteGateway.ts:15
- Duplicated block with local edits (13 matched lines × 2 locations) packages/easy/src/http/HttpVerb.ts:4
- Duplicated block with local edits (13 matched lines × 2 locations) packages/easy/src/types/List.ts:204
- Duplicated block (10 lines × 2 locations) packages/easy-mongo/src/Stages.ts:44
- Duplicated block (10 lines × 2 locations) packages/easy-playwright/src/PlaywrightElement.ts:5
- Duplicated block (7 lines × 2 locations) packages/easy/src/data/InMemoryGateway.ts:28
- Duplicated block (7 lines × 2 locations) packages/easy/src/domain/Repo.ts:27
- Duplicated block (6 lines × 2 locations) packages/easy-service/src/resources/Requires.ts:16
- Duplicated block (6 lines × 2 locations) packages/easy/src/domain/Repo.ts:63
- Repeated repair: packages/easy-domain/src/values/VAT.ts packages/easy-domain/src/values/VAT.ts:19
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Off the main sequence: @thisisagile/easy
- No structured logging
- Duplication concentrated across 6 sibling directories (14 clone groups) packages/easy-playwright/src/PlaywrightTester.ts:39
- Duplicated block (34 lines × 2 locations) packages/easy-playwright/src/PlaywrightTester.ts:39
- Duplicated block with local edits (12 matched lines × 2 locations) packages/easy/src/data/Database.ts:30
- Duplicated block with local edits (11 matched lines × 2 locations) packages/easy-domain/src/enums/UnitOfWeight.ts:10
- Duplicated block (10 lines × 3 locations) packages/easy/src/services/Api.ts:29
- Duplicated block (9 lines × 2 locations) packages/easy/src/validation/Contraints.ts:60
- Duplicated block with local edits (7 matched lines × 2 locations) packages/easy-express/src/types/NamespaceContext.ts:7
- Duplicated block with local edits (6 matched lines × 2 locations) packages/easy/src/sql/Count.ts:5
- Complex function parseCalendar (cyclomatic 18, cognitive 14) REDACTED:522
- Complex function parseToken (cyclomatic 13, cognitive 15) REDACTED:497
- Complex function macro (cyclomatic 13, cognitive 12) REDACTED:360
- Complex function render (cyclomatic 13, cognitive 12) REDACTED:404
- Complex function parseIso (cyclomatic 12, cognitive 9) REDACTED:297
- packages/easy-domain/src/enums/Locale.ts: 1153 lines of code packages/easy-domain/src/enums/Locale.ts:1
- packages/easy-domain/src/enums/Country.ts: 529 lines of code packages/easy-domain/src/enums/Country.ts:1
- REDACTED: 502 lines of code REDACTED:1
- No typecheck script
- Unused dependency 'dpdm'
- Unused dependency 'form-urlencoded'
- Unused dependency 'weak-napi'
Minor — 19 finding(s)
- Mock-dominated test: closable browser testers close their browser packages/easy-test-web/test/Tester.test.ts:68
- Mock-dominated test: interceptors see the outgoing request and the raw response before transform packages/easy/test/services/RequestProvider.test.ts:150
- Off-boarding risk: anonymized user #1
- Off-boarding risk: anonymized user #2
- REDACTED
- REDACTED
- No named authorization policies packages/easy-express/src/express/SecurityHandler.ts:41
- Further sole-owners (lower concentration)
- Projects may be oversized for their cohesion
- Pass-through layer packages/easy/src/process/Manage.ts:6
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- No changelog
- Type-only dependency 'jsonwebtoken' in production deps packages/easy-express/src/express/SecurityHandler.ts:9
- No app-layer HTTPS enforcement detected packages/easy-express/src/express/ExpressProvider.ts:49
- Duplicated predicate packages/easy/src/services/AxiosProvider.ts:36
- 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-faab73422e7d497dae3f0ea454ef69f4/history.json --exit-code 0 --source . | 0 | 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-faab73422e7d497dae3f0ea454ef69f4/tree.json --exit-code 0 --source . | 3 | 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 . | 21 | 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 | 11 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| 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) — `packages/easy/src/utils/View.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 |