Public report of ipa320/RosTooling, published 17 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, 17 November 2026, 15:36 UTC · Survey ID cd_204b1519f89c4756831d5e43bf6321ec
ipa320/RosTooling
Measured 17 November 2026, 15:36 UTC, at code version 7ae42e5
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
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 large codebase: 325,764 lines of product code in 24 projects, tests not counted · Estimated rebuild effort: about 2.5 person-years · Weakest lens: Maturity, 50.3
Findings by how serious they are
6 critical146 serious62 minor
23 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
17 November 2026, 15:36 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 ▸
37of 37 dimensions measured by tools.
205of 214 findings point to an exact file and line, so you can open each one in the code. The other 9 concern the repository as a whole, such as missing documentation.
37dimensions across 5 lenses, read from 325,764 lines of product code in 24 projects.
ipa320/RosTooling falls short of our standard for production, in part because we found no recorded design decisions and no architecture document or diagram. It scores 60.7 out of 100 and is rated Adequate, and all six of its critical findings are security problems in the build pipeline.
Maturity, at 50.3, is the weakest lens and counts most in the score. The best first step is improving the documentation, worth about 10.7 points. Recording design decisions comes next, also worth about 10.7. Raising Maturity to 70 would lift the score to about 68.7.
Six pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Pinning each tool to an exact version would close this risk.
The product code is 325,764 lines, about €360,000 to rebuild. Two of our security checks couldn't finish, among them the one for known security holes in its packages, so those results are missing, not clean passes.
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 Maturity rose from 50.3 to 70, the lowest score rated Strong, the score would rise from 60.7 to about 68.7.
Code composition: what the lines of code are
Product code 98%Tests 2%
Rebuild cost: about €360,000 · Estimate
Cost to rebuild
€120,000 to €600,000, for 1,997 to 6,336 hours of work, about 2.5 person-years for 1 to 5 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 61. 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
Large: 325,764 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 2 Documentation finding(s) in Documentation Quality — start with README.md (2).
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pom.xml.
Raises the score by about 10.7 points · Low effort · ADR Quality
3
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.
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 €360,000 to build again, about 2.5 person-years of work. Its weakest lens is Maturity, at 50.3 (Adequate). Maturity is about how well the project explains and looks after itself, which decides whether a new developer, or a new supplier, can take over. Because the weakest lens counts most in the score, work on Maturity also moves the score most.
Based on: the rebuild estimate · the Maturity grade · how much each lens counts
What to do: Start with the Maturity actions in Top priorities.
If you do one thing first · First action
Resolve the 2 Documentation finding(s) in Documentation Quality. Of all the actions in this report, it raises the score most for the work it takes: about 10.7 points for low effort, because it clears the 2 Documentation Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
30 modules, with 20 dependencies between them. One loop runs through 2 of the modules, marked above the diagonal.
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.
74 pairs of types, where a type in primitives.impl uses a type in primitives. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
primitives.presentation uses primitives, so a change to primitives can break primitives.presentation, while a change to primitives.presentation can't break primitives.
Position
Below the diagonal: primitives.presentation uses a module listed above it, which is the healthy direction.
68 pairs of types, where a type in primitives.util uses a type in primitives. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
The types involved
primitives.util.1 → primitives.AbstractType
primitives.util.1 → primitives.Byte
primitives.util.1 → primitives.ByteArray
primitives.util.1 → primitives.Header
primitives.util.1 → primitives.MessagePart
primitives.util.1 → primitives.bool
primitives.util.1 → primitives.boolArray
primitives.util.1 → primitives.char0
primitives.util.1 → primitives.charArray
primitives.util.1 → primitives.duration
primitives.util.1 → primitives.float32
primitives.util.1 → primitives.float32Array
primitives.util.1 → primitives.float64
primitives.util.1 → primitives.float64Array
primitives.util.1 → primitives.int16
primitives.util.1 → primitives.int16Array
primitives.util.1 → primitives.int32
primitives.util.1 → primitives.int32Array
primitives.util.1 → primitives.int64
primitives.util.1 → primitives.int64Array
primitives.util.1 → primitives.int8
primitives.util.1 → primitives.int8Array
primitives.util.1 → primitives.string
primitives.util.1 → primitives.stringArray
primitives.util.1 → primitives.time
Direction
primitives.util uses primitives, so a change to primitives can break primitives.util, while a change to primitives.util can't break primitives.
Position
Below the diagonal: primitives.util uses a module listed above it, which is the healthy direction.
55 pairs of types, where a type in system.impl uses a type in system. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
46 pairs of types, where a type in system.util uses a type in system. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
primitives.provider uses primitives.util, so a change to primitives.util can break primitives.provider, while a change to primitives.provider can't break primitives.util.
Position
Below the diagonal: primitives.provider uses a module listed above it, which is the healthy direction.
ros.provider uses primitives.provider, so a change to primitives.provider can break ros.provider, while a change to ros.provider can't break primitives.provider.
Position
Below the diagonal: ros.provider uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 67.9 · Adequate · gated by X5 ·
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
6
High / Critical
A03:2025 — Software Supply Chain Failures
6
Medium
Roadmap
Top priorities: Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2); Resolve the 1 No ADRs found finding(s) in ADR Quality — start with pom.xml; Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2).
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
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).
Code Duplication: Edited copies of one member (3 members, 10+ corresponding lines)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 6
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 — 146
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 — 62
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 23
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 37 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, 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 — 37 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, 205 of 214 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.
D1 Cyclomatic Complexity — 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. Most of this repository's production source (.java) had no cyclomatic complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
D2 Cognitive Complexity — 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. Most of this repository's production source (.java) had no cognitive complexity computed for it: no method bodies were exposed for those file kinds by any language model this pass could load.
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 68 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: .java (325,509 lines, 100% 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 (.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.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
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 — 25 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 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.
D14 License Compliance — 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 — this repository's 25 Maven/Gradle manifest(s) were read and none of the dependency coordinates they declare carries a version resolvable from the manifest itself: every one is inherited from a parent POM, a <dependencyManagement> block, an imported BOM or a Gradle version reference the catalogue does not define. Licences are resolved from the POMs Maven Central publishes, which requires a version to ask about, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
D15 Churn × Complexity Hotspots — 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. A hotspot is churn × complexity. Churn was measured (54429 line(s) across the 90-day window), but no complexity could be computed for .java, which is most of this repository's production code — so every churned file would score as complexity 0 and the hotspot list would be empty no matter how tangled the code is. Not scored — this is a gap in the analysis run, not a finding about this repository.
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. Single-maintainer repository — bus factor is not applicable (11 contributor(s) across 856 commit(s) sampled, automation and bot accounts excluded). One of them holds 80% of the history; the other 10 hold 2% each on average, below the 5% at which there is somebody to hand the work to. That is a single maintainer with drive-by contributors, not a team whose knowledge has concentrated — so the bus factor is not applicable and there is nothing here for the owner to act on.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. A language sidecar this run needed FAILED, so the code model the non-MSBuild public-API collector reads was never built — this is a DEGRADED run, not a settled gap, and the surface may well be collectable on a re-run: The Python sidecar exited 0 and produced a model, but its own source census reports it opened ZERO Python files — while the engine's presence probe found Python source in this tree. The model is therefore empty for a reason on OUR side, not the repository's, and Python is recorded as unread rather than as clean.
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. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D34 Knowledge Freshness — 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. File-level freshness contradicts repo activity: 40 commits in the last 90 days, yet 31 of 37 significant files carry no living knowledge. Those two readings cannot both be true, so the per-file recency signal is treated as unreliable here and freshness is not scored for this run.
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 Guice, 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.
AX10 Code composition — 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 filesystem refused tools/ros_model_extractor.py, plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
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.
GD1 Unfinished & placeholder code — 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 filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
IC1 Incompleteness & stubs — 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 filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
IC1 Incompleteness & stubs — 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. 10 further occurrence(s) are not listed individually; the score already reflects all 50.
M3 Folder & project structure — 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. Whether the tests sit apart from production code is not visible here, because the suite is not in a form this pass reads. The test-separation credit is granted rather than withheld: this is a gap in the analyzer's language coverage, not a finding about the repository's tests. You can widen what we reach: keep the test surface somewhere a reader can find it without opening a binary — an exported/checked-in test source tree beside the production code makes the suite reviewable, diffable and discoverable by tooling.
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.
P5 DR & Backup — 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. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X10 Duplicated predicate — 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. `plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py`, `tools/ros_model_extractor.py` could not be listed or read, so no predicate in them was compared with any other file. Every other file was read and its findings stand.
X12 Unreachable branch — 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 filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X13 Undrained process stream — 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 filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X14 Bypassable address classification — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X15 Unvalidated length from an untrusted reader — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X17 Uncapped recursion over a caller-supplied document — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X19 Unrestored process-global state — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X21 Side-effecting pattern guard — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X22 Contradicted release guard — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X23 Unguarded diagnostic materialisation — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X24 Document value interpolated into markup unescaped — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X25 Inert configuration knob — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X26 Unsynchronised callback handoff — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X28 Index access outside its own emptiness 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X30 Support guard that admits what it rejects — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X6 Hand-rolled structured-format parsing — 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. The filesystem refused plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
X9 Subsumed condition operand — 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. The filesystem refused tools/ros_model_extractor.py, plugins/de.fraunhofer.ipa.ros/tools/ros_model_extractor.py while this check was reading the repository. Those files were not read, so a defect in them cannot appear on this card; every other file was read.
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.
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.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
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.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
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").
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 Dockerfile (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.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
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.
68 duplicated block group(s) detected. 1.1 % of the production lines (3,640 of 325,764) are in a reported copy. A further 21 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. Measured on part of this repository only: .java (100% of production source) was not exposed to the token comparison, so duplication there is unmeasured and is not in this count.
+ 57 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 7 Duplicated block (13 lines × 3) finding(s) in Code Duplication — start with PrimitivesEditor.java (5), PrimitivesModelWizard.java (2). — One of this dimension's main actionable groups (7 warning-level).
Resolve the 6 Duplicated block (9 lines × 3) finding(s) in Code Duplication — start with PrimitivesEditor.java (5), PrimitivesModelWizard.java. — One of this dimension's main actionable groups (6 warning-level).
Resolve the 3 Duplicated block (22 lines × 3) finding(s) in Code Duplication — start with PrimitivesEditor.java (2), PrimitivesModelWizard.java. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling10.0 / 10Exemplary✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
24 production modules (Maven), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 0 module(s) off the main sequence, with abstractness counted on 18 of the 24 (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).
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.
Resolve the 1 Low cohesion finding(s) in Cohesion (LCOM4) — start with PrimitivesItemProviderAdapterFactory.java. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: 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.
49 deducted task-comment markers across 325764 LoC (0.0/KLoC) → score 10.0. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
HackComment repeated across 10 filesplugins/de.fraunhofer.ipa.rossystem.xtext.ide/src-gen/de/fraunhofer/ipa/rossystem/ide/contentassist/antlr/lexer/InternalRosSystemLexer.java:3
What to do
Resolve the 39 TodoComment finding(s) in Explicit Debt — start with RosSystemTokenSource.java (6), Ros1TokenSource.java (6), BasicsTokenSource.java (6). — One of this dimension's main actionable groups (39 warning-level).
Resolve the 1 HackComment repeated across 10 files finding(s) in Explicit Debt — start with InternalRosSystemLexer.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.
0 of 2 documentation facets pass in full; short on: F2 example, F4 map. 2 document(s) read across 25 unit(s).
Documentation: no build, run or usage example · ×2README.md:1
What to do
Resolve the 2 Documentation finding(s) in Documentation Quality — start with README.md (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
1 of 22 build units (Maven) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesionplugins/de.fraunhofer.ipa.ros/pom.xml:1
✓ On the Gold path — maintain.
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.3 / 10Strong✓ Tool-verified
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.
25 % of calls cross a namespace and 24 % go through an interface, but 61 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
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).
6 finding(s): 0 critical, 6 high, 0 medium, 0 low. 6 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.
REDACTED
What to do
No action in Static Analysis (SAST) — all 6 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 (6 issue-level, 0 of them charged here).
Detailed fixes: d29_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.
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
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 2 platform declaration(s) and 24 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.
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.
`PrimitivesFactory` declares 33 abstract methods: `createByte`, `createByteArray`, `createHeader`, `createMessagePart`, `createbool`, `createboolArray`, `createchar0`, `createcharArray`, `createduration`, `createfloat32`, `createfloat32Array`, `createfloat64`, `createfloat64Array`, `createint16`, `createint16Array`, `createint32`, `createint32Array`, `createint64`, `createint64Array`, `createint8`, `createint8Array`, `createstring`, `createstringArray`, `createtime`, `createuint16`, `createuint16Array`, `createuint32`, `createuint32Array`, `createuint64`, `createuint64Array`, `createuint8`, `createuint8Array`, `getPrimitivesPackage`. 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. — plugins/de.fraunhofer.ipa.ros/src/primitives/PrimitivesFactory.java:15
`PrimitivesPackage` declares 36 abstract methods: `getAbstractType`, `getByte`, `getByteArray`, `getHeader`, `getMessagePart`, `getMessagePart_Data`, `getMessagePart_Type`, `getPrimitivesFactory`, `getbool`, `getboolArray`, `getchar0`, `getcharArray`, `getduration`, `getfloat32`, `getfloat32Array`, `getfloat64`, `getfloat64Array`, `getint16`, `getint16Array`, `getint32`, `getint32Array`, `getint64`, `getint64Array`, `getint8`, `getint8Array`, `getstring`, `getstringArray`, `gettime`, `getuint16`, `getuint16Array`, `getuint32`, `getuint32Array`, `getuint64`, `getuint64Array`, `getuint8`, `getuint8Array`. 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. — plugins/de.fraunhofer.ipa.ros/src/primitives/PrimitivesPackage.java:28
`QualityOfService` declares 18 abstract methods: `getDeadline`, `getDepth`, `getDurability`, `getHistory`, `getLeaseDuration`, `getLifespan`, `getLiveliness`, `getQoSProfile`, `getReliability`, `setDeadline`, `setDepth`, `setDurability`, `setHistory`, `setLeaseDuration`, `setLifespan`, `setLiveliness`, `setQoSProfile`, `setReliability`. 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. — plugins/de.fraunhofer.ipa.ros/src/ros/QualityOfService.java:31
`RosFactory` declares 48 abstract methods: `createActionClient`, `createActionServer`, `createActionSpec`, `createAmentPackage`, `createArrayTopicSpecMsgRef`, `createArtifact`, `createCatkinPackage`, `createExternalDependency`, `createGlobalNamespace`, `createInterfaceType`, `createMessageDefinition`, `createNode`, `createPackage`, `createPackageDependency`, `createPackageSet`, `createParameter`, `createParameterAny`, `createParameterAnyType`, `createParameterArrayType`, `createParameterBase64`, `createParameterBase64Type`, `createParameterBoolean`, `createParameterBooleanType`, `createParameterDate`, `createParameterDateType`, `createParameterDouble`, `createParameterDoubleType`, `createParameterInteger`, `createParameterIntegerType`, `createParameterListType`, `createParameterSequence`, `createParameterString`, `createParameterStringType`, `createParameterStruct`, `createParameterStructMember`, `createParameterStructType`, `createParameterStructTypeMember`, `createPrivateNamespace`, `createPublisher`, `createQualityOfService`, 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. — plugins/de.fraunhofer.ipa.ros/src/ros/RosFactory.java:15
`RosPackage` declares 134 abstract methods: `getActionClient`, `getActionClient_Action`, `getActionServer`, `getActionServer_Action`, `getActionSpec`, `getActionSpec_Feedback`, `getActionSpec_Goal`, `getActionSpec_Result`, `getAmentPackage`, `getArrayTopicSpecMsgRef`, `getArrayTopicSpecMsgRef_Reference`, `getArtifact`, `getArtifact_Name`, `getArtifact_Node`, `getCatkinPackage`, `getDependency`, `getExternalDependency`, `getExternalDependency_Name`, `getGlobalNamespace`, `getGraphName`, `getInterfaceType`, `getInterfaceType_ActiveStates`, `getInterfaceType_Name`, `getInterfaceType_Namespace`, `getInterfaceType_Qos`, `getLifecycleState`, `getMessageDefinition`, `getMessageDefinition_MessagePart`, `getNamespace`, `getNamespace_Parts`, `getNode`, `getNode_Actionclient`, `getNode_Actionserver`, `getNode_IsLifecycle`, `getNode_Name`, `getNode_Parameter`, `getNode_Publisher`, `getNode_Serviceclient`, `getNode_Serviceserver`, `getNode_Subscriber`, and 94 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. — plugins/de.fraunhofer.ipa.ros/src/ros/RosPackage.java:30
`RossystemFactory` declares 21 abstract methods: `createInterfaceReference`, `createProcess`, `createRosActionClientReference`, `createRosActionConnection`, `createRosActionServerReference`, `createRosConnection`, `createRosInterface`, `createRosNode`, `createRosParameter`, `createRosParameterReference`, `createRosPublisherReference`, `createRosServiceClientReference`, `createRosServiceConnection`, `createRosServiceServerReference`, `createRosSubscriberReference`, `createRosSystemConnection`, `createRosTopicConnection`, `createRossystem`, `createSubSystem`, `createSystem`, `getRossystemPackage`. 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. — plugins/de.fraunhofer.ipa.rossystem/src/system/RossystemFactory.java:15
`RossystemPackage` declares 58 abstract methods: `getComponent`, `getConnection`, `getInterfaceReference`, `getProcess`, `getProcess_Components`, `getProcess_Name`, `getProcess_Threads`, `getRosActionClientReference`, `getRosActionClientReference_From`, `getRosActionConnection`, `getRosActionConnection_From`, `getRosActionConnection_To`, `getRosActionServerReference`, `getRosActionServerReference_From`, `getRosConnection`, `getRosInterface`, `getRosInterface_Name`, `getRosInterface_Reference`, `getRosNode`, `getRosNode_From`, `getRosNode_Name`, `getRosNode_Namespace`, `getRosNode_Rosinterfaces`, `getRosNode_Rosparameters`, `getRosParameter`, `getRosParameterReference`, `getRosParameterReference_From`, `getRosParameter_From`, `getRosParameter_Name`, `getRosParameter_Value`, `getRosPublisherReference`, `getRosPublisherReference_From`, `getRosServiceClientReference`, `getRosServiceClientReference_From`, `getRosServiceConnection`, `getRosServiceConnection_From`, `getRosServiceConnection_To`, `getRosServiceServerReference`, `getRosServiceServerReference_From`, `getRosSubscriberReference`, and 18 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. — plugins/de.fraunhofer.ipa.rossystem/src/system/RossystemPackage.java:26
What to do
Split fat interfaces into focused role-interfaces so clients depend only on what they use.
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.
`@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead. (×40) — plugins/de.fraunhofer.ipa.ros.xtext.ide/src-gen/de/fraunhofer/ipa/ros/ide/AbstractBasicsIdeModule.java:27, plugins/de.fraunhofer.ipa.ros.xtext.ide/src-gen/de/fraunhofer/ipa/ros/ide/AbstractRosIdeModule.java:27, plugins/de.fraunhofer.ipa.ros.xtext.ide/src-gen/de/fraunhofer/ipa/ros/ide/contentassist/antlr/internal/InternalBasicsParser.java:24, …
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.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
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.
tools/README.md links to `docker/README.md`, but `tools/docker/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — tools/README.md:26
What to do
Reconcile the README with reality: tools/README.md links to `docker/README.md`, but `tools/docker/README.md` does not exist.
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 & versioning10.0 / 10Exemplary○ Nothing flagged
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — REDACTED:3
`plugins/de.fraunhofer.ipa.ros.xtext/pom.xml` 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`. — plugins/de.fraunhofer.ipa.ros.xtext/pom.xml:41
What to do
Add a SAST step to CI running what this repository's stack ships: spotbugs with find-sec-bugs — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
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.
Do you agree with this assessment?
P6 · Release Hygiene8.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
What to do
Keep the changelog current — add a versioned entry (Keep-a-Changelog ## [x.y.z]) for each release so the history isn't a stub.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
`!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it. (×9) — plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:1582, plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:1738, plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:1848, …
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
Do you agree with this assessment?
X13 · Undrained process stream3.5 / 10Weak✓ Tool-verified
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and `p.waitFor()` is written before stdout and stderr is read, so nothing drains it while the parent waits. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file). — plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModel.java:117
What to do
Each finding names the span that makes the branch dead and the span it is dead because of. Confirm from the two, then delete the dead arm or fix the predicate that was meant to be reachable.
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.
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.
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.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×2) — plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java:49, plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:45
`catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×2) — plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/contentassist/antlr/Ros2TokenSource.java:23, plugins/de.fraunhofer.ipa.ros2.xtext/src/de/fraunhofer/ipa/ros2/parser/antlr/Ros2TokenSource.java:23
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.
0/91 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?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Not evidenced — 4 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: 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.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 75 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — not 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.
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
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
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.
D1 Cyclomatic Complexity — cyclomatic complexity not measured — .java exposed no member bodies
D10 Test Quality — ~5922 lines of test source are present (.java) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — no .java test runner
D12 Dependency Hygiene — Not scored — 25 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 0 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.
D14 License Compliance — JVM licences not graded — no declared coordinate carries a version the manifest itself resolves
D15 Churn × Complexity Hotspots — complexity unreadable for .java — churn × complexity hotspots could not be measured
D16 Bus Factor — single-maintainer repository — bus factor is not applicable
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.
D2 Cognitive Complexity — cognitive complexity not measured — .java exposed no member bodies
D21 Naming Consistency — D21 withholds its case and prefix conventions rows: 2 candidate(s) found and not reported.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .py, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D3 God Classes — Most of this repository's production source (.java) was not read by god-class detection, so class size was not assessed for the languages that are the product — whatever else this pass did read is not this repository's class size. Not scored — this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — osv: the scanner produced no output at all, so no dependency was actually scanned
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D34 Knowledge Freshness — knowledge concentrated in recent work — freshness signal contradicted by repo activity
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 — osv: the scanner produced no output at all, so no dependency was actually scanned
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 none of the 3 signals this lens looks for
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 (22 module(s), 494 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
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
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 — This check could not read the repository's source, so it has nothing to report. That is a limit of this run, not a finding about your code.
X10 Duplicated predicate — Advisory — this card reports evidence and never carries a score.
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
X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X2 Cancellation propagation — no C# was loaded; this repository's Java and Python were read, and no request in it can be cancelled by a caller — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Python request takes no token: asyncio cancels the task and trio or anyio the scope that made it, from outside the call, and requests, httpx, aiohttp and gRPC take a timeout, not a cancellation
X20 Mistyped argument guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X21 Side-effecting pattern guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X29 Per-element action decided by a fixed element — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X30 Support guard that admits what it rejects — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Java was read, and it logs through none that an assembled message defeats: java.util.logging's level methods, log4j 1, commons-logging, JBoss Logging and Flogger take one finished message (as log4net does in C#), or it makes no call through a named logger at all. Calls made through SLF4J or log4j 2 (`org.slf4j.Logger`, `org.apache.logging.log4j.Logger`, Lombok's `@Slf4j`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X7 Silent fallback defaults — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
TodoComment plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/contentassist/antlr/RosSystemTokenSource.java:19— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/contentassist/antlr/RosSystemTokenSource.java:25— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/contentassist/antlr/RosSystemTokenSource.java:31— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.rossystem.xtext/src/de/fraunhofer/ipa/rossystem/parser/antlr/RosSystemTokenSource.java:19— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.rossystem.xtext/src/de/fraunhofer/ipa/rossystem/parser/antlr/RosSystemTokenSource.java:25— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.rossystem.xtext/src/de/fraunhofer/ipa/rossystem/parser/antlr/RosSystemTokenSource.java:31— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros1.xtext.ide/src/de/fraunhofer/ipa/ros1/ide/contentassist/antlr/Ros1TokenSource.java:19— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros1.xtext.ide/src/de/fraunhofer/ipa/ros1/ide/contentassist/antlr/Ros1TokenSource.java:25— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros1.xtext.ide/src/de/fraunhofer/ipa/ros1/ide/contentassist/antlr/Ros1TokenSource.java:31— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros1.xtext/src/de/fraunhofer/ipa/ros1/parser/antlr/Ros1TokenSource.java:19— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros1.xtext/src/de/fraunhofer/ipa/ros1/parser/antlr/Ros1TokenSource.java:25— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros1.xtext/src/de/fraunhofer/ipa/ros1/parser/antlr/Ros1TokenSource.java:31— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext.ide/src/de/fraunhofer/ipa/ros/ide/contentassist/antlr/BasicsTokenSource.java:19— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext.ide/src/de/fraunhofer/ipa/ros/ide/contentassist/antlr/BasicsTokenSource.java:25— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext.ide/src/de/fraunhofer/ipa/ros/ide/contentassist/antlr/BasicsTokenSource.java:31— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext.ide/src/de/fraunhofer/ipa/ros/ide/contentassist/antlr/RosTokenSource.java:19— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext.ide/src/de/fraunhofer/ipa/ros/ide/contentassist/antlr/RosTokenSource.java:25— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext.ide/src/de/fraunhofer/ipa/ros/ide/contentassist/antlr/RosTokenSource.java:31— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext/src/de/fraunhofer/ipa/ros/parser/antlr/BasicsTokenSource.java:19— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext/src/de/fraunhofer/ipa/ros/parser/antlr/BasicsTokenSource.java:25— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext/src/de/fraunhofer/ipa/ros/parser/antlr/BasicsTokenSource.java:31— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext/src/de/fraunhofer/ipa/ros/parser/antlr/RosTokenSource.java:19— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext/src/de/fraunhofer/ipa/ros/parser/antlr/RosTokenSource.java:25— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.ros.xtext/src/de/fraunhofer/ipa/ros/parser/antlr/RosTokenSource.java:31— // TODO Review assumption — 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 plugins/de.fraunhofer.ipa.rossystem.deployment/src/de/fraunhofer/ipa/rossystem/deployment/GenerationHandler.java:96— // Todo: check if package type maps to the select version — 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.
+ 14 more in this group — see findings.md.
X12 · Unreachable branch· Branch is unreachable · ×9
Branch is unreachable — its condition cannot hold here plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:1582— `!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Branch is unreachable — its condition cannot hold here plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:1738— `!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Branch is unreachable — its condition cannot hold here plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:1848— `!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Branch is unreachable — its condition cannot hold here plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:1925— `!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Branch is unreachable — its condition cannot hold here plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:2035— `!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Branch is unreachable — its condition cannot hold here plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:2145— `!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Branch is unreachable — its condition cannot hold here plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:2264— `!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Branch is unreachable — its condition cannot hold here plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:2374— `!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Branch is unreachable — its condition cannot hold here plugins/de.fraunhofer.ipa.ros2.xtext/src-gen/de/fraunhofer/ipa/ros2/parser/antlr/internal/InternalRos2Parser.java:2493— `!((true))` can never be true where it stands: it is decided by constants. The branch it guards never runs — whatever it was meant to handle is silently handled elsewhere or not at all. Remove it, or fix the test it repeats or the guard that decides it.
Duplicated block (13 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:574— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:574-586 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:571-583 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:574-586 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:574` 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 × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1339— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1339-1351 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1336-1348 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1339-1351 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1336` calls `SuppressWarnings` and `plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1329` 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 × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1569— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1569-1581 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1566-1578 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1569-1581 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (13 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:285— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:285-297 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:267-279 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:283-295 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:285` 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 (13 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:951— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:951-963 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:948-960 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:952-964 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (13 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:444— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:444-456 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:441-453 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:444-456 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:497— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:497-509 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:479-491 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:495-507 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:531— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:531-539 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:528-536 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:531-539 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:531` 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) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1287— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1287-1295 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1284-1292 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1288-1296 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (9 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1305— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1305-1313 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1302-1310 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1306-1314 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (9 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1619— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1619-1627 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1616-1624 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1619-1627 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (9 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:876— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:876-884 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:873-881 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:877-885 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:542— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:542-550 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/NewArtifactProjectWizardPage.java:114-122 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:524-532 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (22 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:421— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:421-442 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:418-439 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:421-442 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (22 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1822— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1822-1843 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1819-1840 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1822-1843 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (22 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:446— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:446-467 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:428-449 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:444-465 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:446` 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 (20 lines × 2) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1126— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1126-1145 | plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1196-1215 — 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 `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1126` 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 (20 lines × 2) plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1123— plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1123-1142 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1193-1212 — 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 `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1123` 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 (20 lines × 2) plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1127— plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1127-1146 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1197-1216 — 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 `plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1127` 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) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1434— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1434-1444 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1431-1441 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1434-1444 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1434` 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) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:195— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:195-205 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:173-183 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:193-203 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:195` 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) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:336— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:336-346 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModel.java:207-217 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:318-328 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. 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 (8 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1649— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1649-1656 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1646-1653 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1649-1656 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1664— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1664-1671 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1661-1668 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1664-1671 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1714— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1714-1721 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1711-1718 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1714-1721 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×2
Edited copies of one member (3 members, 6+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:525— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:525-530 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:522-527 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:525-530 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 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, 6+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:538— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:538-543 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:535-540 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:538-543 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×2
Edited copies of one member (3 members, 4+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:833— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:833-836 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:830-833 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:834-837 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:844— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:844-847 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:841-844 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:845-848 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (47 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:481— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:481-527 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:478-524 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:481-527 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:481` 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 (47 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1506— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1506-1552 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1503-1549 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1506-1552 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1506` 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 (32 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:633— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:633-664 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:630-661 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:633-664 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:633` 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 (32 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1048— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1048-1079 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1045-1076 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1049-1080 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1048` 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 (26 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1083— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1083-1108 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1080-1105 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1084-1109 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1083` 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 (26 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1135— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1135-1160 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1132-1157 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1136-1161 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1135` 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 (24 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1110— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1110-1133 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1107-1130 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1111-1134 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1110` 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 (24 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:420— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:420-443 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:402-425 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:418-441 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:420` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1602— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1602-1611 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1599-1608 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1602-1611 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:516— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:516-525 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:498-507 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:514-523 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (6 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1635— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1635-1640 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1632-1637 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1635-1640 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:178— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:178-183 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosArtifactWizard.java:205-211 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:156-161 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Swallowed exception (empty catch) plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java: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.
Swallowed exception (empty catch) plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:45— 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 (caught, then discarded) plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/contentassist/antlr/Ros2TokenSource.java:23— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) plugins/de.fraunhofer.ipa.ros2.xtext/src/de/fraunhofer/ipa/ros2/parser/antlr/Ros2TokenSource.java:23— `catch (Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
HackComment repeated across 10 files plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src-gen/de/fraunhofer/ipa/rossystem/ide/contentassist/antlr/lexer/InternalRosSystemLexer.java:3— The identical HackComment appears in 10 files (10 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 10 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// Hack: Use our own Lexer superclass by means of import.". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
D4 · Code Duplication· Near-duplicate member family (4 members, 21 shared lines) · ×1
Near-duplicate member family (4 members, 21 shared lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:575— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:575-621 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModel.java:324-356 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:557-603 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:573-619 — These 4 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them 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· Near-duplicate member family (3 members, 227 shared lines) · ×1
Near-duplicate member family (3 members, 227 shared lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1033— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1033-1277 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1030-1274 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1034-1278 — These 3 members are variants of one another: a block of 227 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 61 shared lines) · ×1
Near-duplicate member family (3 members, 61 shared lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:402— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:402-467 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:384-449 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:400-465 — These 3 members are variants of one another: a block of 61 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 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 3 times.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (4 members, 50+ identical tokens) plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationHandler.java:51— plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationHandler.java:51-76 | plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java:62-115 | plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2PythonHandler.java:62-115 | plugins/de.fraunhofer.ipa.rossystem.deployment/src/de/fraunhofer/ipa/rossystem/deployment/GenerationHandler.java:64-101 — 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 copies of one member (3 members, 71+ corresponding lines) · ×1
Edited copies of one member (3 members, 71+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:480— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:480-550 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:477-547 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:480-550 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 71 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 (84 corresponding lines) · ×1
Edited copy of a member (84 corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:204— plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:204-291 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:224-307 — These two members are one piece of code written twice and then edited apart: 84 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, 57+ corresponding lines) · ×1
Edited copies of one member (3 members, 57+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1503— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1503-1559 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1500-1556 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1503-1559 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 57 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, 47+ corresponding lines) · ×1
Edited copies of one member (3 members, 47+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:632— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:632-678 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:629-675 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:632-678 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 47 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, 50+ corresponding lines) · ×1
Edited copies of one member (3 members, 50+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:711— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:711-760 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:708-757 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:711-761 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 50 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 (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:237— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:237-270 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:235-268 — 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, 28+ corresponding lines) · ×1
Edited copies of one member (3 members, 28+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:559— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:559-586 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:556-583 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:559-586 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 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, 20+ corresponding lines) · ×1
Edited copies of one member (3 members, 20+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1425— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1425-1444 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1422-1441 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1425-1444 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 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, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:333— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:333-350 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:330-347 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:333-350 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 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, 15+ corresponding lines) · ×1
Edited copies of one member (3 members, 15+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:191— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:191-205 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:169-183 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:189-203 — These 3 members are one piece of code written 3 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 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×1
Edited copies of one member (3 members, 10+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/AddRosNodeHandler.java:14— plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/AddRosNodeHandler.java:14-23 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/AddRosProjectHandler.java:23-32 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModelHandler.java:14-23 — 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.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:40— plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:40-47 | plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java:44-52 — 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 copies of one member (3 members, 9+ corresponding lines) · ×1
Edited copies of one member (3 members, 9+ corresponding lines) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:557— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:557-565 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:539-547 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:555-563 — 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.
Duplicated block (73 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1205— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1205-1277 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1202-1274 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1206-1278 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1205` 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 (58 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1360— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1360-1417 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1357-1414 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1360-1417 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (44 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:717— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:717-760 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:714-757 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:718-761 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:717` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:717` calls `addAdapterFactory`, `RossystemItemProviderAdapterFactory` and `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:716` 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 (42 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1162— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1162-1203 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1159-1200 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1163-1204 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1162` 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 (41 lines × 2) plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java:75— plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java:75-115 | plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2PythonHandler.java:75-115 — before extracting anything, compare `plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java` and `plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2PythonHandler.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java:75` 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 (38 lines × 2) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:227— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:227-264 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:225-262 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:227` 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 (36 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:896— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:896-931 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:893-928 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:897-932 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (31 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1453— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1453-1483 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1450-1480 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1453-1483 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (30 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:595— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:595-624 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:592-621 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:595-624 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (27 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1729— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1729-1755 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1726-1752 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1729-1755 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (25 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1000— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1000-1024 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:997-1021 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1001-1025 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (24 lines × 2) plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportCommObjectsHandler.java:33— plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportCommObjectsHandler.java:33-56 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModel.java:88-111 — 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 `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportCommObjectsHandler.java:33` 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–22 lines × 4) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:582— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:582-603 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModel.java:329-340 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:564-585 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:580-601 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:582` 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 (22 lines × 2) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:288— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:288-309 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:270-291 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:288` 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 (19 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:972— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:972-990 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:969-987 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:973-991 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (19 lines × 2) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:278— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:278-296 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:276-294 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:278` 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 (18 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:780— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:780-797 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:777-794 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:781-798 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (18 lines × 2) plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:173— plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:173-190 | plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java:147-164 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java` and `plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
Duplicated block (17 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:267— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:267-283 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:250-266 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:265-281 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:267` 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 (16 lines × 4) plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationHandler.java:53— plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationHandler.java:53-68 | plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java:64-79 | plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2PythonHandler.java:64-79 | plugins/de.fraunhofer.ipa.rossystem.deployment/src/de/fraunhofer/ipa/rossystem/deployment/GenerationHandler.java:66-81 — before extracting anything, compare `plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationHandler.java` and `plugins/de.fraunhofer.ipa.rossystem.deployment/src/de/fraunhofer/ipa/rossystem/deployment/GenerationHandler.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 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationHandler.java:53` 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 (15 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:403— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:403-417 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:385-399 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:401-415 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:403` 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 (13 lines × 6) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1046— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1046-1058 | plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1081-1093 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1043-1055 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java:1078-1090 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1047-1059 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemEditor.java:1082-1094 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosEditor.java` as WHOLE FILES: this scan already matched 37 separate duplicated blocks between them, totalling at least 855 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesEditor.java:1046` 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 (12 lines × 2) plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java:118— plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java:118-129 | plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2PythonHandler.java:118-129 — before extracting anything, compare `plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java` and `plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2PythonHandler.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. 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) plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:161— plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:161-170 | plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java:135-144 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java` and `plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. 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.
Duplicated block (9 lines × 4) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:608— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:608-616 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModel.java:342-350 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:590-598 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:606-614 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:608` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:558— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:558-565 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:540-547 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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 (7 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/AddRosNodeHandler.java:17— plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/AddRosNodeHandler.java:17-23 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/AddRosProjectHandler.java:26-32 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModelHandler.java:17-23 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/AddRosNodeHandler.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModelHandler.java` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/AddRosNodeHandler.java:17` 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 (7 lines × 2) plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:113— plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:113-119 | plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java:93-99 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java` and `plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:113` 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 after the matched lines, `plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java:100` calls `forceLog` and `plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:120` 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 (5 lines × 2) plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:132— plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:132-140 | plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java:108-112 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java` and `plugins/de.fraunhofer.ipa.rossystem.xtext.ide/src/de/fraunhofer/ipa/rossystem/ide/RosSystemGeneratorCommandService.java` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `plugins/de.fraunhofer.ipa.ros2.xtext.ide/src/de/fraunhofer/ipa/ros2/ide/Ros2GeneratorCommandService.java:132` 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 × 4) plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationHandler.java:42— plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationHandler.java:42-48 | plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2CppHandler.java:53-59 | plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationRos2PythonHandler.java:53-59 | plugins/de.fraunhofer.ipa.rossystem.deployment/src/de/fraunhofer/ipa/rossystem/deployment/GenerationHandler.java:55-61 — before extracting anything, compare `plugins/de.fraunhofer.ipa.roscode.generator/src/de/fraunhofer/ipa/roscode/generator/GenerationHandler.java` and `plugins/de.fraunhofer.ipa.rossystem.deployment/src/de/fraunhofer/ipa/rossystem/deployment/GenerationHandler.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 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The 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 (5 lines × 3) plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:213— plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java:213-217 | plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java:191-195 | plugins/de.fraunhofer.ipa.rossystem.editor/src/system/presentation/RossystemModelWizard.java:211-215 — before extracting anything, compare `plugins/de.fraunhofer.ipa.ros.editor/src/primitives/presentation/PrimitivesModelWizard.java` and `plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/RosModelWizard.java` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 218 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. 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.
Low cohesion: PrimitivesItemProviderAdapterFactory (LCOM4 32) plugins/de.fraunhofer.ipa.ros.edit/src/primitives/provider/PrimitivesItemProviderAdapterFactory.java:34— PrimitivesItemProviderAdapterFactory's methods fall into 32 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 32 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
X13 · Undrained process stream· Redirected process stream is never drained (deadlock) · ×1
Redirected process stream is never drained (deadlock) plugins/de.fraunhofer.ipa.ros.editor/src/ros/presentation/ImportRosModel.java:117— The JDK pipes both `stdout` and `stderr` of this child — no `redirectErrorStream`, `redirectError`, `redirectOutput` or `inheritIO` is set — and `p.waitFor()` is written before stdout and stderr is read, so nothing drains it while the parent waits. The JDK's own `Process` documentation warns that failing to read a child's output promptly "may cause the process to block, or even deadlock": once the child writes more than the pipe holds (measured on OpenJDK 25 / Linux: 60,000 bytes finishes, 70,000 hangs forever), it blocks on the write, never exits, and the wait never returns. Nothing fails loudly. Read every piped stream before (or while) waiting — a thread or `CompletableFuture` per stream — merge them with `redirectErrorStream(true)` and read the one stream before `waitFor`, or discard what you do not want with `redirectOutput`/`redirectError(ProcessBuilder.Redirect.DISCARD)` (or a file).
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext.ide/src-gen/de/fraunhofer/ipa/ros/ide/AbstractBasicsIdeModule.java:27— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext.ide/src-gen/de/fraunhofer/ipa/ros/ide/AbstractRosIdeModule.java:27— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext.ide/src-gen/de/fraunhofer/ipa/ros/ide/contentassist/antlr/internal/InternalBasicsParser.java:24— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext.ide/src-gen/de/fraunhofer/ipa/ros/ide/contentassist/antlr/internal/InternalRosParser.java:24— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext.ide/src-gen/de/fraunhofer/ipa/ros/ide/contentassist/antlr/lexer/InternalBasicsLexer.java:13— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext.ide/src-gen/de/fraunhofer/ipa/ros/ide/contentassist/antlr/lexer/InternalRosLexer.java:13— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext.ui/src-gen/de/fraunhofer/ipa/ros/ui/AbstractBasicsUiModule.java:87— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext.ui/src-gen/de/fraunhofer/ipa/ros/ui/AbstractRosUiModule.java:89— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/AbstractBasicsRuntimeModule.java:63— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/AbstractRosRuntimeModule.java:65— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/BasicsStandaloneSetupGenerated.java:14— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/RosStandaloneSetupGenerated.java:13— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/parser/antlr/internal/InternalBasicsParser.java:21— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/parser/antlr/internal/InternalRosParser.java:21— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/parser/antlr/lexer/InternalBasicsLexer.java:13— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/parser/antlr/lexer/InternalRosLexer.java:13— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/serializer/BasicsSemanticSequencer.java:78— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/serializer/BasicsSyntacticSequencer.java:20— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/serializer/RosSemanticSequencer.java:92— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros.xtext/src-gen/de/fraunhofer/ipa/ros/serializer/RosSyntacticSequencer.java:21— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros1.xtext.ide/src-gen/de/fraunhofer/ipa/ros1/ide/AbstractRos1IdeModule.java:27— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros1.xtext.ide/src-gen/de/fraunhofer/ipa/ros1/ide/contentassist/antlr/internal/InternalRos1Parser.java:24— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros1.xtext.ide/src-gen/de/fraunhofer/ipa/ros1/ide/contentassist/antlr/lexer/InternalRos1Lexer.java:13— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros1.xtext.ui/src-gen/de/fraunhofer/ipa/ros1/ui/AbstractRos1UiModule.java:87— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Blanket warning suppression plugins/de.fraunhofer.ipa.ros1.xtext/src-gen/de/fraunhofer/ipa/ros1/AbstractRos1RuntimeModule.java:63— `@SuppressWarnings("all")` switches every compiler and analyser warning off for the whole declaration — hidden debt. Suppress the specific warning on the specific member, with a justification, instead.
Fat interface: PrimitivesFactory (33 abstract methods) plugins/de.fraunhofer.ipa.ros/src/primitives/PrimitivesFactory.java:15— `PrimitivesFactory` declares 33 abstract methods: `createByte`, `createByteArray`, `createHeader`, `createMessagePart`, `createbool`, `createboolArray`, `createchar0`, `createcharArray`, `createduration`, `createfloat32`, `createfloat32Array`, `createfloat64`, `createfloat64Array`, `createint16`, `createint16Array`, `createint32`, `createint32Array`, `createint64`, `createint64Array`, `createint8`, `createint8Array`, `createstring`, `createstringArray`, `createtime`, `createuint16`, `createuint16Array`, `createuint32`, `createuint32Array`, `createuint64`, `createuint64Array`, `createuint8`, `createuint8Array`, `getPrimitivesPackage`. 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: PrimitivesPackage (36 abstract methods) plugins/de.fraunhofer.ipa.ros/src/primitives/PrimitivesPackage.java:28— `PrimitivesPackage` declares 36 abstract methods: `getAbstractType`, `getByte`, `getByteArray`, `getHeader`, `getMessagePart`, `getMessagePart_Data`, `getMessagePart_Type`, `getPrimitivesFactory`, `getbool`, `getboolArray`, `getchar0`, `getcharArray`, `getduration`, `getfloat32`, `getfloat32Array`, `getfloat64`, `getfloat64Array`, `getint16`, `getint16Array`, `getint32`, `getint32Array`, `getint64`, `getint64Array`, `getint8`, `getint8Array`, `getstring`, `getstringArray`, `gettime`, `getuint16`, `getuint16Array`, `getuint32`, `getuint32Array`, `getuint64`, `getuint64Array`, `getuint8`, `getuint8Array`. 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: QualityOfService (18 abstract methods) plugins/de.fraunhofer.ipa.ros/src/ros/QualityOfService.java:31— `QualityOfService` declares 18 abstract methods: `getDeadline`, `getDepth`, `getDurability`, `getHistory`, `getLeaseDuration`, `getLifespan`, `getLiveliness`, `getQoSProfile`, `getReliability`, `setDeadline`, `setDepth`, `setDurability`, `setHistory`, `setLeaseDuration`, `setLifespan`, `setLiveliness`, `setQoSProfile`, `setReliability`. 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: RosFactory (48 abstract methods) plugins/de.fraunhofer.ipa.ros/src/ros/RosFactory.java:15— `RosFactory` declares 48 abstract methods: `createActionClient`, `createActionServer`, `createActionSpec`, `createAmentPackage`, `createArrayTopicSpecMsgRef`, `createArtifact`, `createCatkinPackage`, `createExternalDependency`, `createGlobalNamespace`, `createInterfaceType`, `createMessageDefinition`, `createNode`, `createPackage`, `createPackageDependency`, `createPackageSet`, `createParameter`, `createParameterAny`, `createParameterAnyType`, `createParameterArrayType`, `createParameterBase64`, `createParameterBase64Type`, `createParameterBoolean`, `createParameterBooleanType`, `createParameterDate`, `createParameterDateType`, `createParameterDouble`, `createParameterDoubleType`, `createParameterInteger`, `createParameterIntegerType`, `createParameterListType`, `createParameterSequence`, `createParameterString`, `createParameterStringType`, `createParameterStruct`, `createParameterStructMember`, `createParameterStructType`, `createParameterStructTypeMember`, `createPrivateNamespace`, `createPublisher`, `createQualityOfService`, 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: RosPackage (134 abstract methods) plugins/de.fraunhofer.ipa.ros/src/ros/RosPackage.java:30— `RosPackage` declares 134 abstract methods: `getActionClient`, `getActionClient_Action`, `getActionServer`, `getActionServer_Action`, `getActionSpec`, `getActionSpec_Feedback`, `getActionSpec_Goal`, `getActionSpec_Result`, `getAmentPackage`, `getArrayTopicSpecMsgRef`, `getArrayTopicSpecMsgRef_Reference`, `getArtifact`, `getArtifact_Name`, `getArtifact_Node`, `getCatkinPackage`, `getDependency`, `getExternalDependency`, `getExternalDependency_Name`, `getGlobalNamespace`, `getGraphName`, `getInterfaceType`, `getInterfaceType_ActiveStates`, `getInterfaceType_Name`, `getInterfaceType_Namespace`, `getInterfaceType_Qos`, `getLifecycleState`, `getMessageDefinition`, `getMessageDefinition_MessagePart`, `getNamespace`, `getNamespace_Parts`, `getNode`, `getNode_Actionclient`, `getNode_Actionserver`, `getNode_IsLifecycle`, `getNode_Name`, `getNode_Parameter`, `getNode_Publisher`, `getNode_Serviceclient`, `getNode_Serviceserver`, `getNode_Subscriber`, and 94 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: RossystemFactory (21 abstract methods) plugins/de.fraunhofer.ipa.rossystem/src/system/RossystemFactory.java:15— `RossystemFactory` declares 21 abstract methods: `createInterfaceReference`, `createProcess`, `createRosActionClientReference`, `createRosActionConnection`, `createRosActionServerReference`, `createRosConnection`, `createRosInterface`, `createRosNode`, `createRosParameter`, `createRosParameterReference`, `createRosPublisherReference`, `createRosServiceClientReference`, `createRosServiceConnection`, `createRosServiceServerReference`, `createRosSubscriberReference`, `createRosSystemConnection`, `createRosTopicConnection`, `createRossystem`, `createSubSystem`, `createSystem`, `getRossystemPackage`. 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: RossystemPackage (58 abstract methods) plugins/de.fraunhofer.ipa.rossystem/src/system/RossystemPackage.java:26— `RossystemPackage` declares 58 abstract methods: `getComponent`, `getConnection`, `getInterfaceReference`, `getProcess`, `getProcess_Components`, `getProcess_Name`, `getProcess_Threads`, `getRosActionClientReference`, `getRosActionClientReference_From`, `getRosActionConnection`, `getRosActionConnection_From`, `getRosActionConnection_To`, `getRosActionServerReference`, `getRosActionServerReference_From`, `getRosConnection`, `getRosInterface`, `getRosInterface_Name`, `getRosInterface_Reference`, `getRosNode`, `getRosNode_From`, `getRosNode_Name`, `getRosNode_Namespace`, `getRosNode_Rosinterfaces`, `getRosNode_Rosparameters`, `getRosParameter`, `getRosParameterReference`, `getRosParameterReference_From`, `getRosParameter_From`, `getRosParameter_Name`, `getRosParameter_Value`, `getRosPublisherReference`, `getRosPublisherReference_From`, `getRosServiceClientReference`, `getRosServiceClientReference_From`, `getRosServiceConnection`, `getRosServiceConnection_From`, `getRosServiceConnection_To`, `getRosServiceServerReference`, `getRosServiceServerReference_From`, `getRosSubscriberReference`, and 18 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.
Documentation: no build, run or usage example README.md:1— the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
Documentation: no map of the repository's parts README.md:1— The repository has 24 units (`de.fraunhofer.ipa.ros`, `de.fraunhofer.ipa.ros.edit`, `de.fraunhofer.ipa.ros.editor`, `de.fraunhofer.ipa.ros.feature`, `de.fraunhofer.ipa.ros.parent`, ...); `README.md` and the documents it links name none of them. Add a short list of the parts and what each does.
No ADRs found plugins/de.fraunhofer.ipa.rossystem.xtext/pom.xml:30— No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`. ADRs are expected here because `plugins/de.fraunhofer.ipa.rossystem.xtext/pom.xml` makes this repository a deployable product (line 30).
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion plugins/de.fraunhofer.ipa.ros/pom.xml:1— `plugins/de.fraunhofer.ipa.ros` (28358 LoC, 197 module-visible types across 6 directories) overshoots its size bounds. 1 of 22 build unit(s) (Maven) overshoot their size bounds, lowering Project Cohesion to 9.1/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.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
README/code drift tools/README.md:26— tools/README.md links to `docker/README.md`, but `tools/docker/README.md` does not exist. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
No SAST REDACTED:3— No static application security testing detected. For this repository's stack, add spotbugs with find-sec-bugs (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 3 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation plugins/de.fraunhofer.ipa.ros.xtext/pom.xml:41— `plugins/de.fraunhofer.ipa.ros.xtext/pom.xml` 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`.
Changelog looks stale/thin — The changelog this check read carries 2 versioned entries, against a bar of 3. Counted as either the distinct `x.y.z` versions it names (a link's target is not counted) or its version-shaped section headings (`## [1.2.0]`, `## V14.x.x`, `## Updates in 8.0.x`), whichever is the larger — so a log sectioned by minor series counts its sections, not its individual patch numbers. Entries recorded somewhere this check does not read — release notes generated at tag time from a generator config it did not recognise, or a log kept outside the repository — are not counted here, and this row is about what is re-findable in the tree rather than about how often you release.
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/91 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`.
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.
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
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.
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.
Run 01a1ea26-b891-7555-9edc-799a0310677f · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 6 · Warnings: 146 · Recommendations: 62 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 15:36 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.