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

zio/zio-quill

Measured 14 November 2026, 07:03 UTC, at code version fc0800f

CAI score 55out of 100 Adequate
CriticalWeakAdequateStrongExemplary
Down 4 since the last survey

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

A medium codebase: 23,626 lines of product code in 17 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Security and Compliance, 46

Findings by how serious they are

63 critical 134 serious 189 minor

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

This survey was produced by

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 07:03 UTC

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

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

47of 47 dimensions measured by tools.
363of 386 findings point to an exact file and line, so you can open each one in the code. The other 23 concern the repository as a whole, such as missing documentation.
47dimensions across 6 lenses, read from 23,626 lines of product code in 17 projects.
Chapters

Executive summary

zio/zio-quill falls short of our standard for production, in part because it has pipeline tools referenced by a changeable name. It scores 55 out of 100 and is rated Adequate, and all 63 of its critical findings are security problems.

Security and Compliance, at 46, is the weakest lens and counts most in the score. The best first step for the work it takes is replacing the two exposed passwords or keys and switching the old ones off, worth about 3 points. Stopping the 12 pipeline steps that hand secrets to unpinned tools would lift Security and Compliance itself, worth about 5 points. Raising Security and Compliance to 70 would lift the score to about 60.

Thirty-seven pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Thirteen secrets can leak from the build pipeline, and eleven settings leave the servers or containers unsafe. Pinning each tool to an exact version, limiting each secret to its own step and correcting the unsafe settings would close these risks. The two passwords or keys in the code need replacing, with the old ones switched off.

The product code is 23,626 lines, about €65,000 to rebuild.

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

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

If Security and Compliance rose from 46 to 70, the lowest score rated Strong, the score would rise from 55 to about 60.

