Executive summary
reduxjs/redux is rated At risk because critical security findings are open, most of them in the packages it uses. It scores 61 out of 100, which the At risk rating leaves unchanged. We judged it as a template or a sample, against a lower bar.
Every lens scores high enough to be rated Strong, so no single lens holds the score back. The best first step for the work it takes is replacing each deprecated dependency, worth about 4 points. Adopting a logging library comes next, worth about 5 points.
336 known security holes in the packages the code depends on can be used by attackers. One automatic update takes new releases before a bad one can be spotted. Updating the vulnerable packages and setting a waiting period for automatic updates would close both risks. The use of a package that isn't listed needs adding to the project's list of dependencies.
The product code is 5,386 lines, about €11,000 to rebuild.
Every lens already scores high enough to be rated Strong, so no single lens holds the score back.
New since the last survey: 439 findings
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
- Dependency Vulnerabilities · REDACTED
Fixed since the last survey: 19 findings
- Cyclomatic Complexity · combineReducers.combineReducers (cyclomatic 17) src/combineReducers.ts
- Cyclomatic Complexity · mangleErrors.mangleErrorsPlugin (cyclomatic 16) scripts/mangleErrors.mts
- Cognitive Complexity · combineReducers.combineReducers (cognitive 21) src/combineReducers.ts
- Cognitive Complexity · mangleErrors.mangleErrorsPlugin (cognitive 16) scripts/mangleErrors.mts
- Secrets (history) · Secret: generic-api-key book.json
- Secrets (history) · High secret: WD-SECRET-0005 examples/async/package-lock.json
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Secrets (history) · High secret: WD-SECRET-0005 examples/real-world/package-lock.json
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Secrets (history) · High secret: WD-SECRET-0005 examples/todomvc/package-lock.json
- Secrets (history) · High secret: WD-SECRET-0005 examples/todos-flow/package-lock.json
- Secrets (history) · High secret: WD-SECRET-0005 examples/todos-with-undo/package-lock.json
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Secrets (history) · High secret: WD-SECRET-0005 REDACTED
- Secrets (history) · High secret: WD-SECRET-0005 website/package-lock.json
- Test Coverage · No test reaches this file scripts/mangleErrors.mts
- Test Coverage · No test reaches this file scripts/stripSourcemapFileField.mts
- Test Coverage · No test reaches this file scripts/clean.mts
Rebuild cost: about €11,000 · Estimate
| Cost to rebuild | €3,600 to €18,000, for 60 to 189 hours of work, under 0.1 person-years for one engineer |
|---|---|
| Difficulty of the problem | Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write. |
| Quality factor | ×0.8 at a score of 61. 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: 5,386 lines of product code |
| What it is not | Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one. |
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 docs.components | 2 scripts.mangleErrors | 3 src.types.actions | 4 src.types.middleware | 5 src.types.store | 6 src.utils | 7 src.utils.symbol-observable | 8 website.plugins | 9 website.plugins.remark-typescript-tools.linkDocblocks | 10 website.plugins.remark-typescript-tools.linkDocblocks.extract | 11 website.plugins.remark-typescript-tools.transpileCodeblocks.compiler | 12 website.scripts.fetch-external-docs | 13 website.src | 14 website.src.components.ErrorCodesPage | 15 website.src.components.LibraryDropdownNavbarItem | 16 website.src.components.LibraryLanding | 17 website.src.components.LibraryLinksNavbarItem | 18 website.src.components.VideoEmbed | 19 website.src.components.useCurrentLibrary | 20 website.src.pages | 21 scripts | 22 src | 23 website.plugins.remark-typescript-tools.linkDocblocks.plugin | 24 website.plugins.remark-typescript-tools.transpileCodeblocks.plugin | 25 website.scripts | 26 website.src.components | 27 website.src.theme.Navbar.MobileSidebar | 28 website.plugins.remark-typescript-tools.transpileCodeblocks |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 docs.components | ||||||||||||||||||||||||||||
| 2 scripts.mangleErrors | ||||||||||||||||||||||||||||
| 3 src.types.actions | ||||||||||||||||||||||||||||
| 4 src.types.middleware | ||||||||||||||||||||||||||||
| 5 src.types.store | ||||||||||||||||||||||||||||
| 6 src.utils | ||||||||||||||||||||||||||||
| 7 src.utils.symbol-observable | ||||||||||||||||||||||||||||
| 8 website.plugins | ||||||||||||||||||||||||||||
| 9 website.plugins.remark-typescript-tools.linkDocblocks | ||||||||||||||||||||||||||||
| 10 website.plugins.remark-typescript-tools.linkDocblocks.extract | ||||||||||||||||||||||||||||
| 11 website.plugins.remark-typescript-tools.transpileCodeblocks.compiler | ||||||||||||||||||||||||||||
| 12 website.scripts.fetch-external-docs | ||||||||||||||||||||||||||||
| 13 website.src | ||||||||||||||||||||||||||||
| 14 website.src.components.ErrorCodesPage | ||||||||||||||||||||||||||||
| 15 website.src.components.LibraryDropdownNavbarItem | ||||||||||||||||||||||||||||
| 16 website.src.components.LibraryLanding | ||||||||||||||||||||||||||||
| 17 website.src.components.LibraryLinksNavbarItem | ||||||||||||||||||||||||||||
| 18 website.src.components.VideoEmbed | ||||||||||||||||||||||||||||
| 19 website.src.components.useCurrentLibrary | ||||||||||||||||||||||||||||
| 20 website.src.pages | ||||||||||||||||||||||||||||
| 21 scripts | 1 | |||||||||||||||||||||||||||
| 22 src | 1 | 1 | ||||||||||||||||||||||||||
| 23 website.plugins.remark-typescript-tools.linkDocblocks.plugin | 1 | |||||||||||||||||||||||||||
| 24 website.plugins.remark-typescript-tools.transpileCodeblocks.plugin | 1 | |||||||||||||||||||||||||||
| 25 website.scripts | 1 | |||||||||||||||||||||||||||
| 26 website.src.components | 1 | 2 | 1 | 1 | 1 | |||||||||||||||||||||||
| 27 website.src.theme.Navbar.MobileSidebar | 1 | |||||||||||||||||||||||||||
| 28 website.plugins.remark-typescript-tools.transpileCodeblocks | 1 | 2 |
21→2 scripts uses scripts.mangleErrors✕
- Connections
- 1 pair of types, where a type in scripts uses a type in scripts.mangleErrors.
- The types involved
scripts.mangleErrors→scripts.mangleErrors.MangleErrorsPluginOptions
- Direction
- scripts uses scripts.mangleErrors, so a change to scripts.mangleErrors can break scripts, while a change to scripts can't break scripts.mangleErrors.
- Position
- Below the diagonal: scripts uses a module listed above it, which is the healthy direction.
22→3 src uses src.types.actions✕
- Connections
- 1 pair of types, where a type in src uses a type in src.types.actions.
- The types involved
src.bindActionCreators→src.types.actions.ActionCreator
- Direction
- src uses src.types.actions, so a change to src.types.actions can break src, while a change to src can't break src.types.actions.
- Position
- Below the diagonal: src uses a module listed above it, which is the healthy direction.
22→5 src uses src.types.store✕
- Connections
- 1 pair of types, where a type in src uses a type in src.types.store.
- The types involved
src.bindActionCreators→src.types.store.Dispatch
- Direction
- src uses src.types.store, so a change to src.types.store can break src, while a change to src can't break src.types.store.
- Position
- Below the diagonal: src uses a module listed above it, which is the healthy direction.
23→10 website.plugins.remark-typescript-tools.linkDocblocks.plugin uses website.plugins.remark-typescript-tools.linkDocblocks.extract✕
- Connections
- 1 pair of types, where a type in website.plugins.remark-typescript-tools.linkDocblocks.plugin uses a type in website.plugins.remark-typescript-tools.linkDocblocks.extract.
- The types involved
website.plugins.remark-typescript-tools.linkDocblocks.plugin.LinkDocblocksSettings→website.plugins.remark-typescript-tools.linkDocblocks.extract.ExtractorSettings
- Direction
- website.plugins.remark-typescript-tools.linkDocblocks.plugin uses website.plugins.remark-typescript-tools.linkDocblocks.extract, so a change to website.plugins.remark-typescript-tools.linkDocblocks.extract can break website.plugins.remark-typescript-tools.linkDocblocks.plugin, while a change to website.plugins.remark-typescript-tools.linkDocblocks.plugin can't break website.plugins.remark-typescript-tools.linkDocblocks.extract.
- Position
- Below the diagonal: website.plugins.remark-typescript-tools.linkDocblocks.plugin uses a module listed above it, which is the healthy direction.
24→11 website.plugins.remark-typescript-tools.transpileCodeblocks.plugin uses website.plugins.remark-typescript-tools.transpileCodeblocks.compiler✕
- Connections
- 1 pair of types, where a type in website.plugins.remark-typescript-tools.transpileCodeblocks.plugin uses a type in website.plugins.remark-typescript-tools.transpileCodeblocks.compiler.
- The types involved
website.plugins.remark-typescript-tools.transpileCodeblocks.plugin.TranspileCodeblocksSettings→website.plugins.remark-typescript-tools.transpileCodeblocks.compiler.CompilerSettings
- Direction
- website.plugins.remark-typescript-tools.transpileCodeblocks.plugin uses website.plugins.remark-typescript-tools.transpileCodeblocks.compiler, so a change to website.plugins.remark-typescript-tools.transpileCodeblocks.compiler can break website.plugins.remark-typescript-tools.transpileCodeblocks.plugin, while a change to website.plugins.remark-typescript-tools.transpileCodeblocks.plugin can't break website.plugins.remark-typescript-tools.transpileCodeblocks.compiler.
- Position
- Below the diagonal: website.plugins.remark-typescript-tools.transpileCodeblocks.plugin uses a module listed above it, which is the healthy direction.
25→12 website.scripts uses website.scripts.fetch-external-docs✕
- Connections
- 1 pair of types, where a type in website.scripts uses a type in website.scripts.fetch-external-docs.
- The types involved
website.scripts.fetch-external-docs→website.scripts.fetch-external-docs.ExternalSource
- Direction
- website.scripts uses website.scripts.fetch-external-docs, so a change to website.scripts.fetch-external-docs can break website.scripts, while a change to website.scripts can't break website.scripts.fetch-external-docs.
- Position
- Below the diagonal: website.scripts uses a module listed above it, which is the healthy direction.
26→14 website.src.components uses website.src.components.ErrorCodesPage✕
- Connections
- 1 pair of types, where a type in website.src.components uses a type in website.src.components.ErrorCodesPage.
- The types involved
website.src.components.ErrorCodesPage→website.src.components.ErrorCodesPage.ErrorCodesPageProps
- Direction
- website.src.components uses website.src.components.ErrorCodesPage, so a change to website.src.components.ErrorCodesPage can break website.src.components, while a change to website.src.components can't break website.src.components.ErrorCodesPage.
- Position
- Below the diagonal: website.src.components uses a module listed above it, which is the healthy direction.
26→15 website.src.components uses website.src.components.LibraryDropdownNavbarItem✕
- Connections
- 2 pairs of types, where a type in website.src.components uses a type in website.src.components.LibraryDropdownNavbarItem.
- The types involved
website.src.components.LibraryDropdownNavbarItem→website.src.components.LibraryDropdownNavbarItem.Propswebsite.src.components.LibraryLinksNavbarItem→website.src.components.LibraryDropdownNavbarItem.Props
- Direction
- website.src.components uses website.src.components.LibraryDropdownNavbarItem, so a change to website.src.components.LibraryDropdownNavbarItem can break website.src.components, while a change to website.src.components can't break website.src.components.LibraryDropdownNavbarItem.
- Position
- Below the diagonal: website.src.components uses a module listed above it, which is the healthy direction.
26→16 website.src.components uses website.src.components.LibraryLanding✕
- Connections
- 1 pair of types, where a type in website.src.components uses a type in website.src.components.LibraryLanding.
- The types involved
website.src.components.LibraryLanding→website.src.components.LibraryLanding.LibraryLandingProps
- Direction
- website.src.components uses website.src.components.LibraryLanding, so a change to website.src.components.LibraryLanding can break website.src.components, while a change to website.src.components can't break website.src.components.LibraryLanding.
- Position
- Below the diagonal: website.src.components uses a module listed above it, which is the healthy direction.
26→18 website.src.components uses website.src.components.VideoEmbed✕
- Connections
- 1 pair of types, where a type in website.src.components uses a type in website.src.components.VideoEmbed.
- The types involved
website.src.components.VideoEmbed→website.src.components.VideoEmbed.Mode
- Direction
- website.src.components uses website.src.components.VideoEmbed, so a change to website.src.components.VideoEmbed can break website.src.components, while a change to website.src.components can't break website.src.components.VideoEmbed.
- Position
- Below the diagonal: website.src.components uses a module listed above it, which is the healthy direction.
26→19 website.src.components uses website.src.components.useCurrentLibrary✕
- Connections
- 1 pair of types, where a type in website.src.components uses a type in website.src.components.useCurrentLibrary.
- The types involved
website.src.components.useCurrentLibrary→website.src.components.useCurrentLibrary.LibraryEntry
- Direction
- website.src.components uses website.src.components.useCurrentLibrary, so a change to website.src.components.useCurrentLibrary can break website.src.components, while a change to website.src.components can't break website.src.components.useCurrentLibrary.
- Position
- Below the diagonal: website.src.components uses a module listed above it, which is the healthy direction.
27→15 website.src.theme.Navbar.MobileSidebar uses website.src.components.LibraryDropdownNavbarItem✕
- Connections
- 1 pair of types, where a type in website.src.theme.Navbar.MobileSidebar uses a type in website.src.components.LibraryDropdownNavbarItem.
- The types involved
website.src.theme.Navbar.MobileSidebar.index→website.src.components.LibraryDropdownNavbarItem.Props
- Direction
- website.src.theme.Navbar.MobileSidebar uses website.src.components.LibraryDropdownNavbarItem, so a change to website.src.components.LibraryDropdownNavbarItem can break website.src.theme.Navbar.MobileSidebar, while a change to website.src.theme.Navbar.MobileSidebar can't break website.src.components.LibraryDropdownNavbarItem.
- Position
- Below the diagonal: website.src.theme.Navbar.MobileSidebar uses a module listed above it, which is the healthy direction.
28→11 website.plugins.remark-typescript-tools.transpileCodeblocks uses website.plugins.remark-typescript-tools.transpileCodeblocks.compiler✕
- Connections
- 1 pair of types, where a type in website.plugins.remark-typescript-tools.transpileCodeblocks uses a type in website.plugins.remark-typescript-tools.transpileCodeblocks.compiler.
- The types involved
website.plugins.remark-typescript-tools.transpileCodeblocks.plugin→website.plugins.remark-typescript-tools.transpileCodeblocks.compiler.TranspiledFile
- Direction
- website.plugins.remark-typescript-tools.transpileCodeblocks uses website.plugins.remark-typescript-tools.transpileCodeblocks.compiler, so a change to website.plugins.remark-typescript-tools.transpileCodeblocks.compiler can break website.plugins.remark-typescript-tools.transpileCodeblocks, while a change to website.plugins.remark-typescript-tools.transpileCodeblocks can't break website.plugins.remark-typescript-tools.transpileCodeblocks.compiler.
- Position
- Below the diagonal: website.plugins.remark-typescript-tools.transpileCodeblocks uses a module listed above it, which is the healthy direction.
28→24 website.plugins.remark-typescript-tools.transpileCodeblocks uses website.plugins.remark-typescript-tools.transpileCodeblocks.plugin✕
- Connections
- 2 pairs of types, where a type in website.plugins.remark-typescript-tools.transpileCodeblocks uses a type in website.plugins.remark-typescript-tools.transpileCodeblocks.plugin.
- The types involved
website.plugins.remark-typescript-tools.transpileCodeblocks.plugin→website.plugins.remark-typescript-tools.transpileCodeblocks.plugin.CodeNodewebsite.plugins.remark-typescript-tools.transpileCodeblocks.plugin→website.plugins.remark-typescript-tools.transpileCodeblocks.plugin.VirtualFile
- Direction
- website.plugins.remark-typescript-tools.transpileCodeblocks uses website.plugins.remark-typescript-tools.transpileCodeblocks.plugin, so a change to website.plugins.remark-typescript-tools.transpileCodeblocks.plugin can break website.plugins.remark-typescript-tools.transpileCodeblocks, while a change to website.plugins.remark-typescript-tools.transpileCodeblocks can't break website.plugins.remark-typescript-tools.transpileCodeblocks.plugin.
- Position
- Below the diagonal: website.plugins.remark-typescript-tools.transpileCodeblocks 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 — Performance
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A03:2025 — Software Supply Chain Failures | 498 | High / Critical |
| A05:2025 — Injection | 2 | High / Critical |
Roadmap
Top priorities: Adopt pino (or winston) and log at meaningful points in the services you run; Resolve the 37 No assertions finding(s) in Test Quality — start with middleware.test-d.ts (11), enhancers.test-d.ts (8), reducers.test-d.ts (6); Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Resolve the 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. | +4.3 pts | Low | Dependency Hygiene |
| Adopt pino (or winston) and log at meaningful points in the services you run. | +5.2 pts | Medium | Observability |
| Resolve the 37 No assertions finding(s) in Test Quality — start with middleware.test-d.ts (11), enhancers.test-d.ts (8), reducers.test-d.ts (6). | +4.6 pts | Medium | Test Quality |
| 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. | +4.1 pts | Medium | Security & performance tooling |
| Resolve the 4 Orphaned file finding(s) in Knowledge Freshness — start with combineReducers.ts, mangleErrors.mts, actions.ts. | +1.7 pts | Low | Knowledge Freshness |
| Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them. | +2.5 pts | Medium | Architecture documentation |
| Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies. | +2.2 pts | Medium | Dependency Hygiene |
| Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. | +1.0 pts | Low | Static Analysis (SAST) |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| REDACTED | 0.0 | Slop | Dependency Vulnerabilities: Critical CVE: REDACTED |
| test/typescript/reducers.test-d.ts | 6.0 | Near-clean | Explicit Debt: TodoComment |
| test/typescript/middleware.test-d.ts | 7.0 | Near-clean | Test Quality: No assertions: Logger middleware doesn't add any extra types to dispatch, just logs actions and state. |
| test/typescript/enhancers.test-d.ts | 7.0 | Near-clean | Test Quality: No assertions: Store enhancer that extends the type of dispatch. |
| REDACTED | 7.2 | Near-clean | Static Analysis (SAST): High: REDACTED |
| test/typescript/actions.test-d.ts | 7.4 | Near-clean | Test Quality: No assertions: FSA |
| test/typescript/injectedDispatch.test-d.ts | 7.4 | Near-clean | Test Quality: No assertions: inject default dispatch. |
| src/createStore.ts | 7.8 | Near-clean | Cyclomatic Complexity: createStore.createStore (cyclomatic 24) |
| test/typescript/actionCreators.test-d.ts | 7.8 | Near-clean | Test Quality: No assertions: ActionCreator |
| test/typescript/dispatch.test-d.ts | 7.8 | Near-clean | Test Quality: No assertions: default Dispatch type accepts any object with `type` property. |
| REDACTED | 7.9 | Near-clean | Static Analysis (SAST): Medium: REDACTED |
| src/types/middleware.ts | 8.2 | Near-clean | Explicit Debt: TodoComment |
| test/typescript/compose.test-d.ts | 8.5 | Near-clean | Test Quality: No assertions: compose |
| test/typescript/store.test-d.ts | 8.5 | Near-clean | Test Quality: No assertions: createStore |
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 57 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 — 57 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, 564 of 587 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
- D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
- D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (package.json), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
- D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/types/store.ts`, `REDACTED`, `website/plugins/remark-typescript-tools/linkDocblocks/plugin.ts`, `website/plugins/remark-typescript-tools/transpileCodeblocks/plugin.ts` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
- 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.
- 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 (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
- 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. A badge or prose version claim scored 9/17 in its adjudication (docs/plans/deterministic-engine/adjudication/M4-v3.md: badges 9/9, prose 0/8, where prose versions are minimums or history), short of the 95 % precision gate, so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them. The .NET and Node.js version checks are a different kind and still publish.
- 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 none applies: this repository publishes a library and deploys nothing (no container, IaC or deployment manifest), so it holds no runtime state of its own. Any data-access dependency it declares is the store it is a CLIENT for, not one it operates. The DR control belongs to whoever runs that data.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP make no call through a named logger, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
- D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
- D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
- D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
- 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 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- 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.
- D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
- D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
- D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
- D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
- D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
- D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
- D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- 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
1 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was createStore.createStore at 24. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being kindOf.miniKindOf at 17 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: src/utils/kindOf.ts (kindOf.miniKindOf at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
What to do
- Bring the 1 body over 15 down to 15 or less in Cyclomatic Complexity — start with createStore.createStore (cyclomatic 24). — Refactoring it lifts Cyclomatic Complexity from 9.4 to about 10.0/10.
D2 · Cognitive Complexity
1 method(s) exceeded the cognitive complexity threshold of 15; the worst was createStore.createStore at 24.
What to do
- Bring the 1 body over 15 down to 15 or less in Cognitive Complexity — start with createStore.createStore (cognitive 24). — Refactoring it lifts Cognitive Complexity from 9.4 to about 10.0/10.
D3 · God Classes
0 god class(es) detected.
D10 · Test Quality
4 skipped (4 with a documented reason), 37 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 180 tests.
What to do
- Resolve the 37 No assertions finding(s) in Test Quality — start with middleware.test-d.ts (11), enhancers.test-d.ts (8), reducers.test-d.ts (6). — One of this dimension's main actionable groups (37 warning-level).
- Resolve the 4 Mock-dominated test finding(s) in Test Quality — start with createStore.spec.ts (4). — One of this dimension's main actionable groups (4 recommendation-level).
D11 · Test Reliability
0 flaky across 1 measured tier(s). JavaScript/TypeScript (vitest via `pnpm install --frozen-lockfile --ignore-scripts` in the repository root (82 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in docs/ (0 tests); vitest via `pnpm install --frozen-lockfile --ignore-scripts` in website/ (0 tests)): measured (0 flaky).
D12 · Dependency Hygiene
14 outdated direct production npm dependency(ies) of 27 graded, 0 pinning defect(s), across 9 package.json (1 of them the product) and 9 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 1 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 1 Deprecated finding(s) in Dependency Hygiene — start with package.json. — One of this dimension's main actionable groups (1 warning-level).
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D14 · License Compliance
0 of 1273 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 1273 package(s) this repository's committed lockfile installs for a consumer — its 27 production, optional and peer dependency(ies), across 1 product package.json manifest(s), and everything those install in turn. Its 76 `devDependencies` declaration(s), and every package only they reach, are excluded: a consumer installs none of them. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. 1 of them publish no licence this pass can read on registry.npmjs.org — an absent field, `UNLICENSED`, or a `SEE LICENSE IN <file>` pointer into a tarball this pass does not download; that is missing data, not a violation, and none of them is charged. This repository publishes itself under 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
1 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is tsdown.config.mts. Counted over 9 of the 22 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
D17 · Explicit Debt
3 deducted task-comment markers across 3846 LoC (0.1/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 3 TodoComment finding(s) in Explicit Debt — start with reducers.test-d.ts (2), middleware.ts. — One of this dimension's main actionable groups (3 warning-level).
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 91 document(s) read across 3 unit(s).
D24 · Comment Value
0 of 74 judged comments only repeat the code they sit on (0.0 %). 2 comment(s) in another language or script were not judged.
D26 · Project Cohesion
0 of 3 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
17 % of calls cross a namespace and 0 % go through an interface, but 74 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
15 finding(s): 0 critical, 15 high, 0 medium, 0 low.
D29 · Static Analysis (SAST)
2 finding(s): 0 critical, 1 high, 1 medium, 0 low. semgrep hit a parse error in 4 file(s) — `src/types/store.ts` (lines 186–196), `REDACTED` (line 266, line 308, line 322, …), `website/plugins/remark-typescript-tools/linkDocblocks/plugin.ts` (line 79), `website/plugins/remark-typescript-tools/transpileCodeblocks/plugin.ts` (line 119, line 149, line 352, …) — 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 1 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 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
- Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
D30 · Dependency Vulnerabilities
495 finding(s): 74 critical, 262 high, 115 medium, 44 low.
What to do
- Resolve the 252 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (244), REDACTED (8). — One of this dimension's main actionable groups (252 issue-level).
- Resolve the 70 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (68), REDACTED (2). — One of this dimension's main actionable groups (70 issue-level).
- Resolve the 10 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (10). — One of this dimension's main actionable groups (10 issue-level).
D34 · Knowledge Freshness
4 of 9 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/combineReducers.ts. Counted over 9 of the 22 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 4 Orphaned file finding(s) in Knowledge Freshness — start with combineReducers.ts, mangleErrors.mts, actions.ts. — One of this dimension's main actionable groups (4 recommendation-level).
- Resolve the 1 Orphaned files with no living knowledge finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
D35 · Change Coupling
No strong hidden change-coupling between production files.
D36 · Supply-chain Provenance & Signing
2/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).
What to do
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
- Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-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
AX10 · Code composition
AX3 · Project dependency cycles
AX5 · Architecture & structure
AX6 · Interface segregation
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
M1 · Documentation (README)
What to do
- Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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
- docs/usage/UsageWithTypescript.md names Redux 9, but the manifest declares `redux` ^4.0.5. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/usage/UsageWithTypescript.md:84
What to do
- Reconcile the README with reality: docs/usage/UsageWithTypescript.md names Redux 9, but the manifest declares `redux` ^4.0.5.
P1 · CI/CD gates
P10 · Library API & versioning
P2 · Observability
- No logging call was found in the 42 JavaScript/TypeScript production file(s) this check read across 3 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
What to do
- Adopt pino (or winston) and log at meaningful points in the services you run.
- Add a health-check endpoint (@godaddy/terminus or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 4 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. — .github/workflows/release-commit.yml:5
- `REDACTED` schedules updates, but no `package-ecosystem` entry covers `github-actions`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — REDACTED:2
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.
- Dependabot is configured but does not watch `github-actions` — add that `package-ecosystem` entry to REDACTED so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback
P6 · Release Hygiene
PF3 · Async & latency hygiene
R1 · Type Safety
R10 · Code Duplication
- src/createStore.ts:47 · src/createStore.ts:83 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/createStore.ts:47
- src/createStore.ts:433 · src/createStore.ts:474 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — src/createStore.ts:433
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.
R2 · Cyclomatic Complexity
- ThrowStatement has cyclomatic complexity 14 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. — scripts/mangleErrors.mts:96
- combination 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. — src/combineReducers.ts:157
R3 · Large Files
- src/createStore.ts has 456 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — src/createStore.ts:1
What to do
- Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
R4 · Test Coverage
R5 · Dependency Freshness
R6 · Tooling
R7 · Dead Code
- Nothing imports this binding — it is safe to review for removal. — scripts/mangleErrors.mts:187
R8 · Dependency Hygiene
- Imported but not declared in any reachable package.json — installs work only by hoisting accident. — scripts/mangleErrors.mts:2
- Imported only as a TYPE and declared in no reachable package.json. The import is erased at compile time, so nothing is installed and no runtime resolution depends on it — but type-checking a clean clone will fail. Declare the typings it resolves through (or the package itself) in the owning package.json. — tsdown.config.mts:2
What to do
- Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports
S1 · Web-Security Posture
X12 · Unreachable branch
X13 · Undrained process stream
X16 · Unfloored truncation loop
X18 · Disposal-pattern correctness
X21 · Side-effecting pattern guard
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. — src/utils/warning.ts:17
What to do
- Swallowed exception (empty catch)
X5 · Nullable reference types
- ~0.8 `!` null assertions per 1k TypeScript source lines — 3 assertion(s) across the 3713 source line(s) of the 37 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: website/plugins/remark-typescript-tools/linkDocblocks/plugin.ts (1), website/plugins/remark-typescript-tools/transpileCodeblocks/compiler.ts (1), website/plugins/remark-typescript-tools/transpileCodeblocks/plugin.ts (1). Each one tells the compiler to trust the author about null, suppressing the very diagnostic `strictNullChecks` exists to produce. Many are correct: each is a claim the checker could not verify, and it is wrong only where the value can in fact be missing, so review the densest places first.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 76% | Adequate — gated by X3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 100% | Exemplary | Solid. |
| Maturity | 63% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 52% | Adequate — gated by P2, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 59% | Adequate — gated by D28 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Performance | 100% | Exemplary | Strongest area. |
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 — 71 check(s) not relevant to this codebase
- AC1 Text alternatives — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC2 Forms & labels — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC3 Page structure — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC4 Keyboard semantics — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC5 ARIA correctness — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AC6 Visual & motion safety — Frontend below the scale floor (3 DOM element(s) < 25) — too little surface to assess accessibility.
- AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's TypeScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
- AX2 Stateful singletons — Not applicable: TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
- AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
- AX7 Slice cohesion — vertical-slice architecture detected, but individual slices could not be resolved from namespaces or project layout
- 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 dev`) exited before it served a page. Likely cause (the repository): package.json has no "dev" script, so `npm run dev` could not start the app. Last output: "npm error Missing script: "dev" / npm error / npm error To see a list of scripts, run: / npm error npm run / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — this repo declares itself a template / kata / sample / demo; a formal ADR log is deferred to a real application built from it.
- D21 Naming Consistency — Naming consistency does not read html yet; 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
- 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) — 4 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.
- D4 Code Duplication — This repository's production source (.mts, .ts, .tsx) is not read by D4's token comparison, which compares .NET source: duplication in it is measured by R10 Code Duplication, the frontend lens's card running the same clone algorithm over the JS/TS token stream. Not scored here — read the R10 card for this repository's duplication.
- D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
- D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
- D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
- D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D6 Cohesion (LCOM4) — Cohesion (LCOM4) was not measured: of the 3 type(s) found, none both holds instance state and has two or more methods whose shared use of it could be read (1 stateless, 2 vendored from upstream), so LCOM4 is undefined for every type in this repository. Not scored — the metric does not apply here, and this is not a finding about this repository.
- 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 repository root runs vitest but declares no coverage provider, so the suite can run and still produce no lcov — add `@vitest/coverage-v8` (or `@vitest/coverage-istanbul`) as a devDependency. 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.
- 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 — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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.
- X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
- 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 — 338 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
- REDACTED
- REDACTED
- Unlisted import '@babel/helper-module-imports' scripts/mangleErrors.mts:2
Serious — 168 finding(s)
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- REDACTED
- No assertions: ActionCreator test/typescript/actionCreators.test-d.ts:17
- No assertions: bound test/typescript/actionCreators.test-d.ts:26
- No assertions: FSA test/typescript/actions.test-d.ts:4
- No assertions: FreeShapeAction test/typescript/actions.test-d.ts:17
- No assertions: StringLiteralTypeAction test/typescript/actions.test-d.ts:30
- No assertions: compose test/typescript/compose.test-d.ts:12
- No assertions: default Dispatch type accepts any object with `type` property. test/typescript/dispatch.test-d.ts:4
- No assertions: Dispatch accepts type argument that restricts allowed action types. test/typescript/dispatch.test-d.ts:16
- No assertions: Store enhancer that extends the type of dispatch. test/typescript/enhancers.test-d.ts:11
- No assertions: Store enhancer that extends the type of the state. test/typescript/enhancers.test-d.ts:50
- No assertions: Store enhancer that adds methods to the store. test/typescript/enhancers.test-d.ts:100
- No assertions: replaceReducer with a store enhancer test/typescript/enhancers.test-d.ts:121
- No assertions: mhelmersonExample test/typescript/enhancers.test-d.ts:195
- No assertions: state extension expected to work test/typescript/enhancers.test-d.ts:206
- No assertions: finalHelmersonExample test/typescript/enhancers.test-d.ts:296
- No assertions: composedEnhancers test/typescript/enhancers.test-d.ts:376
- No assertions: inject default dispatch. test/typescript/injectedDispatch.test-d.ts:16
- No assertions: inject dispatch that restricts allowed action types. test/typescript/injectedDispatch.test-d.ts:32
- No assertions: inject extended dispatch. test/typescript/injectedDispatch.test-d.ts:72
- No assertions: Logger middleware doesn't add any extra types to dispatch, just logs actions and state. test/typescript/middleware.test-d.ts:31
- No assertions: Promise middleware adds support for dispatching promises. test/typescript/middleware.test-d.ts:49
- No assertions: Thunk middleware adds support for dispatching thunks. test/typescript/middleware.test-d.ts:65
- No assertions: middleware that expects exact state type. test/typescript/middleware.test-d.ts:80
- No assertions: middleware that expects custom dispatch. test/typescript/middleware.test-d.ts:92
- No assertions: test the type of store.dispatch after applying different middleware. test/typescript/middleware.test-d.ts:111
- TodoComment test/typescript/reducers.test-d.ts:216
- TodoComment test/typescript/reducers.test-d.ts:272
- TodoComment src/types/middleware.ts:23
- Duplicated block (11 lines × 2 locations) src/createStore.ts:47
- Duplicated block (11 lines × 2 locations) src/createStore.ts:433
- createStore.createStore (cyclomatic 24) src/createStore.ts:86
- Deprecated: glob package.json:63
- createStore.createStore (cognitive 24) src/createStore.ts:86
- REDACTED
- Coverage not measured — JavaScript/TypeScript suite
- No structured logging
- Complex function ThrowStatement (cyclomatic 14, cognitive 14) scripts/mangleErrors.mts:96
- Complex function combination (cyclomatic 11, cognitive 14) src/combineReducers.ts:157
- src/createStore.ts: 456 lines of code src/createStore.ts:1
- Unlisted import 'rolldown' tsdown.config.mts:2
- Swallowed exception (empty catch) src/utils/warning.ts:17
Minor — 63 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
- Mock-dominated test: supports removing a subscription within a subscription test/createStore.spec.ts:290
- Mock-dominated test: notifies all subscribers about current dispatch regardless if any of them gets unsubscribed in the process test/createStore.spec.ts:313
- Mock-dominated test: notifies only subscribers active at the moment of current dispatch test/createStore.spec.ts:346
- Mock-dominated test: uses the last snapshot of subscribers during nested dispatch test/createStore.spec.ts:380
- Orphaned file src/combineReducers.ts:1
- Orphaned file scripts/mangleErrors.mts:1
- Orphaned file src/types/actions.ts:1
- Orphaned file src/bindActionCreators.ts:1
- Off-boarding risk: anonymized user #1
- Orphaned files with no living knowledge
- REDACTED
- REDACTED
- REDACTED
- No ADRs
- README/code drift docs/usage/UsageWithTypescript.md:84
- No SAST .github/workflows/release-commit.yml:5
- Dependabot does not watch github-actions REDACTED:2
- Unused export 'default' scripts/mangleErrors.mts:187
- Null assertions (`!`) override strict null checking
Minor — 18 finding(s)
- Outdated (npm): @dipakparmar/docusaurus-plugin-umami
- Outdated (npm): @microsoft/tsdoc
- Outdated (npm): @reduxjs/toolkit
- Outdated (npm): mdast-util-mdx-jsx
- Outdated (npm): oxc-transform
- Outdated (npm): oxfmt
- Outdated (npm): prop-types
- Outdated (npm): react
- Outdated (npm): react-dom
- Outdated (npm): react-lite-youtube-embed
- Outdated (npm): react-redux
- Outdated (npm): redux
- Outdated (npm): redux-thunk
- Outdated (npm): unist-util-visit
- Skipped (documented): (unnamed test) test/applyMiddleware.spec.ts:23
- Skipped (documented): (unnamed test) test/applyMiddleware.spec.ts:31
- Skipped (documented): (unnamed test) test/applyMiddleware.spec.ts:48
- Skipped (documented): (unnamed test) test/applyMiddleware.spec.ts:56
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-23b89eb602314b8eb10a2ccfda0bee74/history.json --exit-code 0 --source . | 10 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-23b89eb602314b8eb10a2ccfda0bee74/tree.json --exit-code 0 --source . | 54 | 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 . | 2 | 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/** . | 495 | 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 4 file(s) — `src/types/store.ts`, `REDACTED`, `website/plugins/remark-typescript-tools/linkDocblocks/plugin.ts`, `website/plugins/remark-typescript-tools/transpileCodeblocks/plugin.ts` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . | 0 | artifacts/raw/trivy-fs.json |