Public report — Kreta, published 4 Aug 2026.
Concrete security findings (CVE IDs, secret matches, dependency versions) are hidden in this version;
ask the repo owner for the full report.
99findings with an exact file:lineof 106 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
34/108dimensions across the health lenses15075 LoC — wide & deep
Executive summary
Read through the Preview lens: this repo is pre-1.0 / in development, so the colour bands are relaxed to what a preview needs — *green* means good enough for a preview, not yet production-stable. Code correctness and security stay near-strict even here; the score itself is absolute and comparable across repos.
kreta/Kreta is sound in substance but carries real gaps (46%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Event Sourcing (100%) — its event log is trustworthy to replay. Architecture (77%) is solid too.
Most urgent: a critical security exposure was detected (see the Security & Compliance lens). Treat it as a priority regardless of the overall grade.
The area that most needs attention is Readiness (29%) — releases are harder to depend on — versioning, release notes and dependency hygiene are thin, so consumers can't easily tell what changed or trust an upgrade. Maturity (51%) is the next concern — onboarding is slow — key decisions and the architecture aren't written down, so contributors have to reverse-engineer the intent.
Leadership focus, highest impact first: SAST step to CI running what this repository's stack ships (Security & performance tooling); Codify backups + geo-recovery in IaC and document RTO/RPO… (DR & Backup); Keep the changelog current (Release Hygiene).
For scale: Small (~15,075 production lines); rebuilding it from scratch would take roughly ~0.2 person-years (~1 engineer). Approximate, ±~30%.
It builds on a genuinely strong Event Sourcing foundation (100%); the priorities above are the highest-leverage way to bring the rest up to that level.
How the score is built — each lens's share of the headlineWidth is the lens's weight in the worst-heaviest fold (the weakest area pulls hardest); colour is that lens's own band. A lens fixes the score in proportion to its width.
A full-fidelity diff against the previous run's complete recorded findings — line-move tolerant: a finding that only shifted line counts as unchanged, only genuinely new titles/files surface here.
0.7× (at 46% quality) — the last 20% of quality is most of the work
Size & shape
Small · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
Dead frontend code
~532 LoC unreachable (8 file(s)) — that slice of this estimate buys code with zero runtime value; deleting it is the cheapest win in this report (the R7 card lists every file)
This codebase represents roughly ~0.2 person-years of build effort (about ~€35,000 to rebuild). Its weakest lens is Readiness at 29% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain High (×1.5) — DDD/clean architecture, event sourcing × a 0.7× quality factor, at €60–95/h; indicative, ±~30% · size measured directly from source · effort from total production LoC as straight-line logic (the tier split is a C#-only syntax walk), a conservative lower bound. Indicative only — most sensitive to the hourly rate and the domain tier (both tunable in config).
Top priorities
The highest-leverage moves; the full ranked list is in the Roadmap below.
1
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.
Value concentrated against a weak lens · High · Value at risk
This is a Small asset (~0.2 person-years to rebuild), and its weakest lens is Readiness at 29%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Readiness first — highest risk-reduction per euro on an asset this size.
Highest-leverage move · Medium · Leverage
Of everything flagged, the best return on effort is: 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. The rest can wait behind it.
Evidence: priority ranking: top of 5 ranked by impact/effort
→ 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.
Architecture — module dependency matrix
100 modules, 153 dependencies — 1 dependency cycle, shown as the red cell(s) above the diagonal. Rows and columns are the same modules, ordered so that a module only depends on ones above it. A cell means the row depends on the column, and its number is how many type pairs create that dependency. Read one thing: is anything above the diagonal? A mark there is a dependency cycle. (A cycle is all this shows — an unusual but cycle-free dependency sits below the diagonal like any other.)
At a glance — Code Health · 63% · Adequate · gated by R1
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 category
Findings
Severity
A06:2021 — Vulnerable & Outdated Components
50
High / Critical
A05:2021 — Security Misconfiguration
21
High / Critical
A03:2021 — Injection
1
Medium
Roadmap
First, integrate a static analysis tool like SAST into the CI pipeline to automatically fail the build on security regressions. Next, codify disaster recovery and backup procedures in infrastructure-as-code, explicitly documenting recovery time and data loss objectives. Then, maintain a current changelog for every release to preserve release history. After that, clean up the dependency tree by removing unused packages and explicitly declaring all imports. Finally, add type checking to the build scripts and run it in CI to ensure code quality.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
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.
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. 33 of 34 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 1 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.5 — 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 — 34 dimensions across the health lenses
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
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, 99 of 106 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.)
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.
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.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
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.
D19 Documentation Quality — LLM provider failed — The model provider returned an unusable result, so this LLM-assisted dimension fell back to a measurement gap (confidence 0) rather than a penalty. Re-run with a reachable provider to score it.
D30 Dependency Vulnerabilities — scanner not present in this environment — The backing tool was not installed where this scan ran, so this dimension was not scored. Install the tool (or run in the hosted environment, where it is always present) for a graded result.
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 (jscpd) — 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.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
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").
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.
D33 JS/npm Dependency Vulnerabilities: JS/npm CVE matching reads package manifests and lockfiles — risk from how a dependency is used, and advisories not yet published, fall outside this scan.
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.
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 (2): D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score (documentation, ADR quality, naming, comment value, onboarding) — D25 sets the ADR-conformance fraction over sampled code, D22 judges API accuracy over a sample. These 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.
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.
0 method(s) exceeded the cyclomatic complexity threshold of 15. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being reducer at 16 — they are counted neither in the figure above nor in this dimension's score.
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.
0 method(s) exceeded the cognitive complexity threshold of 15.
✓ On the Gold path — maintain.
Detailed fixes: d2_recommendation.md.
Do you agree with this assessment?
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.
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.
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.
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.
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.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Git-history secret scan via gitleaks detect over full history in an isolated checkout; each match flagged High. Exhaustive; degrades cleanly when tool absent.
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).
High IaC: DS-0002 · ×7etc/docker/nginx/Dockerfiledetected by trivy finding
Medium IaC: CKV_DOCKER_6 · ×11etc/docker/nginx/Dockerfile:11detected by trivy finding
Low IaC: DS-0005 · ×3etc/docker/nginx/Dockerfiledetected by trivy finding
What to do
Resolve the 7 High IaC finding(s) in IaC & Container Security — start with Dockerfile (7). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 11 Medium IaC finding(s) in IaC & Container Security — start with Dockerfile (11). — One of this dimension's main actionable groups (11 warning-level).
Resolve the 3 Low IaC finding(s) in IaC & Container Security — start with Dockerfile (3). — One of this dimension's main actionable groups (3 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
Dormant codebase
What to do
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.
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; coupling through a build step, config, or non-source file isn't seen.
What it measures: Whether dependencies have known published vulnerabilities (CVEs) per the OSV database — read natively from whatever lockfile the repository ships (Cargo, npm, Go, Python, Maven, RubyGems, …). D33 and D30 add ecosystem-specific scanners on top for npm and .NET.
Method: Multi-ecosystem dependency-CVE scan via osv-scanner --recursive (queries the osv.dev database + parses lockfiles natively across ecosystems: npm package-lock/yarn/pnpm/bun, Go go.mod, Rust Cargo.lock, Maven/Gradle pom.xml/gradle.lockfile, PyPI requirements.txt/poetry.lock/Pipfile.lock, Composer composer.lock, RubyGems Gemfile.lock, Hex mix.lock, pub pubspec.lock, Swift Package.resolved); severity tally (Critical/High/Medium/Low) to 0-10 tight normalizer (8.0). NotApplicable only when the repo declares no supported non-.NET dependency lockfile (a NuGet-only repo stays NotApplicable — .NET CVEs are D30's domain); coverage needs a resolved lockfile. Additive to D33 (trivy fs); exhaustive + deterministic, DB kept fresh.
Critical CVE: [GHSA redacted] · ×29CompositeUi/yarn.lockdetected by osv-scanner finding
High CVE: [GHSA redacted] · ×19CompositeUi/yarn.lockdetected by osv-scanner finding
Critical vulnerability: [GHSA redacted]CompositeUi/yarn.lockdetected by osv-scanner finding
High vulnerability: [GHSA redacted]CompositeUi/yarn.lockdetected by osv-scanner finding
What to do
Resolve the 29 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (25), composer.lock (4). — One of this dimension's main actionable groups (29 issue-level).
Resolve the 19 High CVE finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock (18), composer.lock. — One of this dimension's main actionable groups (19 issue-level).
Resolve the 1 Critical vulnerability finding(s) in OSV Dependency Vulnerabilities — start with yarn.lock. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d38_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
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.
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.
Add a 'Testing' section to the root README — 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.
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 `NNNN-title.md` documents 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 significant decisions one document per decision — dated, stating the context, the decision and its consequences — and keep them together wherever your design docs already live (a conventional `docs/adr/` tree with `NNNN-title.md` names is the most discoverable form).
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
What to do
Reconcile the README with reality: README advertises a microservices architecture, but the repo is a single project with no service manifests.
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 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.
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.
Do you agree with this assessment?
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.
Do you agree with this assessment?
P6 · Release Hygiene3.0 / 10Weak✓ 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.
A changelog exists but has few versioned entries — keep it current with each 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.
Stamp a version in your build/package manifest (e.g. csproj <Version>, package.json, pyproject.toml, Cargo.toml, or a VERSION file) or tag releases with semver so builds and releases are traceable.
Do you agree with this assessment?
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.
React / JS · Code Health — Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm over JS/TS tokens, D-386).
Method: Copy-pasted token-identical blocks across the frontend (the D4 clone algorithm run over JS/TS tokens). Deterministic.
CompositeUi/src/views/form/OrganizationNew.js:51 · CompositeUi/src/views/form/ProfileEdit.js:87 · CompositeUi/src/views/form/ProjectEdit.js:59 · CompositeUi/src/views/form/ProjectNew.js:53 — the 4 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. — OrganizationNew.js:51
CompositeUi/src/views/form/TaskEdit.js:113 · CompositeUi/src/views/form/TaskNew.js:115 — 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. — TaskEdit.js:113
CompositeUi/src/api/graphql/mutation/AddMemberToOrganizationMutationRequest.js:34 · CompositeUi/src/api/graphql/mutation/RemoveMemberToOrganizationMutationRequest.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. — AddMemberToOrganizationMutationRequest.js:34
CompositeUi/src/api/graphql/mutation/CreateProjectMutationRequest.js:41 · CompositeUi/src/api/graphql/mutation/EditProjectMutationRequest.js:41 — 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. — CreateProjectMutationRequest.js:41
CompositeUi/config/webpack.config.babel.dev.js:95 · CompositeUi/config/webpack.config.babel.prod.js:97 — 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. — webpack.config.babel.dev.js:95
CompositeUi/src/actions/User.js:77 · CompositeUi/src/actions/User.js:135 — 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. — User.js:77
CompositeUi/src/api/graphql/query/ProjectsQueryRequest.js:44 · CompositeUi/src/api/graphql/query/TasksQueryRequest.js:74 — 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. — ProjectsQueryRequest.js:44
CompositeUi/src/views/form/ProfileEdit.js:83 · CompositeUi/src/views/form/ProjectEdit.js:55 · CompositeUi/src/views/form/ProjectNew.js:49 — 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. — ProfileEdit.js:83
What to do
Extract the duplicated blocks into shared functions/components.
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.
Branch-heavy code is where defects cluster — extract decisions into smaller functions. — CurrentProject.js:102
Do you agree with this assessment?
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.
Do you agree with this assessment?
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. (×8) — Task.js, CurrentProject.js, build.js, …
What to do
Add tests that import the unreached modules (directly or through their public entry).
Do you agree with this assessment?
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 ✗
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.
Do you agree with this assessment?
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 your build/type-check — an undetected custom entry would make these reachable.
no import path from any entry point (4 application, 6 tooling, 16 test roots considered) (×7) — Task.js, LogoHeader.js, 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.
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. — Root.js:14
Declared in CompositeUi/package.json but never imported anywhere in that package or its workspace members — dead weight and attack surface. Verify against build tooling before removing. (×3)
What to do
Remove unused dependencies, declare unlisted imports explicitly, and demote type-/test-only packages to devDependencies.
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) — Routes.js
What to do
Break each cycle by extracting the shared piece into a module both sides can import.
Do you agree with this assessment?
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.
Not included — 74 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 — no DI registrations detected
AX10 Code composition — not assessed — code composition is computed by ROLE over a document set 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 — no singleton implementations detected
AX3 Project dependency cycles — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
AX4 Dependency direction — not assessed — project cycles and dependency direction are computed over a project-reference graph 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
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 — not assessed — test isolation is computed from a project graph (which projects are test projects, and what they reference) 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
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.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D10 Test Quality — ~12172 lines of test source are present (.php, .js) but the test-quality collector reads C# only, so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included
D12 Dependency Hygiene — Dependency hygiene not measured — dependency manifest found but not parsed for hygiene
D14 License Compliance — Not scored — this repository's package manifest is not parsed for licence data yet. A gap in the analyzer's language coverage, NOT a finding that the repository's licenses are compliant (composer.json and package.json), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D17 Explicit Debt — explicit-debt markers are read through a C# workspace today, so they were not read for this repository's language — this asserts nothing about how many markers the code carries. Not scored — this is a gap in the analyzer, not a finding about this repository
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.
D19 Documentation Quality — LLM evaluation failed
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — No exposed public API
D23 Boundary Type-Coupling — Production source is present (.php) but bounded contexts are resolved over the C#/VB project set, which exposed none, so context scope could not be assessed. Not scored — this is a gap in the analyzer, not a verdict about this repository. Declaring the codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed — see the recommendation on this dimension for where. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — Project cohesion is assessed over the .NET project set; this target exposed no projects, so project size and spread could not be assessed. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D27 Navigability — No calls could be sampled, so navigability was not assessed — tracing effort is measured over resolved call sites and this target exposed none. Not scored — this is a gap in the analyzer's reach, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (composer.json and package.json — not scanned yet) — where an OSV-supported manifest exists, dependency vulnerabilities for this repository are reported under D38 instead.
D32 Data Compliance (PII/GDPR) — No PII/GDPR-handling patterns detected (p/gdpr ruleset) — no data-compliance surface to assess.
D36 Supply-chain Provenance & Signing — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
D5 Coupling — Inter-project coupling could not be assessed — no analyzable project graph was found for this repository. Not scored: a gap in the analyzer's reach, not a verdict about this repository. (Coupling here is Martin afferent/efferent/instability plus reference cycles across a project-reference graph, read today from .NET project files; other ecosystems' module graphs are not read yet.)
D6 Cohesion (LCOM4) — Cohesion (LCOM4) is measured over a C#/VB class graph, and this repository's production source is .php, which this pass does not read — so no class could be assessed. Not scored — this is a gap in the analyzer, not a finding about this repository.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.php, .js) but the test-pyramid classifier reads C# only, so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Domain Modelling — applicable but not scored (2 of 3 signals for this style — below the bar we score at): 11 aggregate root(s) (AggregateRoot/IAggregateRoot); a Domain/Aggregates/ValueObjects layer
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this check 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
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, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P2 Observability — Observability was not assessed: this check reads a source model that does not carry this repository's product — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of a logging idiom this check recognises is NOT evidence that this repo lacks structured logging (it may log through its own ecosystem's logger). This is a gap in the analyzer, not a finding about this repository.
P7 Outbound HTTP resilience — not measured — the application kind could not be determined for this repo
P8 Schema migrations — not assessed — schema-migration practice is read from 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
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (Clover XML — `vendor/bin/phpunit --coverage-clover coverage.xml`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF2 Allocation hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
PF3 Async & latency hygiene — Performance was not assessed: this lens reads a source model that was not loaded for this repository, because the repository is written in a language this lens does not yet model or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository — in particular it is NOT a statement that this repo is unpackaged or performance-careless.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R5 Dependency Freshness — uses a yarn lockfile — dependency freshness not measured here; JS/npm CVEs are scored in D33 (JS/npm Dependency Vulnerabilities)
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — 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
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X3 Exception handling — 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
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
X5 Nullable reference types — 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
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 CVE: [GHSA redacted] CompositeUi/yarn.lock— atob 1.1.3: [GHSA redacted] — atob is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 2.1.0 is a MAJOR ahead of the resolved 1.1.3, so an `overrides` pin would force a breaking version under a dependent written against 1.1.3; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— babel-traverse 6.25.0: [GHSA redacted] — no fixed version has been published yet. Track the advisory; babel-traverse is not declared in this repo's manifests: it is pulled in transitively, so the action is on the dependency that requires it — upgrade or replace that dependent.
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— cipher-base 1.0.4: [GHSA redacted] — cipher-base is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin cipher-base to 1.0.5 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— deep-extend 0.4.2: [GHSA redacted] — deep-extend is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin deep-extend to 0.5.1 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— eventsource 0.1.6: [GHSA redacted] — eventsource is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 1.1.1 is a MAJOR ahead of the resolved 0.1.6, so an `overrides` pin would force a breaking version under a dependent written against 0.1.6; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— form-data 2.1.4: [GHSA redacted] — form-data is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin form-data to 2.5.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against form-data 2.1.4, and their fixed versions do not agree — anything below 2.5.6 still leaves at least one of them open. Take this package to 2.5.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against form-data 2.1.4: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— fsevents 1.1.2: [GHSA redacted] — fsevents is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin fsevents to 1.2.11 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against fsevents 1.1.2: [GHSA redacted], MAL-2023-462.
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— handlebars 4.0.10: [GHSA redacted] — handlebars is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin handlebars to 4.7.9 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 17 advisories with a published fix this scan raises against handlebars 4.0.10, and their fixed versions do not agree — anything below 4.7.9 still leaves at least one of them open. Take this package to 4.7.9 or later: that is the floor for the package, not this row's target alone. This one row stands for the 17 advisories this scan raises against handlebars 4.0.10: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— json-schema 0.2.3: [GHSA redacted] — json-schema is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin json-schema to 0.4.0 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— loader-utils 0.2.17: [GHSA redacted] — loader-utils is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 1.4.1 is a MAJOR ahead of the resolved 0.2.17, so an `overrides` pin would force a breaking version under a dependent written against 0.2.17; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— loader-utils 1.1.0: [GHSA redacted] — loader-utils is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin loader-utils to 1.4.1 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 3 advisories with a published fix this scan raises against loader-utils 1.1.0, and their fixed versions do not agree — anything below 1.4.2 still leaves at least one of them open. Take this package to 1.4.2 or later: that is the floor for the package, not this row's target alone. This one row stands for the 3 advisories this scan raises against loader-utils 1.1.0: [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— lodash 4.17.4: [GHSA redacted] — this repo declares lodash ^4.17, a range that ALREADY admits the fixed 4.17.12, so there is no manifest edit to make here. Re-resolve the lock so lodash moves onto 4.17.12 or later; if the flagged 4.17.4 comes back, a dependency is pinning it — upgrade that dependent, or pin lodash with an `overrides` entry (`resolutions` if you use Yarn) so only one copy resolves. This is 1 of 8 advisories with a published fix this scan raises against lodash 4.17.4, and their fixed versions do not agree — anything below 4.18.0 still leaves at least one of them open. Take this package to 4.18.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 8 advisories this scan raises against lodash 4.17.4: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— lodash-es 4.17.4: [GHSA redacted] — lodash-es is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin lodash-es to 4.17.14 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 6 advisories with a published fix this scan raises against lodash-es 4.17.4, and their fixed versions do not agree — anything below 4.18.0 still leaves at least one of them open. Take this package to 4.18.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 6 advisories this scan raises against lodash-es 4.17.4: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— macaddress 0.2.8: [GHSA redacted] — macaddress is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin macaddress to 0.2.9 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— merge-options 0.0.64: [GHSA redacted] — merge-options is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 1.0.1 is a MAJOR ahead of the resolved 0.0.64, so an `overrides` pin would force a breaking version under a dependent written against 0.0.64; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— minimist 0.0.10: [GHSA redacted] — minimist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimist to 0.2.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against minimist 0.0.10, and their fixed versions do not agree — anything below 0.2.4 still leaves at least one of them open. Take this package to 0.2.4 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against minimist 0.0.10: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— minimist 0.0.8: [GHSA redacted] — minimist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimist to 0.2.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against minimist 0.0.8, and their fixed versions do not agree — anything below 0.2.4 still leaves at least one of them open. Take this package to 0.2.4 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against minimist 0.0.8: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— minimist 1.2.0: [GHSA redacted] — minimist is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin minimist to 1.2.6 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against minimist 1.2.0, and their fixed versions do not agree — anything below 1.2.6 still leaves at least one of them open. Take this package to 1.2.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against minimist 1.2.0: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— pbkdf2 3.0.13: [GHSA redacted] — pbkdf2 is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin pbkdf2 to 3.1.3 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against pbkdf2 3.0.13: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— sha.js 2.4.8: [GHSA redacted] — sha.js is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin sha.js to 2.4.12 with an `overrides` entry (`resolutions` if you use Yarn)).
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— shell-quote 1.6.1: [GHSA redacted] — shell-quote is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin shell-quote to 1.8.4 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against shell-quote 1.6.1, and their fixed versions do not agree — anything below 1.9.0 still leaves at least one of them open. Take this package to 1.9.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against shell-quote 1.6.1: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] IdentityAccess/composer.lock— symfony/symfony v3.2.11: [GHSA redacted] — upgrade to 2.8.37. This is 1 of 40 advisories with a published fix this scan raises against symfony/symfony v3.2.11, and their fixed versions do not agree — anything below 3.4.49 still leaves at least one of them open. Take this package to 3.4.49 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: IdentityAccess/composer.lock, TaskManager/composer.lock) This one row stands for the 40 advisories this scan raises against symfony/symfony v3.2.11: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] Notifier/composer.lock— symfony/symfony v3.3.4: [GHSA redacted] — upgrade to 2.8.37. This is 1 of 43 advisories with a published fix this scan raises against symfony/symfony v3.3.4, and their fixed versions do not agree — anything below 3.4.49 still leaves at least one of them open. Take this package to 3.4.49 or later: that is the floor for the package, not this row's target alone. This one row stands for the 43 advisories this scan raises against symfony/symfony v3.3.4: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] CompositeUi/yarn.lock— tar 2.2.1: [GHSA redacted] — tar is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 7.5.19 is a MAJOR ahead of the resolved 2.2.1, so an `overrides` pin would force a breaking version under a dependent written against 2.2.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This one row stands for the 16 advisories this scan raises against tar 2.2.1: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] IdentityAccess/composer.lock— twig/twig v1.34.4: [GHSA redacted] — upgrade to 3.26.0. This is 1 of 15 advisories with a published fix this scan raises against twig/twig v1.34.4, and their fixed versions do not agree — anything below 1.44.8 still leaves at least one of them open. Take this package to 1.44.8 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: IdentityAccess/composer.lock, TaskManager/composer.lock) This one row stands for the 15 advisories this scan raises against twig/twig v1.34.4: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
+ 4 more in this group — see findings.md.
D38 · OSV Dependency Vulnerabilities· High CVE · ×19
High CVE: [GHSA redacted] CompositeUi/yarn.lock— ansi-html 0.0.7: [GHSA redacted] — ansi-html is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ansi-html to 0.0.8 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— ansi-regex 3.0.0: [GHSA redacted] — ansi-regex is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ansi-regex to 3.0.1 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— async 2.5.0: [GHSA redacted] — async is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin async to 2.6.4 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— brace-expansion 1.1.8: [GHSA redacted] — brace-expansion is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin brace-expansion to 1.1.16 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 5 advisories with a published fix this scan raises against brace-expansion 1.1.8, and their fixed versions do not agree — anything below 1.1.18 still leaves at least one of them open. Take this package to 1.1.18 or later: that is the floor for the package, not this row's target alone. This one row stands for the 5 advisories this scan raises against brace-expansion 1.1.8: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] CompositeUi/yarn.lock— braces 1.8.5: [GHSA redacted] — braces is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 3.0.3 is a MAJOR ahead of the resolved 1.8.5, so an `overrides` pin would force a breaking version under a dependent written against 1.8.5; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— browserify-sign 4.0.4: [GHSA redacted] — browserify-sign is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin browserify-sign to 4.2.2 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— cross-spawn 3.0.1: [GHSA redacted] — this repo declares cross-spawn ^5.1.0, but the vulnerable 3.0.1 is a SEPARATE copy on another release line, so editing your own cross-spawn entry cannot move it: upgrade the dependency that pulls it in (— 6.0.6 is a MAJOR ahead of the resolved 3.0.1, so an `overrides` pin would force a breaking version under a dependent written against 3.0.1; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— cross-spawn 5.1.0: [GHSA redacted] — upgrade to 6.0.6
High CVE: [GHSA redacted] CompositeUi/yarn.lock— css-what 2.1.0: [GHSA redacted] — css-what is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin css-what to 2.1.3 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— debug 2.6.8: [GHSA redacted] — debug is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin debug to 2.6.9 with an `overrides` entry (`resolutions` if you use Yarn)). This one row stands for the 2 advisories this scan raises against debug 2.6.8: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] CompositeUi/yarn.lock— dns-packet 1.1.1: [GHSA redacted] — dns-packet is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin dns-packet to 1.3.2 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— dot-prop 3.0.0: [GHSA redacted] — dot-prop is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 4.2.1 is a MAJOR ahead of the resolved 3.0.0, so an `overrides` pin would force a breaking version under a dependent written against 3.0.0; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— forwarded 0.1.0: [GHSA redacted] — forwarded is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin forwarded to 0.1.2 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— fresh 0.5.0: [GHSA redacted] — fresh is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin fresh to 0.5.2 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— fstream 1.0.11: [GHSA redacted] — fstream is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin fstream to 1.0.12 with an `overrides` entry (`resolutions` if you use Yarn)).
High CVE: [GHSA redacted] Notifier/composer.lock— guzzlehttp/guzzle 6.3.0: [GHSA redacted] — guzzlehttp/guzzle is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or require guzzlehttp/guzzle:^6.5.8 explicitly so composer resolves the patched copy). This is 1 of 13 advisories with a published fix this scan raises against guzzlehttp/guzzle 6.3.0, and their fixed versions do not agree — anything below 6.5.8 still leaves at least one of them open. Take this package to 6.5.8 or later: that is the floor for the package, not this row's target alone. (in 2 dependency files: Notifier/composer.lock, TaskManager/composer.lock) This one row stands for the 13 advisories this scan raises against guzzlehttp/guzzle 6.3.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] CompositeUi/yarn.lock— hawk 3.1.3: [GHSA redacted] — hawk is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 9.0.1 is a MAJOR ahead of the resolved 3.1.3, so an `overrides` pin would force a breaking version under a dependent written against 3.1.3; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
High CVE: [GHSA redacted] CompositeUi/yarn.lock— hoek 2.16.3: [GHSA redacted] — no fixed version has been published yet. Track the advisory; hoek is not declared in this repo's manifests: it is pulled in transitively, so the action is on the dependency that requires it — upgrade or replace that dependent. This one row stands for the 2 advisories this scan raises against hoek 2.16.3: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] CompositeUi/yarn.lock— html-minifier 3.5.3: [GHSA redacted] — no fixed version has been published yet. Track the advisory; html-minifier is not declared in this repo's manifests: it is pulled in transitively, so the action is on the dependency that requires it — upgrade or replace that dependent.
High IaC: DS-0002 etc/docker/nginx/Dockerfile— Image user should not be 'root' A container that starts as root runs your process with root's capabilities inside the namespace, so a compromise of the process starts from there. The step: create an unprivileged account in the image (`RUN useradd -r -M app` — or whatever this base image's account tooling is, `adduser` and `useradd` are not both present everywhere`), give it ownership of the paths the process writes at runtime (`COPY --chown=` on those layers, or a `RUN chown -R`), and end the final stage with `USER app` so it is the default at start. Build stages that only compile can stay root; it is the stage that RUNS that needs the account. If the process genuinely requires root — it manages the container runtime, ptraces another process or opens raw devices — say so here rather than making a change that breaks it.
High IaC: DS-0022 etc/docker/nginx/Dockerfile— Deprecated MAINTAINER used
High IaC: DS-0002 etc/docker/node/Dockerfile— Image user should not be 'root' A container that starts as root runs your process with root's capabilities inside the namespace, so a compromise of the process starts from there. The step: create an unprivileged account in the image (`RUN useradd -r -M app` — or whatever this base image's account tooling is, `adduser` and `useradd` are not both present everywhere`), give it ownership of the paths the process writes at runtime (`COPY --chown=` on those layers, or a `RUN chown -R`), and end the final stage with `USER app` so it is the default at start. Build stages that only compile can stay root; it is the stage that RUNS that needs the account. If the process genuinely requires root — it manages the container runtime, ptraces another process or opens raw devices — say so here rather than making a change that breaks it.
High IaC: DS-0022 etc/docker/node/Dockerfile— Deprecated MAINTAINER used
High IaC: DS-0002 etc/docker/php7-fpm/Dockerfile— Image user should not be 'root' A container that starts as root runs your process with root's capabilities inside the namespace, so a compromise of the process starts from there. The step: create an unprivileged account in the image (`RUN adduser --system --no-create-home app`), give it ownership of the paths the process writes at runtime (`COPY --chown=` on those layers, or a `RUN chown -R`), and end the final stage with `USER app` so it is the default at start. Build stages that only compile can stay root; it is the stage that RUNS that needs the account. If the process genuinely requires root — it manages the container runtime, ptraces another process or opens raw devices — say so here rather than making a change that breaks it.
High IaC: DS-0022 etc/docker/php7-fpm/Dockerfile— Deprecated MAINTAINER used
High IaC: DS-0029 etc/docker/php7-fpm/Dockerfile— 'apt-get' missing '--no-install-recommends'
Critical vulnerability: [GHSA redacted] CompositeUi/yarn.lock— elliptic 6.4.0: [GHSA redacted] — elliptic is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin elliptic to 6.6.1 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 8 advisories with a published fix this scan raises against elliptic 6.4.0, and their fixed versions do not agree — anything below 6.6.1 still leaves at least one of them open. Take this package to 6.6.1 or later: that is the floor for the package, not this row's target alone. This one row stands for the 9 advisories this scan raises against elliptic 6.4.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×1
High vulnerability: [GHSA redacted] CompositeUi/yarn.lock— diff 3.3.0: [GHSA redacted] — diff is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin diff to 3.5.0 with an `overrides` entry (`resolutions` if you use Yarn)). This is 1 of 2 advisories with a published fix this scan raises against diff 3.3.0, and their fixed versions do not agree — anything below 3.5.1 still leaves at least one of them open. Take this package to 3.5.1 or later: that is the floor for the package, not this row's target alone. This one row stands for the 2 advisories this scan raises against diff 3.3.0: [GHSA redacted], [GHSA redacted].
Change coupling: AddMember.js ↔ Show.js CompositeUi/src/views/page/organization/AddMember.js— `CompositeUi/src/views/page/organization/AddMember.js` and `CompositeUi/src/views/page/organization/Show.js` change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) 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.
Change coupling: TasksQueryRequest.js ↔ TaskList.js CompositeUi/src/api/graphql/query/TasksQueryRequest.js— `CompositeUi/src/api/graphql/query/TasksQueryRequest.js` and `CompositeUi/src/views/page/project/TaskList.js` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking.
Change coupling: MemberTypeResolver.php ↔ OrganizationResolver.php TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/MemberTypeResolver.php— `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/MemberTypeResolver.php` and `TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationResolver.php` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking.
Duplicated block (12 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46— TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46-57 | TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/EditTaskHandler.php:46-61 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Application/Command/Project/Task/ChangeTaskPriorityHandler.php:46` 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.
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 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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/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 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 (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: extract the block into a single shared function in that directory and call it from each site, 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 (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: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 (8 lines × 2) SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:71— SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:71-78 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/EventListener/AuthenticationListener.php:71-78 — 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 `SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:71` 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 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 (8 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20161022171904.php:24— TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20161022171904.php:24-31 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/Migrations/Version20161022171904.php:38-45 — 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 (12 lines × 3) TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationMemberOfIdHandler.php:40— TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationMemberOfIdHandler.php:40-51 | TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OrganizationOfIdHandler.php:39-50 | TaskManager/src/Kreta/TaskManager/Application/Query/Organization/OwnerOfIdHandler.php:40-51 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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/Organization/OrganizationMemberOfIdHandler.php:40` 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. 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 (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. 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 (11 lines × 2) SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:47— SharedKernel/src/Kreta/SharedKernel/Infrastructure/Symfony/EventListener/AuthenticationListener.php:47-57 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/EventListener/AuthenticationListener.php:47-57 — 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 (11 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:42— TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:42-52 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Project/DoctrineORMFilterableSpecification.php:41-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. Read the line range as the matched WINDOW rather than a finished unit: at `TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Organization/DoctrineORMFilterableSpecification.php:42` 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 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 (10 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:62-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 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 (10 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:43— TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationsResolver.php:43-52 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php:57-66 — 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:43` 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 (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.
Duplicated block (6 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:104— TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:104-109 | TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php:110-115 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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/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.
dormant codebase — no living knowledge left to concentrate — 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).
LLM evaluation failed — JSON parse error: Expected end of string, but instead reached end of data. Path: $.findings[0].suggestion | LineNumber: 0 | BytePositionInLine: 1216.
Medium: react-dangerouslysetinnerhtml CompositeUi/src/views/component/HtmlArea.js:19— Detection of dangerouslySetInnerHTML from non-constant definition. This can inadvertently expose users to cross-site scripting (XSS) attacks if this comes from user-provided input. If you have to use dangerouslySetInnerHTML, consider using a sanitization library such as DOMPurify to sanitize your HTML. This is a semgrep security-AUDIT rule: it reports that a sensitive construct is present, not that it is exploitable here. Confirm whether this site handles untrusted input or is reachable across a trust boundary — and apply the change where it is; where the construct is required by the platform or protocol it calls into, and carries no untrusted data (a syscall/FFI shim, a build- or debug-gated tool, a fixed local surface), record the review and leave the code as it is.
Duplicated block (24 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-92 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/MemberResolver.php:102-125 — 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 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 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/Mutation/Organization/AddMemberToOrganizationMutation.php:54— TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Organization/AddMemberToOrganizationMutation.php:54-76 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Mutation/Organization/RemoveMemberToOrganizationMutation.php:54-76 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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/Mutation/Organization/AddMemberToOrganizationMutation.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.
Duplicated block (22 lines × 2) TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationMemberResolver.php:44— TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OrganizationMemberResolver.php:44-65 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Organization/OwnerResolver.php:44-65 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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:44` 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 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 (17 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-98 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/ProjectsResolver.php:104-120 | TaskManager/src/Kreta/TaskManager/Infrastructure/Symfony/GraphQl/Query/Project/Task/TasksResolver.php:131-147 — 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 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 (15 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:127— TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:127-141 | TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php:141-155 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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/Task/CountTasksHandler.php:127` 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.
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.
Duplicated block (13 lines × 3) Notifier/src/Kreta/Notifier/Infrastructure/Serialization/Inbox/Notification/SymfonyNotificationMarkedAsReadDenormalizer.php:43— Notifier/src/Kreta/Notifier/Infrastructure/Serialization/Inbox/Notification/SymfonyNotificationMarkedAsReadDenormalizer.php:43-55 | Notifier/src/Kreta/Notifier/Infrastructure/Serialization/Inbox/Notification/SymfonyNotificationMarkedAsUnreadDenormalizer.php:43-55 | Notifier/src/Kreta/Notifier/Infrastructure/Serialization/Inbox/Notification/SymfonyNotificationPublishedDenormalizer.php:47-59 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once. 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 (13 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:70— TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/CountTasksHandler.php:70-82 | TaskManager/src/Kreta/TaskManager/Application/Query/Project/Task/FilterTasksHandler.php:75-88 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, 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/Task/CountTasksHandler.php:70` 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 (9 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-77 | TaskManager/src/Kreta/TaskManager/Infrastructure/Persistence/Doctrine/ORM/Project/DoctrineORMFilterableSpecification.php:61-69 — 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. 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 (7 lines × 2) TaskManager/src/Kreta/TaskManager/Application/Command/Organization/AddOrganizationMemberToOrganizationHandler.php:39— TaskManager/src/Kreta/TaskManager/Application/Command/Organization/AddOrganizationMemberToOrganizationHandler.php:39-45 | TaskManager/src/Kreta/TaskManager/Application/Command/Organization/AddOwnerToOrganizationHandler.php:39-45 — the copies sit in sibling files of one directory: extract the block into a single shared function in that directory and call it from each site, so a change lands once.
Low IaC: DS-0005 etc/docker/nginx/Dockerfile— ADD instead of COPY
Low IaC: DS-0026 etc/docker/nginx/Dockerfile— No HEALTHCHECK defined Without one the runtime only knows whether the process is alive, not whether it is serving, so a wedged container is restarted by nobody. The step: add a `HEALTHCHECK` to the image that probes the service the way a client would — this image already declares `EXPOSE 80`, so a request to `localhost:80` on the service's own health or root route, exiting non-zero when it does not answer, is the probe — and give it an `--interval`, a `--timeout` and a `--start-period` long enough to cover startup. If the image ships no HTTP client, probe with whatever the runtime already has, or declare the check in the orchestrator instead and say so here.
Low IaC: DS-0026 etc/docker/node/Dockerfile— No HEALTHCHECK defined Without one the runtime only knows whether the process is alive, not whether it is serving, so a wedged container is restarted by nobody. The step: add a `HEALTHCHECK` to the image that probes the service the way a client would — this image already declares `EXPOSE 3000`, so a request to `localhost:3000` on the service's own health or root route, exiting non-zero when it does not answer, is the probe — and give it an `--interval`, a `--timeout` and a `--start-period` long enough to cover startup. If the image ships no HTTP client, probe with whatever the runtime already has, or declare the check in the orchestrator instead and say so here.
D11 · Test Reliability· Test reliability not included · ×1
Test reliability not included — Test source is present (.php, .js) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
Dormant codebase — 53 of 53 significant files have no living knowledge — the codebase as a whole is dormant, not 53 separate risks. Re-engage owners or document before change.
Coverage not included — suite not readable by the collector — Coverage NOT MEASURED: test source is present (.php, .js) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (Clover XML — `vendor/bin/phpunit --coverage-clover coverage.xml`, or lcov — `vitest --coverage`, `jest --coverage`, `bun test --coverage --coverage-reporter=lcov`, or `nyc`) into the repo working tree before the scan — a CI step is the usual place, since the artefact is commonly gitignored.
Info — 2 finding(s)
D12 · Dependency Hygiene· Dependency hygiene not measured · ×1
Dependency hygiene not measured — dependency manifest found but not parsed for hygiene — This repository's dependency manifests (composer.json and package.json) were found, but this pass cannot parse them for hygiene, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D38 wherever the manifest is OSV-readable.
D22 · Internal API Consistency· No exposed public API · ×1
No exposed public API — No intentionally-exposed types (IsPackable or .Contracts) to evaluate.
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.
provenance: not applicable — No CI/build pipeline found (.github/.forgejo/.gitea workflows, .gitlab-ci.yml, azure-pipelines*.yml, .pipelines/, .vsts-ci/, Jenkinsfile, .circleci); there is no build to attest provenance for.
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.
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.
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.
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
—
Run 019fcf17-0a8c-7818-9c71-b78ec9523700 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 57 · Warnings: 41 · Recommendations: 6 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 04-08-2026 @ 23:23 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.