Code composition: what the lines of code are
Product code 36%Tests 64%
New since the last survey: 33 findings

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

  • Code Duplication · Edited copy of a member (70 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
  • Code Duplication · Edited copy of a member (75 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
  • Code Duplication · Edited copy of a member (47 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
  • Code Duplication · Edited copy of a member (30 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
  • Code Duplication · Edited copy of a member (56 corresponding lines) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala
  • Code Duplication · Edited copy of a member (22 corresponding lines) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala
  • Code Duplication · Edited copy of a member (36 corresponding lines) quill-engine/src/main/scala/zio/quill/norm/AdHocReduction.scala
  • Code Duplication · Edited copy of a member (14 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
  • Code Duplication · Edited copy of a member (13 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
  • Code Duplication · Edited copy of a member (18 corresponding lines) quill-core/src/main/scala/zio/quill/quotation/TranspileConfigSummoning.scala
  • Code Duplication · Edited copy of a member (17 corresponding lines) quill-engine/src/main/scala/zio/quill/norm/RepropagateQuats.scala
  • Code Duplication · Edited copy of a member (17 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala
  • Code Duplication · Edited copy of a member (11 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/norm/AddDropToNestedOrderBy.scala
  • Code Duplication · Edited copy of a member (7 corresponding lines) quill-engine/src/main/scala/zio/quill/quotation/FreeVariables.scala
  • Code Duplication · Edited copy of a member (9 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/norm/ExpandNestedQueries.scala
  • Code Duplication · Edited copy of a member (19 corresponding lines) quill-codegen-jdbc/src/main/scala/zio/quill/codegen/jdbc/gen/DefaultJdbcSchemaReader.scala
  • Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala
  • Code Duplication · Edited copy of a member (7 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala
  • Code Duplication · Edited copy of a member (10 corresponding lines) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala
  • Code Duplication · Edited copy of a member (11 corresponding lines) quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) quill-core/src/main/scala/zio/quill/context/mirror/MirrorEncoders.scala
  • Code Duplication · Edited copy of a member (7 corresponding lines) quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala
  • Code Duplication · Edited copy of a member (5 corresponding lines) quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala
  • Code Duplication · Edited copy of a member (6 corresponding lines) quill-core/src/main/scala/zio/quill/context/ContextVerbTranslate.scala
  • Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) quill-engine/src/main/scala/zio/quill/MySQLDialect.scala
  • Code Duplication · Edited copy of a member (4 corresponding lines) quill-engine/src/main/scala/zio/quill/PostgresDialect.scala

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

Fixed since the last survey: 5 findings

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

  • Code Duplication · Duplicated block (8–14 lines × 2) quill-engine/src/main/scala/zio/quill/SqliteDialect.scala
  • Code Duplication · Duplicated block (8 lines × 2) quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala
  • Code Duplication · Duplicated block (5 lines × 2) quill-engine/src/main/scala/zio/quill/OracleDialect.scala
  • Code Duplication · Duplicated block (5 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala
  • Code Duplication · Duplicated block (5 lines × 2) quill-engine/src/main/scala/zio/quill/MirrorIdiom.scala
Rebuild cost: about €65,000 · Estimate
Cost to rebuild€21,000 to €110,000, for 358 to 1,137 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemStandard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor×0.8 at a score of 55. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
SizeMedium: 23,626 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

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

Top priorities

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

1
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED.
Raises the score by about 3 points · Low effort · Secret Scanning
2
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2).
Raises the score by about 5 points · Medium effort · Static Analysis (SAST)
3
Resolve the 118 Orphaned file finding(s) in Knowledge Freshness — start with Encoders.scala (3), Decoders.scala (3), Quill.scala (2).
Raises the score by about 4 points · High effort · Knowledge Freshness

Diagnosis: what the measurements show together

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

Where the investment is most exposed · Value at risk
This code would cost about €65,000 to build again, about 0.4 person-years of work. Its weakest lens is Security and Compliance, at 46 (checked 4 of 10). Security and Compliance is about how well the product is protected, and how it handles personal data. Because the weakest lens counts most in the score, work on Security and Compliance also moves the score most.
Based on: the rebuild estimate · the Security and Compliance grade · how much each lens counts
What to do: Start with the Security and Compliance actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Leaked secret finding(s) in Secret Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 3 points for low effort, because it clears the 2 Secret Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

Architecture: which parts of the code depend on which

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

221 modules, with 293 dependencies between them. One loop runs through 25 of the modules, marked above the diagonal.

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

Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
uses →1 codegen.model2 monad3 util.Messages4 codegen.gen5 context.json6 context.mirror7 dsl8 idiom9 util10 codegen.jdbc.gen11 context12 idiom.StatementInterpolator13 norm14 context.orientdb15 quotation16 quat17 ast18 context.cassandra19 context.sql20 context.sql.idiom.SqlIdiom21 quat.Quat22 context.jdbc23 context.sql.idiom24 context.qzio25 sql.idiom26 zio.quill27 AsyncMirrorContext28 H2ZioJdbcContext29 MirrorContext30 MirrorSqlDialect31 MysqlZioJdbcContext32 PostgresDialect33 PostgresZioJdbcContext34 doobie35 jdbczio36 quotation.TranspileConfigSummoning37 sql.norm38 context.spark39 context.sql.norm40 jdbczio.Quill
1 codegen.model
2 monad
3 util.Messages
4 codegen.gen13
5 context.json2
6 context.mirror2
7 dsl1237
8 idiom2183
9 util2
10 codegen.jdbc.gen102
11 context262384
12 idiom.StatementInterpolator5
13 norm121582
14 context.orientdb3
15 quotation1112573
16 quat11
17 ast76
18 context.cassandra147
19 context.sql1112151
20 context.sql.idiom.SqlIdiom321
21 quat.Quat111
22 context.jdbc11015
23 context.sql.idiom31123124814
24 context.qzio13122
25 sql.idiom12212
26 zio.quill6141414871021463541838133
27 AsyncMirrorContext151
28 H2ZioJdbcContext111
29 MirrorContext131
30 MirrorSqlDialect131
31 MysqlZioJdbcContext111
32 PostgresDialect1132
33 PostgresZioJdbcContext1111
34 doobie1211
35 jdbczio41131
36 quotation.TranspileConfigSummoning11121
37 sql.norm221111
38 context.spark121174142
39 context.sql.norm31963
40 jdbczio.Quill1777
Uses a module listed above itPart of a loopThe module itself
1 codegen.model2 monad3 util.Messages4 codegen.gen5 context.json6 context.mirror7 dsl8 idiom9 util10 codegen.jdbc.gen11 context12 idiom.StatementInterpolator13 norm14 context.orientdb15 quotation16 quat17 ast18 context.cassandra19 context.sql20 context.sql.idiom.SqlIdiom21 quat.Quat22 context.jdbc23 context.sql.idiom24 context.qzio25 sql.idiom26 zio.quill27 AsyncMirrorContext28 H2ZioJdbcContext29 MirrorContext30 MirrorSqlDialect31 MysqlZioJdbcContext32 PostgresDialect33 PostgresZioJdbcContext34 doobie35 jdbczio36 quotation.TranspileConfigSummoning37 sql.norm38 context.spark39 context.sql.norm40 jdbczio.Quillcodegen.model1monad2util.Messages3codegen.gen4context.json5context.mirror6dsl7idiom8util9codegen.jdbc.gen10context11idiom.StatementInterpolator12norm13context.orientdb14quotation15quat16ast17context.cassandra18context.sql19context.sql.idiom.SqlIdiom20quat.Quat21context.jdbc22context.sql.idiom23context.qzio24sql.idiom25zio.quill26AsyncMirrorContext27H2ZioJdbcContext28MirrorContext29MirrorSqlDialect30MysqlZioJdbcContext31PostgresDialect32PostgresZioJdbcContext33doobie34jdbczio35quotation.TranspileConfigSummoning36sql.norm37context.spark38context.sql.norm39jdbczio.Quill401322123721832102262384512158231112573117614711121513211111101531123124814131221221261414148710214635418381331511111311311111132111112114113111121221111121174142319631777+181 more modules (most-connected shown)

At a glance — Code Health · 63% · Adequate · gated by X5 ·

At a glance — Architecture · 99% · Exemplary ·

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

At a glance — Readiness · 61% · Adequate · gated by D13, P3 ·

At a glance — Security · 46% · Checked 4 of 10 · gated by D29, D36 ·

At a glance — Performance · 100% · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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

OWASP categoryFindingsSeverity
A05:2025 — Injection50High / Critical
A02:2025 — Security Misconfiguration27High / Critical
A03:2025 — Software Supply Chain Failures4Medium
A07:2025 — Authentication Failures2High / Critical

Roadmap

Top priorities: Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2); Resolve the 118 Orphaned file finding(s) in Knowledge Freshness — start with Encoders.scala (3), Decoders.scala (3), Quill.scala (2); Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.

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

Do thisHelpsEffortDimension
Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED.+3.1 ptsLowSecret Scanning
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2).+4.6 ptsMediumStatic Analysis (SAST)
Resolve the 118 Orphaned file finding(s) in Knowledge Freshness — start with Encoders.scala (3), Decoders.scala (3), Quill.scala (2).+4.1 ptsHighKnowledge Freshness
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.+3.9 ptsMediumArchitecture documentation
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED.+1.5 ptsLowStatic Analysis (SAST)
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.4 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.4 ptsLowSupply-chain Provenance & Signing
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing.+1.4 ptsLowSupply-chain Provenance & Signing

File quality

Per-file score 0–10 — a quality signature. Of 73 files carrying findings, judged against the Production bar: 5% slop · 46% mixed · 49% near-clean.

FileScoreBandWorst signal
REDACTED0.0SlopSecret Scanning: Leaked secret: REDACTED
REDACTED0.7SlopSecret Scanning: Leaked secret: REDACTED
REDACTED3.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED3.7SlopIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedIaC & Container Security: High IaC: REDACTED
REDACTED4.4MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED4.8MixedStatic Analysis (SAST): High: REDACTED
REDACTED5.8MixedStatic Analysis (SAST): High: REDACTED
quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala6.0MixedExplicit Debt: TodoComment
quill-core/src/main/scala/zio/quill/quotation/Parsing.scala6.0MixedExplicit Debt: TodoComment
quill-core/src/main/scala/zio/quill/dsl/DynamicQueryDSL.scala6.0MixedExplicit Debt: TodoComment
quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcUnderlyingContext.scala6.7MixedExplicit Debt: TodoComment
quill-core/src/main/scala/zio/quill/context/ContextVerbTranslate.scala6.7MixedExplicit Debt: TodoComment
quill-engine/src/main/scala/zio/quill/MySQLDialect.scala6.7MixedExplicit Debt: TodoComment
quill-core/src/main/scala/zio/quill/context/ActionMacro.scala6.7MixedExplicit Debt: TodoComment

How the grades work

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

Critical — 63

A definite problem that already costs you something and drags the score down: a missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here tends to cause failures elsewhere.

Serious — 134

Likely wrong, but not failing yet. It degrades the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to carry for two years either.

Minor — 189

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

Could not be resolved — 14

Something this survey could not settle from the outside, and which could be critical or serious. Either a control was required and no positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean result. These are excluded from the score rather than awarded a pass, so the number on the cover neither rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each one is named under Limitations.

Methodology & how to trust this report

This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 47 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 47 dimensions across the health lenses
D1D2D3D4D5D6D12D13D14D15D16D17D28D29D30D31D34D35D36D43AX10AX3AX4AX6AX8GD1IC1M1M2M3M4P1P10P2P3P4P6PF3X1X12X16X20X21X23X27X3X5

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

How to trust any code-health report — three questions
  1. Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 363 of 386 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.

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

Tools & methods

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

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivy · checkovSecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3 · 3.2.533✓ deterministic

Every finding is locatable in findings.md. Run 01a1d8de-32c4-75d7-8231-c0acbc95a0af.

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

Run transparency — what happened this run

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

  • D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT READ here — but this repository measures it: a Codecov configuration (codecov.yml) and a coverage step in CI (`sbt $SBT_ARGS coverageReport`) shows that coverage is collected and tracked in your own CI. The built-in collector has no runner for this ecosystem (.scala), so the analyzer could not read the number — a gap in the analyzer's language coverage, not an unmeasured repo. Not scored.
  • D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.scala) and this repository declares an sbt build (repository root, 410 test files), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
  • D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares package.json, but the licence verdict published here was taken over its sbt dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.sbt), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
  • D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (23626 LoC, 1262 module-visible types across 68 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D27 Navigability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `quill-core/src/main/scala/zio/quill/quotation/Parsing.scala` produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 17 — an image could not be built) — failed to solve: failed to load cache key: invalid response status 429; runtime evidence skipped.
  • C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'javax.sql.DataSource' is imported (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'javax.sql.DataSource' is imported (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 'javax.sql.DataSource' is imported (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10), but no entity, schema, table or model declaration this check reads was found beside it, so whether personal data is stored could not be decided.
  • M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.

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

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.

Per-dimension blind spots

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

  • D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
  • D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
  • D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
  • D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
  • D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
  • D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
  • D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
  • D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
  • D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
  • D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
  • D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
  • D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
  • D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
  • D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
  • D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
  • D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
  • D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
  • D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
  • D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
  • AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
  • M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
  • P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
  • P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.

Dimensions

D1 · Cyclomatic Complexity8.1 / 10Strong✓ Tool-verified

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

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

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

9 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SqlQueryApply.flatten at 46. A further 25 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 DefaultJdbcTyper.apply at 26 — they are counted neither in the figure above nor in this dimension's score. 14 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: quill-codegen-jdbc/src/main/scala/zio/quill/codegen/jdbc/model/DefaultJdbcTyper.scala (DefaultJdbcTyper.apply at 26), quill-engine/src/main/scala/zio/quill/MirrorIdiom.scala (MirrorIdiomBase.astTokenizer at 23), quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala (StatefulTransformer.apply at 23), quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala (StatefulTransformerWithStack.apply at 23), quill-engine/src/main/scala/zio/quill/ast/StatelessTransformer.scala (StatelessTransformer.apply at 23), and 9 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.

SqlQueryApply.flatten (cyclomatic 46)quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:204
QuatMakingBase.inferQuat (cyclomatic 38)quill-core/src/main/scala/zio/quill/quat/QuatMaking.scala:158
SheathLeafClauses.apply (cyclomatic 26)quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:114
NormalizeNestedStructures.unapply (cyclomatic 22)quill-engine/src/main/scala/zio/quill/norm/NormalizeNestedStructures.scala:7
SqlIdiom.actionTokenizer (cyclomatic 21)quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:654

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

What to do

  1. Bring the 2 bodies over 30 down to 30 or less in Cyclomatic Complexity — start with SqlQueryApply.flatten (cyclomatic 46), QuatMakingBase.inferQuat (cyclomatic 38). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 8.1 to about 8.6/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.

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

D2 · Cognitive Complexity8.0 / 10Strong✓ Tool-verified

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

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

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

11 method(s) exceeded the cognitive complexity threshold of 15; the worst was SqlQueryApply.flatten at 44.

SqlQueryApply.flatten (cognitive 44)quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:204
QuatMakingBase.inferQuat (cognitive 40)quill-core/src/main/scala/zio/quill/quat/QuatMaking.scala:158
ZioJdbcContext.transaction (cognitive 35)quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcContext.scala:192
OrientDBIdiom.orientDBQueryTokenizer (cognitive 32)quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:128
ReifyLiftings.apply (cognitive 25)quill-core/src/main/scala/zio/quill/quotation/ReifyLiftings.scala:83

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

What to do

  1. Bring the 11 bodies over 15 down to 15 or less in Cognitive Complexity — start with SqlQueryApply.flatten (cognitive 44), QuatMakingBase.inferQuat (cognitive 40), ZioJdbcContext.transaction (cognitive 35). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 11 together lifts Cognitive Complexity from 8.0 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.

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

D3 · God Classes8.8 / 10Strong✓ Tool-verified

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

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

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

8 god class(es) detected.

TooManyMethods: SqlIdiom · ×5quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:24
FileTooLong: quotation/Parsing.scala · ×3quill-core/src/main/scala/zio/quill/quotation/Parsing.scala

What to do

  1. Resolve the 5 TooManyMethods finding(s) in God Classes — start with SqlIdiom.scala, DynamicQueryDSL.scala, Parsing.scala. — One of this dimension's main actionable groups (5 warning-level).
  2. Resolve the 3 FileTooLong finding(s) in God Classes — start with Parsing.scala, SqlIdiom.scala, Ast.scala. — One of this dimension's main actionable groups (3 warning-level).

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

D4 · Code Duplication7.3 / 10Strong✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

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

25 duplicated block group(s) detected. 6.8 % of the production lines (1,602 of 23,626) are in a reported copy. A further 33 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (6 lines × 2) · ×8quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:155
Edited copy of a member (6 corresponding lines) · ×4quill-engine/src/main/scala/zio/quill/sql/norm/AddDropToNestedOrderBy.scala:15
Edited copy of a member (5 corresponding lines) · ×4quill-core/src/main/scala/zio/quill/context/mirror/MirrorEncoders.scala:30
Edited copy of a member (7 corresponding lines) · ×3quill-engine/src/main/scala/zio/quill/quotation/FreeVariables.scala:49
Edited copy of a member (17 corresponding lines) · ×2quill-engine/src/main/scala/zio/quill/norm/RepropagateQuats.scala:60

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

What to do

  1. Resolve the 8 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with SqlIdiom.scala (3), StatefulTransformer.scala (2), Encoders.scala. — One of this dimension's main actionable groups (8 warning-level).
  2. Resolve the 4 Edited copy of a member (6 corresponding lines) finding(s) in Code Duplication — start with AddDropToNestedOrderBy.scala, StatefulTransformerWithStack.scala, AsyncMirrorContext.scala. — One of this dimension's main actionable groups (4 warning-level).
  3. Resolve the 4 Edited copy of a member (5 corresponding lines) finding(s) in Code Duplication — start with MirrorEncoders.scala, StatefulTransformer.scala, CassandraPekkoContext.scala. — One of this dimension's main actionable groups (4 warning-level).

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

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

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

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

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

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

17 production modules (sbt), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a dependsOn spread (deps: _*) and a project whose directory a helper computes are not visible there; 0 module(s) off the main sequence, with abstractness counted on 15 of the 17 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

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

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

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

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

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

0 of 26 classes have LCOM4 above 3.

✓ On the Gold path — maintain.

Detailed fixes: d6_recommendation.md.

D12 · Dependency Hygiene9.3 9.0 / 10Strong✓ Tool-verified

What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.

Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.

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

13 outdated direct sbt declarations. 23 of 24 direct declarations were graded against Maven Central (0 not published there, which is what a private Nexus or Artifactory artifact looks like, 1 declaring a version range rather than an exact version). An sbt declaration names an EXACT version, so the remedy is an edit to the build file — there is no lockfile refresh that would move it. Test-, Provided- and it-scoped declarations are excluded, because a consumer of this project never receives them. A version held in a Scala val is read only when the val is one string literal: sbt is a program rather than a manifest, and evaluating a computed version would invent the measurement rather than take it. Whether any artifact is DEPRECATED or ABANDONED is not graded and cannot be — Maven Central publishes no such marker, and release age does not stand in for one: the most widely depended-upon libraries are routinely the stalest, being finished rather than abandoned. Known CVEs in this dependency graph are D30's question.

Outdated: com.github.ben-manes.caffeine:caffeine · ×13

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

D13 · Secret Scanning0.0 / 10Critical✓ Tool-verified

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

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

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

2 secret(s) detected.

REDACTED

What to do

  1. Resolve the 2 Leaked secret finding(s) in Secret Scanning — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).

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

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

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

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

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

0 of 23 declared sbt dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the production coordinates this repository's 2 sbt build file(s) (build.sbt and project/*.scala) declare with a literal version, directly or through a string-literal val — `%%` resolved to the Scala binary suffix Central publishes under, test-scoped declarations excluded — the same declaration-site closure this analysis reads for dependency currency. sbt has no lockfile a checkout carries, so this is deliberately NOT the transitive closure. 3 further production coordinate(s) are declared with a version the build computes rather than writes as a literal — sbt is a program, and this pass does not run it — and are NOT graded: this verdict covers what the build pins literally or through a string-literal val, not the full graph. A further 1 coordinate(s) are not published to Maven Central — another repository (Google's Maven hosts androidx), a SNAPSHOT, or a private artifact — so their licences are not readable from here and they are outside this verdict. ★ COVERAGE OF THIS VERDICT: it grades this repository's sbt dependencies and nothing else. The repository also declares package.json, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.

✓ On the Gold path — maintain.

Detailed fixes: d14_recommendation.md.

D15 · Churn × Complexity Hotspots10.0 / 10Stronggated by 2 serious findings✓ Tool-verified

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

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

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

Top hotspots: quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala (2×26=52); quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala (2×16=32)

Hotspot: quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala · ×2quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:114

What to do

  1. Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with SheathLeafClauses.scala, BetaReduction.scala. — One of this dimension's main actionable groups (2 warning-level).

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

D16 · Bus Factor9.8 / 10Exemplary✓ 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.

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

2 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is quill-engine/src/main/scala/zio/quill/norm/ApplyMap.scala. Counted over 130 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Off-boarding risk: anonymized user #1

✓ On the Gold path — maintain.

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

D17 · Explicit Debt9.8 / 10Stronggated by 30 serious findings✓ Tool-verified

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

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

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

30 deducted task-comment markers across 23626 LoC (0.1/KLoC) → score 9.8. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.

TodoComment · ×28quill-sql-test/src/test/scala/zio/quill/context/sql/norm/SheathLeafClausesSpec.scala:52
HackComment · ×2quill-jdbc-test-sqlserver/src/test/scala/zio/quill/context/jdbc/sqlserver/OptionJdbcSpec.scala:23

What to do

  1. Resolve the 28 TodoComment finding(s) in Explicit Debt — start with SheathLeafClausesSpec.scala (3), Parsing.scala (3), ExpandEntityIdsSpec.scala (2). — One of this dimension's main actionable groups (28 warning-level).
  2. Resolve the 2 HackComment finding(s) in Explicit Debt — start with OptionJdbcSpec.scala, MirrorContexts.scala. — One of this dimension's main actionable groups (2 warning-level).

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

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

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

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

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

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

✓ On the Gold path — maintain.

Detailed fixes: d28_recommendation.md.

D29 · Static Analysis (SAST)1.1 / 10Critical✓ Tool-verified

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

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

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

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

50 finding(s): 0 critical, 50 high, 0 medium, 0 low. 37 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `quill-core/src/main/scala/zio/quill/quotation/Parsing.scala` — so no absence of findings in them is evidence of anything, and nothing in them was analysed. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.

REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (12 issue-level).
  2. Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. No action in Static Analysis (SAST) — all 37 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (37 issue-level, 0 of them charged here).

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

D30 · Dependency Vulnerabilities10.0 / 10Exemplary○ Nothing flagged

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

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

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

No known-vulnerable dependencies in any ecosystem this repository declares.

✓ On the Gold path — maintain.

Detailed fixes: d30_recommendation.md.

D31 · IaC & Container Security5.0 / 10Adequate✓ Tool-verified

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

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

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

27 finding(s): 0 critical, 11 high, 12 medium, 4 low.

REDACTED
REDACTED
REDACTED

What to do

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

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

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

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

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

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

121 of 130 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is quill-core/src/main/scala/zio/quill/quotation/Parsing.scala. Counted over 130 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned file · ×118quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:1
Most significant orphaned file · ×3quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:1
Concentrated knowledge decay

What to do

  1. Resolve the 118 Orphaned file finding(s) in Knowledge Freshness — start with Encoders.scala (3), Decoders.scala (3), Quill.scala (2). — One of this dimension's main actionable groups (118 recommendation-level).
  2. Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with Parsing.scala, SqlIdiom.scala, Ast.scala. — One of this dimension's main actionable groups (3 recommendation-level).
  3. Resolve the 1 Concentrated knowledge decay finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).

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

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

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

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

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

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

Strongest change-coupling: ActionMacro.scala↔QueryMacro.scala 75%

Change coupling: ActionMacro.scala ↔ QueryMacro.scalaquill-core/src/main/scala/zio/quill/context/ActionMacro.scala:1

What to do

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

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

D36 · Supply-chain Provenance & Signing2.5 / 10Weak✓ Tool-verified

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

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

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

1/4 supply-chain integrity signals present (provenance, signing, SBOM, pinned actions).

REDACTED
REDACTED
REDACTED
REDACTED

What to do

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

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

D43 · Malicious Dependencies10.0 / 10Exemplary✓ Tool-verified

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

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

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

No dependency in any ecosystem this repository declares is published as malicious.

✓ On the Gold path — maintain.

Detailed fixes: d43_recommendation.md.

Frontend & cross-cutting dimensions

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

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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

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

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

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

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

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

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

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

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

AX6 · Interface segregation9.8 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `CassandraContext[N]` declares 34 abstract members: `optionDecoder`, `optionEncoder`, `stringDecoder`, `bigDecimalDecoder`, `booleanDecoder`, `byteDecoder`, `shortDecoder`, `intDecoder`, `longDecoder`, `floatDecoder`, `doubleDecoder`, `byteArrayDecoder`, `uuidDecoder`, `timestampDecoder`, `cassandraLocalDateDecoder`, `stringEncoder`, `bigDecimalEncoder`, `booleanEncoder`, `byteEncoder`, `shortEncoder`, `intEncoder`, `longEncoder`, `floatEncoder`, `doubleEncoder`, `byteArrayEncoder`, `uuidEncoder`, `timestampEncoder`, `cassandraLocalDateEncoder`, `listDecoder`, `setDecoder`, `mapDecoder`, `listEncoder`, `setEncoder`, `mapEncoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — quill-cassandra/src/main/scala/zio/quill/context/cassandra/CassandraContext.scala:11
  • `OrientDBContext[Naming]` declares 28 abstract members: `optionDecoder`, `optionEncoder`, `stringDecoder`, `doubleDecoder`, `bigDecimalDecoder`, `booleanDecoder`, `shortDecoder`, `intDecoder`, `longDecoder`, `floatDecoder`, `byteArrayDecoder`, `dateDecoder`, `stringEncoder`, `bigDecimalEncoder`, `booleanEncoder`, `shortEncoder`, `intEncoder`, `longEncoder`, `floatEncoder`, `doubleEncoder`, `dateEncoder`, `byteArrayEncoder`, `listDecoder`, `setDecoder`, `mapDecoder`, `listEncoder`, `setEncoder`, `mapEncoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBContext.scala:9
  • `SqlContext[Idiom, Naming]` declares 29 abstract members: `nullChecker`, `optionDecoder`, `optionEncoder`, `stringDecoder`, `bigDecimalDecoder`, `booleanDecoder`, `byteDecoder`, `shortDecoder`, `intDecoder`, `longDecoder`, `floatDecoder`, `doubleDecoder`, `byteArrayDecoder`, `dateDecoder`, `localDateDecoder`, `uuidDecoder`, `stringEncoder`, `bigDecimalEncoder`, `booleanEncoder`, `byteEncoder`, `shortEncoder`, `intEncoder`, `longEncoder`, `floatEncoder`, `doubleEncoder`, `byteArrayEncoder`, `dateEncoder`, `localDateEncoder`, `uuidEncoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — quill-sql/src/main/scala/zio/quill/context/sql/SqlContext.scala:12
  • `ArrayEncoding` declares 22 abstract members: `arrayStringEncoder`, `arrayBigDecimalEncoder`, `arrayBooleanEncoder`, `arrayByteEncoder`, `arrayShortEncoder`, `arrayIntEncoder`, `arrayLongEncoder`, `arrayFloatEncoder`, `arrayDoubleEncoder`, `arrayDateEncoder`, `arrayLocalDateEncoder`, `arrayStringDecoder`, `arrayBigDecimalDecoder`, `arrayBooleanDecoder`, `arrayByteDecoder`, `arrayShortDecoder`, `arrayIntDecoder`, `arrayLongDecoder`, `arrayFloatDecoder`, `arrayDoubleDecoder`, `arrayDateDecoder`, `arrayLocalDateDecoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — quill-sql/src/main/scala/zio/quill/context/sql/encoding/ArrayEncoding.scala:11

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.

Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.

GD1 · Unfinished & placeholder code10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unreviewed-generation residue in this repository's Scala: methods whose whole body is still `???` or a "not implemented" throw where nothing overrides them, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.

Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.

IC1 · Incompleteness & stubs10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Scala: methods whose body is `???` or only throws a "not implemented" error, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.

Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.

  • A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something. (×37) — quill-core/src/test/scala/zio/quill/util/LogToFileSpec.scala:10, quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:26, quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:39, …

What to do

  • Clear the softer debt: re-enable or delete `ignore`d and `pending` tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace a bare `// scalastyle:off` or `@nowarn` with targeted, justified suppressions.
M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

What to do

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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

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

  • No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

What to do

  • Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure10.0 / 10Exemplary✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

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

M4 · Documentation accuracy10.0 / 10Exemplary○ Nothing flagged

Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.

Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.

P1 · CI/CD gates10.0 / 10Exemplary○ Nothing flagged

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

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

P10 · Library API & versioning10.0 / 10Exemplary○ Nothing flagged

Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.

Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.

P2 · Observability7.0 / 10Strong✓ Tool-verified

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

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

What to do

  • Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
P3 · Security & performance tooling3.0 / 10Weak✓ Tool-verified

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

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

  • No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/auto-approve.yml:7
  • `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list. — .github/dependabot.yml:5

What to do

  • Add a SAST step to CI running what this repository's stack ships: scalafix or scapegoat — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Dependabot is configured but does not watch `npm` — add that `package-ecosystem` entry to .github/dependabot.yml so those dependencies get the same automatic update and advisory pressure as the ones it already covers.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P4 · Deployment & Rollback7.0 / 10Strong✓ Tool-verified

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

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

  • Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.

What to do

  • Add a `healthcheck:` to the served compose service — probing the endpoint it already answers on where it has one — with `depends_on: condition: service_healthy` on whatever waits for it, and keep the deployed image tag immutable and recorded so rolling back is re-pointing at the previous tag rather than rebuilding.
P6 · Release Hygiene10.0 / 10Exemplary✓ Tool-verified

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

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

PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.

Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.

X1 · Async correctness10.0 / 10Exemplary○ Nothing flagged

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

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

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

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

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

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

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

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

X20 · Mistyped argument guard10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.

Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements (or a repository exception type deriving from it) controlled by an `if` — directly or through the `using`, `lock` or `try` that wraps the throw — whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`); in the `else` branch, for a conjunct of the admitting condition that is FALSE of a non-null `p`. Range guards are read for bounds that leave nothing and for a `p > C.Count` bound whose index then reaches `C[p]`, `C.RemoveAt(p)` or a method of the same type that indexes with it. Deterministic, provable per finding. Advisory.

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

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

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

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

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

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

X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged

Other · Code Health — Whether a `for` comprehension or `foreach` leaves the mutable collection it is walking alone — an `ArrayBuffer` or `ListBuffer` counts its changes and its iterator checks the count, an `ArrayDeque` (and `mutable.Queue`/`mutable.Stack`) is walked by index up to its starting length, and a `java.util` collection walked through `asScala` is fail-fast, so a body that adds to or removes from the very collection the loop is walking makes a later step throw `ConcurrentModificationException` (`IndexOutOfBoundsException` for a deque) and the remaining elements are never seen.

Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.

X3 · Exception handling5.9 / 10Adequate✓ Tool-verified

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

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

  • An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. — quill-core/src/main/scala/zio/logging/extensions.scala:82

What to do

  • Swallowed exception (empty catch)
X5 · Nullable reference types2.0 / 10Critical✓ Tool-verified

Other · Code Health — Whether Scala's null is held to the type system and not undermined by assertions — a file compiled with `-Yexplicit-nulls` is one where `String` excludes null and `String | Null` admits it, a file under WartRemover's `Null` wart or Scalafix's `DisableSyntax.noNulls` is one whose code cannot write `null` and must say `Option`, and each `.nn`, `import scala.language.unsafeNulls` or null-lint suppression is the author overruling that.

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

  • No build over this repository's 302 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.

What to do

  • On Scala 3, add `-Yexplicit-nulls` to `scalacOptions` so `String` and `String | Null` mean different things, and type each Java API's result as nullable where it can return null; on Scala 2 (or as a first step), enable WartRemover's `Null` wart (`wartremoverErrors += Wart.Null`) or Scalafix's `DisableSyntax.noNulls = true` so the code holds absence in `Option`. Then pay the assertions down rather than adding to them: each `.nn` is a null the compiler could not rule out — wrap the Java value in `Option(…)` at the boundary, pattern-match on `null` once there, or change the API so the null cannot arrive; an `unsafeNulls` import switches the checking off for everything after it.

Reference — by lens

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

LensScoreRatingImpact
Code Health63%Adequate — gated by X5Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture99%ExemplarySolid.
Maturity52%Adequate — gated by D34, M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness61%Adequate — gated by D13, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security46%Checked 4 of 10Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100%ExemplaryStrongest area.
Not evidenced — 4 control(s) we could not find positive evidence for

These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.

  • C3 Audit Trail — Not assessed: this repository stores data through 'javax.sql.DataSource' (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether its changes need an audit trail could not be established, and the trail's absence is not scored.
  • C4 Data Retention — Not assessed: this repository stores data through 'javax.sql.DataSource' (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether a retention limit applies here could not be established, and its absence is not scored.
  • C5 Data-Subject Rights — Not assessed: this repository stores data through 'javax.sql.DataSource' (quill-jdbc-zio/src/main/scala/zio/quill/ZioJdbcContexts.scala:10) but declares no persisted model this check reads (Slick table columns, CREATE TABLE and ALTER TABLE … ADD columns in SQL migrations). Personal data may be written through raw SQL or a hosted backend, so whether data-subject rights apply here could not be established, and their absence is not scored.
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 66 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 — No web markup found — accessibility is not applicable to this repository.
  • AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
  • AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
  • AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
  • AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
  • AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
  • AX1 Captive dependencies — Not applicable: this repository's Scala imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Scala code is a Play controller, a Cask routes object, a Scalatra servlet, a Finatra controller, an Akka/Pekko HTTP routes holder or a JSR-330/Spring singleton, so no instance is shared between request threads.
  • AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
  • AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • AXR1 Runtime accessibility — compose up failed (exit 17 — an image could not be built) — failed to solve: failed to load cache key: invalid response status 429; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
  • C1 Data Protection — 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.
  • D10 Test Quality — ~41673 lines of test source are present (.scala) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — 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 — the .scala suite was found but not re-run
  • D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
  • D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
  • D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 6 candidate(s) found and not reported.
  • D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
  • D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
  • D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only; comments in this repository's .scala source were not judged.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.scala), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D32 Data Compliance (PII/GDPR) — 1 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
  • D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
  • D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
  • D8 Code Coverage — Coverage not included — suite not readable by the collector
  • DM1 Domain Modelling — applicable but not scored (2 signals for this style, 2 needed — the count is met but a required primary signal is absent): 256 value object(s); 4 domain event(s); its domain events are published by services or handlers — no domain entity raises one
  • ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
  • ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
  • ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
  • P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
  • P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM, JavaScript/TypeScript source, so there is no service whose uptime a failing dependency could take down
  • P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
  • P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — No web surface: 302 Scala file(s) were read for weak hashes and ciphers, key material fixed in the source, disabled TLS certificate validation and obsolete TLS versions, and none was found. This repository serves no HTTP of its own — no HTTP-server artifact (akka-http, pekko-http, http4s, Play, Finagle, zio-http, cask, Scalatra, a tapir server, Jetty, Undertow, …) outside test scope in its build, and no server package imported or server bound in its production source — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker. If this codebase starts serving HTTP, the dimension reactivates automatically.
  • X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X2 Cancellation propagation — no C# was loaded; this repository's Scala was read, and no request in it can be cancelled by a caller — a Scala request takes no token: a Future cannot be cancelled, and cats-effect, ZIO and Monix interrupt the fiber that made the request from outside the call, not through a parameter
  • X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X28 Index access outside its own emptiness guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Scala was read, and it logs through none that an interpolated message defeats: scala-logging takes an `s"…"` message apart into SLF4J's pattern and arguments at compile time, and log4s, grizzled-slf4j, Play's Logger, Akka's LoggingAdapter, sbt's Logger and Spark's Logging take one finished message (as log4net does in C#). Calls made straight through SLF4J (`org.slf4j.Logger`) would be judged.
  • X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.

Appendix A — Findings (grouped)

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

Critical — 63 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • + 12 more in this group — see findings.md.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D31 · IaC & Container Security · High IaC · ×11
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D13 · Secret Scanning · Leaked secret · ×2
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED · ×1
  • REDACTED
Serious — 134 finding(s)
D17 · Explicit Debt · TodoComment · ×28
  • TodoComment quill-sql-test/src/test/scala/zio/quill/context/sql/norm/SheathLeafClausesSpec.scala:52 — // TODO Replace all p.x with p._1 in c then can use this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-sql-test/src/test/scala/zio/quill/context/sql/norm/SheathLeafClausesSpec.scala:67 — // TODO This should actually live the quill-jdbc module and be executed since it should be a working example — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-sql-test/src/test/scala/zio/quill/context/sql/norm/SheathLeafClausesSpec.scala:117 — // TODO star identifiers should not have aliases — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-sql-test/src/test/scala/zio/quill/context/sql/idiom/SqlIdiomSpec.scala:499 — // TODO flatten left flatMaps — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-spark/src/test/scala/zio/quill/context/spark/norm/ExpandEntityIdsSpec.scala:370 — // TODO Ad-Hoc case class union inside for comprehension — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-spark/src/test/scala/zio/quill/context/spark/norm/ExpandEntityIdsSpec.scala:371 — // TODO Tuple union inside for comprehension — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-spark/src/main/scala/zio/quill/context/spark/SparkDialect.scala:119 — // TODO Maybe we should even introduce an exception here because all the support single-value selects have already been enumerated — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcUnderlyingContext.scala:206 — // TODO Assuming chunk size is fetch size. Not sure if this is optimal. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-engine/src/main/scala/zio/quill/MySQLDialect.scala:70 — // TODO Are there situations where you could have invisible properties here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-engine/src/main/scala/zio/quill/SqliteDialect.scala:62 — // TODO Quat.BooleanValue change — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:420 — // TODO Finish describing — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-engine/src/main/scala/zio/quill/sql/norm/SelectPropertyProtractor.scala:168 — // TODO Quat once renames changed to LinkedHashSet change the lookup here to lookup from the hash for better perf — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-engine/src/main/scala/zio/quill/quat/FindBranches.scala:79 — // TODO What about a a top-level branch, what's the text for that? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-engine/src/main/scala/zio/quill/norm/ExpandReturning.scala:62 — // TODO Should propagate ExecutionType from caller of this method. Need to trace — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/test/scala/zio/quill/util/LogToFileSpec.scala:9 — // TODO temporarily ignore this test, will release ZIO2 RC1 without query logging support — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/test/scala/zio/quill/quat/QuatSpec.scala:66 — // TODO Should be Unknown here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:379 — // TODO Verify Quat in what cases does this come up? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:463 — // TODO Check to see that all these conditions work — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:471 — // TODO Verify Quat what is the type of this thing? In what cases does it happen? Do we need to do something more clever with the tree and get a TypeRef? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/main/scala/zio/quill/quotation/Rebind.scala:28 — // TODO Verify Quat — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/main/scala/zio/quill/dsl/DynamicQueryDSL.scala:379 — // TODO Verify Quat Later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/main/scala/zio/quill/dsl/DynamicQueryDSL.scala:380 — // TODO Verify Quat Later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/main/scala/zio/quill/context/ActionMacro.scala:39 — // TODO need to change this to include liftings — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-core/src/main/scala/zio/quill/context/ContextVerbTranslate.scala:106 — // TODO these groups need to have liftings lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • TodoComment quill-codegen/src/main/scala/zio/quill/codegen/model/Typing.scala:8 — // TODO Need to document — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
  • + 3 more in this group — see findings.md.
D31 · IaC & Container Security · Medium IaC · ×12
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×8
  • Duplicated block (6 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:155 — quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:155-160 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:97-102 — 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 `quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:155` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
  • Duplicated block (6 lines × 2) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/Encoders.scala:28 — quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/Encoders.scala:28-33 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/encoding/Encoders.scala:29-34 — 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 (6 lines × 2) quill-core/src/main/scala/zio/quill/quat/QuatMacro.scala:10 — quill-core/src/main/scala/zio/quill/quat/QuatMacro.scala:10-15 | quill-core/src/main/scala/zio/quill/quotation/Quotation.scala:90-95 — 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 (6 lines × 2) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:305 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:305-310 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:321-326 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:313 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:313-318 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:329-334 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
  • Duplicated block (6 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:770 — quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:770-775 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:382-387 — 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 (6 lines × 2) quill-jdbc-zio/src/main/scala/zio/quill/context/ZioJdbc.scala:73 — quill-jdbc-zio/src/main/scala/zio/quill/context/ZioJdbc.scala:73-78 | quill-jdbc-zio/src/main/scala/zio/quill/jdbczio/Quill.scala:143-148 — 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 (6 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:349 — quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:349-354 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:197-202 — 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 `quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:349` 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.
D3 · God Classes · TooManyMethods · ×5
  • TooManyMethods: SqlIdiom quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:24 — TooManyMethods — 47 methods. The bar is 30 methods; this is 17 over it, 1.57× the bar. 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: DynamicQuery quill-core/src/main/scala/zio/quill/dsl/DynamicQueryDSL.scala:194 — TooManyMethods — 38 methods. The bar is 30 methods; this is 8 over it, 1.27× the bar. 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: Parsing quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:23 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. 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: Query quill-engine/src/main/scala/zio/quill/Model.scala:15 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. 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: Messages quill-engine/src/main/scala/zio/quill/util/Messages.scala:6 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.10× the bar. 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.
D4 · Code Duplication · Edited copy of a member (6 corresponding lines) · ×4
  • Edited copy of a member (6 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/norm/AddDropToNestedOrderBy.scala:15 — quill-engine/src/main/scala/zio/quill/sql/norm/AddDropToNestedOrderBy.scala:15-25 | quill-engine/src/main/scala/zio/quill/sql/norm/AddDropToNestedOrderBy.scala:36-41 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:238 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:238-243 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:246-251 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala:136 — quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala:136-143 | quill-core/src/main/scala/zio/quill/MirrorContext.scala:130-135 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (6 corresponding lines) quill-core/src/main/scala/zio/quill/context/ContextVerbTranslate.scala:119 — quill-core/src/main/scala/zio/quill/context/ContextVerbTranslate.scala:119-124 | quill-engine/src/main/scala/zio/quill/util/ContextLogger.scala:44-49 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×4
  • Edited copy of a member (5 corresponding lines) quill-core/src/main/scala/zio/quill/context/mirror/MirrorEncoders.scala:30 — quill-core/src/main/scala/zio/quill/context/mirror/MirrorEncoders.scala:30-35 | quill-spark/src/main/scala/zio/quill/context/spark/Encoders.scala:20-24 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:238 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:238-242 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:254-258 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala:96 — quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala:96-101 | quill-cassandra/src/main/scala/zio/quill/CassandraAsyncContext.scala:67-71 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (5 corresponding lines) quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala:73 — quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala:73-78 | quill-jdbc/src/main/scala/zio/quill/context/jdbc/SimplifiedContexts.scala:119-123 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D3 · God Classes · FileTooLong · ×3
  • FileTooLong: quotation/Parsing.scala quill-core/src/main/scala/zio/quill/quotation/Parsing.scala — FileTooLong — 854 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 354 over it, 1.71× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: idiom/SqlIdiom.scala quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala — FileTooLong — 614 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 114 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
  • FileTooLong: ast/Ast.scala quill-engine/src/main/scala/zio/quill/ast/Ast.scala — FileTooLong — 602 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 102 over it, 1.20× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×3
  • Edited copy of a member (7 corresponding lines) quill-engine/src/main/scala/zio/quill/quotation/FreeVariables.scala:49 — quill-engine/src/main/scala/zio/quill/quotation/FreeVariables.scala:49-55 | quill-engine/src/main/scala/zio/quill/quotation/FreeVariables.scala:58-67 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:544 — quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:544-550 | quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:553-559 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (7 corresponding lines) quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala:149 — quill-core/src/main/scala/zio/quill/AsyncMirrorContext.scala:149-157 | quill-core/src/main/scala/zio/quill/MirrorContext.scala:141-147 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D15 · Churn × Complexity Hotspots · Hotspot · ×2
  • Hotspot: quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:114 — quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 26 in SheathLeafClauses.apply at line 114. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 00:36:59 +00:00' --until='2026-11-10 00:36:59 +00:00' --full-history --no-merges -- quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
  • Hotspot: quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala:44 — quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in BetaReduction.apply at line 44. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-12..2026-11-10, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-12 00:36:59 +00:00' --until='2026-11-10 00:36:59 +00:00' --full-history --no-merges -- quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D17 · Explicit Debt · HackComment · ×2
  • HackComment quill-jdbc-test-sqlserver/src/test/scala/zio/quill/context/jdbc/sqlserver/OptionJdbcSpec.scala:23 — // Hack because Quill does not have correct SQL Server infix concatenation. See issue #1054 for more info. — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
  • HackComment quill-core/src/test/scala/zio/quill/MirrorContexts.scala:11 — // hack to avoid Await.result since scala.js doesn't support it — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D4 · Code Duplication · Edited copy of a member (17 corresponding lines) · ×2
  • Edited copy of a member (17 corresponding lines) quill-engine/src/main/scala/zio/quill/norm/RepropagateQuats.scala:60 — quill-engine/src/main/scala/zio/quill/norm/RepropagateQuats.scala:60-76 | quill-engine/src/main/scala/zio/quill/quat/Quat.scala:268-286 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (17 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:163 — quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:163-179 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:105-121 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×2
  • Edited copy of a member (11 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:260 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:260-270 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:276-286 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (11 corresponding lines) quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala:40 — quill-cassandra-pekko/src/main/scala/zio/quill/CassandraPekkoContext.scala:40-50 | quill-cassandra/src/main/scala/zio/quill/context/Caches.scala:21-32 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (10 corresponding lines) · ×2
  • Edited copy of a member (10 corresponding lines) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:58 — quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:58-67 | quill-jdbc-zio/src/main/scala-2.13/zio/quill/context/json/PostgresJsonExtensions.scala:58-67 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (10 corresponding lines) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:28 — quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:28-37 | quill-jdbc-zio/src/main/scala-2.13/zio/quill/context/json/PostgresJsonExtensions.scala:28-37 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (4 corresponding lines) · ×2
  • Edited copy of a member (4 corresponding lines) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:224 — quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:224-227 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:376-379 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
  • Edited copy of a member (4 corresponding lines) quill-engine/src/main/scala/zio/quill/PostgresDialect.scala:36 — quill-engine/src/main/scala/zio/quill/PostgresDialect.scala:36-40 | quill-engine/src/main/scala/zio/quill/SqliteDialect.scala:31-34 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Duplicated block (11 lines × 2) · ×2
  • Duplicated block (11 lines × 2) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:40 — quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:40-50 | quill-jdbc-zio/src/main/scala-2.13/zio/quill/context/json/PostgresJsonExtensions.scala:40-50 — before extracting anything, compare `quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala` and `quill-jdbc-zio/src/main/scala-2.13/zio/quill/context/json/PostgresJsonExtensions.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
  • Duplicated block (11 lines × 2) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:75 — quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:75-85 | quill-jdbc-zio/src/main/scala-2.13/zio/quill/context/json/PostgresJsonExtensions.scala:75-85 — before extracting anything, compare `quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala` and `quill-jdbc-zio/src/main/scala-2.13/zio/quill/context/json/PostgresJsonExtensions.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×2
  • Duplicated block (8 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:554 — quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:554-561 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:300-307 — 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 (8 lines × 2) quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:60 — quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:60-67 | quill-jdbc-zio/src/main/scala-2.13/zio/quill/context/json/PostgresJsonExtensions.scala:60-67 — before extracting anything, compare `quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala` and `quill-jdbc-zio/src/main/scala-2.13/zio/quill/context/json/PostgresJsonExtensions.scala` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 30 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `quill-jdbc-zio/src/main/scala-2.12/zio/quill/context/json/PostgresJsonExtensions.scala:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×2
  • Duplicated block (7 lines × 2) quill-cassandra/src/main/scala/zio/quill/CassandraMirrorContext.scala:22 — quill-cassandra/src/main/scala/zio/quill/CassandraMirrorContext.scala:22-40 | quill-orientdb/src/main/scala/zio/quill/OrientDBMirrorContext.scala:9-15 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (7 lines × 2) quill-core/src/main/scala/zio/quill/util/ExceptionOps.scala:7 — quill-core/src/main/scala/zio/quill/util/ExceptionOps.scala:7-13 | quill-util/src/main/scala/zio/quill/util/ThrowableOps.scala:7-13 — 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.
D1 · Cyclomatic Complexity · SqlQueryApply.flatten (cyclomatic 46) · ×1
  • SqlQueryApply.flatten (cyclomatic 46) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:204 — SqlQueryApply.flatten has cyclomatic complexity 46 (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.
D1 · Cyclomatic Complexity · QuatMakingBase.inferQuat (cyclomatic 38) · ×1
  • QuatMakingBase.inferQuat (cyclomatic 38) quill-core/src/main/scala/zio/quill/quat/QuatMaking.scala:158 — QuatMakingBase.inferQuat has cyclomatic complexity 38 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
D1 · Cyclomatic Complexity · SheathLeafClauses.apply (cyclomatic 26) · ×1
  • SheathLeafClauses.apply (cyclomatic 26) quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:114 — SheathLeafClauses.apply has cyclomatic complexity 26 (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.
D1 · Cyclomatic Complexity · NormalizeNestedStructures.unapply (cyclomatic 22) · ×1
  • NormalizeNestedStructures.unapply (cyclomatic 22) quill-engine/src/main/scala/zio/quill/norm/NormalizeNestedStructures.scala:7 — NormalizeNestedStructures.unapply has cyclomatic complexity 22 (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.
D1 · Cyclomatic Complexity · SqlIdiom.actionTokenizer (cyclomatic 21) · ×1
  • SqlIdiom.actionTokenizer (cyclomatic 21) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:654 — SqlIdiom.actionTokenizer has cyclomatic complexity 21 (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.
D1 · Cyclomatic Complexity · OrientDBIdiom.orientDBQueryTokenizer (cyclomatic 21) · ×1
  • OrientDBIdiom.orientDBQueryTokenizer (cyclomatic 21) quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:128 — OrientDBIdiom.orientDBQueryTokenizer has cyclomatic complexity 21 (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.
D1 · Cyclomatic Complexity · ReifyLiftings.apply (cyclomatic 19) · ×1
  • ReifyLiftings.apply (cyclomatic 19) quill-core/src/main/scala/zio/quill/quotation/ReifyLiftings.scala:83 — ReifyLiftings.apply has cyclomatic complexity 19 (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.
D1 · Cyclomatic Complexity · AstPrinter.treeify (cyclomatic 19) · ×1
  • AstPrinter.treeify (cyclomatic 19) quill-engine/src/main/scala/zio/quill/AstPrinter.scala:90 — AstPrinter.treeify 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.
D1 · Cyclomatic Complexity · BetaReduction.apply (cyclomatic 16) · ×1
  • BetaReduction.apply (cyclomatic 16) quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala:44 — BetaReduction.apply has cyclomatic complexity 16 (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.
D2 · Cognitive Complexity · SqlQueryApply.flatten (cognitive 44) · ×1
  • SqlQueryApply.flatten (cognitive 44) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:204 — SqlQueryApply.flatten has cognitive complexity 44 (threshold 15). Drivers by points: if/else 19 (26 pts), match/switch 7 (12 pts), boolean chains 6 (nesting depth added 12). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · QuatMakingBase.inferQuat (cognitive 40) · ×1
  • QuatMakingBase.inferQuat (cognitive 40) quill-core/src/main/scala/zio/quill/quat/QuatMaking.scala:158 — QuatMakingBase.inferQuat has cognitive complexity 40 (threshold 15). Drivers by points: if/else 25, match/switch 6 (8 pts), boolean chains 7 (nesting depth added 2). 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.
D2 · Cognitive Complexity · ZioJdbcContext.transaction (cognitive 35) · ×1
  • ZioJdbcContext.transaction (cognitive 35) quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcContext.scala:192 — ZioJdbcContext.transaction has cognitive complexity 35 (threshold 15). Drivers by points: loops 6 (27 pts), match/switch 2 (8 pts) (nesting depth added 27). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · OrientDBIdiom.orientDBQueryTokenizer (cognitive 32) · ×1
  • OrientDBIdiom.orientDBQueryTokenizer (cognitive 32) quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:128 — OrientDBIdiom.orientDBQueryTokenizer has cognitive complexity 32 (threshold 15). Drivers by points: if/else 11 (16 pts), match/switch 8 (16 pts) (nesting depth added 13). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ReifyLiftings.apply (cognitive 25) · ×1
  • ReifyLiftings.apply (cognitive 25) quill-core/src/main/scala/zio/quill/quotation/ReifyLiftings.scala:83 — ReifyLiftings.apply has cognitive complexity 25 (threshold 15). Drivers by points: match/switch 9 (18 pts), if/else 7 (nesting depth added 9). 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · AstPrinter.treeify (cognitive 24) · ×1
  • AstPrinter.treeify (cognitive 24) quill-engine/src/main/scala/zio/quill/AstPrinter.scala:90 — AstPrinter.treeify has cognitive complexity 24 (threshold 15). Drivers by points: if/else 14 (20 pts), match/switch 2 (4 pts) (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · Parsing.combinedInfixParser (cognitive 23) · ×1
  • Parsing.combinedInfixParser (cognitive 23) quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:394 — Parsing.combinedInfixParser has cognitive complexity 23 (threshold 15). Drivers by points: match/switch 5 (13 pts), if/else 6 (10 pts) (nesting depth added 12). 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · SheathLeafClauses.apply (cognitive 22) · ×1
  • SheathLeafClauses.apply (cognitive 22) quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:114 — SheathLeafClauses.apply has cognitive complexity 22 (threshold 15). Drivers by points: match/switch 8 (14 pts), if/else 7 (8 pts) (nesting depth added 7). 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · InsertReturnCapabilityExtension.verifyAst (cognitive 18) · ×1
  • InsertReturnCapabilityExtension.verifyAst (cognitive 18) quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:964 — InsertReturnCapabilityExtension.verifyAst has cognitive complexity 18 (threshold 15). Drivers by points: match/switch 6 (13 pts), if/else 5 (nesting depth added 7). 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D2 · Cognitive Complexity · ZioJdbcUnderlyingContext.streamQuery (cognitive 18) · ×1
  • ZioJdbcUnderlyingContext.streamQuery (cognitive 18) quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcUnderlyingContext.scala:175 — ZioJdbcUnderlyingContext.streamQuery has cognitive complexity 18 (threshold 15). Drivers by points: loops 6 (16 pts), match/switch 1 (2 pts) (nesting depth added 11). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
D2 · Cognitive Complexity · SeedRenames.apply (cognitive 17) · ×1
  • SeedRenames.apply (cognitive 17) quill-engine/src/main/scala/zio/quill/norm/RenameProperties.scala:119 — SeedRenames.apply has cognitive complexity 17 (threshold 15). Drivers by points: match/switch 4 (9 pts), if/else 5 (7 pts), boolean chains 1 (nesting depth added 7). 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. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
D35 · Change Coupling · Change coupling · ×1
  • Change coupling: ActionMacro.scala ↔ QueryMacro.scala quill-core/src/main/scala/zio/quill/context/ActionMacro.scala:1 — `quill-core/src/main/scala/zio/quill/context/ActionMacro.scala` and `quill-core/src/main/scala/zio/quill/context/QueryMacro.scala` change together 75% of the time (12 of the 16 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). 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. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `87bcdb2b` Improve translate function. Make contexts more lazy. (#3146) (at that commit the files were still `quill-core/src/main/scala/io/getquill/context/ActionMacro.scala` and `quill-core/src/main/scala/io/getquill/context/QueryMacro.scala`); `3c97b8de` Pretty printing for SQL Dialects (at that commit the files were still `quill-core/src/main/scala/io/getquill/context/ActionMacro.scala` and `quill-core/src/main/scala/io/getquill/context/QueryMacro.scala`); `6a50fff2` Refactor method names for consistency (at that commit the files were still `quill-core/src/main/scala/io/getquill/context/ActionMacro.scala` and `quill-core/src/main/scala/io/getquill/context/QueryMacro.scala`) — run `git show` on any of them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Edited copy of a member (70 corresponding lines) · ×1
  • Edited copy of a member (70 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:150 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:150-219 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:166-235 — These two members are one piece of code written twice and then edited apart: 70 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (75 corresponding lines) · ×1
  • Edited copy of a member (75 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:57 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:57-131 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:73-147 — These two members are one piece of code written twice and then edited apart: 75 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (47 corresponding lines) · ×1
  • Edited copy of a member (47 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:8 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:8-54 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:24-70 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (30 corresponding lines) · ×1
  • Edited copy of a member (30 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:273 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:273-302 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:289-318 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (56 corresponding lines) · ×1
  • Edited copy of a member (56 corresponding lines) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:81 — quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:81-136 | quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:138-200 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×1
  • Edited copy of a member (22 corresponding lines) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:44 — quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:44-65 | quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:129-160 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (36 corresponding lines) · ×1
  • Edited copy of a member (36 corresponding lines) quill-engine/src/main/scala/zio/quill/norm/AdHocReduction.scala:16 — quill-engine/src/main/scala/zio/quill/norm/AdHocReduction.scala:16-51 | quill-engine/src/main/scala/zio/quill/norm/SymbolicReduction.scala:20-70 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×1
  • Edited copy of a member (14 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:134 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:134-147 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:150-163 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (13 corresponding lines) · ×1
  • Edited copy of a member (13 corresponding lines) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:245 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:245-257 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:261-273 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (18 corresponding lines) · ×1
  • Edited copy of a member (18 corresponding lines) quill-core/src/main/scala/zio/quill/quotation/TranspileConfigSummoning.scala:29 — quill-core/src/main/scala/zio/quill/quotation/TranspileConfigSummoning.scala:29-46 | quill-core/src/main/scala/zio/quill/quotation/TranspileConfigSummoning.scala:48-65 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×1
  • Edited copy of a member (9 corresponding lines) quill-engine/src/main/scala/zio/quill/sql/norm/ExpandNestedQueries.scala:193 — quill-engine/src/main/scala/zio/quill/sql/norm/ExpandNestedQueries.scala:193-206 | quill-engine/src/main/scala/zio/quill/sql/norm/StatelessQueryTransformer.scala:49-57 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×1
  • Edited copy of a member (19 corresponding lines) quill-codegen-jdbc/src/main/scala/zio/quill/codegen/jdbc/gen/DefaultJdbcSchemaReader.scala:33 — quill-codegen-jdbc/src/main/scala/zio/quill/codegen/jdbc/gen/DefaultJdbcSchemaReader.scala:33-54 | quill-codegen-jdbc/src/main/scala/zio/quill/codegen/jdbc/gen/DefaultJdbcSchemaReader.scala:56-74 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 13+ corresponding lines) quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala:105 — quill-jdbc/src/main/scala/zio/quill/context/jdbc/JdbcContextVerbExecute.scala:105-117 | quill-jdbc/src/main/scala/zio/quill/context/jdbc/SimplifiedContexts.scala:90-106 | quill-jdbc/src/main/scala/zio/quill/context/jdbc/SimplifiedContexts.scala:129-159 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 4+ corresponding lines) quill-engine/src/main/scala/zio/quill/MySQLDialect.scala:86 — quill-engine/src/main/scala/zio/quill/MySQLDialect.scala:86-89 | quill-engine/src/main/scala/zio/quill/OracleDialect.scala:71-74 | quill-engine/src/main/scala/zio/quill/SQLServerDialect.scala:67-70 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (73–74 lines × 2) · ×1
  • Duplicated block (73–74 lines × 2) quill-core/src/main/scala/zio/quill/context/QueryMacro.scala:60 — quill-core/src/main/scala/zio/quill/context/QueryMacro.scala:60-133 | quill-core/src/main/scala/zio/quill/context/QueryMacro.scala:141-213 — 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 `quill-core/src/main/scala/zio/quill/context/QueryMacro.scala:60` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (13–23 lines × 2) · ×1
  • Duplicated block (13–23 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:141 — quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:141-153 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:74-96 — 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. 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×1
  • Duplicated block (19 lines × 2) quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:165 — quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:165-183 | quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:207-225 — 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×1
  • Duplicated block (15 lines × 2) quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:110 — quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:110-124 | quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:171-185 — 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 `quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:110` 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 first that the copies are not typed on the same thing: the declarations holding them bind `tpe` to `Type) = q"$mapper: $encoding.CassandraMapper[$absType` in one and `Type) = q"$mapper: $encoding.CassandraMapper[$tpe` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
D4 · Code Duplication · Duplicated block (14–15 lines × 2) · ×1
  • Duplicated block (14–15 lines × 2) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:10 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:10-24 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:26-39 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:10` 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.
D4 · Code Duplication · Duplicated block (14 lines × 2) · ×1
  • Duplicated block (14 lines × 2) quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:164 — quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:164-177 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:106-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication · Duplicated block (25–26 lines × 2) · ×1
  • Duplicated block (25–26 lines × 2) quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:27 — quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:27-52 | quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:101-125 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
D4 · Code Duplication · Duplicated block (7–10 lines × 2) · ×1
  • Duplicated block (7–10 lines × 2) quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:318 — quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:318-327 | quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:350-356 — 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 `quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:350` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×1
  • Duplicated block (10 lines × 2) quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:58 — quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:58-67 | quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:186-195 — 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 `quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:58` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×1
  • Duplicated block (7 lines × 3) quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:8 — quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:8-14 | quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:24-30 | quill-engine/src/main/scala/zio/quill/ast/StatelessTransformer.scala:8-14 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:8` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×1
  • Duplicated block (5 lines × 3) quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:155 — quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:155-159 | quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:564-568 | quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:313-317 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:155` 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.
X3 · Exception handling · Swallowed exception (empty catch) · ×1
  • Swallowed exception (empty catch) quill-core/src/main/scala/zio/logging/extensions.scala:82 — An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Minor — 176 finding(s)
D34 · Knowledge Freshness · Orphaned file · ×118
  • Orphaned file quill-engine/src/main/scala/zio/quill/sql/SqlQuery.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/quat/Quat.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/norm/SheathLeafClauses.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-core/src/main/scala/zio/quill/context/ActionMacro.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/MirrorIdiom.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBIdiom.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/util/Using.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-core/src/main/scala/zio/quill/quotation/Liftables.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-core/src/main/scala/zio/quill/quat/QuatMaking.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/norm/capture/AvoidAliasConflict.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/ast/StatefulTransformerWithStack.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/norm/BetaReduction.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcContext.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/util/Messages.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/ast/StatefulTransformer.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/context/cassandra/CqlIdiom.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/sql/norm/SelectPropertyProtractor.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-codegen/src/main/scala/zio/quill/codegen/gen/Generator.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-jdbc-zio/src/main/scala/zio/quill/context/qzio/ZioJdbcUnderlyingContext.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-core/src/main/scala/zio/quill/context/QueryMacro.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-cassandra/src/main/scala/zio/quill/context/cassandra/encoding/UdtEncodingMacro.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/idiom/ReifyStatement.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-spark/src/main/scala/zio/quill/context/spark/SparkDialect.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/norm/RepropagateQuats.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • Orphaned file quill-engine/src/main/scala/zio/quill/quat/FindBranches.scala:1 — No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
  • + 93 more in this group — see findings.md.
IC1 · Incompleteness & stubs · Disabled test · ×37
  • Disabled test quill-core/src/test/scala/zio/quill/util/LogToFileSpec.scala:10 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:26 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:39 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:46 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-h2/src/test/scala/zio/quill/context/jdbc/h2/PeopleJdbcReturningSpec.scala:53 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-mysql/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:26 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-mysql/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:39 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-mysql/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:46 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-mysql/src/test/scala/zio/quill/context/jdbc/mysql/PeopleJdbcReturningSpec.scala:53 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-oracle/src/test/scala/zio/quill/context/jdbc/oracle/JdbcContextSpec.scala:88 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-oracle/src/test/scala/zio/quill/context/jdbc/oracle/PeopleJdbcReturningSpec.scala:38 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-oracle/src/test/scala/zio/quill/context/jdbc/oracle/PeopleJdbcReturningSpec.scala:45 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-oracle/src/test/scala/zio/quill/context/jdbc/oracle/PeopleJdbcReturningSpec.scala:52 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-sqlite/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:26 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-sqlite/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:39 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-sqlite/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:46 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-sqlite/src/test/scala/zio/quill/context/jdbc/sqlite/PeopleJdbcReturningSpec.scala:53 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-test-sqlserver/src/test/scala/zio/quill/context/jdbc/sqlserver/PeopleJdbcReturningSpec.scala:50 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:29 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:46 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:56 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-zio/src/test/scala/zio/quill/h2/PeopleZioReturningSpec.scala:66 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-zio/src/test/scala/zio/quill/mysql/PeopleZioReturningSpec.scala:29 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-zio/src/test/scala/zio/quill/mysql/PeopleZioReturningSpec.scala:46 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • Disabled test quill-jdbc-zio/src/test/scala/zio/quill/mysql/PeopleZioReturningSpec.scala:56 — A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
  • + 12 more in this group — see findings.md.
AX6 · Interface segregation · Fat interface · ×4
  • Fat interface: CassandraContext[N] (34 abstract members) quill-cassandra/src/main/scala/zio/quill/context/cassandra/CassandraContext.scala:11 — `CassandraContext[N]` declares 34 abstract members: `optionDecoder`, `optionEncoder`, `stringDecoder`, `bigDecimalDecoder`, `booleanDecoder`, `byteDecoder`, `shortDecoder`, `intDecoder`, `longDecoder`, `floatDecoder`, `doubleDecoder`, `byteArrayDecoder`, `uuidDecoder`, `timestampDecoder`, `cassandraLocalDateDecoder`, `stringEncoder`, `bigDecimalEncoder`, `booleanEncoder`, `byteEncoder`, `shortEncoder`, `intEncoder`, `longEncoder`, `floatEncoder`, `doubleEncoder`, `byteArrayEncoder`, `uuidEncoder`, `timestampEncoder`, `cassandraLocalDateEncoder`, `listDecoder`, `setDecoder`, `mapDecoder`, `listEncoder`, `setEncoder`, `mapEncoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: OrientDBContext[Naming] (28 abstract members) quill-orientdb/src/main/scala/zio/quill/context/orientdb/OrientDBContext.scala:9 — `OrientDBContext[Naming]` declares 28 abstract members: `optionDecoder`, `optionEncoder`, `stringDecoder`, `doubleDecoder`, `bigDecimalDecoder`, `booleanDecoder`, `shortDecoder`, `intDecoder`, `longDecoder`, `floatDecoder`, `byteArrayDecoder`, `dateDecoder`, `stringEncoder`, `bigDecimalEncoder`, `booleanEncoder`, `shortEncoder`, `intEncoder`, `longEncoder`, `floatEncoder`, `doubleEncoder`, `dateEncoder`, `byteArrayEncoder`, `listDecoder`, `setDecoder`, `mapDecoder`, `listEncoder`, `setEncoder`, `mapEncoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: SqlContext[Idiom, Naming] (29 abstract members) quill-sql/src/main/scala/zio/quill/context/sql/SqlContext.scala:12 — `SqlContext[Idiom, Naming]` declares 29 abstract members: `nullChecker`, `optionDecoder`, `optionEncoder`, `stringDecoder`, `bigDecimalDecoder`, `booleanDecoder`, `byteDecoder`, `shortDecoder`, `intDecoder`, `longDecoder`, `floatDecoder`, `doubleDecoder`, `byteArrayDecoder`, `dateDecoder`, `localDateDecoder`, `uuidDecoder`, `stringEncoder`, `bigDecimalEncoder`, `booleanEncoder`, `byteEncoder`, `shortEncoder`, `intEncoder`, `longEncoder`, `floatEncoder`, `doubleEncoder`, `byteArrayEncoder`, `dateEncoder`, `localDateEncoder`, `uuidEncoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: ArrayEncoding (22 abstract members) quill-sql/src/main/scala/zio/quill/context/sql/encoding/ArrayEncoding.scala:11 — `ArrayEncoding` declares 22 abstract members: `arrayStringEncoder`, `arrayBigDecimalEncoder`, `arrayBooleanEncoder`, `arrayByteEncoder`, `arrayShortEncoder`, `arrayIntEncoder`, `arrayLongEncoder`, `arrayFloatEncoder`, `arrayDoubleEncoder`, `arrayDateEncoder`, `arrayLocalDateEncoder`, `arrayStringDecoder`, `arrayBigDecimalDecoder`, `arrayBooleanDecoder`, `arrayByteDecoder`, `arrayShortDecoder`, `arrayIntDecoder`, `arrayLongDecoder`, `arrayFloatDecoder`, `arrayDoubleDecoder`, `arrayDateDecoder`, `arrayLocalDateDecoder`. Counted over its ABSTRACT members — a `def` with no body or a `val`/`var` with no initializer, once per signature; concrete members, private and protected members, and members of a companion `object` are not counted, because no implementer is forced to write them. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
D31 · IaC & Container Security · Low IaC · ×4
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Most significant orphaned file · ×3
  • Most significant orphaned file quill-core/src/main/scala/zio/quill/quotation/Parsing.scala:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file quill-engine/src/main/scala/zio/quill/sql/idiom/SqlIdiom.scala:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
  • Most significant orphaned file quill-engine/src/main/scala/zio/quill/ast/Ast.scala:1 — One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 2 significant file(s) lose their only recent owner: quill-engine/src/main/scala/zio/quill/norm/ApplyMap.scala, quill-engine/src/main/scala/zio/quill/sql/norm/ExpandNestedQueries.scala. Pair on, review, or document these before any departure.
D34 · Knowledge Freshness · Concentrated knowledge decay · ×1
  • Concentrated knowledge decay — 121 of 130 significant files have no living knowledge, while the repository is still being changed at a low rate (29 commit(s) in the last 90 days) — so this is one repo-wide knowledge-decay state, not 121 separate risks. Counted over 130 of the 305 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. The code moved on without the people who understood these files: document them or schedule a read-through before the next change lands in them.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
M2 · Architecture documentation · No ADRs · ×1
  • No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST .github/workflows/auto-approve.yml:7 — No static application security testing detected. For this repository's stack, add scalafix or scapegoat (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 6 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P3 · Security & performance tooling · Dependabot does not watch npm · ×1
  • Dependabot does not watch npm .github/dependabot.yml:5 — `.github/dependabot.yml` schedules updates, but no `package-ecosystem` entry covers `npm`, which this tree depends on — so those dependencies get no update pull requests and no advisory pressure, however complete the dep-scan credit looks. Add the missing entry to the `updates:` list.
P4 · Deployment & Rollback · No rollback/health safety · ×1
  • No rollback/health safety — Deployment is orchestrated by compose, but no service declares a `healthcheck:` and nothing pins a previous image to fall back to — the runtime can tell that the container is up, not that it is serving, so a bad release is harder to detect and reverse.
X5 · Nullable reference types · Scala's null is not held to the type system everywhere · ×1
  • Scala's null is not held to the type system everywhere — No build over this repository's 302 Scala product file(s) passes `-Yexplicit-nulls`, enables WartRemover's `Null` wart or runs Scalafix's `DisableSyntax.noNulls`, so every reference type admits null and nothing reports a `null` written into the code or returned from a Java API — the first one to reach a method call is a `NullPointerException`. `Option` by convention is a habit no tool here holds the code to.
Minor — 13 finding(s)
D12 · Dependency Hygiene · Outdated · ×13
  • Outdated: com.github.ben-manes.caffeine:caffeine — `com.github.ben-manes.caffeine %% caffeine` is declared at 3.2.2 in build.sbt, but 3.3.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.2.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.lihaoyi:fansi_2.13 — `com.lihaoyi %% fansi_2.13` is declared at 0.3.0 in build.sbt, but 0.5.1 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.3.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.lihaoyi:pprint_2.13 — `com.lihaoyi %% pprint_2.13` is declared at 0.9.3 in build.sbt, but 0.9.6 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.9.3 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: com.lihaoyi:sourcecode_2.13 — `com.lihaoyi %% sourcecode_2.13` is declared at 0.3.0 in build.sbt, but 0.4.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.3.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: dev.zio:zio-json_2.13 — `dev.zio %% zio-json_2.13` is declared at 0.7.44 in build.sbt, but 1.1.2 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 0.7.44 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: dev.zio:zio-logging_2.13 — `dev.zio %% zio-logging_2.13` is declared at 2.5.1 in build.sbt, but 2.5.4 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.5.1 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: dev.zio:zio-streams_2.13 — `dev.zio %% zio-streams_2.13` is declared at 2.1.20 in build.sbt, but 2.1.27 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.1.20 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: dev.zio:zio_2.13 — `dev.zio %% zio_2.13` is declared at 2.1.20 in build.sbt, but 2.1.27 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.1.20 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.apache.pekko:pekko-connectors-cassandra_2.13 — `org.apache.pekko %% pekko-connectors-cassandra_2.13` is declared at 1.0.2 in build.sbt, but 1.3.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.0.2 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.apache.spark:spark-sql_2.13 — `org.apache.spark %% spark-sql_2.13` is declared at 3.4.0 in build.sbt, but 4.3.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.4.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.scala-lang.modules:scala-collection-compat_2.13 — `org.scala-lang.modules %% scala-collection-compat_2.13` is declared at 2.13.0 in build.sbt, but 2.14.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 2.13.0 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.scala-lang.modules:scala-parallel-collections_2.13 — `org.scala-lang.modules %% scala-parallel-collections_2.13` is declared at 1.0.4 in build.sbt, but 1.3.0 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 1.0.4 until the declaration is edited — there is no lockfile refresh that would move it.
  • Outdated: org.scalameta:scalafmt-core_2.13 — `org.scalameta %% scalafmt-core_2.13` is declared at 3.9.10 in build.sbt, but 3.11.5 is the current release on Maven Central. An sbt declaration names an exact version, so this repository builds against 3.9.10 until the declaration is edited — there is no lockfile refresh that would move it.

Appendix B — Reproduction & audit trail

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

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-42c012bd62404475a90d48f528fe788c/history.json --exit-code 0 --source .0artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-42c012bd62404475a90d48f528fe788c/tree.json --exit-code 0 --source .0artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt .50artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json
D31 · IaC & Container Securitytrivy—trivy config --format json --quiet .27artifacts/raw/trivy-config.json
D32 · Data Compliance (PII/GDPR)semgrep—semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 1 file(s) — `quill-core/src/main/scala/zio/quill/quotation/Parsing.scala` — so the PII/GDPR sweep did not cover them at all.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.0—
D41 · Kernel & Syscall Confinementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.0—
D42 · Runtime Threat Enforcementruntime-hardening—runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.0—
D43 · Malicious Dependenciestrivy—trivy fs --scanners vuln --format json --quiet --severity CRITICAL,HIGH,MEDIUM,LOW --skip-dirs **/bin/** --skip-dirs **/obj/** .0artifacts/raw/trivy-fs.json

Run 01a1d8de-32c4-75d7-8231-c0acbc95a0af · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

Downloadable artifacts

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

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