Public report of kreta/Kreta, published 22 October 2026. It has the same score, grades and number of findings as the full report. The details of security findings (where they are in the code, which known vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey → Signed and filed in the standard's public register, 22 October 2026, 21:28 UTC · Survey ID cd_4940dbd7201647feb6cf4a1944af9f47

kreta/Kreta

Measured 22 October 2026, 21:24 UTC, at code version 3d092f4

Code coverage: not measuredBus factor: not measured

Code coverage is not measured: JavaScript/TypeScript suite (CouldNotMeasureTestRunFailed).

Bus factor is not measured: No living knowledge left to concentrate.

CAI score 41out of 100 At risk Down 2 since the last survey

The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.

Event Sourcing 100 Exemplary Domain Modelling 86 Exemplary Security and Compliance 54 Adequate Maturity 51 Adequate Code Health 51 Adequate Architecture 50 Adequate Production Readiness 25 Weak

A small codebase: 15,075 lines of product code in 5 projects, tests not counted · Estimated rebuild effort: about 0.3 person-years · Weakest lens: Production Readiness, 25

Findings by how serious they are

120 critical 210 serious 159 minor

11 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.

This survey was produced by

Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
22 October 2026, 21:24 UTC

A measurement, not a certificate. The Code Assurance Index records a number together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that implements it, and today Watchdog is the only one that does.

A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.

The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸

77of 81 dimensions measured by tools. The other 4 are advisory notes from an AI model, which explain the code but don't count towards the score.
455of 489 findings point to an exact file and line, so you can open each one in the code. The other 34 concern the repository as a whole, such as missing documentation.
81dimensions across 7 lenses, read from 15,075 lines of product code in 5 projects.
Chapters

Executive summary

kreta/Kreta scores 41 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged. The project hasn't declared a stable release yet, so its lenses are rated against a lower bar than a released product's, while the score itself is worked out as for any repository.

The weakest lens counts most in the score, and here that is Production Readiness, which scores 25 and is rated Weak. Its Observability dimension scores 0 out of 10, and until that reaches 4, Production Readiness can't be rated higher than Adequate. The first actions are to resolve the 7 No assertions (empty test) finding(s) in Test Quality and to resolve the 54 Deprecated finding(s) in Dependency Hygiene, and if Production Readiness rose to 70, the score would rise from 41 to about 53.

120 findings are critical: 102 in Dependency Vulnerabilities, nine in IaC & Container Security, seven in Test Quality, one in Circular Imports and one in Dependency Hygiene.

Watchdog couldn't measure 11 dimensions in this code, among them Test Reliability, Internal API Consistency and Navigability, so they are left out of the score. The product code is 15,075 lines, which would take an estimated 0.3 person-years, around €37,000, to rebuild.

Code Health 51 Adequate, capped by Type Safety and Nullable reference types Architecture 50 Adequate, capped by Project Cohesion and Import Boundaries Maturity 51 Adequate, capped by Knowledge Freshness and Architecture documentation Production Readiness 25 Weak, capped by Dependency Hygiene, Observability, Security & performance tooling and DR & Backup Security and Compliance 54 Adequate, capped by Dependency Vulnerabilities, Supply-chain Provenance & Signing and Malicious Dependencies Domain Modelling 86 ★ Exemplary Event Sourcing 100 ★ Exemplary

A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.

How the score is built: what each lens counts for The lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
Production Readiness 25 · counts for 46%Architecture 50 · counts for 25%Code Health 51 · counts for 14%Maturity 51 · counts for 8%Security and Compliance 54 · counts for 4%Domain Modelling 86 · counts for 2%Event Sourcing 100 · counts for 1%

If Production Readiness rose from 25 to 70, the lowest score rated Strong, the score would rise from 41 to about 53.

Code composition: what the lines of code are
Product code 55%Tests 45%
New since the last survey: 27 findings

These 27 critical or serious findings weren't in the previous survey, on 8 October 2026.

Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.

Fixed since the last survey: 3 findings

These 3 critical or serious findings were in the previous survey, on 8 October 2026, and are gone from this one.

  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Critical CVE: REDACTED REDACTED
  • Dependency Vulnerabilities · Medium CVE: [GHSA redacted] REDACTED
Rebuild cost: about €37,000 · Estimate
Cost to rebuild€12,000 to €62,000, for 205 to 652 hours of work, about 0.3 person-years for one engineer
Difficulty of the problemHigh, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.7 at a score of 41. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeSmall: 15,075 lines of product code

How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.

Top priorities

The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.

1
Resolve the 7 No assertions (empty test) finding(s) in Test Quality — start with CurrentProject.spec.js (7).
Raises the score by about 12 points · Low effort · Test Quality
2
Resolve the 54 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (54).
Raises the score by about 12 points · Medium effort · Dependency Hygiene
3
Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run.
Raises the score by about 4 points · Medium effort · Observability

Diagnosis: what the measurements show together

Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.

Where the investment is most exposed · Value at risk
This code would cost about €37,000 to build again, about 0.3 person-years of work. Its weakest lens is Production Readiness, at 25 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 7 No assertions (empty test) finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 12 points for low effort, because it clears the 7 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.

197 modules, with 157 dependencies between them. One loop runs through 3 of the modules, marked above the diagonal.

The table shows the 40 modules with the most connections; 157 more are left out to keep it readable.

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 SharedKernel.Application2 SharedKernel.Http.GraphQl3 SharedKernel.Http.GraphQl.Relay4 SharedKernel.Infrastructure.Persistence.Doctrine.ORM5 SharedKernel.Domain.Model.Identity6 SharedKernel.Infrastructure.Persistence.Doctrine.DataFixtures7 TaskManager.Infrastructure.Symfony.GraphQl.Query.Organization8 SharedKernel.Event9 TaskManager.Infrastructure.Symfony.GraphQl.Mutation.Organization10 TaskManager.Infrastructure.Symfony.GraphQl.Query.Project11 SharedKernel.Domain.Model12 TaskManager.Infrastructure.Symfony.GraphQl.Query.Project.Task13 IdentityAccess.Domain.Model.User14 Notifier.Domain.Model.Inbox15 SharedKernel.Domain.Event16 SharedKernel.Domain.ReadEvent17 SharedKernel.Serialization18 TaskManager.Domain.Model.User19 Notifier.Domain.Event.Inbox20 Notifier.Domain.Model.Inbox.Notification21 Notifier.Domain.ReadModel.Inbox22 SharedKernel.Infrastructure.Messaging.AMQP.PhpAmqpLib23 TaskManager.Domain.Event.User24 TaskManager.Domain.Model.Organization25 Notifier.Domain.ReadEvent.Inbox26 Notifier.Domain.ReadModel.Inbox.Notification27 TaskManager.Domain.Model.Project28 TaskManager.Infrastructure.Persistence.Doctrine.ORM.Organization29 Notifier.Application.Inbox.Notification30 Notifier.Domain.ReadEvent.Inbox.Notification31 Notifier.Infrastructure.Domain.ReadModel.Inbox.Notification32 TaskManager.Application.Command.Project33 TaskManager.Application.Query.Project34 TaskManager.Domain.Model.Project.Task35 TaskManager.Infrastructure.Persistence.Doctrine.ORM.Project36 TaskManager.Application.Command.Organization37 TaskManager.Application.Command.Project.Task38 TaskManager.Application.DataTransformer.Project.Task39 TaskManager.Infrastructure.Persistence.Doctrine.ORM.Project.Task40 TaskManager.Application.Query.Project.Task
1 SharedKernel.Application
2 SharedKernel.Http.GraphQl
3 SharedKernel.Http.GraphQl.Relay
4 SharedKernel.Infrastructure.Persistence.Doctrine.ORM
5 SharedKernel.Domain.Model.Identity1
6 SharedKernel.Infrastructure.Persistence.Doctrine.DataFixtures1
7 TaskManager.Infrastructure.Symfony.GraphQl.Query.Organization661
8 SharedKernel.Event14
9 TaskManager.Infrastructure.Symfony.GraphQl.Mutation.Organization444
10 TaskManager.Infrastructure.Symfony.GraphQl.Query.Project2212
11 SharedKernel.Domain.Model1
12 TaskManager.Infrastructure.Symfony.GraphQl.Query.Project.Task23111
13 IdentityAccess.Domain.Model.User4
14 Notifier.Domain.Model.Inbox115
15 SharedKernel.Domain.Event2
16 SharedKernel.Domain.ReadEvent1
17 SharedKernel.Serialization12
18 TaskManager.Domain.Model.User13
19 Notifier.Domain.Event.Inbox111
20 Notifier.Domain.Model.Inbox.Notification11104
21 Notifier.Domain.ReadModel.Inbox1
22 SharedKernel.Infrastructure.Messaging.AMQP.PhpAmqpLib1
23 TaskManager.Domain.Event.User111
24 TaskManager.Domain.Model.Organization71713
25 Notifier.Domain.ReadEvent.Inbox111
26 Notifier.Domain.ReadModel.Inbox.Notification1
27 TaskManager.Domain.Model.Project481
28 TaskManager.Infrastructure.Persistence.Doctrine.ORM.Organization3324
29 Notifier.Application.Inbox.Notification642
30 Notifier.Domain.ReadEvent.Inbox.Notification333
31 Notifier.Infrastructure.Domain.ReadModel.Inbox.Notification13
32 TaskManager.Application.Command.Project1134
33 TaskManager.Application.Query.Project178
34 TaskManager.Domain.Model.Project.Task11953
35 TaskManager.Infrastructure.Persistence.Doctrine.ORM.Project324
36 TaskManager.Application.Command.Organization28142
37 TaskManager.Application.Command.Project.Task28710
38 TaskManager.Application.DataTransformer.Project.Task112
39 TaskManager.Infrastructure.Persistence.Doctrine.ORM.Project.Task21110
40 TaskManager.Application.Query.Project.Task27572
Uses a module listed above itPart of a loopThe module itself
1 SharedKernel.Application2 SharedKernel.Http.GraphQl3 SharedKernel.Http.GraphQl.Relay4 SharedKernel.Infrastructure.Persistence.Doctrine.ORM5 SharedKernel.Domain.Model.Identity6 SharedKernel.Infrastructure.Persistence.Doctrine.DataFixtures7 TaskManager.Infrastructure.Symfony.GraphQl.Query.Organization8 SharedKernel.Event9 TaskManager.Infrastructure.Symfony.GraphQl.Mutation.Organization10 TaskManager.Infrastructure.Symfony.GraphQl.Query.Project11 SharedKernel.Domain.Model12 TaskManager.Infrastructure.Symfony.GraphQl.Query.Project.Task13 IdentityAccess.Domain.Model.User14 Notifier.Domain.Model.Inbox15 SharedKernel.Domain.Event16 SharedKernel.Domain.ReadEvent17 SharedKernel.Serialization18 TaskManager.Domain.Model.User19 Notifier.Domain.Event.Inbox20 Notifier.Domain.Model.Inbox.Notification21 Notifier.Domain.ReadModel.Inbox22 SharedKernel.Infrastructure.Messaging.AMQP.PhpAmqpLib23 TaskManager.Domain.Event.User24 TaskManager.Domain.Model.Organization25 Notifier.Domain.ReadEvent.Inbox26 Notifier.Domain.ReadModel.Inbox.Notification27 TaskManager.Domain.Model.Project28 TaskManager.Infrastructure.Persistence.Doctrine.ORM.Organization29 Notifier.Application.Inbox.Notification30 Notifier.Domain.ReadEvent.Inbox.Notification31 Notifier.Infrastructure.Domain.ReadModel.Inbox.Notification32 TaskManager.Application.Command.Project33 TaskManager.Application.Query.Project34 TaskManager.Domain.Model.Project.Task35 TaskManager.Infrastructure.Persistence.Doctrine.ORM.Project36 TaskManager.Application.Command.Organization37 TaskManager.Application.Command.Project.Task38 TaskManager.Application.DataTransformer.Project.Task39 TaskManager.Infrastructure.Persistence.Doctrine.ORM.Project.Task40 TaskManager.Application.Query.Project.TaskSharedKernel.Application1SharedKernel.Http.GraphQl2SharedKernel.Http.GraphQl.Relay3SharedKernel.Infrastructure.Persistence.Doctrine.ORM4SharedKernel.Domain.Model.Identity5SharedKernel.Infrastructure.Persistence.Doctrine.DataFixtures6TaskManager.Infrastructure.Symfony.GraphQl.Query.Organization7SharedKernel.Event8TaskManager.Infrastructure.Symfony.GraphQl.Mutation.Organization9TaskManager.Infrastructure.Symfony.GraphQl.Query.Project10SharedKernel.Domain.Model11TaskManager.Infrastructure.Symfony.GraphQl.Query.Project.Task12IdentityAccess.Domain.Model.User13Notifier.Domain.Model.Inbox14SharedKernel.Domain.Event15SharedKernel.Domain.ReadEvent16SharedKernel.Serialization17TaskManager.Domain.Model.User18Notifier.Domain.Event.Inbox19Notifier.Domain.Model.Inbox.Notification20Notifier.Domain.ReadModel.Inbox21SharedKernel.Infrastructure.Messaging.AMQP.PhpAmqpLib22TaskManager.Domain.Event.User23TaskManager.Domain.Model.Organization24Notifier.Domain.ReadEvent.Inbox25Notifier.Domain.ReadModel.Inbox.Notification26TaskManager.Domain.Model.Project27TaskManager.Infrastructure.Persistence.Doctrine.ORM.Organization28Notifier.Application.Inbox.Notification29Notifier.Domain.ReadEvent.Inbox.Notification30Notifier.Infrastructure.Domain.ReadModel.Inbox.Notification31TaskManager.Application.Command.Project32TaskManager.Application.Query.Project33TaskManager.Domain.Model.Project.Task34TaskManager.Infrastructure.Persistence.Doctrine.ORM.Project35TaskManager.Application.Command.Organization36TaskManager.Application.Command.Project.Task37TaskManager.Application.DataTransformer.Project.Task38TaskManager.Infrastructure.Persistence.Doctrine.ORM.Project.Task39TaskManager.Application.Query.Project.Task40116611444422121231114115211213111111041111171713111148133246423331311341781195332428142287101122111027572+157 more modules (most-connected shown)

At a glance — Code Health · 51% · Adequate · gated by R1, X5 ·

The Good
D1 · PHP Cyclomatic Complexity 9.7 D2 · PHP Cognitive Complexity 10.0 D3 · PHP God Classes 10.0 D4 · PHP Code Duplication 9.0 D17 · PHP Explicit Debt 10.0 R10 · React / TS Code Duplication 8.6 R2 · React / TS Cyclomatic Complexity 10.0 R3 · React / TS Large Files 10.0 R7 · React / TS Dead Code 9.0 X1 · Repo Async correctness 10.0 X12 · Repo Unreachable branch 10.0 X13 · Repo Undrained process stream 10.0 X16 · Repo Unfloored truncation loop 10.0 X18 · Repo Disposal-pattern correctness 10.0 X19 · Repo Unrestored process-global state 10.0 X21 · Repo Side-effecting pattern guard 10.0 X22 · Repo Contradicted release guard 10.0 X23 · Repo Unguarded diagnostic materialisation 10.0 X25 · Repo Inert configuration knob 10.0 X28 · Repo Index access outside its own emptiness guard 10.0 X29 · Repo Per-element action decided by a fixed element 10.0 X3 · Repo Exception handling 7.4 X30 · Repo Support guard that admits what it rejects 10.0
The Ugly
R1 · React / TS Type Safety 0.0 X5 · Repo Nullable reference types 2.0

At a glance — Architecture · 50% · Adequate · gated by D26, R11 ·

The Good
D5 · PHP Coupling 10.0 D6 · PHP Cohesion (LCOM4) 10.0 D23 · PHP Boundary Type-Coupling 10.0 D35 · PHP Change Coupling 10.0 AX10 · Repo Code composition 6.8 AX3 · Repo Project dependency cycles 10.0 AX4 · Repo Dependency direction 10.0 AX5 · Repo Architecture & structure 10.0
The Bad
R9 · React / TS Circular Imports 4.7
The Ugly
D26 · PHP Project Cohesion 2.0 R11 · React / TS Import Boundaries 0.0

At a glance — Maturity · 51% · Adequate · gated by D34, M2 ·

The Good
D15 · PHP Churn × Complexity Hotspots 10.0 D19 · PHP Documentation Quality 8.0 D21 · PHP Naming Consistency 10.0 M3 · Repo Folder & project structure 10.0 M4 · Repo Documentation accuracy 8.0
The Bad
M1 · Repo Documentation (README) 6.0
The Ugly
D20 · PHP ADR Quality 0.0 D34 · PHP Knowledge Freshness 0.0 M2 · Repo Architecture documentation 2.0

At a glance — Readiness · 25% · Weak · gated by R8, P2, P3, P5 ·

The Good
D9 · PHP Test Distribution 10.0 D13 · PHP Secret Scanning 10.0 D14 · PHP License Compliance 10.0 P1 · Repo CI/CD gates 10.0 P4 · Repo Deployment & Rollback 8.0 P6 · Repo Release Hygiene 8.0 P8 · Repo Schema migrations 10.0 R4 · React / TS Test Coverage 8.1 R6 · React / TS Tooling 6.7
The Bad
D10 · PHP Test Quality 4.3 D12 · PHP Dependency Hygiene 6.0
The Ugly
P2 · Repo Observability 0.0 P3 · Repo Security & performance tooling 0.0 P5 · Repo DR & Backup 0.0 R8 · React / TS Dependency Hygiene 3.0

At a glance — Security · 54% · Adequate · gated by D30, D36, D43 ·

The Good
D28 · PHP Secrets (history) 10.0 S1 · Repo Web-Security Posture 8.0 X14 · Repo Bypassable address classification 10.0 X15 · Repo Unvalidated length from an untrusted reader 10.0 X17 · Repo Uncapped recursion over a caller-supplied document 10.0
The Bad
D31 · PHP IaC & Container Security 6.1
The Ugly
D29 · PHP Static Analysis (SAST) 4.1 D30 · PHP Dependency Vulnerabilities 0.0 D36 · PHP Supply-chain Provenance & Signing 0.0 D43 · PHP Malicious Dependencies 0.0 X24 · Repo Document value interpolated into markup unescaped 3.5

At a glance — Domain Modelling · 86% · Exemplary ·

The Good
DM1 · Repo Aggregate boundaries 10.0 DM11 · Repo Constructible invalid state 8.1 DM12 · Repo Ambient inputs in the domain 10.0 DM4 · Repo Rich vs anemic model 6.5 DM5 · Repo Encapsulated state 10.0 DM6 · Repo Domain ↔ infrastructure boundary 10.0 DM7 · Repo Repository granularity 10.0 DM8 · Repo Value-object opportunities 10.0 DM9 · Repo Scattered domain decisions 10.0

At a glance — Event Sourcing · 100% · Exemplary ·

The Good
ES1 · Repo Fold determinism 10.0

Security & Compliance — OWASP Top-10 mapping

Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).

OWASP categoryFindingsSeverity
A03:2025 — Software Supply Chain Failures141High / Critical
A02:2025 — Security Misconfiguration24High / Critical
A05:2025 — Injection17Medium
A08:2025 — Software or Data Integrity Failures1Medium

Roadmap

Begin by cleaning up 54 deprecated dependencies in REDACTED and fixing seven empty test files to ensure code stability. Next, implement structured JSON logging across all application modules and integrate automated static analysis into the CI pipeline to prevent security regressions. Finally, codify disaster recovery procedures by documenting RTO and RPO targets and ensuring backups are managed through infrastructure as code.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 7 No assertions (empty test) finding(s) in Test Quality — start with CurrentProject.spec.js (7).+11.9 ptsLowTest Quality
Resolve the 54 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (54).+12.1 ptsMediumDependency Hygiene
Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run.+4.2 ptsMediumObservability
Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+4.2 ptsMediumSecurity & performance tooling
Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.+4.2 ptsMediumDR & Backup
Resolve the 1 No ADRs found finding(s) in ADR Quality.+1.5 ptsLowADR Quality
Resolve the 5 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (5).+1.4 ptsLowDependency Hygiene
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.+2.2 ptsMediumDependency Hygiene

File quality

Per-file score 0–10 — a quality signature. Of 42 files carrying findings, judged against the Preview bar: 10% slop · 16% mixed · 74% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED2.0SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.3SlopIaC & Container Security: High IaC: REDACTED
REDACTED2.7SlopDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED3.0MixedDependency Vulnerabilities: Critical CVE: REDACTED
REDACTED3.0MixedIaC & Container Security: High IaC: REDACTED
REDACTED3.5MixedIaC & Container Security: High IaC: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): Medium: REDACTED
REDACTED5.8MixedDependency Vulnerabilities: High CVE: REDACTED
CompositeUi/src/actions/__tests__/CurrentProject.spec.js6.0MixedTest Quality: No assertions (empty test): fetches projects
CompositeUi/package.json6.0MixedDependency Hygiene: Deprecated: babel-eslint
TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php7.2Near-cleanCode Duplication: Members sharing a duplicated core (4 members, 50+ identical tokens)
TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php7.4Near-cleanCode Duplication: Duplicated block (41–42 lines × 2)
TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php7.4Near-cleanCode Duplication: Duplicated block (12 lines × 2)
TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php7.8Near-cleanCode Duplication: Duplicated block (32 lines × 3)
SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php7.8Near-cleanCode Duplication: Duplicated block (19 lines × 2)
REDACTED7.9Near-cleanStatic Analysis (SAST): Medium: REDACTED
REDACTED7.9Near-cleanIaC & Container Security: Medium IaC: REDACTED
CompositeUi/src/reducers/CurrentProject.js8.5Near-cleanCyclomatic Complexity: CurrentProject.reducer (cyclomatic 17)
TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php8.5Near-cleanCode Duplication: Edited copy of a member (34 corresponding lines)

How the grades work

Every finding carries one of four grades. Three say how serious it is. The fourth says this survey could not settle it — and it is a grade, not a gap.

Critical — 120

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.

Serious — 210

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.

Minor — 159

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 11

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

Watchdog 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. 77 of 81 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 4 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.

Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.

What we checked — 81 dimensions across the health lenses
D1D2D3D4D5D6D9D10D12D13D14D15D17D19D20D21D23D26D28D29D30D31D34D35D36D43AX10AX3AX4AX5DM1DM11DM12DM4DM5DM6DM7DM8DM9ES1M1M2M3M4P1P2P3P4P5P6P8R1R10R11R2R3R4R6R7R8R9S1X1X12X13X14X15X16X17X18X19X21X22X23X24X25X28X29X3X30X5

Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.

How to trust any code-health report — three questions
  1. 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, 455 of 489 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
  3. 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.

This report answers yes to all three. That's the bar to hold any assessment to.

Tools & methods

The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Watchdog duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic
LLM (sampled · advisory)Documentation quality, ADR conformance, naming — sampled over a bounded sample; advisory, never a deterministic measurementLocal LLM◐ LLM · sampled · advisory

Every finding is locatable in findings.md. Run 01a16580-3656-7081-805a-6dbed1978c67.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.

  • D10 Test Quality — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. The 37 test(s) behind this row are the ones the JavaScript/TypeScript census could read, and this repository also carries at least 230 test source file(s) (.php) that it cannot: it reads JavaScript/TypeScript test declarations off disk, so a JUnit/pytest-style suite is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
  • D11 Test Reliability — not measured this run — Watchdog 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 `yarn install --frozen-lockfile --ignore-scripts` in CompositeUi/ (0 tests)) ran but surfaced no test cases to the runner, so flakiness couldn't be exercised.
  • D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares composer.json, but the licence verdict published here was taken over its npm package dependencies. Nothing was read about its Composer dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • 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. Every one of the 53 significant source file(s) was last meaningfully changed so long ago that no living knowledge remains, so there is no concentration to measure — the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness).
  • D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D27 Navigability — not measured this run — Watchdog 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. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D44 Platform End-of-Life — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a REDACTED) is simply not read here yet.
  • AX1 Captive dependencies — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Symfony DependencyInjection and an unrecognised PHP container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AX6 Interface segregation — not measured this run — Watchdog 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 is computed over the public interfaces this run's compilations declare, and none was loaded, so it had nothing to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 15 — the compose project is invalid) — time="2026-10-22T21:24:40Z" level=warning msg="The \"COMPOSITE_UI_HOST\" variable is not set. Defaulting to a blank string." validating REDACTED: services.php.extra_hosts array items[0,1] must be unique; runtime evidence skipped.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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.
  • DM9 Scattered domain decisions — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. Some of this repository's production types come from a frontend that does not bind comparison operands to the members they read, which arm one needs, and those types were not walked for this dimension. The counts above speak for the languages that declare it.
  • GD1 Unfinished & placeholder code — not measured this run — Watchdog 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, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • IC1 Incompleteness & stubs — not measured this run — Watchdog 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, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's PHP is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • R10 Code Duplication — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it 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. The filesystem refused the listing or the read of: IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Ui/Http/Symfony/public/uploads. Every other path was read.
  • X27 Collection changed while being enumerated — not measured this run — Watchdog 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 Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded, no Java, Rust, Erlang, F#, Python, Dart, Ruby, Scala or Kotlin was found, and this repository's PHP is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
  • X4 Structured logging — not measured this run — Watchdog 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

Watchdog assesses the repository exactly as committed, and only the repository. By design it does 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

For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.

  • 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.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D9 Test Distribution: The test-pyramid shape is inferred from project/folder naming and references, with a single test host bucketed per-file by its path tier and content signals — a suite that names tiers unconventionally and gives no per-file signal can still be mis-bucketed.
  • D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • 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 is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
  • D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
  • D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
  • D23 Boundary Type-Coupling: Boundary leakage is detected from type references across detected contexts — leaks that flow through primitives, serialization or shared infrastructure may not surface as a typed reference.
  • D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
  • 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.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • DM4 Rich vs anemic model: Behaviour is detected as state mutation inside a method body — a method that enforces an invariant by validating-and-throwing without mutating reads as a query, and mutation delegated through an interface the scan can't resolve isn't credited; entities with zero public properties still drop out of the population. It detects that state changes, not whether the rule is correct.
  • DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
  • M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
  • 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.

The LLM boundary

LLM-set scores this run (4): D19, D21, D26, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.

Dimensions

D1 · Cyclomatic Complexity9.7 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: How tangled the control flow is — methods with many branches are hard to test and change.

Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Prevented

2 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was CurrentProject.reducer at 17.

CurrentProject.reducer (cyclomatic 17)CompositeUi/src/reducers/CurrentProject.js:102

What to do

  1. Bring the 2 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with CurrentProject.reducer (cyclomatic 17), reducer (cyclomatic 17). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 9.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
  2. Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity10.0 / 10Exemplary✓ Tool-verified

What it measures: How hard the code is for a person to follow, beyond raw branching.

Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 method(s) exceeded the cognitive complexity threshold of 15.

✓ On the Gold path — maintain.

Detailed fixes: d2_recommendation.md.

D3 · God Classes10.0 / 10Exemplary✓ Tool-verified

What it measures: Over-large classes that try to do too much ("god classes").

Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 god class(es) detected.

✓ On the Gold path — maintain.

Detailed fixes: d3_recommendation.md.

D4 · Code Duplication9.0 / 10Stronggated by 36 serious findings✓ Tool-verified

What it measures: Copy-pasted code that should be shared instead.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.

Maturity: Documented → Verified → Prevented · effective 9.0 / 10 · rule-coverage 100% · ceiling Verified

34 duplicated block group(s) detected. A further 2 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.

Duplicated block (12 lines × 2) · ×4TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationOfIdHandler.php:41
Duplicated block (9 lines × 2) · ×3SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:70
Duplicated block (8 lines × 2) · ×3SharedKernel/src/Kreta/SharedKernel/Infrastructure/Persistence/Fake/FakeDataCapabilities.php:41
Duplicated block (23 lines × 2) · ×2TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/MemberResolver.php:69
Duplicated block (10 lines × 3) · ×2TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46

+ 20 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 4 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with OrganizationOfIdHandler.php, CountProjectsHandler.php, DoctrineORMFilterableSpecification.php. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with AuthenticationListener.php, MarkAsReadNotification.php, UserSignedUpSubscriber.php. — One of this dimension's main actionable groups (3 warning-level).
  3. Resolve the 3 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with FakeDataCapabilities.php, AddOrganizationMemberToOrganizationHandler.php, DoctrineORMFilterableSpecification.php. — One of this dimension's main actionable groups (3 warning-level).
  4. Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.

Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.

Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

5 production modules (npm+Composer), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 4 of the 5 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether a class's methods are focused on a single responsibility.

Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.

Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 65 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D9 · Test Distribution10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether the test suite has a healthy mix of unit / integration / end-to-end tests.

Method: Test projects classified (Unit/Integration/BDD/E2E) from compiled metadata; test methods counted exhaustively across projects with placement-agnostic disk fallback. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

37 test methods: 37 unit, 0 integration, 0 BDD, 0 e2e. The JavaScript/TypeScript suite contributes 37 `it`/`test` case(s) across 10 test file(s) declaring at least one; its tier split is read from package names and paths only.

✓ On the Gold path — maintain.

Detailed fixes: d9_recommendation.md.

D10 · Test Quality4.3 / 10Weak✓ Tool-verified

What it measures: Whether the tests truly assert behaviour rather than just running the code.

Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.

Maturity: Documented → Verified → Prevented · effective 4.3 / 10 · rule-coverage 100% · ceiling Prevented

0 skipped, 7 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 37 tests. Measured on the JavaScript/TypeScript suite only — at least 230 test source file(s) (.php) went unread, so its test quality is unmeasured and is not in these counts.

No assertions (empty test): fetches projects · ×7CompositeUi/src/actions/__tests__/CurrentProject.spec.js:17

What to do

  1. Resolve the 7 No assertions (empty test) finding(s) in Test Quality — start with CurrentProject.spec.js (7). — One of this dimension's main actionable groups (7 issue-level).
  2. Enforce Test Quality in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.

Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.

D12 · Dependency Hygiene6.0 / 10Adequate✓ Tool-verified

What it measures: Whether dependencies are current, secure, and not bloated.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Verified

20 outdated direct production npm dependency(ies) of 23 graded, 0 pinning defect(s), across 1 package.json (1 of them the product) and 1 committed lockfile(s). Development dependencies are deliberately not graded for currency: that grade is about what SHIPS. 8 direct dependency(ies) — production, development or optional — are marked DEPRECATED by their publisher (the registry's per-version mark, or the lockfile's copy of it when the registry could not be asked); deprecated transitive packages are listed but not charged. Whether any is UNMAINTAINED is not graded — the registry publishes no maintenance status, and release age does not stand in for one. Whether any is UNUSED is not graded either: that is a source question, and the frontend dependency lens (R8) answers it in this same run. Known CVEs in this dependency graph are D30's question, read from the manifest there.

Deprecated: babel-eslint · ×8CompositeUi/package.json:108
Deprecated: abab · ×54REDACTED:5
Outdated (npm): react · ×5CompositeUi/package.json:90
Outdated (npm): classnames · ×15

What to do

  1. Resolve the 54 Deprecated finding(s) in Dependency Hygiene — start with REDACTED (54). — One of this dimension's main actionable groups (54 recommendation-level).
  2. Resolve the 8 Deprecated finding(s) in Dependency Hygiene — start with package.json (8). — One of this dimension's main actionable groups (8 warning-level).
  3. Resolve the 5 Outdated (npm) finding(s) in Dependency Hygiene — start with package.json (5). — One of this dimension's main actionable groups (5 recommendation-level).
  4. Enforce Dependency Hygiene in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.

Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · Secret Scanning10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.

Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

Secret scan ran and found no leaked secrets.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D14 · License Compliance10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether the licenses of third-party packages are compatible with your policy.

Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

0 of 23 shipped npm package(s) use a banned license. Licences were resolved from registry.npmjs.org over the 23 production dependency(ies) this repository's committed lockfile resolves, across 1 product package.json manifest(s). Its 61 `devDependencies` declaration(s) are excluded: a consumer installs none of them. ★ DEPTH: this is the DIRECT production set the lockfile resolves, NOT the transitive closure — only one of the four lock dialects this pass reads states a full graph, so a banned licence pulled in only by a dependency's OWN dependencies is outside this verdict, exactly as the JVM arm's declaration-site verdict is. ★ Each licence is the one the registry publishes for the package's CURRENT release rather than for the pinned version, which is the same caveat the Hex and RubyGems arms carry. This repository publishes itself under MIT, which is its own choice and is not judged here. ★ COVERAGE OF THIS VERDICT: it grades this repository's npm package dependencies and nothing else. The repository also declares composer.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Exemplary✓ Tool-verified

What it measures: Files that change often and are also complex — the riskiest hotspots.

Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

No churn × complexity hotspots in the window.

✓ On the Gold path — maintain.

Detailed fixes: d15_recommendation.md.

D17 · Explicit Debt10.0 / 10Exemplary○ Nothing flagged

What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.

Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

0 deducted task-comment markers across 15075 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.

✓ On the Gold path — maintain.

Detailed fixes: d17_recommendation.md.

D19 · Documentation QualityStrong◐ Sampled · advisory

What it measures: Whether the project's documentation is clear, complete, and useful.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Strong / 10 · rule-coverage 100% · ceiling Documented

The repository's root README and three subdirectories' READMEs all document their own directories: the top-level one is a project overview with links to Travis, Slack, and the license; the etc/ansible README explains how to install Ansible via pip and remove unstable roles before provisioning; the Docker README shows installation steps, host-file updates, and a docker-compose ps output table plus a 'Usefu' section that clips mid-sentence. The docs also include an explicit docs/index.md pointing readers to the documentation directory, which is itself thin on content (only Usage headings with links to installation and docker docs).

What to do

  1. Improve Documentation Quality — currently 8.0/10. — The repository's root README and three subdirectories' READMEs all document their own directories: the top-level one is a project overview with links to Travis, Slack, and the license; the etc/ansible README explains how to install Ansible via pip and remove unstable roles before provisioning; the Docker README shows installation steps, host-file updates, and a docker-compose ps output table plus a 'Usefu' section that clips mid-sentence. The docs also include an explicit docs/index.md pointing readers to the documentation directory, which is itself thin on content (only Usage headings with links to installation and docker docs).

Detailed fixes: d19_recommendation.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs found

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming ConsistencyExemplary◐ Sampled · advisory

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.

Maturity: Documented → Verified → Prevented · effective Exemplary / 10 · rule-coverage 100% · ceiling Verified

0 naming inconsistencies across 0 sampled symbols.

✓ On the Gold path — maintain.

Detailed fixes: d21_recommendation.md.

D23 · Boundary Type-Coupling10.0 / 10Exemplary✓ Tool-verified

What it measures: Whether domain types (IDs, enums, value objects) leak across bounded-context boundaries.

Method: Cross-context domain-type leakage via Roslyn structural classification (strongly-typed IDs / value objects) over every public surface. Exhaustive, deterministic, type-level aggregate-boundary check.

Coverage: Bounded contexts derived from NAMESPACE prefix (or graph-inferred where available); cross-boundary domain-type leakage then checked exhaustively over every public member of every type.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Verified

No domain types leak across context boundaries (2 contexts).

✓ On the Gold path — maintain.

Detailed fixes: d23_recommendation.md.

D26 · Project Cohesion2.0 / 10Critical✓ Tool-verified

What it measures: Whether each project is a focused, coherent unit rather than an oversized grab-bag.

Method: Project size overshoot penalties (LoC / public-type count / namespace count, 2-of-3 flag) weighted by log magnitude. Exhaustive across projects, deterministic, LLM-independent.

Maturity: Documented → Verified → Prevented · effective 2.0 / 10 · rule-coverage 100% · ceiling Documented

2 of 5 build units (Composer, npm) flagged as possibly oversized/incoherent.

Split CompositeUi

What to do

  1. Resolve the 1 Split CompositeUi finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.

D28 · Secrets (history)10.0 / 10Exemplary○ Nothing flagged

What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.

Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

gitleaks scanned the full history AND the current working tree and found no secrets.

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)4.1 / 10Weak✓ Tool-verified

What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.

Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.

Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).

Maturity: Documented → Verified → Prevented · effective 4.1 / 10 · rule-coverage 100% · ceiling Documented

17 finding(s): 0 critical, 0 high, 17 medium, 0 low. semgrep hit a parse error in 5 file(s) — `IdentityAccess/.phpspec/class.tpl` (lines 3–5), `IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Symfony/Framework/config/config_dev.yml`, `Notifier/.phpspec/class.tpl` (lines 3–5), `SharedKernel/.phpspec/class.tpl` (lines 3–5), `TaskManager/.phpspec/class.tpl` (lines 3–5) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED

What to do

  1. Resolve the 16 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (16). — One of this dimension's main actionable groups (16 warning-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D30 · Dependency Vulnerabilities0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.

Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

137 finding(s): 31 critical, 71 high, 28 medium, 7 low.

REDACTED
REDACTED
REDACTED
REDACTED
REDACTED

+ 3 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 64 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (62), REDACTED (2). — One of this dimension's main actionable groups (64 issue-level).
  2. Resolve the 30 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (26), REDACTED (4). — One of this dimension's main actionable groups (30 issue-level).
  3. Resolve the 7 High vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 issue-level).

Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.

D31 · IaC & Container Security6.1 / 10Adequate✓ Tool-verified

What it measures: Whether Dockerfiles / Terraform / Kubernetes config follow security best practices.

Method: IaC/container misconfiguration scan via trivy config (REDACTED/Terraform/K8s/Helm/CloudFormation); severity rules to 0-10 moderate normalizer. NotApplicable without manifests. Exhaustive, deterministic.

Maturity: Documented → Verified → Prevented · effective 6.1 / 10 · rule-coverage 100% · ceiling Documented

24 finding(s): 0 critical, 9 high, 7 medium, 8 low.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 9 High IaC finding(s) in IaC & Container Security — start with REDACTED (8), REDACTED. — One of this dimension's main actionable groups (9 issue-level).
  2. Resolve the 8 Low IaC finding(s) in IaC & Container Security — start with REDACTED (8). — One of this dimension's main actionable groups (8 recommendation-level).
  3. Resolve the 7 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3), REDACTED (3), REDACTED. — One of this dimension's main actionable groups (7 warning-level).

Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness0.0 / 10Critical✓ Tool-verified

What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.

Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

53 of 53 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/CreateTaskHandler.php. Counted over 53 of the 361 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×53TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/CreateTaskHandler.php:1
Dormant codebase

What to do

  1. Resolve the 53 Orphaned file finding(s) in Knowledge Freshness — start with AppKernel.php (3), DoctrineORMFilterableSpecification.php (3), AuthenticationListener.php (2). — One of this dimension's main actionable groups (53 recommendation-level).
  2. Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.

D35 · Change Coupling10.0 / 10Stronggated by 1 serious finding✓ Tool-verified

What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.

Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.

Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: AddMember.js↔Show.js 60%

Change coupling: AddMember.js ↔ Show.jsCompositeUi/src/views/page/organization/AddMember.js:1

What to do

  1. Resolve the 1 Change coupling finding(s) in Change Coupling — start with AddMember.js. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

D36 · Supply-chain Provenance & Signing0.0 / 10Critical✓ Tool-verified

What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.

Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

0/3 supply-chain integrity signals present (provenance, signing, SBOM).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  2. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
  3. Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.

D43 · Malicious Dependencies0.0 / 10Critical✓ Tool-verified

What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.

Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

1 finding(s): 0 critical, 0 high, 1 medium, 0 low.

REDACTED

What to do

  1. Resolve the 1 Malicious package finding(s) in Malicious Dependencies — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d43_recommendation.md · top locations in Appendix A, every location in findings.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition6.8 / 10Strong✓ Tool-verified

Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.

Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.

Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).

Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.

Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.

AX5 · Architecture & structure10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.

Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.

DM1 · Aggregate boundaries10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether aggregates reference each other by identity (id) rather than by direct object reference — the core DDD consistency-boundary rule.

Method: Roslyn (DDD-gated): aggregate roots identified by convention; each aggregate field checked for direct references to other aggregates versus id-only. Deterministic, DDD-native.

Coverage: Population: aggregate roots identified by AggregateRoot/IAggregateRoot base/interface NAME convention; reference-by-identity then checked exhaustively within that set — a root not using those names is invisible.

DM11 · Constructible invalid state8.1 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether an aggregate can be constructed in a state its own rules forbid — a public constructor that takes a raw primitive, stores it, and validates nothing, with no factory beside it. A constructor taking only value objects is not counted: each parameter has already validated itself.

Method: Neutral surface (DDD-gated): each non-abstract entity/aggregate checked for a PUBLIC constructor taking at least one RAW PRIMITIVE parameter whose body contains no guard token (throw / Guard. / Ensure. / ArgumentException / CheckRule), on a type that also offers no static Create/Of/From/New factory. A constructor taking only value objects is never charged -- measured: 64 of 87 unguarded public constructors on the C# corpus take value objects only, so ignoring parameter types would be 73% false positives. One finding per entity. Deterministic.

  • `NumericId`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `NumericId` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/NumericId.php:26
  • `Task`'s public constructor takes `description` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Task` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/Task.php:36
  • `TaskCreated`'s public constructor takes `description` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TaskCreated` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse. — TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/TaskCreated.php:34

What to do

  • Give each aggregate one way in that can refuse — a guarded constructor, value-object parameters that validate themselves, or a private constructor behind a factory that returns a failure.
DM12 · Ambient inputs in the domain10.0 / 10Exemplary○ Nothing flagged

Other · Domain Modelling — Whether domain types receive the time and randomness their rules depend on, rather than reading the process clock or a global random source directly — an ambient read makes the rule it feeds untestable at the instant that matters and lets two reads inside one operation disagree.

