Executive summary
MichalPaszkiewicz/cqrs-react-router falls short of our standard for production because we found no working pipeline that builds or tests changes to the code and no automated security scanning of the code, its secrets or its dependencies. It scores 51 out of 100 and is rated Adequate, and neither of its two critical findings concerns security.
Production Readiness, at 37, is the weakest lens and counts most in the score. The best first steps are moving the pipeline to a build service that still runs and adding automated security scanning, each worth about 7 points. Raising Production Readiness to 70 would lift the score to about 64.
The loop of files that import each other needs breaking.
The product code is 940 lines, too few for a meaningful rebuild estimate.
If Production Readiness rose from 37 to 70, the lowest score rated Strong, the score would rise from 51 to about 64.
Top priorities
Diagnosis: what the measurements show together
Architecture: which parts of the code depend on which
| uses → | 1 helpers | 2 helpers.clock | 3 helpers.guid | 4 interfaces.iamacommand | 5 interfaces.iamavalueobject | 6 objects | 7 objects.domainerror | 8 objects.statereport | 9 interfaces.iamadomainevent | 10 objects.commandvalidator | 11 objects.navigatetopage | 12 objects.datedevent | 13 objects.view | 14 services.eventstore | 15 objects.aggregateroot | 16 objects.auditedevent | 17 objects.pagenavigated | 18 objects.route | 19 services.domainservice | 20 interfaces.iamacommandhandler | 21 objects.pagenavigationaggregate | 22 services.applicationservice | 23 objects.page | 24 objects.pagenavigationcommandhandler | 25 objects.router |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 helpers | |||||||||||||||||||||||||
| 2 helpers.clock | |||||||||||||||||||||||||
| 3 helpers.guid | |||||||||||||||||||||||||
| 4 interfaces.iamacommand | |||||||||||||||||||||||||
| 5 interfaces.iamavalueobject | |||||||||||||||||||||||||
| 6 objects | |||||||||||||||||||||||||
| 7 objects.domainerror | |||||||||||||||||||||||||
| 8 objects.statereport | |||||||||||||||||||||||||
| 9 interfaces.iamadomainevent | 1 | ||||||||||||||||||||||||
| 10 objects.commandvalidator | 1 | ||||||||||||||||||||||||
| 11 objects.navigatetopage | 1 | ||||||||||||||||||||||||
| 12 objects.datedevent | 1 | 1 | |||||||||||||||||||||||
| 13 objects.view | 1 | ||||||||||||||||||||||||
| 14 services.eventstore | 1 | 1 | |||||||||||||||||||||||
| 15 objects.aggregateroot | 1 | 1 | |||||||||||||||||||||||
| 16 objects.auditedevent | 1 | 1 | |||||||||||||||||||||||
| 17 objects.pagenavigated | 1 | ||||||||||||||||||||||||
| 18 objects.route | 1 | 1 | |||||||||||||||||||||||
| 19 services.domainservice | 1 | 1 | |||||||||||||||||||||||
| 20 interfaces.iamacommandhandler | 1 | 1 | |||||||||||||||||||||||
| 21 objects.pagenavigationaggregate | 1 | 1 | 1 | ||||||||||||||||||||||
| 22 services.applicationservice | 1 | 1 | 1 | 1 | 1 | 1 | 1 | ||||||||||||||||||
| 23 objects.page | 1 | ||||||||||||||||||||||||
| 24 objects.pagenavigationcommandhandler | 1 | 1 | 1 | ||||||||||||||||||||||
| 25 objects.router | 1 |
9→2 interfaces.iamadomainevent uses helpers.clock✕
- Connections
- 1 pair of types, where a type in interfaces.iamadomainevent uses a type in helpers.clock.
- The types involved
src.interfaces.iamadomainevent.IAmADomainEvent→src.helpers.clock.ClockDate
- Direction
- interfaces.iamadomainevent uses helpers.clock, so a change to helpers.clock can break interfaces.iamadomainevent, while a change to interfaces.iamadomainevent can't break helpers.clock.
- Position
- Below the diagonal: interfaces.iamadomainevent uses a module listed above it, which is the healthy direction.
10→4 objects.commandvalidator uses interfaces.iamacommand✕
- Connections
- 1 pair of types, where a type in objects.commandvalidator uses a type in interfaces.iamacommand.
- The types involved
src.objects.commandvalidator.CommandValidator→src.interfaces.iamacommand.IAmACommand
- Direction
- objects.commandvalidator uses interfaces.iamacommand, so a change to interfaces.iamacommand can break objects.commandvalidator, while a change to objects.commandvalidator can't break interfaces.iamacommand.
- Position
- Below the diagonal: objects.commandvalidator uses a module listed above it, which is the healthy direction.
11→4 objects.navigatetopage uses interfaces.iamacommand✕
- Connections
- 1 pair of types, where a type in objects.navigatetopage uses a type in interfaces.iamacommand.
- The types involved
src.objects.navigatetopage.NavigateToPageCommand→src.interfaces.iamacommand.IAmACommand
- Direction
- objects.navigatetopage uses interfaces.iamacommand, so a change to interfaces.iamacommand can break objects.navigatetopage, while a change to objects.navigatetopage can't break interfaces.iamacommand.
- Position
- Below the diagonal: objects.navigatetopage uses a module listed above it, which is the healthy direction.
12→2 objects.datedevent uses helpers.clock✕
- Connections
- 1 pair of types, where a type in objects.datedevent uses a type in helpers.clock.
- The types involved
src.objects.datedevent.DatedEvent→src.helpers.clock.ClockDate
- Direction
- objects.datedevent uses helpers.clock, so a change to helpers.clock can break objects.datedevent, while a change to objects.datedevent can't break helpers.clock.
- Position
- Below the diagonal: objects.datedevent uses a module listed above it, which is the healthy direction.
12→9 objects.datedevent uses interfaces.iamadomainevent✕
- Connections
- 1 pair of types, where a type in objects.datedevent uses a type in interfaces.iamadomainevent.
- The types involved
src.objects.datedevent.DatedEvent→src.interfaces.iamadomainevent.IAmADomainEvent
- Direction
- objects.datedevent uses interfaces.iamadomainevent, so a change to interfaces.iamadomainevent can break objects.datedevent, while a change to objects.datedevent can't break interfaces.iamadomainevent.
- Position
- Below the diagonal: objects.datedevent uses a module listed above it, which is the healthy direction.
13→9 objects.view uses interfaces.iamadomainevent✕
- Connections
- 1 pair of types, where a type in objects.view uses a type in interfaces.iamadomainevent.
- The types involved
src.objects.view.View→src.interfaces.iamadomainevent.IAmADomainEvent
- Direction
- objects.view uses interfaces.iamadomainevent, so a change to interfaces.iamadomainevent can break objects.view, while a change to objects.view can't break interfaces.iamadomainevent.
- Position
- Below the diagonal: objects.view uses a module listed above it, which is the healthy direction.
14→2 services.eventstore uses helpers.clock✕
- Connections
- 1 pair of types, where a type in services.eventstore uses a type in helpers.clock.
- The types involved
src.services.eventstore.EventStore→src.helpers.clock.ClockDate
- Direction
- services.eventstore uses helpers.clock, so a change to helpers.clock can break services.eventstore, while a change to services.eventstore can't break helpers.clock.
- Position
- Below the diagonal: services.eventstore uses a module listed above it, which is the healthy direction.
14→9 services.eventstore uses interfaces.iamadomainevent✕
- Connections
- 1 pair of types, where a type in services.eventstore uses a type in interfaces.iamadomainevent.
- The types involved
src.services.eventstore.EventStore→src.interfaces.iamadomainevent.IAmADomainEvent
- Direction
- services.eventstore uses interfaces.iamadomainevent, so a change to interfaces.iamadomainevent can break services.eventstore, while a change to services.eventstore can't break interfaces.iamadomainevent.
- Position
- Below the diagonal: services.eventstore uses a module listed above it, which is the healthy direction.
15→9 objects.aggregateroot uses interfaces.iamadomainevent✕
- Connections
- 1 pair of types, where a type in objects.aggregateroot uses a type in interfaces.iamadomainevent.
- The types involved
src.objects.aggregateroot.AggregateRoot→src.interfaces.iamadomainevent.IAmADomainEvent
- Direction
- objects.aggregateroot uses interfaces.iamadomainevent, so a change to interfaces.iamadomainevent can break objects.aggregateroot, while a change to objects.aggregateroot can't break interfaces.iamadomainevent.
- Position
- Below the diagonal: objects.aggregateroot uses a module listed above it, which is the healthy direction.
15→14 objects.aggregateroot uses services.eventstore✕
- Connections
- 1 pair of types, where a type in objects.aggregateroot uses a type in services.eventstore.
- The types involved
src.objects.aggregateroot.AggregateRoot→src.services.eventstore.EventStore
- Direction
- objects.aggregateroot uses services.eventstore, so a change to services.eventstore can break objects.aggregateroot, while a change to objects.aggregateroot can't break services.eventstore.
- Position
- Below the diagonal: objects.aggregateroot uses a module listed above it, which is the healthy direction.
16→2 objects.auditedevent uses helpers.clock✕
- Connections
- 1 pair of types, where a type in objects.auditedevent uses a type in helpers.clock.
- The types involved
src.objects.auditedevent.AuditedEvent→src.helpers.clock.ClockDate
- Direction
- objects.auditedevent uses helpers.clock, so a change to helpers.clock can break objects.auditedevent, while a change to objects.auditedevent can't break helpers.clock.
- Position
- Below the diagonal: objects.auditedevent uses a module listed above it, which is the healthy direction.
16→12 objects.auditedevent uses objects.datedevent✕
- Connections
- 1 pair of types, where a type in objects.auditedevent uses a type in objects.datedevent.
- The types involved
src.objects.auditedevent.AuditedEvent→src.objects.datedevent.DatedEvent
- Direction
- objects.auditedevent uses objects.datedevent, so a change to objects.datedevent can break objects.auditedevent, while a change to objects.auditedevent can't break objects.datedevent.
- Position
- Below the diagonal: objects.auditedevent uses a module listed above it, which is the healthy direction.
17→12 objects.pagenavigated uses objects.datedevent✕
- Connections
- 1 pair of types, where a type in objects.pagenavigated uses a type in objects.datedevent.
- The types involved
src.objects.pagenavigated.PageNavigatedEvent→src.objects.datedevent.DatedEvent
- Direction
- objects.pagenavigated uses objects.datedevent, so a change to objects.datedevent can break objects.pagenavigated, while a change to objects.pagenavigated can't break objects.datedevent.
- Position
- Below the diagonal: objects.pagenavigated uses a module listed above it, which is the healthy direction.
18→9 objects.route uses interfaces.iamadomainevent✕
- Connections
- 1 pair of types, where a type in objects.route uses a type in interfaces.iamadomainevent.
- The types involved
src.objects.route.PageNavigationView→src.interfaces.iamadomainevent.IAmADomainEvent
- Direction
- objects.route uses interfaces.iamadomainevent, so a change to interfaces.iamadomainevent can break objects.route, while a change to objects.route can't break interfaces.iamadomainevent.
- Position
- Below the diagonal: objects.route uses a module listed above it, which is the healthy direction.
18→13 objects.route uses objects.view✕
- Connections
- 1 pair of types, where a type in objects.route uses a type in objects.view.
- The types involved
src.objects.route.PageNavigationView→src.objects.view.View
- Direction
- objects.route uses objects.view, so a change to objects.view can break objects.route, while a change to objects.route can't break objects.view.
- Position
- Below the diagonal: objects.route uses a module listed above it, which is the healthy direction.
19→9 services.domainservice uses interfaces.iamadomainevent✕
- Connections
- 1 pair of types, where a type in services.domainservice uses a type in interfaces.iamadomainevent.
- The types involved
src.services.domainservice.DomainService→src.interfaces.iamadomainevent.IAmADomainEvent
- Direction
- services.domainservice uses interfaces.iamadomainevent, so a change to interfaces.iamadomainevent can break services.domainservice, while a change to services.domainservice can't break interfaces.iamadomainevent.
- Position
- Below the diagonal: services.domainservice uses a module listed above it, which is the healthy direction.
19→14 services.domainservice uses services.eventstore✕
- Connections
- 1 pair of types, where a type in services.domainservice uses a type in services.eventstore.
- The types involved
src.services.domainservice.DomainService→src.services.eventstore.EventStore
- Direction
- services.domainservice uses services.eventstore, so a change to services.eventstore can break services.domainservice, while a change to services.domainservice can't break services.eventstore.
- Position
- Below the diagonal: services.domainservice uses a module listed above it, which is the healthy direction.
20→4 interfaces.iamacommandhandler uses interfaces.iamacommand✕
- Connections
- 1 pair of types, where a type in interfaces.iamacommandhandler uses a type in interfaces.iamacommand.
- The types involved
src.interfaces.iamacommandhandler.IAmACommandHandler→src.interfaces.iamacommand.IAmACommand
- Direction
- interfaces.iamacommandhandler uses interfaces.iamacommand, so a change to interfaces.iamacommand can break interfaces.iamacommandhandler, while a change to interfaces.iamacommandhandler can't break interfaces.iamacommand.
- Position
- Below the diagonal: interfaces.iamacommandhandler uses a module listed above it, which is the healthy direction.
20→19 interfaces.iamacommandhandler uses services.domainservice✕
- Connections
- 1 pair of types, where a type in interfaces.iamacommandhandler uses a type in services.domainservice.
- The types involved
src.interfaces.iamacommandhandler.IAmACommandHandler→src.services.domainservice.DomainService
- Direction
- interfaces.iamacommandhandler uses services.domainservice, so a change to services.domainservice can break interfaces.iamacommandhandler, while a change to interfaces.iamacommandhandler can't break services.domainservice.
- Position
- Below the diagonal: interfaces.iamacommandhandler uses a module listed above it, which is the healthy direction.
21→9 objects.pagenavigationaggregate uses interfaces.iamadomainevent✕
- Connections
- 1 pair of types, where a type in objects.pagenavigationaggregate uses a type in interfaces.iamadomainevent.
- The types involved
src.objects.pagenavigationaggregate.PageNavigationAggregate→src.interfaces.iamadomainevent.IAmADomainEvent
- Direction
- objects.pagenavigationaggregate uses interfaces.iamadomainevent, so a change to interfaces.iamadomainevent can break objects.pagenavigationaggregate, while a change to objects.pagenavigationaggregate can't break interfaces.iamadomainevent.
- Position
- Below the diagonal: objects.pagenavigationaggregate uses a module listed above it, which is the healthy direction.
21→11 objects.pagenavigationaggregate uses objects.navigatetopage✕
- Connections
- 1 pair of types, where a type in objects.pagenavigationaggregate uses a type in objects.navigatetopage.
- The types involved
src.objects.pagenavigationaggregate.PageNavigationAggregate→src.objects.navigatetopage.NavigateToPageCommand
- Direction
- objects.pagenavigationaggregate uses objects.navigatetopage, so a change to objects.navigatetopage can break objects.pagenavigationaggregate, while a change to objects.pagenavigationaggregate can't break objects.navigatetopage.
- Position
- Below the diagonal: objects.pagenavigationaggregate uses a module listed above it, which is the healthy direction.
21→15 objects.pagenavigationaggregate uses objects.aggregateroot✕
- Connections
- 1 pair of types, where a type in objects.pagenavigationaggregate uses a type in objects.aggregateroot.
- The types involved
src.objects.pagenavigationaggregate.PageNavigationAggregate→src.objects.aggregateroot.AggregateRoot
- Direction
- objects.pagenavigationaggregate uses objects.aggregateroot, so a change to objects.aggregateroot can break objects.pagenavigationaggregate, while a change to objects.pagenavigationaggregate can't break objects.aggregateroot.
- Position
- Below the diagonal: objects.pagenavigationaggregate uses a module listed above it, which is the healthy direction.
22→2 services.applicationservice uses helpers.clock✕
- Connections
- 1 pair of types, where a type in services.applicationservice uses a type in helpers.clock.
- The types involved
src.services.applicationservice.ApplicationService→src.helpers.clock.ClockDate
- Direction
- services.applicationservice uses helpers.clock, so a change to helpers.clock can break services.applicationservice, while a change to services.applicationservice can't break helpers.clock.
- Position
- Below the diagonal: services.applicationservice uses a module listed above it, which is the healthy direction.
22→4 services.applicationservice uses interfaces.iamacommand✕
- Connections
- 1 pair of types, where a type in services.applicationservice uses a type in interfaces.iamacommand.
- The types involved
src.services.applicationservice.ApplicationService→src.interfaces.iamacommand.IAmACommand
- Direction
- services.applicationservice uses interfaces.iamacommand, so a change to interfaces.iamacommand can break services.applicationservice, while a change to services.applicationservice can't break interfaces.iamacommand.
- Position
- Below the diagonal: services.applicationservice uses a module listed above it, which is the healthy direction.
22→8 services.applicationservice uses objects.statereport✕
- Connections
- 1 pair of types, where a type in services.applicationservice uses a type in objects.statereport.
- The types involved
src.services.applicationservice.ApplicationService→src.objects.statereport.StateReport
- Direction
- services.applicationservice uses objects.statereport, so a change to objects.statereport can break services.applicationservice, while a change to services.applicationservice can't break objects.statereport.
- Position
- Below the diagonal: services.applicationservice uses a module listed above it, which is the healthy direction.
22→9 services.applicationservice uses interfaces.iamadomainevent✕
- Connections
- 1 pair of types, where a type in services.applicationservice uses a type in interfaces.iamadomainevent.
- The types involved
src.services.applicationservice.ApplicationService→src.interfaces.iamadomainevent.IAmADomainEvent
- Direction
- services.applicationservice uses interfaces.iamadomainevent, so a change to interfaces.iamadomainevent can break services.applicationservice, while a change to services.applicationservice can't break interfaces.iamadomainevent.
- Position
- Below the diagonal: services.applicationservice uses a module listed above it, which is the healthy direction.
22→13 services.applicationservice uses objects.view✕
- Connections
- 1 pair of types, where a type in services.applicationservice uses a type in objects.view.
- The types involved
src.services.applicationservice.ApplicationService→src.objects.view.View
- Direction
- services.applicationservice uses objects.view, so a change to objects.view can break services.applicationservice, while a change to services.applicationservice can't break objects.view.
- Position
- Below the diagonal: services.applicationservice uses a module listed above it, which is the healthy direction.
22→19 services.applicationservice uses services.domainservice✕
- Connections
- 1 pair of types, where a type in services.applicationservice uses a type in services.domainservice.
- The types involved
src.services.applicationservice.ApplicationService→src.services.domainservice.DomainService
- Direction
- services.applicationservice uses services.domainservice, so a change to services.domainservice can break services.applicationservice, while a change to services.applicationservice can't break services.domainservice.
- Position
- Below the diagonal: services.applicationservice uses a module listed above it, which is the healthy direction.
22→23 services.applicationservice uses objects.page part of a loop✕
- Connections
- 1 pair of types, where a type in services.applicationservice uses a type in objects.page.
- The types involved
src.services.applicationservice.ApplicationService→src.objects.page.Page
- Direction
- services.applicationservice uses objects.page, so a change to objects.page can break services.applicationservice, while a change to services.applicationservice can't break objects.page.
- Position
- Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
23→22 objects.page uses services.applicationservice✕
- Connections
- 1 pair of types, where a type in objects.page uses a type in services.applicationservice.
- The types involved
src.objects.page.PageProps→src.services.applicationservice.ApplicationService
- Direction
- objects.page uses services.applicationservice, so a change to services.applicationservice can break objects.page, while a change to objects.page can't break services.applicationservice.
- Position
- Below the diagonal: objects.page uses a module listed above it, which is the healthy direction.
24→4 objects.pagenavigationcommandhandler uses interfaces.iamacommand✕
- Connections
- 1 pair of types, where a type in objects.pagenavigationcommandhandler uses a type in interfaces.iamacommand.
- The types involved
src.objects.pagenavigationcommandhandler.PageNavigationCommandHandler→src.interfaces.iamacommand.IAmACommand
- Direction
- objects.pagenavigationcommandhandler uses interfaces.iamacommand, so a change to interfaces.iamacommand can break objects.pagenavigationcommandhandler, while a change to objects.pagenavigationcommandhandler can't break interfaces.iamacommand.
- Position
- Below the diagonal: objects.pagenavigationcommandhandler uses a module listed above it, which is the healthy direction.
24→19 objects.pagenavigationcommandhandler uses services.domainservice✕
- Connections
- 1 pair of types, where a type in objects.pagenavigationcommandhandler uses a type in services.domainservice.
- The types involved
src.objects.pagenavigationcommandhandler.PageNavigationCommandHandler→src.services.domainservice.DomainService
- Direction
- objects.pagenavigationcommandhandler uses services.domainservice, so a change to services.domainservice can break objects.pagenavigationcommandhandler, while a change to objects.pagenavigationcommandhandler can't break services.domainservice.
- Position
- Below the diagonal: objects.pagenavigationcommandhandler uses a module listed above it, which is the healthy direction.
24→20 objects.pagenavigationcommandhandler uses interfaces.iamacommandhandler✕
- Connections
- 1 pair of types, where a type in objects.pagenavigationcommandhandler uses a type in interfaces.iamacommandhandler.
- The types involved
src.objects.pagenavigationcommandhandler.PageNavigationCommandHandler→src.interfaces.iamacommandhandler.IAmACommandHandler
- Direction
- objects.pagenavigationcommandhandler uses interfaces.iamacommandhandler, so a change to interfaces.iamacommandhandler can break objects.pagenavigationcommandhandler, while a change to objects.pagenavigationcommandhandler can't break interfaces.iamacommandhandler.
- Position
- Below the diagonal: objects.pagenavigationcommandhandler uses a module listed above it, which is the healthy direction.
25→22 objects.router uses services.applicationservice✕
- Connections
- 1 pair of types, where a type in objects.router uses a type in services.applicationservice.
- The types involved
src.objects.router.RouterProps→src.services.applicationservice.ApplicationService
- Direction
- objects.router uses services.applicationservice, so a change to services.applicationservice can break objects.router, while a change to objects.router can't break services.applicationservice.
- Position
- Below the diagonal: objects.router uses a module listed above it, which is the healthy direction.
At a glance — Code Health
At a glance — Architecture
At a glance — Maturity
At a glance — Readiness
At a glance — Security
At a glance — Domain Modelling
Security & Compliance — OWASP Top-10 mapping
| OWASP category | Findings | Severity |
|---|---|---|
| A05:2025 — Injection | 1 | Medium |
Roadmap
Top priorities: Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists; 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; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
| Do this | Helps | Effort | Dimension |
|---|---|---|---|
| Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists. | +6.9 pts | Medium | CI/CD gates |
| 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. | +6.9 pts | Medium | Security & performance tooling |
| 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. | +4.1 pts | Medium | Architecture documentation |
| Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release. | +2.2 pts | Medium | Release Hygiene |
| Add tests that import the unreached modules (directly or through their public entry). | +2.1 pts | Medium | Test Coverage |
| Add an 'Architecture' / 'How it works' section to the root README — the high-level shape. | +1.9 pts | Medium | Documentation (README) |
| Add eslint as package.json scripts and run them in CI. | +1.3 pts | Medium | Tooling |
| 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 `?`). | +0.7 pts | Medium | Nullable reference types |
File quality
| File | Score | Band | Worst signal |
|---|---|---|---|
| src/helpers/clock.ts | 7.8 | Mixed | Cognitive Complexity: clock.fixDates (cognitive 27) |
| REDACTED | 7.9 | Mixed | Static Analysis (SAST): Medium: REDACTED |
| src/services/applicationservice.ts | 8.5 | Near-clean | Cognitive Complexity: ApplicationService.handleCommand (cognitive 16) |
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 64 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
What we checked — 64 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, 37 of 49 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line.
- Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
- Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
Tools & methods
| Method | Backs | Version | Evaluator |
|---|---|---|---|
| Roslyn static analysis | Complexity, cohesion, coupling, dead code, API surface, layering | 5.3.0 | ✓ deterministic |
| Native secret scanner | Hardcoded secrets / credentials | 1.0.0 | ✓ deterministic |
| Canine Code Analyzer duplication detector (in-process) | Code duplication | 1.0.0 | ✓ deterministic |
| Coverage (coverlet / dotnet-coverage) | Line & branch coverage | 10.0.400 | ✓ deterministic |
| NuGet / dotnet | Outdated, vulnerable & deprecated dependencies | 10.0.400 | ✓ deterministic |
| git / LibGit2Sharp | Churn hotspots, knowledge concentration, history | 2.43.0 · 0.31.0 | ✓ deterministic |
| gitleaks · semgrep · trivy | Secrets in history, SAST, CVEs, IaC & container, PII / GDPR | 1.86.0 · 0.69.3 | ✓ deterministic |
Run transparency — what happened this run
- D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test reliability not scored — the JavaScript/TypeScript suite (jest via `npm install --ignore-scripts` (no lockfile) in the repository root (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
- D12 Dependency Hygiene — 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. This repository's 1 package.json manifest(s) WERE read and their pinning discipline assessed; what went unanswered is the currency half, because answering it needs a lockfile resolved to CONCRETE versions and this repository commits none — a package.json states version RANGES, and a range names no particular release to be behind. So registry.npmjs.org was never asked, and there was nothing here for it to grade. This is a true statement about the repository and NOT a gap on our side: no lockfile reader we could write would find anything here to read, so there is no capability behind this row to build.
- D14 License Compliance — 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. Not scored — this repository declares package.json manifests but commits no lockfile this pass can resolve (npm, pnpm, yarn and bun each write a different one, and `bun.lockb` is a binary format with no published shape), so the set of packages it actually ships is not resolvable from the checkout: its declarations carry version RANGES, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. Commit the lock and this dimension grades its production dependencies against registry.npmjs.org. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
- D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. Too few commits for a meaningful bus factor (37 commit(s) sampled, fewer than the 50 this dimension needs before a bus factor means anything).
- D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
- D30 Dependency Vulnerabilities — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- D34 Knowledge Freshness — 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. Too few commits to judge knowledge freshness (37 commit(s) sampled).
- D43 Malicious Dependencies — measured, with a gap in what it reached — 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. The scanner produced no output at all, so no dependency was actually scanned. 1 of 2 declared ecosystem(s) (npm) WERE scanned and every vulnerability they reported is included in this result; osv was not, so this dimension's score covers less than the dependency surface this repository declares, and nothing here is evidence that osv is free of known-vulnerable dependencies. osv: the scanner produced no output at all, so no dependency was actually scanned. This is reported as a measurement gap rather than a clean pass. osv-scanner documents exit 128 as "no package sources found" — but this scan only invoked it because the tree declares a source it supports (`pom.xml` and the resolved lockfiles among them), so the tool's report and this repository disagree. Check that those sources are reachable from the directory the scan ran in before concluding anything is missing. If this tree really does commit only range-pinned manifests, commit the lockfile your package manager produces — but only where your ecosystem HAS one and commits it: Maven has none at all (osv-scanner reads `pom.xml` directly) and Gradle writes one only under opt-in dependency locking, while a published Composer package and a published Dart library both deliberately exclude theirs. In those three, generate one in CI before the scan instead — a resolved dependency list or an SBOM fed to the scanner.
- AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Subject: 2 markup document(s) — HTML, Razor, JSX, Vue, Svelte or server templates. The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
- DM9 Scattered domain decisions — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Arm two tells a construction that PRODUCES a measurement from one that merely passes it along, and this repository's frontend does not compute that fact. A measurement built independently in two places would not appear above.
- 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.
- S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 26 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled certificate validation, obsolete TLS versions, plaintext password storage and session cookies set without HttpOnly, Secure or SameSite, and none was found. The server controls this dimension also scores were not assessed, so no score is given.
- X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
- X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Java, Kotlin, Python, PHP, Dart, Ruby, Scala and Rust source only, and no C# was loaded, and this repository's JavaScript/TypeScript, Python and PHP 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.
- D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
- D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
- D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
- D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
- D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
- 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.
- 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.
- D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
- D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
- D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a Dockerfile (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
- AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
- DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
- P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
Dimensions
D1 · Cyclomatic Complexity
0 method(s) exceeded the cyclomatic complexity threshold of 15.
D2 · Cognitive Complexity
2 method(s) exceeded the cognitive complexity threshold of 15; the worst was clock.fixDates at 27.
What to do
- Bring the 2 bodies over 15 down to 15 or less in Cognitive Complexity — start with clock.fixDates (cognitive 27), ApplicationService.handleCommand (cognitive 16). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 9.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
- Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D3 · God Classes
1 god class(es) detected.
What to do
- Resolve the 1 TooManyMethods finding(s) in God Classes — start with clock.ts. — One of this dimension's main actionable groups (1 warning-level).
- Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
D6 · Cohesion (LCOM4)
0 of 6 classes have LCOM4 above 3.
D9 · Test Distribution
40 test methods: 40 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 40 `it`/`test` case(s) across 8 test file(s) declaring at least one; its tier split is read from package names and paths only.
D10 · Test Quality
0 skipped, 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 40 tests.
D13 · Secret Scanning
Secret scan ran and found no leaked secrets.
D15 · Churn × Complexity Hotspots
No churn × complexity hotspots in the window.
D17 · Explicit Debt
0 deducted task-comment markers across 929 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
D19 · Documentation Quality
1 of 1 documentation facets pass in full. 1 document(s) read across 1 unit(s).
D26 · Project Cohesion
0 of 1 build units (npm) flagged as possibly oversized/incoherent.
D27 · Navigability
39 % of calls cross a namespace and 2 % go through an interface, but 45 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What to do
- Improve Navigability — currently 8.8/10. — 39 % of calls cross a namespace and 2 % go through an interface, but 45 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
D28 · Secrets (history)
gitleaks scanned the full history AND the current working tree and found no secrets.
D29 · Static Analysis (SAST)
1 finding(s): 0 critical, 0 high, 1 medium, 0 low.
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 warning-level).
D30 · Dependency Vulnerabilities
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D35 · Change Coupling
No strong hidden change-coupling between production files.
D43 · Malicious Dependencies
No known-vulnerable dependencies in the 1 ecosystem(s) that were scanned (npm). Partial dependency scan: 1 of 2 declared ecosystem(s) were scanned (npm), and the findings above are real and complete for them. osv was not scanned (osv: the scanner produced no output at all, so no dependency was actually scanned), so this is not the whole dependency surface and the result is reported at reduced confidence.
D44 · Platform End-of-Life
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 5 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Frontend & cross-cutting dimensions
AX10 · Code composition
What to do
- The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
AX3 · Project dependency cycles
AX4 · Dependency direction
AX6 · Interface segregation
DM1 · Aggregate boundaries
DM11 · Constructible invalid state
DM4 · Rich vs anemic model
- `TestAggregate` is an aggregate/entity with 1 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. (×2) — tests/objects/aggregateroot.ts:39, tests/objects/aggregateroot.ts:66
What to do
- Move business rules onto the aggregates/entities they govern so invariants are enforced at the source, not in anemic services.
DM5 · Encapsulated state
- `TestAggregate` exposes publicly writable state (ID). (×2) — tests/objects/aggregateroot.ts:39, tests/objects/aggregateroot.ts:66
- `SingleCommandOnlyPleaseAggregateRoot` exposes publicly writable state (actionCount). — tests/services/applicationservice.ts:124
What to do
- Make entity setters private/init-only and hand collections out as IReadOnlyList/IReadOnlyCollection over a private backing field; change state only through methods that enforce the invariants (Marten/EF can bind via constructor or private setters).
DM9 · Scattered domain decisions
GD1 · Unfinished & placeholder code
IC1 · Incompleteness & stubs
- `getViewByName` takes parameters but its body is empty — it accepts inputs and does nothing. Either implement it or remove it. — src/objects/commandvalidator.ts:7
What to do
- Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
M1 · Documentation (README)
What to do
- Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
M2 · Architecture documentation
- No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
- No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
- Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
- Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure
P1 · CI/CD gates
- The pipeline is well-formed, but the only CI definition is `.travis.yml`, and its `README.md` build badge still points at `travis-ci.org` — a service shut down in June 2021. No other CI is configured in this repository, so nothing has been building or testing changes here since that shutdown — the steps below describe a gate that is not running. Porting it is mostly mechanical: the build and test commands already written here are what a replacement pipeline would run.
What to do
- Port the existing pipeline to a CI service that is still operating — the build and test steps are already specified — and remove the dead configuration and its badge so the repository stops advertising a gate that no longer exists.
P10 · Library API & versioning
P3 · Security & performance tooling
- No static application security testing detected. For this repository's stack, add CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security as a CI step. What was searched, so you can tell an absence from a miss: the 36 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
- `package.json` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — package.json:17
What to do
- Add a SAST step to CI running what this repository's stack ships: CodeQL's javascript-typescript pack, `semgrep --config=p/typescript`, or eslint-plugin-security — so a security regression fails the build instead of landing.
- Enable Dependabot/Renovate or a dependency-review gate.
- Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene
- No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
- Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
R1 · Type Safety
- 33 typed · 1 plain JS — the untyped files are preprocessor.js. tsconfig.json switches off noImplicitAny, so the typed files are only partly type-checked.
What to do
- Migrate the remaining .js/.jsx files to TypeScript.
R10 · Code Duplication
- src/services/eventstore.ts:16 · src/services/eventstore.ts:49 — the two spans are one implementation copied and then locally edited — 72 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — src/services/eventstore.ts:16
- src/services/applicationservice.ts:150 · src/services/applicationservice.ts:214 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — src/services/applicationservice.ts:150
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
- fixDates has cyclomatic complexity 11 and cognitive complexity 27; 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/helpers/clock.ts:97
R3 · Large Files
R4 · Test Coverage
- No test imports this module directly or transitively. Import reachability cannot see a test that executes a file by path instead of importing it, nor one that drives it through a running browser by navigating to a URL — if neither does, no test reaches this one. (×10) — src/objects/route.tsx:1, REDACTED:1, src/objects/router.tsx:1, …
What to do
- Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling
- test ✓ · lint ✗ · typecheck ✓ — read from this repository's package.json scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
- Add eslint as package.json scripts and run them in CI.
R7 · Dead Code
- Unreachable from the 1 application, 0 tooling and 8 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
- no import path from any entry point (1 application, 0 tooling, 8 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make — preprocessor.js
- dist/interfaces/iamanaction.js.map sits in 'dist', which tsconfig.json declares as this project's outDir, so it is committed compiler output; the map itself records that it was generated from 'src/interfaces/iamanaction.ts', and no such file exists in the repository — its emitted file 'dist/interfaces/iamanaction.js' is still committed beside it and is stale for the same reason. 25 other map(s) in the same directory resolve to sources that do exist, which is what makes the absence provable rather than a path-resolution gap. Delete the orphaned artefact(s), or stop committing the output directory and let the build produce it. — dist/interfaces/iamanaction.js.map
- dist/interfaces/iamanaggregateroot.js.map sits in 'dist', which tsconfig.json declares as this project's outDir, so it is committed compiler output; the map itself records that it was generated from 'src/interfaces/iamanaggregateroot.ts', and no such file exists in the repository — its emitted file 'dist/interfaces/iamanaggregateroot.js' is still committed beside it and is stale for the same reason. 25 other map(s) in the same directory resolve to sources that do exist, which is what makes the absence provable rather than a path-resolution gap. Delete the orphaned artefact(s), or stop committing the output directory and let the build produce it. — dist/interfaces/iamanaggregateroot.js.map
- dist/objects/auditedaction.js.map sits in 'dist', which tsconfig.json declares as this project's outDir, so it is committed compiler output; the map itself records that it was generated from 'src/objects/auditedaction.ts', and no such file exists in the repository — its emitted file 'dist/objects/auditedaction.js' is still committed beside it and is stale for the same reason. 25 other map(s) in the same directory resolve to sources that do exist, which is what makes the absence provable rather than a path-resolution gap. Delete the orphaned artefact(s), or stop committing the output directory and let the build produce it. — dist/objects/auditedaction.js.map
- dist/objects/datedaction.js.map sits in 'dist', which tsconfig.json declares as this project's outDir, so it is committed compiler output; the map itself records that it was generated from 'src/objects/datedaction.ts', and no such file exists in the repository — its emitted file 'dist/objects/datedaction.js' is still committed beside it and is stale for the same reason. 25 other map(s) in the same directory resolve to sources that do exist, which is what makes the absence provable rather than a path-resolution gap. Delete the orphaned artefact(s), or stop committing the output directory and let the build produce it. — dist/objects/datedaction.js.map
- dist/services/actionstore.js.map sits in 'dist', which tsconfig.json declares as this project's outDir, so it is committed compiler output; the map itself records that it was generated from 'src/services/actionstore.ts', and no such file exists in the repository — its emitted file 'dist/services/actionstore.js' is still committed beside it and is stale for the same reason. 25 other map(s) in the same directory resolve to sources that do exist, which is what makes the absence provable rather than a path-resolution gap. Delete the orphaned artefact(s), or stop committing the output directory and let the build produce it. — dist/services/actionstore.js.map
- This top-level declaration is not exported and its name occurs nowhere else in its module — not called, read, typed against, re-exported or named by a string. Nothing outside the module can reach a non-exported binding, so this is the whole search: remove it, or use it. (×4) — src/objects/route.tsx:18, src/objects/route.tsx:28, tests/services/viewsubscriber.ts:23, …
What to do
- Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
R8 · Dependency Hygiene
R9 · Circular Imports
- src/objects/page.tsx → src/services/applicationservice.ts → src/objects/page.tsx — src/objects/page.tsx:2
What to do
- Break each cycle by extracting the shared piece into a module both sides can import.
X1 · Async correctness
X12 · Unreachable branch
X13 · Undrained process stream
X14 · Bypassable address classification
X15 · Unvalidated length from an untrusted reader
X16 · Unfloored truncation loop
X17 · Uncapped recursion over a caller-supplied document
- `fixDates` is exported and takes `item: any` from its caller, and it calls itself at line 109 (`fixDates`) with a piece of `item` — and nowhere in `fixDates` is there a depth parameter, a descent counter, or any other cap. The walk therefore spends one stack frame per LEVEL of the value it is handed, so the nesting of the caller's document — not this code — decides how deep the stack goes. JavaScript sets no limit of its own on that nesting: `JSON.parse` accepts any depth, so a 100,000-byte body — inside Express's default 100kb limit — parses to 50,000 levels, and a walk like this one throws `RangeError: Maximum call stack size exceeded` long before it reaches the bottom. Wherever that throw lands, the work fails: a request errors, and a walk running outside any `try` — an event handler, a timer, a promise nobody awaits — takes the Node process down with every other request in flight. Thread a depth argument through `fixDates` and reject the value past a fixed maximum, or rewrite the descent with an explicit stack. — src/helpers/clock.ts:109
What to do
- Each finding names the externally-callable member that accepts the document and the self-call that descends, and states that no depth parameter or counter exists anywhere in the walk. Confirm from the two, then thread a depth argument through the walk and reject documents past a fixed maximum, or rewrite it with an explicit stack.
X18 · Disposal-pattern correctness
X19 · Unrestored process-global state
X21 · Side-effecting pattern guard
X22 · Contradicted release guard
X23 · Unguarded diagnostic materialisation
X24 · Document value interpolated into markup unescaped
X25 · Inert configuration knob
X28 · Index access outside its own emptiness guard
X29 · Per-element action decided by a fixed element
X3 · Exception handling
X30 · Support guard that admits what it rejects
X5 · Nullable reference types
- 0/1 of this repository's type-checking configuration(s) turn on strict null checking (`"strict": true`, or `"strictNullChecks": true`). A configuration that states neither is counted as OFF, because off is tsc's own default; a solution-style one whose `"files"` is empty and whose `"references"` point at other projects is in neither number, because it checks no source itself. Where it is off, `string` admits `null` and `undefined`: passing a value that is null compiles silently and throws on the first property access.
What to do
- The findings name the configuration each number was taken from and, for the assertions, the files that hold them. Turn null checking on where it is off — `"strict": true` in the base tsconfig that the others extend switches `strictNullChecks` on with the rest of the family — and then resolve the assertions rather than adding to them. A `!` on a value the checker could show to be null is a promise the author cannot check from where they are standing, and each one is a `TypeError: Cannot read properties of null` waiting for the path that makes it true; where the value genuinely cannot be null, say something the checker can see instead (narrow it with a test, make the property required, drop the `?`).
Reference — by lens
| Lens | Score | Rating | Impact |
|---|---|---|---|
| Code Health | 69% | Adequate — gated by X5 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Architecture | 69% | Adequate | Acceptable, with room to improve. |
| Maturity | 56% | Adequate — gated by M2 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Readiness | 37% | Weak — gated by P1, P3 | Capped at Fair by a Critical contributor — resolve it before relying on this lens. |
| Security | 98% | Exemplary | Strongest area. |
| Domain Modelling | 69% | Adequate | Acceptable, with room to improve. |
Unscored — 1 check(s) recorded observations but carry no score
- SC1 Supply-chain hygiene — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
- P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
- P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 74 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.
- AC7 A11y enforcement — 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).
- AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- AX7 Slice cohesion — not applicable — not a vertical-slice architecture
- AX8 Test isolation — no test/production split to check
- AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
- AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no data at rest for these controls to protect. If it does persist personal data (through a hosted backend configured outside this repository, for instance), the controls belong to wherever that data is stored.
- C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server (no Express, Fastify, Koa, Hono, NestJS or similar app, no Next.js/SvelteKit/Nuxt server route, no edge function), creates no Supabase tables and talks to no hosted backend. Access control is therefore N/A here — a browser application or library is authorized by the server it calls, not by itself; a client-side route guard hides a page and authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
- C3 Audit Trail — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a hosted backend configured outside this repository, for instance), the trail belongs to wherever that data is stored.
- C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound. If it does (through a hosted backend configured outside this repository, for instance), the limit belongs wherever that data is stored.
- C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a TypeORM/MikroORM/sequelize-typescript/NestJS-Mongoose entity, a Mongoose schema, a Sequelize or Drizzle table, a Knex migration or a Prisma model — and no database or data-store client in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over. If it does (through a hosted backend configured outside this repository, for instance), the rights are served wherever that data is stored.
- D11 Test Reliability — No tests discovered
- D12 Dependency Hygiene — Dependency currency not established — this repository commits no lockfile to resolve
- D14 License Compliance — npm licences not graded — this npm repository commits no lockfile this pass can resolve
- D16 Bus Factor — too few commits for a meaningful bus factor
- D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
- D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
- D21 Naming Consistency — N/A — too few peers to establish a naming convention (498 declarations, no unit with a dominant convention).
- D22 Internal API Consistency — API consistency is measured on C# only; the exposed TypeScript surface was not measured.
- D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Aggregate roots were found in only one source directory (objects), which is a layered codebase, not two contexts. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
- D24 Comment Value — Too few judgeable comments (8 of at least 30); comment value is not applicable here.
- D25 ADR Conformance — no ADRs to check
- D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
- D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
- D34 Knowledge Freshness — too few commits to judge knowledge freshness
- D36 Supply-chain Provenance & Signing — The CI pipeline builds and tests but publishes no released artifact — no package publish, container push, GitHub release or deployment step. Supply-chain provenance, signing and SBOM attest RELEASED artifacts, so there is nothing to attest here. Add them to the release pipeline when this repo starts shipping artifacts (a published package, a container image, a deployed service or a tagged release). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
- D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
- D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
- D4 Code Duplication — This repository's production source (.ts, .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.
- D5 Coupling — Not applicable — this npm build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
- D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
- D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in the repository root ran and not one test passed (No tests found, exiting with code 1), so the coverage would describe the failed run, not the code. Coverage is excluded from the score rather than counted as a near-zero. The named suite step is one the repository's maintainers can perform; once it passes, the real number is measured on the next scan. Alternatively, commit the lcov/Cobertura report your CI produces and it is read without a re-run.
- DM10 One transaction, one aggregate — no repository writes detected — no operation to judge against the one-aggregate rule
- DM2 Strongly-typed ids — no id-bearing domain types detected — strongly-typed-id adoption not assessable
- DM3 Integration-event coupling — no integration events detected — coupling check not applicable
- DM6 Domain ↔ infrastructure boundary — this TypeScript/JavaScript repository maps no type to a persistence framework (TypeORM/Prisma/MikroORM/Sequelize/Mongoose), so DM6's domain↔infrastructure fusion read has no population to be taken over
- DM7 Repository granularity — no repository abstraction detected (e.g. uses a document session)
- ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
- ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
- ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
- M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks. 1 claim(s) of kinds M4 does not check were not checked (install 1); M4 checks only links and versions and artefact counts.
- P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
- P2 Observability — This repository's JavaScript/TypeScript source (1 module(s), 26 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
- P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
- P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
- P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `jest --coverage --coverageReporters=lcovonly`) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
- PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for tinybench, mitata, benchmark.js, benny or vitest `bench(...)` calls in files that import them (or `*.bench.*` files), or one of those in a package.json, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
- PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
- PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
- R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
- R5 Dependency Freshness — no package-lock.json — dependency freshness not measured (would require an npm lockfile); JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
- S1 Web-Security Posture — Not assessed: 26 JavaScript/TypeScript file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation, obsolete TLS versions, passwords stored or checked as plaintext and session cookies set without HttpOnly, Secure or SameSite, and none was found. That half of the dimension is clean, but it is not scored on its own: a C# repository with the same clean reading is scored on its server controls as well, or is N/A for having no web surface, and neither can be decided here. Of the server controls, two are read where the source shows them: every session or sign-in cookie the code sets is read for HttpOnly, Secure and SameSite at the line that sets it (a raw `Set-Cookie` header, Express, Fastify, Hono, Koa, Next.js, `cookie.serialize`, express-session and cookie-session), and every Node listener for HTTPS enforcement. HSTS, security response headers and input validation are NOT assessed for JavaScript/TypeScript: each is scored as an absence, an absence is only reportable over the production HTTP server, and in this ecosystem the file that opens the port is build output or a framework launcher rather than a file in the source tree. Their absence here is not a finding about this repository.
- X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X26 Unsynchronised callback handoff — Not applicable: this check looks for a collection written by a callback on one thread while the body waiting on it touches it on another, and in this repository's languages no collection is reachable from two threads at once. TypeScript/JavaScript runs every callback on the one thread that owns its objects: a callback runs only when the body waiting on it has yielded, never alongside it, and a worker thread receives a COPY of what it is sent. A SharedArrayBuffer carries raw bytes, never an Array, Map or Set, so no collection is reachable from two threads at once. Not a gap in the analyzer and not a finding about your code.
- X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Not a gap in the analyzer and not a finding about your code.
- X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
- X4 Structured logging — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
- X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
- X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
Critical — 2 finding(s)
- Test suite declares a test script but contains no test files: the repository root
- Import cycle (2 files) src/objects/page.tsx:2
Serious — 35 finding(s)
- No test reaches this file src/objects/route.tsx:1
- No test reaches this file REDACTED:1
- No test reaches this file src/objects/router.tsx:1
- No test reaches this file src/objects/pagenavigationcommandhandler.ts:1
- No test reaches this file src/objects/pagenavigationaggregate.ts:1
- No test reaches this file preprocessor.js:1
- No test reaches this file src/objects/pagenavigated.ts:1
- No test reaches this file src/objects/auditedevent.ts:1
- No test reaches this file src/objects/navigatetopage.ts:1
- No test reaches this file src/objects/datedevent.ts:1
- Stale committed build artefact — its source no longer exists dist/interfaces/iamanaction.js.map
- Stale committed build artefact — its source no longer exists dist/interfaces/iamanaggregateroot.js.map
- Stale committed build artefact — its source no longer exists dist/objects/auditedaction.js.map
- Stale committed build artefact — its source no longer exists dist/objects/datedaction.js.map
- Stale committed build artefact — its source no longer exists dist/services/actionstore.js.map
- Mutable entity: TestAggregate tests/objects/aggregateroot.ts:39
- Mutable entity: TestAggregate tests/objects/aggregateroot.ts:66
- Mutable entity: SingleCommandOnlyPleaseAggregateRoot tests/services/applicationservice.ts:124
- Anemic entity: TestAggregate tests/objects/aggregateroot.ts:39
- Anemic entity: TestAggregate tests/objects/aggregateroot.ts:66
- clock.fixDates (cognitive 27) src/helpers/clock.ts:97
- ApplicationService.handleCommand (cognitive 16) src/services/applicationservice.ts:128
- REDACTED
- TooManyMethods: ClockDate src/helpers/clock.ts:2
- Coverage not measured — JavaScript/TypeScript suite
- Empty method body — does nothing with its inputs src/objects/commandvalidator.ts:7
- CI pipeline targets a decommissioned service
- Type Safety
- Duplicated block with local edits (15 matched lines × 2 locations) src/services/eventstore.ts:16
- Duplicated block (5 lines × 2 locations) src/services/applicationservice.ts:150
- Complex function fixDates (cyclomatic 11, cognitive 27) src/helpers/clock.ts:97
- No lint script
- Dead file (~13 LoC) preprocessor.js
- JavaScript dependencies are not locked package.json:17
- Recursive walk over a caller-supplied document has no depth cap src/helpers/clock.ts:109
Minor — 11 finding(s)
- REDACTED
- No ADRs
- No architecture diagram/doc
- No SAST
- No dependency-update automation package.json:17
- No changelog
- Unused module-local declaration 'currentPage' src/objects/route.tsx:18
- Unused module-local declaration 'historyReplace' src/objects/route.tsx:28
- Unused module-local declaration 'TestAggregateRoot' tests/services/viewsubscriber.ts:23
- Unused module-local declaration 'TestCommand' tests/services/viewsubscriber.ts:33
- Strict null checking is not enabled everywhere the repository type-checks
Minor — 1 finding(s)
- Dependency hygiene PARTLY measured — npm pinning read, dependency currency not (no committed lockfile, so no resolved version to grade)
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-e0a9fe8922544b46851af94eaa7cc31b/history.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-history.json |
| D28 · Secrets (history) | gitleaks | — | gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-e0a9fe8922544b46851af94eaa7cc31b/tree.json --exit-code 0 --source . | 0 | artifacts/raw/gitleaks-tree.json |
| D29 · Static Analysis (SAST) | semgrep | — | semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt . | 1 | artifacts/raw/semgrep.json |
| D30 · Dependency Vulnerabilities | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D30 · Dependency Vulnerabilities | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |
| D31 · IaC & Container Security | trivy | — | trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan. | 0 | — |
| D32 · Data Compliance (PII/GDPR) | semgrep | — | semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. | 0 | — |
| D37 · Vulnerability-disclosure Policy | disclosure | — | disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed. | 0 | — |
| D40 · Network Egress Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here. | 0 | — |
| D41 · Kernel & Syscall Confinement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here. | 0 | — |
| D42 · Runtime Threat Enforcement | runtime-hardening | — | runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here. | 0 | — |
| D43 · Malicious Dependencies | osv-scanner | — | osv-scanner --format json --recursive --experimental-disable-plugins transitivedependency/requirements --experimental-disable-plugins dotnet/csproj --experimental-disable-plugins dotnet/nugetcpm . | 0 | — |
| D43 · Malicious Dependencies | trivy | — | trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update | 0 | artifacts/raw/trivy-fs.json |