Executive summary
ngxs/store is rated At risk because critical security findings are open, most of them in the packages it uses. Its score is held back because we found no access checks on the code's endpoints or handlers and it has packages with a known security hole. It scores 38 out of 100, which the At risk rating leaves unchanged.
Security and Compliance, at 16, is the weakest lens and counts most in the score. The best first step is adding access checks, worth about 17 points. Fixing the password or key in the code comes next, worth about 5 points. Raising Security and Compliance to 70 would lift the score to about 56.
119 known security holes in the packages the code depends on can be used by attackers. Twenty-nine pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and three passwords or keys in the code's history and one in the code are open to anyone who can read the repository. Replacing each exposed password or key, updating the vulnerable packages and pinning each tool to an exact version would close these risks. Limiting each secret to its own step would fix the three secrets exposed to more of the pipeline than needed, and the two places where the code runs text as code or as a command need a direct call instead. The eight tests that check nothing need to check the result they produce.
The product code is 11,264 lines, about €31,000 to rebuild.
If Security and Compliance rose from 16 to 70, the lowest score rated Strong, the score would rise from 38 to about 56.
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
- Cyclomatic Complexity · Complex function handle (cyclomatic 29, cognitive 70) packages/storage-plugin/src/storage.plugin.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 16, cognitive 28) packages/storage-plugin/src/storage.plugin.ts
- Page structure · Page without a main landmark integration/src/index.html
- Page structure · Page without a main landmark integrations/hello-world-ng22/src/index.html
- Page structure · Page without a main landmark tutorials/create-app/src/templates/ngxs/src/index.html
Fixed since the last survey: 49 findings
- Churn × Complexity Hotspots · Hotspot: packages/storage-plugin/src/storage.plugin.ts packages/storage-plugin/src/storage.plugin.ts
- Churn × Complexity Hotspots · Hotspot: packages/store/src/internal/action-handler-factory.ts packages/store/src/internal/action-handler-factory.ts
- Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: 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 · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: REDACTED REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · High CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: REDACTED REDACTED
- Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
- Cyclomatic Complexity · Complex function handle (cyclomatic 17, cognitive 36) packages/storage-plugin/src/storage.plugin.ts
- Cyclomatic Complexity · Complex function (anonymous) (cyclomatic 13, cognitive 21) packages/storage-plugin/src/storage.plugin.ts
- Test Coverage · No test reaches this file packages/store/schematics/src/utils/common/properties.ts
- Test Coverage · No test reaches this file tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/1-create-action/_solution/src/app/todo/store/todo.actions.ts
- Test Coverage · No test reaches this file tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/2-handle-the-action/_files/src/app/todo/store/todo.actions.ts
- Test Coverage · No test reaches this file integration/src/test-setup.ts
- Test Coverage · No test reaches this file packages/devtools-plugin/test-setup.ts
- Test Coverage · No test reaches this file packages/form-plugin/test-setup.ts
- Test Coverage · No test reaches this file packages/hmr-plugin/test-setup.ts
- Test Coverage · No test reaches this file packages/logger-plugin/test-setup.ts
- Test Coverage · No test reaches this file packages/router-plugin/test-setup.ts
- Test Coverage · No test reaches this file packages/storage-plugin/test-setup.ts
- Test Coverage · No test reaches this file packages/store/test-setup.ts
- Test Coverage · No test reaches this file packages/websocket-plugin/test-setup.ts
- Forms & labels · <input> without a programmatic label tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/todo-list/todo-list.component.html
- Forms & labels · <input> without a programmatic label tutorials/create-app/src/templates/ngxs/src/app/todo/todo-list/todo-list.component.html
Rebuild cost: about €31,000 · Estimate
| Cost to rebuild | €10,000 to €51,000, for 170 to 541 hours of work, about 0.2 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.7 at a score of 38. 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: 11,264 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 integration.src.app.store.todos.todos_model | 2 packages.devtools-plugin.src.symbols | 3 packages.hmr-plugin.src.internal.hmr-storage | 4 packages.logger-plugin.src.symbols | 5 packages.router-plugin.internals.src.symbols | 6 packages.storage-plugin.internals.src.symbols | 7 packages.store.internals.src.custom-rxjs-subjects | 8 packages.store.internals.src.dev-features | 9 packages.store.internals.src.symbols | 10 packages.store.plugins.src.symbols | 11 packages.store.src.selectors.selector-types_util | 12 packages.websocket-plugin.src.symbols | 13 tutorials.create-app.src.templates.ngxs.src.app.todo.types.todo | 14 packages.form-plugin.src.form_plugin | 15 packages.logger-plugin.src.log-writer | 16 packages.storage-plugin.src.storage_plugin | 17 packages.store.internals.src.state-stream | 18 packages.store.src.actions-stream | 19 packages.store.src.internal.internals | 20 packages.store.src.selectors | 21 packages.store.src.store | 22 packages.store.src.symbols | 23 integration.src.app.counter.counter_state | 24 integration.src.app.store.todos.todo.todo_state | 25 integration.src.app.store.todos.todos_state | 26 packages.devtools-plugin.src.devtools_plugin | 27 packages.hmr-plugin.src.internal.hmr-state-context-factory | 28 packages.hmr-plugin.src.symbols | 29 packages.logger-plugin.src.action-logger | 30 packages.logger-plugin.src.logger_plugin | 31 packages.router-plugin.src.router_state | 32 packages.store.internals.testing.src.symbol | 33 packages.store.src.internal.state-factory | 34 packages.store.src.module | 35 packages.store.src.operators | 36 packages.store.src.utils | 37 packages.hmr-plugin.src.internal.hmr-options-builder | 38 packages.router-plugin.src.router_actions | 39 packages.hmr-plugin.src.internal.hmr-lifecycle | 40 packages.hmr-plugin.src.hmr-manager |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 integration.src.app.store.todos.todos_model | ||||||||||||||||||||||||||||||||||||||||
| 2 packages.devtools-plugin.src.symbols | ||||||||||||||||||||||||||||||||||||||||
| 3 packages.hmr-plugin.src.internal.hmr-storage | ||||||||||||||||||||||||||||||||||||||||
| 4 packages.logger-plugin.src.symbols | ||||||||||||||||||||||||||||||||||||||||
| 5 packages.router-plugin.internals.src.symbols | ||||||||||||||||||||||||||||||||||||||||
| 6 packages.storage-plugin.internals.src.symbols | ||||||||||||||||||||||||||||||||||||||||
| 7 packages.store.internals.src.custom-rxjs-subjects | ||||||||||||||||||||||||||||||||||||||||
| 8 packages.store.internals.src.dev-features | ||||||||||||||||||||||||||||||||||||||||
| 9 packages.store.internals.src.symbols | ||||||||||||||||||||||||||||||||||||||||
| 10 packages.store.plugins.src.symbols | ||||||||||||||||||||||||||||||||||||||||
| 11 packages.store.src.selectors.selector-types_util | ||||||||||||||||||||||||||||||||||||||||
| 12 packages.websocket-plugin.src.symbols | ||||||||||||||||||||||||||||||||||||||||
| 13 tutorials.create-app.src.templates.ngxs.src.app.todo.types.todo | ||||||||||||||||||||||||||||||||||||||||
| 14 packages.form-plugin.src.form_plugin | 1 | |||||||||||||||||||||||||||||||||||||||
| 15 packages.logger-plugin.src.log-writer | 1 | |||||||||||||||||||||||||||||||||||||||
| 16 packages.storage-plugin.src.storage_plugin | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 17 packages.store.internals.src.state-stream | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 18 packages.store.src.actions-stream | 1 | |||||||||||||||||||||||||||||||||||||||
| 19 packages.store.src.internal.internals | 1 | |||||||||||||||||||||||||||||||||||||||
| 20 packages.store.src.selectors | 5 | 3 | ||||||||||||||||||||||||||||||||||||||
| 21 packages.store.src.store | 1 | |||||||||||||||||||||||||||||||||||||||
| 22 packages.store.src.symbols | 1 | |||||||||||||||||||||||||||||||||||||||
| 23 integration.src.app.counter.counter_state | 3 | |||||||||||||||||||||||||||||||||||||||
| 24 integration.src.app.store.todos.todo.todo_state | 3 | |||||||||||||||||||||||||||||||||||||||
| 25 integration.src.app.store.todos.todos_state | 2 | 1 | ||||||||||||||||||||||||||||||||||||||
| 26 packages.devtools-plugin.src.devtools_plugin | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 27 packages.hmr-plugin.src.internal.hmr-state-context-factory | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 28 packages.hmr-plugin.src.symbols | 1 | |||||||||||||||||||||||||||||||||||||||
| 29 packages.logger-plugin.src.action-logger | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 30 packages.logger-plugin.src.logger_plugin | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 31 packages.router-plugin.src.router_state | 1 | 2 | ||||||||||||||||||||||||||||||||||||||
| 32 packages.store.internals.testing.src.symbol | 1 | 1 | ||||||||||||||||||||||||||||||||||||||
| 33 packages.store.src.internal.state-factory | 2 | 3 | ||||||||||||||||||||||||||||||||||||||
| 34 packages.store.src.module | 1 | |||||||||||||||||||||||||||||||||||||||
| 35 packages.store.src.operators | 1 | |||||||||||||||||||||||||||||||||||||||
| 36 packages.store.src.utils | 2 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 37 packages.hmr-plugin.src.internal.hmr-options-builder | 1 | |||||||||||||||||||||||||||||||||||||||
| 38 packages.router-plugin.src.router_actions | 6 | |||||||||||||||||||||||||||||||||||||||
| 39 packages.hmr-plugin.src.internal.hmr-lifecycle | 1 | 1 | 1 | |||||||||||||||||||||||||||||||||||||
| 40 packages.hmr-plugin.src.hmr-manager | 1 | 1 | 1 | 1 | 1 |
14→10 packages.form-plugin.src.form_plugin uses packages.store.plugins.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.form-plugin.src.form_plugin uses a type in packages.store.plugins.src.symbols.
- The types involved
packages.form-plugin.src.form_plugin.NgxsFormPlugin→packages.store.plugins.src.symbols.NgxsPlugin
- Direction
- packages.form-plugin.src.form_plugin uses packages.store.plugins.src.symbols, so a change to packages.store.plugins.src.symbols can break packages.form-plugin.src.form_plugin, while a change to packages.form-plugin.src.form_plugin can't break packages.store.plugins.src.symbols.
- Position
- Below the diagonal: packages.form-plugin.src.form_plugin uses a module listed above it, which is the healthy direction.
15→4 packages.logger-plugin.src.log-writer uses packages.logger-plugin.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.logger-plugin.src.log-writer uses a type in packages.logger-plugin.src.symbols.
- The types involved
packages.logger-plugin.src.log-writer.LogWriter→packages.logger-plugin.src.symbols.NgxsLoggerPluginOptions
- Direction
- packages.logger-plugin.src.log-writer uses packages.logger-plugin.src.symbols, so a change to packages.logger-plugin.src.symbols can break packages.logger-plugin.src.log-writer, while a change to packages.logger-plugin.src.log-writer can't break packages.logger-plugin.src.symbols.
- Position
- Below the diagonal: packages.logger-plugin.src.log-writer uses a module listed above it, which is the healthy direction.
16→9 packages.storage-plugin.src.storage_plugin uses packages.store.internals.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.storage-plugin.src.storage_plugin uses a type in packages.store.internals.src.symbols.
- The types involved
packages.storage-plugin.src.storage_plugin.NgxsStoragePlugin→packages.store.internals.src.symbols.ɵPlainObject
- Direction
- packages.storage-plugin.src.storage_plugin uses packages.store.internals.src.symbols, so a change to packages.store.internals.src.symbols can break packages.storage-plugin.src.storage_plugin, while a change to packages.storage-plugin.src.storage_plugin can't break packages.store.internals.src.symbols.
- Position
- Below the diagonal: packages.storage-plugin.src.storage_plugin uses a module listed above it, which is the healthy direction.
16→10 packages.storage-plugin.src.storage_plugin uses packages.store.plugins.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.storage-plugin.src.storage_plugin uses a type in packages.store.plugins.src.symbols.
- The types involved
packages.storage-plugin.src.storage_plugin.NgxsStoragePlugin→packages.store.plugins.src.symbols.NgxsPlugin
- Direction
- packages.storage-plugin.src.storage_plugin uses packages.store.plugins.src.symbols, so a change to packages.store.plugins.src.symbols can break packages.storage-plugin.src.storage_plugin, while a change to packages.storage-plugin.src.storage_plugin can't break packages.store.plugins.src.symbols.
- Position
- Below the diagonal: packages.storage-plugin.src.storage_plugin uses a module listed above it, which is the healthy direction.
17→7 packages.store.internals.src.state-stream uses packages.store.internals.src.custom-rxjs-subjects✕
- Connections
- 1 pair of types, where a type in packages.store.internals.src.state-stream uses a type in packages.store.internals.src.custom-rxjs-subjects.
- The types involved
packages.store.internals.src.state-stream.ɵStateStream→packages.store.internals.src.custom-rxjs-subjects.ɵOrderedBehaviorSubject
- Direction
- packages.store.internals.src.state-stream uses packages.store.internals.src.custom-rxjs-subjects, so a change to packages.store.internals.src.custom-rxjs-subjects can break packages.store.internals.src.state-stream, while a change to packages.store.internals.src.state-stream can't break packages.store.internals.src.custom-rxjs-subjects.
- Position
- Below the diagonal: packages.store.internals.src.state-stream uses a module listed above it, which is the healthy direction.
17→9 packages.store.internals.src.state-stream uses packages.store.internals.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.store.internals.src.state-stream uses a type in packages.store.internals.src.symbols.
- The types involved
packages.store.internals.src.state-stream.ɵStateStream→packages.store.internals.src.symbols.ɵPlainObject
- Direction
- packages.store.internals.src.state-stream uses packages.store.internals.src.symbols, so a change to packages.store.internals.src.symbols can break packages.store.internals.src.state-stream, while a change to packages.store.internals.src.state-stream can't break packages.store.internals.src.symbols.
- Position
- Below the diagonal: packages.store.internals.src.state-stream uses a module listed above it, which is the healthy direction.
18→7 packages.store.src.actions-stream uses packages.store.internals.src.custom-rxjs-subjects✕
- Connections
- 1 pair of types, where a type in packages.store.src.actions-stream uses a type in packages.store.internals.src.custom-rxjs-subjects.
- The types involved
packages.store.src.actions-stream.InternalActions→packages.store.internals.src.custom-rxjs-subjects.ɵOrderedSubject
- Direction
- packages.store.src.actions-stream uses packages.store.internals.src.custom-rxjs-subjects, so a change to packages.store.internals.src.custom-rxjs-subjects can break packages.store.src.actions-stream, while a change to packages.store.src.actions-stream can't break packages.store.internals.src.custom-rxjs-subjects.
- Position
- Below the diagonal: packages.store.src.actions-stream uses a module listed above it, which is the healthy direction.
19→9 packages.store.src.internal.internals uses packages.store.internals.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.store.src.internal.internals uses a type in packages.store.internals.src.symbols.
- The types involved
packages.store.src.internal.internals.MappedStore→packages.store.internals.src.symbols.ɵPlainObjectOf
- Direction
- packages.store.src.internal.internals uses packages.store.internals.src.symbols, so a change to packages.store.internals.src.symbols can break packages.store.src.internal.internals, while a change to packages.store.src.internal.internals can't break packages.store.internals.src.symbols.
- Position
- Below the diagonal: packages.store.src.internal.internals uses a module listed above it, which is the healthy direction.
20→9 packages.store.src.selectors uses packages.store.internals.src.symbols✕
- Connections
- 5 pairs of types, where a type in packages.store.src.selectors uses a type in packages.store.internals.src.symbols.
- The types involved
packages.store.src.selectors.selector-metadata→packages.store.internals.src.symbols.ɵSelectorMetaDataModelpackages.store.src.selectors.selector-metadata→packages.store.internals.src.symbols.ɵSharedSelectorOptionspackages.store.src.selectors.selector-utils→packages.store.internals.src.symbols.ɵRuntimeSelectorContextpackages.store.src.selectors.selector-utils→packages.store.internals.src.symbols.ɵSelectorMetaDataModelpackages.store.src.selectors.selector-utils→packages.store.internals.src.symbols.ɵSharedSelectorOptions
- Direction
- packages.store.src.selectors uses packages.store.internals.src.symbols, so a change to packages.store.internals.src.symbols can break packages.store.src.selectors, while a change to packages.store.src.selectors can't break packages.store.internals.src.symbols.
- Position
- Below the diagonal: packages.store.src.selectors uses a module listed above it, which is the healthy direction.
20→11 packages.store.src.selectors uses packages.store.src.selectors.selector-types_util✕
- Connections
- 3 pairs of types, where a type in packages.store.src.selectors uses a type in packages.store.src.selectors.selector-types_util.
- The types involved
packages.store.src.selectors.create-pick-selector→packages.store.src.selectors.selector-types_util.TypedSelectorpackages.store.src.selectors.create-property-selectors→packages.store.src.selectors.selector-types_util.ɵSelectorDefpackages.store.src.selectors.selector-checks.util→packages.store.src.selectors.selector-types_util.ɵSelectorDef
- Direction
- packages.store.src.selectors uses packages.store.src.selectors.selector-types_util, so a change to packages.store.src.selectors.selector-types_util can break packages.store.src.selectors, while a change to packages.store.src.selectors can't break packages.store.src.selectors.selector-types_util.
- Position
- Below the diagonal: packages.store.src.selectors uses a module listed above it, which is the healthy direction.
21→11 packages.store.src.store uses packages.store.src.selectors.selector-types_util✕
- Connections
- 1 pair of types, where a type in packages.store.src.store uses a type in packages.store.src.selectors.selector-types_util.
- The types involved
packages.store.src.store.Store→packages.store.src.selectors.selector-types_util.TypedSelector
- Direction
- packages.store.src.store uses packages.store.src.selectors.selector-types_util, so a change to packages.store.src.selectors.selector-types_util can break packages.store.src.store, while a change to packages.store.src.store can't break packages.store.src.selectors.selector-types_util.
- Position
- Below the diagonal: packages.store.src.store uses a module listed above it, which is the healthy direction.
22→9 packages.store.src.symbols uses packages.store.internals.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.store.src.symbols uses a type in packages.store.internals.src.symbols.
- The types involved
packages.store.src.symbols.NgxsConfig→packages.store.internals.src.symbols.ɵSharedSelectorOptions
- Direction
- packages.store.src.symbols uses packages.store.internals.src.symbols, so a change to packages.store.internals.src.symbols can break packages.store.src.symbols, while a change to packages.store.src.symbols can't break packages.store.internals.src.symbols.
- Position
- Below the diagonal: packages.store.src.symbols uses a module listed above it, which is the healthy direction.
23→22 integration.src.app.counter.counter_state uses packages.store.src.symbols✕
- Connections
- 3 pairs of types, where a type in integration.src.app.counter.counter_state uses a type in packages.store.src.symbols.
- The types involved
integration.src.app.counter.counter_state.CounterState→packages.store.src.symbols.NgxsAfterBootstrapintegration.src.app.counter.counter_state.CounterState→packages.store.src.symbols.NgxsOnInitintegration.src.app.counter.counter_state.CounterState→packages.store.src.symbols.StateContext
- Direction
- integration.src.app.counter.counter_state uses packages.store.src.symbols, so a change to packages.store.src.symbols can break integration.src.app.counter.counter_state, while a change to integration.src.app.counter.counter_state can't break packages.store.src.symbols.
- Position
- Below the diagonal: integration.src.app.counter.counter_state uses a module listed above it, which is the healthy direction.
24→22 integration.src.app.store.todos.todo.todo_state uses packages.store.src.symbols✕
- Connections
- 3 pairs of types, where a type in integration.src.app.store.todos.todo.todo_state uses a type in packages.store.src.symbols.
- The types involved
integration.src.app.store.todos.todo.todo_state.TodoState→packages.store.src.symbols.NgxsAfterBootstrapintegration.src.app.store.todos.todo.todo_state.TodoState→packages.store.src.symbols.NgxsOnInitintegration.src.app.store.todos.todo.todo_state.TodoState→packages.store.src.symbols.StateContext
- Direction
- integration.src.app.store.todos.todo.todo_state uses packages.store.src.symbols, so a change to packages.store.src.symbols can break integration.src.app.store.todos.todo.todo_state, while a change to integration.src.app.store.todos.todo.todo_state can't break packages.store.src.symbols.
- Position
- Below the diagonal: integration.src.app.store.todos.todo.todo_state uses a module listed above it, which is the healthy direction.
25→1 integration.src.app.store.todos.todos_state uses integration.src.app.store.todos.todos_model✕
- Connections
- 2 pairs of types, where a type in integration.src.app.store.todos.todos_state uses a type in integration.src.app.store.todos.todos_model.
- The types involved
integration.src.app.store.todos.todos_state.TodosState→integration.src.app.store.todos.todos_model.Pizzaintegration.src.app.store.todos.todos_state.TodosState→integration.src.app.store.todos.todos_model.TodoStateModel
- Direction
- integration.src.app.store.todos.todos_state uses integration.src.app.store.todos.todos_model, so a change to integration.src.app.store.todos.todos_model can break integration.src.app.store.todos.todos_state, while a change to integration.src.app.store.todos.todos_state can't break integration.src.app.store.todos.todos_model.
- Position
- Below the diagonal: integration.src.app.store.todos.todos_state uses a module listed above it, which is the healthy direction.
25→22 integration.src.app.store.todos.todos_state uses packages.store.src.symbols✕
- Connections
- 1 pair of types, where a type in integration.src.app.store.todos.todos_state uses a type in packages.store.src.symbols.
- The types involved
integration.src.app.store.todos.todos_state.TodosState→packages.store.src.symbols.StateContext
- Direction
- integration.src.app.store.todos.todos_state uses packages.store.src.symbols, so a change to packages.store.src.symbols can break integration.src.app.store.todos.todos_state, while a change to integration.src.app.store.todos.todos_state can't break packages.store.src.symbols.
- Position
- Below the diagonal: integration.src.app.store.todos.todos_state uses a module listed above it, which is the healthy direction.
26→2 packages.devtools-plugin.src.devtools_plugin uses packages.devtools-plugin.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.devtools-plugin.src.devtools_plugin uses a type in packages.devtools-plugin.src.symbols.
- The types involved
packages.devtools-plugin.src.devtools_plugin.NgxsReduxDevtoolsPlugin→packages.devtools-plugin.src.symbols.NgxsDevtoolsAction
- Direction
- packages.devtools-plugin.src.devtools_plugin uses packages.devtools-plugin.src.symbols, so a change to packages.devtools-plugin.src.symbols can break packages.devtools-plugin.src.devtools_plugin, while a change to packages.devtools-plugin.src.devtools_plugin can't break packages.devtools-plugin.src.symbols.
- Position
- Below the diagonal: packages.devtools-plugin.src.devtools_plugin uses a module listed above it, which is the healthy direction.
26→10 packages.devtools-plugin.src.devtools_plugin uses packages.store.plugins.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.devtools-plugin.src.devtools_plugin uses a type in packages.store.plugins.src.symbols.
- The types involved
packages.devtools-plugin.src.devtools_plugin.NgxsReduxDevtoolsPlugin→packages.store.plugins.src.symbols.NgxsPlugin
- Direction
- packages.devtools-plugin.src.devtools_plugin uses packages.store.plugins.src.symbols, so a change to packages.store.plugins.src.symbols can break packages.devtools-plugin.src.devtools_plugin, while a change to packages.devtools-plugin.src.devtools_plugin can't break packages.store.plugins.src.symbols.
- Position
- Below the diagonal: packages.devtools-plugin.src.devtools_plugin uses a module listed above it, which is the healthy direction.
26→21 packages.devtools-plugin.src.devtools_plugin uses packages.store.src.store✕
- Connections
- 1 pair of types, where a type in packages.devtools-plugin.src.devtools_plugin uses a type in packages.store.src.store.
- The types involved
packages.devtools-plugin.src.devtools_plugin.NgxsReduxDevtoolsPlugin→packages.store.src.store.Store
- Direction
- packages.devtools-plugin.src.devtools_plugin uses packages.store.src.store, so a change to packages.store.src.store can break packages.devtools-plugin.src.devtools_plugin, while a change to packages.devtools-plugin.src.devtools_plugin can't break packages.store.src.store.
- Position
- Below the diagonal: packages.devtools-plugin.src.devtools_plugin uses a module listed above it, which is the healthy direction.
27→21 packages.hmr-plugin.src.internal.hmr-state-context-factory uses packages.store.src.store✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.internal.hmr-state-context-factory uses a type in packages.store.src.store.
- The types involved
packages.hmr-plugin.src.internal.hmr-state-context-factory.HmrStateContextFactory→packages.store.src.store.Store
- Direction
- packages.hmr-plugin.src.internal.hmr-state-context-factory uses packages.store.src.store, so a change to packages.store.src.store can break packages.hmr-plugin.src.internal.hmr-state-context-factory, while a change to packages.hmr-plugin.src.internal.hmr-state-context-factory can't break packages.store.src.store.
- Position
- Below the diagonal: packages.hmr-plugin.src.internal.hmr-state-context-factory uses a module listed above it, which is the healthy direction.
27→22 packages.hmr-plugin.src.internal.hmr-state-context-factory uses packages.store.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.internal.hmr-state-context-factory uses a type in packages.store.src.symbols.
- The types involved
packages.hmr-plugin.src.internal.hmr-state-context-factory.HmrStateContextFactory→packages.store.src.symbols.StateContext
- Direction
- packages.hmr-plugin.src.internal.hmr-state-context-factory uses packages.store.src.symbols, so a change to packages.store.src.symbols can break packages.hmr-plugin.src.internal.hmr-state-context-factory, while a change to packages.hmr-plugin.src.internal.hmr-state-context-factory can't break packages.store.src.symbols.
- Position
- Below the diagonal: packages.hmr-plugin.src.internal.hmr-state-context-factory uses a module listed above it, which is the healthy direction.
28→22 packages.hmr-plugin.src.symbols uses packages.store.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.symbols uses a type in packages.store.src.symbols.
- The types involved
packages.hmr-plugin.src.symbols.NgxsHmrLifeCycle→packages.store.src.symbols.StateContext
- Direction
- packages.hmr-plugin.src.symbols uses packages.store.src.symbols, so a change to packages.store.src.symbols can break packages.hmr-plugin.src.symbols, while a change to packages.hmr-plugin.src.symbols can't break packages.store.src.symbols.
- Position
- Below the diagonal: packages.hmr-plugin.src.symbols uses a module listed above it, which is the healthy direction.
29→15 packages.logger-plugin.src.action-logger uses packages.logger-plugin.src.log-writer✕
- Connections
- 1 pair of types, where a type in packages.logger-plugin.src.action-logger uses a type in packages.logger-plugin.src.log-writer.
- The types involved
packages.logger-plugin.src.action-logger.ActionLogger→packages.logger-plugin.src.log-writer.LogWriter
- Direction
- packages.logger-plugin.src.action-logger uses packages.logger-plugin.src.log-writer, so a change to packages.logger-plugin.src.log-writer can break packages.logger-plugin.src.action-logger, while a change to packages.logger-plugin.src.action-logger can't break packages.logger-plugin.src.log-writer.
- Position
- Below the diagonal: packages.logger-plugin.src.action-logger uses a module listed above it, which is the healthy direction.
29→21 packages.logger-plugin.src.action-logger uses packages.store.src.store✕
- Connections
- 1 pair of types, where a type in packages.logger-plugin.src.action-logger uses a type in packages.store.src.store.
- The types involved
packages.logger-plugin.src.action-logger.ActionLogger→packages.store.src.store.Store
- Direction
- packages.logger-plugin.src.action-logger uses packages.store.src.store, so a change to packages.store.src.store can break packages.logger-plugin.src.action-logger, while a change to packages.logger-plugin.src.action-logger can't break packages.store.src.store.
- Position
- Below the diagonal: packages.logger-plugin.src.action-logger uses a module listed above it, which is the healthy direction.
30→10 packages.logger-plugin.src.logger_plugin uses packages.store.plugins.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.logger-plugin.src.logger_plugin uses a type in packages.store.plugins.src.symbols.
- The types involved
packages.logger-plugin.src.logger_plugin.NgxsLoggerPlugin→packages.store.plugins.src.symbols.NgxsPlugin
- Direction
- packages.logger-plugin.src.logger_plugin uses packages.store.plugins.src.symbols, so a change to packages.store.plugins.src.symbols can break packages.logger-plugin.src.logger_plugin, while a change to packages.logger-plugin.src.logger_plugin can't break packages.store.plugins.src.symbols.
- Position
- Below the diagonal: packages.logger-plugin.src.logger_plugin uses a module listed above it, which is the healthy direction.
30→15 packages.logger-plugin.src.logger_plugin uses packages.logger-plugin.src.log-writer✕
- Connections
- 1 pair of types, where a type in packages.logger-plugin.src.logger_plugin uses a type in packages.logger-plugin.src.log-writer.
- The types involved
packages.logger-plugin.src.logger_plugin.NgxsLoggerPlugin→packages.logger-plugin.src.log-writer.LogWriter
- Direction
- packages.logger-plugin.src.logger_plugin uses packages.logger-plugin.src.log-writer, so a change to packages.logger-plugin.src.log-writer can break packages.logger-plugin.src.logger_plugin, while a change to packages.logger-plugin.src.logger_plugin can't break packages.logger-plugin.src.log-writer.
- Position
- Below the diagonal: packages.logger-plugin.src.logger_plugin uses a module listed above it, which is the healthy direction.
30→21 packages.logger-plugin.src.logger_plugin uses packages.store.src.store✕
- Connections
- 1 pair of types, where a type in packages.logger-plugin.src.logger_plugin uses a type in packages.store.src.store.
- The types involved
packages.logger-plugin.src.logger_plugin.NgxsLoggerPlugin→packages.store.src.store.Store
- Direction
- packages.logger-plugin.src.logger_plugin uses packages.store.src.store, so a change to packages.store.src.store can break packages.logger-plugin.src.logger_plugin, while a change to packages.logger-plugin.src.logger_plugin can't break packages.store.src.store.
- Position
- Below the diagonal: packages.logger-plugin.src.logger_plugin uses a module listed above it, which is the healthy direction.
31→22 packages.router-plugin.src.router_state uses packages.store.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.router-plugin.src.router_state uses a type in packages.store.src.symbols.
- The types involved
packages.router-plugin.src.router_state.RouterState→packages.store.src.symbols.StateContext
- Direction
- packages.router-plugin.src.router_state uses packages.store.src.symbols, so a change to packages.store.src.symbols can break packages.router-plugin.src.router_state, while a change to packages.router-plugin.src.router_state can't break packages.store.src.symbols.
- Position
- Below the diagonal: packages.router-plugin.src.router_state uses a module listed above it, which is the healthy direction.
31→38 packages.router-plugin.src.router_state uses packages.router-plugin.src.router_actions part of a loop✕
- Connections
- 2 pairs of types, where a type in packages.router-plugin.src.router_state uses a type in packages.router-plugin.src.router_actions.
- The types involved
packages.router-plugin.src.router_state.RouterState→packages.router-plugin.src.router_actions.Navigatepackages.router-plugin.src.router_state.RouterState→packages.router-plugin.src.router_actions.RouterAction
- Direction
- packages.router-plugin.src.router_state uses packages.router-plugin.src.router_actions, so a change to packages.router-plugin.src.router_actions can break packages.router-plugin.src.router_state, while a change to packages.router-plugin.src.router_state can't break packages.router-plugin.src.router_actions.
- 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.
32→21 packages.store.internals.testing.src.symbol uses packages.store.src.store✕
- Connections
- 1 pair of types, where a type in packages.store.internals.testing.src.symbol uses a type in packages.store.src.store.
- The types involved
packages.store.internals.testing.src.symbol.NgxsTesting→packages.store.src.store.Store
- Direction
- packages.store.internals.testing.src.symbol uses packages.store.src.store, so a change to packages.store.src.store can break packages.store.internals.testing.src.symbol, while a change to packages.store.internals.testing.src.symbol can't break packages.store.src.store.
- Position
- Below the diagonal: packages.store.internals.testing.src.symbol uses a module listed above it, which is the healthy direction.
32→22 packages.store.internals.testing.src.symbol uses packages.store.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.store.internals.testing.src.symbol uses a type in packages.store.src.symbols.
- The types involved
packages.store.internals.testing.src.symbol.NgxsOptionsTesting→packages.store.src.symbols.NgxsModuleOptions
- Direction
- packages.store.internals.testing.src.symbol uses packages.store.src.symbols, so a change to packages.store.src.symbols can break packages.store.internals.testing.src.symbol, while a change to packages.store.internals.testing.src.symbol can't break packages.store.src.symbols.
- Position
- Below the diagonal: packages.store.internals.testing.src.symbol uses a module listed above it, which is the healthy direction.
33→9 packages.store.src.internal.state-factory uses packages.store.internals.src.symbols✕
- Connections
- 2 pairs of types, where a type in packages.store.src.internal.state-factory uses a type in packages.store.internals.src.symbols.
- The types involved
packages.store.src.internal.state-factory.StateFactory→packages.store.internals.src.symbols.ɵMetaDataModelpackages.store.src.internal.state-factory.StateFactory→packages.store.internals.src.symbols.ɵPlainObjectOf
- Direction
- packages.store.src.internal.state-factory uses packages.store.internals.src.symbols, so a change to packages.store.internals.src.symbols can break packages.store.src.internal.state-factory, while a change to packages.store.src.internal.state-factory can't break packages.store.internals.src.symbols.
- Position
- Below the diagonal: packages.store.src.internal.state-factory uses a module listed above it, which is the healthy direction.
33→19 packages.store.src.internal.state-factory uses packages.store.src.internal.internals✕
- Connections
- 3 pairs of types, where a type in packages.store.src.internal.state-factory uses a type in packages.store.src.internal.internals.
- The types involved
packages.store.src.internal.state-factory.StateFactory→packages.store.src.internal.internals.MappedStorepackages.store.src.internal.state-factory.StateFactory→packages.store.src.internal.internals.StatesAndDefaultspackages.store.src.internal.state-factory.StateFactory→packages.store.src.internal.internals.StatesByName
- Direction
- packages.store.src.internal.state-factory uses packages.store.src.internal.internals, so a change to packages.store.src.internal.internals can break packages.store.src.internal.state-factory, while a change to packages.store.src.internal.state-factory can't break packages.store.src.internal.internals.
- Position
- Below the diagonal: packages.store.src.internal.state-factory uses a module listed above it, which is the healthy direction.
34→22 packages.store.src.module uses packages.store.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.store.src.module uses a type in packages.store.src.symbols.
- The types involved
packages.store.src.module.NgxsModule→packages.store.src.symbols.NgxsModuleOptions
- Direction
- packages.store.src.module uses packages.store.src.symbols, so a change to packages.store.src.symbols can break packages.store.src.module, while a change to packages.store.src.module can't break packages.store.src.symbols.
- Position
- Below the diagonal: packages.store.src.module uses a module listed above it, which is the healthy direction.
35→18 packages.store.src.operators uses packages.store.src.actions-stream✕
- Connections
- 1 pair of types, where a type in packages.store.src.operators uses a type in packages.store.src.actions-stream.
- The types involved
packages.store.src.operators.of-action→packages.store.src.actions-stream.ActionContext
- Direction
- packages.store.src.operators uses packages.store.src.actions-stream, so a change to packages.store.src.actions-stream can break packages.store.src.operators, while a change to packages.store.src.operators can't break packages.store.src.actions-stream.
- Position
- Below the diagonal: packages.store.src.operators uses a module listed above it, which is the healthy direction.
36→9 packages.store.src.utils uses packages.store.internals.src.symbols✕
- Connections
- 2 pairs of types, where a type in packages.store.src.utils uses a type in packages.store.internals.src.symbols.
- The types involved
packages.store.src.utils.dispatch→packages.store.internals.src.symbols.ActionDefpackages.store.src.utils.store-validators→packages.store.internals.src.symbols.ɵStateClassInternal
- Direction
- packages.store.src.utils uses packages.store.internals.src.symbols, so a change to packages.store.internals.src.symbols can break packages.store.src.utils, while a change to packages.store.src.utils can't break packages.store.internals.src.symbols.
- Position
- Below the diagonal: packages.store.src.utils uses a module listed above it, which is the healthy direction.
36→11 packages.store.src.utils uses packages.store.src.selectors.selector-types_util✕
- Connections
- 1 pair of types, where a type in packages.store.src.utils uses a type in packages.store.src.selectors.selector-types_util.
- The types involved
packages.store.src.utils.select→packages.store.src.selectors.selector-types_util.TypedSelector
- Direction
- packages.store.src.utils uses packages.store.src.selectors.selector-types_util, so a change to packages.store.src.selectors.selector-types_util can break packages.store.src.utils, while a change to packages.store.src.utils can't break packages.store.src.selectors.selector-types_util.
- Position
- Below the diagonal: packages.store.src.utils uses a module listed above it, which is the healthy direction.
36→19 packages.store.src.utils uses packages.store.src.internal.internals✕
- Connections
- 1 pair of types, where a type in packages.store.src.utils uses a type in packages.store.src.internal.internals.
- The types involved
packages.store.src.utils.store-validators→packages.store.src.internal.internals.StatesByName
- Direction
- packages.store.src.utils uses packages.store.src.internal.internals, so a change to packages.store.src.internal.internals can break packages.store.src.utils, while a change to packages.store.src.utils can't break packages.store.src.internal.internals.
- Position
- Below the diagonal: packages.store.src.utils uses a module listed above it, which is the healthy direction.
37→28 packages.hmr-plugin.src.internal.hmr-options-builder uses packages.hmr-plugin.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.internal.hmr-options-builder uses a type in packages.hmr-plugin.src.symbols.
- The types involved
packages.hmr-plugin.src.internal.hmr-options-builder.HmrOptionBuilder→packages.hmr-plugin.src.symbols.NgxsHmrOptions
- Direction
- packages.hmr-plugin.src.internal.hmr-options-builder uses packages.hmr-plugin.src.symbols, so a change to packages.hmr-plugin.src.symbols can break packages.hmr-plugin.src.internal.hmr-options-builder, while a change to packages.hmr-plugin.src.internal.hmr-options-builder can't break packages.hmr-plugin.src.symbols.
- Position
- Below the diagonal: packages.hmr-plugin.src.internal.hmr-options-builder uses a module listed above it, which is the healthy direction.
38→31 packages.router-plugin.src.router_actions uses packages.router-plugin.src.router_state✕
- Connections
- 6 pairs of types, where a type in packages.router-plugin.src.router_actions uses a type in packages.router-plugin.src.router_state.
- The types involved
packages.router-plugin.src.router_actions.RouterCancel→packages.router-plugin.src.router_state.RouterTriggerpackages.router-plugin.src.router_actions.RouterDataResolved→packages.router-plugin.src.router_state.RouterTriggerpackages.router-plugin.src.router_actions.RouterError→packages.router-plugin.src.router_state.RouterTriggerpackages.router-plugin.src.router_actions.RouterNavigated→packages.router-plugin.src.router_state.RouterTriggerpackages.router-plugin.src.router_actions.RouterNavigation→packages.router-plugin.src.router_state.RouterTriggerpackages.router-plugin.src.router_actions.RouterRequest→packages.router-plugin.src.router_state.RouterTrigger
- Direction
- packages.router-plugin.src.router_actions uses packages.router-plugin.src.router_state, so a change to packages.router-plugin.src.router_state can break packages.router-plugin.src.router_actions, while a change to packages.router-plugin.src.router_actions can't break packages.router-plugin.src.router_state.
- Position
- Below the diagonal: packages.router-plugin.src.router_actions uses a module listed above it, which is the healthy direction.
39→3 packages.hmr-plugin.src.internal.hmr-lifecycle uses packages.hmr-plugin.src.internal.hmr-storage✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.internal.hmr-lifecycle uses a type in packages.hmr-plugin.src.internal.hmr-storage.
- The types involved
packages.hmr-plugin.src.internal.hmr-lifecycle.HmrLifecycle→packages.hmr-plugin.src.internal.hmr-storage.HmrStorage
- Direction
- packages.hmr-plugin.src.internal.hmr-lifecycle uses packages.hmr-plugin.src.internal.hmr-storage, so a change to packages.hmr-plugin.src.internal.hmr-storage can break packages.hmr-plugin.src.internal.hmr-lifecycle, while a change to packages.hmr-plugin.src.internal.hmr-lifecycle can't break packages.hmr-plugin.src.internal.hmr-storage.
- Position
- Below the diagonal: packages.hmr-plugin.src.internal.hmr-lifecycle uses a module listed above it, which is the healthy direction.
39→27 packages.hmr-plugin.src.internal.hmr-lifecycle uses packages.hmr-plugin.src.internal.hmr-state-context-factory✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.internal.hmr-lifecycle uses a type in packages.hmr-plugin.src.internal.hmr-state-context-factory.
- The types involved
packages.hmr-plugin.src.internal.hmr-lifecycle.HmrLifecycle→packages.hmr-plugin.src.internal.hmr-state-context-factory.HmrStateContextFactory
- Direction
- packages.hmr-plugin.src.internal.hmr-lifecycle uses packages.hmr-plugin.src.internal.hmr-state-context-factory, so a change to packages.hmr-plugin.src.internal.hmr-state-context-factory can break packages.hmr-plugin.src.internal.hmr-lifecycle, while a change to packages.hmr-plugin.src.internal.hmr-lifecycle can't break packages.hmr-plugin.src.internal.hmr-state-context-factory.
- Position
- Below the diagonal: packages.hmr-plugin.src.internal.hmr-lifecycle uses a module listed above it, which is the healthy direction.
39→37 packages.hmr-plugin.src.internal.hmr-lifecycle uses packages.hmr-plugin.src.internal.hmr-options-builder✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.internal.hmr-lifecycle uses a type in packages.hmr-plugin.src.internal.hmr-options-builder.
- The types involved
packages.hmr-plugin.src.internal.hmr-lifecycle.HmrLifecycle→packages.hmr-plugin.src.internal.hmr-options-builder.HmrOptionBuilder
- Direction
- packages.hmr-plugin.src.internal.hmr-lifecycle uses packages.hmr-plugin.src.internal.hmr-options-builder, so a change to packages.hmr-plugin.src.internal.hmr-options-builder can break packages.hmr-plugin.src.internal.hmr-lifecycle, while a change to packages.hmr-plugin.src.internal.hmr-lifecycle can't break packages.hmr-plugin.src.internal.hmr-options-builder.
- Position
- Below the diagonal: packages.hmr-plugin.src.internal.hmr-lifecycle uses a module listed above it, which is the healthy direction.
40→3 packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.internal.hmr-storage✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.hmr-manager uses a type in packages.hmr-plugin.src.internal.hmr-storage.
- The types involved
packages.hmr-plugin.src.hmr-manager.HmrManager→packages.hmr-plugin.src.internal.hmr-storage.HmrStorage
- Direction
- packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.internal.hmr-storage, so a change to packages.hmr-plugin.src.internal.hmr-storage can break packages.hmr-plugin.src.hmr-manager, while a change to packages.hmr-plugin.src.hmr-manager can't break packages.hmr-plugin.src.internal.hmr-storage.
- Position
- Below the diagonal: packages.hmr-plugin.src.hmr-manager uses a module listed above it, which is the healthy direction.
40→27 packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.internal.hmr-state-context-factory✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.hmr-manager uses a type in packages.hmr-plugin.src.internal.hmr-state-context-factory.
- The types involved
packages.hmr-plugin.src.hmr-manager.HmrManager→packages.hmr-plugin.src.internal.hmr-state-context-factory.HmrStateContextFactory
- Direction
- packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.internal.hmr-state-context-factory, so a change to packages.hmr-plugin.src.internal.hmr-state-context-factory can break packages.hmr-plugin.src.hmr-manager, while a change to packages.hmr-plugin.src.hmr-manager can't break packages.hmr-plugin.src.internal.hmr-state-context-factory.
- Position
- Below the diagonal: packages.hmr-plugin.src.hmr-manager uses a module listed above it, which is the healthy direction.
40→28 packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.symbols✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.hmr-manager uses a type in packages.hmr-plugin.src.symbols.
- The types involved
packages.hmr-plugin.src.hmr-manager.HmrManager→packages.hmr-plugin.src.symbols.NgxsHmrOptions
- Direction
- packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.symbols, so a change to packages.hmr-plugin.src.symbols can break packages.hmr-plugin.src.hmr-manager, while a change to packages.hmr-plugin.src.hmr-manager can't break packages.hmr-plugin.src.symbols.
- Position
- Below the diagonal: packages.hmr-plugin.src.hmr-manager uses a module listed above it, which is the healthy direction.
40→37 packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.internal.hmr-options-builder✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.hmr-manager uses a type in packages.hmr-plugin.src.internal.hmr-options-builder.
- The types involved
packages.hmr-plugin.src.hmr-manager.HmrManager→packages.hmr-plugin.src.internal.hmr-options-builder.HmrOptionBuilder
- Direction
- packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.internal.hmr-options-builder, so a change to packages.hmr-plugin.src.internal.hmr-options-builder can break packages.hmr-plugin.src.hmr-manager, while a change to packages.hmr-plugin.src.hmr-manager can't break packages.hmr-plugin.src.internal.hmr-options-builder.
- Position
- Below the diagonal: packages.hmr-plugin.src.hmr-manager uses a module listed above it, which is the healthy direction.
40→39 packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.internal.hmr-lifecycle✕
- Connections
- 1 pair of types, where a type in packages.hmr-plugin.src.hmr-manager uses a type in packages.hmr-plugin.src.internal.hmr-lifecycle.
- The types involved
packages.hmr-plugin.src.hmr-manager.HmrManager→packages.hmr-plugin.src.internal.hmr-lifecycle.HmrLifecycle
- Direction
- packages.hmr-plugin.src.hmr-manager uses packages.hmr-plugin.src.internal.hmr-lifecycle, so a change to packages.hmr-plugin.src.internal.hmr-lifecycle can break packages.hmr-plugin.src.hmr-manager, while a change to packages.hmr-plugin.src.hmr-manager can't break packages.hmr-plugin.src.internal.hmr-lifecycle.
- Position
- Below the diagonal: packages.hmr-plugin.src.hmr-manager 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 — Accessibility
At a glance — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 177 | High / Critical |
| A05:2025 — Injection | 34 | High / Critical |
| A07:2025 — Authentication Failures | 5 | High / Critical |
Roadmap
Top priorities: Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do; Resolve the 104 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (98), REDACTED (6); Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do. | +17.2 pts | Medium | Access Controls |
| Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. | +5.0 pts | Low | REDACTED Scanning |
| Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. | +3.9 pts | Low | Supply-chain Provenance & Signing |
| Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. | +3.2 pts | Low | Static Analysis (SAST) |
| Resolve the 18 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (18). | +4.0 pts | Medium | Dependency Hygiene |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +3.8 pts | Medium | Dependency Hygiene |
| Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. | +1.8 pts | Low | Secrets (history) |
| Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). | +1.8 pts | Low | Secrets (history) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: High CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| REDACTED | 2.3 | Slop | Static Analysis (SAST): High: REDACTED |
| packages/store/types/tests/state-operators.iif.lint.ts | 3.1 | Slop | Test Quality: No assertions (empty test): should return the correct implied null or undefined type |
| REDACTED | 4.4 | Mixed | REDACTED Scanning: Leaked secret: REDACTED |
| packages/store/types/tests/create-selector.lint.ts | 4.5 | Mixed | Test Quality: No assertions (empty test): should be correct detect type with createSelector |
| packages/store/types/tests/state-operators.compose.lint.ts | 5.1 | Mixed | Test Quality: No assertions (empty test): should return the correct array type |
| packages/store/types/tests/selection.lint.ts | 5.2 | Mixed | Test Quality: No assertions (empty test): should be correct passed selectors |
| REDACTED | 5.8 | Mixed | Secrets (history): REDACTED: REDACTED |
| packages/store/tests/dev-mode.spec.ts | 6.0 | Mixed | Explicit Debt: TodoComment |
| packages/store/tests/ensure-store.spec.ts | 6.7 | Mixed | Explicit Debt: TodoComment |
| packages/store/types/tests/action.lint.ts | 7.0 | Mixed | Test Quality: No assertions: ofAction() |
| packages/store/types/tests/selector-options.lint.ts | 7.0 | Mixed | Test Quality: No assertions: should be valid on on State classes |
| packages/store/types/tests/dispatch.lint.ts | 7.1 | Mixed | Test Quality: No assertions: should be correct type in action decorator |
| packages/store/types/tests/state-token.lint.ts | 7.1 | Mixed | Test Quality: No assertions: should successfully create a simple token |
| REDACTED | 7.2 | Mixed | Static Analysis (SAST): High: REDACTED |
How the grades work
A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.
Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.
Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.
Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 76 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 — 76 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, 506 of 534 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
- D11 Test Reliability — 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. Test reliability for the vitest suite in integrations/hello-world-ng22/ was NOT MEASURED: the dependency install for integrations/hello-world-ng22/ failed in the analyzer sandbox (yarn install v1.22.22), so the suite never ran. This is OUR limitation, not a defect in the repository, and the suite is excluded from the measurement rather than counted against it.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's deterministic naming rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. Until then its declarations carry no naming verdict this run — this says nothing about whether its names are consistent.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published REDACTED's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `integration/src/app/counter/counter.state.ts`, `integration/src/app/list/list.state.ts`, `integration/src/app/store/todos/todo/todo.state.ts`, `integration/src/app/store/todos/todos.state.ts`, `integrations/hello-world-ng22/src/app/store/counter/counter.state.ts`, … (+5 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- D44 Platform End-of-Life — not measured this run — 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
- AXB2 Runtime readiness — 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. A program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. (rule: missing-tool). The renderer reported: the dev server (`npm run start`) exited before it served a page. Likely cause (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> ngxs@22.0.0 start / > yarn serve:hmr:integration / sh: 1: yarn: not found" No runtime evidence was gathered.
- 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 (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> ngxs@22.0.0 start / > yarn serve:hmr:integration / sh: 1: yarn: not found" No runtime evidence was gathered.
- 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.
- R4 Test Coverage — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 12 further occurrence(s) are not listed individually; the score already reflects all 52.
- R7 Dead Code — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 28 further occurrence(s) are not listed individually; the score already reflects all 68.
- S1 Web-Security Posture — 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. 252 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP 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.
- D11 Test Reliability: Flakiness is inferred from history/markers — we run the suite once (for coverage), not the repeated runs under varied conditions that reveal nondeterminism, so a flaky test never recorded as failing is invisible here.
- D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
- D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
- D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
- D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
- D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- 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.
- AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
- AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
- AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
- AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
- AC7 A11y enforcement: Enforcement is scored from in-repo config/CI evidence only — an a11y gate enforced in external tooling with no in-repo trace can't be credited, and a configured linter is presence, not proof the rules actually run or block a merge.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
- P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
- 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
2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was NgxsStoragePlugin.handle at 49.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with NgxsStoragePlugin.handle (cyclomatic 49), NgxsFormPlugin.handle (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 8.6 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D2 · Cognitive Complexity
4 method(s) exceeded the cognitive complexity threshold of 15; the worst was NgxsStoragePlugin.handle at 106.
What to do
- Bring the 1 body over 30 down to 30 or less in Cognitive Complexity — start with NgxsStoragePlugin.handle (cognitive 106). — Refactoring it lifts Cognitive Complexity from 7.6 to about 9.0/10.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
0 god class(es) detected.
D5 · Coupling
11 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 27 classes have LCOM4 above 3.
D9 · Test Distribution
828 test methods: 803 unit, 15 integration, 0 BDD, 10 e2e. The JavaScript/TypeScript suite contributes 828 `it`/`test` case(s) across 142 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
5 skipped (2 with a documented reason), 84 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 828 tests.
What to do
- Resolve the 8 No assertions (empty test) finding(s) in Test Quality — start with state-operators.iif.lint.ts (5), create-selector.lint.ts, selection.lint.ts. — One of this dimension's main actionable groups (8 issue-level).
- Resolve the 76 No assertions finding(s) in Test Quality — start with action.lint.ts (12), state-operators.iif.lint.ts (11), selector-options.lint.ts (8). — One of this dimension's main actionable groups (76 warning-level).
- Resolve the 3 Skipped test finding(s) in Test Quality — start with dev-mode.spec.ts (2), ensure-store.spec.ts. — One of this dimension's main actionable groups (3 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.
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (jest via `yarn install --frozen-lockfile --ignore-scripts` in the repository root (705 tests); vitest via `yarn install --frozen-lockfile --ignore-scripts` in integrations/hello-world-ng22/): measured (0 flaky).
D12 · Dependency Hygiene
10 outdated direct production npm dependency(ies) of 18 graded, 0 pinning defect(s), across 5 REDACTED (4 of them the product) and 3 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 3 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 18 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (18). — One of this dimension's main actionable groups (18 recommendation-level).
- Resolve the 3 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (3). — One of this dimension's main actionable groups (3 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
1 secret(s) detected.
What to do
- Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D14 · License Compliance
0 of 67 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 67 package(s) this repository's committed lockfile installs for a consumer — its 18 production, optional and peer dependency(ies), across 4 product REDACTED manifest(s), and everything those install in turn. Its 112 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D16 · Bus Factor
25 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is packages/store/src/internal/state-factory.ts. Counted over 50 of the 280 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 1 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (1 recommendation-level).
D17 · Explicit Debt
4 deducted task-comment markers across 11154 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
What to do
- Resolve the 4 TodoComment finding(s) in Explicit Debt — start with websocket-handler.ts, dev-mode.spec.ts, ensure-store.spec.ts. — One of this dimension's main actionable groups (4 warning-level).
- Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D19 · Documentation Quality
1 of 2 documentation facets pass in full; short on: F2 example. 85 document(s) read across 12 unit(s).
What to do
- Resolve the 9 Documentation finding(s) in Documentation Quality — start with README.md (9). — One of this dimension's main actionable groups (9 recommendation-level).
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).
D24 · Comment Value
3 of 775 judged comments only repeat the code they sit on (0.4 %). 29 comment(s) in another language or script were not judged.
D26 · Project Cohesion
1 of 11 build units (npm) flagged as possibly oversized/incoherent.
What to do
- Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
D28 · Secrets (history)
3 finding(s): 0 critical, 3 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
What to do
- Resolve the 2 REDACTED finding(s) in Secrets (history) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
- Resolve the 1 High secret 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)
34 finding(s): 0 critical, 34 high, 0 medium, 0 low. 29 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 10 file(s) — `integration/src/app/counter/counter.state.ts` (line 17), `integration/src/app/list/list.state.ts` (line 4), `integration/src/app/store/todos/todo/todo.state.ts` (line 14), `integration/src/app/store/todos/todos.state.ts` (line 14), `integrations/hello-world-ng22/src/app/store/counter/counter.state.ts` (line 8), … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 3 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
What to do
- Resolve the 3 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- No action in Static Analysis (SAST) — all 29 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 (29 issue-level, 0 of them charged here).
D30 · Dependency Vulnerabilities
170 finding(s): 14 critical, 105 high, 36 medium, 15 low.
What to do
- Resolve the 104 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (98), REDACTED (6). — One of this dimension's main actionable groups (104 issue-level).
- Resolve the 13 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (13). — One of this dimension's main actionable groups (13 issue-level).
- Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
D34 · Knowledge Freshness
3 of 50 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is packages/store/src/decorators/selector/symbols.ts. Counted over 50 of the 280 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D35 · Change Coupling
Strongest change-coupling: app.component.ts↔list.component.ts 67%
What to do
- Resolve the 1 Change coupling finding(s) in Change Coupling — start with app.component.ts. — One of this dimension's main actionable groups (1 warning-level).
D36 · Supply-chain Provenance & Signing
0/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 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.
Frontend & cross-cutting dimensions
AC2 · Forms & labels
- This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — integration/src/app/app.component.html:13, integration/src/app/app.component.html:14, integration/src/app/app.component.html:17
- This control has only a placeholder — a placeholder is not a label (it vanishes on input and many AT ignore it). Add a <label for>, a wrapping <label>, or aria-label. — integration/src/app/app.component.html:30
What to do
- Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
AC3 · Page structure
- No <main> (or role="main") means no "skip to content" target and a weaker landmark map. This document's body is only the mount point <app-root>, so there is no content here to wrap — render the <main> from the component mounted into it. (×3) — integration/src/index.html:2, integrations/hello-world-ng22/src/index.html:2, tutorials/create-app/src/templates/ngxs/src/index.html:2
What to do
- Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
AC5 · ARIA correctness
AC6 · Visual & motion safety
AC7 · A11y enforcement
- No accessibility enforcement found — no a11y linter (@angular-eslint/eslint-plugin-template (a11y rules)) and no axe/pa11y/Lighthouse in tests or CI. Start with the linter to catch issues at author time. What was searched, so you can tell an absence from a miss: the 12 markup file(s) this pass actually assessed, the linter configuration checked in beside them, and this repository's test and CI files — matched by name against the accessibility checkers this dimension carries. An audit run outside the repository, a hosted scanner, or a check whose name is not one of those, is not seen here. — REDACTED:95
What to do
- Enforce accessibility in the toolchain: add @angular-eslint/eslint-plugin-template (a11y rules), then assert with @axe-core/playwright in tests, then gate axe/pa11y/Lighthouse in CI.
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
C2 · Access Controls
- This repository serves requests — express() (integration/src/server.ts:13) — and no route guard, auth-gate middleware, global guard or imperative check that refuses a caller (401/403, an Unauthorized/Forbidden error) was found: its endpoints may be unprotected. — integration/src/server.ts:13
What to do
- Protect endpoints by default-deny: a global authentication guard or middleware with explicit public opt-outs, or a guard on every route, plus named role/permission rules for what an authenticated caller may do.
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `toggleItem` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. (×3) — tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:76, tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/4-select-query-from-component/_files/src/app/todo/todo-list/todo-list.component.ts:59, tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/4-select-query-from-component/_solution/src/app/todo/todo-list/todo-list.component.ts:54
- `error` has an empty body — confirm it's an intentional no-op and not an unfinished method. — packages/store/src/internal/dispatcher.ts:41
- A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×5) — packages/store/tests/dev-mode.spec.ts:406, packages/store/tests/dev-mode.spec.ts:442, packages/store/tests/ensure-store.spec.ts:165, …
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
- Clear the softer debt: re-enable or delete skipped tests, decide whether each empty function is a deliberate no-op (and say so in a comment), and replace blanket `eslint-disable` / `@ts-nocheck` with targeted, justified suppressions.
M1 · Documentation (README)
- 78 code files changed in the last 6 months but the README was not touched — it may no longer reflect the system.
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
- Add a README to the 3 of 12 project(s) that lack one — worth up to 0.5 pts.
- Review the README against recent changes; refresh the parts that drifted.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure
M4 · Documentation accuracy
P1 · CI/CD gates
P2 · Observability
- Only 3/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `.`.
- `packages/logger-plugin/src/log-writer.ts` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/logger-plugin/src/log-writer.ts:18
- `packages/storage-plugin/src/with-storage-feature.ts` reports through `console.*` at line 19 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/storage-plugin/src/with-storage-feature.ts:19
- `packages/storage-plugin/src/features/with-ngxs-storage-transfer-state.ts` reports through `console.*` at line 103 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/storage-plugin/src/features/with-ngxs-storage-transfer-state.ts:103
- `packages/storage-plugin/src/features/with-ngxs-storage-transfer-state.ts` reports through `console.*` at line 121 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/storage-plugin/src/features/with-ngxs-storage-transfer-state.ts:121
- `packages/store/src/pending-tasks.ts` reports through `console.*` at line 109 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/pending-tasks.ts:109
- `packages/store/src/store.ts` reports through `console.*` at line 136 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/store.ts:136
- `packages/store/src/standalone-features/preboot.ts` reports through `console.*` at line 23 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/standalone-features/preboot.ts:23
- `packages/store/src/selectors/selector-checks.util.ts` reports through `console.*` at line 38 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/selectors/selector-checks.util.ts:38
- `packages/store/src/selectors/selector-types.util.ts` reports through `console.*` at line 24 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/selectors/selector-types.util.ts:24
- `packages/store/src/selectors/selector-utils.ts` reports through `console.*` at line 60 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/selectors/selector-utils.ts:60
- `packages/store/src/ivy/ivy-enabled-in-dev-mode.ts` reports through `console.*` at line 15 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/ivy/ivy-enabled-in-dev-mode.ts:15
- `packages/store/src/ivy/ivy-enabled-in-dev-mode.ts` reports through `console.*` at line 20 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/ivy/ivy-enabled-in-dev-mode.ts:20
- `packages/store/src/internal/action-handler-factory.ts` reports through `console.*` at line 107 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/internal/action-handler-factory.ts:107
- `packages/store/src/internal/lifecycle-state-manager.ts` reports through `console.*` at line 45 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/internal/lifecycle-state-manager.ts:45
- `packages/store/src/internal/state-context-factory.ts` reports through `console.*` at line 161 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/internal/state-context-factory.ts:161
- `packages/store/src/dev-features/ngxs-unhandled-actions-logger.ts` reports through `console.*` at line 46 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/src/dev-features/ngxs-unhandled-actions-logger.ts:46
- `packages/store/schematics/src/_testing/schematics.ts` reports through `console.*` at line 65 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/schematics/src/_testing/schematics.ts:65
- `packages/store/internals/src/action-registry.ts` reports through `console.*` at line 56 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — packages/store/internals/src/action-registry.ts:56
What to do
- Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
- Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
- Consider OpenTelemetry tracing/metrics (@opentelemetry/sdk-node) and a health-check endpoint (@godaddy/terminus or a /health route) for operability.
P3 · Security & performance tooling
- 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 21161 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:8
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.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
What to do
- Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where we can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- 5 duplicated blocks under tutorials/create-app/src/ have copies in at least two of the sibling directories content, templates — 3 of them are reported below, and 2 are counted here but not reported individually: those copies match on shape but no longer clear R10's bar for an individually reported row — either they kept neither their own names nor their values, or what was copied is too small to stand on its own (it reports near-exact duplication only, and only of substantial extent). What this row states is the concentration, which the detector measured over all 5 and which does not depend on how exactly each block's copies still match. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:13
- tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:13 · tutorials/create-app/src/templates/ngxs/src/app/todo/todo-list/todo-list.component.ts:15 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:13
- tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/store/todo.state.ts:7 · tutorials/create-app/src/templates/ngxs/src/app/todo/store/todo.state.ts:8 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/store/todo.state.ts:7
- tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/store/todo.state.ts:2 · tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/2-handle-the-action/_files/src/app/todo/store/todo.state.ts:2 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/store/todo.state.ts:2
- packages/storage-plugin/schematics/src/_testing/schematics.ts:7 · packages/store/schematics/src/_testing/schematics.ts:7 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/storage-plugin/schematics/src/_testing/schematics.ts:7
- packages/devtools-plugin/src/devtools.module.ts:25 · packages/logger-plugin/src/logger.module.ts:32 — the 2 copies are spread across 2 files, and the SHAPE of this repetition could not be determined. It is not a run of declarations, a listing, a declaration header, a type body or a slice through a construct — and it was not measured as a run of executable statements either, so this row cannot tell you whether a function can stand where these lines are. Read the two spans before acting, because the move is opposite in the two cases. Where they are statements, the ordinary answer holds: give the shared part one home and call it from each site. Where they turn out to be declarations, a literal's entries, or the cases of an enumeration, there is no call site to call anything from, and collapsing them would delete what each copy pins — a shared base type, a generated set, or one exported constant each site refers to is the move instead, and sometimes the honest answer is that there is nothing to extract at all. Reported because the copies drift apart the first time only one of them is edited, which is true whichever of those they are. — packages/devtools-plugin/src/devtools.module.ts:25
- tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/todo-list/todo-list.component.ts:15 · tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/4-select-query-from-component/_solution/src/app/todo/todo-list/todo-list.component.ts:15 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/todo-list/todo-list.component.ts:15
- tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:12 · tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/4-select-query-from-component/_files/src/app/todo/todo-list/todo-list.component.ts:14 · tutorials/create-app/src/templates/ngxs/src/app/todo/todo-list/todo-list.component.ts:14 — the 3 copies are spread across 3 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:12
- packages/store/schematics/src/state/state.factory.ts:10 · packages/store/schematics/src/store/store.factory.ts:10 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — packages/store/schematics/src/state/state.factory.ts:10
- packages/form-plugin/src/directive.ts:94 · packages/form-plugin/src/directive.ts:129 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/form-plugin/src/directive.ts:94
- packages/store/operators/src/remove-item.ts:24 · packages/store/operators/src/update-item.ts:40 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/store/operators/src/remove-item.ts:24
- packages/store/operators/src/remove-items.ts:25 · packages/store/operators/src/update-items.ts:32 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/store/operators/src/remove-items.ts:25
- packages/store/src/execution/execution-strategy.ts:2 · packages/store/src/execution/noop-execution-strategy.ts:3 — the two spans are one implementation copied and then locally edited — 51 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — packages/store/src/execution/execution-strategy.ts:2
- packages/store/src/internal/dispatcher.ts:41 · packages/store/src/internal/lifecycle-state-manager.ts:12 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — packages/store/src/internal/dispatcher.ts:41
- packages/store/internals/testing/src/skip-console-logging.ts:13 · packages/store/internals/testing/src/skip-console-logging.ts:19 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — packages/store/internals/testing/src/skip-console-logging.ts:13
What to do
- Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries
- packages/devtools-plugin/test-setup.ts:1 reaches into another package with a relative path (./../../setup-jest-preset) — import the package by name instead. — packages/devtools-plugin/test-setup.ts:1
- packages/form-plugin/test-setup.ts:1 reaches into another package with a relative path (./../../setup-jest-preset) — import the package by name instead. — packages/form-plugin/test-setup.ts:1
- packages/hmr-plugin/test-setup.ts:1 reaches into another package with a relative path (./../../setup-jest-preset) — import the package by name instead. — packages/hmr-plugin/test-setup.ts:1
- packages/logger-plugin/test-setup.ts:1 reaches into another package with a relative path (./../../setup-jest-preset) — import the package by name instead. — packages/logger-plugin/test-setup.ts:1
- packages/router-plugin/test-setup.ts:1 reaches into another package with a relative path (./../../setup-jest-preset) — import the package by name instead. — packages/router-plugin/test-setup.ts:1
- packages/storage-plugin/test-setup.ts:1 reaches into another package with a relative path (./../../setup-jest-preset) — import the package by name instead. — packages/storage-plugin/test-setup.ts:1
- packages/store/test-setup.ts:1 reaches into another package with a relative path (./../../setup-jest-preset) — import the package by name instead. — packages/store/test-setup.ts:1
- packages/websocket-plugin/test-setup.ts:1 reaches into another package with a relative path (./../../setup-jest-preset) — import the package by name instead. — packages/websocket-plugin/test-setup.ts:1
What to do
- Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity
- handle has cyclomatic complexity 29 and cognitive complexity 70; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/storage-plugin/src/storage.plugin.ts:101
- handle has cyclomatic complexity 17 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/form-plugin/src/form.plugin.ts:24
- (anonymous) has cyclomatic complexity 16 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/storage-plugin/src/storage.plugin.ts:231
- (anonymous) has cyclomatic complexity 11 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — packages/router-plugin/src/router.state.ts:208
What to do
- Break down the listed branch-heavy functions; aim P95 cyclomatic ≤ 5.
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. (×40) — packages/store/schematics/src/ng-add/add-declaration.ts:1, packages/storage-plugin/schematics/src/ng-generate/index.ts:1, packages/store/schematics/src/ng-add/ng-add.factory.ts:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
R7 · Dead Code
- 20 file(s) (~573 LoC) were excluded from dead-code analysis — declare main/module/exports or a conventional entry (src/index.*, an index.html script) so reachability can see this package. — tutorials/create-app
- Unreachable from the 18 application, 37 tooling and 172 test entry point(s) detected in this repo. Gate removals on `yarn run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (18 application, 37 tooling, 172 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/store/schematics/src/ng-add/ng-add.factory.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/store/schematics/src/ng-add/add-declaration.ts
- no import path from any entry point (18 application, 37 tooling, 172 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 (×18) — packages/storage-plugin/schematics/src/ng-generate/index.ts, integration/src/server.ts, tools/build-schematics.mjs, …
- no import path from any entry point (18 application, 37 tooling, 172 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/store/schematics/src/ng-add/add-declaration.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/store/schematics/src/ng-add/ng-add.factory.ts
- no import path from any entry point (18 application, 37 tooling, 172 test roots considered), but 4 in-repo import(s) from 4 other file(s) do name it (packages/store/schematics/src/actions/actions.factory.ts, packages/store/schematics/src/starter-kit/starter-kit.factory.ts, packages/store/schematics/src/state/state.factory.ts and 1 more) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/store/schematics/src/utils/generate-utils.ts
- no import path from any entry point (18 application, 37 tooling, 172 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (packages/storage-plugin/schematics/src/ng-generate/index.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/storage-plugin/schematics/src/utils/visit-files.ts
- no import path from any entry point (18 application, 37 tooling, 172 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (packages/store/schematics/src/actions/actions.factory.ts, packages/store/schematics/src/state/state.factory.ts, packages/store/schematics/src/store/store.factory.ts) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — packages/store/schematics/src/utils/common/properties.ts
- Nothing ultimately consumes this binding: its only referrer is the re-export in packages/router-plugin/src/public_api.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/router-plugin/src/public_api.ts in the same commit, or the barrel will import a name that no longer exists. (×3) — packages/router-plugin/src/router-selectors.ts:28, packages/router-plugin/src/router-selectors.ts:52, packages/router-plugin/src/router-selectors.ts:80
- Nothing ultimately consumes this binding: its only referrer is the re-export in packages/store/internals/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/store/internals/src/index.ts in the same commit, or the barrel will import a name that no longer exists. — packages/store/internals/src/symbols.ts:24
- Nothing ultimately consumes this binding: its only referrer is the re-export in packages/store/plugins/src/index.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/store/plugins/src/index.ts in the same commit, or the barrel will import a name that no longer exists. — packages/store/plugins/src/utils.ts:65
- Nothing imports this binding — it is safe to review for removal. (×2) — packages/store/schematics/src/utils/config.ts:5, REDACTED:4
- Nothing ultimately consumes this binding: its only referrer is the re-export in packages/store/src/private_api.ts, whose re-exported name has no consumer either. Removing it is therefore not a one-file change — drop the re-export line in packages/store/src/private_api.ts in the same commit, or the barrel will import a name that no longer exists. (×2) — packages/store/src/internal/provide-internal-tokens.ts:15, packages/store/src/internal/provide-internal-tokens.ts:31
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×6) — packages/store/src/selectors/create-pick-selector.ts:5, packages/store/tests/select-signal.spec.ts:24, packages/store/types/tests/playground.ts:3, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
- Imported but not declared in any reachable REDACTED — installs work only by hoisting accident. (×4) — tools/publish-dev-builds.ts:1, packages/storage-plugin/schematics/src/_testing/schematics.ts:2, packages/store/schematics/src/_testing/schematics.ts:2, …
- Declared in the root REDACTED but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
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
- `deepFreeze` is exported and takes `o: any` from its caller, and it calls itself at line 20 (`deepFreeze`) with a piece of `o` — and nowhere in `deepFreeze` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `deepFreeze` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — packages/store/src/utils/freeze.ts:20
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
- An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×4) — packages/store/src/store.ts:141, packages/store/src/internal/state-context-factory.ts:165, packages/store/internals/testing/src/fresh-platform.ts:16, …
What to do
- Swallowed exception (empty catch)
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- ~6.6 `!` null assertions per 1k TypeScript source lines — 84 assertion(s) across the 12684 source line(s) of the 247 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/storage-plugin/src/storage.plugin.ts (7), REDACTED (7), packages/hmr-plugin/src/hmr-manager.ts (6). 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 `?`).
WCAG coverage — what static analysis assessed
| Dimension | WCAG 2.2 A/AA criteria | Coverage |
|---|---|---|
| AC2 · Forms & labels | 1.3.1, 3.3.2, 4.1.2 | Partial signal |
| AC3 · Page structure | 1.4.4, 2.2.1, 2.4.1, 2.4.2, 3.1.1, 4.1.2 | Partial signal |
| AC5 · ARIA correctness | 4.1.2 | Partial signal |
| AC6 · Visual & motion safety | 1.4.3, 2.4.7 | Partial — literal CSS only |
| AC7 · A11y enforcement | enforcement — no page criterion | Enforcement posture (process) |
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 74% | Strong | Solid. |
| Architecture | 92% | Exemplary | Solid. |
| Maturity | 74% | Strong | Solid. |
| Readiness | 44% | Weak — gated by R8, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 16% | Critical — gated by D36, C2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Accessibility | 58% | Adequate | Acceptable, with room to improve. |
| Performance | 100% | Exemplary | Strongest area. |
Unscored — 2 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 2 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
- X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 1 control(s) we could not find positive evidence for
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase
- AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
- AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
- AX1 Captive dependencies — Not applicable: Angular's root injector cannot see a component-level provider, so a root service asking for one fails with NullInjectorError instead of capturing it.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- 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 (our sandbox): a program the dev server needs is not installed in our sandbox image. This is a limit of our sandbox, not of your repository. Last output: "> ngxs@22.0.0 start / > yarn serve:hmr:integration / sh: 1: yarn: not found" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D21 Naming Consistency — Naming consistency is measured on C# and TypeScript only; JavaScript not measured.
- D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D25 ADR Conformance — no ADRs to check
- D27 Navigability — symbol resolution incomplete — navigability not assessed
- 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) — 10 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (ERROR RuntimeError: NG0101: ApplicationRef.tick is called recursively), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript source (service entry point: integration/src/server.ts:13 (express()))
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — 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 REDACTED, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 252 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 173 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions (empty test): should be correct detect type with createSelector packages/store/types/tests/create-selector.lint.ts:20
- No assertions (empty test): should be correct passed selectors packages/store/types/tests/selection.lint.ts:104
- No assertions (empty test): should return the correct array type packages/store/types/tests/state-operators.compose.lint.ts:86
- No assertions (empty test): should return the correct implied null or undefined type packages/store/types/tests/state-operators.iif.lint.ts:7
- No assertions (empty test): should return the correct implied number type packages/store/types/tests/state-operators.iif.lint.ts:16
- No assertions (empty test): should return the correct implied string type packages/store/types/tests/state-operators.iif.lint.ts:44
- No assertions (empty test): should return the correct implied boolean type packages/store/types/tests/state-operators.iif.lint.ts:72
- No assertions (empty test): should return the correct implied object type packages/store/types/tests/state-operators.iif.lint.ts:100
- <input> without a programmatic label integration/src/app/app.component.html:13
- <input> without a programmatic label integration/src/app/app.component.html:14
- <input> without a programmatic label integration/src/app/app.component.html:17
- <input> without a programmatic label integration/src/app/app.component.html:30
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import '@nx/devkit' packages/storage-plugin/schematics/src/_testing/schematics.ts:2
- Unlisted import '@nx/devkit' packages/store/schematics/src/_testing/schematics.ts:2
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Unlisted import 'semver' tools/publish-dev-builds.ts:1
- Unlisted import 'node-fetch' packages/store/tests/abort-signal.spec.ts:6
Serious — 244 finding(s)
- No assertions: ofAction() packages/store/types/tests/action.lint.ts:43
- No assertions: ofActionDispatched() packages/store/types/tests/action.lint.ts:74
- No assertions: ofActionSuccessful() packages/store/types/tests/action.lint.ts:105
- No assertions: ofActionCanceled() packages/store/types/tests/action.lint.ts:136
- No assertions: ofActionErrored() packages/store/types/tests/action.lint.ts:167
- No assertions: ofActionCompleted() packages/store/types/tests/action.lint.ts:198
- No assertions: ofActionDispatched() with a parameterized constructor action type match helper packages/store/types/tests/action.lint.ts:278
- No assertions: ofActionDispatched() directly constrained with a parameterized constructor match only packages/store/types/tests/action.lint.ts:310
- No assertions: ofActionDispatched() directly constrained with an instance shape match only packages/store/types/tests/action.lint.ts:333
- No assertions: ofActionDispatched() directly constrained with a constructor and instance shape match packages/store/types/tests/action.lint.ts:367
- No assertions: decorator matches method packages/store/types/tests/action.lint.ts:418
- No assertions: decorator does not match method packages/store/types/tests/action.lint.ts:441
- No assertions: should error on invalid use cases packages/store/types/tests/create-dispatch-map.lint.ts:6
- No assertions: should infer correct return types packages/store/types/tests/create-dispatch-map.lint.ts:24
- No assertions: should error on invalid use cases packages/store/types/tests/create-select-map.lint.ts:25
- No assertions: should infer correct return types packages/store/types/tests/create-select-map.lint.ts:30
- No assertions: should disallow mismatched projector parameter types packages/store/types/tests/create-selector.lint.ts:68
- No assertions: should get inferrable type from createSelector packages/store/types/tests/create-selector.lint.ts:75
- No assertions: should infer projector parameter types from selectors packages/store/types/tests/create-selector.lint.ts:144
- No assertions: should infer projector parameter types from mixed selectors packages/store/types/tests/create-selector.lint.ts:157
- No assertions: should infer projector parameter types from mixed selectors (explicit typing where needed) packages/store/types/tests/create-selector.lint.ts:173
- No assertions: doesnt allow invalid overridden projector parameter types packages/store/types/tests/create-selector.lint.ts:189
- No assertions: allows valid overridden projector parameter types packages/store/types/tests/create-selector.lint.ts:205
- No assertions: should be correct type in action decorator packages/store/types/tests/dispatch.lint.ts:30
- No assertions: should be success or compile error when property type is missing packages/store/types/tests/dispatch.lint.ts:44
- No test reaches this file packages/store/schematics/src/ng-add/add-declaration.ts:1
- No test reaches this file packages/storage-plugin/schematics/src/ng-generate/index.ts:1
- No test reaches this file packages/store/schematics/src/ng-add/ng-add.factory.ts:1
- No test reaches this file REDACTED:1
- No test reaches this file tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:1
- No test reaches this file setup-jest-preset.ts:1
- No test reaches this file tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/todo-list/todo-list.component.ts:1
- No test reaches this file tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/4-select-query-from-component/_files/src/app/todo/todo-list/todo-list.component.ts:1
- No test reaches this file integration/src/server.ts:1
- No test reaches this file tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/4-select-query-from-component/_solution/src/app/todo/todo-list/todo-list.component.ts:1
- No test reaches this file tools/build-schematics.mjs:1
- No test reaches this file tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/2-handle-the-action/_files/src/app/todo/store/todo.state.ts:1
- No test reaches this file tools/set-metadata.ts:1
- No test reaches this file integration/src/app/counter/counter.state.ts:1
- No test reaches this file tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/2-handle-the-action/_solution/src/app/todo/store/todo.state.ts:1
- No test reaches this file packages/store/schematics/src/state/state.factory.ts:1
- No test reaches this file packages/store/schematics/src/store/store.factory.ts:1
- No test reaches this file packages/store/schematics/src/utils/generate-utils.ts:1
- No test reaches this file tools/publish-dev-builds.ts:1
- No test reaches this file packages/storage-plugin/schematics/src/utils/visit-files.ts:1
- No test reaches this file integration/src/app/list/list.component.ts:1
- No test reaches this file packages/store/schematics/src/starter-kit/starter-kit.factory.ts:1
- No test reaches this file integration/src/app/counter/counter.component.ts:1
- No test reaches this file packages/store/schematics/src/actions/actions.factory.ts:1
- No test reaches this file integration/src/app/detail/detail.component.ts:1
- 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
- Boundary violation [package:relative-cross-package] packages/devtools-plugin/test-setup.ts:1
- Boundary violation [package:relative-cross-package] packages/form-plugin/test-setup.ts:1
- Boundary violation [package:relative-cross-package] packages/hmr-plugin/test-setup.ts:1
- Boundary violation [package:relative-cross-package] packages/logger-plugin/test-setup.ts:1
- Boundary violation [package:relative-cross-package] packages/router-plugin/test-setup.ts:1
- Boundary violation [package:relative-cross-package] packages/storage-plugin/test-setup.ts:1
- Boundary violation [package:relative-cross-package] packages/store/test-setup.ts:1
- Boundary violation [package:relative-cross-package] packages/websocket-plugin/test-setup.ts:1
- Dead file (~1 LoC) packages/devtools-plugin/test-setup.ts
- Dead file (~1 LoC) packages/form-plugin/test-setup.ts
- Dead file (~1 LoC) packages/hmr-plugin/test-setup.ts
- Dead file (~1 LoC) packages/logger-plugin/test-setup.ts
- Dead file (~1 LoC) packages/router-plugin/test-setup.ts
- Dead file (~1 LoC) packages/storage-plugin/test-setup.ts
- Dead file (~1 LoC) packages/store/test-setup.ts
- Dead file (~1 LoC) packages/websocket-plugin/test-setup.ts
- TodoComment packages/websocket-plugin/src/websocket-handler.ts:67
- TodoComment packages/store/tests/dev-mode.spec.ts:338
- TodoComment packages/store/tests/ensure-store.spec.ts:145
- TodoComment packages/store/src/internal/state-factory.ts:328
- Swallowed exception (empty catch) packages/store/src/store.ts:141
- Swallowed exception (empty catch) packages/store/src/internal/state-context-factory.ts:165
- Swallowed exception (empty catch) packages/store/internals/testing/src/fresh-platform.ts:16
- Swallowed exception (empty catch) packages/hmr-plugin/src/hmr-manager.ts:99
- Page without a main landmark integration/src/index.html:2
- Page without a main landmark integrations/hello-world-ng22/src/index.html:2
- Page without a main landmark tutorials/create-app/src/templates/ngxs/src/index.html:2
- Skipped test: should give an error if the action is mutated by a handler packages/store/tests/dev-mode.spec.ts:406
- Skipped test: should give an error if a child action is mutated by a handler packages/store/tests/dev-mode.spec.ts:442
- Skipped test: should get the selector meta data from the SuperCountState.canInheritSelectFn packages/store/tests/ensure-store.spec.ts:165
- Deprecated: @angular/animations REDACTED:100
- Deprecated: @angular/platform-browser-dynamic REDACTED:110
- Deprecated: eslint REDACTED:132
- REDACTED
- REDACTED
- REDACTED
- Empty method body — does nothing with its inputs tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:76
- Empty method body — does nothing with its inputs tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/4-select-query-from-component/_files/src/app/todo/todo-list/todo-list.component.ts:59
- Empty method body — does nothing with its inputs tutorials/create-app/src/content/tutorial/1-create-a-todo-app/3-get-todo-items/4-select-query-from-component/_solution/src/app/todo/todo-list/todo-list.component.ts:54
- Duplicated block (8 lines × 2 locations) packages/store/operators/src/remove-item.ts:24
- Duplicated block (8 lines × 2 locations) packages/store/operators/src/remove-items.ts:25
- Duplicated block (8 lines × 2 locations) packages/store/src/internal/dispatcher.ts:41
- REDACTED
- REDACTED
- Duplicated block (47 lines × 2 locations) tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/store/todo.state.ts:7
- Duplicated block (47 lines × 2 locations) tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/store/todo.state.ts:2
- Dead file (~34 LoC) packages/store/schematics/src/state/state.factory.ts
- Dead file (~34 LoC) packages/store/schematics/src/store/store.factory.ts
- JavaScript dependencies are not locked tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/1-using-schematics/_files/REDACTED:10
- JavaScript dependencies are not locked tutorials/create-app/src/templates/ngxs/REDACTED:10
- Accessibility enforcement below the top rung REDACTED:95
- No authorization integration/src/server.ts:13
- NgxsStoragePlugin.handle (cyclomatic 49) packages/storage-plugin/src/storage.plugin.ts:101
- NgxsFormPlugin.handle (cyclomatic 17) packages/form-plugin/src/form.plugin.ts:24
- NgxsStoragePlugin.handle (cognitive 106) packages/storage-plugin/src/storage.plugin.ts:101
- NgxsFormPlugin.handle (cognitive 18) packages/form-plugin/src/form.plugin.ts:24
- InternalActionHandlerFactory.createActionHandler (cognitive 16) packages/store/src/internal/action-handler-factory.ts:25
- pending-tasks.withNgxsPendingTasks (cognitive 16) packages/store/src/pending-tasks.ts:35
- Change coupling: app.component.ts ↔ list.component.ts integration/src/app/app.component.ts:1
- REDACTED
- Off the main sequence: @ngxs/store
- Coverage not measured — JavaScript/TypeScript suite
- README may be stale
- Duplication concentrated across 2 sibling directories (5 clone groups) tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:13
- Duplicated block (63 lines × 2 locations) tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:13
- Duplicated block (35 lines × 2 locations) packages/storage-plugin/schematics/src/_testing/schematics.ts:7
- Duplicated block (33 lines × 2 locations) packages/devtools-plugin/src/devtools.module.ts:25
- Duplicated block (32 lines × 2 locations) tutorials/create-app/src/content/tutorial/1-create-a-todo-app/2-installation/2-create-store/_files/src/app/todo/todo-list/todo-list.component.ts:15
- Duplicated block (26 lines × 3 locations) tutorials/create-app/src/content/tutorial/1-create-a-todo-app/1-welcome/1-welcome/_files/src/app/todo/todo-list/todo-list.component.ts:12
- Duplicated block (22 lines × 2 locations) packages/store/schematics/src/state/state.factory.ts:10
- Duplicated block (15 lines × 2 locations) packages/form-plugin/src/directive.ts:94
- Duplicated block with local edits (8 matched lines × 2 locations) packages/store/src/execution/execution-strategy.ts:2
- Duplicated block (6 lines × 2 locations) packages/store/internals/testing/src/skip-console-logging.ts:13
- Complex function handle (cyclomatic 29, cognitive 70) packages/storage-plugin/src/storage.plugin.ts:101
- Complex function handle (cyclomatic 17, cognitive 17) packages/form-plugin/src/form.plugin.ts:24
- Complex function (anonymous) (cyclomatic 16, cognitive 28) packages/storage-plugin/src/storage.plugin.ts:231
- Complex function (anonymous) (cyclomatic 11, cognitive 14) packages/router-plugin/src/router.state.ts:208
- Dead file (~124 LoC) packages/store/schematics/src/ng-add/add-declaration.ts
- Dead file (~111 LoC) packages/storage-plugin/schematics/src/ng-generate/index.ts
- Dead file (~106 LoC) packages/store/schematics/src/ng-add/ng-add.factory.ts
- Dead file (~63 LoC) integration/src/server.ts
- Dead file (~52 LoC) tools/build-schematics.mjs
- Dead file (~32 LoC) packages/store/schematics/src/utils/generate-utils.ts
- Dead file (~28 LoC) packages/storage-plugin/schematics/src/utils/visit-files.ts
- Dead file (~25 LoC) packages/store/schematics/src/starter-kit/starter-kit.factory.ts
- Dead file (~23 LoC) packages/store/schematics/src/actions/actions.factory.ts
- Dead file (~9 LoC) integration/src/main.server.ts
- Dead file (~8 LoC) packages/store/schematics/src/utils/interfaces/package.interface.ts
- Dead file (~6 LoC) integration/src/main.ts
- Dead file (~3 LoC) packages/store/schematics/src/utils/common/properties.ts
- Unused dependency '@angular/animations'
- Unused dependency '@angular/cli'
- Unused dependency '@angular/language-service'
- Recursive walk over a caller-supplied document has no depth cap packages/store/src/utils/freeze.ts:20
Minor — 103 finding(s)
- Deprecated: @humanwhocodes/config-array REDACTED:2330
- Deprecated: @humanwhocodes/object-schema REDACTED:2344
- Deprecated: @ungap/structured-clone REDACTED:5245
- Deprecated: abab REDACTED:5508
- Deprecated: cron-parser REDACTED:6991
- Deprecated: domexception REDACTED:7458
- Deprecated: git-raw-commits REDACTED:8681
- Deprecated: glob REDACTED:8718
- Deprecated: glob REDACTED:8739
- Deprecated: image-size REDACTED:9200
- Deprecated: inflight REDACTED:9236
- Deprecated: memfs REDACTED:11157
- Deprecated: rimraf REDACTED:13311
- Deprecated: tar REDACTED:14522
- Deprecated: uuid REDACTED:15151
- Deprecated: whatwg-encoding REDACTED:15432
- Deprecated: @ungap/structured-clone REDACTED:1862
- Deprecated: tsconfck REDACTED:5162
- Console output used as the logging channel packages/logger-plugin/src/log-writer.ts:18
- Console output used as the logging channel packages/storage-plugin/src/with-storage-feature.ts:19
- Console output used as the logging channel packages/storage-plugin/src/features/with-ngxs-storage-transfer-state.ts:103
- Console output used as the logging channel packages/storage-plugin/src/features/with-ngxs-storage-transfer-state.ts:121
- Console output used as the logging channel packages/store/src/pending-tasks.ts:109
- Console output used as the logging channel packages/store/src/store.ts:136
- Console output used as the logging channel packages/store/src/standalone-features/preboot.ts:23
- Console output used as the logging channel packages/store/src/selectors/selector-checks.util.ts:38
- Console output used as the logging channel packages/store/src/selectors/selector-types.util.ts:24
- Console output used as the logging channel packages/store/src/selectors/selector-utils.ts:60
- Console output used as the logging channel packages/store/src/ivy/ivy-enabled-in-dev-mode.ts:15
- Console output used as the logging channel packages/store/src/ivy/ivy-enabled-in-dev-mode.ts:20
- Console output used as the logging channel packages/store/src/internal/action-handler-factory.ts:107
- Console output used as the logging channel packages/store/src/internal/lifecycle-state-manager.ts:45
- Console output used as the logging channel packages/store/src/internal/state-context-factory.ts:161
- Console output used as the logging channel packages/store/src/dev-features/ngxs-unhandled-actions-logger.ts:46
- Console output used as the logging channel packages/store/schematics/src/_testing/schematics.ts:65
- Console output used as the logging channel packages/store/internals/src/action-registry.ts:56
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Documentation: no build, run or usage example packages/devtools-plugin/README.md:1
- Documentation: no build, run or usage example packages/form-plugin/README.md:1
- Documentation: no build, run or usage example packages/hmr-plugin/README.md:1
- Documentation: no build, run or usage example packages/logger-plugin/README.md:1
- Documentation: no build, run or usage example packages/router-plugin/README.md:1
- Documentation: no build, run or usage example packages/storage-plugin/README.md:1
- Documentation: no build, run or usage example packages/store/README.md:1
- Documentation: no build, run or usage example packages/websocket-plugin/README.md:1
- Documentation: no build, run or usage example tutorials/create-app/README.md:1
- Disabled test packages/store/tests/dev-mode.spec.ts:406
- Disabled test packages/store/tests/dev-mode.spec.ts:442
- Disabled test packages/store/tests/ensure-store.spec.ts:165
- Disabled test packages/store/tests/issues/actions-stream-causing-ticks.spec.ts:17
- Disabled test packages/store/tests/issues/issue-933-selectors-causing-ticks.spec.ts:8
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- Duplicated predicate packages/store/schematics/src/starter-kit/starter-kit.factory.ts:13
- Duplicated predicate packages/storage-plugin/src/features/with-ngxs-storage-sync.ts:44
- Duplicated predicate packages/router-plugin/internals/src/symbols.ts:15
- Duplicated predicate packages/storage-plugin/src/engines.ts:14
- redundant comment packages/logger-plugin/tests/helpers/utils.ts:27
- redundant comment packages/store/src/execution/symbols.ts:1
- redundant comment packages/store/types/tests/create-selector.lint.ts:98
- Orphaned file packages/store/src/decorators/selector/symbols.ts:1
- Orphaned file packages/storage-plugin/schematics/src/ng-generate/index.ts:1
- Orphaned file packages/store/schematics/src/_testing/schematics.ts:1
- Off-boarding risk: anonymized user #1
- No ADRs found
- Projects may be oversized for their cohesion
- REDACTED
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- Empty method body packages/store/src/internal/dispatcher.ts:41
- No ADRs
- Logging is not universal
- No SAST REDACTED:8
- Unused export 'routerQueryParamMap' packages/router-plugin/src/router-selectors.ts:28
- Unused export 'routerParamMap' packages/router-plugin/src/router-selectors.ts:52
- Unused export 'routerParamMapForOutlet' packages/router-plugin/src/router-selectors.ts:80
- Unused export 'ɵStateToken' packages/store/internals/src/symbols.ts:24
- Unused export 'actionMatcher' packages/store/plugins/src/utils.ts:65
- Unused export 'AppConfig' packages/store/schematics/src/utils/config.ts:5
- Unused export 'ɵprovideNgxsInternalStateTokens' packages/store/src/internal/provide-internal-tokens.ts:15
- Unused export 'ɵgetTypedNgxsStateFactory' packages/store/src/internal/provide-internal-tokens.ts:31
- Unused export 'ArgvType' REDACTED:4
- Unused module-local declaration 'KeysToValues' packages/store/src/selectors/create-pick-selector.ts:5
- Unused module-local declaration 'waitForStateSignalToReceiveUpdate' packages/store/tests/select-signal.spec.ts:24
- Unused module-local declaration 'CheckRO_' packages/store/types/tests/playground.ts:3
- Unused module-local declaration 'nul' packages/store/types/tests/playground.ts:6
- Unused module-local declaration 'und' packages/store/types/tests/playground.ts:7
- Unused module-local declaration 'str' packages/store/types/tests/playground.ts:8
- Null assertions (`!`) reduce the strict null checking score
Minor — 14 finding(s)
- Outdated (npm): @angular/common
- Outdated (npm): @angular/compiler
- Outdated (npm): @angular/core
- Outdated (npm): @angular/forms
- Outdated (npm): @angular/platform-browser
- Outdated (npm): @angular/router
- Outdated (npm): @tutorialkit/components-react
- Outdated (npm): react
- Outdated (npm): react-dom
- Outdated (npm): tslib
- Skipped (documented): (unnamed test) packages/store/tests/action-handler.spec.ts:88
- Skipped (documented): (unnamed test) packages/store/tests/action-handler.spec.ts:191
- doc comments repeat the names packages/storage-plugin/src/transfer-state.ts:20
- doc comments repeat the names packages/store/plugins/src/utils.ts:28
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-ed9f5a2d5d804235be7ca17b7cfc32b6/history.json --exit-code 0 --source . | 4 | 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-ed9f5a2d5d804235be7ca17b7cfc32b6/tree.json --exit-code 0 --source . | 1 | 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 --exclude .circleci --exclude .vscode . | 34 | 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 | 170 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 10 file(s) — `integration/src/app/counter/counter.state.ts`, `integration/src/app/list/list.state.ts`, `integration/src/app/store/todos/todo/todo.state.ts`, `integration/src/app/store/todos/todos.state.ts`, `integrations/hello-world-ng22/src/app/store/counter/counter.state.ts`, … (+5 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |