Executive summary
archimedes-projects/archimedes-js is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because two files are no longer known to anyone active in the project and the project keeps no record of its design decisions. It scores 62 out of 100, which the At risk rating leaves unchanged.
Maturity, at 53, is the weakest lens and counts most in the score. The best first step is recording design decisions, worth about 9 points. Having someone learn and document the two files no active contributor knows comes next, worth about 7 points. Raising Maturity to 70 would lift the score to about 67.
175 known security holes in the packages the code depends on can be used by attackers. Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and one password or key is open to anyone who can read the repository. Updating the vulnerable packages, pinning each tool to an exact version and replacing the exposed password or key would close these risks. The loop of files that import each other needs breaking.
The product code is 2,217 lines, about €5,000 to rebuild.
If Maturity rose from 53 to 70, the lowest score rated Strong, the score would rise from 62 to about 67.
New since the last survey: 65 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 21 findings
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · High vulnerability: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
Rebuild cost: about €5,000 · Estimate
| Cost to rebuild | €1,700 to €8,400, for 28 to 88 hours of work, under 0.1 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.9 at a score of 62. 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: 2,217 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 arch.src.cache.cache | 2 arch.src.notifications.notification | 3 arch.src.notifications.notification-center-options | 4 arch.src.runner.logger | 5 arch.src.use-case.execution-options | 6 components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable | 7 components.src.components.button.button | 8 components.src.utils.position | 9 utils.src.datetime.duration | 10 utils.src.extended-error.extended-error | 11 utils.src.http-client.http-client | 12 arch.src.cache.cache-options | 13 arch.src.cache.lru-cache | 14 arch.src.runner.chain-error | 15 arch.src.use-case.use-case | 16 components.src.components.behavioural-components.activable-item.activated-item-handler | 17 components.src.components.behavioural-components.focusable-item.focusable-item | 18 components.src.components.behavioural-components.focusable-item.focused-item-handler | 19 components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler | 20 components.src.utils | 21 utils.src.datetime.datetime | 22 utils.src.observer.subject | 23 arch.src.cache.cache-manager | 24 arch.src.runner.context | 25 arch.src.use-case.command | 26 arch.src.use-case.query | 27 components.src.components.behavioural-components.activable-item.activated-item-listener | 28 components.src.components.behavioural-components.focusable-item.focused-item-listener | 29 components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener | 30 utils.src.observer.observer | 31 arch.src.notifications.notification-center | 32 arch.src.runner.links.link | 33 arch.src.runner.links.base-link | 34 arch.src.runner.links.empty-link | 35 arch.src.runner.runner | 36 arch.src.runner.links.cache-link | 37 arch.src.runner.links.executor-link | 38 arch.src.runner.links.logger-link | 39 arch.src.runner.links.notification-link | 40 arch.src.runner.links.null-link |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 arch.src.cache.cache | ||||||||||||||||||||||||||||||||||||||||
| 2 arch.src.notifications.notification | ||||||||||||||||||||||||||||||||||||||||
| 3 arch.src.notifications.notification-center-options | ||||||||||||||||||||||||||||||||||||||||
| 4 arch.src.runner.logger | ||||||||||||||||||||||||||||||||||||||||
| 5 arch.src.use-case.execution-options | ||||||||||||||||||||||||||||||||||||||||
| 6 components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable | ||||||||||||||||||||||||||||||||||||||||
| 7 components.src.components.button.button | ||||||||||||||||||||||||||||||||||||||||
| 8 components.src.utils.position | ||||||||||||||||||||||||||||||||||||||||
| 9 utils.src.datetime.duration | ||||||||||||||||||||||||||||||||||||||||
| 10 utils.src.extended-error.extended-error | ||||||||||||||||||||||||||||||||||||||||
| 11 utils.src.http-client.http-client | ||||||||||||||||||||||||||||||||||||||||
| 12 arch.src.cache.cache-options | 1 | |||||||||||||||||||||||||||||||||||||||
| 13 arch.src.cache.lru-cache | 2 | |||||||||||||||||||||||||||||||||||||||
| 14 arch.src.runner.chain-error | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 arch.src.use-case.use-case | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 components.src.components.behavioural-components.activable-item.activated-item-handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 17 components.src.components.behavioural-components.focusable-item.focusable-item | 1 | |||||||||||||||||||||||||||||||||||||||
| 18 components.src.components.behavioural-components.focusable-item.focused-item-handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 components.src.utils | 1 | |||||||||||||||||||||||||||||||||||||||
| 21 utils.src.datetime.datetime | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 utils.src.observer.subject | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 arch.src.cache.cache-manager | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 24 arch.src.runner.context | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 25 arch.src.use-case.command | 1 | |||||||||||||||||||||||||||||||||||||||
| 26 arch.src.use-case.query | 1 | |||||||||||||||||||||||||||||||||||||||
| 27 components.src.components.behavioural-components.activable-item.activated-item-listener | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 components.src.components.behavioural-components.focusable-item.focused-item-listener | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 29 components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 utils.src.observer.observer | 1 | |||||||||||||||||||||||||||||||||||||||
| 31 arch.src.notifications.notification-center | 1 | 1 | 1 | 1 | ||||||||||||||||||||||||||||||||||||
| 32 arch.src.runner.links.link | 1 | |||||||||||||||||||||||||||||||||||||||
| 33 arch.src.runner.links.base-link | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 34 arch.src.runner.links.empty-link | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 35 arch.src.runner.runner | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 36 arch.src.runner.links.cache-link | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 arch.src.runner.links.executor-link | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 38 arch.src.runner.links.logger-link | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 39 arch.src.runner.links.notification-link | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 arch.src.runner.links.null-link | 1 | 1 |
12→1 arch.src.cache.cache-options uses arch.src.cache.cache✕
- Connections
- 1 pair of types, where a type in arch.src.cache.cache-options uses a type in arch.src.cache.cache.
- The types involved
packages.arch.src.cache.cache-options.CacheOptions→packages.arch.src.cache.cache.Cache
- Direction
- arch.src.cache.cache-options uses arch.src.cache.cache, so a change to arch.src.cache.cache can break arch.src.cache.cache-options, while a change to arch.src.cache.cache-options can't break arch.src.cache.cache.
- Position
- Below the diagonal: arch.src.cache.cache-options uses a module listed above it, which is the healthy direction.
13→1 arch.src.cache.lru-cache uses arch.src.cache.cache✕
- Connections
- 2 pairs of types, where a type in arch.src.cache.lru-cache uses a type in arch.src.cache.cache.
- The types involved
packages.arch.src.cache.lru-cache.LruCache→packages.arch.src.cache.cache.Cachepackages.arch.src.cache.lru-cache.LruCache→packages.arch.src.cache.cache.CacheResult
- Direction
- arch.src.cache.lru-cache uses arch.src.cache.cache, so a change to arch.src.cache.cache can break arch.src.cache.lru-cache, while a change to arch.src.cache.lru-cache can't break arch.src.cache.cache.
- Position
- Below the diagonal: arch.src.cache.lru-cache uses a module listed above it, which is the healthy direction.
14→10 arch.src.runner.chain-error uses utils.src.extended-error.extended-error✕
- Connections
- 1 pair of types, where a type in arch.src.runner.chain-error uses a type in utils.src.extended-error.extended-error.
- The types involved
packages.arch.src.runner.chain-error.ChainError→packages.utils.src.extended-error.extended-error.ExtendedError
- Direction
- arch.src.runner.chain-error uses utils.src.extended-error.extended-error, so a change to utils.src.extended-error.extended-error can break arch.src.runner.chain-error, while a change to arch.src.runner.chain-error can't break utils.src.extended-error.extended-error.
- Position
- Below the diagonal: arch.src.runner.chain-error uses a module listed above it, which is the healthy direction.
15→5 arch.src.use-case.use-case uses arch.src.use-case.execution-options✕
- Connections
- 1 pair of types, where a type in arch.src.use-case.use-case uses a type in arch.src.use-case.execution-options.
- The types involved
packages.arch.src.use-case.use-case.UseCase→packages.arch.src.use-case.execution-options.ExecutionOptions
- Direction
- arch.src.use-case.use-case uses arch.src.use-case.execution-options, so a change to arch.src.use-case.execution-options can break arch.src.use-case.use-case, while a change to arch.src.use-case.use-case can't break arch.src.use-case.execution-options.
- Position
- Below the diagonal: arch.src.use-case.use-case uses a module listed above it, which is the healthy direction.
16→8 components.src.components.behavioural-components.activable-item.activated-item-handler uses components.src.utils.position✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.activable-item.activated-item-handler uses a type in components.src.utils.position.
- The types involved
packages.components.src.components.behavioural-components.activable-item.activated-item-handler.ActivatedItemHandler→packages.components.src.utils.position.ItemPosition
- Direction
- components.src.components.behavioural-components.activable-item.activated-item-handler uses components.src.utils.position, so a change to components.src.utils.position can break components.src.components.behavioural-components.activable-item.activated-item-handler, while a change to components.src.components.behavioural-components.activable-item.activated-item-handler can't break components.src.utils.position.
- Position
- Below the diagonal: components.src.components.behavioural-components.activable-item.activated-item-handler uses a module listed above it, which is the healthy direction.
17→8 components.src.components.behavioural-components.focusable-item.focusable-item uses components.src.utils.position✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.focusable-item.focusable-item uses a type in components.src.utils.position.
- The types involved
packages.components.src.components.behavioural-components.focusable-item.focusable-item.FocusableItem→packages.components.src.utils.position.ItemPosition
- Direction
- components.src.components.behavioural-components.focusable-item.focusable-item uses components.src.utils.position, so a change to components.src.utils.position can break components.src.components.behavioural-components.focusable-item.focusable-item, while a change to components.src.components.behavioural-components.focusable-item.focusable-item can't break components.src.utils.position.
- Position
- Below the diagonal: components.src.components.behavioural-components.focusable-item.focusable-item uses a module listed above it, which is the healthy direction.
18→8 components.src.components.behavioural-components.focusable-item.focused-item-handler uses components.src.utils.position✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.focusable-item.focused-item-handler uses a type in components.src.utils.position.
- The types involved
packages.components.src.components.behavioural-components.focusable-item.focused-item-handler.FocusedItemHandler→packages.components.src.utils.position.ItemPosition
- Direction
- components.src.components.behavioural-components.focusable-item.focused-item-handler uses components.src.utils.position, so a change to components.src.utils.position can break components.src.components.behavioural-components.focusable-item.focused-item-handler, while a change to components.src.components.behavioural-components.focusable-item.focused-item-handler can't break components.src.utils.position.
- Position
- Below the diagonal: components.src.components.behavioural-components.focusable-item.focused-item-handler uses a module listed above it, which is the healthy direction.
19→6 components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler uses components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler uses a type in components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable.
- The types involved
packages.components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler.KeyboardNavigationHandler→packages.components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable.KeyboardNavigationAction
- Direction
- components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler uses components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable, so a change to components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable can break components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler, while a change to components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler can't break components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable.
- Position
- Below the diagonal: components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler uses a module listed above it, which is the healthy direction.
20→8 components.src.utils uses components.src.utils.position✕
- Connections
- 1 pair of types, where a type in components.src.utils uses a type in components.src.utils.position.
- The types involved
packages.components.src.utils.position→packages.components.src.utils.position.ItemPosition
- Direction
- components.src.utils uses components.src.utils.position, so a change to components.src.utils.position can break components.src.utils, while a change to components.src.utils can't break components.src.utils.position.
- Position
- Below the diagonal: components.src.utils uses a module listed above it, which is the healthy direction.
21→9 utils.src.datetime.datetime uses utils.src.datetime.duration✕
- Connections
- 1 pair of types, where a type in utils.src.datetime.datetime uses a type in utils.src.datetime.duration.
- The types involved
packages.utils.src.datetime.datetime.Datetime→packages.utils.src.datetime.duration.Duration
- Direction
- utils.src.datetime.datetime uses utils.src.datetime.duration, so a change to utils.src.datetime.duration can break utils.src.datetime.datetime, while a change to utils.src.datetime.datetime can't break utils.src.datetime.duration.
- Position
- Below the diagonal: utils.src.datetime.datetime uses a module listed above it, which is the healthy direction.
22→30 utils.src.observer.subject uses utils.src.observer.observer part of a loop✕
- Connections
- 1 pair of types, where a type in utils.src.observer.subject uses a type in utils.src.observer.observer.
- The types involved
packages.utils.src.observer.subject.Subject→packages.utils.src.observer.observer.Observer
- Direction
- utils.src.observer.subject uses utils.src.observer.observer, so a change to utils.src.observer.observer can break utils.src.observer.subject, while a change to utils.src.observer.subject can't break utils.src.observer.observer.
- 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.
23→1 arch.src.cache.cache-manager uses arch.src.cache.cache✕
- Connections
- 1 pair of types, where a type in arch.src.cache.cache-manager uses a type in arch.src.cache.cache.
- The types involved
packages.arch.src.cache.cache-manager.CacheManager→packages.arch.src.cache.cache.Cache
- Direction
- arch.src.cache.cache-manager uses arch.src.cache.cache, so a change to arch.src.cache.cache can break arch.src.cache.cache-manager, while a change to arch.src.cache.cache-manager can't break arch.src.cache.cache.
- Position
- Below the diagonal: arch.src.cache.cache-manager uses a module listed above it, which is the healthy direction.
23→12 arch.src.cache.cache-manager uses arch.src.cache.cache-options✕
- Connections
- 1 pair of types, where a type in arch.src.cache.cache-manager uses a type in arch.src.cache.cache-options.
- The types involved
packages.arch.src.cache.cache-manager.CacheManager→packages.arch.src.cache.cache-options.CacheOptions
- Direction
- arch.src.cache.cache-manager uses arch.src.cache.cache-options, so a change to arch.src.cache.cache-options can break arch.src.cache.cache-manager, while a change to arch.src.cache.cache-manager can't break arch.src.cache.cache-options.
- Position
- Below the diagonal: arch.src.cache.cache-manager uses a module listed above it, which is the healthy direction.
24→5 arch.src.runner.context uses arch.src.use-case.execution-options✕
- Connections
- 1 pair of types, where a type in arch.src.runner.context uses a type in arch.src.use-case.execution-options.
- The types involved
packages.arch.src.runner.context.Context→packages.arch.src.use-case.execution-options.ExecutionOptions
- Direction
- arch.src.runner.context uses arch.src.use-case.execution-options, so a change to arch.src.use-case.execution-options can break arch.src.runner.context, while a change to arch.src.runner.context can't break arch.src.use-case.execution-options.
- Position
- Below the diagonal: arch.src.runner.context uses a module listed above it, which is the healthy direction.
24→15 arch.src.runner.context uses arch.src.use-case.use-case✕
- Connections
- 1 pair of types, where a type in arch.src.runner.context uses a type in arch.src.use-case.use-case.
- The types involved
packages.arch.src.runner.context.Context→packages.arch.src.use-case.use-case.UseCase
- Direction
- arch.src.runner.context uses arch.src.use-case.use-case, so a change to arch.src.use-case.use-case can break arch.src.runner.context, while a change to arch.src.runner.context can't break arch.src.use-case.use-case.
- Position
- Below the diagonal: arch.src.runner.context uses a module listed above it, which is the healthy direction.
25→15 arch.src.use-case.command uses arch.src.use-case.use-case✕
- Connections
- 1 pair of types, where a type in arch.src.use-case.command uses a type in arch.src.use-case.use-case.
- The types involved
packages.arch.src.use-case.command.Command→packages.arch.src.use-case.use-case.UseCase
- Direction
- arch.src.use-case.command uses arch.src.use-case.use-case, so a change to arch.src.use-case.use-case can break arch.src.use-case.command, while a change to arch.src.use-case.command can't break arch.src.use-case.use-case.
- Position
- Below the diagonal: arch.src.use-case.command uses a module listed above it, which is the healthy direction.
26→15 arch.src.use-case.query uses arch.src.use-case.use-case✕
- Connections
- 1 pair of types, where a type in arch.src.use-case.query uses a type in arch.src.use-case.use-case.
- The types involved
packages.arch.src.use-case.query.Query→packages.arch.src.use-case.use-case.UseCase
- Direction
- arch.src.use-case.query uses arch.src.use-case.use-case, so a change to arch.src.use-case.use-case can break arch.src.use-case.query, while a change to arch.src.use-case.query can't break arch.src.use-case.use-case.
- Position
- Below the diagonal: arch.src.use-case.query uses a module listed above it, which is the healthy direction.
27→8 components.src.components.behavioural-components.activable-item.activated-item-listener uses components.src.utils.position✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.activable-item.activated-item-listener uses a type in components.src.utils.position.
- The types involved
packages.components.src.components.behavioural-components.activable-item.activated-item-listener.ActivatedItemListener→packages.components.src.utils.position.ItemPosition
- Direction
- components.src.components.behavioural-components.activable-item.activated-item-listener uses components.src.utils.position, so a change to components.src.utils.position can break components.src.components.behavioural-components.activable-item.activated-item-listener, while a change to components.src.components.behavioural-components.activable-item.activated-item-listener can't break components.src.utils.position.
- Position
- Below the diagonal: components.src.components.behavioural-components.activable-item.activated-item-listener uses a module listed above it, which is the healthy direction.
27→16 components.src.components.behavioural-components.activable-item.activated-item-listener uses components.src.components.behavioural-components.activable-item.activated-item-handler✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.activable-item.activated-item-listener uses a type in components.src.components.behavioural-components.activable-item.activated-item-handler.
- The types involved
packages.components.src.components.behavioural-components.activable-item.activated-item-listener.ActivatedItemListener→packages.components.src.components.behavioural-components.activable-item.activated-item-handler.ActivatedItemHandler
- Direction
- components.src.components.behavioural-components.activable-item.activated-item-listener uses components.src.components.behavioural-components.activable-item.activated-item-handler, so a change to components.src.components.behavioural-components.activable-item.activated-item-handler can break components.src.components.behavioural-components.activable-item.activated-item-listener, while a change to components.src.components.behavioural-components.activable-item.activated-item-listener can't break components.src.components.behavioural-components.activable-item.activated-item-handler.
- Position
- Below the diagonal: components.src.components.behavioural-components.activable-item.activated-item-listener uses a module listed above it, which is the healthy direction.
28→8 components.src.components.behavioural-components.focusable-item.focused-item-listener uses components.src.utils.position✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.focusable-item.focused-item-listener uses a type in components.src.utils.position.
- The types involved
packages.components.src.components.behavioural-components.focusable-item.focused-item-listener.FocusedItemListener→packages.components.src.utils.position.ItemPosition
- Direction
- components.src.components.behavioural-components.focusable-item.focused-item-listener uses components.src.utils.position, so a change to components.src.utils.position can break components.src.components.behavioural-components.focusable-item.focused-item-listener, while a change to components.src.components.behavioural-components.focusable-item.focused-item-listener can't break components.src.utils.position.
- Position
- Below the diagonal: components.src.components.behavioural-components.focusable-item.focused-item-listener uses a module listed above it, which is the healthy direction.
28→18 components.src.components.behavioural-components.focusable-item.focused-item-listener uses components.src.components.behavioural-components.focusable-item.focused-item-handler✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.focusable-item.focused-item-listener uses a type in components.src.components.behavioural-components.focusable-item.focused-item-handler.
- The types involved
packages.components.src.components.behavioural-components.focusable-item.focused-item-listener.FocusedItemListener→packages.components.src.components.behavioural-components.focusable-item.focused-item-handler.FocusedItemHandler
- Direction
- components.src.components.behavioural-components.focusable-item.focused-item-listener uses components.src.components.behavioural-components.focusable-item.focused-item-handler, so a change to components.src.components.behavioural-components.focusable-item.focused-item-handler can break components.src.components.behavioural-components.focusable-item.focused-item-listener, while a change to components.src.components.behavioural-components.focusable-item.focused-item-listener can't break components.src.components.behavioural-components.focusable-item.focused-item-handler.
- Position
- Below the diagonal: components.src.components.behavioural-components.focusable-item.focused-item-listener uses a module listed above it, which is the healthy direction.
29→6 components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener uses components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener uses a type in components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable.
- The types involved
packages.components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener.KeyboardNavigationListener→packages.components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable.KeyboardNavigationAction
- Direction
- components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener uses components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable, so a change to components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable can break components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener, while a change to components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener can't break components.src.components.behavioural-components.keyboard-navigable.keyboard-navigable.
- Position
- Below the diagonal: components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener uses a module listed above it, which is the healthy direction.
29→19 components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener uses components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler✕
- Connections
- 1 pair of types, where a type in components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener uses a type in components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler.
- The types involved
packages.components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener.KeyboardNavigationListener→packages.components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler.KeyboardNavigationHandler
- Direction
- components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener uses components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler, so a change to components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler can break components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener, while a change to components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener can't break components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-handler.
- Position
- Below the diagonal: components.src.components.behavioural-components.keyboard-navigable.keyboard-navigation-listener uses a module listed above it, which is the healthy direction.
30→22 utils.src.observer.observer uses utils.src.observer.subject✕
- Connections
- 1 pair of types, where a type in utils.src.observer.observer uses a type in utils.src.observer.subject.
- The types involved
packages.utils.src.observer.observer.Observer→packages.utils.src.observer.subject.Subject
- Direction
- utils.src.observer.observer uses utils.src.observer.subject, so a change to utils.src.observer.subject can break utils.src.observer.observer, while a change to utils.src.observer.observer can't break utils.src.observer.subject.
- Position
- Below the diagonal: utils.src.observer.observer uses a module listed above it, which is the healthy direction.
31→2 arch.src.notifications.notification-center uses arch.src.notifications.notification✕
- Connections
- 1 pair of types, where a type in arch.src.notifications.notification-center uses a type in arch.src.notifications.notification.
- The types involved
packages.arch.src.notifications.notification-center.NotificationCenter→packages.arch.src.notifications.notification.Notification
- Direction
- arch.src.notifications.notification-center uses arch.src.notifications.notification, so a change to arch.src.notifications.notification can break arch.src.notifications.notification-center, while a change to arch.src.notifications.notification-center can't break arch.src.notifications.notification.
- Position
- Below the diagonal: arch.src.notifications.notification-center uses a module listed above it, which is the healthy direction.
31→3 arch.src.notifications.notification-center uses arch.src.notifications.notification-center-options✕
- Connections
- 1 pair of types, where a type in arch.src.notifications.notification-center uses a type in arch.src.notifications.notification-center-options.
- The types involved
packages.arch.src.notifications.notification-center.NotificationCenter→packages.arch.src.notifications.notification-center-options.NotificationCenterOptions
- Direction
- arch.src.notifications.notification-center uses arch.src.notifications.notification-center-options, so a change to arch.src.notifications.notification-center-options can break arch.src.notifications.notification-center, while a change to arch.src.notifications.notification-center can't break arch.src.notifications.notification-center-options.
- Position
- Below the diagonal: arch.src.notifications.notification-center uses a module listed above it, which is the healthy direction.
31→22 arch.src.notifications.notification-center uses utils.src.observer.subject✕
- Connections
- 1 pair of types, where a type in arch.src.notifications.notification-center uses a type in utils.src.observer.subject.
- The types involved
packages.arch.src.notifications.notification-center.NotificationCenter→packages.utils.src.observer.subject.Subject
- Direction
- arch.src.notifications.notification-center uses utils.src.observer.subject, so a change to utils.src.observer.subject can break arch.src.notifications.notification-center, while a change to arch.src.notifications.notification-center can't break utils.src.observer.subject.
- Position
- Below the diagonal: arch.src.notifications.notification-center uses a module listed above it, which is the healthy direction.
31→30 arch.src.notifications.notification-center uses utils.src.observer.observer✕
- Connections
- 1 pair of types, where a type in arch.src.notifications.notification-center uses a type in utils.src.observer.observer.
- The types involved
packages.arch.src.notifications.notification-center.NotificationCenter→packages.utils.src.observer.observer.Observer
- Direction
- arch.src.notifications.notification-center uses utils.src.observer.observer, so a change to utils.src.observer.observer can break arch.src.notifications.notification-center, while a change to arch.src.notifications.notification-center can't break utils.src.observer.observer.
- Position
- Below the diagonal: arch.src.notifications.notification-center uses a module listed above it, which is the healthy direction.
32→24 arch.src.runner.links.link uses arch.src.runner.context✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.link uses a type in arch.src.runner.context.
- The types involved
packages.arch.src.runner.links.link.Link→packages.arch.src.runner.context.Context
- Direction
- arch.src.runner.links.link uses arch.src.runner.context, so a change to arch.src.runner.context can break arch.src.runner.links.link, while a change to arch.src.runner.links.link can't break arch.src.runner.context.
- Position
- Below the diagonal: arch.src.runner.links.link uses a module listed above it, which is the healthy direction.
33→24 arch.src.runner.links.base-link uses arch.src.runner.context✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.base-link uses a type in arch.src.runner.context.
- The types involved
packages.arch.src.runner.links.base-link.BaseLink→packages.arch.src.runner.context.Context
- Direction
- arch.src.runner.links.base-link uses arch.src.runner.context, so a change to arch.src.runner.context can break arch.src.runner.links.base-link, while a change to arch.src.runner.links.base-link can't break arch.src.runner.context.
- Position
- Below the diagonal: arch.src.runner.links.base-link uses a module listed above it, which is the healthy direction.
33→32 arch.src.runner.links.base-link uses arch.src.runner.links.link✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.base-link uses a type in arch.src.runner.links.link.
- The types involved
packages.arch.src.runner.links.base-link.BaseLink→packages.arch.src.runner.links.link.Link
- Direction
- arch.src.runner.links.base-link uses arch.src.runner.links.link, so a change to arch.src.runner.links.link can break arch.src.runner.links.base-link, while a change to arch.src.runner.links.base-link can't break arch.src.runner.links.link.
- Position
- Below the diagonal: arch.src.runner.links.base-link uses a module listed above it, which is the healthy direction.
34→24 arch.src.runner.links.empty-link uses arch.src.runner.context✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.empty-link uses a type in arch.src.runner.context.
- The types involved
packages.arch.src.runner.links.empty-link.EmptyLink→packages.arch.src.runner.context.Context
- Direction
- arch.src.runner.links.empty-link uses arch.src.runner.context, so a change to arch.src.runner.context can break arch.src.runner.links.empty-link, while a change to arch.src.runner.links.empty-link can't break arch.src.runner.context.
- Position
- Below the diagonal: arch.src.runner.links.empty-link uses a module listed above it, which is the healthy direction.
34→32 arch.src.runner.links.empty-link uses arch.src.runner.links.link✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.empty-link uses a type in arch.src.runner.links.link.
- The types involved
packages.arch.src.runner.links.empty-link.EmptyLink→packages.arch.src.runner.links.link.Link
- Direction
- arch.src.runner.links.empty-link uses arch.src.runner.links.link, so a change to arch.src.runner.links.link can break arch.src.runner.links.empty-link, while a change to arch.src.runner.links.empty-link can't break arch.src.runner.links.link.
- Position
- Below the diagonal: arch.src.runner.links.empty-link uses a module listed above it, which is the healthy direction.
35→5 arch.src.runner.runner uses arch.src.use-case.execution-options✕
- Connections
- 1 pair of types, where a type in arch.src.runner.runner uses a type in arch.src.use-case.execution-options.
- The types involved
packages.arch.src.runner.runner.Runner→packages.arch.src.use-case.execution-options.ExecutionOptions
- Direction
- arch.src.runner.runner uses arch.src.use-case.execution-options, so a change to arch.src.use-case.execution-options can break arch.src.runner.runner, while a change to arch.src.runner.runner can't break arch.src.use-case.execution-options.
- Position
- Below the diagonal: arch.src.runner.runner uses a module listed above it, which is the healthy direction.
35→15 arch.src.runner.runner uses arch.src.use-case.use-case✕
- Connections
- 1 pair of types, where a type in arch.src.runner.runner uses a type in arch.src.use-case.use-case.
- The types involved
packages.arch.src.runner.runner.Runner→packages.arch.src.use-case.use-case.UseCase
- Direction
- arch.src.runner.runner uses arch.src.use-case.use-case, so a change to arch.src.use-case.use-case can break arch.src.runner.runner, while a change to arch.src.runner.runner can't break arch.src.use-case.use-case.
- Position
- Below the diagonal: arch.src.runner.runner uses a module listed above it, which is the healthy direction.
35→32 arch.src.runner.runner uses arch.src.runner.links.link✕
- Connections
- 1 pair of types, where a type in arch.src.runner.runner uses a type in arch.src.runner.links.link.
- The types involved
packages.arch.src.runner.runner.Runner→packages.arch.src.runner.links.link.Link
- Direction
- arch.src.runner.runner uses arch.src.runner.links.link, so a change to arch.src.runner.links.link can break arch.src.runner.runner, while a change to arch.src.runner.runner can't break arch.src.runner.links.link.
- Position
- Below the diagonal: arch.src.runner.runner uses a module listed above it, which is the healthy direction.
36→23 arch.src.runner.links.cache-link uses arch.src.cache.cache-manager✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.cache-link uses a type in arch.src.cache.cache-manager.
- The types involved
packages.arch.src.runner.links.cache-link.CacheLink→packages.arch.src.cache.cache-manager.CacheManager
- Direction
- arch.src.runner.links.cache-link uses arch.src.cache.cache-manager, so a change to arch.src.cache.cache-manager can break arch.src.runner.links.cache-link, while a change to arch.src.runner.links.cache-link can't break arch.src.cache.cache-manager.
- Position
- Below the diagonal: arch.src.runner.links.cache-link uses a module listed above it, which is the healthy direction.
36→24 arch.src.runner.links.cache-link uses arch.src.runner.context✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.cache-link uses a type in arch.src.runner.context.
- The types involved
packages.arch.src.runner.links.cache-link.CacheLink→packages.arch.src.runner.context.Context
- Direction
- arch.src.runner.links.cache-link uses arch.src.runner.context, so a change to arch.src.runner.context can break arch.src.runner.links.cache-link, while a change to arch.src.runner.links.cache-link can't break arch.src.runner.context.
- Position
- Below the diagonal: arch.src.runner.links.cache-link uses a module listed above it, which is the healthy direction.
36→33 arch.src.runner.links.cache-link uses arch.src.runner.links.base-link✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.cache-link uses a type in arch.src.runner.links.base-link.
- The types involved
packages.arch.src.runner.links.cache-link.CacheLink→packages.arch.src.runner.links.base-link.BaseLink
- Direction
- arch.src.runner.links.cache-link uses arch.src.runner.links.base-link, so a change to arch.src.runner.links.base-link can break arch.src.runner.links.cache-link, while a change to arch.src.runner.links.cache-link can't break arch.src.runner.links.base-link.
- Position
- Below the diagonal: arch.src.runner.links.cache-link uses a module listed above it, which is the healthy direction.
37→24 arch.src.runner.links.executor-link uses arch.src.runner.context✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.executor-link uses a type in arch.src.runner.context.
- The types involved
packages.arch.src.runner.links.executor-link.ExecutorLink→packages.arch.src.runner.context.Context
- Direction
- arch.src.runner.links.executor-link uses arch.src.runner.context, so a change to arch.src.runner.context can break arch.src.runner.links.executor-link, while a change to arch.src.runner.links.executor-link can't break arch.src.runner.context.
- Position
- Below the diagonal: arch.src.runner.links.executor-link uses a module listed above it, which is the healthy direction.
37→33 arch.src.runner.links.executor-link uses arch.src.runner.links.base-link✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.executor-link uses a type in arch.src.runner.links.base-link.
- The types involved
packages.arch.src.runner.links.executor-link.ExecutorLink→packages.arch.src.runner.links.base-link.BaseLink
- Direction
- arch.src.runner.links.executor-link uses arch.src.runner.links.base-link, so a change to arch.src.runner.links.base-link can break arch.src.runner.links.executor-link, while a change to arch.src.runner.links.executor-link can't break arch.src.runner.links.base-link.
- Position
- Below the diagonal: arch.src.runner.links.executor-link uses a module listed above it, which is the healthy direction.
38→4 arch.src.runner.links.logger-link uses arch.src.runner.logger✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.logger-link uses a type in arch.src.runner.logger.
- The types involved
packages.arch.src.runner.links.logger-link.LoggerLink→packages.arch.src.runner.logger.Logger
- Direction
- arch.src.runner.links.logger-link uses arch.src.runner.logger, so a change to arch.src.runner.logger can break arch.src.runner.links.logger-link, while a change to arch.src.runner.links.logger-link can't break arch.src.runner.logger.
- Position
- Below the diagonal: arch.src.runner.links.logger-link uses a module listed above it, which is the healthy direction.
38→24 arch.src.runner.links.logger-link uses arch.src.runner.context✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.logger-link uses a type in arch.src.runner.context.
- The types involved
packages.arch.src.runner.links.logger-link.LoggerLink→packages.arch.src.runner.context.Context
- Direction
- arch.src.runner.links.logger-link uses arch.src.runner.context, so a change to arch.src.runner.context can break arch.src.runner.links.logger-link, while a change to arch.src.runner.links.logger-link can't break arch.src.runner.context.
- Position
- Below the diagonal: arch.src.runner.links.logger-link uses a module listed above it, which is the healthy direction.
38→33 arch.src.runner.links.logger-link uses arch.src.runner.links.base-link✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.logger-link uses a type in arch.src.runner.links.base-link.
- The types involved
packages.arch.src.runner.links.logger-link.LoggerLink→packages.arch.src.runner.links.base-link.BaseLink
- Direction
- arch.src.runner.links.logger-link uses arch.src.runner.links.base-link, so a change to arch.src.runner.links.base-link can break arch.src.runner.links.logger-link, while a change to arch.src.runner.links.logger-link can't break arch.src.runner.links.base-link.
- Position
- Below the diagonal: arch.src.runner.links.logger-link uses a module listed above it, which is the healthy direction.
39→24 arch.src.runner.links.notification-link uses arch.src.runner.context✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.notification-link uses a type in arch.src.runner.context.
- The types involved
packages.arch.src.runner.links.notification-link.NotificationLink→packages.arch.src.runner.context.Context
- Direction
- arch.src.runner.links.notification-link uses arch.src.runner.context, so a change to arch.src.runner.context can break arch.src.runner.links.notification-link, while a change to arch.src.runner.links.notification-link can't break arch.src.runner.context.
- Position
- Below the diagonal: arch.src.runner.links.notification-link uses a module listed above it, which is the healthy direction.
39→31 arch.src.runner.links.notification-link uses arch.src.notifications.notification-center✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.notification-link uses a type in arch.src.notifications.notification-center.
- The types involved
packages.arch.src.runner.links.notification-link.NotificationLink→packages.arch.src.notifications.notification-center.NotificationCenter
- Direction
- arch.src.runner.links.notification-link uses arch.src.notifications.notification-center, so a change to arch.src.notifications.notification-center can break arch.src.runner.links.notification-link, while a change to arch.src.runner.links.notification-link can't break arch.src.notifications.notification-center.
- Position
- Below the diagonal: arch.src.runner.links.notification-link uses a module listed above it, which is the healthy direction.
39→33 arch.src.runner.links.notification-link uses arch.src.runner.links.base-link✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.notification-link uses a type in arch.src.runner.links.base-link.
- The types involved
packages.arch.src.runner.links.notification-link.NotificationLink→packages.arch.src.runner.links.base-link.BaseLink
- Direction
- arch.src.runner.links.notification-link uses arch.src.runner.links.base-link, so a change to arch.src.runner.links.base-link can break arch.src.runner.links.notification-link, while a change to arch.src.runner.links.notification-link can't break arch.src.runner.links.base-link.
- Position
- Below the diagonal: arch.src.runner.links.notification-link uses a module listed above it, which is the healthy direction.
40→24 arch.src.runner.links.null-link uses arch.src.runner.context✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.null-link uses a type in arch.src.runner.context.
- The types involved
packages.arch.src.runner.links.null-link.NullLink→packages.arch.src.runner.context.Context
- Direction
- arch.src.runner.links.null-link uses arch.src.runner.context, so a change to arch.src.runner.context can break arch.src.runner.links.null-link, while a change to arch.src.runner.links.null-link can't break arch.src.runner.context.
- Position
- Below the diagonal: arch.src.runner.links.null-link uses a module listed above it, which is the healthy direction.
40→33 arch.src.runner.links.null-link uses arch.src.runner.links.base-link✕
- Connections
- 1 pair of types, where a type in arch.src.runner.links.null-link uses a type in arch.src.runner.links.base-link.
- The types involved
packages.arch.src.runner.links.null-link.NullLink→packages.arch.src.runner.links.base-link.BaseLink
- Direction
- arch.src.runner.links.null-link uses arch.src.runner.links.base-link, so a change to arch.src.runner.links.base-link can break arch.src.runner.links.null-link, while a change to arch.src.runner.links.null-link can't break arch.src.runner.links.base-link.
- Position
- Below the diagonal: arch.src.runner.links.null-link uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 266 | High / Critical |
| A05:2025 — Injection | 11 | High / Critical |
| A07:2025 — Authentication Failures | 2 | High / Critical |
Roadmap
Top priorities: Resolve the 1 No ADRs found finding(s) in ADR Quality; Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with datetime.ts, http-client.ts; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 No ADRs found finding(s) in ADR Quality. | +8.5 pts | Low | ADR Quality |
| Resolve the 2 Orphaned file finding(s) in Knowledge Freshness — start with datetime.ts, http-client.ts. | +7.4 pts | Low | Knowledge Freshness |
| Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. | +5.1 pts | Low | Knowledge Freshness |
| 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. | +6.6 pts | Medium | Architecture documentation |
| Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing. | +3.8 pts | Medium | Security & performance tooling |
| Resolve the 14 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (14). | +3.6 pts | Medium | Dependency Hygiene |
| Resolve the 15 No assertions finding(s) in Test Quality — start with cache-link.spec.ts (7), cache-manager.spec.ts (3), executor-link.spec.ts (2). | +2.3 pts | Medium | Test Quality |
| Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). | +1.0 pts | Low | Dependency Hygiene |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 1.0 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.0 | Slop | Static Analysis (SAST): High: REDACTED |
| packages/arch/src/runner/links/cache-link.spec.ts | 7.0 | Mixed | Test Quality: No assertions: should not use the cache when cache manager has not this execution registered |
| REDACTED | 7.2 | Mixed | Secrets (history): REDACTED: REDACTED |
| packages/arch/src/cache/cache-manager.spec.ts | 7.4 | Mixed | Test Quality: No assertions: should delete cache if ttl has passed |
| packages/arch/src/runner/links/executor-link.spec.ts | 7.8 | Mixed | Test Quality: No assertions: should execute |
| packages/arch/src/runner/links/notification-link.spec.ts | 7.8 | Mixed | Test Quality: No assertions: should call next link |
| .nvmrc | 7.9 | Mixed | Platform End-of-Life: End-of-life runtime: Node.js 17 |
| packages/arch/src/runner/runner.spec.ts | 8.5 | Near-clean | Test Quality: No assertions: should run the runner |
| package.json | 8.5 | Near-clean | Dependency Hygiene: Deprecated: rimraf |
| packages/components/package.json | 8.5 | Near-clean | Dependency Hygiene: Deprecated: puppeteer |
| examples/with-angular/package.json | 9.0 | Near-clean | Dependency Hygiene: Outdated (npm): @angular/animations |
| examples/with-react/package.json | 9.1 | Near-clean | Dependency Hygiene: Outdated (npm): @testing-library/react |
| packages/arch/package.json | 9.5 | Near-clean | Dependency Hygiene: Outdated (npm): tiny-lru |
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 74 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 — 74 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, 329 of 365 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
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 2 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 2 of the 78 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
- 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.
- 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.
- AX1 Captive dependencies — 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 Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is tsyringe, whose lifetimes are not modelled yet, 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.
- AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (start). the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
- P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP log through no library that carries a message's values as fields (pino, winston, bunyan, tslog, LogTape, roarr; Python's logging, structlog; PHP's PSR-3 loggers), so its log calls cannot be judged, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
- 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.
- 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
0 god class(es) detected.
D5 · Coupling
3 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 17 classes have LCOM4 above 3.
D9 · Test Distribution
115 test methods: 115 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 115 `it`/`test` case(s) across 19 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 15 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 115 tests.
What to do
- Resolve the 15 No assertions finding(s) in Test Quality — start with cache-link.spec.ts (7), cache-manager.spec.ts (3), executor-link.spec.ts (2). — One of this dimension's main actionable groups (15 warning-level).
- Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D12 · Dependency Hygiene
31 outdated direct production npm dependency(ies) of 32 graded, 0 pinning defect(s), across 6 package.json (4 of them the product) and 3 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 2 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.
What to do
- Resolve the 14 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (14). — One of this dimension's main actionable groups (14 recommendation-level).
- Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 recommendation-level).
- Resolve the 2 Deprecated finding(s) in Dependency Hygiene — start with package.json (2). — One of this dimension's main actionable groups (2 warning-level).
- Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
D13 · REDACTED Scanning
REDACTED scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1297 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1297 package(s) this repository's committed lockfile installs for a consumer — its 32 production, optional and peer dependency(ies), across 4 product package.json manifest(s), and everything those install in turn. Its 46 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under Apache-2.0, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 2170 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. 5 document(s) read across 4 unit(s).
D20 · ADR Quality
No architecture decision records were found.
What to do
- Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).
D23 · Boundary Type-Coupling
No domain types leak across context boundaries (5 contexts). Contexts: arch, components, utils, with-angular, with-react.
D26 · Project Cohesion
0 of 3 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
41 % of calls cross a namespace and 24 % go through an interface, but 87 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Improve Navigability — currently 8.5/10. — 41 % of calls cross a namespace and 24 % go through an interface, but 87 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
D29 · Static Analysis (SAST)
11 finding(s): 0 critical, 6 high, 5 medium, 0 low. 6 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.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
- Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
259 finding(s): 40 critical, 135 high, 59 medium, 25 low.
What to do
- Resolve the 132 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (132). — One of this dimension's main actionable groups (132 issue-level).
- Resolve the 38 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (38). — One of this dimension's main actionable groups (38 issue-level).
- Resolve the 3 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
D34 · Knowledge Freshness
2 of 2 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/utils/src/datetime/datetime.ts. Counted over 2 of the 78 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 Orphaned file finding(s) in Knowledge Freshness — start with datetime.ts, http-client.ts. — One of this dimension's main actionable groups (2 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
- 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. — One of this dimension's main actionable groups (1 recommendation-level).
D43 · Malicious Dependencies
No dependency in any ecosystem this repository declares is published as malicious.
D44 · Platform End-of-Life
1 end-of-life runtime(s) and 0 end-of-life framework(s), read from 2 platform declaration(s) and 1 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
What to do
- Resolve the 1 End-of-life runtime finding(s) in Platform End-of-Life — start with .nvmrc. — One of this dimension's main actionable groups (1 warning-level).
Frontend & cross-cutting dimensions
AX10 · Code composition
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
AX5 · Architecture & structure
AX6 · Interface segregation
DM6 · Domain ↔ infrastructure boundary
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. — packages/arch/src/runner/links/notification-link.spec.ts:8
What to do
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
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.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 1571 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:27
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
R2 · Cyclomatic Complexity
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×11) — packages/components/src/components/swiper/swiper.tsx:1, packages/components/src/components/behavioural-components/keyboard-navigable/keyboard-navigation-listener.tsx:1, packages/components/src/components/behavioural-components/activable-item/activable-item.tsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R5 · Dependency Freshness
What to do
- Bump outdated dependencies to current versions to limit upgrade debt.
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 eslint as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 4 application, 6 tooling and 30 test entry point(s) detected in this repo. Gate removals on `npm run compile` — an undetected custom entry would make these reachable.
- no import path from any entry point (4 application, 6 tooling, 30 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×2) — packages/components/src/components/button/button.tsx, packages/components/src/components/toast/toast.tsx
- no import path from any entry point (4 application, 6 tooling, 30 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/components/src/components/button/button.tsx) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/components/src/utils/theme.ts
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- 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. (×2)
- Declared in packages/arch/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
- packages/arch/src/runner/context.ts → packages/arch/src/use-case/use-case.ts → packages/arch/src/runner/runner.ts → packages/arch/src/runner/context.ts (one verified cycle inside a mutually-dependent group of 6 files) — packages/arch/src/runner/context.ts:1
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture
- MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`createHash("sha256")`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — packages/arch/src/cache/cache-manager.ts:63
What to do
- Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X2 · Cancellation propagation
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
- ~6.6 `!` null assertions per 1k TypeScript source lines — 12 assertion(s) across the 1828 source line(s) of the 72 TypeScript file(s) read, which is the only code the operator asserts anything in (a `!` in a `.js` file is not this operator and was not counted, and one in a file whose null checking is off silences nothing). Densest: packages/arch/src/cache/cache-manager.ts (2), packages/components/src/components/behavioural-components/focusable-item/focusable-item.tsx (2), packages/components/src/components/swiper/swiper.tsx (2). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 92% | Exemplary | Solid. |
| Architecture | 91% | Exemplary | Solid. |
| Maturity | 53% | Adequate — gated by D34, M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 58% | Adequate — gated by P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 67% | Adequate — gated by D36 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Domain Modelling | 100% | Exemplary | Strongest area. |
| Performance | 100% | Exemplary | Solid. |
Not evidenced — 2 control(s) we could not find positive evidence for
- 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 — 64 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AC7 A11y enforcement — Frontend below the scale floor (16 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — 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
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXR1 Runtime accessibility — the dev server (`npm run start`) exited before it served a page. Likely cause (the repository): package.json has no "start" script, so `npm run start` could not start the app. Last output: "npm error Missing script: "start" / npm error / npm error Did you mean one of these? / npm error npm star # Mark your favorite packages / npm error npm stars # View packages marked as favorites / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — Test reliability NOT MEASURED: the JavaScript/TypeScript suite's dependency install refused the committed lockfile, so no test ever ran and flakiness could not be exercised — the dependency install for the repository root refused the committed lockfile (npm error code EUSAGE), so the suite never ran. It is excluded from the score rather than counted as a defect; a lockfile in sync with package.json is what lets the suite be re-run.
- D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D24 Comment Value — Too few judgeable comments (2 of at least 30); comment value is not applicable here.
- 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) — 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.
- 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
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the dependency install for the repository root refused the committed lockfile (npm error code EUSAGE), so the suite never ran. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Aggregate boundaries — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM10 One transaction, one aggregate — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM2 Strongly-typed ids — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM3 Integration-event coupling — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM4 Rich vs anemic model — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM5 Encapsulated state — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- DM7 Repository granularity — not applicable: no DDD domain layer was detected (no aggregate, entity or value-object structure), so there is no domain model for this card to grade
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — 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'.
- P2 Observability — This repository's JavaScript/TypeScript source (3 module(s), 74 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- 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 — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- 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 — 184 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test suite cannot be installed from its own lockfile: the repository root
- REDACTED
- Import cycle (3 files) packages/arch/src/runner/context.ts:1
Serious — 107 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions: should run the runner packages/arch/src/runner/runner.spec.ts:7
- No assertions: should not use the cache when cache manager has not this execution registered packages/arch/src/runner/links/cache-link.spec.ts:12
- No assertions: should invalidate the cache when 'invalidateCache' flag is true packages/arch/src/runner/links/cache-link.spec.ts:34
- No assertions: should break the link if it is cached packages/arch/src/runner/links/cache-link.spec.ts:56
- No assertions: should not cache commands packages/arch/src/runner/links/cache-link.spec.ts:78
- No assertions: should invalidate using no cache policy packages/arch/src/runner/links/cache-link.spec.ts:98
- No assertions: should invalidate using all cache policy packages/arch/src/runner/links/cache-link.spec.ts:122
- No assertions: should invalidate using all cache policy packages/arch/src/runner/links/cache-link.spec.ts:146
- No assertions: should execute packages/arch/src/runner/links/executor-link.spec.ts:8
- No assertions: should call next link packages/arch/src/runner/links/executor-link.spec.ts:20
- No assertions: should call next link packages/arch/src/runner/links/notification-link.spec.ts:38
- No assertions: should not create a new notification when there is an error an it's configured to inline the error packages/arch/src/runner/links/notification-link.spec.ts:65
- No assertions: should delete cache if ttl has passed packages/arch/src/cache/cache-manager.spec.ts:71
- No assertions: should not delete cache if the ttl has not passed packages/arch/src/cache/cache-manager.spec.ts:90
- No assertions: should use different caches for different keys packages/arch/src/cache/cache-manager.spec.ts:109
- No test reaches this file packages/components/src/components/swiper/swiper.tsx:1
- No test reaches this file packages/components/src/components/behavioural-components/keyboard-navigable/keyboard-navigation-listener.tsx:1
- No test reaches this file packages/components/src/components/behavioural-components/activable-item/activable-item.tsx:1
- No test reaches this file packages/components/src/components/button/button.tsx:1
- No test reaches this file packages/arch/src/runner/links/logger-link.ts:1
- No test reaches this file packages/components/src/components/behavioural-components/activable-item/activated-item-listener.tsx:1
- No test reaches this file packages/components/src/components/behavioural-components/focusable-item/focusable-item.tsx:1
- No test reaches this file packages/components/src/components/behavioural-components/focusable-item/focused-item-listener.tsx:1
- No test reaches this file packages/components/src/components/toast/toast.tsx:1
- No test reaches this file packages/arch/src/cache/invalidate-cache.ts:1
- No test reaches this file packages/arch/src/archimedes.ts:1
- REDACTED
- REDACTED
- REDACTED
- Deprecated: rimraf package.json:46
- Deprecated: puppeteer packages/components/package.json:45
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Test reliability not measured — JavaScript/TypeScript suite install refused the lockfile
- REDACTED
- End-of-life runtime: Node.js 17 .nvmrc:1
- Off the main sequence: @archimedes/utils
- Coverage not measured — JavaScript/TypeScript suite
- No lint script
- Dead file (~38 LoC) packages/components/src/components/button/button.tsx
- Dead file (~21 LoC) packages/components/src/components/toast/toast.tsx
- Dead file (~1 LoC) packages/components/src/utils/theme.ts
- Unused dependency '@parcel/packager-ts'
- Unused dependency '@parcel/transformer-typescript-types'
- Unused dependency '@archimedes/utils'
- Weak hash algorithm packages/arch/src/cache/cache-manager.ts:63
Minor — 57 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Outdated (npm): @angular/animations examples/with-angular/package.json:13
- Outdated (npm): @angular/common examples/with-angular/package.json:14
- Outdated (npm): @angular/compiler examples/with-angular/package.json:15
- Outdated (npm): @angular/core examples/with-angular/package.json:16
- Outdated (npm): @angular/forms examples/with-angular/package.json:17
- Outdated (npm): @angular/platform-browser examples/with-angular/package.json:18
- Outdated (npm): @angular/platform-browser-dynamic examples/with-angular/package.json:19
- Outdated (npm): @angular/router examples/with-angular/package.json:20
- Outdated (npm): @testing-library/react examples/with-react/package.json:8
- Outdated (npm): @types/jest examples/with-react/package.json:10
- Outdated (npm): @types/node examples/with-react/package.json:11
- Outdated (npm): tiny-lru packages/arch/package.json:20
- Outdated (npm): typescript examples/with-angular/package.json:37
- Outdated (npm): web-vitals examples/with-react/package.json:21
- Deprecated: @npmcli/move-file REDACTED:741
- Deprecated: @npmcli/move-file REDACTED:35660
- Deprecated: @npmcli/move-file REDACTED:40209
- Orphaned file packages/utils/src/datetime/datetime.ts:1
- Orphaned file packages/utils/src/http-client/http-client.ts:1
- No ADRs found
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Disabled test packages/arch/src/runner/links/notification-link.spec.ts:8
- No ADRs
- No architecture diagram/doc
- No SAST REDACTED:3
- No dependency-update automation package.json:27
- Null assertions (`!`) reduce the strict null checking score
Minor — 17 finding(s)
- Outdated (npm): @archimedes/arch
- Outdated (npm): @parcel/transformer-typescript-tsc
- Outdated (npm): @testing-library/jest-dom
- Outdated (npm): @testing-library/user-event
- Outdated (npm): @types/luxon
- Outdated (npm): @types/react
- Outdated (npm): @types/react-dom
- Outdated (npm): luxon
- Outdated (npm): react
- Outdated (npm): react-dom
- Outdated (npm): react-router-dom
- Outdated (npm): reflect-metadata
- Outdated (npm): rxjs
- Outdated (npm): ts-md5
- Outdated (npm): tslib
- Outdated (npm): tsyringe
- Outdated (npm): zone.js
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-774006e5e3094e768c25ad954688887c/history.json --exit-code 0 --source . | 10 | 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-774006e5e3094e768c25ad954688887c/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 11 | 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 | 259 | 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. | 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 |