Method: Roslyn (DDD-gated, C#/VB only): domain-layer types scanned for ambient reads — DateTime/DateTimeOffset.Now/UtcNow/Today, Random.Shared, new Random(), Stopwatch.GetTimestamp — resolved against the semantic model, with a comment/string-stripped token fallback only where resolution fails. Body reads are scored; field/property initialisers are surfaced unscored. Apply/When folds excluded (ES1 owns them). Deterministic, symbol-resolved.

DM4 · Rich vs anemic model6.5 / 10Strong✓ Tool-verified

Other · Domain Modelling — Whether aggregates/entities carry the behaviour that protects their invariants, rather than being data bags driven by external services.

Method: Roslyn (DDD-gated): entity method BODIES classified mutator-vs-query — only methods that mutate the entity's own declared state count as invariant-protecting behaviour, so a getter/passthrough doesn't rescue an anemic class. Deterministic, exhaustive over domain-layer entities.

Coverage: Population: entities by name/base convention; rich-vs-anemic judged by classifying each method body mutator-vs-query — logic-bearing domain types outside the convention are invisible.

  • `ProjectCreated` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — TaskManager/src/Kreta/TaskManager/Domain/Model/Project/ProjectCreated.php:19
  • `ProjectEdited` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — TaskManager/src/Kreta/TaskManager/Domain/Model/Project/ProjectEdited.php:19
  • `TaskCreated` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/TaskCreated.php:21
  • `TaskParentChanged` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service. — TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/TaskParentChanged.php:19
  • `User` 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. — TaskManager/src/Kreta/TaskManager/Domain/Model/User/User.php:19

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 state10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether entities protect their state — private/init-only setters, and collections handed out as read-only views rather than the mutable backing collection — instead of exposing writable state that bypasses invariants. Softened when a rehydration framework (Marten/EF) is present.

Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.

Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.

DM6 · Domain ↔ infrastructure boundary10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies (EF/Marten/HTTP/ASP.NET) — the clean-architecture dependency rule.

Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.

Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.

DM7 · Repository granularity10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether repositories are per aggregate root (not per child entity) and keep the persistence query handle behind the contract, so the root's invariants can't be bypassed.

Method: Roslyn (DDD-gated): repository abstraction detection; repositories over non-aggregate-root entities flagged, and (C#/VB) repository INTERFACES whose members return a live persistence query handle (IQueryable/DbSet/IMongoQueryable) — implementations and specification evaluators are out of population by design, since composing a query internally is what an implementation is for. Deterministic, DDD-native.

Coverage: Population: repositories + aggregate roots by NAME convention; per-root repository rule checked within the set.

DM8 · Value-object opportunities10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether clusters of primitives that travel together (a missing value object) are extracted — a low-weight suggestion, LLM-confirmed when configured.

Method: Roslyn (DDD-gated): primitive parameter clusters recurring three or more times across signatures extracted, then confirmed by language model when configured. Advisory, low-weight.

DM9 · Scattered domain decisions10.0 / 10Exemplary✓ Tool-verified

Other · Domain Modelling — Whether one domain rule is decided — or one measurement produced — in more than one place, rather than living on the type that owns it.

Method: Neutral body surface plus Roslyn (DDD-gated), two arms. DECISION (Roslyn only): a predicate over a domain type's members judged in two or more types, where none of those decisions live on the owning type — operands of comparisons and relational property patterns only, so a member merely passed as an argument is not judged. DERIVATION: a plain all-numeric carrier of ≥2 members, with no base type and exactly one constructor, CONSTRUCTED as the result of a method (returned or assigned, never inline as an argument) in two or more types other than its own — the same measurement produced twice, which centralising the judgement does not fix. DERIVATION runs on every language whose frontend declares the produced-or-passed fact per construction (Roslyn and the Java sidecar today); a target with only the derivation arm carries an engine gap naming the decision arm as not assessed, and a frontend that declares nothing keeps the dimension not measured rather than clean. Single-member rules, test code and generated code are out of population for both. Advisory.

ES1 · Fold determinism10.0 / 10Exemplary✓ Tool-verified

Other · Event Sourcing — Whether Apply/When folds reconstruct state purely from the event (no DateTime.Now, Guid.NewGuid, Random or IO) so replay is reproducible.

Method: Roslyn syntax scan (event-sourcing gated): Apply/When folds checked for forbidden tokens (DateTime.Now, Guid.NewGuid, Random, IO), stripped of comments/strings. Deterministic, hard fact per fold.

M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.

Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
  • Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
  • Add a README to the 5 of 5 project(s) that lack one — worth up to 2 pts.
M2 · Architecture documentation2.0 / 10Weak✓ Tool-verified

Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.

Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repo is organised deliberately — src/test separation and consistent project naming.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

M4 · Documentation accuracy8.0 / 10Strong◐ Sampled · advisory

Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).

Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.

  • README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong. — README.md:26

What to do

  • Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests.
P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether an automated pipeline builds and tests every change.

Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.

P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No logging call was found in the 506 JavaScript/TypeScript, PHP production file(s) this check read across 5 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; PHP: PSR-3 loggers (Monolog), Laravel's Log facade, error_log()) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.

What to do

  • Log through a PSR-3 logger (Monolog, or Laravel's `Log` facade) with a JSON formatter at meaningful points in the applications you run.
  • Consider OpenTelemetry tracing/metrics (opentelemetry-php) and a health-check endpoint (Laravel's /up health route or a /health route) for operability.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).

Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.

  • No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 9346 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.

What to do

  • Add a SAST step to CI running what this repository's stack ships: phpstan or psalm — or `semgrep --config=auto`, which runs on any language — 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.
P4 · Deployment & Rollback8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.

Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.

What to do

  • Add an approval/environment gate (required reviewers / protection rules) before production promotion.
P5 · DR & Backup0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.

Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.

  • A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.

What to do

  • Codify backups + geo-recovery in IaC and document RTO/RPO and the restore procedure — a persistence guard alone is not disaster recovery.
P6 · Release Hygiene8.0 / 10Strong✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • The changelog this check read carries 1 versioned entry, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.

What to do

  • Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
P8 · Schema migrations10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — Whether database schema changes go through versioned migrations rather than being auto-created from the model at startup.

Method: Roslyn scan: EF Core DbContext for a versioned migrations directory versus bare EnsureCreated usage; off .NET, a file scan of dependency manifests, migration histories (Flyway, Liquibase, Alembic, Django, Rails, Prisma, TypeORM, Knex/Sequelize, golang-migrate, goose, Laravel, Doctrine, Diesel/sqlx) and schema auto-create in production source or config. Exhaustive, deterministic.

R1 · Type Safety0.0 / 10Critical✓ Tool-verified

React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.

Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.

  • 0 typed · 159 plain JS — the untyped files are CompositeUi/config/babelRelayPlugin.js, CompositeUi/config/env.js, CompositeUi/config/jest/babelTransform.js, CompositeUi/config/jest/cssTransform.js, CompositeUi/config/jest/fileTransform.js, CompositeUi/config/paths.js (+153 more).

What to do

  • Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
R10 · Code Duplication8.6 / 10Strong✓ Tool-verified

React / JS · Code Health — Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm over JS/TS tokens, D-386): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.

Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Deterministic.

  • CompositeUi/src/views/form/TaskEdit.js:11 · CompositeUi/src/views/form/TaskNew.js:11 — these 2 files are line-for-line copies of one another — 69 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — CompositeUi/src/views/form/TaskEdit.js:11
  • CompositeUi/src/actions/CurrentOrganization.js:127 · CompositeUi/src/actions/CurrentOrganization.js:163 — 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. — CompositeUi/src/actions/CurrentOrganization.js:127
  • CompositeUi/src/views/form/ProjectEdit.js:43 · CompositeUi/src/views/form/ProjectNew.js:37 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — CompositeUi/src/views/form/ProjectEdit.js:43
  • CompositeUi/src/actions/CurrentProject.js:117 · CompositeUi/src/actions/CurrentProject.js:166 — 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. — CompositeUi/src/actions/CurrentProject.js:117
  • CompositeUi/src/actions/User.js:66 · CompositeUi/src/actions/User.js:124 — 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. — CompositeUi/src/actions/User.js:66
  • CompositeUi/src/actions/CurrentOrganization.js:48 · CompositeUi/src/actions/CurrentOrganization.js:88 — 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. — CompositeUi/src/actions/CurrentOrganization.js:48
  • CompositeUi/src/views/form/Login.js:28 · CompositeUi/src/views/form/Register.js:34 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — CompositeUi/src/views/form/Login.js:28
  • CompositeUi/src/views/form/OrganizationNew.js:41 · CompositeUi/src/views/form/ProjectEdit.js:43 · CompositeUi/src/views/form/ProjectNew.js:37 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — CompositeUi/src/views/form/OrganizationNew.js:41
  • CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:30 · CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:30 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:30
  • CompositeUi/src/views/form/ProfileEdit.js:79 · CompositeUi/src/views/form/ProjectEdit.js:51 · CompositeUi/src/views/form/ProjectNew.js:45 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — CompositeUi/src/views/form/ProfileEdit.js:79
  • CompositeUi/config/webpack.config.babel.dev.js:92 · CompositeUi/config/webpack.config.babel.prod.js:94 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — CompositeUi/config/webpack.config.babel.dev.js:92
  • CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:25 · CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:25 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:25
  • CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:42 · CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:42 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:42
  • CompositeUi/src/actions/CurrentProject.js:64 · CompositeUi/src/actions/CurrentProject.js:86 — 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. — CompositeUi/src/actions/CurrentProject.js:64
  • CompositeUi/src/views/page/Register.js:22 · CompositeUi/src/views/page/RequestResetPassword.js:22 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — CompositeUi/src/views/page/Register.js:22
  • CompositeUi/src/views/page/project/Settings.js:22 · CompositeUi/src/views/page/task/Edit.js:28 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — CompositeUi/src/views/page/project/Settings.js:22
  • CompositeUi/src/actions/CurrentOrganization.js:184 · CompositeUi/src/actions/CurrentProject.js:231 · CompositeUi/src/actions/Organization.js:49 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — CompositeUi/src/actions/CurrentOrganization.js:184
  • CompositeUi/src/views/component/Search.js:20 · CompositeUi/src/views/component/SearchMember.js:17 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — CompositeUi/src/views/component/Search.js:20
  • CompositeUi/src/views/form/Register.js:67 · CompositeUi/src/views/form/ResetPassword.js:53 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — CompositeUi/src/views/form/Register.js:67
  • CompositeUi/src/views/page/Login.js:34 · CompositeUi/src/views/page/Register.js:25 · CompositeUi/src/views/page/RequestResetPassword.js:25 · CompositeUi/src/views/page/ResetPassword.js:45 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — CompositeUi/src/views/page/Login.js:34
  • CompositeUi/src/views/page/organization/New.js:18 · CompositeUi/src/views/page/profile/Edit.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — CompositeUi/src/views/page/organization/New.js:18
  • CompositeUi/src/views/component/UserCard.js:16 · CompositeUi/src/views/component/UserThumbnail.js:15 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — CompositeUi/src/views/component/UserCard.js:16
  • CompositeUi/src/views/composition/AssignedTasksDashboardWidget.js:18 · CompositeUi/src/views/composition/LastUpdatedProjectsDashboardWidget.js:20 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — CompositeUi/src/views/composition/AssignedTasksDashboardWidget.js:18
  • CompositeUi/src/views/component/NavigableList.js:93 · CompositeUi/src/views/component/NavigableList.js:118 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — CompositeUi/src/views/component/NavigableList.js:93
  • CompositeUi/src/views/composition/Members.js:137 · CompositeUi/src/views/composition/Projects.js:65 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — CompositeUi/src/views/composition/Members.js:137
  • CompositeUi/src/views/form/RequestResetPassword.js:20 · CompositeUi/src/views/form/TaskEdit.js:25 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — CompositeUi/src/views/form/RequestResetPassword.js:20
  • CompositeUi/src/views/form/ProjectEdit.js:21 · CompositeUi/src/views/form/ProjectNew.js:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. — CompositeUi/src/views/form/ProjectEdit.js:21
  • CompositeUi/src/views/page/project/Root.js:18 · CompositeUi/src/views/page/project/Root.js:32 — the two spans are one implementation copied and then locally edited — 64 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. — CompositeUi/src/views/page/project/Root.js:18
  • CompositeUi/src/api/graphql/GraphQl.js:17 · CompositeUi/src/api/rest/Rest.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — CompositeUi/src/api/graphql/GraphQl.js:17

What to do

  • Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
R11 · Import Boundaries0.0 / 10Critical✓ Tool-verified

React / JS · Architecture — Conformance to the detected frontend architecture layout (feature-sliced / layered src) plus cross-package deep-import rules (D-386).

Method: Conformance to the detected frontend layout (feature-sliced / layered src) plus cross-package deep-import rules, over the module graph. Deterministic.

  • CompositeUi/config/polyfills.js:12 imports promise/lib/rejection-tracking, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/config/polyfills.js:12
  • CompositeUi/config/polyfills.js:13 imports promise/lib/es6-extensions.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/config/polyfills.js:13
  • CompositeUi/src/api/graphql/GraphQl.js:12 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/GraphQl.js:12
  • CompositeUi/src/api/graphql/GraphQl.js:13 imports react-relay/lib/RelayQueryRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/GraphQl.js:13
  • CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:12
  • CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:13
  • CompositeUi/src/api/graphql/mutation/ChangeTaskProgressMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/ChangeTaskProgressMutationRequest.js:12
  • CompositeUi/src/api/graphql/mutation/ChangeTaskProgressMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/ChangeTaskProgressMutationRequest.js:13
  • CompositeUi/src/api/graphql/mutation/CreateOrganizationMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/CreateOrganizationMutationRequest.js:12
  • CompositeUi/src/api/graphql/mutation/CreateOrganizationMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/CreateOrganizationMutationRequest.js:13
  • CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:12
  • CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:13
  • CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:12
  • CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:13
  • CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:12
  • CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:13
  • CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:12
  • CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:13
  • CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:12
  • CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:13
  • CompositeUi/src/api/graphql/query/OrganizationQueryRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/OrganizationQueryRequest.js:12
  • CompositeUi/src/api/graphql/query/OrganizationQueryRequest.js:13 imports react-relay/lib/RelayQueryRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/OrganizationQueryRequest.js:13
  • CompositeUi/src/api/graphql/query/OrganizationsQueryRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/OrganizationsQueryRequest.js:12
  • CompositeUi/src/api/graphql/query/OrganizationsQueryRequest.js:13 imports react-relay/lib/RelayQueryRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/OrganizationsQueryRequest.js:13
  • CompositeUi/src/api/graphql/query/ProjectQueryRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/ProjectQueryRequest.js:12
  • CompositeUi/src/api/graphql/query/ProjectQueryRequest.js:13 imports react-relay/lib/RelayQueryRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/ProjectQueryRequest.js:13
  • CompositeUi/src/api/graphql/query/ProjectsQueryRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/ProjectsQueryRequest.js:12
  • CompositeUi/src/api/graphql/query/ProjectsQueryRequest.js:13 imports react-relay/lib/RelayQueryRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/ProjectsQueryRequest.js:13
  • CompositeUi/src/api/graphql/query/TasksQueryRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/TasksQueryRequest.js:12
  • CompositeUi/src/api/graphql/query/TasksQueryRequest.js:13 imports react-relay/lib/RelayQueryRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead. — CompositeUi/src/api/graphql/query/TasksQueryRequest.js:13

What to do

  • Fix the listed violations: import through public entries (package exports / slice index), never reach into another layer or package's internals.
R2 · Cyclomatic Complexity10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.

Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.

R3 · Large Files10.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — How many source files exceed the large-file threshold.

Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.

R4 · Test Coverage8.1 / 10Strong✓ Tool-verified

React / JS · Readiness — Static test reachability (D-386): the share of production files reachable from any test via the import graph — measured without running anything.

Method: Static test reachability: the share of production files reachable from any test via the import graph — measured without running anything. Deterministic.

  • 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. (×26) — REDACTED:1, CompositeUi/src/reducers/CurrentProject.js:1, CompositeUi/scripts/build.js:1, …

What to do

  • Add tests that import the unreached modules (directly or through their public entry).
R6 · Tooling6.7 / 10Strong✓ Tool-verified

React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.

Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.

  • 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 type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as package.json scripts and run them in CI.
R7 · Dead Code9.0 / 10Exemplary✓ Tool-verified

React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).

Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.

  • Unreachable from the 4 application, 6 tooling and 16 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 (4 application, 6 tooling, 16 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 (×8) — REDACTED, CompositeUi/src/views/component/LogoHeader.js, CompositeUi/config/jest/cssTransform.js, …

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 Hygiene3.0 / 10Weak✓ Tool-verified

React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.

Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.

  • Imported but not declared in any reachable package.json — installs work only by hoisting accident. — CompositeUi/src/views/layout/Root.js:14
  • Declared in CompositeUi/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it. (×3)

What to do

  • Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
R9 · Circular Imports4.7 / 10Adequate✓ Tool-verified

React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.

Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.

  • CompositeUi/src/Routes.js → CompositeUi/src/views/layout/Base.js → CompositeUi/src/actions/Profile.js → CompositeUi/src/actions/User.js → CompositeUi/src/Routes.js (one verified cycle inside a mutually-dependent group of 38 files) — CompositeUi/src/Routes.js:16

What to do

  • Break each cycle by extracting the shared piece into a module both sides can import.
S1 · Web-Security Posture8.0 / 10Strong✓ Tool-verified

Other · Security — Only what this repository's own non-C# files could be read for was assessed — and because this repository commits the configuration that serves its own HTTP surface, that configuration could be read in full for the security response headers it sets. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.

Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.

  • None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` builds the web-server image that serves this application, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.) — REDACTED:9

What to do

  • Set security response headers on the surface this repository serves: an `add_header` directive per header in the nginx/Caddy/Apache config, a `_headers` / `vercel.json` / `netlify.toml` entry for a static host, or `helmet()` in the HTTP server. `Content-Security-Policy` is the one that pays for itself first — it is what contains an injected script once one reaches the page — followed by `X-Content-Type-Options: nosniff` and a frame policy (`X-Frame-Options: DENY`, or CSP `frame-ancestors`). Where the app is served from a build container, the header configuration belongs in the image beside the built assets, so it ships with them rather than depending on where it lands.
X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.

Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.

X12 · Unreachable branch10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.

Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.

X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.

Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.

X14 · Bypassable address classification10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.

Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.

X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.

Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.

X16 · Unfloored truncation loop10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.

Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.

X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged

Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.

Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.

X18 · Disposal-pattern correctness10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.

Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.

X19 · Unrestored process-global state10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.

Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.

X21 · Side-effecting pattern guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.

Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.

X22 · Contradicted release guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.

Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.

X23 · Unguarded diagnostic materialisation10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.

Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.

X24 · Document value interpolated into markup unescaped3.5 / 10Weak✓ Tool-verified

Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.

Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.

  • `children` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup. — REDACTED:19

What to do

  • Each finding names the expression, the attribute it lands in and the line. Confirm the value's origin from the read this analyzer traced, then escape it at the sink or validate it against the shape the attribute accepts before interpolating.
X25 · Inert configuration knob10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.

Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.

X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.

Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.

X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.

Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.

X3 · Exception handling7.4 / 10Strong✓ Tool-verified

Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.

Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.

  • `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — SharedKernel/src/Kreta/SharedKernel/Infrastructure/Messaging/AMQP/PhpAmqpLib/PhpAmqpLibAMQPConsumer.php:62

What to do

  • Swallowed exception (caught, then discarded)
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.

Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.

X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether PHP's static analysis checks null and is not undermined by a nullness baseline — PHPStan from level 8 (`checkNullables`) or Psalm at `errorLevel` 3 or stricter is what makes `?User` a type whose method call is an error, and the null entries of a baseline, `@psalm-suppress PossiblyNull…` and `@phpstan-ignore *.nonObject` are what silence it.

Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.

  • This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.

What to do

  • Raise PHPStan to level 8 (`level: 8` in `phpstan.neon.dist`, or `max`) or Psalm to `errorLevel="3"` or stricter, so `?Type` is a type the checker holds you to; generate a baseline for what that surfaces only to pay it down, not to keep it. Then resolve the baselined nullness errors rather than adding to them: each is a call on a value the checker showed could be null — narrow it (`if ($x === null) { … }`, `?->`, an early return), make the property non-nullable and initialise it in the constructor, or change the return type so the null cannot arrive.

Reference — by lens

The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.

LensScoreRatingImpact
Code Health51%Adequate — gated by R1, X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture50%Adequate — gated by D26, R11Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Maturity51%Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness25%Weak — gated by R8, P2, P3, P5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security54%Adequate — gated by D30, D36, D43Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Domain Modelling86%ExemplarySolid.
Event Sourcing100%ExemplaryStrongest area.
Unscored — 1 check(s) recorded observations but carry no score

These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.

  • X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not included — 62 check(s) not relevant to this codebase

These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.

  • AC1 Text alternatives — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC2 Forms & labels — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC3 Page structure — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC4 Keyboard semantics — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC5 ARIA correctness — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC6 Visual & motion safety — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
  • AC7 A11y enforcement — Frontend below the scale floor (17 DOM element(s) < 25) — too little surface to assess accessibility.
  • AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX2 Stateful singletons — Not applicable: PHP builds its object graph per request and shares none of it between requests. 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).
  • AX6 Interface segregation — not assessed — interface segregation is computed over a type surface that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 15 — the compose project is invalid) — time="2026-10-22T21:24:40Z" level=warning msg="The \"COMPOSITE_UI_HOST\" variable is not set. Defaulting to a blank string." validating REDACTED: services.php.extra_hosts array items[0,1] must be unique; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no data at rest for these controls to protect.
  • C2 Access Controls — No access-control surface detected in the analyzed source — this repository registers no route (no Laravel Route::…, no Symfony #[Route], no Filament panel, no WordPress REST route or AJAX action). Access control is therefore N/A here — a Composer library is authorized by the application that mounts it, not by itself. 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, first_name, date_of_birth, phone_number, …) or stored credential in a Laravel migration, an Eloquent model's $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) 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, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, first_name, date_of_birth, phone, …) or stored credential in a Laravel migration, an Eloquent $fillable/$hidden list or a Doctrine #[ORM\Column] property — and no database client (PDO, mysqli, Laravel's DB facade, $wpdb) in the source either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D11 Test Reliability — No tests discovered
  • D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D24 Comment Value — No inline comments to assess — comment value is not applicable here.
  • D25 ADR Conformance — no ADRs to check
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.php), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in CompositeUi/ ran and not one test passed ( FAIL  src/reducers/__tests__/CurrentOrganization.spec.js), 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
  • 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
  • ES2 Immutable events — no persisted event types detected — immutability check not applicable
  • ES3 PII in the event store — no persisted event types detected — PII-in-events check not applicable
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — 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
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — no outbound HTTP usage detected — no HTTP client call or construction in the JavaScript/TypeScript, PHP source (service entry point: TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/Controller/GraphiQLController.php:20 (extends Controller))
  • P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — with Xdebug (`XDEBUG_MODE=coverage`) or PCOV installed, `vendor/bin/phpunit --coverage-clover coverage.xml`) 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 PHPBench subjects (`bench*` methods, or `@Subject`/`#[Subject]` ones) in a file importing PhpBench or carrying its annotations, `bench*` methods in a `*Bench.php` file where PHPBench is installed, or phpbench/phpbench in a composer.json or a phpbench.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 applicable: PHP and TypeScript/JavaScript runs on a garbage-collected runtime that gives a program no allocation-control idiom to choose on a hot path — no pools, stack allocation or value types — so allocation awareness is not something this code can be rated on.
  • PF3 Async & latency hygiene — Not applicable: PHP has no async/await function colour, so there is no asynchronous code for a blocking call to stall.
  • R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D30 (Dependency Vulnerabilities), which answers every ecosystem
  • SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X2 Cancellation propagation — no C# was loaded; this repository's PHP was read and makes no request a caller can cancel (amphp's HttpClient or connect) — synchronous PHP offers its callers no cancellation to take
  • 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. PHP gives a request one thread of its own; the event-loop libraries (ReactPHP, Amp) run callbacks one at a time, and ext-parallel copies every value across its channels, so no array or 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 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
  • 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)

