Public report of realm/realm-java, published 16 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 reportMeasured 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, 16 November 2026, 15:38 UTC · Survey ID cd_72cfde97ee7d4191883804aea6420e23
realm/realm-java
Measured 16 November 2026, 15:35 UTC, at code version e5f4caa
Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.
Bus factor is not measured: No living knowledge left to concentrate.
CAI scoreAdequate
CriticalWeakAdequateStrongExemplary
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: 73,188 lines of product code in 10 projects, tests not counted · Estimated rebuild effort: about 1.3 person-years · Weakest lens: Code Health, 50.6
Findings by how serious they are
18 critical451 serious294 minor
16 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
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 15:35 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 ▸
56of 56 dimensions measured by tools.
753of 763 findings point to an exact file and line, so you can open each one in the code. The other 10 concern the repository as a whole, such as missing documentation.
56dimensions across 7 lenses, read from 73,188 lines of product code in 10 projects.
realm/realm-java falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 58.2 out of 100 and is rated Adequate, and 17 of its 18 critical findings are security problems.
Code Health, at 50.6, is the weakest lens and counts most in the score. The best first step for the work it takes is fixing the password or key in the code, worth about 2.6 points. Writing log messages as searchable templates would lift Code Health itself, worth about 4.7 points. Raising Code Health to 70 would lift the score to about 62.9.
Eight pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Four passwords or keys in the code's history and one in the code are open to anyone who can read the repository, and three settings leave the servers or containers unsafe. Replacing each exposed password or key, pinning each tool to an exact version and correcting the unsafe settings would close these risks. Limiting each secret to its own step would fix the secret exposed to more of the pipeline than needed. The test the project itself marks as unreliable needs fixing or deleting.
The product code is 73,188 lines, about €190,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 forThe 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.
If Code Health rose from 50.6 to 70, the lowest score rated Strong, the score would rise from 58.2 to about 62.9.
Code composition: what the lines of code are
Product code 40%Tests 60%
Rebuild cost: about €190,000 · Estimate
Cost to rebuild
€64,000 to €320,000, for 1,066 to 3,382 hours of work, about 1.3 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, 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 58. 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.
Size
Medium: 73,188 lines of product code
What it is not
Not 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 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Raises the score by about 2.6 points · Low effort · REDACTED Scanning
Raises the score by about 4.7 points · Medium effort · Structured logging
3
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced.
Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
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 €190,000 to build again, about 1.3 person-years of work. Its weakest lens is Code Health, at 50.6 (Adequate). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 2.6 points for low effort, because it clears the 1 REDACTED 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
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 11,280 lines over the last 90 days, which is about 45,747 lines a year. At that pace, the extra work comes to an estimated 2.3 to 15.2 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
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.
44 modules, with 44 dependencies between them. 2 loops run through 12 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 4 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.
gradle.SimpleAGPVersion uses gradle, so a change to gradle can break gradle.SimpleAGPVersion, while a change to gradle.SimpleAGPVersion can't break gradle.
Position
Below the diagonal: gradle.SimpleAGPVersion uses a module listed above it, which is the healthy direction.
internal.coroutines uses coroutines, so a change to coroutines can break internal.coroutines, while a change to internal.coroutines can't break coroutines.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
51 pairs of types, where a type in processor.Constants.RealmFieldType uses a type in processor.Constants. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
processor.Constants.RealmFieldType uses processor.Constants, so a change to processor.Constants can break processor.Constants.RealmFieldType, while a change to processor.Constants.RealmFieldType can't break processor.Constants.
Position
Below the diagonal: processor.Constants.RealmFieldType uses a module listed above it, which is the healthy direction.
27→33 processor.ModuleMetaData uses processorpart of a loop✕
Connections
1 pair of types, where a type in processor.ModuleMetaData uses a type in processor.
processor.ModuleMetaData uses processor, so a change to processor can break processor.ModuleMetaData, while a change to processor.ModuleMetaData can't break processor.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
28→33 processor.RealmJsonTypeHelper uses processorpart of a loop✕
Connections
9 pairs of types, where a type in processor.RealmJsonTypeHelper uses a type in processor.
processor.RealmJsonTypeHelper uses processor, so a change to processor can break processor.RealmJsonTypeHelper, while a change to processor.RealmJsonTypeHelper can't break processor.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
analytics.UrlEncodedAnalytics uses analytics, so a change to analytics can break analytics.UrlEncodedAnalytics, while a change to analytics.UrlEncodedAnalytics can't break analytics.
Position
Below the diagonal: analytics.UrlEncodedAnalytics uses a module listed above it, which is the healthy direction.
coroutines uses internal.coroutines, so a change to internal.coroutines can break coroutines, while a change to coroutines can't break internal.coroutines.
Position
Below the diagonal: coroutines uses a module listed above it, which is the healthy direction.
internal.objectstore uses internal.async, so a change to internal.async can break internal.objectstore, while a change to internal.objectstore can't break internal.async.
Position
Below the diagonal: internal.objectstore uses a module listed above it, which is the healthy direction.
internal.objectstore uses mongodb.sync, so a change to mongodb.sync can break internal.objectstore, while a change to internal.objectstore can't break mongodb.sync.
Position
Below the diagonal: internal.objectstore uses a module listed above it, which is the healthy direction.
32→34 internal.objectstore uses internalpart of a loop✕
Connections
12 pairs of types, where a type in internal.objectstore uses a type in internal.
internal.objectstore uses internal, so a change to internal can break internal.objectstore, while a change to internal.objectstore can't break internal.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
32→38 internal.objectstore uses io.realmpart of a loop✕
Connections
14 pairs of types, where a type in internal.objectstore uses a type in io.realm.
internal.objectstore uses io.realm, so a change to io.realm can break internal.objectstore, while a change to internal.objectstore can't break io.realm.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
processor uses processor.Constants, so a change to processor.Constants can break processor, while a change to processor can't break processor.Constants.
Position
Below the diagonal: processor uses a module listed above it, which is the healthy direction.
processor uses processor.nameconverter, so a change to processor.nameconverter can break processor, while a change to processor can't break processor.nameconverter.
Position
Below the diagonal: processor uses a module listed above it, which is the healthy direction.
processor uses processor.ModuleMetaData, so a change to processor.ModuleMetaData can break processor, while a change to processor can't break processor.ModuleMetaData.
Position
Below the diagonal: processor uses a module listed above it, which is the healthy direction.
processor uses processor.RealmJsonTypeHelper, so a change to processor.RealmJsonTypeHelper can break processor, while a change to processor can't break processor.RealmJsonTypeHelper.
Position
Below the diagonal: processor uses a module listed above it, which is the healthy direction.
internal uses internal.objectstore, so a change to internal.objectstore can break internal, while a change to internal can't break internal.objectstore.
Position
Below the diagonal: internal uses a module listed above it, which is the healthy direction.
processor.RealmProxyClassGenerator uses processor, so a change to processor can break processor.RealmProxyClassGenerator, while a change to processor.RealmProxyClassGenerator can't break processor.
Position
Below the diagonal: processor.RealmProxyClassGenerator uses a module listed above it, which is the healthy direction.
processor.RealmVersionChecker uses processor, so a change to processor can break processor.RealmVersionChecker, while a change to processor.RealmVersionChecker can't break processor.
Position
Below the diagonal: processor.RealmVersionChecker uses a module listed above it, which is the healthy direction.
io.realm uses internal.objectstore, so a change to internal.objectstore can break io.realm, while a change to io.realm can't break internal.objectstore.
Position
Below the diagonal: io.realm uses a module listed above it, which is the healthy direction.
200 pairs of types, where a type in io.realm uses a type in internal. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
13
High / Critical
A03:2025 — Software Supply Chain Failures
10
Medium
A02:2025 — Security Misconfiguration
7
High / Critical
A07:2025 — Authentication Failures
6
High / Critical
Roadmap
Top priorities: Interpolated log message defeats structured logging; Resolve the 203 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (8), DynamicRealmObject.java, SetValueOperator.java; Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
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.
Bring the 23 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RealmProxyClassGenerator.emitCreateExpectedObjectSchemaInfo (cyclomatic 63), DynamicRealmObject.toString (cyclomatic 61), ProxyUtils.createRealmListWithJsonStream (cyclomatic 55).
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 — 18
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 — 451
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 — 294
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 16
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 56 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, 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 — 56 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 753 of 763 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D4 Code Duplication — 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. The 75 duplicated block group(s) on this row were found in the languages this pass could tokenize, and they do NOT cover all of this repository's production source: .cpp (16,118 lines, 18% of production source) went unread, because no language model this pass could load exposed a clone-unit token stream for those file kinds. Duplication in that source is UNMEASURED — its absence from the count above is a gap in this analyzer's language coverage, not a finding that the code is free of duplication.
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 MEASURED: test source is present (.kt, .java) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo.
D10 Test Quality — 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. The 104 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 127 test source file(s) (.kt) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — 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 repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt, .java), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 27 Maven/Gradle manifest(s) were read, stating a version for 70 dependency(ies) and leaving 27 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 206 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 97 of the 357 production source files in this repository: 151 are under the ~2,400-byte size floor this dimension measures over, and the remaining 109 have no attributable history left to measure.
D19 Documentation Quality — 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. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
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.
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's deterministic call-shape rules are gated per language (docs/plans/deterministic-engine.md, P5; C# and each NeutralApiArms arm pass): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
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 — 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. Project size and spread are measured over build units whose source a code model reads. This repository's .cpp source is a material share of its production lines and was read by none, so the score is a verdict about the units that were read. Not a finding that the unread source is cohesive — it is unmeasured.
D27 Navigability — 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. Tracing effort is measured over resolved call sites, and all 622 sampled here came from .java files. This repository's .cpp, .kt source is a material share of its production lines and contributed none, so the score above is a verdict about the part that was read. Not a finding that the unread half navigates well — it is unmeasured.
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. `REDACTED`, `realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt`, `realm/realm-annotations-processor/src/main/java/io/realm/processor/Utils.kt` 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.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is an unrecognised JSR-330 (javax.inject / jakarta.inject) container, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AX6 Interface segregation — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
AXB2 Runtime readiness — 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. Our sandbox ran out of disk space while building the image. This is a limit of our sandbox, not of your repository. (rule: disk-full). The renderer reported: docker build failed (exit 1) — 85 | >>> 'system-images;android-31;default;x86_64' 86 | -------------------- ERROR: failed to solve: process "/bin/sh -c yes | sdkmanager 'build-tools;30.0.3' 'emulator' 'extras;android;m2repository' 'platforms;android-30' 'platform-tools' 'ndk;23.1.7779620' 'system-images;android-31;default;x86_64'" did not complete successfully: exit code: 1; likely cause (our sandbox): our sandbox ran out of disk space while building the image. This is a limit of our sandbox, not of your repository; runtime evidence skipped.
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 REDACTED (REDACTED). docker build failed (exit 1) — 85 | >>> 'system-images;android-31;default;x86_64' 86 | -------------------- ERROR: failed to solve: process "/bin/sh -c yes | sdkmanager 'build-tools;30.0.3' 'emulator' 'extras;android;m2repository' 'platforms;android-30' 'platform-tools' 'ndk;23.1.7779620' 'system-images;android-31;default;x86_64'" did not complete successfully: exit code: 1; likely cause (our sandbox): our sandbox ran out of disk space while building the image. This is a limit of our sandbox, not of your repository; 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. These audit 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 audit controls.
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. These retention 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 retention controls.
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. These data-subject rights 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 data-subject rights controls.
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.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security 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 web-security controls.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X18 Disposal-pattern correctness — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X19 Unrestored process-global state — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch, got, undici, node:http; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X21 Side-effecting pattern guard — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X23 Unguarded diagnostic materialisation — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X25 Inert configuration knob — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X26 Unsynchronised callback handoff — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X27 Collection changed while being enumerated — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X3 Exception handling — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X30 Support guard that admits what it rejects — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
X4 Structured logging — 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 check's reader does not cover every language in this repository. The score describes the part it read, which is most of the product; the rest is a gap in this analyzer's language reach.
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.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
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.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
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".
P5 DR & Backup: Backup/restore and disaster-recovery readiness is judged from in-repo evidence — a config that exists is not a tested restore, so the absence of positive evidence is reported as "not evidenced", never scored as present.
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
23 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was RealmProxyClassGenerator.emitCreateExpectedObjectSchemaInfo at 63. A further 10 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 RealmFieldType.isValid at 52 — they are counted neither in the figure above nor in this dimension's score. 4 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: realm/realm-library/src/main/java/io/realm/RealmFieldType.java (RealmFieldType.isValid at 52), realm/realm-library/src/main/java/io/realm/internal/Property.java (Property.convertFromRealmFieldType at 51), realm/realm-library/src/main/java/io/realm/internal/Table.java (Table.addColumn at 45), realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java (RealmMapEntrySet.iteratorFactory at 17). 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.
+ 18 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 23 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with RealmProxyClassGenerator.emitCreateExpectedObjectSchemaInfo (cyclomatic 63), DynamicRealmObject.toString (cyclomatic 61), ProxyUtils.createRealmListWithJsonStream (cyclomatic 55). — 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 23 together lifts Cyclomatic Complexity from 6.7 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 29 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 60 down to 60 or less in Cognitive Complexity — start with ProxyUtils.createRealmListWithJsonStream (cognitive 122), ProxyUtils.setRealmListWithJsonObject (cognitive 105), ClassMetaData.categorizeField (cognitive 61). — 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 3 together lifts Cognitive Complexity from 5.8 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.7 / 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.
Resolve the 32 TooManyMethods finding(s) in God Classes — start with RealmSet.java (3), RealmQuery.java, Table.java. — One of this dimension's main actionable groups (32 warning-level).
Resolve the 14 MethodTooLong finding(s) in God Classes — start with RealmProxyClassGenerator.kt (8), Property.java (2), ProxyUtils.java (2). — One of this dimension's main actionable groups (14 warning-level).
Resolve the 12 ClassTooLong finding(s) in God Classes — start with RealmProxyClassGenerator.kt, DynamicRealmObject.java, Realm.java. — One of this dimension's main actionable groups (12 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
75 duplicated block group(s) detected. 6.8 % of the production lines (4,952 of 73,188) are in a reported copy. A further 90 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 13 of the 165 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population. Measured on part of this repository only: .cpp (18% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
Edited copy of a member (13 corresponding lines) · ×4realm/realm-library/src/main/java/io/realm/internal/OsList.java:26
Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:307
+ 97 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 10 Duplicated block (10 lines × 2) finding(s) in Code Duplication — start with RealmObservableFactory.java (4), Realm.java, RealmObject.java. — One of this dimension's main actionable groups (10 warning-level).
Resolve the 6 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with OsList.java (4), Realm.java, RealmObject.java. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 5 Duplicated block (11 lines × 2) finding(s) in Code Duplication — start with RealmProxyClassGenerator.kt (4), CityAdapter.java. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.2 / 10Stronggated by 1 serious finding✓ 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.
10 production modules (Gradle+CMake), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 7 of the 10 (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).
Off the main sequence: realm:realm-library
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
D10 · Test Quality10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
3 skipped (3 with a documented reason), 0 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 104 tests. Measured on the .java suite only — at least 127 test source file(s) (.kt) went unread, so its test quality is unmeasured and is not in these counts.
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.
1 secret(s) detected. 2 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
REDACTED
What to do
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
0 of 36 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 27 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 27 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. A further 23 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.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
What it measures: 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.
143 deducted task-comment markers across 73188 LoC (0.2/KLoC) → score 9.6. 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.
Resolve the 97 TodoComment finding(s) in Explicit Debt — start with some_test_AllTypesRealmProxy-pre-dictionary.java (15), RealmTests.java (7), RealmProxyClassGenerator.kt (5). — One of this dimension's main actionable groups (97 warning-level).
Resolve the 45 FixmeComment finding(s) in Explicit Debt — start with SyncSessionTests.kt (5), EmbeddedObjectsTest.kt (4), SyncedRealmTests.kt (3). — One of this dimension's main actionable groups (45 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with RealmCore.java. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 9 build units (Gradle) flagged as possibly oversized/incoherent. This repository's .cpp source was read by no build unit, so this covers part of the tree, not all of it.
Projects may be oversized for their cohesionrealm/realm-library/build.gradle:1
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
81 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated. Measured over the .java source only — this repository's .cpp, .kt was not sampled for call sites, so this score covers part of the tree, not all of it.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED 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.
4 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
REDACTED
What to do
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
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).
13 finding(s): 0 critical, 9 high, 4 medium, 0 low. 8 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 18 file(s) — `examples/gradlew` (line 72, line 173), `gradle-plugin/gradlew` (line 72, line 173), `gradlew` (line 72, line 173), `library-benchmarks/gradlew` (line 72, line 173), `library-build-transformer/gradlew` (line 72, line 173), … (+13 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 7 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 (7 issue-level, 0 of them charged here).
No action in Static Analysis (SAST) — all 1 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 (1 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 3 High IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 issue-level).
Resolve the 4 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
206 of 206 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt. Counted over 206 of the 357 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1
Dormant codebase
What to do
Resolve the 203 Orphaned file finding(s) in Knowledge Freshness — start with build.gradle (8), DynamicRealmObject.java, SetValueOperator.java. — One of this dimension's main actionable groups (203 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with RealmProxyClassGenerator.kt, RealmQuery.java, Realm.java. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. 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.
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.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 18 platform declaration(s) and 70 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
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.
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.
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.
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.
`Row` declares 48 abstract methods: `checkIfAttached`, `createEmbeddedObject`, `freeze`, `getBinaryByteArray`, `getBoolean`, `getColumnCount`, `getColumnKey`, `getColumnNames`, `getColumnType`, `getDate`, `getDecimal128`, `getDouble`, `getFloat`, `getLink`, `getLong`, `getModelList`, `getModelMap`, `getModelSet`, `getNativeRealmAny`, `getObjectId`, `getObjectKey`, `getRealmAnyMap`, `getRealmAnySet`, `getString`, `getTable`, `getUUID`, `getValueList`, `getValueMap`, `getValueSet`, `hasColumn`, `isLoaded`, `isNull`, `isNullLink`, `isValid`, `nullifyLink`, `setBinaryByteArray`, `setBoolean`, `setDate`, `setDecimal128`, `setDouble`, and 8 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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. — realm/realm-library/src/main/java/io/realm/internal/Row.java:39
`RxObservableFactory` declares 16 abstract methods under just 2 distinct name(s): `changesetsFrom`, `changesetsFrom`, `changesetsFrom`, `changesetsFrom`, `changesetsFrom`, `changesetsFrom`, `from`, `from`, `from`, `from`, `from`, `from`, `from`, `from`, `from`, `from`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 2 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface. — realm/realm-library/src/main/java/io/realm/rx/RxObservableFactory.java:35
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
Where the width is an overload set rather than separate responsibilities, collapse the overloads instead — segregating those relieves no caller.
Other · Code Health — Unreviewed-generation residue in this repository's Java: methods whose whole body only throws a "not implemented" or bare unsupported-operation exception, or returns a default value (or nothing) under a TODO/FIXME marker, 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.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Java: methods that only throw a "not implemented" exception, 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. (×17) — examples/unitTestExample/src/test/java/io/realm/examples/unittesting/ExampleActivityTest.java:71, examples/unitTestExample/src/test/java/io/realm/examples/unittesting/ExampleRealmTest.java:54, realm/realm-annotations-processor/src/test/java/io/realm/processor/RealmProcessorTest.java:95, …
What to do
Clear the softer debt: re-enable or delete @Disabled/@Ignore tests, decide whether each empty method or UnsupportedOperationException is deliberate (and say so in a comment), and replace @SuppressWarnings("all") with targeted, justified suppressions.
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.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
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.
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.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
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.
Do you agree with this assessment?
P10 · Library API & versioning8.1 / 10Strong✓ Tool-verified
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.
8 public types in `io.realm.internal.async` are marked as implementation by their own namespace, folder or name: `RealmResultTaskImplTestKt` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/async/RealmResultTaskImplTest.kt:1, `internal`), `RealmResultTaskImplTest` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/async/RealmResultTaskImplTest.kt:35, `internal`), `RealmStreamTaskImplTest` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/async/RealmStreamTaskImplTest.kt:30, `internal`), `BadVersionException` (realm/realm-library/src/main/java/io/realm/internal/async/BadVersionException.java:27, `internal`), `BgPriorityCallable` (realm/realm-library/src/main/java/io/realm/internal/async/BgPriorityCallable.java:26, `internal`), `BgPriorityRunnable` (realm/realm-library/src/main/java/io/realm/internal/async/BgPriorityRunnable.java:23, `internal`), `RealmAsyncTaskImpl` (realm/realm-library/src/main/java/io/realm/internal/async/RealmAsyncTaskImpl.java:25, `internal`), `RealmThreadPoolExecutor` (realm/realm-library/src/main/java/io/realm/internal/async/RealmThreadPoolExecutor.java:37, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/async/RealmResultTaskImplTest.kt:1
2 public types in `io.realm.internal.network` are marked as implementation by their own namespace, folder or name: `LoggingInterceptorTest` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/network/LoggingInterceptorTest.kt:36, `internal`), `NetworkRequestTests` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/network/NetworkRequestTests.kt:13, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/network/LoggingInterceptorTest.kt:36
1 public type in `io.realm` is marked as implementation by its own namespace, folder or name: `RealmAnyNativeFunctionsImpl` (realm/realm-library/src/main/java/io/realm/RealmAnyNativeFunctionsImpl.java:27, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — realm/realm-library/src/main/java/io/realm/RealmAnyNativeFunctionsImpl.java:27
72 public types in `io.realm.internal` are marked as implementation by their own namespace, folder or name: `Capabilities` (realm/realm-library/src/main/java/io/realm/internal/Capabilities.java:27, `internal`), `CheckedRow` (realm/realm-library/src/main/java/io/realm/internal/CheckedRow.java:31, `internal`), `ColumnIndices` (realm/realm-library/src/main/java/io/realm/internal/ColumnIndices.java:50, `internal`), `ColumnInfo` (realm/realm-library/src/main/java/io/realm/internal/ColumnInfo.java:63, `internal`), `ColumnDetails` (realm/realm-library/src/main/java/io/realm/internal/ColumnInfo.java:66, `internal`), `EmptyLoadChangeSet` (realm/realm-library/src/main/java/io/realm/internal/EmptyLoadChangeSet.java:24, `internal`), `Freezable` (realm/realm-library/src/main/java/io/realm/internal/Freezable.java:28, `internal`), `IOException` (realm/realm-library/src/main/java/io/realm/internal/IOException.java:20, `internal`), and 64 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — realm/realm-library/src/main/java/io/realm/internal/Capabilities.java:27
5 public types in `io.realm.internal.android` are marked as implementation by their own namespace, folder or name: `AndroidCapabilities` (realm/realm-library/src/main/java/io/realm/internal/android/AndroidCapabilities.java:29, `internal`), `AndroidRealmNotifier` (realm/realm-library/src/main/java/io/realm/internal/android/AndroidRealmNotifier.java:18, `internal`), `ISO8601Utils` (realm/realm-library/src/main/java/io/realm/internal/android/ISO8601Utils.java:37, `internal`), `JsonUtils` (realm/realm-library/src/main/java/io/realm/internal/android/JsonUtils.java:32, `internal`), `TypeUtils` (realm/realm-library/src/main/java/io/realm/internal/android/TypeUtils.java:19, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — realm/realm-library/src/main/java/io/realm/internal/android/AndroidCapabilities.java:29
1 public type in `io.realm.internal.annotations` is marked as implementation by its own namespace, folder or name: `ObjectServer` (realm/realm-library/src/main/java/io/realm/internal/annotations/ObjectServer.java:30, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — realm/realm-library/src/main/java/io/realm/internal/annotations/ObjectServer.java:30
2 public types in `io.realm.internal.core` are marked as implementation by their own namespace, folder or name: `NativeRealmAny` (realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAny.java:37, `internal`), `NativeRealmAnyCollection` (realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:33, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAny.java:37
1 public type in `io.realm.internal.coroutines` is marked as implementation by its own namespace, folder or name: `InternalFlowFactory` (realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:34, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:34
2 public types in `io.realm.internal.modules` are marked as implementation by their own namespace, folder or name: `CompositeMediator` (realm/realm-library/src/main/java/io/realm/internal/modules/CompositeMediator.java:48, `internal`), `FilterableMediator` (realm/realm-library/src/main/java/io/realm/internal/modules/FilterableMediator.java:49, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — realm/realm-library/src/main/java/io/realm/internal/modules/CompositeMediator.java:48
5 public types in `io.realm.internal.objectstore` are marked as implementation by their own namespace, folder or name: `OsKeyPathMapping` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsKeyPathMapping.java:35, `internal`), `OsMutableSubscriptionSet` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsMutableSubscriptionSet.java:27, `internal`), `OsObjectBuilder` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:76, `internal`), `OsSubscription` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscription.java:25, `internal`), `OsSubscriptionSet` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscriptionSet.java:41, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — realm/realm-library/src/main/java/io/realm/internal/objectstore/OsKeyPathMapping.java:35
1 public type in `io.realm.internal.util` is marked as implementation by its own namespace, folder or name: `Pair` (realm/realm-library/src/main/java/io/realm/internal/util/Pair.java:24, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers. — realm/realm-library/src/main/java/io/realm/internal/util/Pair.java:24
What to do
Hide `io.realm.internal.async` (`RealmResultTaskImplTestKt`, `RealmResultTaskImplTest`, `RealmStreamTaskImplTest`, `BadVersionException`, `BgPriorityCallable`, `BgPriorityRunnable`, `RealmAsyncTaskImpl`, `RealmThreadPoolExecutor`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm.internal.network` (`LoggingInterceptorTest`, `NetworkRequestTests`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm` (`RealmAnyNativeFunctionsImpl`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm.internal` (`Capabilities`, `CheckedRow`, `ColumnIndices`, `ColumnInfo`, `ColumnDetails`, `EmptyLoadChangeSet`, `Freezable`, `IOException`, and 64 more) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm.internal.android` (`AndroidCapabilities`, `AndroidRealmNotifier`, `ISO8601Utils`, `JsonUtils`, `TypeUtils`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm.internal.annotations` (`ObjectServer`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm.internal.core` (`NativeRealmAny`, `NativeRealmAnyCollection`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm.internal.coroutines` (`InternalFlowFactory`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm.internal.modules` (`CompositeMediator`, `FilterableMediator`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm.internal.objectstore` (`OsKeyPathMapping`, `OsMutableSubscriptionSet`, `OsObjectBuilder`, `OsSubscription`, `OsSubscriptionSet`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `io.realm.internal.util` (`Pair`) (Java: package-private (no modifier), or leave its package out of `module-info` exports; Kotlin: `internal`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
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.
`examples/architectureComponentsExample/build.gradle` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — examples/architectureComponentsExample/build.gradle:33
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Nothing pauses a release for a human: publish as a draft release (or gate the release job on a protected tag/manual dispatch) so a bad build can be stopped before users can download it.
Do you agree with this assessment?
P5 · DR & Backup4.0 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether disaster recovery is planned and codified — backups, geo-recovery, RTO/RPO, persistence guarantees — from IaC + container manifests + docs, never the live cloud.
Method: Filesystem scan: disaster recovery, backup, geo-recovery, RTO/RPO, persistence guarantees from IaC, manifests, and docs. Exhaustive, deterministic, never a live environment.
What to do
Document RTO/RPO and a tested restore procedure (a backup config alone isn't disaster recovery).
Enable purge protection / soft-delete (and prevent_destroy on critical resources) so data stores can't be lost to an accidental or malicious delete.
Readiness · Performance — Whether the code protects its performance with benchmarks — a benchmark suite, allocation/memory measurement, and (ideally) a CI gate. Presence is credited as a bonus, never a deduction.
Method: Repo + source scan: BenchmarkDotNet referenced (csproj/source), [Benchmark]/[MemoryDiagnoser] attribute counts, and a benchmark step in CI; off .NET, the same ladder over Go testing.B, Rust criterion/#[bench]/divan, JMH/kotlinx-benchmark, pytest-benchmark/asv/pyperf, tinybench/mitata/vitest bench/benchmark.js and Swift package-benchmark — scored as a bonus ladder (absence is neutral, never a deduction). Deterministic, presence detection.
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.
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.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
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.
The guard on line 293 rejects `className` and line 294 reports that rejection as `NullPointerException` — but the condition's own test `className.isEmpty()` is true of a value that is NOT null: it is satisfied by an EMPTY `className`, and on that path `className` was already proven non-null by the very expression that decided it. So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `NullPointerException` to handle a real null handles the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. Throw `IllegalArgumentException` for the empty case, or split the guard and throw each on its own condition. — realm/realm-library/src/main/java/io/realm/internal/RealmProxyMediator.java:294
What to do
Each finding names the throw and the test in its own condition that is true of a NON-null value. Confirm from the two, then throw the exception that describes what was actually wrong: on the JVM `IllegalArgumentException` for a value that arrived empty (`Objects.requireNonNull(x)` for the null half, Kotlin's `require(x.isNotEmpty())` for the empty one), in Dart `ArgumentError.value(x, 'x', 'must not be empty')`, in F# `invalidArg (nameof x) "must not be empty"` (keeping `nullArg` for the null half). Splitting the two conditions is usually clearer than picking one exception for both: they are different failures and the caller may want to handle them differently.
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.
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.
`debug` at line 121 is called with an argument built by `proxyMediatorClasses.joinToString("…")` (line 121), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:121
`debug` at line 91 is called with an argument built by `allManagedFields.joinToString("…")` (line 91), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — realm-transformer/src/main/kotlin/io/realm/transformer/build/FullBuild.kt:91
`debug` at line 90 is called with an argument built by `outputClassNames.joinToString("…")` (line 90), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on. — realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:90
What to do
In Kotlin, hand the logger a lambda it calls only when the level is on (`logger.debug { "rows: ${rows.joinToString()}" }` — kotlin-logging and Log4j 2's Kotlin API take one), or put the line behind `if (log.isDebugEnabled)` (`if (BuildConfig.DEBUG)` for a line only a debug build needs). A string template is not the fix on SLF4J or Timber: their message is a `String`, so every `joinToString` or `toJson` inside the `${…}` runs before the call is entered.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` 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.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — realm-transformer/src/main/kotlin/io/realm/transformer/ext/ProjectExt.kt:71, realm-transformer/src/main/kotlin/io/realm/analytics/ComputerIdentifierGenerator.kt:49
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. (×2) — realm-transformer/src/main/kotlin/io/realm/analytics/UrlEncodedAnalytics.kt:38, realm/realm-library/src/main/java/io/realm/internal/RealmCore.java:94
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. 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 `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`debug` at line 82 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:82
`debug` at line 130 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:130
`debug` at line 151 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:151
`debug` at line 155 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:155
`debug` at line 156 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:156
`debug` at line 181 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:181
`debug` at line 185 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:185
`debug` at line 186 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:186
`debug` at line 237 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/RealmTransformer.kt:237
`debug` at line 52 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. (×2) — realm-transformer/src/main/kotlin/io/realm/transformer/Stopwatch.kt:52, library-build-transformer/src/main/kotlin/io/realm/buildtransformer/util/Stopwatch.kt:52
`debug` at line 61 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. (×2) — realm-transformer/src/main/kotlin/io/realm/transformer/Stopwatch.kt:61, library-build-transformer/src/main/kotlin/io/realm/buildtransformer/util/Stopwatch.kt:61
`debug` at line 106 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:106
`debug` at line 121 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:121
`debug` at line 131 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:131
`debug` at line 205 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:205
`debug` at line 45 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/FullBuild.kt:45
`debug` at line 91 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/FullBuild.kt:91
`debug` at line 95 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. (×2) — realm-transformer/src/main/kotlin/io/realm/transformer/build/FullBuild.kt:95, gradle-plugin/src/main/kotlin/io/realm/gradle/Realm.kt:95
`debug` at line 67 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:67
`debug` at line 89 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:89
`debug` at line 90 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:90
`debug` at line 105 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:105
`debug` at line 81 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — realm-transformer/src/main/kotlin/io/realm/analytics/RealmAnalytics.kt:81
`debug` at line 47 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — library-build-transformer/src/main/kotlin/io/realm/buildtransformer/asm/visitors/AnnotatedCodeStripVisitor.kt:47
`debug` at line 57 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — library-build-transformer/src/main/kotlin/io/realm/buildtransformer/asm/visitors/AnnotatedCodeStripVisitor.kt:57
`debug` at line 65 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — library-build-transformer/src/main/kotlin/io/realm/buildtransformer/asm/visitors/AnnotatedCodeStripVisitor.kt:65
`debug` at line 74 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — library-build-transformer/src/main/kotlin/io/realm/buildtransformer/asm/visitors/AnnotatedCodeStripVisitor.kt:74
Other · Code Health — Whether Java packages are null-marked and not undermined by heavy nullness suppression — a package under `@NullMarked` (or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, or a NullAway/Checker Framework configuration naming it) makes an unannotated reference exclude null, and `@SuppressWarnings("NullAway")`, `("nullness")`, `("null")` and `castToNonNull(…)` are what silence it.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
12/44 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 13 of 55 WCAG 2.2 Level A/AA success criteria (24%; ≈26% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 42 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
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.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D11 Test Reliability — 1 observation(s) recorded · This repository declares 1 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.kt, .java), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
X10 Duplicated predicate — 10 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X6 Hand-rolled structured-format parsing — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 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: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — Not assessed: these retention controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks retention controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C5 Data-Subject Rights — Not assessed: these data-subject rights controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks data-subject rights controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
Not included — 54 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.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — docker build failed (exit 1) — 85 | >>> 'system-images;android-31;default;x86_64' 86 | -------------------- ERROR: failed to solve: process "/bin/sh -c yes | sdkmanager 'build-tools;30.0.3' 'emulator' 'extras;android;m2repository' 'platforms;android-30' 'platform-tools' 'ndk;23.1.7779620' 'system-images;android-31;default;x86_64'" did not complete successfully: exit code: 1; likely cause (our sandbox): our sandbox ran out of disk space while building the image. This is a limit of our sandbox, not of your repository; 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.
D12 Dependency Hygiene — Not scored — 27 Maven/Gradle manifest(s) were read, stating a version for 70 dependency(ies) and leaving 27 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
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: 12 candidate(s) found and not reported.
D22 Internal API Consistency — API consistency is measured on C#, TypeScript, Go only; the exposed Kotlin surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. 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 .java, .kt, .py source were not judged.
D25 ADR Conformance — no ADRs to check
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
D32 Data Compliance (PII/GDPR) — 3 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.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
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 — not scored — this repository shows only 1 of the 3 signals this lens looks for (35 value object(s))
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'.
P2 Observability — This repository's JVM source (7 module(s), 320 file(s) read) declares no entry point and bootstraps no server, and nothing here deploys a service — it is a library, run inside whatever hosts it, so production observability (structured logging, tracing/metrics, health checks) is N/A. If it grows a binary or a service, the dimension reactivates.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM 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
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 — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — X1 reached only 16% of this repository's production lines — java (59,320 lines), cpp (16,118 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 16% of this repository's production lines — java (59,320 lines), cpp (16,118 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
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
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
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
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
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.
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.
D11 · Test Reliability· Test declared unreliable · ×1
Test declared unreliable: compactRealm_populatedRealm realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/mongodb/sync/SyncedRealmTests.kt:211— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "FIXME Flaky, seems like Realm.compactRealm(config) sometimes returns false". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
TodoComment realm/realm-library/src/testUtils/java/io/realm/rule/RunWithRemoteService.java:184— // TODO: Find a way to block caller thread until the service process finishes current step. — 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 realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncSessionTests.kt:119— // TODO We generate new partition value for each test to avoid overlaps in data. We — 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 realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncedRealmIntegrationTests.kt:73— // TODO We generate new partition value for each test to avoid overlaps in data. We — 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 realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncSessionTests.kt:1070— // TODO Seems to align with tests in SessionTests, should we move them to same location — 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 realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncSessionTests.kt:1244— // TODO We cannot currently easily verify that token is actually invalid and triggering — 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 realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncedRealmIntegrationTests.kt:106— // TODO: We don't have a way to ensure that the Realm instance on client thread has been — 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 realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncedRealmIntegrationTests.kt:287— // TODO: We don't have a way to ensure that the Realm instance on client thread has been — 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 realm/realm-library/src/syncIntegrationTest/java/io/realm/objectserver/utils/HttpUtils.java:35— // TODO If the timeouts are longer than the test timeout you risk getting — 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 REDACTED:315— // TODO Check that it doesn't contain invalid filesystem chars — 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 realm/realm-library/src/objectServer/java/io/realm/internal/SyncObjectServerFacade.java:185— // TODO Simplify. org.bson serialization only allows writing full documents, so the partition — 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 realm/realm-library/src/objectServer/java/io/realm/internal/network/OkHttpNetworkTransport.java:169— // TODO: timeOuts are not expected to change between requests. So for now just use the timeout first send. — 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 realm/realm-library/src/objectServer/java/io/realm/internal/network/OkHttpNetworkTransport.java:173— // TODO There doesn't appear to set a timeout for the entire http request, — 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 realm/realm-library/src/main/java/io/realm/BaseRealm.java:751— // TODO: Remove this after RealmList is backed by OS Results. — 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 realm/realm-library/src/main/java/io/realm/ManagedMapManager.java:373— // TODO: inefficient, pass array of keys and array of values to JNI instead, — 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 realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java:193— // TODO: Implement the delete in OS level and do check there! — 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 realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java:455— // TODO: Implement the deleteLast in OS level and do check there! — 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 realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java:467— // TODO: Implement the deleteLast in OS level and do check there! — 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 realm/realm-library/src/main/java/io/realm/RealmAny.java:596— // TODO: only used for testing purposes, see https://github.com/realm/realm-java/issues/7385
TodoComment realm/realm-library/src/main/java/io/realm/RealmCache.java:471— // TODO Ideally this would be part of `downloadInitialRemoteChanges` called before — 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 realm/realm-library/src/main/java/io/realm/RealmObject.java:109— // TODO What type of exception IllegalArgument/IllegalState? — 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 realm/realm-library/src/main/java/io/realm/RealmObject.java:876— // TODO Is this true? Should we just return Observable.just(object) ? — 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 realm/realm-library/src/main/java/io/realm/RealmObject.java:927— // TODO Is this true? Should we just return Observable.just(object) ? — 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 realm/realm-library/src/main/java/io/realm/RealmQuery.java:2742— // TODO Revisit this when primitive list queries are implemented. — 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 realm/realm-library/src/main/java/io/realm/RealmQuery.java:2782— // TODO implement 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 realm/realm-library/src/main/java/io/realm/RealmQuery.java:2818— // TODO: The performance by the pending query will be a little bit worse than directly calling core's — 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.
FixmeComment realm-transformer/src/main/kotlin/io/realm/transformer/RealmTransformer.kt:92— // FIXME With the new transformer API changes, processed classes from the Realm transformer aren't — 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.
FixmeComment realm/realm-library/src/syncTestUtils/java/io/realm/objectserver/utils/Constants.java:31— // FIXME: This doesn't work because the name changes — 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.
FixmeComment realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/EncryptedSynchronizedRealmTests.kt:104— // FIXME: ignore until https://github.com/realm/realm-java/issues/7028 is fixed
FixmeComment realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncSessionTests.kt:722— // FIXME: Investigate if this behavior is correct https://github.com/realm/realm-java/issues/7591
FixmeComment realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncSessionTests.kt:870— // FIXME Reavaluate with new sync states — 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.
FixmeComment realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncSessionTests.kt:1062— //FIXME not calling refresh will still point to the previous version of the Realm count == 1 — 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.
FixmeComment realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncSessionTests.kt:1078— // FIXME Is this critical for the test — 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.
FixmeComment realm/realm-library/src/syncIntegrationTest/kotlin/io/realm/SyncSessionTests.kt:1196— // FIXME Investigate — 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.
FixmeComment realm/realm-library/src/syncIntegrationTest/java/io/realm/BaseIntegrationTest.java:77— // FIXME: WARNING: Do not use `SyncTestRealmConfigurationFactory`, but use this. Refactor 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.
FixmeComment realm/realm-library/src/syncIntegrationTest/java/io/realm/objectserver/utils/HttpUtils.java:37— // FIXME re-adjust timeout after https://github.com/realm/realm-object-server-private/issues/697 is fixed
FixmeComment REDACTED:312— // FIXME Add support for partition key — 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.
FixmeComment realm/realm-library/src/objectServer/java/io/realm/internal/SyncObjectServerFacade.java:264— //FIXME remove this reflection call once we redesign the SyncManager to separate interface — 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.
FixmeComment realm/realm-library/src/objectServer/java/io/realm/internal/objectstore/OsMongoCollection.java:320— // FIXME Type illegal argument might be thrown wrong — 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.
FixmeComment realm/realm-library/src/main/java/io/realm/DynamicRealm.java:486— // FIXME: ThreadPoolExecutor will never throw the exception in the background. — 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.
FixmeComment realm/realm-library/src/main/java/io/realm/Realm.java:1808— // FIXME: ThreadPoolExecutor will never throw the exception in the background. — 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.
FixmeComment realm/realm-library/src/main/java/io/realm/Realm.java:164— // FIXME: This is to work around the different behaviour between the read only Realms in the Object Store and — 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.
FixmeComment realm/realm-library/src/main/java/io/realm/RealmObject.java:196— // FIXME: Consider adding type parameters to all RealmObject/RealmModel classes? — 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.
FixmeComment realm/realm-library/src/main/java/io/realm/RealmQuery.java:73— // FIXME Make private somehow — 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.
FixmeComment realm/realm-library/src/main/java/io/realm/internal/OsObject.java:236— // FIXME: Proxy could just pass the pk index here which is much faster. — 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.
FixmeComment realm/realm-library/src/main/java/io/realm/internal/OsRealmConfig.java:323— // FIXME — 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.
FixmeComment realm/kotlin-extensions/src/androidTestObjectServer/kotlin/io/realm/kotlin/KotlinSyncedRealmTests.kt:23— // FIXME — 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.
FixmeComment realm/kotlin-extensions/src/androidTestObjectServer/kotlin/io/realm/kotlin/KotlinSyncedRealmTests.kt:32— // FIXME — 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.
FixmeComment realm/realm-library/src/main/java/io/realm/internal/OsRealmConfig.java:373— // FIXME: enable once realm-sync adds support for SOCKS proxies — 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.
FixmeComment realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/mongodb/sync/FlexibleSyncConfigurationTests.kt:109— // FIXME: Figure out exactly what to return 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.
FixmeComment realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/mongodb/sync/SyncConfigurationTests.kt:229— // FIXME: Figure out exactly what to return 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.
TooManyMethods: RealmQuery realm/realm-library/src/main/java/io/realm/RealmQuery.java:69— TooManyMethods — 165 methods. The bar is 30 methods; this is 135 over it, 5.50× 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: Table realm/realm-library/src/main/java/io/realm/internal/Table.java:36— TooManyMethods — 161 methods. The bar is 30 methods; this is 131 over it, 5.37× 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: OsObjectBuilder realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:76— TooManyMethods — 136 methods. The bar is 30 methods; this is 106 over it, 4.53× 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: OsSet realm/realm-library/src/main/java/io/realm/internal/OsSet.java:31— TooManyMethods — 125 methods. The bar is 30 methods; this is 95 over it, 4.17× 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: OsList realm/realm-library/src/main/java/io/realm/internal/OsList.java:17— TooManyMethods — 121 methods. The bar is 30 methods; this is 91 over it, 4.03× 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: OsResults realm/realm-library/src/main/java/io/realm/internal/OsResults.java:43— TooManyMethods — 105 methods. The bar is 30 methods; this is 75 over it, 3.50× 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: TableQuery realm/realm-library/src/main/java/io/realm/internal/TableQuery.java:33— TooManyMethods — 105 methods. The bar is 30 methods; this is 75 over it, 3.50× 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: UncheckedRow realm/realm-library/src/main/java/io/realm/internal/UncheckedRow.java:40— TooManyMethods — 93 methods. The bar is 30 methods; this is 63 over it, 3.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: OsSharedRealm realm/realm-library/src/main/java/io/realm/internal/OsSharedRealm.java:37— TooManyMethods — 80 methods. The bar is 30 methods; this is 50 over it, 2.67× 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: Realm realm/realm-library/src/main/java/io/realm/Realm.java:138— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× 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: OsMap realm/realm-library/src/main/java/io/realm/internal/OsMap.java:34— TooManyMethods — 73 methods. The bar is 30 methods; this is 43 over it, 2.43× 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: DynamicRealmObject realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:53— TooManyMethods — 69 methods. The bar is 30 methods; this is 39 over it, 2.30× 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: Utils realm/realm-annotations-processor/src/main/java/io/realm/processor/Utils.kt:36— TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× 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: RealmList realm/realm-library/src/main/java/io/realm/RealmList.java:64— TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.03× 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: NativeRealmAny realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAny.java:37— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× 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: RealmProxyClassGenerator realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:49— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× 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: PendingRow realm/realm-library/src/main/java/io/realm/internal/PendingRow.java:24— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. Most of these members implement internal.Row (48 of 53 members), so moving them onto a smaller type would remove them from that contract rather than reduce it. To reduce it, split the contract instead: give each cohesive group of operations its own smaller interface and its own implementing type. Where the contract has to stay whole, move the work behind these members into collaborator types, so what is left here is a forward per member rather than a responsibility per member.
TooManyMethods: OrderedRealmCollectionImpl realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java:23— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× 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: BaseRealm realm/realm-library/src/main/java/io/realm/BaseRealm.java:59— 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: RealmResults realm/realm-library/src/main/java/io/realm/RealmResults.java:71— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× 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: ClassMetaData realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt:33— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× 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: RealmObjectSchema realm/realm-library/src/main/java/io/realm/RealmObjectSchema.java:49— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: RealmSet realm/realm-library/src/main/java/io/realm/RealmSet.java:74— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: CheckedRow realm/realm-library/src/main/java/io/realm/internal/CheckedRow.java:31— TooManyMethods — 41 methods. The bar is 30 methods; this is 11 over it, 1.37× 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: RealmAny realm/realm-library/src/main/java/io/realm/RealmAny.java:132— TooManyMethods — 40 methods. The bar is 30 methods; this is 10 over it, 1.33× 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.
MethodTooLong: RealmProxyClassGenerator.insertOrUpdateInternal realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1730— MethodTooLong — insertOrUpdateInternal runs 255 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 155 over it, 2.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RealmProxyClassGenerator.emitUpdateMethod realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2576— MethodTooLong — emitUpdateMethod runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RealmProxyClassGenerator.emitCopyMethod realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2173— MethodTooLong — emitCopyMethod runs 207 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 107 over it, 2.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RealmProxyClassGenerator.emitInsertInternal realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1437— MethodTooLong — emitInsertInternal runs 184 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 84 over it, 1.84× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: DynamicRealmObject.toString realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1716— MethodTooLong — toString runs 169 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 69 over it, 1.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Property.convertFromRealmFieldType realm/realm-library/src/main/java/io/realm/internal/Property.java:115— MethodTooLong — convertFromRealmFieldType runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ProxyUtils.createRealmListWithJsonStream realm/realm-library/src/main/java/io/realm/ProxyUtils.java:228— MethodTooLong — createRealmListWithJsonStream runs 133 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 33 over it, 1.33× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RealmProxyClassGenerator.emitCreateOrUpdateUsingJsonObject realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2996— MethodTooLong — emitCreateOrUpdateUsingJsonObject runs 130 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 30 over it, 1.30× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RealmProxyClassGenerator.emitCreateDetachedCopyMethod realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2427— MethodTooLong — emitCreateDetachedCopyMethod runs 127 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 27 over it, 1.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: OsRealmConfig.<init> realm/realm-library/src/main/java/io/realm/internal/OsRealmConfig.java:214— MethodTooLong — <init> runs 122 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 22 over it, 1.22× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ProxyUtils.setRealmListWithJsonObject realm/realm-library/src/main/java/io/realm/ProxyUtils.java:57— MethodTooLong — setRealmListWithJsonObject runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RealmProxyClassGenerator.setTableValues realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1298— MethodTooLong — setTableValues runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Property.convertToRealmFieldType realm/realm-library/src/main/java/io/realm/internal/Property.java:275— MethodTooLong — convertToRealmFieldType runs 103 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 3 over it, 1.03× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RealmProxyClassGenerator.emitRealmDictionary realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:502— MethodTooLong — emitRealmDictionary runs 102 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2 over it, 1.02× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
ClassTooLong: RealmProxyClassGenerator realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:49— ClassTooLong — 2676 significant lines (blank, comment-only and punctuation-only lines excluded), 56 methods. The bar is 400 significant lines; this is 2276 over it, 6.69× 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.
ClassTooLong: DynamicRealmObject realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:53— ClassTooLong — 1087 significant lines (blank, comment-only and punctuation-only lines excluded), 69 methods. The bar is 400 significant lines; this is 687 over it, 2.72× 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.
ClassTooLong: Realm realm/realm-library/src/main/java/io/realm/Realm.java:138— ClassTooLong — 612 significant lines (blank, comment-only and punctuation-only lines excluded), 76 methods. The bar is 400 significant lines; this is 212 over it, 1.53× 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.
ClassTooLong: OsObjectBuilder realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:76— ClassTooLong — 554 significant lines (blank, comment-only and punctuation-only lines excluded), 136 methods. The bar is 400 significant lines; this is 154 over it, 1.39× 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.
ClassTooLong: RealmList realm/realm-library/src/main/java/io/realm/RealmList.java:64— ClassTooLong — 541 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. The bar is 400 significant lines; this is 141 over it, 1.35× 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.
ClassTooLong: OsResults realm/realm-library/src/main/java/io/realm/internal/OsResults.java:43— ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 105 methods. The bar is 400 significant lines; this is 60 over it, 1.15× 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.
ClassTooLong: RealmProxyMediatorGenerator realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:28— ClassTooLong — 458 significant lines (blank, comment-only and punctuation-only lines excluded), 24 methods. The bar is 400 significant lines; this is 58 over it, 1.15× 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.
ClassTooLong: RealmObservableFactory realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:59— ClassTooLong — 436 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 36 over it, 1.09× 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.
ClassTooLong: Table realm/realm-library/src/main/java/io/realm/internal/Table.java:36— ClassTooLong — 428 significant lines (blank, comment-only and punctuation-only lines excluded), 161 methods. The bar is 400 significant lines; this is 28 over it, 1.07× 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.
ClassTooLong: RealmConfiguration realm/realm-library/src/main/java/io/realm/RealmConfiguration.java:68— ClassTooLong — 424 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 24 over it, 1.06× 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.
ClassTooLong: OrderedRealmCollectionImpl realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java:23— ClassTooLong — 416 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 16 over it, 1.04× 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.
ClassTooLong: OsSet realm/realm-library/src/main/java/io/realm/internal/OsSet.java:31— ClassTooLong — 405 significant lines (blank, comment-only and punctuation-only lines excluded), 125 methods. The bar is 400 significant lines; this is 5 over it, 1.01× 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.
Duplicated block (10 lines × 2) realm/realm-library/src/main/java/io/realm/Realm.java:1419— realm/realm-library/src/main/java/io/realm/Realm.java:1419-1428 | realm/realm-library/src/main/java/io/realm/Realm.java:1486-1495 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) realm/realm-library/src/main/java/io/realm/RealmObject.java:584— realm/realm-library/src/main/java/io/realm/RealmObject.java:584-593 | realm/realm-library/src/main/java/io/realm/RealmObject.java:676-685 — 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 `realm/realm-library/src/main/java/io/realm/RealmObject.java:584` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `listener` to `RealmObjectChangeListener<E>` in one and `RealmObjectChangeListener` 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.
Duplicated block (10 lines × 2) realm/realm-library/src/main/java/io/realm/RealmQuery.java:177— realm/realm-library/src/main/java/io/realm/RealmQuery.java:177-186 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:192-201 — 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 `realm/realm-library/src/main/java/io/realm/RealmQuery.java:177` 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.
Duplicated block (10 lines × 2) realm/realm-library/src/main/java/io/realm/SetValueOperator.java:1283— realm/realm-library/src/main/java/io/realm/SetValueOperator.java:1283-1292 | realm/realm-library/src/main/java/io/realm/SetValueOperator.java:1398-1407 — 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.
Duplicated block (10 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:177— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:177-186 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:276-285 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `realm` to `Realm` in one and `DynamicRealm` 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.
Duplicated block (10 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:231— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:231-240 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:322-331 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:231` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `realm` to `Realm` in one and `DynamicRealm` 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.
Duplicated block (10 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:367— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:367-376 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:472-481 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:367` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `realm` to `Realm` in one and `DynamicRealm` 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.
Duplicated block (10 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:420— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:420-429 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:525-534 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:420` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `realm` to `Realm` in one and `DynamicRealm` 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.
Duplicated block (10 lines × 2) realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:288— realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:288-297 | realm/realm-library/src/main/java/io/realm/SetValueOperator.java:1616-1625 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:122— examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:122-132 | examples/unitTestExample/src/main/java/io/realm/examples/unittesting/ExampleActivity.java:113-122 — 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 `examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:122` 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: `Person` names `io.realm.examples.intro.model.Person` in one and `io.realm.examples.unittesting.model.Person` in another — different types that share a simple name, which is why the text matched. A single extracted unit cannot be given a parameter type that fits both, so unifying those types (or introducing a shared abstraction over them) is the step that has to come BEFORE the extraction above; if they are deliberately separate, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:121` calls `getPhoneNumbers`, `add` and `examples/unitTestExample/src/main/java/io/realm/examples/unittesting/ExampleActivity.java:112` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
FileTooLong: processor/RealmProxyClassGenerator.kt realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt— FileTooLong — 2691 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: RealmProxyClassGenerator (49-3444). The bar is 500 significant lines; this is 2191 over it, 5.38× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: realm/DynamicRealmObject.java realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java— FileTooLong — 1113 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: DynamicRealmObject (53-1981). The bar is 500 significant lines; this is 613 over it, 2.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: realm/SetValueOperator.java realm/realm-library/src/main/java/io/realm/SetValueOperator.java— FileTooLong — 985 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 485 over it, 1.97× 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: realm/RealmQuery.java realm/realm-library/src/main/java/io/realm/RealmQuery.java— FileTooLong — 932 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 432 over it, 1.86× 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: realm/Realm.java realm/realm-library/src/main/java/io/realm/Realm.java— FileTooLong — 664 significant lines (blank, comment-only and punctuation-only lines excluded), about 92% of them inside a single declaration: Realm (138-2095). The bar is 500 significant lines; this is 164 over it, 1.33× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: objectstore/OsObjectBuilder.java realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java— FileTooLong — 578 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: OsObjectBuilder (76-1065). The bar is 500 significant lines; this is 78 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: realm/RealmList.java realm/realm-library/src/main/java/io/realm/RealmList.java— FileTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: RealmList (64-1354). The bar is 500 significant lines; this is 65 over it, 1.13× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: processor/ClassMetaData.kt realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt— FileTooLong — 531 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 31 over it, 1.06× 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.
Duplicated block (7 lines × 2) realm/realm-library/src/main/java/io/realm/Realm.java:1250— realm/realm-library/src/main/java/io/realm/Realm.java:1250-1256 | realm/realm-library/src/main/java/io/realm/Realm.java:1423-1429 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `realm/realm-library/src/main/java/io/realm/Realm.java:1430` calls `toSet` and `realm/realm-library/src/main/java/io/realm/Realm.java:1257` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) realm/realm-library/src/main/java/io/realm/RealmObject.java:683— realm/realm-library/src/main/java/io/realm/RealmObject.java:683-689 | realm/realm-library/src/main/java/io/realm/RealmObject.java:724-730 — 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 `realm/realm-library/src/main/java/io/realm/RealmObject.java:683` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) realm/realm-library/src/main/java/io/realm/internal/OsList.java:199— realm/realm-library/src/main/java/io/realm/internal/OsList.java:199-205 | realm/realm-library/src/main/java/io/realm/internal/OsResults.java:493-499 — 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 (7 lines × 2) realm/realm-library/src/main/java/io/realm/internal/OsList.java:223— realm/realm-library/src/main/java/io/realm/internal/OsList.java:223-229 | realm/realm-library/src/main/java/io/realm/internal/OsResults.java:501-507 — 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 (7 lines × 2) realm/realm-library/src/main/java/io/realm/internal/OsList.java:247— realm/realm-library/src/main/java/io/realm/internal/OsList.java:247-253 | realm/realm-library/src/main/java/io/realm/internal/OsResults.java:509-515 — 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 (7 lines × 2) realm/realm-library/src/main/java/io/realm/internal/OsList.java:316— realm/realm-library/src/main/java/io/realm/internal/OsList.java:316-322 | realm/realm-library/src/main/java/io/realm/internal/OsResults.java:679-685 — 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 (11 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:509— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:509-519 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:638-648 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:509` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1652— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1652-1662 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2019-2029 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1652` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1691— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1691-1701 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2052-2062 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1691` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:974— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:974-984 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:990-1000 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:974` 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.
Duplicated block (11 lines × 2) examples/gridViewExample/src/main/java/io/realm/examples/realmgridview/CityAdapter.java:86— examples/gridViewExample/src/main/java/io/realm/examples/realmgridview/CityAdapter.java:86-96 | examples/jsonExample/src/main/java/io/realm/examples/json/CityAdapter.java:80-90 — 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 `examples/gridViewExample/src/main/java/io/realm/examples/realmgridview/CityAdapter.java:86` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×4
Edited copy of a member (13 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/OsList.java:26— realm/realm-library/src/main/java/io/realm/internal/OsList.java:26-39 | realm/realm-library/src/main/java/io/realm/internal/OsSet.java:53-65 — 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.
Edited copy of a member (13 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmList.java:166— realm/realm-library/src/main/java/io/realm/RealmList.java:166-182 | realm/realm-library/src/main/java/io/realm/RealmResults.java:628-640 — 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.
Edited copy of a member (13 corresponding lines) realm/realm-library/src/main/java/io/realm/MutableRealmSchema.java:48— realm/realm-library/src/main/java/io/realm/MutableRealmSchema.java:48-60 | realm/realm-library/src/main/java/io/realm/internal/Util.java:168-182 — 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.
Edited copy of a member (13 corresponding lines) examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:277— examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:277-289 | examples/unitTestExample/src/main/java/io/realm/examples/unittesting/ExampleActivity.java:145-160 — 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· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:307— realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:307-316 | realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:326-335 | realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:345-354 | realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:364-373 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:584— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:584-616 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:629-661 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:674-707 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:720-752 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:155— realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:155-200 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:255-300 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:355-402 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:456-503 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×3
Edited copy of a member (20 corresponding lines) realm/kotlin-extensions/src/main/kotlin/io/realm/kotlin/RealmObjectExtensions.kt:58— realm/kotlin-extensions/src/main/kotlin/io/realm/kotlin/RealmObjectExtensions.kt:58-77 | realm/kotlin-extensions/src/main/kotlin/io/realm/kotlin/RealmObjectExtensions.kt:117-136 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmObject.java:582— realm/realm-library/src/main/java/io/realm/RealmObject.java:582-601 | realm/realm-library/src/main/java/io/realm/RealmObject.java:674-695 — These two members are one piece of code written twice and then edited apart: 20 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 (20 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/TableQuery.java:344— realm/realm-library/src/main/java/io/realm/internal/TableQuery.java:344-363 | realm/realm-library/src/main/java/io/realm/internal/TableQuery.java:365-384 — These two members are one piece of code written twice and then edited apart: 20 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 (21 corresponding lines) · ×3
Edited copy of a member (21 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmSchema.java:165— realm/realm-library/src/main/java/io/realm/RealmSchema.java:165-186 | realm/realm-library/src/main/java/io/realm/RealmSchema.java:189-209 — These two members are one piece of code written twice and then edited apart: 21 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 (21 corresponding lines) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:458— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:458-478 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:481-501 — These two members are one piece of code written twice and then edited apart: 21 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 (21 corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealm.java:301— realm/realm-library/src/main/java/io/realm/DynamicRealm.java:301-321 | realm/realm-library/src/main/java/io/realm/Realm.java:1623-1643 — These two members are one piece of code written twice and then edited apart: 21 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 (15 corresponding lines) · ×3
Edited copy of a member (15 corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:491— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:491-505 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:518-533 — These two members are one piece of code written twice and then edited apart: 15 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 (15 corresponding lines) realm/realm-annotations-processor/src/main/java/io/realm/processor/ModuleMetaData.kt:386— realm/realm-annotations-processor/src/main/java/io/realm/processor/ModuleMetaData.kt:386-403 | realm/realm-annotations-processor/src/main/java/io/realm/processor/ModuleMetaData.kt:411-425 — These two members are one piece of code written twice and then edited apart: 15 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 (15 corresponding lines) examples/threadExample/src/main/java/io/realm/examples/threads/ReceivingService.java:34— examples/threadExample/src/main/java/io/realm/examples/threads/ReceivingService.java:34-48 | examples/threadExample/src/main/java/io/realm/examples/threads/WakefulReceivingService.java:35-52 — These two members are one piece of code written twice and then edited apart: 15 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 (16 corresponding lines) · ×3
Edited copy of a member (16 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmList.java:481— realm/realm-library/src/main/java/io/realm/RealmList.java:481-496 | realm/realm-library/src/main/java/io/realm/RealmList.java:517-532 — These two members are one piece of code written twice and then edited apart: 16 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 (16 corresponding lines) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmJsonTypeHelper.kt:83— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmJsonTypeHelper.kt:83-98 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmJsonTypeHelper.kt:108-127 — These two members are one piece of code written twice and then edited apart: 16 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 (16 corresponding lines) examples/gridViewExample/src/main/java/io/realm/examples/realmgridview/CityAdapter.java:81— examples/gridViewExample/src/main/java/io/realm/examples/realmgridview/CityAdapter.java:81-96 | examples/jsonExample/src/main/java/io/realm/examples/json/CityAdapter.java:74-90 — These two members are one piece of code written twice and then edited apart: 16 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.
Duplicated block (23 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:102— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:102-124 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:151-173 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:102` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `realm` to `Realm` in one and `DynamicRealm` 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.
Duplicated block (23 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1529— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1529-1551 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1897-1919 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1529` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1528` calls `getRealmDictionaryElementTypeMirror` and `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1896` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (23 lines × 2) realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:47— realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:47-69 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:80-102 — 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 `realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:47` 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.
Duplicated block (17 lines × 2) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1378— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1378-1394 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1516-1532 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) realm/realm-library/src/main/java/io/realm/ProxyUtils.java:517— realm/realm-library/src/main/java/io/realm/ProxyUtils.java:517-533 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:537-553 — 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.
Duplicated block (17 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1704— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1704-1720 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2066-2082 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) realm/realm-library/src/main/java/io/realm/ProxyUtils.java:466— realm/realm-library/src/main/java/io/realm/ProxyUtils.java:466-478 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:493-505 — 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 `realm/realm-library/src/main/java/io/realm/ProxyUtils.java:466` 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 (13 lines × 2) examples/threadExample/src/main/java/io/realm/examples/threads/ReceivingService.java:35— examples/threadExample/src/main/java/io/realm/examples/threads/ReceivingService.java:35-47 | examples/threadExample/src/main/java/io/realm/examples/threads/WakefulReceivingService.java:36-48 — before extracting anything, compare `examples/threadExample/src/main/java/io/realm/examples/threads/ReceivingService.java` and `examples/threadExample/src/main/java/io/realm/examples/threads/WakefulReceivingService.java` as WHOLE FILES: 86% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `examples/threadExample/src/main/java/io/realm/examples/threads/WakefulReceivingService.java:51` calls `completeWakefulIntent` and `examples/threadExample/src/main/java/io/realm/examples/threads/ReceivingService.java:48` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) examples/compatibilityExample/src/main/java/io/realm/examples/compatibility/MyApplication.kt:32— examples/compatibilityExample/src/main/java/io/realm/examples/compatibility/MyApplication.kt:32-44 | examples/mongoDbRealmExample/src/main/java/com/mongodb/realm/example/MyApplication.kt:32-44 — before extracting anything, compare `examples/compatibilityExample/src/main/java/io/realm/examples/compatibility/MyApplication.kt` and `examples/mongoDbRealmExample/src/main/java/com/mongodb/realm/example/MyApplication.kt` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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. 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· Edited copy of a member (32 corresponding lines) · ×2
Edited copy of a member (32 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/OsObject.java:193— realm/realm-library/src/main/java/io/realm/internal/OsObject.java:193-224 | realm/realm-library/src/main/java/io/realm/internal/OsObject.java:237-269 — These two members are one piece of code written twice and then edited apart: 32 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 (32 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:128— realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:128-159 | realm/realm-library/src/main/java/io/realm/RealmSet.java:747-782 — These two members are one piece of code written twice and then edited apart: 32 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 (23 corresponding lines) · ×2
Edited copy of a member (23 corresponding lines) realm/realm-library/src/main/java/io/realm/TypeSelectorForMap.java:146— realm/realm-library/src/main/java/io/realm/TypeSelectorForMap.java:146-168 | realm/realm-library/src/main/java/io/realm/TypeSelectorForMap.java:197-219 — These two members are one piece of code written twice and then edited apart: 23 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 (23 corresponding lines) realm/realm-library/src/main/java/io/realm/Realm.java:763— realm/realm-library/src/main/java/io/realm/Realm.java:763-787 | realm/realm-library/src/main/java/io/realm/Realm.java:1027-1049 — These two members are one piece of code written twice and then edited apart: 23 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) · ×2
Edited copy of a member (19 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmObject.java:859— realm/realm-library/src/main/java/io/realm/RealmObject.java:859-879 | realm/realm-library/src/main/java/io/realm/RealmObject.java:912-930 — 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.
Edited copy of a member (19 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:456— realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:456-475 | realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:871-889 — 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 copy of a member (11 corresponding lines) · ×2
Edited copy of a member (11 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmList.java:996— realm/realm-library/src/main/java/io/realm/RealmList.java:996-1006 | realm/realm-library/src/main/java/io/realm/RealmResults.java:879-889 — 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) realm/realm-library/src/main/java/io/realm/RealmList.java:955— realm/realm-library/src/main/java/io/realm/RealmList.java:955-965 | realm/realm-library/src/main/java/io/realm/RealmResults.java:834-848 — 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 (14 corresponding lines) · ×2
Edited copy of a member (14 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmQuery.java:173— realm/realm-library/src/main/java/io/realm/RealmQuery.java:173-186 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:188-201 — 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.
Edited copy of a member (14 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmQuery.java:143— realm/realm-library/src/main/java/io/realm/RealmQuery.java:143-156 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:158-171 — 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 (9 corresponding lines) · ×2
Edited copy of a member (9 corresponding lines) realm/realm-library/src/main/java/io/realm/rx/CollectionChange.java:84— realm/realm-library/src/main/java/io/realm/rx/CollectionChange.java:84-92 | realm/realm-library/src/main/java/io/realm/rx/ObjectChange.java:79-87 — 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.
Edited copy of a member (9 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:115— realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:115-125 | realm/realm-library/src/main/java/io/realm/RealmSet.java:735-743 — 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 (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) realm/realm-annotations-processor/src/main/java/io/realm/processor/nameconverter/CamelCaseConverter.kt:25— realm/realm-annotations-processor/src/main/java/io/realm/processor/nameconverter/CamelCaseConverter.kt:25-42 | realm/realm-annotations-processor/src/main/java/io/realm/processor/nameconverter/PascalCaseConverter.kt:25-36 — These two members are one piece of code written twice and then edited apart: 12 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 (12 corresponding lines) examples/architectureComponentsExample/src/main/java/io/realm/examples/arch/livemodel/LiveRealmObject.java:64— examples/architectureComponentsExample/src/main/java/io/realm/examples/arch/livemodel/LiveRealmObject.java:64-76 | realm/realm-library/src/main/java/io/realm/Realm.java:1887-1898 — These two members are one piece of code written twice and then edited apart: 12 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 (4 members, 15+ corresponding lines) · ×2
Edited copies of one member (4 members, 15+ corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:544— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:544-558 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:571-586 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:597-611 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:624-639 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 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 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 15+ corresponding lines) realm/realm-library/src/main/java/io/realm/Realm.java:640— realm/realm-library/src/main/java/io/realm/Realm.java:640-654 | realm/realm-library/src/main/java/io/realm/Realm.java:679-695 | realm/realm-library/src/main/java/io/realm/Realm.java:883-897 | realm/realm-library/src/main/java/io/realm/Realm.java:923-939 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×2
Edited copy of a member (6 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmAnyOperator.java:181— realm/realm-library/src/main/java/io/realm/RealmAnyOperator.java:181-186 | realm/realm-library/src/main/java/io/realm/RealmAnyOperator.java:418-423 — 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) realm/realm-library/src/main/java/io/realm/RealmAnyOperator.java:236— realm/realm-library/src/main/java/io/realm/RealmAnyOperator.java:236-241 | realm/realm-library/src/main/java/io/realm/RealmAnyOperator.java:304-309 — 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 (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscriptionSet.java:149— realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscriptionSet.java:149-166 | realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscriptionSet.java:195-212 — 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.
Edited copy of a member (18 corresponding lines) examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:141— examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:141-158 | examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:160-179 — 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 copies of one member (3 members, 9+ corresponding lines) · ×2
Edited copies of one member (3 members, 9+ corresponding lines) realm/realm-library/src/main/java/io/realm/internal/CheckedRow.java:112— realm/realm-library/src/main/java/io/realm/internal/CheckedRow.java:112-120 | realm/realm-library/src/main/java/io/realm/internal/CheckedRow.java:145-153 | realm/realm-library/src/main/java/io/realm/internal/CheckedRow.java:166-174 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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.
Edited copies of one member (3 members, 9+ corresponding lines) realm/realm-library/src/main/java/io/realm/RealmQuery.java:203— realm/realm-library/src/main/java/io/realm/RealmQuery.java:203-211 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:213-221 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:223-231 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 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 copy of a member (8 corresponding lines) · ×2
Edited copy of a member (8 corresponding lines) realm/realm-library/src/main/java/io/realm/ImmutableRealmSchema.java:41— realm/realm-library/src/main/java/io/realm/ImmutableRealmSchema.java:41-48 | realm/realm-library/src/main/java/io/realm/MutableRealmSchema.java:38-45 — These two members are one piece of code written twice and then edited apart: 8 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 (8 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/TableQuery.java:451— realm/realm-library/src/main/java/io/realm/internal/TableQuery.java:451-459 | realm/realm-library/src/main/java/io/realm/internal/UncheckedRow.java:170-177 — These two members are one piece of code written twice and then edited apart: 8 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 (7 corresponding lines) · ×2
Edited copy of a member (7 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/OsList.java:191— realm/realm-library/src/main/java/io/realm/internal/OsList.java:191-197 | realm/realm-library/src/main/java/io/realm/internal/UncheckedRow.java:338-345 — 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) realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java:567— realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java:567-573 | realm/realm-library/src/main/java/io/realm/RealmList.java:823-832 — 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.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×2
Edited copy of a member (5 corresponding lines) realm/realm-library/src/main/java/io/realm/rx/CollectionChange.java:95— realm/realm-library/src/main/java/io/realm/rx/CollectionChange.java:95-99 | realm/realm-library/src/main/java/io/realm/rx/ObjectChange.java:90-94 — 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) realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:432— realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:432-436 | realm/realm-library/src/main/java/io/realm/RealmObjectSchema.java:746-750 — 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.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×2
Edited copy of a member (4 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/modules/CompositeMediator.java:144— realm/realm-library/src/main/java/io/realm/internal/modules/CompositeMediator.java:144-147 | realm/realm-library/src/main/java/io/realm/internal/modules/FilterableMediator.java:159-162 — 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) realm/realm-library/src/main/java/io/realm/internal/modules/CompositeMediator.java:156— realm/realm-library/src/main/java/io/realm/internal/modules/CompositeMediator.java:156-159 | realm/realm-library/src/main/java/io/realm/internal/modules/FilterableMediator.java:171-174 — 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.
Duplicated block (35 lines × 2) realm/realm-library/src/main/java/io/realm/DynamicRealm.java:384— realm/realm-library/src/main/java/io/realm/DynamicRealm.java:384-418 | realm/realm-library/src/main/java/io/realm/Realm.java:1706-1740 — 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 `realm/realm-library/src/main/java/io/realm/DynamicRealm.java:384` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `onError` to `Transaction.OnError` in one and `Realm.Transaction.OnError` 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.
Duplicated block (35 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:434— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:434-468 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:539-573 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:434` 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.
Duplicated block (29 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:191— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:191-219 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:290-318 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:191` 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.
Duplicated block (29 lines × 2) realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:577— realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:577-605 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:682-710 — 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 `realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:577` 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.
Duplicated block (15 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:258— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:258-272 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:349-363 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:258` 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.
Duplicated block (15 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:649— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:649-663 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:740-754 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:649` 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.
Duplicated block (14 lines × 4) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:199— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:199-212 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:253-266 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:298-311 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:344-357 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:199` 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 (14 lines × 4) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:396— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:396-409 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:449-462 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:501-514 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:554-567 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:396` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1148— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1148-1159 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1341-1352 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1479-1490 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1148` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 3) realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:150— realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:150-161 | realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:169-180 | realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:204-215 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:150` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 3) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:340— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:340-350 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:445-455 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:550-560 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:340` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 3) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:599— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:599-609 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:644-654 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:689-699 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:599` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 3) realm/realm-library/src/main/java/io/realm/RealmQuery.java:144— realm/realm-library/src/main/java/io/realm/RealmQuery.java:144-152 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:174-182 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:189-197 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/RealmQuery.java:144` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `realm` to `Realm` in one and `BaseRealm` 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.
Duplicated block (9 lines × 3) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:535— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:535-543 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:664-673 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:780-789 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:535` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) realm/realm-library/src/main/java/io/realm/TypeSelectorForMap.java:158— realm/realm-library/src/main/java/io/realm/TypeSelectorForMap.java:158-165 | realm/realm-library/src/main/java/io/realm/TypeSelectorForMap.java:209-216 — 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 `realm/realm-library/src/main/java/io/realm/TypeSelectorForMap.java:158` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note first that the copies are not typed on the same thing: the declarations holding them bind `value` to `V` in one and `DynamicRealmObject` 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.
Duplicated block (8 lines × 2) examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:151— examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:151-158 | examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:172-179 — 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 `examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:151` 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 × 4) realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:308— realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:308-313 | realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:327-332 | realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:346-351 | realm/realm-library/src/main/java/io/realm/RealmMapEntrySet.java:365-370 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6 lines × 4) examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:101— examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:101-106 | examples/migrationExample/src/main/java/io/realm/examples/realmmigrationexample/MigrationExampleActivity.java:135-140 | examples/moduleExample/app/src/main/java/io/realm/examples/appmodules/ModulesExampleActivity.java:170-175 | examples/unitTestExample/src/main/java/io/realm/examples/unittesting/ExampleActivity.java:96-101 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 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 4 times. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `examples/introExample/src/main/java/io/realm/examples/intro/IntroExampleActivity.java:97` calls `removeAllChangeListeners` and `examples/unitTestExample/src/main/java/io/realm/examples/unittesting/ExampleActivity.java:92` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:618— realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:618-623 | realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:641-646 — 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 `realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:618` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) examples/rxJavaExample/src/main/java/io/realm/examples/rxjava/animation/AnimationActivity.java:40— examples/rxJavaExample/src/main/java/io/realm/examples/rxjava/animation/AnimationActivity.java:40-45 | REDACTED:58-63 — 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 (25–26 lines × 4) realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:125— realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:125-150 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:225-250 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:326-350 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:427-451 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:125` 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.
Duplicated block (25–26 lines × 4) realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:175— realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:175-200 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:275-300 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:378-402 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:479-503 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:175` 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.
Swallowed exception (caught, then discarded) realm-transformer/src/main/kotlin/io/realm/transformer/ext/ProjectExt.kt:71— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) realm-transformer/src/main/kotlin/io/realm/analytics/ComputerIdentifierGenerator.kt:49— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (empty catch) realm-transformer/src/main/kotlin/io/realm/analytics/UrlEncodedAnalytics.kt:38— 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.
Swallowed exception (empty catch) realm/realm-library/src/main/java/io/realm/internal/RealmCore.java:94— 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.
RealmProxyClassGenerator.emitCreateExpectedObjectSchemaInfo (cyclomatic 63) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1017— RealmProxyClassGenerator.emitCreateExpectedObjectSchemaInfo has cyclomatic complexity 63 (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.
DynamicRealmObject.toString (cyclomatic 61) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1716— DynamicRealmObject.toString has cyclomatic complexity 61 (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.
ProxyUtils.createRealmListWithJsonStream (cyclomatic 55) realm/realm-library/src/main/java/io/realm/ProxyUtils.java:228— ProxyUtils.createRealmListWithJsonStream has cyclomatic complexity 55 (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.
ProxyUtils.setRealmListWithJsonObject (cyclomatic 51) realm/realm-library/src/main/java/io/realm/ProxyUtils.java:57— ProxyUtils.setRealmListWithJsonObject has cyclomatic complexity 51 (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.
ClassMetaData.categorizeField (cyclomatic 42) realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt:632— ClassMetaData.categorizeField has cyclomatic complexity 42 (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.
RealmProxyClassGenerator.setTableValues (cyclomatic 33) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1298— RealmProxyClassGenerator.setTableValues has cyclomatic complexity 33 (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.
ISO8601Utils.parse (cyclomatic 31) realm/realm-library/src/main/java/io/realm/internal/android/ISO8601Utils.java:68— ISO8601Utils.parse has cyclomatic complexity 31 (threshold 15). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
RealmResults.setValue (cyclomatic 29) realm/realm-library/src/main/java/io/realm/RealmResults.java:173— RealmResults.setValue has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RealmConfiguration.equals (cyclomatic 26) realm/realm-library/src/main/java/io/realm/RealmConfiguration.java:344— RealmConfiguration.equals has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OsRealmConfig.<init> (cyclomatic 24) realm/realm-library/src/main/java/io/realm/internal/OsRealmConfig.java:214— OsRealmConfig.<init> has cyclomatic complexity 24 (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.
RealmProxyClassGenerator.emitCreateOrUpdateUsingJsonObject (cyclomatic 21) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2996— RealmProxyClassGenerator.emitCreateOrUpdateUsingJsonObject has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RealmAny.valueOf (cyclomatic 19) realm/realm-library/src/main/java/io/realm/RealmAny.java:486— RealmAny.valueOf has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OsMap.put (cyclomatic 18) realm/realm-library/src/main/java/io/realm/internal/OsMap.java:157— OsMap.put has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RealmProxyClassGenerator.emitInsertInternal (cyclomatic 18) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1437— RealmProxyClassGenerator.emitInsertInternal has cyclomatic complexity 18 (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.
RealmProxyClassGenerator.insertOrUpdateInternal (cyclomatic 18) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1730— RealmProxyClassGenerator.insertOrUpdateInternal has cyclomatic complexity 18 (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.
RealmProxyClassGenerator.emitUpdateMethod (cyclomatic 18) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2576— RealmProxyClassGenerator.emitUpdateMethod has cyclomatic complexity 18 (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.
WordTokenizer.split (cyclomatic 18) realm/realm-annotations-processor/src/main/java/io/realm/processor/nameconverter/WordTokenizer.kt:51— WordTokenizer.split has cyclomatic complexity 18 (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.
DynamicRealmObject.setValue (cyclomatic 17) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:837— DynamicRealmObject.setValue has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: DynamicRealmObject.get (cyclomatic 39) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
RealmSet.getStrategy (cyclomatic 17) realm/realm-library/src/main/java/io/realm/RealmSet.java:489— RealmSet.getStrategy has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SetValueOperator.iteratorFactory (cyclomatic 17) realm/realm-library/src/main/java/io/realm/SetValueOperator.java:322— SetValueOperator.iteratorFactory has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OsMap.containsPrimitiveValue (cyclomatic 16) realm/realm-library/src/main/java/io/realm/internal/OsMap.java:91— OsMap.containsPrimitiveValue has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RealmList.toString (cyclomatic 16) realm/realm-library/src/main/java/io/realm/RealmList.java:835— RealmList.toString has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ClassMetaData.generate (cyclomatic 16) realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt:312— ClassMetaData.generate has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
HackComment realm/realm-library/src/main/java/io/realm/internal/RealmCore.java:109— // Hack for having a cross platform location for the lib: — 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.
ProxyUtils.createRealmListWithJsonStream (cognitive 122) realm/realm-library/src/main/java/io/realm/ProxyUtils.java:228— ProxyUtils.createRealmListWithJsonStream has cognitive complexity 122 (threshold 15). Drivers by points: if/else 55 (90 pts), loops 16 (32 pts) (nesting depth added 51). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: realm/realm-library/src/main/java/io/realm/ProxyUtils.java holds 2 of the 34 methods over the threshold — including the worst — and 197 of the 571 points over it (35%), 2.5× the next-largest file (realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt at 79). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ProxyUtils.setRealmListWithJsonObject (cognitive 105) realm/realm-library/src/main/java/io/realm/ProxyUtils.java:57— ProxyUtils.setRealmListWithJsonObject has cognitive complexity 105 (threshold 15). Drivers by points: if/else 50 (82 pts), loops 11 (22 pts), boolean chains 1 (nesting depth added 43). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This file is where this pass's cognitive complexity CONCENTRATES: realm/realm-library/src/main/java/io/realm/ProxyUtils.java holds 2 of the 34 methods over the threshold — including the worst — and 197 of the 571 points over it (35%), 2.5× the next-largest file (realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt at 79). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
ClassMetaData.categorizeField (cognitive 61) realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt:632— ClassMetaData.categorizeField has cognitive complexity 61 (threshold 15). Drivers by points: if/else 28 (46 pts), boolean chains 15 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OsRealmConfig.<init> (cognitive 55) realm/realm-library/src/main/java/io/realm/internal/OsRealmConfig.java:214— OsRealmConfig.<init> has cognitive complexity 55 (threshold 15). Drivers by points: if/else 18 (39 pts), error handling 2 (5 pts), match/switch 1 (5 pts), boolean chains 2, loops 1 (2 pts), ternaries 2 (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ISO8601Utils.parse (cognitive 53) realm/realm-library/src/main/java/io/realm/internal/android/ISO8601Utils.java:68— ISO8601Utils.parse has cognitive complexity 53 (threshold 15). Drivers by points: if/else 20 (38 pts), boolean chains 6, match/switch 1 (5 pts), error handling 3, ternaries 1 (nesting depth added 22). This file's own header attributes it to another copyright holder, so it is code this repository carries rather than code it wrote: restructuring the body in place forks it from upstream and turns every future re-sync into a manual merge. The performable moves are to leave the body as close to its upstream form as possible and keep it behind a narrow interface of your own, and to re-sync it when upstream changes — or, if it has already diverged far enough that you maintain it here, adopt it deliberately and then split the body into named stages.
ModuleMetaData.validateNamingPolicies (cognitive 40) realm/realm-annotations-processor/src/main/java/io/realm/processor/ModuleMetaData.kt:122— ModuleMetaData.validateNamingPolicies has cognitive complexity 40 (threshold 15). Drivers by points: if/else 8 (24 pts), loops 6 (16 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmList.toString (cognitive 37) realm/realm-library/src/main/java/io/realm/RealmList.java:835— RealmList.toString has cognitive complexity 37 (threshold 15). Drivers by points: if/else 17 (29 pts), loops 3 (8 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmProxyClassGenerator.emitCreateExpectedObjectSchemaInfo (cognitive 35) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1017— RealmProxyClassGenerator.emitCreateExpectedObjectSchemaInfo has cognitive complexity 35 (threshold 15). Drivers by points: if/else 18 (31 pts), loops 2, match/switch 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DynamicRealmObject.toString (cognitive 34) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1716— DynamicRealmObject.toString has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 10 (30 pts), match/switch 1 (2 pts), if/else 1, loops 1 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmConfiguration.equals (cognitive 32) realm/realm-library/src/main/java/io/realm/RealmConfiguration.java:344— RealmConfiguration.equals has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17, ternaries 7 (14 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
RealmProxyClassGenerator.emitCreateOrUpdateUsingJsonObject (cognitive 28) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2996— RealmProxyClassGenerator.emitCreateOrUpdateUsingJsonObject has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (24 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
CollectionUtils.copyToRealmIfNeeded (cognitive 27) realm/realm-library/src/main/java/io/realm/CollectionUtils.java:115— CollectionUtils.copyToRealmIfNeeded has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (26 pts), boolean chains 1 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
RealmProxyClassGenerator.addPrimaryKeyCheckIfNeeded (cognitive 26) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2092— RealmProxyClassGenerator.addPrimaryKeyCheckIfNeeded has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (25 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OsMap.put (cognitive 24) realm/realm-library/src/main/java/io/realm/internal/OsMap.java:157— OsMap.put has cognitive complexity 24 (threshold 15). Drivers by points: if/else 19 (22 pts), error handling 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RealmCache.release (cognitive 24) realm/realm-library/src/main/java/io/realm/RealmCache.java:529— RealmCache.release has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (9 pts), ternaries 1 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
RealmFieldType.fromNativeValue (cognitive 24) realm/realm-library/src/main/java/io/realm/RealmFieldType.java:257— RealmFieldType.fromNativeValue has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmProxyClassGenerator.setTableValues (cognitive 24) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1298— RealmProxyClassGenerator.setTableValues has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (23 pts), match/switch 1 (nesting depth added 11). 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.
WordTokenizer.split (cognitive 24) realm/realm-annotations-processor/src/main/java/io/realm/processor/nameconverter/WordTokenizer.kt:51— WordTokenizer.split has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 8, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmResults.setValue (cognitive 23) realm/realm-library/src/main/java/io/realm/RealmResults.java:173— RealmResults.setValue has cognitive complexity 23 (threshold 15). Drivers by points: if/else 19, match/switch 1 (2 pts), boolean chains 1, ternaries 1 (nesting depth added 1). 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.
RealmProxyClassGenerator.emitInsertInternal (cognitive 23) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1437— RealmProxyClassGenerator.emitInsertInternal has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmProxyClassGenerator.insertOrUpdateInternal (cognitive 23) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1730— RealmProxyClassGenerator.insertOrUpdateInternal has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (20 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OsObject.createRowWithPrimaryKey (cognitive 20) realm/realm-library/src/main/java/io/realm/internal/OsObject.java:237— OsObject.createRowWithPrimaryKey has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (11 pts), ternaries 3 (6 pts), boolean chains 3 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OrderedRealmCollectionImpl.contains (cognitive 20) realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java:100— OrderedRealmCollectionImpl.contains has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmAny.valueOf (cognitive 20) realm/realm-library/src/main/java/io/realm/RealmAny.java:486— RealmAny.valueOf has cognitive complexity 20 (threshold 15). Drivers by points: if/else 18 (19 pts), boolean chains 1 (nesting depth added 1). 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.
RealmProxyClassGenerator.emitUpdateMethod (cognitive 20) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2576— RealmProxyClassGenerator.emitUpdateMethod has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (16 pts), match/switch 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CollectionUtils.checkCanObjectBeCopied (cognitive 19) realm/realm-library/src/main/java/io/realm/CollectionUtils.java:67— CollectionUtils.checkCanObjectBeCopied has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FilterableMediator.<init> (cognitive 18) realm/realm-library/src/main/java/io/realm/internal/modules/FilterableMediator.java:71— FilterableMediator.<init> has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (6 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmProxyClassGenerator.emitCopyMethod (cognitive 18) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2173— RealmProxyClassGenerator.emitCopyMethod has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DynamicRealmObject.setValue (cognitive 17) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:837— DynamicRealmObject.setValue has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. 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.
Realm.checkFilesDirAvailable (cognitive 17) realm/realm-library/src/main/java/io/realm/Realm.java:382— Realm.checkFilesDirAvailable has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 3, error handling 1 (3 pts), loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmSet.getStrategy (cognitive 17) realm/realm-library/src/main/java/io/realm/RealmSet.java:489— RealmSet.getStrategy has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. 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.
SetValueOperator.iteratorFactory (cognitive 17) realm/realm-library/src/main/java/io/realm/SetValueOperator.java:322— SetValueOperator.iteratorFactory has cognitive complexity 17 (threshold 15). Drivers by points: if/else 17. 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.
RealmProcessor.process (cognitive 17) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProcessor.kt:164— RealmProcessor.process has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (17 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RealmProxyClassGenerator.emitCopyOrUpdateMethod (cognitive 17) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1191— RealmProxyClassGenerator.emitCopyOrUpdateMethod has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (17 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Near-duplicate member pair (61 shared lines) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1437— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1437-1648 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1730-2015 — These two members are variants of one another: 61 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (10 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (10 members, 50+ identical tokens) realm/realm-library/src/main/java/io/realm/RealmQuery.java:535— realm/realm-library/src/main/java/io/realm/RealmQuery.java:535-557 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:568-581 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:592-605 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:616-629 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:641-654 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:666-679 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:690-703 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:715-728 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:739-752 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:763-777 — These 10 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 10 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 10 times.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (6 members, 50+ identical tokens) realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:39— realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:39-69 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:72-102 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:105-150 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:205-250 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:303-350 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:404-451 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (5 members, 50+ identical tokens) realm/realm-library/src/main/java/io/realm/ProxyUtils.java:438— realm/realm-library/src/main/java/io/realm/ProxyUtils.java:438-461 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:464-488 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:491-513 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:516-533 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:536-553 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (115 corresponding lines) · ×1
Edited copy of a member (115 corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealm.java:383— realm/realm-library/src/main/java/io/realm/DynamicRealm.java:383-497 | realm/realm-library/src/main/java/io/realm/Realm.java:1705-1819 — These two members are one piece of code written twice and then edited apart: 115 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 (37 corresponding lines) · ×1
Edited copy of a member (37 corresponding lines) realm/realm-library/src/main/java/io/realm/RealmSet.java:491— realm/realm-library/src/main/java/io/realm/RealmSet.java:491-533 | realm/realm-library/src/main/java/io/realm/RealmSet.java:538-574 — These two members are one piece of code written twice and then edited apart: 37 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 (46 corresponding lines) · ×1
Edited copy of a member (46 corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1280— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1280-1325 | realm/realm-library/src/main/java/io/realm/RealmList.java:1305-1353 — These two members are one piece of code written twice and then edited apart: 46 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 (82 corresponding lines) · ×1
Edited copy of a member (82 corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealm.java:412— realm/realm-library/src/main/java/io/realm/DynamicRealm.java:412-493 | realm/realm-library/src/main/java/io/realm/Realm.java:1734-1815 — These two members are one piece of code written twice and then edited apart: 82 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 (50 corresponding lines) · ×1
Edited copy of a member (50 corresponding lines) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:419— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:419-468 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:524-573 — These two members are one piece of code written twice and then edited apart: 50 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 (51 corresponding lines) · ×1
Edited copy of a member (51 corresponding lines) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:366— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:366-416 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:471-521 — These two members are one piece of code written twice and then edited apart: 51 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, 46+ corresponding lines) · ×1
Edited copies of one member (3 members, 46+ corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1192— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1192-1238 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1375-1422 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1513-1558 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 46 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, 35+ corresponding lines) · ×1
Edited copies of one member (3 members, 35+ corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1241— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1241-1278 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1425-1463 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1561-1595 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 35 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 (4 members, 43+ corresponding lines) · ×1
Edited copies of one member (4 members, 43+ corresponding lines) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:230— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:230-272 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:321-363 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:621-663 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:712-754 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 43 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:427— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:427-466 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:532-571 — These two members are one piece of code written twice and then edited apart: 40 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 (6 members, 37+ corresponding lines) · ×1
Edited copies of one member (6 members, 37+ corresponding lines) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:88— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:88-124 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:137-173 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:176-219 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:275-318 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:576-618 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:666-709 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 37 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:374— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:374-414 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:479-519 — These two members are one piece of code written twice and then edited apart: 41 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 (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:352— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:352-399 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:408-455 — These two members are one piece of code written twice and then edited apart: 48 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 (4 members, 33+ corresponding lines) · ×1
Edited copies of one member (4 members, 33+ corresponding lines) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:184— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:184-217 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:238-270 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:283-316 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:329-361 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 33 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 48+ corresponding lines) · ×1
Edited copies of one member (3 members, 48+ corresponding lines) realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:506— realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:506-553 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:558-605 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:663-710 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 48 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, 31+ corresponding lines) · ×1
Edited copies of one member (3 members, 31+ corresponding lines) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1690— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1690-1727 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2018-2048 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2051-2089 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 31 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 copy of a member (27 corresponding lines) · ×1
Edited copy of a member (27 corresponding lines) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:96— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:96-122 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:145-171 — These two members are one piece of code written twice and then edited apart: 27 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 (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1340— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1340-1373 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1478-1511 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×1
Edited copies of one member (3 members, 14+ corresponding lines) realm/realm-library/src/main/java/io/realm/ManagedListOperator.java:209— realm/realm-library/src/main/java/io/realm/ManagedListOperator.java:209-222 | realm/realm-library/src/main/java/io/realm/ManagedListOperator.java:230-245 | realm/realm-library/src/main/java/io/realm/ManagedListOperator.java:253-266 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 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 copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:291— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:291-319 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:322-349 — These two members are one piece of code written twice and then edited apart: 28 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, 19+ corresponding lines) · ×1
Edited copies of one member (3 members, 19+ corresponding lines) realm/realm-library/src/main/java/io/realm/Realm.java:1245— realm/realm-library/src/main/java/io/realm/Realm.java:1245-1263 | realm/realm-library/src/main/java/io/realm/Realm.java:1417-1437 | realm/realm-library/src/main/java/io/realm/Realm.java:1483-1503 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 19 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, 17+ corresponding lines) · ×1
Edited copies of one member (3 members, 17+ corresponding lines) realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:145— realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:145-161 | realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:164-180 | realm/realm-library/src/main/java/io/realm/MutableRealmObjectSchema.java:199-215 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 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 copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscriptionSet.java:146— realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscriptionSet.java:146-169 | realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscriptionSet.java:192-215 — These two members are one piece of code written twice and then edited apart: 24 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 (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:617— realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:617-633 | realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:850-866 — 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 copies of one member (4 members, 17+ corresponding lines) · ×1
Edited copies of one member (4 members, 17+ corresponding lines) realm/realm-library/src/main/java/io/realm/RealmQuery.java:2204— realm/realm-library/src/main/java/io/realm/RealmQuery.java:2204-2224 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:2237-2253 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:2304-2322 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:2372-2390 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 17 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 14+ corresponding lines) · ×1
Edited copies of one member (6 members, 14+ corresponding lines) realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:51— realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:51-64 | realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:128-141 | realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:143-157 | realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:159-175 | realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:177-191 | realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:193-208 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 14 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 14+ corresponding lines) · ×1
Edited copies of one member (5 members, 14+ corresponding lines) realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:36— realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:36-49 | realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:66-79 | realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:81-94 | realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:96-110 | realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:112-126 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 14 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:375— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:375-385 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:394-404 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:413-423 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:448-458 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×1
Edited copies of one member (3 members, 16+ corresponding lines) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmJsonTypeHelper.kt:292— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmJsonTypeHelper.kt:292-307 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmJsonTypeHelper.kt:379-394 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmJsonTypeHelper.kt:428-443 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 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 (6 members, 9+ corresponding lines) · ×1
Edited copies of one member (6 members, 9+ corresponding lines) realm/realm-library/src/main/java/io/realm/RealmQuery.java:319— realm/realm-library/src/main/java/io/realm/RealmQuery.java:319-327 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:815-823 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:1665-1673 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:1724-1732 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:1783-1791 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:1858-1866 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 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 6 times and the copies 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) realm/realm-library/src/main/java/io/realm/Realm.java:566— realm/realm-library/src/main/java/io/realm/Realm.java:566-580 | realm/realm-library/src/main/java/io/realm/Realm.java:605-619 | realm/realm-library/src/main/java/io/realm/Realm.java:848-860 — 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 (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1020— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1020-1029 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1038-1047 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1056-1065 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1074-1083 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:1092-1101 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 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 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×1
Edited copy of a member (10 corresponding lines) realm/realm-library/src/main/java/io/realm/SetValueOperator.java:1320— realm/realm-library/src/main/java/io/realm/SetValueOperator.java:1320-1329 | realm/realm-library/src/main/java/io/realm/SetValueOperator.java:1435-1444 — 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 copies of one member (6 members, 11+ corresponding lines) · ×1
Edited copies of one member (6 members, 11+ corresponding lines) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:204— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:204-214 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:257-267 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:295-305 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:318-328 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:337-347 | realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:356-366 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 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 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) realm/realm-library/src/main/java/io/realm/SetValueOperator.java:112— realm/realm-library/src/main/java/io/realm/SetValueOperator.java:112-123 | realm/realm-library/src/main/java/io/realm/SetValueOperator.java:125-136 | realm/realm-library/src/main/java/io/realm/SetValueOperator.java:138-149 | realm/realm-library/src/main/java/io/realm/SetValueOperator.java:151-162 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 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 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×1
Edited copies of one member (3 members, 8+ corresponding lines) realm/realm-library/src/main/java/io/realm/ProxyState.java:211— realm/realm-library/src/main/java/io/realm/ProxyState.java:211-218 | realm/realm-library/src/main/java/io/realm/SetValueOperator.java:1281-1292 | realm/realm-library/src/main/java/io/realm/SetValueOperator.java:1396-1407 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 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.
Duplicated block (77 lines × 2) realm/realm-library/src/main/java/io/realm/DynamicRealm.java:421— realm/realm-library/src/main/java/io/realm/DynamicRealm.java:421-497 | realm/realm-library/src/main/java/io/realm/Realm.java:1743-1819 — 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 `realm/realm-library/src/main/java/io/realm/DynamicRealm.java:421` 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. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (36 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:381— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:381-416 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:486-521 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:381` 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.
Duplicated block (26 lines × 2) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:792— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:792-817 | realm/realm-library/src/main/java/io/realm/RealmResults.java:194-219 — 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 `realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:792` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:819` calls `valueOf` and `realm/realm-library/src/main/java/io/realm/RealmResults.java:220` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (24–25 lines × 2) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:595— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:595-618 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:685-709 — 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 `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:595` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `obj` to `E` in one and `DynamicRealmObject` 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.
Duplicated block (19–20 lines × 2) realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:838— realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:838-856 | realm/realm-library/src/main/java/io/realm/RealmResults.java:229-248 — 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 `realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:838` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:837` calls `setValue` and `realm/realm-library/src/main/java/io/realm/RealmResults.java:226` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 2) realm/realm-library/src/main/java/io/realm/ProxyUtils.java:331— realm/realm-library/src/main/java/io/realm/ProxyUtils.java:331-348 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:376-393 — 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 `realm/realm-library/src/main/java/io/realm/ProxyUtils.java:331` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 6) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:102— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:102-113 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:151-162 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:195-206 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:294-305 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:392-403 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:497-508 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:102` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `realm` to `Realm` in one and `DynamicRealm` 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.
Duplicated block (10 lines × 8) realm/realm-library/src/main/java/io/realm/RealmQuery.java:572— realm/realm-library/src/main/java/io/realm/RealmQuery.java:572-581 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:596-605 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:620-629 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:645-654 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:670-679 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:694-703 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:719-728 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:743-752 — all 8 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/RealmQuery.java:572` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note first that the copies are not typed on the same thing: the declarations holding them bind `values` to `Byte[]` in one and `Short[]` 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.
Duplicated block (10 lines × 4) realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:603— realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:603-612 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:648-657 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:693-702 | realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java:739-748 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7–8 lines × 10) realm/realm-library/src/main/java/io/realm/RealmQuery.java:536— realm/realm-library/src/main/java/io/realm/RealmQuery.java:536-542 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:569-575 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:593-599 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:617-623 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:642-648 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:667-673 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:691-697 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:716-722 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:740-746 | realm/realm-library/src/main/java/io/realm/RealmQuery.java:764-771 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/RealmQuery.java:536` 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `values` to `String[]` in one and `Byte[]` 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.
Duplicated block (6 lines × 5) realm/realm-library/src/main/java/io/realm/ProxyUtils.java:440— realm/realm-library/src/main/java/io/realm/ProxyUtils.java:440-445 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:466-471 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:493-498 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:518-523 | realm/realm-library/src/main/java/io/realm/ProxyUtils.java:538-543 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/ProxyUtils.java:440` 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 (24 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2343— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2343-2366 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2740-2763 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2343` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2340` calls `emitStatement` and `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2738` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (22 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1558— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1558-1579 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1860-1881 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1558` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1556` calls `emitEmptyLine` and `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1858` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18 lines × 4) realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:47— realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:47-64 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:80-97 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:124-142 | realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:224-242 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:47` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (15–16 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:534— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:534-548 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:663-678 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:534` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1440— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1440-1455 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1733-1748 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1440` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 3) realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt:659— realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt:659-663 | realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt:679-683 | realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt:699-703 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt:659` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (30 lines × 2) library-build-transformer/src/main/kotlin/io/realm/buildtransformer/util/Stopwatch.kt:33— library-build-transformer/src/main/kotlin/io/realm/buildtransformer/util/Stopwatch.kt:33-62 | realm-transformer/src/main/kotlin/io/realm/transformer/Stopwatch.kt:33-62 — before extracting anything, compare `library-build-transformer/src/main/kotlin/io/realm/buildtransformer/util/Stopwatch.kt` and `realm-transformer/src/main/kotlin/io/realm/transformer/Stopwatch.kt` as WHOLE FILES: 94% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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 (55 lines × 2) realm/kotlin-extensions/src/main/kotlin/io/realm/kotlin/RealmListExtensions.kt:56— realm/kotlin-extensions/src/main/kotlin/io/realm/kotlin/RealmListExtensions.kt:56-110 | realm/kotlin-extensions/src/main/kotlin/io/realm/kotlin/RealmResultsExtensions.kt:60-114 — 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 (14 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:305— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:305-319 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:336-349 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt:305` 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.
Duplicated block (9 lines × 2) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:320— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:320-328 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:340-349 — 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 `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:320` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1559— realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1559-1565 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1861-1867 | realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:2333-2339 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1556` calls `emitEmptyLine` and `realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt:1858` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) examples/multiprocessExample/src/main/java/io/realm/examples/realmmultiprocessexample/MyApplication.java:26— examples/multiprocessExample/src/main/java/io/realm/examples/realmmultiprocessexample/MyApplication.java:26-35 | examples/rxJavaExample/src/main/java/io/realm/examples/rxjava/MyApplication.java:45-55 | examples/threadExample/src/main/java/io/realm/examples/threads/MyApplication.java:27-38 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 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.
Duplicated block (93 lines × 2) examples/introExample/src/main/java/io/realm/examples/intro/model/Person.java:1— examples/introExample/src/main/java/io/realm/examples/intro/model/Person.java:1-111 | examples/unitTestExample/src/main/java/io/realm/examples/unittesting/model/Person.java:1-93 — 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 `examples/introExample/src/main/java/io/realm/examples/intro/model/Person.java:1` 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.
Off the main sequence: realm:realm-library — realm:realm-library: abstractness 0.19, instability 0.00, distance 0.81 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
X20 · Mistyped argument guard· Argument guard throws the exception its own condition disproves · ×1
Argument guard throws the exception its own condition disproves realm/realm-library/src/main/java/io/realm/internal/RealmProxyMediator.java:294— The guard on line 293 rejects `className` and line 294 reports that rejection as `NullPointerException` — but the condition's own test `className.isEmpty()` is true of a value that is NOT null: it is satisfied by an EMPTY `className`, and on that path `className` was already proven non-null by the very expression that decided it. So a caller who passes a valid empty argument is told a parameter was null. That is not a wording problem: the exception type is the contract. A caller catching `NullPointerException` to handle a real null handles the empty case with it, and whoever reads the stack trace later is told a failure the source disproves. Throw `IllegalArgumentException` for the empty case, or split the guard and throw each on its own condition.
Orphaned file realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java: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 realm/realm-library/src/main/java/io/realm/SetValueOperator.java: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 REDACTED: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 realm/realm-library/src/main/java/io/realm/RealmList.java: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 realm/realm-library/src/main/java/io/realm/BaseRealm.java: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 realm/realm-library/src/main/java/io/realm/RealmObject.java: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 realm/realm-library/src/main/java/io/realm/RealmConfiguration.java: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 realm/realm-library/src/objectServer/java/io/realm/mongodb/mongo/MongoCollection.java: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 realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java: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 realm/realm-library/src/main/java/io/realm/RealmResults.java: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 realm/realm-library/src/objectServer/java/io/realm/mongodb/sync/SyncSession.java: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 realm/realm-library/src/main/java/io/realm/RealmObjectSchema.java: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 realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt: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 realm/realm-library/src/main/java/io/realm/rx/RealmObservableFactory.java: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 realm/realm-library/src/main/java/io/realm/internal/Table.java: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 realm/realm-library/src/main/java/io/realm/RealmSet.java: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 realm/realm-library/src/main/java/io/realm/RealmCache.java: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 realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmJsonTypeHelper.kt: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 realm/realm-library/src/objectServer/java/io/realm/mongodb/AppConfiguration.java: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 realm/realm-library/src/main/java/io/realm/internal/OsResults.java: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 realm/realm-library/src/objectServer/java/io/realm/internal/objectstore/OsMongoCollection.java: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 realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java: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 realm/realm-annotations-processor/src/main/java/io/realm/processor/Utils.kt: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 realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyMediatorGenerator.kt: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 realm/realm-library/src/main/java/io/realm/DynamicRealm.java: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.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:82— `debug` at line 82 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:130— `debug` at line 130 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:151— `debug` at line 151 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:155— `debug` at line 155 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:156— `debug` at line 156 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:181— `debug` at line 181 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:185— `debug` at line 185 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/ByteCodeModifier.kt:186— `debug` at line 186 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/RealmTransformer.kt:237— `debug` at line 237 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/Stopwatch.kt:52— `debug` at line 52 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/Stopwatch.kt:61— `debug` at line 61 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:106— `debug` at line 106 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:121— `debug` at line 121 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:131— `debug` at line 131 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:205— `debug` at line 205 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/FullBuild.kt:45— `debug` at line 45 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/FullBuild.kt:91— `debug` at line 91 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/FullBuild.kt:95— `debug` at line 95 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:67— `debug` at line 67 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:89— `debug` at line 89 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:90— `debug` at line 90 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:105— `debug` at line 105 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging realm-transformer/src/main/kotlin/io/realm/analytics/RealmAnalytics.kt:81— `debug` at line 81 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging library-build-transformer/src/main/kotlin/io/realm/buildtransformer/util/Stopwatch.kt:52— `debug` at line 52 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging library-build-transformer/src/main/kotlin/io/realm/buildtransformer/util/Stopwatch.kt:61— `debug` at line 61 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Disabled test examples/unitTestExample/src/test/java/io/realm/examples/unittesting/ExampleActivityTest.java:71— 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 examples/unitTestExample/src/test/java/io/realm/examples/unittesting/ExampleRealmTest.java:54— 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 realm/realm-annotations-processor/src/test/java/io/realm/processor/RealmProcessorTest.java:95— 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 realm/realm-annotations-processor/src/test/java/io/realm/processor/RealmProcessorTest.java:270— 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 realm/realm-annotations-processor/src/test/java/io/realm/processor/ValueListProcessorTest.java:34— 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 realm/realm-library/src/androidTest/java/io/realm/NotificationsTest.java:641— 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 realm/realm-library/src/androidTest/java/io/realm/RealmInMemoryTest.java:42— 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 realm/realm-library/src/androidTest/java/io/realm/RealmTests.java:4786— 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 realm/realm-library/src/androidTest/java/io/realm/entities/AllJavaTypes.java:93— 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 realm/realm-library/src/androidTest/java/io/realm/entities/AllJavaTypesUnsupportedTypes.java:127— 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 realm/realm-library/src/androidTest/java/io/realm/entities/AnnotationTypes.java: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 realm/realm-library/src/androidTest/java/io/realm/entities/DefaultValueConstructor.java:70— 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 realm/realm-library/src/androidTest/java/io/realm/entities/DefaultValueOfField.java:111— 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 realm/realm-library/src/androidTest/java/io/realm/entities/DefaultValueSetter.java:70— 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 realm/realm-library/src/androidTest/java/io/realm/entities/MappedAllJavaTypes.java: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 realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/mongodb/sync/TrustManagerCertificateValidationTests.java:31— 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 realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/mongodb/sync/TrustManagerCertificateValidationTests.java:248— A test is skipped/ignored — coverage that looks present but never runs. Re-enable it or delete it so the green run means something.
P10 · Library API & versioning· Implementation type on the public API · ×11
Implementation type on the public API realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/async/RealmResultTaskImplTest.kt:1— 8 public types in `io.realm.internal.async` are marked as implementation by their own namespace, folder or name: `RealmResultTaskImplTestKt` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/async/RealmResultTaskImplTest.kt:1, `internal`), `RealmResultTaskImplTest` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/async/RealmResultTaskImplTest.kt:35, `internal`), `RealmStreamTaskImplTest` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/async/RealmStreamTaskImplTest.kt:30, `internal`), `BadVersionException` (realm/realm-library/src/main/java/io/realm/internal/async/BadVersionException.java:27, `internal`), `BgPriorityCallable` (realm/realm-library/src/main/java/io/realm/internal/async/BgPriorityCallable.java:26, `internal`), `BgPriorityRunnable` (realm/realm-library/src/main/java/io/realm/internal/async/BgPriorityRunnable.java:23, `internal`), `RealmAsyncTaskImpl` (realm/realm-library/src/main/java/io/realm/internal/async/RealmAsyncTaskImpl.java:25, `internal`), `RealmThreadPoolExecutor` (realm/realm-library/src/main/java/io/realm/internal/async/RealmThreadPoolExecutor.java:37, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/network/LoggingInterceptorTest.kt:36— 2 public types in `io.realm.internal.network` are marked as implementation by their own namespace, folder or name: `LoggingInterceptorTest` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/network/LoggingInterceptorTest.kt:36, `internal`), `NetworkRequestTests` (realm/realm-library/src/androidTestObjectServer/kotlin/io/realm/internal/network/NetworkRequestTests.kt:13, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/main/java/io/realm/RealmAnyNativeFunctionsImpl.java:27— 1 public type in `io.realm` is marked as implementation by its own namespace, folder or name: `RealmAnyNativeFunctionsImpl` (realm/realm-library/src/main/java/io/realm/RealmAnyNativeFunctionsImpl.java:27, name ends in `Impl`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/main/java/io/realm/internal/Capabilities.java:27— 72 public types in `io.realm.internal` are marked as implementation by their own namespace, folder or name: `Capabilities` (realm/realm-library/src/main/java/io/realm/internal/Capabilities.java:27, `internal`), `CheckedRow` (realm/realm-library/src/main/java/io/realm/internal/CheckedRow.java:31, `internal`), `ColumnIndices` (realm/realm-library/src/main/java/io/realm/internal/ColumnIndices.java:50, `internal`), `ColumnInfo` (realm/realm-library/src/main/java/io/realm/internal/ColumnInfo.java:63, `internal`), `ColumnDetails` (realm/realm-library/src/main/java/io/realm/internal/ColumnInfo.java:66, `internal`), `EmptyLoadChangeSet` (realm/realm-library/src/main/java/io/realm/internal/EmptyLoadChangeSet.java:24, `internal`), `Freezable` (realm/realm-library/src/main/java/io/realm/internal/Freezable.java:28, `internal`), `IOException` (realm/realm-library/src/main/java/io/realm/internal/IOException.java:20, `internal`), and 64 more. While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/main/java/io/realm/internal/android/AndroidCapabilities.java:29— 5 public types in `io.realm.internal.android` are marked as implementation by their own namespace, folder or name: `AndroidCapabilities` (realm/realm-library/src/main/java/io/realm/internal/android/AndroidCapabilities.java:29, `internal`), `AndroidRealmNotifier` (realm/realm-library/src/main/java/io/realm/internal/android/AndroidRealmNotifier.java:18, `internal`), `ISO8601Utils` (realm/realm-library/src/main/java/io/realm/internal/android/ISO8601Utils.java:37, `internal`), `JsonUtils` (realm/realm-library/src/main/java/io/realm/internal/android/JsonUtils.java:32, `internal`), `TypeUtils` (realm/realm-library/src/main/java/io/realm/internal/android/TypeUtils.java:19, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/main/java/io/realm/internal/annotations/ObjectServer.java:30— 1 public type in `io.realm.internal.annotations` is marked as implementation by its own namespace, folder or name: `ObjectServer` (realm/realm-library/src/main/java/io/realm/internal/annotations/ObjectServer.java:30, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAny.java:37— 2 public types in `io.realm.internal.core` are marked as implementation by their own namespace, folder or name: `NativeRealmAny` (realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAny.java:37, `internal`), `NativeRealmAnyCollection` (realm/realm-library/src/main/java/io/realm/internal/core/NativeRealmAnyCollection.java:33, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:34— 1 public type in `io.realm.internal.coroutines` is marked as implementation by its own namespace, folder or name: `InternalFlowFactory` (realm/realm-library/src/main/java/io/realm/internal/coroutines/InternalFlowFactory.kt:34, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/main/java/io/realm/internal/modules/CompositeMediator.java:48— 2 public types in `io.realm.internal.modules` are marked as implementation by their own namespace, folder or name: `CompositeMediator` (realm/realm-library/src/main/java/io/realm/internal/modules/CompositeMediator.java:48, `internal`), `FilterableMediator` (realm/realm-library/src/main/java/io/realm/internal/modules/FilterableMediator.java:49, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/main/java/io/realm/internal/objectstore/OsKeyPathMapping.java:35— 5 public types in `io.realm.internal.objectstore` are marked as implementation by their own namespace, folder or name: `OsKeyPathMapping` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsKeyPathMapping.java:35, `internal`), `OsMutableSubscriptionSet` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsMutableSubscriptionSet.java:27, `internal`), `OsObjectBuilder` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsObjectBuilder.java:76, `internal`), `OsSubscription` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscription.java:25, `internal`), `OsSubscriptionSet` (realm/realm-library/src/main/java/io/realm/internal/objectstore/OsSubscriptionSet.java:41, `internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API realm/realm-library/src/main/java/io/realm/internal/util/Pair.java:24— 1 public type in `io.realm.internal.util` is marked as implementation by its own namespace, folder or name: `Pair` (realm/realm-library/src/main/java/io/realm/internal/util/Pair.java:24, `internal`). While it is public, every consumer of the library can bind to it, so changing it is a breaking change for those consumers.
Duplicated predicate realm/realm-library/src/main/java/io/realm/DynamicRealm.java:193— `!RealmObject.isManaged(parentObject) || !RealmObject.isValid(parentObject)` appears character-identically in 2 files — realm/realm-library/src/main/java/io/realm/DynamicRealm.java, realm/realm-library/src/main/java/io/realm/Realm.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate realm/realm-library/src/main/java/io/realm/ProxyState.java:212— `!RealmObject.isValid(value) || !RealmObject.isManaged(value)` appears character-identically in 3 files — realm/realm-library/src/main/java/io/realm/ProxyState.java, realm/realm-library/src/main/java/io/realm/RealmAnyOperator.java, realm/realm-library/src/main/java/io/realm/SetValueOperator.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate realm/realm-library/src/objectServer/java/io/realm/internal/async/RealmEventStreamAsyncTaskImpl.java:76— `(eventStream != null) && eventStream.isOpen()` appears character-identically in 2 files — realm/realm-library/src/objectServer/java/io/realm/internal/async/RealmEventStreamAsyncTaskImpl.java, realm/realm-library/src/objectServer/java/io/realm/internal/async/RealmEventStreamTaskImpl.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate realm/realm-library/src/main/java/io/realm/DynamicRealm.java:449— `backgroundVersionID != null && onSuccess != null` appears character-identically in 2 files — realm/realm-library/src/main/java/io/realm/DynamicRealm.java, realm/realm-library/src/main/java/io/realm/Realm.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate realm/realm-library/src/main/java/io/realm/RealmList.java:189— `baseRealm != null && baseRealm.isFrozen()` appears character-identically in 2 files — realm/realm-library/src/main/java/io/realm/RealmList.java, realm/realm-library/src/main/java/io/realm/RealmResults.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:754— `fieldName == null || fieldName.isEmpty()` appears character-identically in 3 files — realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java, realm/realm-library/src/main/java/io/realm/OrderedRealmCollectionImpl.java, realm/realm-library/src/main/java/io/realm/RealmObjectSchema.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate realm/realm-library/src/main/java/io/realm/RealmConfiguration.java:942— `flowFactory == null && Util.isCoroutinesAvailable()` appears character-identically in 2 files — realm/realm-library/src/main/java/io/realm/RealmConfiguration.java, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java:792— `isString && type != RealmFieldType.STRING` appears character-identically in 2 files — realm/realm-library/src/main/java/io/realm/DynamicRealmObject.java, realm/realm-library/src/main/java/io/realm/RealmResults.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate realm/realm-library/src/main/java/io/realm/ProxyState.java:55— `obj instanceof RealmChangeListenerWrapper && listener == ((RealmChangeListenerWrapper) obj).listener` appears character-identically in 2 files — realm/realm-library/src/main/java/io/realm/ProxyState.java, realm/realm-library/src/main/java/io/realm/internal/ObservableCollection.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate realm/realm-library/src/main/java/io/realm/RealmConfiguration.java:938— `rxFactory == null && Util.isRxJavaAvailable()` appears character-identically in 2 files — realm/realm-library/src/main/java/io/realm/RealmConfiguration.java, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file realm/realm-annotations-processor/src/main/java/io/realm/processor/RealmProxyClassGenerator.kt: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 realm/realm-library/src/main/java/io/realm/RealmQuery.java: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 realm/realm-library/src/main/java/io/realm/Realm.java: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.
X23 · Unguarded diagnostic materialisation· Diagnostic log message is built whether or not it is wanted · ×3
Diagnostic log message is built whether or not it is wanted realm-transformer/src/main/kotlin/io/realm/transformer/build/BuildTemplate.kt:121— `debug` at line 121 is called with an argument built by `proxyMediatorClasses.joinToString("…")` (line 121), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted realm-transformer/src/main/kotlin/io/realm/transformer/build/FullBuild.kt:91— `debug` at line 91 is called with an argument built by `allManagedFields.joinToString("…")` (line 91), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on.
Diagnostic log message is built whether or not it is wanted realm-transformer/src/main/kotlin/io/realm/transformer/build/IncrementalBuild.kt:90— `debug` at line 90 is called with an argument built by `outputClassNames.joinToString("…")` (line 90), whose cost grows with the collection it walks. Kotlin evaluates a call's arguments BEFORE entering the method, so that join/projection runs in full every time this line is reached — and then the level check inside the logger discards the string it produced, because debug is a level a shipped configuration normally leaves off. Nothing here decides beforehand whether the message is wanted: no `isDebugEnabled` test, no `BuildConfig.DEBUG` flag, no trailing lambda (`logger.debug { … }`) the logger calls only when the level is on.
Fat interface: Row (48 abstract methods) realm/realm-library/src/main/java/io/realm/internal/Row.java:39— `Row` declares 48 abstract methods: `checkIfAttached`, `createEmbeddedObject`, `freeze`, `getBinaryByteArray`, `getBoolean`, `getColumnCount`, `getColumnKey`, `getColumnNames`, `getColumnType`, `getDate`, `getDecimal128`, `getDouble`, `getFloat`, `getLink`, `getLong`, `getModelList`, `getModelMap`, `getModelSet`, `getNativeRealmAny`, `getObjectId`, `getObjectKey`, `getRealmAnyMap`, `getRealmAnySet`, `getString`, `getTable`, `getUUID`, `getValueList`, `getValueMap`, `getValueSet`, `hasColumn`, `isLoaded`, `isNull`, `isNullLink`, `isValid`, `nullifyLink`, `setBinaryByteArray`, `setBoolean`, `setDate`, `setDecimal128`, `setDouble`, and 8 more. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants 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: RxObservableFactory (16 abstract methods) realm/realm-library/src/main/java/io/realm/rx/RxObservableFactory.java:35— `RxObservableFactory` declares 16 abstract methods under just 2 distinct name(s): `changesetsFrom`, `changesetsFrom`, `changesetsFrom`, `changesetsFrom`, `changesetsFrom`, `changesetsFrom`, `from`, `from`, `from`, `from`, `from`, `from`, `from`, `from`, `from`, `from`. Counted over its ABSTRACT methods, once per signature; `default`, `static` and `private` methods and constants are not counted, because no implementer is forced to write them. That is an OVERLOAD SET, not 16 separate responsibilities: a caller binds to 2 operation(s) and uses the overload it selected, so the Interface-Segregation harm does NOT apply on the caller's side and splitting this into role-interfaces would scatter one operation without relieving anything. The burden that does remain is the IMPLEMENTER's — all 16 signatures must be written and kept in step. Reduce it by collapsing overloads (optional or default parameters, or an options object) rather than by segregating the interface.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion realm/realm-library/build.gradle:1— `realm/realm-library` (54066 LoC, 193 module-visible types across 18 directories) overshoots its size bounds. 1 of 9 build unit(s) (Gradle) overshoot their size bounds, lowering Project Cohesion to 7.8/10. Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
Dormant codebase — 206 of 206 significant files have no living knowledge — the codebase as a whole is dormant, not 206 separate risks. Counted over 206 of the 357 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
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.
No dependency-update automation examples/architectureComponentsExample/build.gradle:33— `examples/architectureComponentsExample/build.gradle` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 12/44 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
Hand-rolled JSON/XML parsing via regex realm/realm-library/src/objectServer/java/io/realm/internal/log/obfuscator/CustomFunctionObfuscator.java:47— A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This JVM code already uses a real parser in the same package; use it here too.
Silent fallback default in catch realm-transformer/src/main/kotlin/io/realm/transformer/ext/ProjectExt.kt:71— `getAgpVersion` swallows every exception into `"unknown"` — a data error becomes a silent behavior change with no trail. Log the failure or let it propagate. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
Skipped (documented): compileFieldNamesFiles realm/realm-annotations-processor/src/test/java/io/realm/processor/RealmProcessorTest.java:271— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): compileSimpleProxyFile realm/realm-annotations-processor/src/test/java/io/realm/processor/RealmProcessorTest.java:97— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
Skipped (documented): compileValueList realm/realm-annotations-processor/src/test/java/io/realm/processor/ValueListProcessorTest.java:35— Skipped with a documented reason — a deferral, not lazy debt: switched off by @Ignore
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.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
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 3 file(s) — `REDACTED`, `realm/realm-annotations-processor/src/main/java/io/realm/processor/ClassMetaData.kt`, `realm/realm-annotations-processor/src/main/java/io/realm/processor/Utils.kt` — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
0
—
Run 01a1e4ff-7805-74f1-a2f8-fb968d9a8c5f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 18 · Warnings: 451 · Recommendations: 291 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 16-11-2026 @ 15:35 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.