Public report — sqrl, 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.
155findings with an exact file:lineof 165 — the remainder are repo-wide signals (a dimension-level measurement, not a single line); open any file:line and verify
26/95dimensions across the health lenses57748 LoC — wide & deep
Executive summary
Read through the Production lens — the standard calibration. *Green* means good enough to run in production. The score is absolute and comparable across repos.
DataSQRL/sqrl is sound in substance but carries real gaps (62%). It is not in crisis, but the issues below raise the cost of changing it — friction its consumers ultimately inherit.
It is strongest in Architecture (100%) — the structure is clean and changes stay contained. Code Health (81%) 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 Security (54%) — exposure to security and compliance incidents is elevated. Readiness (59%) is the next concern — 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.
Leadership focus, highest impact first: SAST step to CI running what this repository's stack ships (Security & performance tooling); Keep a changelog (e.g. Keep-a-Changelog) recording what shipped… (Release Hygiene); 11 High finding(s) (Static Analysis (SAST)).
For scale: Medium (~57,748 production lines); rebuilding it from scratch would take roughly ~0.7 person-years (~1–2 engineers). Approximate, ±~30%.
It builds on a genuinely strong Architecture 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.
0.9× (at 62% quality) — the last 20% of quality is most of the work
Size & shape
Medium · effort split not classified (source measured from disk; the effort-tier breakdown is a C#-only syntax walk)
This codebase represents roughly ~0.7 person-years of build effort (about ~€100,000 to rebuild). Its weakest lens is Security at 54% — the part of that asset most exposed by the findings below.
How we model this: boilerplate at a scaffolding rate + logic × domain Standard (×1.2) — CQRS × a 0.9× 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: spotbugs with find-sec-bugs — 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 · Medium · Value at risk
This is a Medium asset (~0.7 person-years to rebuild), and its weakest lens is Security at 54%. The operational and business risk on an asset this size concentrates there — that's where remediation buys the most protection.
→ Direct remediation budget at Security 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: spotbugs with find-sec-bugs — 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: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Architecture — module dependency matrix
105 modules, 411 dependencies — 4 dependency cycles, 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.)
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
33
High / Critical
A03:2021 — Injection
11
High / Critical
A05:2021 — Security Misconfiguration
11
High / Critical
Roadmap
First, integrate a security scanning step into the CI pipeline to fail the build on new vulnerabilities. Next, maintain a changelog to clearly document what is shipped in each release. Then, address the 11 high-priority static analysis findings, focusing on the build and deployment workflows. After that, resolve the 12 high-severity dependency vulnerabilities. Finally, establish an architecture decision record system to document significant technical choices and their consequences.
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: spotbugs with find-sec-bugs — 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. 24 of 26 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 2 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.6 — 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 — 26 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, 155 of 165 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.
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.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement.
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".
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 (3): D19, 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.
15 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was GraphqlSchemaUtil.getGraphQLType at 51. A further 5 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 SqrlTypeRelDataTypeConverter.convert at 39 — they are counted neither in the figure above nor in this dimension's score.
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 GraphqlSchemaUtil.getGraphQLType (cyclomatic 51) finding(s) in Cyclomatic Complexity — start with GraphqlSchemaUtil.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FlexibleJsonFlinkFormatTypeMapper.getMapper (cyclomatic 41) finding(s) in Cyclomatic Complexity — start with FlexibleJsonFlinkFormatTypeMapper.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 SQRLLogicalPlanAnalyzer.visit (cyclomatic 39) finding(s) in Cyclomatic Complexity — start with SQRLLogicalPlanAnalyzer.java. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
+ 41 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 SqlScriptPlanner.planStatement (cognitive 108) finding(s) in Cognitive Complexity — start with SqlScriptPlanner.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 DefaultSchemaGenerator.merge (cognitive 84) finding(s) in Cognitive Complexity — start with DefaultSchemaGenerator.java. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 SQRLLogicalPlanAnalyzer.visit (cognitive 68) finding(s) in Cognitive Complexity — start with SQRLLogicalPlanAnalyzer.java. — One of this dimension's main actionable groups (1 warning-level).
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.2 / 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.
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor8.7 / 10Strong✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
33 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is sqrl-planner/src/main/java/com/datasqrl/plan/rules/SqrlRelMdRowCount.java.
Off-boarding risk: anonymized user #1 · ×2
What to do
Resolve the 2 Off-boarding risk finding(s) in Bus Factor. — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
DataSQRL's documentation is clear and complete for an open-source agentic data engineering harness. The README gives a strong overview of what DataSQRL does, its three key capabilities (Conceptual Framework, Comprehensive Validation, Real-World Feedback), and links to the CircleCI CI badge, Maven Central, Docker image version, and license. A dedicated SQRL Testing section explains where integration tests live and lists important test classes, while the server, planner, discovery, and CLI modules each have their own READMEs covering core functionality. The website is also documented (Docusaurus), though its body is clipped mid-installation.
The website README installs Docusaurus and begins the installation, but no further documentation is shown (no body), so it cannot be confirmed whether topics such as API reference or migration guides are present.documentation/README.md
What to do
Resolve the 1 The website README installs Docusaurus and begins the installation, but… finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
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: dependabot-missing-cooldown · ×11.github/dependabot.yml:8detected by semgrep finding
What to do
Resolve the 11 High finding(s) in Static Analysis (SAST) — start with build.yml (3), deploy.yml (3), bump-examples-version.yml (2). — One of this dimension's main actionable groups (11 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
High IaC: DS-0002 · ×4Dockerfile.mcp-inspectordetected by trivy finding
Medium IaC: CKV_DOCKER_3 · ×5sqrl-cli/Dockerfile:1detected by trivy finding
Low IaC: DS-0014 · ×2sqrl-cli/Dockerfile.basedetected by trivy finding
What to do
Resolve the 4 High IaC finding(s) in IaC & Container Security — start with Dockerfile (2), Dockerfile.mcp-inspector, Dockerfile.base. — One of this dimension's main actionable groups (4 issue-level).
Resolve the 5 Medium IaC finding(s) in IaC & Container Security — start with Dockerfile (2), Dockerfile.duckdb-extensions, Dockerfile.base. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with Dockerfile.base (2). — One of this dimension's main actionable groups (2 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.
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 the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
Resolve the 1 Unpinned build actions finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 PR-triggered workflow without a permissions block finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 No build provenance finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
High CVE: [GHSA redacted] · ×12documentation/package-lock.jsondetected by osv-scanner finding
High vulnerability: [GHSA redacted] · ×3documentation/package-lock.jsondetected by osv-scanner finding
Critical CVE: [GHSA redacted] · ×2documentation/package-lock.jsondetected by osv-scanner finding
Medium CVE: [GHSA redacted] · ×13documentation/package-lock.jsondetected by osv-scanner finding
Low CVE: [GHSA redacted] · ×3documentation/package-lock.jsondetected by osv-scanner finding
What to do
Resolve the 12 High CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (12). — One of this dimension's main actionable groups (12 issue-level).
Resolve the 3 High vulnerability finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 2 Critical CVE finding(s) in OSV Dependency Vulnerabilities — start with package-lock.json (2). — One of this dimension's main actionable groups (2 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.
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 'Testing' section to the root README — how to run the test suite.
Add a README to the 5 of 11 project(s) that lack one — worth up to 0.9 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 Kubernetes, but no Kubernetes manifest or chart exists
What to do
Reconcile the README with reality: README advertises Kubernetes, but no Kubernetes manifest or chart exists.
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 spotbugs with find-sec-bugs (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: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
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.
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.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
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.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not included — 69 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 (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC2 Forms & labels — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC3 Page structure — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC4 Keyboard semantics — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC5 ARIA correctness — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC6 Visual & motion safety — Frontend below the scale floor (19 DOM element(s) < 25) — too little surface to assess accessibility.
AC7 A11y enforcement — Frontend below the scale floor (19 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 applicable to a CQRS architecture (the inward-dependency rule is for layered/clean styles)
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 — ~17827 lines of test source are present (.java) 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 (a Maven POM and package.json), which this pass does not parse yet — so this dimension asserts nothing about this repository's licensing in either direction.
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.
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 (.java, .ts, .tsx) 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 (a Maven POM 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.
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 .java, .ts, .tsx, 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 (.java) 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): 183 value object(s); 1 domain event(s)
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this check looks for (6 CQRS handler(s))
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this check looks for
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 — this card publishes what the CI gate does with the test inventory rather than grading it. The findings above are its output.
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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
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 (JaCoCo XML — `mvn jacoco:report`) 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.
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.
Issue — 33 finding(s)
D38 · OSV Dependency Vulnerabilities· High CVE · ×12
High CVE: [GHSA redacted] documentation/package-lock.json— @babel/plugin-transform-modules-systemjs 7.29.0: [GHSA redacted] — @babel/plugin-transform-modules-systemjs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/plugin-transform-modules-systemjs to 7.29.4 with an `overrides` entry).
High CVE: [GHSA redacted] documentation/package-lock.json— brace-expansion 1.1.14: [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). This is 1 of 3 advisories with a published fix this scan raises against brace-expansion 1.1.14, 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 3 advisories this scan raises against brace-expansion 1.1.14: [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— fast-uri 3.0.6: [GHSA redacted] — fast-uri is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin fast-uri to 3.1.3 with an `overrides` entry). This is 1 of 5 advisories with a published fix this scan raises against fast-uri 3.0.6, and their fixed versions do not agree — anything below 3.1.5 still leaves at least one of them open. Take this package to 3.1.5 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 fast-uri 3.0.6: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— js-yaml 3.14.1: [GHSA redacted] — this repo already declares js-yaml ^5.2.0 directly, at or above the fixed 3.15.0; the vulnerable 3.14.1 is a second copy resolved for a dependency that requires an older range. Upgrade those dependents, or pin js-yaml with an `overrides` entry so only one copy resolves. This is 1 of 3 advisories with a published fix this scan raises against js-yaml 3.14.1, and their fixed versions do not agree — anything below 3.15.0 still leaves at least one of them open. Take this package to 3.15.0 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 js-yaml 3.14.1: [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— lodash 4.17.21: [GHSA redacted] — lodash is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin lodash to 4.18.0 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against lodash 4.17.21, 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 2 advisories this scan raises against lodash 4.17.21: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— lodash-es 4.17.21: [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.18.0 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against lodash-es 4.17.21, 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 2 advisories this scan raises against lodash-es 4.17.21: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— path-to-regexp 0.1.12: [GHSA redacted] — path-to-regexp is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin path-to-regexp to 0.1.13 with an `overrides` entry).
High CVE: [GHSA redacted] documentation/package-lock.json— picomatch 2.3.1: [GHSA redacted] — picomatch is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin picomatch to 2.3.2 with an `overrides` entry). This one row stands for the 2 advisories this scan raises against picomatch 2.3.1: [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— postcss 8.5.8: [GHSA redacted] — postcss is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin postcss to 8.5.12 with an `overrides` entry). This is 1 of 4 advisories with a published fix this scan raises against postcss 8.5.8, and their fixed versions do not agree — anything below 8.5.23 still leaves at least one of them open. Take this package to 8.5.23 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against postcss 8.5.8: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— undici 7.11.0: [GHSA redacted] — undici is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin undici to 7.29.0 with an `overrides` entry). This is 1 of 16 advisories with a published fix this scan raises against undici 7.11.0, and their fixed versions do not agree — anything below 7.29.0 still leaves at least one of them open. Take this package to 7.29.0 or later: that is the floor for the package, not this row's target alone. This one row stands for the 16 advisories this scan raises against undici 7.11.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], [GHSA redacted], [GHSA redacted], [GHSA redacted].
High CVE: [GHSA redacted] documentation/package-lock.json— ws 7.5.10: [GHSA redacted] — ws is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ws to 7.5.11 with an `overrides` entry).
High CVE: [GHSA redacted] documentation/package-lock.json— ws 8.19.0: [GHSA redacted] — ws is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ws to 8.21.0 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against ws 8.19.0, and their fixed versions do not agree — anything below 8.21.0 still leaves at least one of them open. Take this package to 8.21.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 ws 8.19.0: [GHSA redacted], [GHSA redacted].
High: dependabot-missing-cooldown .github/dependabot.yml:8— This Dependabot configuration does not set a cooldown period. Newly published packages can be malicious or unstable. Add a `cooldown` block with `default-days: 7` to each `package-ecosystem` entry under `updates` to wait 7 days before proposing updates to newly published package versions. Reference: https://docs.github.com/en/code-security/dependabot/dependabot-version-updates/configuration-options-for-the-dependabot.yml-file#cooldown. This is a semgrep security-AUDIT rule reporting a POLICY that is absent or weaker than its recommendation, not an exploitable defect. Confirm whether the current setting is a deliberate decision for this repository — and apply the change where it is not; where it is (a policy your release process already enforces elsewhere, or one this repository has consciously opted out of), record the decision and leave the configuration as it is. This configuration file has 4 such entries; one cooldown decision clears them all — reported once.
High: github-actions-mutable-action-tag .github/workflows/build.yml:17— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v6`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:41— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v6`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/build.yml:55— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-node@<40-character SHA>`. This step references `actions/setup-node@v6`; resolve the SHA it points at today with `gh api repos/actions/setup-node/commits/v6 --jq .sha`.
High: run-shell-injection .github/workflows/bump-examples-version.yml:19— Using variable interpolation `${{...}}` with `github` context data in a `run:` step could allow an attacker to inject their own code into the runner. This would allow them to steal secrets and code. `github` context data can have arbitrary user input and should be treated as untrusted. Instead, use an intermediate environment variable with `env:` to store the data and use the environment variable in the `run:` script. Reference it as a shell VARIABLE rather than a `${{ }}` interpolation, using your shell's own syntax (`"$ENVVAR"` in bash, `$env:ENVVAR` in PowerShell), so the value is passed as data and never re-expanded as code.
High: github-actions-mutable-action-tag .github/workflows/bump-examples-version.yml:33— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v6`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/deploy.yml:14— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/checkout@<40-character SHA>`. This step references `actions/checkout@v6`; resolve the SHA it points at today with `gh api repos/actions/checkout/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/deploy.yml:31— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: actions/setup-node@<40-character SHA>`. This step references `actions/setup-node@v6`; resolve the SHA it points at today with `gh api repos/actions/setup-node/commits/v6 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/deploy.yml:47— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: peaceiris/actions-gh-pages@<40-character SHA>`. This step references `peaceiris/actions-gh-pages@v4`; resolve the SHA it points at today with `gh api repos/peaceiris/actions-gh-pages/commits/v4 --jq .sha`.
High: github-actions-mutable-action-tag .github/workflows/lint-pr-title.yml:14— GitHub Actions step uses a mutable tag or branch reference. Tags and branch names can be silently repointed by the action owner, enabling supply-chain attacks — as seen in the trivy-action and kics-github-action compromises. Pin the reference to a full 40-character commit SHA instead, e.g. `uses: amannn/action-semantic-pull-request@<40-character SHA>`. This step references `amannn/action-semantic-pull-request@v6`; resolve the SHA it points at today with `gh api repos/amannn/action-semantic-pull-request/commits/v6 --jq .sha`.
High: object-deserialization sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/exec/FlinkExecFunctionPlan.java:39— Found object deserialization using ObjectInputStream. Deserializing entire Java objects is dangerous because malicious actors can create Java object streams with unintended consequences. Ensure that the objects being deserialized are not user-controlled. If this must be done, consider using HMACs to sign the data stream to make sure it is not tampered with, or consider only transmitting object fields and populating a new object. 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.
High IaC: DS-0002 Dockerfile.mcp-inspector— 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 -S -D 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-0002 sqrl-cli/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-0002 sqrl-cli/Dockerfile.base— 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-0002 sqrl-server/sqrl-server-vertx/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.
D38 · OSV Dependency Vulnerabilities· High vulnerability · ×3
High vulnerability: [GHSA redacted] documentation/package-lock.json— js-yaml 5.2.0: [GHSA redacted] — this repo declares js-yaml ^5.2.0, a range that ALREADY admits the fixed 5.2.2, so there is no manifest edit to make here. Re-resolve the lock so js-yaml moves onto 5.2.2 or later; if the flagged 5.2.0 comes back, a dependency is pinning it — upgrade that dependent, or pin js-yaml with an `overrides` entry so only one copy resolves. This is 1 of 2 advisories with a published fix this scan raises against js-yaml 5.2.0, and their fixed versions do not agree — anything below 5.2.2 still leaves at least one of them open. Take this package to 5.2.2 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 js-yaml 5.2.0: [GHSA redacted], [GHSA redacted].
High vulnerability: [GHSA redacted] documentation/package-lock.json— serialize-javascript 6.0.2: [GHSA redacted] — serialize-javascript is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 7.0.3 is a MAJOR ahead of the resolved 6.0.2, so an `overrides` pin would force a breaking version under a dependent written against 6.0.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead). This is 1 of 2 advisories with a published fix this scan raises against serialize-javascript 6.0.2, and their fixed versions do not agree — anything below 7.0.5 still leaves at least one of them open. Take this package to 7.0.5 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 serialize-javascript 6.0.2: [GHSA redacted], [GHSA redacted].
High vulnerability: [GHSA redacted] documentation/package-lock.json— svgo 3.3.3: [GHSA redacted] — svgo is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin svgo to 3.3.4 with an `overrides` entry).
Critical CVE: [GHSA redacted] documentation/package-lock.json— shell-quote 1.8.3: [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). This is 1 of 2 advisories with a published fix this scan raises against shell-quote 1.8.3, 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.8.3: [GHSA redacted], [GHSA redacted].
Critical CVE: [GHSA redacted] documentation/package-lock.json— websocket-driver 0.7.4: [GHSA redacted] — websocket-driver is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin websocket-driver to 0.7.5 with an `overrides` entry). This one row stands for the 2 advisories this scan raises against websocket-driver 0.7.4: [GHSA redacted], [GHSA redacted].
Boundary-crossing change coupling: CompilationProcess.java ↔ GraphqlSchemaHandler.java sqrl-cli/src/main/java/com/datasqrl/compile/CompilationProcess.java— `sqrl-cli/src/main/java/com/datasqrl/compile/CompilationProcess.java` (context sqrl-cli) and `sqrl-planner/src/main/java/com/datasqrl/server/GraphqlSchemaHandler.java` (context sqrl-planner) sit in DIFFERENT parts of the tree yet change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see.
Warning — 118 finding(s)
D38 · OSV Dependency Vulnerabilities· Medium CVE · ×13
Medium CVE: [GHSA redacted] documentation/package-lock.json— ajv 6.12.6: [GHSA redacted] — ajv is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ajv to 6.14.0 with an `overrides` entry).
Medium CVE: [GHSA redacted] documentation/package-lock.json— ajv 8.17.1: [GHSA redacted] — ajv is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin ajv to 8.18.0 with an `overrides` entry).
Medium CVE: [GHSA redacted] documentation/package-lock.json— dompurify 3.2.7: [GHSA redacted] — dompurify is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin dompurify to 3.4.0 with an `overrides` entry). This is 1 of 16 advisories with a published fix this scan raises against dompurify 3.2.7, and their fixed versions do not agree — anything below 3.4.12 still leaves at least one of them open. Take this package to 3.4.12 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 dompurify 3.2.7: [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].
Medium CVE: [GHSA redacted] documentation/package-lock.json— follow-redirects 1.15.11: [GHSA redacted] — follow-redirects is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin follow-redirects to 1.16.0 with an `overrides` entry).
Medium CVE: [GHSA redacted] documentation/package-lock.json— http-proxy-middleware 2.0.9: [GHSA redacted] — http-proxy-middleware is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin http-proxy-middleware to 2.0.10 with an `overrides` entry).
Medium CVE: [GHSA redacted] documentation/package-lock.json— joi 17.13.3: [GHSA redacted] — joi is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin joi to 17.13.4 with an `overrides` entry).
Medium CVE: [GHSA redacted] documentation/package-lock.json— launch-editor 2.13.1: [GHSA redacted] — launch-editor is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin launch-editor to 2.14.1 with an `overrides` entry).
Medium CVE: [GHSA redacted] documentation/package-lock.json— mdast-util-to-hast 13.2.0: [GHSA redacted] — mdast-util-to-hast is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin mdast-util-to-hast to 13.2.1 with an `overrides` entry).
Medium CVE: [GHSA redacted] documentation/package-lock.json— mermaid 11.12.0: [GHSA redacted] — mermaid is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin mermaid to 11.15.0 with an `overrides` entry). This one row stands for the 4 advisories this scan raises against mermaid 11.12.0: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
Medium CVE: [GHSA redacted] documentation/package-lock.json— qs 6.14.2: [GHSA redacted] — qs is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin qs to 6.15.2 with an `overrides` entry).
Medium CVE: [GHSA redacted] documentation/package-lock.json— uuid 11.1.0: [GHSA redacted] — uuid is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin uuid to 11.1.1 with an `overrides` entry).
Medium CVE: [GHSA redacted] documentation/package-lock.json— uuid 8.3.2: [GHSA redacted] — uuid is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (— 11.1.1 is a MAJOR ahead of the resolved 8.3.2, so an `overrides` pin would force a breaking version under a dependent written against 8.3.2; upgrading the declaring package is the remedy, and where no patched release exists in your major line, record the exposure instead).
Medium CVE: [GHSA redacted] documentation/package-lock.json— webpack-dev-server 5.2.3: [GHSA redacted] — webpack-dev-server is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin webpack-dev-server to 5.2.4 with an `overrides` entry). This is 1 of 4 advisories with a published fix this scan raises against webpack-dev-server 5.2.3, and their fixed versions do not agree — anything below 5.2.6 still leaves at least one of them open. Take this package to 5.2.6 or later: that is the floor for the package, not this row's target alone. This one row stands for the 4 advisories this scan raises against webpack-dev-server 5.2.3: [GHSA redacted], [GHSA redacted], [GHSA redacted], [GHSA redacted].
TooManyMethods: GraphqlSchemaVisitor sqrl-planner/src/main/java/com/datasqrl/server/visitor/GraphqlSchemaVisitor.java:67— TooManyMethods — 56 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Sqrl2FlinkSQLTranslator sqrl-planner/src/main/java/com/datasqrl/planner/Sqrl2FlinkSQLTranslator.java:168— TooManyMethods — 45 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ErrorCollector sqrl-planner/src/main/java/com/datasqrl/error/ErrorCollector.java:31— TooManyMethods — 41 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SqrlConfig sqrl-planner/src/main/java/com/datasqrl/config/SqrlConfig.java:52— TooManyMethods — 39 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CalciteUtil sqrl-planner/src/main/java/com/datasqrl/util/CalciteUtil.java:72— TooManyMethods — 38 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SqrlRexUtil sqrl-planner/src/main/java/com/datasqrl/calcite/SqrlRexUtil.java:69— TooManyMethods — 32 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: PostgresConformance sqrl-planner/src/main/java/com/datasqrl/calcite/dialect/PostgresConformance.java:21— TooManyMethods — 32 methods. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Hotspot: sqrl-planner/src/main/java/com/datasqrl/planner/SqlScriptPlanner.java sqrl-planner/src/main/java/com/datasqrl/planner/SqlScriptPlanner.java— sqrl-planner/src/main/java/com/datasqrl/planner/SqlScriptPlanner.java changed 9 times in last 90 days, max complexity 38. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: sqrl-planner/src/main/java/com/datasqrl/planner/analyzer/SQRLLogicalPlanAnalyzer.java sqrl-planner/src/main/java/com/datasqrl/planner/analyzer/SQRLLogicalPlanAnalyzer.java— sqrl-planner/src/main/java/com/datasqrl/planner/analyzer/SQRLLogicalPlanAnalyzer.java changed 3 times in last 90 days, max complexity 39. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: sqrl-planner/src/main/java/com/datasqrl/server/util/GraphqlSchemaUtil.java sqrl-planner/src/main/java/com/datasqrl/server/util/GraphqlSchemaUtil.java— sqrl-planner/src/main/java/com/datasqrl/server/util/GraphqlSchemaUtil.java changed 2 times in last 90 days, max complexity 51. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
Hotspot: sqrl-planner/src/main/java/com/datasqrl/function/translation/duckdb/builtin/DuckDbSqlTranslationUtils.java sqrl-planner/src/main/java/com/datasqrl/function/translation/duckdb/builtin/DuckDbSqlTranslationUtils.java— sqrl-planner/src/main/java/com/datasqrl/function/translation/duckdb/builtin/DuckDbSqlTranslationUtils.java changed 2 times in last 90 days, max complexity 32. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: sqrl-planner/src/main/java/com/datasqrl/engine/log/kafka/KafkaLogEngine.java sqrl-planner/src/main/java/com/datasqrl/engine/log/kafka/KafkaLogEngine.java— sqrl-planner/src/main/java/com/datasqrl/engine/log/kafka/KafkaLogEngine.java changed 3 times in last 90 days, max complexity 20. 1 of those changes was a fix/bug commit, so the churn is repair rather than feature work. Before the next change lands here, cover the area it touches with tests, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time.
Hotspot: sqrl-planner/src/main/java/com/datasqrl/planner/dag/plan/MutationDatabase.java sqrl-planner/src/main/java/com/datasqrl/planner/dag/plan/MutationDatabase.java— sqrl-planner/src/main/java/com/datasqrl/planner/dag/plan/MutationDatabase.java changed 2 times in last 90 days, max complexity 15. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, behind tests written first.
FileTooLong: planner/SqlScriptPlanner.java sqrl-planner/src/main/java/com/datasqrl/planner/SqlScriptPlanner.java:0— FileTooLong — 905 significant lines (blank, comment-only and punctuation-only lines excluded), about 87% of them inside a single declaration: SqlScriptPlanner (147-1237). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: planner/Sqrl2FlinkSQLTranslator.java sqrl-planner/src/main/java/com/datasqrl/planner/Sqrl2FlinkSQLTranslator.java:0— FileTooLong — 793 significant lines (blank, comment-only and punctuation-only lines excluded), about 84% of them inside a single declaration: Sqrl2FlinkSQLTranslator (168-1178). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: analyzer/SQRLLogicalPlanAnalyzer.java sqrl-planner/src/main/java/com/datasqrl/planner/analyzer/SQRLLogicalPlanAnalyzer.java:0— FileTooLong — 706 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: SQRLLogicalPlanAnalyzer (112-1004). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: dag/DAGPlanner.java sqrl-planner/src/main/java/com/datasqrl/planner/dag/DAGPlanner.java:0— FileTooLong — 517 significant lines (blank, comment-only and punctuation-only lines excluded), about 85% of them inside a single declaration: DAGPlanner (98-735). Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Change coupling: MutationConfigurationImpl.java ↔ SubscriptionConfigurationImpl.java sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/MutationConfigurationImpl.java— `sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/MutationConfigurationImpl.java` and `sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/SubscriptionConfigurationImpl.java` change together 62% of the time (8 of the 13 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.
Change coupling: VertxJdbcClient.java ↔ VertxQueryExecutionContext.java sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/jdbc/VertxJdbcClient.java— `sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/jdbc/VertxJdbcClient.java` and `sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/jdbc/VertxQueryExecutionContext.java` change together 56% of the time (10 of the 18 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.
Change coupling: docusaurus.config.ts ↔ index.tsx documentation/docusaurus.config.ts— `documentation/docusaurus.config.ts` and `documentation/src/pages/index.tsx` 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.
Duplicated block (9 lines × 2) sqrl-planner/src/main/java/com/datasqrl/engine/stream/flink/FlinkSqlNodes.java:166— sqrl-planner/src/main/java/com/datasqrl/engine/stream/flink/FlinkSqlNodes.java:166-174 | sqrl-planner/src/main/java/com/datasqrl/engine/stream/flink/FlinkSqlNodes.java:181-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) sqrl-planner/src/main/java/com/datasqrl/engine/stream/flink/FlinkSqlNodes.java:244— sqrl-planner/src/main/java/com/datasqrl/engine/stream/flink/FlinkSqlNodes.java:244-252 | sqrl-planner/src/main/java/com/datasqrl/engine/stream/flink/FlinkSqlNodes.java:280-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/RestBridgeVerticle.java:113— sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/RestBridgeVerticle.java:113-121 | sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/RestBridgeVerticle.java:131-139 — 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 `sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/RestBridgeVerticle.java:113` 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 (7 lines × 2) sqrl-planner/src/main/java/com/datasqrl/function/translation/duckdb/builtin/ElementSqlTranslation.java:43— sqrl-planner/src/main/java/com/datasqrl/function/translation/duckdb/builtin/ElementSqlTranslation.java:43-49 | sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/ElementSqlTranslation.java:42-48 — 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 (7 lines × 2) sqrl-planner/src/main/java/com/datasqrl/function/translation/PostgresLikeTranslations.java:60— sqrl-planner/src/main/java/com/datasqrl/function/translation/PostgresLikeTranslations.java:60-66 | sqrl-planner/src/main/java/com/datasqrl/function/translation/PostgresLikeTranslations.java:80-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/graphql/GraphQLQueryMetricsInstrumentation.java:43— sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/graphql/GraphQLQueryMetricsInstrumentation.java:43-49 | sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/graphql/GraphQLTailSampleTracingInstrumentation.java:85-91 — 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. 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 (8 lines × 2) sqrl-planner/src/main/java/com/datasqrl/util/BaseFileUtil.java:35— sqrl-planner/src/main/java/com/datasqrl/util/BaseFileUtil.java:35-42 | sqrl-planner/src/main/java/com/datasqrl/util/FileUtil.java:110-117 — 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 `sqrl-planner/src/main/java/com/datasqrl/util/BaseFileUtil.java:35` 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. 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) sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/HexSqlTranslation.java:37— sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/HexSqlTranslation.java:37-44 | sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/UnhexSqlTranslation.java:37-44 — 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.
GraphqlSchemaUtil.getGraphQLType (cyclomatic 51) sqrl-planner/src/main/java/com/datasqrl/server/util/GraphqlSchemaUtil.java:111— GraphqlSchemaUtil.getGraphQLType has cyclomatic complexity 51 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
FlexibleJsonFlinkFormatTypeMapper.getMapper (cyclomatic 41) sqrl-planner/src/main/java/com/datasqrl/datatype/flink/json/FlexibleJsonFlinkFormatTypeMapper.java:30— FlexibleJsonFlinkFormatTypeMapper.getMapper has cyclomatic complexity 41 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SQRLLogicalPlanAnalyzer.visit (cyclomatic 39) sqrl-planner/src/main/java/com/datasqrl/planner/analyzer/SQRLLogicalPlanAnalyzer.java:623— SQRLLogicalPlanAnalyzer.visit has cyclomatic complexity 39 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SqlScriptPlanner.planStatement (cyclomatic 38) sqrl-planner/src/main/java/com/datasqrl/planner/SqlScriptPlanner.java:308— SqlScriptPlanner.planStatement has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DuckDbSqlTranslationUtils.flinkDateFormatToDuckDb (cyclomatic 32) sqrl-planner/src/main/java/com/datasqrl/function/translation/duckdb/builtin/DuckDbSqlTranslationUtils.java:95— DuckDbSqlTranslationUtils.flinkDateFormatToDuckDb has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExtendedPostgresSqlDialect.getCastSpec (cyclomatic 23) sqrl-planner/src/main/java/com/datasqrl/calcite/dialect/ExtendedPostgresSqlDialect.java:68— ExtendedPostgresSqlDialect.getCastSpec has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
DefaultSchemaGenerator.merge (cyclomatic 22) sqrl-discovery/src/main/java/com/datasqrl/discovery/stats/DefaultSchemaGenerator.java:135— DefaultSchemaGenerator.merge has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
KafkaLogEngine.createInternal (cyclomatic 20) sqrl-planner/src/main/java/com/datasqrl/engine/log/kafka/KafkaLogEngine.java:156— KafkaLogEngine.createInternal has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DAGPlanner.assemble (cyclomatic 20) sqrl-planner/src/main/java/com/datasqrl/planner/dag/DAGPlanner.java:173— DAGPlanner.assemble has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GraphqlSchemaVisitor.accept (cyclomatic 20) sqrl-planner/src/main/java/com/datasqrl/server/visitor/GraphqlSchemaVisitor.java:96— GraphqlSchemaVisitor.accept has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TypeSignatureUtil.detectSimpleTypeSignature (cyclomatic 19) sqrl-planner/src/main/java/com/datasqrl/io/schema/flexible/input/TypeSignatureUtil.java:36— TypeSignatureUtil.detectSimpleTypeSignature has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SqrlStatementParser.parseStatement (cyclomatic 19) sqrl-planner/src/main/java/com/datasqrl/planner/parser/SqrlStatementParser.java:149— SqrlStatementParser.parseStatement has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SqrlRelMdRowCount.getRowCount (cyclomatic 17) sqrl-planner/src/main/java/com/datasqrl/plan/rules/SqrlRelMdRowCount.java:529— SqrlRelMdRowCount.getRowCount has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DocStringParser.parse (cyclomatic 17) sqrl-planner/src/main/java/com/datasqrl/planner/hint/DocStringParser.java:68— DocStringParser.parse has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
GraphQLSchemaConverter.visit (cyclomatic 16) sqrl-planner/src/main/java/com/datasqrl/server/converter/GraphQLSchemaConverter.java:408— GraphQLSchemaConverter.visit has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SqlScriptPlanner.planStatement (cognitive 108) sqrl-planner/src/main/java/com/datasqrl/planner/SqlScriptPlanner.java:308— SqlScriptPlanner.planStatement has cognitive complexity 108 (threshold 15). Drivers by points: if/else 79, loops 13, boolean chains 11, ternaries 5 (nesting depth added 68). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultSchemaGenerator.merge (cognitive 84) sqrl-discovery/src/main/java/com/datasqrl/discovery/stats/DefaultSchemaGenerator.java:135— DefaultSchemaGenerator.merge has cognitive complexity 84 (threshold 15). Drivers by points: if/else 70, loops 11, ternaries 2, boolean chains 1 (nesting depth added 54). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SQRLLogicalPlanAnalyzer.visit (cognitive 68) sqrl-planner/src/main/java/com/datasqrl/planner/analyzer/SQRLLogicalPlanAnalyzer.java:623— SQRLLogicalPlanAnalyzer.visit has cognitive complexity 68 (threshold 15). Drivers by points: if/else 41, boolean chains 13, ternaries 8, loops 6 (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TypeSignatureUtil.detectSimpleTypeSignature (cognitive 44) sqrl-planner/src/main/java/com/datasqrl/io/schema/flexible/input/TypeSignatureUtil.java:36— TypeSignatureUtil.detectSimpleTypeSignature has cognitive complexity 44 (threshold 15). Drivers by points: if/else 39, boolean chains 2, loops 2, ternaries 1 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DAGPlanner.assemble (cognitive 41) sqrl-planner/src/main/java/com/datasqrl/planner/dag/DAGPlanner.java:173— DAGPlanner.assemble has cognitive complexity 41 (threshold 15). Drivers by points: if/else 36, boolean chains 2, loops 2, error handling 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DuckDbSqlTranslationUtils.flinkDateFormatToDuckDb (cognitive 37) sqrl-planner/src/main/java/com/datasqrl/function/translation/duckdb/builtin/DuckDbSqlTranslationUtils.java:95— DuckDbSqlTranslationUtils.flinkDateFormatToDuckDb has cognitive complexity 37 (threshold 15). Drivers by points: if/else 22, loops 6, boolean chains 5, ternaries 4 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphQLSchemaConverter.visit (cognitive 37) sqrl-planner/src/main/java/com/datasqrl/server/converter/GraphQLSchemaConverter.java:408— GraphQLSchemaConverter.visit has cognitive complexity 37 (threshold 15). Drivers by points: if/else 28, loops 8, boolean chains 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KafkaLogEngine.createInternal (cognitive 35) sqrl-planner/src/main/java/com/datasqrl/engine/log/kafka/KafkaLogEngine.java:156— KafkaLogEngine.createInternal has cognitive complexity 35 (threshold 15). Drivers by points: if/else 20, loops 6, ternaries 6, boolean chains 3 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FieldStats.validate (cognitive 34) sqrl-discovery/src/main/java/com/datasqrl/discovery/stats/FieldStats.java:40— FieldStats.validate has cognitive complexity 34 (threshold 15). Drivers by points: if/else 31, loops 2, boolean chains 1 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqlScriptPlanner.planMain (cognitive 34) sqrl-planner/src/main/java/com/datasqrl/planner/SqlScriptPlanner.java:223— SqlScriptPlanner.planMain has cognitive complexity 34 (threshold 15). Drivers by points: if/else 25, error handling 6, boolean chains 2, loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MutationDatabase.isBackwardsCompatible (cognitive 33) sqrl-planner/src/main/java/com/datasqrl/planner/dag/plan/MutationDatabase.java:72— MutationDatabase.isBackwardsCompatible has cognitive complexity 33 (threshold 15). Drivers by points: if/else 28, loops 3, boolean chains 2 (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BasicTypeManager.computeTypeCombinationMatrix (cognitive 32) sqrl-planner/src/main/java/com/datasqrl/io/schema/flexible/type/basic/BasicTypeManager.java:61— BasicTypeManager.computeTypeCombinationMatrix has cognitive complexity 32 (threshold 15). Drivers by points: if/else 23, loops 7, boolean chains 2 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqrlStatementParser.parseStatement (cognitive 32) sqrl-planner/src/main/java/com/datasqrl/planner/parser/SqrlStatementParser.java:149— SqrlStatementParser.parseStatement has cognitive complexity 32 (threshold 15). Drivers by points: if/else 26, boolean chains 4, ternaries 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SQRLLogicalPlanAnalyzer.visit (cognitive 29) sqrl-planner/src/main/java/com/datasqrl/planner/analyzer/SQRLLogicalPlanAnalyzer.java:478— SQRLLogicalPlanAnalyzer.visit has cognitive complexity 29 (threshold 15). Drivers by points: if/else 24, boolean chains 4, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DocStringParser.parse (cognitive 28) sqrl-planner/src/main/java/com/datasqrl/planner/hint/DocStringParser.java:68— DocStringParser.parse has cognitive complexity 28 (threshold 15). Drivers by points: if/else 21, boolean chains 5, loops 1, ternaries 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RelWriterWithHints.explain_ (cognitive 27) sqrl-planner/src/main/java/com/datasqrl/plan/util/RelWriterWithHints.java:52— RelWriterWithHints.explain_ has cognitive complexity 27 (threshold 15). Drivers by points: if/else 21, loops 4, boolean chains 1, match/switch 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqlScriptStatementSplitter.parseLine (cognitive 27) sqrl-planner/src/main/java/com/datasqrl/planner/parser/SqlScriptStatementSplitter.java:159— SqlScriptStatementSplitter.parseLine has cognitive complexity 27 (threshold 15). Drivers by points: if/else 23, boolean chains 3, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqrlConfig.as (cognitive 26) sqrl-planner/src/main/java/com/datasqrl/config/SqrlConfig.java:177— SqrlConfig.as has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17, error handling 5, boolean chains 2, loops 2 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueryIndexSummary.ofFilter (cognitive 26) sqrl-planner/src/main/java/com/datasqrl/plan/global/QueryIndexSummary.java:69— QueryIndexSummary.ofFilter has cognitive complexity 26 (threshold 15). Drivers by points: if/else 15, ternaries 6, loops 3, boolean chains 2 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphqlSchemaWalker.walkObjectType (cognitive 26) sqrl-planner/src/main/java/com/datasqrl/server/GraphqlSchemaWalker.java:152— GraphqlSchemaWalker.walkObjectType has cognitive complexity 26 (threshold 15). Drivers by points: if/else 25, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PipelineDAGExporter.export (cognitive 24) sqrl-planner/src/main/java/com/datasqrl/plan/global/PipelineDAGExporter.java:72— PipelineDAGExporter.export has cognitive complexity 24 (threshold 15). Drivers by points: if/else 18, ternaries 4, boolean chains 1, loops 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QueryIndexSummary.getCost (cognitive 24) sqrl-planner/src/main/java/com/datasqrl/plan/global/QueryIndexSummary.java:124— QueryIndexSummary.getCost has cognitive complexity 24 (threshold 15). Drivers by points: if/else 19, loops 4, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqlScriptPlanner.addExport (cognitive 23) sqrl-planner/src/main/java/com/datasqrl/planner/SqlScriptPlanner.java:1025— SqlScriptPlanner.addExport has cognitive complexity 23 (threshold 15). Drivers by points: if/else 19, error handling 3, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Sqrl2FlinkSQLTranslator.addTable (cognitive 21) sqrl-planner/src/main/java/com/datasqrl/planner/Sqrl2FlinkSQLTranslator.java:832— Sqrl2FlinkSQLTranslator.addTable has cognitive complexity 21 (threshold 15). Drivers by points: if/else 17, loops 2, boolean chains 1, ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Sqrl2FlinkSQLTranslator.parseSchema (cognitive 20) sqrl-planner/src/main/java/com/datasqrl/planner/Sqrl2FlinkSQLTranslator.java:1032— Sqrl2FlinkSQLTranslator.parseSchema has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18, boolean chains 1, loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DatasqrlTest.run (cognitive 19) sqrl-cli/src/main/java/com/datasqrl/cli/DatasqrlTest.java:90— DatasqrlTest.run has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8, error handling 6, loops 2, ternaries 2, boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
FieldStats.add (cognitive 19) sqrl-discovery/src/main/java/com/datasqrl/discovery/stats/FieldStats.java:87— FieldStats.add has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16, loops 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SchemaImport.convert (cognitive 19) sqrl-planner/src/main/java/com/datasqrl/io/schema/flexible/external/SchemaImport.java:113— SchemaImport.convert has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, loops 3, boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IndexSelector.optimizeIndexesWithCostMinimization (cognitive 19) sqrl-planner/src/main/java/com/datasqrl/plan/global/IndexSelector.java:189— IndexSelector.optimizeIndexesWithCostMinimization has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10, boolean chains 5, loops 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IndexFinder.visit (cognitive 19) sqrl-planner/src/main/java/com/datasqrl/plan/global/IndexSelector.java:389— IndexFinder.visit has cognitive complexity 19 (threshold 15). Drivers by points: if/else 14, boolean chains 5 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphqlSchemaVisitor.accept (cognitive 19) sqrl-planner/src/main/java/com/datasqrl/server/visitor/GraphqlSchemaVisitor.java:96— GraphqlSchemaVisitor.accept has cognitive complexity 19 (threshold 15). Drivers by points: if/else 19. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SqrlRexUtil.decomposeEqualityCondition (cognitive 18) sqrl-planner/src/main/java/com/datasqrl/calcite/SqrlRexUtil.java:134— SqrlRexUtil.decomposeEqualityCondition has cognitive complexity 18 (threshold 15). Drivers by points: if/else 14, boolean chains 4 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
KafkaLogEngine.plan (cognitive 18) sqrl-planner/src/main/java/com/datasqrl/engine/log/kafka/KafkaLogEngine.java:273— KafkaLogEngine.plan has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9, loops 8, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlinkSqlNodes.createColumns (cognitive 18) sqrl-planner/src/main/java/com/datasqrl/engine/stream/flink/FlinkSqlNodes.java:310— FlinkSqlNodes.createColumns has cognitive complexity 18 (threshold 15). Drivers by points: if/else 17, loops 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FlexibleTypeMatcher.matchSingleType (cognitive 18) sqrl-planner/src/main/java/com/datasqrl/io/schema/flexible/input/FlexibleTypeMatcher.java:55— FlexibleTypeMatcher.matchSingleType has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11, ternaries 4, loops 2, boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqlScriptPlanner.addImport (cognitive 18) sqrl-planner/src/main/java/com/datasqrl/planner/SqlScriptPlanner.java:904— SqlScriptPlanner.addImport has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12, ternaries 4, error handling 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ResultSetPrinter.print (cognitive 17) sqrl-cli/src/main/java/com/datasqrl/util/ResultSetPrinter.java:35— ResultSetPrinter.print has cognitive complexity 17 (threshold 15). Drivers by points: if/else 14, loops 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConfigLoaderUtils.resolveConnectorEnvVars (cognitive 17) sqrl-planner/src/main/java/com/datasqrl/util/ConfigLoaderUtils.java:358— ConfigLoaderUtils.resolveConnectorEnvVars has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, loops 5 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqrlRelMdRowCount.getRowCount (cognitive 17) sqrl-planner/src/main/java/com/datasqrl/plan/rules/SqrlRelMdRowCount.java:286— SqrlRelMdRowCount.getRowCount has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12, loops 3, boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DAGPlanner.determinePrimaryKey (cognitive 17) sqrl-planner/src/main/java/com/datasqrl/planner/dag/DAGPlanner.java:436— DAGPlanner.determinePrimaryKey has cognitive complexity 17 (threshold 15). Drivers by points: if/else 15, boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphqlSchemaValidator.validateStructurallyEqualTypes (cognitive 17) sqrl-planner/src/main/java/com/datasqrl/server/GraphqlSchemaValidator.java:131— GraphqlSchemaValidator.validateStructurallyEqualTypes has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13, boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilePath.getComponents (cognitive 16) sqrl-planner/src/main/java/com/datasqrl/io/file/FilePath.java:114— FilePath.getComponents has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
IndexSelector.generateIndexCandidates (cognitive 16) sqrl-planner/src/main/java/com/datasqrl/plan/global/IndexSelector.java:284— IndexSelector.generateIndexCandidates has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9, ternaries 3, loops 2, match/switch 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SqrlRelMdRowCount.getRowCount (cognitive 16) sqrl-planner/src/main/java/com/datasqrl/plan/rules/SqrlRelMdRowCount.java:529— SqrlRelMdRowCount.getRowCount has cognitive complexity 16 (threshold 15). Drivers by points: if/else 16. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SQRLLogicalPlanAnalyzer.analyze (cognitive 16) sqrl-planner/src/main/java/com/datasqrl/planner/analyzer/SQRLLogicalPlanAnalyzer.java:164— SQRLLogicalPlanAnalyzer.analyze has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10, boolean chains 4, ternaries 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GraphQLSchemaConverter.convert (cognitive 16) sqrl-planner/src/main/java/com/datasqrl/server/converter/GraphQLSchemaConverter.java:359— GraphQLSchemaConverter.convert has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11, loops 5 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Unpinned build actions — CI references GitHub Actions by a floating ref (@main / @tag) rather than a pinned commit SHA, weakening build integrity. 8 floating ref(s) across 4 workflow file(s). Each floating ref is itemized at file:line by the SAST (D29) lens.
D36 · Supply-chain Provenance & Signing· PR-triggered workflow without a permissions block · ×1
PR-triggered workflow without a permissions block — 1 workflow(s) triggered by pull_request declare no `permissions:` block (build.yml) and so run with the repository's default GITHUB_TOKEN scope, while 3 sibling workflows in the same repository are already scoped. Pull-request runs build the least-trusted code in the repository; give each of these workflows its own least-privilege block — `permissions: {contents: read}` at the top of the workflow, widened per job only where a job genuinely writes.
Duplicated block (16 lines × 2) sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/swagger/SwaggerService.java:186— sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/swagger/SwaggerService.java:186-201 | sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/swagger/SwaggerService.java:205-220 — 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 (14 lines × 2) sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/auth/JwtFailureHandler.java:35— sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/auth/JwtFailureHandler.java:35-48 | sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/auth/OAuthFailureHandler.java:43-56 — 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.
Duplicated block (13 lines × 2) sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/modules/ApiDeploymentModule.java:119— sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/modules/ApiDeploymentModule.java:119-131 | sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/modules/ApiDeploymentModule.java:136-148 — 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 `sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/modules/ApiDeploymentModule.java:119` 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 × 2) sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/auth/OAuth2AuthFactory.java:95— sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/auth/OAuth2AuthFactory.java:95-106 | sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/auth/OAuth2AuthFactory.java:116-127 — 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 `sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/auth/OAuth2AuthFactory.java:95` 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. 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) sqrl-cli/src/main/java/com/datasqrl/cli/ExecCmd.java:36— sqrl-cli/src/main/java/com/datasqrl/cli/ExecCmd.java:36-46 | sqrl-cli/src/main/java/com/datasqrl/cli/RunCmd.java:39-50 — 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.
Duplicated block (10 lines × 2) sqrl-planner/src/main/java/com/datasqrl/planner/util/CompiledPlanCondenser.java:62— sqrl-planner/src/main/java/com/datasqrl/planner/util/CompiledPlanCondenser.java:62-71 | sqrl-planner/src/main/java/com/datasqrl/planner/util/CompiledPlanCondenser.java:90-99 — 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 `sqrl-planner/src/main/java/com/datasqrl/planner/util/CompiledPlanCondenser.java:62` 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 (8 lines × 3) sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/BaseShaSqlTranslation.java:37— sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/BaseShaSqlTranslation.java:37-44 | sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/FromBase64SqlTranslation.java:37-44 | sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/ToBase64SqlTranslation.java:37-44 — 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.
Duplicated block (7 lines × 4) sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/FromBase64SqlTranslation.java:36— sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/FromBase64SqlTranslation.java:36-42 | sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/HexSqlTranslation.java:36-42 | sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/ToBase64SqlTranslation.java:36-42 | sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/UnhexSqlTranslation.java:36-42 — 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.
Duplicated block (6 lines × 2) sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/LogSqlTranslation.java:43— sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/LogSqlTranslation.java:43-48 | sqrl-planner/src/main/java/com/datasqrl/function/translation/PostgresLikeTranslations.java:32-37 — 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 `sqrl-planner/src/main/java/com/datasqrl/function/translation/postgres/builtinflink/LogSqlTranslation.java: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.
Low CVE: [GHSA redacted] documentation/package-lock.json— @babel/core 7.29.0: [GHSA redacted] — @babel/core is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin @babel/core to 7.29.6 with an `overrides` entry).
Low CVE: [GHSA redacted] documentation/package-lock.json— body-parser 1.20.4: [GHSA redacted] — body-parser is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin body-parser to 1.20.6 with an `overrides` entry).
Low CVE: [GHSA redacted] documentation/package-lock.json— webpack 5.99.7: [GHSA redacted] — webpack is not declared in this repo's manifests: it is pulled in transitively, so upgrade the dependency that requires it (or pin webpack to 5.104.0 with an `overrides` entry). This is 1 of 2 advisories with a published fix this scan raises against webpack 5.99.7, and their fixed versions do not agree — anything below 5.104.1 still leaves at least one of them open. Take this package to 5.104.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 webpack 5.99.7: [GHSA redacted], [GHSA redacted].
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 28 significant file(s) lose their only recent owner: sqrl-planner/src/main/java/com/datasqrl/util/ConfigLoaderUtils.java, sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/graphql/GraphQLTailSampleTracingInstrumentation.java, sqrl-planner/src/main/java/com/datasqrl/planner/FlinkPlannerConfigBuilder.java, sqrl-planner/src/main/java/com/datasqrl/function/translation/duckdb/builtin/TimestampDiffSqlTranslation.java, sqrl-planner/src/main/java/com/datasqrl/function/translation/duckdb/builtin/DuckDbSqlTranslationUtils.java, sqrl-server/sqrl-server-vertx-base/src/main/java/com/datasqrl/server/GraphQLServerVerticle.java, sqrl-planner/src/main/java/com/datasqrl/planner/parser/SqlScriptStatementSplitter.java, sqrl-cli/src/main/java/com/datasqrl/cli/AbstractCompileCmd.java (+20 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: sqrl-planner/src/main/java/com/datasqrl/plan/rules/SqrlRelMdRowCount.java, sqrl-planner/src/main/java/com/datasqrl/planner/analyzer/TableAnalysis.java, sqrl-planner/src/main/java/com/datasqrl/planner/tables/SqrlTableFunction.java, sqrl-planner/src/main/java/com/datasqrl/engine/EngineFeature.java, sqrl-planner/src/main/java/com/datasqrl/planner/hint/RowCountHint.java. Pair on, review, or document these before any departure.
Low IaC: DS-0014 sqrl-cli/Dockerfile.base— RUN using 'wget' and 'curl'
Low IaC: DS-0026 sqrl-cli/Dockerfile.base— 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 8080`, so a request to `localhost:8080` 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 (.java) 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.
D19 · Documentation Quality· The website README installs Docusaurus and begins the installation, but no further documentation is shown (no body), so it cannot be confirmed whether topics such as API reference or migration guides are present. · ×1
The website README installs Docusaurus and begins the installation, but no further documentation is shown (no body), so it cannot be confirmed whether topics such as API reference or migration guides are present. documentation/README.md— Add a short 'Getting Started' section for the site covering how to contribute docs locally.
No build provenance — No SLSA provenance generation or build attestation found in CI — nothing binds a released artifact to the build that produced it, so a consumer cannot tell your artifact from a substituted one. Your release already signs its artifacts, so this is the remaining step rather than a new pipeline: attestation records HOW the artifact was built, which a signature over the finished file does not. On GitHub Actions, `actions/attest-build-provenance` (or slsa-github-generator) emits one from the job's own OIDC identity; elsewhere, run `cosign attest` over the released artifact from the release pipeline and publish the attestation beside it.
D36 · Supply-chain Provenance & Signing· No SBOM · ×1
No SBOM — No SBOM generation or committed SBOM found — produce one with what your ecosystem ships (the `cyclonedx-maven-plugin` bound to the package phase, `syft` (or `anchore/sbom-action` in CI) over the source tree or released image). Publish it as a release asset (`*.spdx.json` / `*.cdx.json`) so consumers can see what they are installing.
Coverage not included — suite not readable by the collector — Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml) and a coverage step in CI (`codecov upload`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.java), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored. To have the real number read, produce a coverage report in a standard format (JaCoCo XML — `mvn jacoco:report`) 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 (a Maven POM 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.
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 019fceab-258e-7646-b4a6-f02e0a97148f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 33 · Warnings: 118 · Recommendations: 12 · Info: 2 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 04-08-2026 @ 21:25 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.