The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.

Critical — 120 finding(s)
D30 · Dependency Vulnerabilities · High CVE · ×64
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 39 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Critical CVE · ×30
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 5 more in this group — see findings.md.
D31 · IaC & Container Security · High IaC · ×9
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D10 · Test Quality · No assertions (empty test) · ×7
  • No assertions (empty test): fetches projects CompositeUi/src/actions/__tests__/CurrentProject.spec.js:17 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): changes selected task CompositeUi/src/actions/__tests__/CurrentProject.spec.js:19 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): creates an task CompositeUi/src/actions/__tests__/CurrentProject.spec.js:21 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): it handles errors on invalid task creation attempt CompositeUi/src/actions/__tests__/CurrentProject.spec.js:23 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): updates an task CompositeUi/src/actions/__tests__/CurrentProject.spec.js:25 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): filters tasks CompositeUi/src/actions/__tests__/CurrentProject.spec.js:27 — Test method has an empty body — it asserts nothing and exercises no code.
  • No assertions (empty test): adds a participant CompositeUi/src/actions/__tests__/CurrentProject.spec.js:29 — Test method has an empty body — it asserts nothing and exercises no code.
D30 · Dependency Vulnerabilities · High vulnerability · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Critical vulnerability · ×1
  • REDACTED
R8 · Dependency Hygiene · Unlisted import 'invariant' · ×1
  • Unlisted import 'invariant' CompositeUi/src/views/layout/Root.js:14 — Imported but not declared in any reachable package.json — installs work only by hoisting accident.
R9 · Circular Imports · Import cycle (4 files) · ×1
  • Import cycle (4 files) CompositeUi/src/Routes.js:16 — CompositeUi/src/Routes.js → CompositeUi/src/views/layout/Base.js → CompositeUi/src/actions/Profile.js → CompositeUi/src/actions/User.js → CompositeUi/src/Routes.js (one verified cycle inside a mutually-dependent group of 38 files)
Serious — 210 finding(s)
R11 · Import Boundaries · Boundary violation [package · ×30
  • Boundary violation [package:third-party-deep-import] CompositeUi/config/polyfills.js:12 — CompositeUi/config/polyfills.js:12 imports promise/lib/rejection-tracking, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/config/polyfills.js:13 — CompositeUi/config/polyfills.js:13 imports promise/lib/es6-extensions.js, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/GraphQl.js:12 — CompositeUi/src/api/graphql/GraphQl.js:12 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/GraphQl.js:13 — CompositeUi/src/api/graphql/GraphQl.js:13 imports react-relay/lib/RelayQueryRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:12 — CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:13 — CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/ChangeTaskProgressMutationRequest.js:12 — CompositeUi/src/api/graphql/mutation/ChangeTaskProgressMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/ChangeTaskProgressMutationRequest.js:13 — CompositeUi/src/api/graphql/mutation/ChangeTaskProgressMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/CreateOrganizationMutationRequest.js:12 — CompositeUi/src/api/graphql/mutation/CreateOrganizationMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/CreateOrganizationMutationRequest.js:13 — CompositeUi/src/api/graphql/mutation/CreateOrganizationMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:12 — CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:13 — CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:12 — CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:13 — CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:12 — CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:13 — CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:12 — CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:13 — CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:12 — CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:13 — CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:13 imports react-relay/lib/RelayMutationRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/query/OrganizationQueryRequest.js:12 — CompositeUi/src/api/graphql/query/OrganizationQueryRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/query/OrganizationQueryRequest.js:13 — CompositeUi/src/api/graphql/query/OrganizationQueryRequest.js:13 imports react-relay/lib/RelayQueryRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/query/OrganizationsQueryRequest.js:12 — CompositeUi/src/api/graphql/query/OrganizationsQueryRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/query/OrganizationsQueryRequest.js:13 — CompositeUi/src/api/graphql/query/OrganizationsQueryRequest.js:13 imports react-relay/lib/RelayQueryRequest, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • Boundary violation [package:third-party-deep-import] CompositeUi/src/api/graphql/query/ProjectQueryRequest.js:12 — CompositeUi/src/api/graphql/query/ProjectQueryRequest.js:12 imports react-relay/lib/RelayQuery, reaching past a declared dependency's public entry into its build output — that path is the package's toolchain layout, not its API, and a minor version bump can relocate it with no semver signal. Import from the package's documented entry point instead.
  • + 5 more in this group — see findings.md.
R4 · Test Coverage · No test reaches this file · ×26
  • No test reaches this file REDACTED:1 — 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.
  • No test reaches this file CompositeUi/src/reducers/CurrentProject.js:1 — 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.
  • No test reaches this file CompositeUi/scripts/build.js:1 — 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.
  • No test reaches this file CompositeUi/scripts/start.js:1 — 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.
  • No test reaches this file CompositeUi/config/paths.js:1 — 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.
  • No test reaches this file CompositeUi/src/reducers/Profile.js:1 — 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.
  • No test reaches this file CompositeUi/scripts/utils/printBuildError.js:1 — 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.
  • No test reaches this file CompositeUi/src/reducers/Notification.js:1 — 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.
  • No test reaches this file CompositeUi/src/reducers/Projects.js:1 — 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.
  • No test reaches this file CompositeUi/src/reducers/User.js:1 — 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.
  • No test reaches this file CompositeUi/src/reducers/Dashboard.js:1 — 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.
  • No test reaches this file CompositeUi/src/views/layout/Root.js:1 — 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.
  • No test reaches this file CompositeUi/src/reducers/MainMenu.js:1 — 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.
  • No test reaches this file CompositeUi/src/Reducers.js:1 — 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.
  • No test reaches this file CompositeUi/src/reducers/Organization.js:1 — 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.
  • No test reaches this file CompositeUi/config/env.js:1 — 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.
  • No test reaches this file CompositeUi/src/stores/Store.js:1 — 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.
  • No test reaches this file CompositeUi/scripts/test.js:1 — 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.
  • No test reaches this file CompositeUi/src/Kreta.js:1 — 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.
  • No test reaches this file CompositeUi/src/views/component/LogoHeader.js:1 — 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.
  • No test reaches this file CompositeUi/config/jest/cssTransform.js:1 — 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.
  • No test reaches this file CompositeUi/src/api/graphql/IdentityAccessGraphQl.js:1 — 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.
  • No test reaches this file CompositeUi/src/api/rest/TaskManagerRest.js:1 — 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.
  • No test reaches this file CompositeUi/config/jest/babelTransform.js:1 — 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.
  • No test reaches this file CompositeUi/config/jest/fileTransform.js:1 — 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.
  • + 1 more in this group — see findings.md.
D30 · Dependency Vulnerabilities · Medium CVE · ×25
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Deprecated · ×8
  • Deprecated: babel-eslint CompositeUi/package.json:108 — babel-eslint 7.2.3, declared in CompositeUi/package.json, is marked deprecated by its publisher: "babel-eslint is now @babel/eslint-parser. This package will no longer receive updates.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: babel-preset-es2015 CompositeUi/package.json:113 — babel-preset-es2015 6.24.1, declared in CompositeUi/package.json, is marked deprecated by its publisher: "🙌 Thanks for using Babel: we recommend using babel-preset-env now: please read https://babeljs.io/env to update!". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: babel-relay-plugin CompositeUi/package.json:117 — babel-relay-plugin 0.11.0, declared in CompositeUi/package.json, is marked deprecated by its publisher: "Replaced by the new babel-plugin-relay". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint CompositeUi/package.json:127 — eslint 4.4.1, declared in CompositeUi/package.json, is marked deprecated by its publisher: "This version is no longer supported. Please see https://eslint.org/version-support for other options.". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: eslint-loader CompositeUi/package.json:128 — eslint-loader 1.9.0, declared in CompositeUi/package.json, is marked deprecated by its publisher: "This loader has been deprecated. Please use eslint-webpack-plugin". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: extract-text-webpack-plugin CompositeUi/package.json:133 — extract-text-webpack-plugin 3.0.0, declared in CompositeUi/package.json, is marked deprecated by its publisher: "Deprecated. Please use https://github.com/webpack-contrib/mini-css-extract-plugin". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: html-webpack-plugin CompositeUi/package.json:138 — html-webpack-plugin 2.30.1, declared in CompositeUi/package.json, is marked deprecated by its publisher: "out of support". Replace it with the package or version that message names, or record why this one must stay.
  • Deprecated: node-sass CompositeUi/package.json:142 — node-sass 4.5.3, declared in CompositeUi/package.json, is marked deprecated by its publisher: "Node Sass is no longer supported. Please use `sass` or `sass-embedded` instead.". Replace it with the package or version that message names, or record why this one must stay.
D31 · IaC & Container Security · Medium IaC · ×7
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
DM4 · Rich vs anemic model · Anemic entity · ×5
  • Anemic entity: ProjectCreated TaskManager/src/Kreta/TaskManager/Domain/Model/Project/ProjectCreated.php:19 — `ProjectCreated` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: ProjectEdited TaskManager/src/Kreta/TaskManager/Domain/Model/Project/ProjectEdited.php:19 — `ProjectEdited` is an aggregate/entity with 2 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: TaskCreated TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/TaskCreated.php:21 — `TaskCreated` is an aggregate/entity with 10 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: TaskParentChanged TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/TaskParentChanged.php:19 — `TaskParentChanged` is an aggregate/entity with 3 data propert(ies) but no state-changing behaviour (only data and queries) — the business logic lives in a service.
  • Anemic entity: User TaskManager/src/Kreta/TaskManager/Domain/Model/User/User.php:19 — `User` 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×4
  • Duplicated block (12 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationOfIdHandler.php:41 — TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationOfIdHandler.php:41-52 | TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationOfSlugHandler.php:40-51 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationOfIdHandler.php` and `TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationOfSlugHandler.php` as WHOLE FILES: 85% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationOfIdHandler.php:41` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (12 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Query/Project/CountProjectsHandler.php:53 — TaskManager/src/Kreta/TaskManager/Application/Query/Project/CountProjectsHandler.php:53-64 | TaskManager/src/Kreta/TaskManager/Application/Query/Project/FilterProjectsHandler.php:58-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/Query/Project/CountProjectsHandler.php:53` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (12 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:41 — TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:41-52 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Project/DoctrineORMFilterableSpecification.php:40-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
  • Duplicated block (12 lines × 2) Notifier/src/Kreta/Notifier/Infrastructure/Symfony/HttpAction/MarkAsReadNotificationAction.php:37 — Notifier/src/Kreta/Notifier/Infrastructure/Symfony/HttpAction/MarkAsReadNotificationAction.php:37-48 | Notifier/src/Kreta/Notifier/Infrastructure/Symfony/HttpAction/MarkAsUnreadNotificationAction.php:37-48 — before extracting anything, compare `Notifier/src/Kreta/Notifier/Infrastructure/Symfony/HttpAction/MarkAsReadNotificationAction.php` and `Notifier/src/Kreta/Notifier/Infrastructure/Symfony/HttpAction/MarkAsUnreadNotificationAction.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D30 · Dependency Vulnerabilities · Medium vulnerability · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×3
  • Duplicated block (9 lines × 2) SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:70 — SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:70-78 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/EventListener/AuthenticationListener.php:70-78 — before extracting anything, compare `SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php` and `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/EventListener/AuthenticationListener.php` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 2) Notifier/src/Kreta/Notifier/Application/Inbox/Notification/MarkAsReadNotification.php:35 — Notifier/src/Kreta/Notifier/Application/Inbox/Notification/MarkAsReadNotification.php:35-43 | Notifier/src/Kreta/Notifier/Application/Inbox/Notification/MarkAsUnreadNotification.php:35-43 — before extracting anything, compare `Notifier/src/Kreta/Notifier/Application/Inbox/Notification/MarkAsReadNotification.php` and `Notifier/src/Kreta/Notifier/Application/Inbox/Notification/MarkAsUnreadNotification.php` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (9 lines × 2) Notifier/src/Kreta/Notifier/Domain/Event/Inbox/UserSignedUpSubscriber.php:34 — Notifier/src/Kreta/Notifier/Domain/Event/Inbox/UserSignedUpSubscriber.php:34-42 | TaskManager/src/Kreta/TaskManager/Domain/Event/User/UserRegisteredSubscriber.php:34-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×3
  • Duplicated block (8 lines × 2) SharedKernel/src/Kreta/SharedKernel/Infrastructure/Persistence/Fake/FakeDataCapabilities.php:41 — SharedKernel/src/Kreta/SharedKernel/Infrastructure/Persistence/Fake/FakeDataCapabilities.php:41-48 | SharedKernel/src/Kreta/SharedKernel/Infrastructure/Persistence/Fake/UserFakeData.php:33-40 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Command/Organization/AddOrganizationMemberToOrganizationHandler.php:39 — TaskManager/src/Kreta/TaskManager/Application/Command/Organization/AddOrganizationMemberToOrganizationHandler.php:39-46 | TaskManager/src/Kreta/TaskManager/Application/Command/Organization/AddOwnerToOrganizationHandler.php:39-46 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Application/Command/Organization/AddOrganizationMemberToOrganizationHandler.php` and `TaskManager/src/Kreta/TaskManager/Application/Command/Organization/AddOwnerToOrganizationHandler.php` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
  • Duplicated block (8 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:69 — TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:69-76 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Project/DoctrineORMFilterableSpecification.php:61-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
DM11 · Constructible invalid state · Constructible in an invalid state · ×3
  • Constructible in an invalid state: NumericId TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/NumericId.php:26 — `NumericId`'s public constructor takes `id` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `NumericId` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: Task TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/Task.php:36 — `Task`'s public constructor takes `description` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `Task` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
  • Constructible in an invalid state: TaskCreated TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/TaskCreated.php:34 — `TaskCreated`'s public constructor takes `description` as raw primitives, and neither of the two things that would make that safe was found. What was searched, so you can tell an absence from a miss: for VALIDATION, the constructor body was scanned for `throw`, `Guard.`, `Ensure.`, `ArgumentNullException`, `ArgumentException`, `CheckRule` or `Requires.` — a guard reached through a helper method those tokens do not name is not seen; for a FACTORY, only this type's OWN static members were read, and only names beginning `Create`, `Of`, `From`, `New` or `Build` — one inherited from a base type, one on a companion builder, or one called `Parse`, `Make` or `Rehydrate` is not seen. If either exists, this row is wrong. If neither does, a caller can build a `TaskCreated` that breaks the rules it exists to enforce, and every rule downstream then has to cope with a state the model said was impossible. Guard in the constructor, take value objects that validate themselves, or make the constructor private behind a `Create` that can refuse.
R7 · Dead Code · Dead file (~22 LoC) · ×3
  • Dead file (~22 LoC) CompositeUi/config/jest/cssTransform.js — no import path from any entry point (4 application, 6 tooling, 16 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
  • Dead file (~22 LoC) CompositeUi/src/api/graphql/IdentityAccessGraphQl.js — no import path from any entry point (4 application, 6 tooling, 16 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
  • Dead file (~22 LoC) CompositeUi/src/api/rest/TaskManagerRest.js — no import path from any entry point (4 application, 6 tooling, 16 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
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/MemberResolver.php:69 — TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/MemberResolver.php:69-91 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/MemberResolver.php:102-124 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/MemberResolver.php:69` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
  • Duplicated block (23 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationMemberResolver.php:42 — TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationMemberResolver.php:42-64 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OwnerResolver.php:42-64 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationMemberResolver.php:42` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10 lines × 3) · ×2
  • Duplicated block (10 lines × 3) TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46 — TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46-55 | TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php:46-59 | TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ReassignTaskHandler.php:45-54 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php` and `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php:46` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (10 lines × 3) TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46 — TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46-55 | TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php:48-59 | TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/TaskOfIdHandler.php:51-61 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php` and `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php:48` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20161022171904.php:24 — TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20161022171904.php:24-30 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20161022171904.php:38-44 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) Notifier/src/Kreta/Notifier/Domain/Model/Inbox/Notification/Notification.php:101 — Notifier/src/Kreta/Notifier/Domain/Model/Inbox/Notification/Notification.php:101-107 | Notifier/src/Kreta/Notifier/Domain/Model/Inbox/User.php:44-50 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×2
  • Duplicated block (18 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Command/Organization/RemoveOrganizationMemberToOrganizationCommand.php:25 — TaskManager/src/Kreta/TaskManager/Application/Command/Organization/RemoveOrganizationMemberToOrganizationCommand.php:25-42 | TaskManager/src/Kreta/TaskManager/Application/Command/Organization/RemoveOwnerToOrganizationCommand.php:25-42 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Application/Command/Organization/RemoveOrganizationMemberToOrganizationCommand.php` and `TaskManager/src/Kreta/TaskManager/Application/Command/Organization/RemoveOwnerToOrganizationCommand.php` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/Command/Organization/RemoveOrganizationMemberToOrganizationCommand.php:25` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (18 lines × 2) TaskManager/src/Kreta/TaskManager/Domain/Model/Organization/OrganizationMemberRemoved.php:28 — TaskManager/src/Kreta/TaskManager/Domain/Model/Organization/OrganizationMemberRemoved.php:28-45 | TaskManager/src/Kreta/TaskManager/Domain/Model/Organization/OwnerRemoved.php:28-45 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Domain/Model/Organization/OrganizationMemberRemoved.php` and `TaskManager/src/Kreta/TaskManager/Domain/Model/Organization/OwnerRemoved.php` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Domain/Model/Organization/OrganizationMemberRemoved.php:28` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
R10 · Code Duplication · Duplicated block (32 lines × 2 locations) · ×2
  • Duplicated block (32 lines × 2 locations) CompositeUi/src/actions/CurrentProject.js:117 — CompositeUi/src/actions/CurrentProject.js:117 · CompositeUi/src/actions/CurrentProject.js:166 — 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.
  • Duplicated block (32 lines × 2 locations) CompositeUi/src/actions/User.js:66 — CompositeUi/src/actions/User.js:66 · CompositeUi/src/actions/User.js:124 — 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.
R10 · Code Duplication · Duplicated block (17 lines × 2 locations) · ×2
  • Duplicated block (17 lines × 2 locations) CompositeUi/src/views/component/Search.js:20 — CompositeUi/src/views/component/Search.js:20 · CompositeUi/src/views/component/SearchMember.js:17 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (17 lines × 2 locations) CompositeUi/src/views/form/Register.js:67 — CompositeUi/src/views/form/Register.js:67 · CompositeUi/src/views/form/ResetPassword.js:53 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (12 lines × 2 locations) · ×2
  • Duplicated block (12 lines × 2 locations) CompositeUi/src/views/component/NavigableList.js:93 — CompositeUi/src/views/component/NavigableList.js:93 · CompositeUi/src/views/component/NavigableList.js:118 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
  • Duplicated block (12 lines × 2 locations) CompositeUi/src/views/composition/Members.js:137 — CompositeUi/src/views/composition/Members.js:137 · CompositeUi/src/views/composition/Projects.js:65 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
D1 · Cyclomatic Complexity · CurrentProject.reducer (cyclomatic 17) · ×1
  • CurrentProject.reducer (cyclomatic 17) CompositeUi/src/reducers/CurrentProject.js:102 — CurrentProject.reducer has cyclomatic complexity 17 (threshold 15). Of this number, 16 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: AddMember.js ↔ Show.js CompositeUi/src/views/page/organization/AddMember.js:1 — `CompositeUi/src/views/page/organization/AddMember.js` and `CompositeUi/src/views/page/organization/Show.js` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `a8ebd37d` Moved memeber management from REST to GraphQl endpoints; `1630a3ea` Fixes and refactor related to add member; `92bd472c` Refactored the member preview replacing deprecated user preview (at that commit the file was still `CompositeUi/src/views/page/organization/AddMemberToOrganization.js`) — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (34 corresponding lines) · ×1
  • Edited copy of a member (34 corresponding lines) TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php:100 — TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php:100-135 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/Task/TasksResolver.php:122-162 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (4 members, 50+ identical tokens) TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:45 — TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:45-63 | TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php:45-72 | TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ReassignTaskHandler.php:44-66 | TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/TaskOfIdHandler.php:48-68 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication · Duplicated block (41–42 lines × 2) · ×1
  • Duplicated block (41–42 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:59 — TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:59-99 | TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php:64-105 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php` and `TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (37 lines × 2) · ×1
  • Duplicated block (37 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Organization/AddMemberToOrganizationMutation.php:46 — TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Organization/AddMemberToOrganizationMutation.php:46-82 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Organization/RemoveMemberToOrganizationMutation.php:46-82 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Organization/AddMemberToOrganizationMutation.php` and `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Organization/RemoveMemberToOrganizationMutation.php` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Organization/AddMemberToOrganizationMutation.php:46` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (32 lines × 3) · ×1
  • Duplicated block (32 lines × 3) TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:82 — TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:82-113 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php:104-135 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/Task/TasksResolver.php:131-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:82` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (10–27 lines × 2) · ×1
  • Duplicated block (10–27 lines × 2) IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Symfony/Framework/AppKernel.php:87 — IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Symfony/Framework/AppKernel.php:87-96 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/Framework/AppKernel.php:45-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Symfony/Framework/AppKernel.php:87` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×1
  • Duplicated block (22 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:127 — TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:127-148 | TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php:141-162 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php` and `TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:47 — SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:47-65 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/EventListener/AuthenticationListener.php:47-65 — before extracting anything, compare `SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php` and `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/EventListener/AuthenticationListener.php` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: `User` names `Kreta\SharedKernel\Infrastructure\Symfony\Security\User` in one and `Kreta\TaskManager\Infrastructure\Symfony\Security\User` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (18 lines × 3) · ×1
  • Duplicated block (18 lines × 3) Notifier/src/Kreta/Notifier/Infrastructure/Serialization/Inbox/Notification/SymfonyNotificationMarkedAsReadDenormalizer.php:38 — Notifier/src/Kreta/Notifier/Infrastructure/Serialization/Inbox/Notification/SymfonyNotificationMarkedAsReadDenormalizer.php:38-55 | Notifier/src/Kreta/Notifier/Infrastructure/Serialization/Inbox/Notification/SymfonyNotificationMarkedAsUnreadDenormalizer.php:38-55 | Notifier/src/Kreta/Notifier/Infrastructure/Serialization/Inbox/Notification/SymfonyNotificationPublishedDenormalizer.php:42-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Notifier/src/Kreta/Notifier/Infrastructure/Serialization/Inbox/Notification/SymfonyNotificationMarkedAsReadDenormalizer.php:38` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (14–18 lines × 2) · ×1
  • Duplicated block (14–18 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46 — TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46-59 | TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php:46-63 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php` and `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php:46` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) Notifier/src/Kreta/Notifier/Infrastructure/Domain/Model/Inbox/EventStoreUserRepository.php:57 — Notifier/src/Kreta/Notifier/Infrastructure/Domain/Model/Inbox/EventStoreUserRepository.php:57-70 | Notifier/src/Kreta/Notifier/Infrastructure/Domain/Model/Inbox/Notification/EventStoreNotificationRepository.php:57-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×1
  • Duplicated block (13 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:42 — TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:42-54 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php:56-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:42` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php:53` calls `isset` and `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:41` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×1
  • Duplicated block (12 lines × 3) TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMOrganizationRepository.php:54 — TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMOrganizationRepository.php:54-65 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Project/DoctrineORMProjectRepository.php:53-64 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Project/Task/DoctrineORMTaskRepository.php:48-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×1
  • Duplicated block (11 lines × 3) TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationMemberOfIdHandler.php:39 — TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationMemberOfIdHandler.php:39-49 | TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationOfIdHandler.php:38-48 | TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OwnerOfIdHandler.php:39-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:53 — TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:53-62 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:77-86 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:63` calls `setFirstResult` and `TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:87` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×1
  • Duplicated block (6 lines × 2) TaskManager/src/Kreta/TaskManager/Application/DataTransformer/Project/Task/TaskDTODataTransformer.php:54 — TaskManager/src/Kreta/TaskManager/Application/DataTransformer/Project/Task/TaskDTODataTransformer.php:54-59 | TaskManager/src/Kreta/TaskManager/Application/DataTransformer/Project/Task/TaskDTODataTransformer.php:62-67 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/DataTransformer/Project/Task/TaskDTODataTransformer.php:54` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×1
  • Duplicated block (5 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:104 — TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:104-108 | TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php:110-114 — before extracting anything, compare `TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php` and `TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:104` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×1
  • Duplicated block (10 lines × 6) IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Persistence/Doctrine/Migrations/Version20161101130554.php:24 — IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Persistence/Doctrine/Migrations/Version20161101130554.php:24-33 | IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Persistence/Doctrine/Migrations/Version20170212142132.php:24-33 | IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Persistence/Doctrine/Migrations/Version20170731164211.php:24-33 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20161214205121.php:24-33 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20170307182355.php:24-33 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20170727174543.php:24-33 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Persistence/Doctrine/Migrations/Version20161101130554.php:24` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D43 · Malicious Dependencies · Malicious package · ×1
  • REDACTED
D8 · Code Coverage · Coverage not measured · ×1
  • Coverage not measured — JavaScript/TypeScript suite — Coverage NOT MEASURED: the JavaScript/TypeScript half could not be measured — the jest suite in CompositeUi/ ran and not one test passed ( FAIL  src/reducers/__tests__/CurrentOrganization.spec.js), 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.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging call was found in the 506 JavaScript/TypeScript, PHP production file(s) this check read across 5 module(s). Each was searched for its ecosystem's logging libraries (JavaScript/TypeScript: pino, winston, bunyan, log4js, loglevel, consola, the NestJS Logger; PHP: PSR-3 loggers (Monolog), Laravel's Log facade, error_log()) and for a call on a receiver named `log`/`logger` (or ending in `Logger`/`_logger`) with a level verb. It cannot see logging through a repo-local wrapper named otherwise, or in source it did not read — this is 'no logging found by this walk', not a verdict that nothing here logs. If it is right, production issues will be hard to diagnose.
P5 · DR & Backup · No DR/backup evidence · ×1
  • No DR/backup evidence — A persistence guard (data volume / purge-protection) was found, but no backup, geo-recovery or RTO/RPO controls were evidenced — a volume that survives a container recreate is not a tested restore from catastrophic loss.
R1 · Type Safety · Type Safety · ×1
  • Type Safety — 0 typed · 159 plain JS — the untyped files are CompositeUi/config/babelRelayPlugin.js, CompositeUi/config/env.js, CompositeUi/config/jest/babelTransform.js, CompositeUi/config/jest/cssTransform.js, CompositeUi/config/jest/fileTransform.js, CompositeUi/config/paths.js (+153 more).
R10 · Code Duplication · Wholesale file copy (69 identical lines × 2 files) · ×1
  • Wholesale file copy (69 identical lines × 2 files) CompositeUi/src/views/form/TaskEdit.js:11 — CompositeUi/src/views/form/TaskEdit.js:11 · CompositeUi/src/views/form/TaskNew.js:11 — these 2 files are line-for-line copies of one another — 69 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
R10 · Code Duplication · Duplicated block (36 lines × 2 locations) · ×1
  • Duplicated block (36 lines × 2 locations) CompositeUi/src/actions/CurrentOrganization.js:127 — CompositeUi/src/actions/CurrentOrganization.js:127 · CompositeUi/src/actions/CurrentOrganization.js:163 — 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.
R10 · Code Duplication · Duplicated block (35 lines × 2 locations) · ×1
  • Duplicated block (35 lines × 2 locations) CompositeUi/src/views/form/ProjectEdit.js:43 — CompositeUi/src/views/form/ProjectEdit.js:43 · CompositeUi/src/views/form/ProjectNew.js:37 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (31 lines × 2 locations) · ×1
  • Duplicated block (31 lines × 2 locations) CompositeUi/src/actions/CurrentOrganization.js:48 — CompositeUi/src/actions/CurrentOrganization.js:48 · CompositeUi/src/actions/CurrentOrganization.js:88 — 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.
R10 · Code Duplication · Duplicated block (30 lines × 2 locations) · ×1
  • Duplicated block (30 lines × 2 locations) CompositeUi/src/views/form/Login.js:28 — CompositeUi/src/views/form/Login.js:28 · CompositeUi/src/views/form/Register.js:34 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (30 lines × 3 locations) · ×1
  • Duplicated block (30 lines × 3 locations) CompositeUi/src/views/form/OrganizationNew.js:41 — CompositeUi/src/views/form/OrganizationNew.js:41 · CompositeUi/src/views/form/ProjectEdit.js:43 · CompositeUi/src/views/form/ProjectNew.js:37 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (29 lines × 2 locations) · ×1
  • Duplicated block (29 lines × 2 locations) CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:30 — CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:30 · CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:30 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (29 lines × 3 locations) · ×1
  • Duplicated block (29 lines × 3 locations) CompositeUi/src/views/form/ProfileEdit.js:79 — CompositeUi/src/views/form/ProfileEdit.js:79 · CompositeUi/src/views/form/ProjectEdit.js:51 · CompositeUi/src/views/form/ProjectNew.js:45 — the 3 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it. There is one copy in each of 3 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
R10 · Code Duplication · Duplicated block (28 lines × 2 locations) · ×1
  • Duplicated block (28 lines × 2 locations) CompositeUi/config/webpack.config.babel.dev.js:92 — CompositeUi/config/webpack.config.babel.dev.js:92 · CompositeUi/config/webpack.config.babel.prod.js:94 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (27 lines × 2 locations) · ×1
  • Duplicated block (27 lines × 2 locations) CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:25 — CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:25 · CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.js:25 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (24 lines × 2 locations) · ×1
  • Duplicated block (24 lines × 2 locations) CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:42 — CompositeUi/src/api/graphql/mutation/CreateTaskMutationRequest.js:42 · CompositeUi/src/api/graphql/mutation/EditTaskMutationRequest.js:42 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (22 lines × 2 locations) · ×1
  • Duplicated block (22 lines × 2 locations) CompositeUi/src/actions/CurrentProject.js:64 — CompositeUi/src/actions/CurrentProject.js:64 · CompositeUi/src/actions/CurrentProject.js:86 — 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.
R10 · Code Duplication · Duplicated block (20 lines × 2 locations) · ×1
  • Duplicated block (20 lines × 2 locations) CompositeUi/src/views/page/Register.js:22 — CompositeUi/src/views/page/Register.js:22 · CompositeUi/src/views/page/RequestResetPassword.js:22 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block (18 lines × 2 locations) · ×1
  • Duplicated block (18 lines × 2 locations) CompositeUi/src/views/page/project/Settings.js:22 — CompositeUi/src/views/page/project/Settings.js:22 · CompositeUi/src/views/page/task/Edit.js:28 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block (17 lines × 3 locations) · ×1
  • Duplicated block (17 lines × 3 locations) CompositeUi/src/actions/CurrentOrganization.js:184 — CompositeUi/src/actions/CurrentOrganization.js:184 · CompositeUi/src/actions/CurrentProject.js:231 · CompositeUi/src/actions/Organization.js:49 — the 3 copies are spread across 3 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (17 lines × 4 locations) · ×1
  • Duplicated block (17 lines × 4 locations) CompositeUi/src/views/page/Login.js:34 — CompositeUi/src/views/page/Login.js:34 · CompositeUi/src/views/page/Register.js:25 · CompositeUi/src/views/page/RequestResetPassword.js:25 · CompositeUi/src/views/page/ResetPassword.js:45 — the 4 copies are spread across 4 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block (14 lines × 2 locations) · ×1
  • Duplicated block (14 lines × 2 locations) CompositeUi/src/views/page/organization/New.js:18 — CompositeUi/src/views/page/organization/New.js:18 · CompositeUi/src/views/page/profile/Edit.js:19 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
R10 · Code Duplication · Duplicated block with local edits (13 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (13 matched lines × 2 locations) CompositeUi/src/views/component/UserCard.js:16 — CompositeUi/src/views/component/UserCard.js:16 · CompositeUi/src/views/component/UserThumbnail.js:15 — the two spans are one implementation copied and then locally edited — 70 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (13 lines × 2 locations) · ×1
  • Duplicated block (13 lines × 2 locations) CompositeUi/src/views/composition/AssignedTasksDashboardWidget.js:18 — CompositeUi/src/views/composition/AssignedTasksDashboardWidget.js:18 · CompositeUi/src/views/composition/LastUpdatedProjectsDashboardWidget.js:20 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication · Duplicated block with local edits (12 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (12 matched lines × 2 locations) CompositeUi/src/views/form/RequestResetPassword.js:20 — CompositeUi/src/views/form/RequestResetPassword.js:20 · CompositeUi/src/views/form/TaskEdit.js:25 — the two spans are one implementation copied and then locally edited — 62 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication · Duplicated block (11 lines × 2 locations) · ×1
  • Duplicated block (11 lines × 2 locations) CompositeUi/src/views/form/ProjectEdit.js:21 — CompositeUi/src/views/form/ProjectEdit.js:21 · CompositeUi/src/views/form/ProjectNew.js:21 — the 2 copies sit in sibling files in one directory, so check first whether one of them (or an existing module there) already owns this behaviour and the others should call it; otherwise extract it into one module in that directory and have each site call it.
R10 · Code Duplication · Duplicated block with local edits (11 matched lines × 2 locations) · ×1
  • Duplicated block with local edits (11 matched lines × 2 locations) CompositeUi/src/views/page/project/Root.js:18 — CompositeUi/src/views/page/project/Root.js:18 · CompositeUi/src/views/page/project/Root.js:32 — the two spans are one implementation copied and then locally edited — 64 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.
R10 · Code Duplication · Duplicated block (10 lines × 2 locations) · ×1
  • Duplicated block (10 lines × 2 locations) CompositeUi/src/api/graphql/GraphQl.js:17 — CompositeUi/src/api/graphql/GraphQl.js:17 · CompositeUi/src/api/rest/Rest.js:11 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R6 · Tooling · No typecheck script · ×1
  • No typecheck script — 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.
R7 · Dead Code · Dead file (~398 LoC) · ×1
  • Dead file (~398 LoC) REDACTED — no import path from any entry point (4 application, 6 tooling, 16 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
R7 · Dead Code · Dead file (~23 LoC) · ×1
  • Dead file (~23 LoC) CompositeUi/src/views/component/LogoHeader.js — no import path from any entry point (4 application, 6 tooling, 16 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
R7 · Dead Code · Dead file (~16 LoC) · ×1
  • Dead file (~16 LoC) CompositeUi/config/jest/babelTransform.js — no import path from any entry point (4 application, 6 tooling, 16 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
R7 · Dead Code · Dead file (~15 LoC) · ×1
  • Dead file (~15 LoC) CompositeUi/config/jest/fileTransform.js — no import path from any entry point (4 application, 6 tooling, 16 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
R7 · Dead Code · Dead file (~14 LoC) · ×1
  • Dead file (~14 LoC) CompositeUi/config/babelRelayPlugin.js — no import path from any entry point (4 application, 6 tooling, 16 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
R8 · Dependency Hygiene · Unused dependency 'connect-history-api-fallback' · ×1
  • Unused dependency 'connect-history-api-fallback' — Declared in CompositeUi/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'cross-spawn' · ×1
  • Unused dependency 'cross-spawn' — Declared in CompositeUi/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
R8 · Dependency Hygiene · Unused dependency 'detect-port' · ×1
  • Unused dependency 'detect-port' — Declared in CompositeUi/package.json but never imported anywhere in that package or its workspace members — no static import reaches it. Usually that is dead weight and attack surface, but two shapes are indistinguishable from source and are NOT dead: an optional or native peer that another dependency loads dynamically at runtime, and a package a build, docs or test step installs and invokes separately. Confirm which of the three this is before removing it.
X24 · Document value interpolated into markup unescaped · Untrusted text written into markup unescaped · ×1
  • Untrusted text written into markup unescaped REDACTED:19 — `children` is text this program did not author, and it is written into the text of an element through `dangerouslySetInnerHTML` with nothing encoding it for that place. Whoever controls the value controls the markup: it can close the element or attribute it sits in and open a script of its own. Encode it for HTML at this site, render it through the framework's escaping output, or sanitise it if it must stay markup.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×1
  • Swallowed exception (caught, then discarded) SharedKernel/src/Kreta/SharedKernel/Infrastructure/Messaging/AMQP/PhpAmqpLib/PhpAmqpLibAMQPConsumer.php:62 — `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Minor — 144 finding(s)
D12 · Dependency Hygiene · Deprecated · ×54
  • Deprecated: abab REDACTED:5 — abab 1.0.3 is resolved in REDACTED and is marked deprecated by its publisher: "Use your platform's native atob() and btoa() methods instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: acorn-dynamic-import REDACTED:20 — acorn-dynamic-import 2.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "This is probably built in to whatever tool you're using. If you still need it... idk". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: are-we-there-yet REDACTED:163 — are-we-there-yet 1.1.4 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: boom REDACTED:1139 — boom 2.10.1 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: browserslist REDACTED:1235 — browserslist 1.7.7 is resolved in REDACTED and is marked deprecated by its publisher: "Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: browserslist REDACTED:1242 — browserslist 2.3.1 is resolved in REDACTED and is marked deprecated by its publisher: "Browserslist 2 could fail on reading Browserslist >3.0 config used in other tools.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: buffer REDACTED:1269 — buffer 4.9.1 is resolved in REDACTED and is marked deprecated by its publisher: "This version of 'buffer' is out-of-date. You must update to v4.9.2 or newer". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: circular-json REDACTED:1434 — circular-json 0.3.3 is resolved in REDACTED and is marked deprecated by its publisher: "CircularJSON is in maintenance only, flatted is its successor.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: clone REDACTED:1500 — clone 1.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "XSS vulnerability fixed in v1.0.3". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: content-type-parser REDACTED:1642 — content-type-parser 1.0.1 is resolved in REDACTED and is marked deprecated by its publisher: "Use whatwg-mimetype instead". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: core-js REDACTED:1666 — core-js 1.2.7 is resolved in REDACTED and is marked deprecated by its publisher: "core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: core-js REDACTED:1670 — core-js 2.5.0 is resolved in REDACTED and is marked deprecated by its publisher: "core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: cryptiles REDACTED:1746 — cryptiles 2.0.5 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: deep-diff REDACTED:1914 — deep-diff 0.3.4 is resolved in REDACTED and is marked deprecated by its publisher: "Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: domelementtype REDACTED:2091 — domelementtype 1.3.0 is resolved in REDACTED and is marked deprecated by its publisher: "update to domelementtype@1.3.1". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: flatten REDACTED:2798 — flatten 1.0.2 is resolved in REDACTED and is marked deprecated by its publisher: "flatten is deprecated in favor of utility frameworks such as lodash.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: fsevents REDACTED:2872 — fsevents 1.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "Upgrade to fsevents v2 to mitigate potential security issues". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: fstream-ignore REDACTED:2879 — fstream-ignore 1.0.5 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: fstream REDACTED:2887 — fstream 1.0.11 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: gauge REDACTED:2912 — gauge 2.7.4 is resolved in REDACTED and is marked deprecated by its publisher: "This package is no longer supported.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: glob REDACTED:2966 — glob 7.1.2 is resolved in REDACTED and is marked deprecated by its publisher: "Old versions of glob are not supported, and contain widely publicized security vulnerabilities, which have been fixed in the current version. Please update. Support for old versions may be purchased (at exorbitant rates) by contacting i@izs.me". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: graphql REDACTED:3063 — graphql 0.9.1 is resolved in REDACTED and is marked deprecated by its publisher: "No longer supported; please update to a newer version. Details: https://github.com/graphql/graphql-js#version-support". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: har-validator REDACTED:3097 — har-validator 4.2.1 is resolved in REDACTED and is marked deprecated by its publisher: "this library is no longer supported". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: hawk REDACTED:3141 — hawk 3.1.3 is resolved in REDACTED and is marked deprecated by its publisher: "This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • Deprecated: hoek REDACTED:3181 — hoek 2.16.3 is resolved in REDACTED and is marked deprecated by its publisher: "This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).". This repository does not declare it — a direct dependency pulls it in, so the move is to upgrade or replace that dependency.
  • + 29 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×53
  • Orphaned file TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/CreateTaskHandler.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Symfony/Framework/AppKernel.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Domain/Model/Organization/Organization.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Domain/Model/Project/Task/Task.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/Task/TasksResolver.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/MemberResolver.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Application/Command/Organization/RemoveOrganizationMemberToOrganizationHandler.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Project/Task/DoctrineORMFilterableSpecification.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Project/Task/EditTaskMutation.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Symfony/HttpAction/EditProfileAction.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20161022171904.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Application/Command/Project/CreateProjectHandler.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectResolver.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/Framework/AppKernel.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file SharedKernel/src/Kreta/SharedKernel/Infrastructure/Persistence/InMemory/EventStore/InMemoryEventStore.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Application/Query/Project/FilterProjectsHandler.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file SharedKernel/src/Kreta/SharedKernel/Infrastructure/Persistence/Doctrine/DataFixtures/AbstractFixture.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file IdentityAccess/src/Kreta/IdentityAccess/Application/Command/EditProfileHandler.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Project/Task/CreateTaskMutation.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationResolver.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file Notifier/src/Kreta/Notifier/Infrastructure/Symfony/CliCommand/LoadFakeNotificationsCommand.php:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 28 more in this group — see findings.md.
D31 · IaC & Container Security · Low IaC · ×8
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D30 · Dependency Vulnerabilities · Low CVE · ×6
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D12 · Dependency Hygiene · Outdated (npm) · ×5
  • Outdated (npm): react CompositeUi/package.json:90 — react is pinned at 15.6.1; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react-dom CompositeUi/package.json:92 — react-dom is pinned at 15.6.1; registry.npmjs.org publishes 19.3.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react-redux CompositeUi/package.json:94 — react-redux is pinned at 5.0.6; registry.npmjs.org publishes 9.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react-relay CompositeUi/package.json:95 — react-relay is pinned at 0.9.3; registry.npmjs.org publishes 21.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react-router CompositeUi/package.json:96 — react-router is pinned at 2.8.1; registry.npmjs.org publishes 8.5.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
X10 · Duplicated predicate · Duplicated predicate · ×4
  • Duplicated predicate CompositeUi/src/views/form/Register.js:26 — `typeof values.password !== 'undefined' && values.password.length < 6` appears character-identically in 2 files — CompositeUi/src/views/form/Register.js, CompositeUi/src/views/form/ResetPassword.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Ui/Http/Symfony/public/app_dev.php:19 — `isset($_SERVER['HTTP_CLIENT_IP']) || isset($_SERVER['HTTP_X_FORWARDED_FOR']) || !(in_array(@$_SERVER['REMOTE_ADDR'], ['127.0.0.1', '::1', ge…` appears character-identically in 3 files — IdentityAccess/src/Kreta/IdentityAccess/Infrastructure/Ui/Http/Symfony/public/app_dev.php, Notifier/src/Kreta/Notifier/Infrastructure/Ui/Http/Symfony/public/app_dev.php, TaskManager/src/Kreta/TaskManager/Infrastructure/Ui/Http/Symfony/public/app_dev.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:100 — `isset($args['first']) && is_numeric($args['first'])` appears character-identically in 3 files — TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php, TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php, TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/Task/TasksResolver.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
  • Duplicated predicate TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:103 — `isset($args['last']) && is_numeric($args['last'])` appears character-identically in 3 files — TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php, TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php, TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/Task/TasksResolver.php. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D26 · Project Cohesion · Split CompositeUi · ×1
  • Split CompositeUi — A huge UI project whose namespaces are views/form/layout/composition/page and a graphql API split across two unrelated namespaces. Suggested: split CompositeUi/src/views into view-component, view-form, view-layout, view-composition, view-page
D30 · Dependency Vulnerabilities · Low vulnerability · ×1
  • REDACTED
D34 · Knowledge Freshness · Dormant codebase · ×1
  • Dormant codebase — 53 of 53 significant files have no living knowledge — the codebase as a whole is dormant, not 53 separate risks. Counted over 53 of the 361 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — 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.
M4 · Documentation accuracy · README/code drift · ×1
  • README/code drift README.md:26 — README advertises a microservices architecture, but the repo is a single project with no service manifests — searched for: `microservice`, `service-mesh`, `istio`. Each was matched case- and separator-insensitively against file and directory NAMES anywhere in the tree, and against the CONTENTS of manifest and configuration files (package.json and other *.json, *.csproj, *.props, *.sln/*.slnx, *.yml, *.toml, *.config, tool configs such as eslint.config.js, REDACTED); the README's own prose never counts, so a claim is never refuted by merely being made. Nothing outside that search was read — a footprint living only in a submodule, in a file type not listed here, or under a name none of those terms matches is not seen, and this row is then wrong.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add phpstan or psalm (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 9346 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.
P6 · Release Hygiene · Changelog looks stale/thin · ×1
  • Changelog looks stale/thin — The changelog this check read carries 1 versioned entry, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
S1 · Web-Security Posture · No security response headers detected · ×1
  • No security response headers detected REDACTED:9 — None of the 11 security response headers the OWASP Secure Headers Project recommends (Content-Security-Policy, Strict-Transport-Security, X-Content-Type-Options, X-Frame-Options, …) is configured — defense in depth, even when a reverse proxy could set them. This is reported because `REDACTED` builds the web-server image that serves this application, so the configuration that would carry these headers is in this repository and was read in full. (−2.0 on this card.)
X5 · Nullable reference types · PHP static analysis does not check null everywhere · ×1
  • PHP static analysis does not check null everywhere — This repository commits no PHPStan or Psalm configuration (`phpstan.neon[.dist]`, `phpstan.dist.neon`, `psalm.xml[.dist]`, or one a composer.json script names with `--configuration`), so nothing checks null: a `?Customer` reaches `->name()` silently and throws `Error: Call to a member function name() on null` the first time it is null. If the build passes a level on a command line instead, put it in a committed configuration — this check reads configuration, and configuration is all it can read.
Minor — 15 finding(s)
D12 · Dependency Hygiene · Outdated (npm) · ×15
  • Outdated (npm): classnames — classnames is pinned at 2.2.5; registry.npmjs.org publishes 2.5.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): draft-js — draft-js is pinned at 0.10.1; registry.npmjs.org publishes 0.11.7 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): draftjs-to-html — draftjs-to-html is pinned at 0.6.3; registry.npmjs.org publishes 0.9.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): history — history is pinned at 4.6.3; registry.npmjs.org publishes 5.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): lodash — lodash is pinned at 4.17.4; registry.npmjs.org publishes 4.18.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): mousetrap — mousetrap is pinned at 1.6.1; registry.npmjs.org publishes 1.6.5 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): promise — promise is pinned at 8.0.1; registry.npmjs.org publishes 8.3.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react-addons-test-utils — react-addons-test-utils is pinned at 15.6.0; registry.npmjs.org publishes 15.6.2 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react-draft-wysiwyg — react-draft-wysiwyg is pinned at 1.10.7; registry.npmjs.org publishes 1.15.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): react-router-redux — react-router-redux is pinned at 2.1.0; registry.npmjs.org publishes 4.0.8 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): redux — redux is pinned at 3.7.2; registry.npmjs.org publishes 5.0.1 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): redux-form — redux-form is pinned at 6.8.0; registry.npmjs.org publishes 8.3.10 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): redux-logger — redux-logger is pinned at 2.10.2; registry.npmjs.org publishes 3.0.6 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): redux-thunk — redux-thunk is pinned at 1.0.3; registry.npmjs.org publishes 3.1.0 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.
  • Outdated (npm): whatwg-fetch — whatwg-fetch is pinned at 2.0.3; registry.npmjs.org publishes 3.6.20 as the latest release. Upgrading is a judgement call — read that package's changelog for what changed between the two — but a direct production dependency several releases behind is where security and compatibility debt accumulates silently.

Appendix B — Reproduction & audit trail

Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-06c687282f9844009ee1fca08c94829c/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/watchdog-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-06c687282f9844009ee1fca08c94829c/tree.json --exit-code 0 --source .0artifacts/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/watchdog-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off .17artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update137artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .24artifacts/raw/trivy-config.json
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 Policydisclosure—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 Confinementruntime-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 Confinementruntime-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 Enforcementruntime-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 Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** . --skip-db-update1artifacts/raw/trivy-fs.json

Run 01a16580-3656-7081-805a-6dbed1978c67 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Issues: 120 · Warnings: 210 · Recommendations: 144 · Info: 15 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 22-10-2026 @ 21:24 UTC.

Downloadable artifacts

Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md