Public report of MobilityData/gtfs-validator, 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, 02:16 UTC · Survey ID cd_5a6e8c93ab064014b65b48ae7bb16ce3
MobilityData/gtfs-validator
Measured 17 November 2026, 02:15 UTC, at code version c430ce1
Knowledge freshness is not measured: Freshness signal contradicted by repo activity.
CAI scoreAt risk
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A medium codebase: 37,490 lines of product code in 16 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Code Health, 43.7
Findings by how serious they are
192 critical207 serious198 minor
13 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, 02:15 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.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
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 ▸
73of 73 dimensions measured by tools.
415of 597 findings point to an exact file and line, so you can open each one in the code. The other 182 concern the repository as a whole, such as missing documentation.
73dimensions across 7 lenses, read from 37,490 lines of product code in 16 projects.
MobilityData/gtfs-validator is rated At risk because critical security findings are open, most of them in the build pipeline. It scores 50.9 out of 100, which the At risk rating leaves unchanged.
Code Health, at 43.7, is the weakest lens and counts most in the score. The best first step is fixing the password or key in the code, worth about 5.2 points. Adding type checking would lift Code Health itself, worth about 4.1 points. Raising Code Health to 70 would lift the score to about 56.2.
133 pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Twenty-eight known security holes in the packages the code depends on can be used by attackers, and twelve secrets can leak from the build pipeline. Pinning each tool to an exact version, updating the vulnerable packages and limiting each secret to its own step would close these risks. Correcting the flagged pipeline settings would fix the seven weaknesses in the build pipeline's configuration, and passing outside input through environment variables would deal with the two pipeline steps that put outside input straight into a shell command. The three form fields without a label need a label.
The product code is 37,490 lines, about €62,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 43.7 to 70, the lowest score rated Strong, the score would rise from 50.9 to about 56.2.
Code composition: what the lines of code are
Product code 57%Tests 43%
Rebuild cost: about €62,000 · Estimate
Cost to rebuild
€21,000 to €100,000, for 345 to 1,095 hours of work, about 0.4 person-years for one engineer
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.7 at a score of 51. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Medium: 37,490 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Raises the score by about 5.2 points · Low effort · REDACTED Scanning
2
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with MainTests.java.
Raises the score by about 4.6 points · Low effort · Test Quality
3
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 4.1 points · Medium effort · Type Safety
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €62,000 to build again, about 0.4 person-years of work. Its weakest lens is Code Health, at 43.7 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning. Of all the actions in this report, it raises the score most for the work it takes: about 5.2 points for low effort, because it clears the 1 REDACTED Scanning findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
38 modules, with 76 dependencies between them. 3 loops run through 13 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.
org.mobilitydata.gtfsvalidator.model uses org.mobilitydata.gtfsvalidator.performance, so a change to org.mobilitydata.gtfsvalidator.performance can break org.mobilitydata.gtfsvalidator.model, while a change to org.mobilitydata.gtfsvalidator.model can't break org.mobilitydata.gtfsvalidator.performance.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.model uses a module listed above it, which is the healthy direction.
13→14 org.mobilitydata.gtfsvalidator.model uses org.mobilitydata.gtfsvalidator.noticepart of a loop✕
Connections
1 pair of types, where a type in org.mobilitydata.gtfsvalidator.model uses a type in org.mobilitydata.gtfsvalidator.notice.
org.mobilitydata.gtfsvalidator.model uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.model, while a change to org.mobilitydata.gtfsvalidator.model can't break org.mobilitydata.gtfsvalidator.notice.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.mobilitydata.gtfsvalidator.notice uses org.mobilitydata.gtfsvalidator.type, so a change to org.mobilitydata.gtfsvalidator.type can break org.mobilitydata.gtfsvalidator.notice, while a change to org.mobilitydata.gtfsvalidator.notice can't break org.mobilitydata.gtfsvalidator.type.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.notice uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.notice uses org.mobilitydata.gtfsvalidator.model, so a change to org.mobilitydata.gtfsvalidator.model can break org.mobilitydata.gtfsvalidator.notice, while a change to org.mobilitydata.gtfsvalidator.notice can't break org.mobilitydata.gtfsvalidator.model.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.notice uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.deprecated uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.deprecated, while a change to org.mobilitydata.gtfsvalidator.deprecated can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.deprecated uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.input uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.input, while a change to org.mobilitydata.gtfsvalidator.input can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.input uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.io uses org.mobilitydata.gtfsvalidator.model, so a change to org.mobilitydata.gtfsvalidator.model can break org.mobilitydata.gtfsvalidator.io, while a change to org.mobilitydata.gtfsvalidator.io can't break org.mobilitydata.gtfsvalidator.model.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.io uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.io uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.io, while a change to org.mobilitydata.gtfsvalidator.io can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.io uses a module listed above it, which is the healthy direction.
1 pair of types, where a type in org.mobilitydata.gtfsvalidator.outputcomparator.io uses a type in org.mobilitydata.gtfsvalidator.outputcomparator.model.
org.mobilitydata.gtfsvalidator.outputcomparator.io uses org.mobilitydata.gtfsvalidator.outputcomparator.model, so a change to org.mobilitydata.gtfsvalidator.outputcomparator.model can break org.mobilitydata.gtfsvalidator.outputcomparator.io, while a change to org.mobilitydata.gtfsvalidator.outputcomparator.io can't break org.mobilitydata.gtfsvalidator.outputcomparator.model.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.outputcomparator.io uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in org.mobilitydata.gtfsvalidator.outputcomparator.io uses a type in org.mobilitydata.gtfsvalidator.outputcomparator.model.report.
org.mobilitydata.gtfsvalidator.outputcomparator.io uses org.mobilitydata.gtfsvalidator.outputcomparator.model.report, so a change to org.mobilitydata.gtfsvalidator.outputcomparator.model.report can break org.mobilitydata.gtfsvalidator.outputcomparator.io, while a change to org.mobilitydata.gtfsvalidator.outputcomparator.io can't break org.mobilitydata.gtfsvalidator.outputcomparator.model.report.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.outputcomparator.io uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.outputcomparator.io uses org.mobilitydata.gtfsvalidator.model, so a change to org.mobilitydata.gtfsvalidator.model can break org.mobilitydata.gtfsvalidator.outputcomparator.io, while a change to org.mobilitydata.gtfsvalidator.outputcomparator.io can't break org.mobilitydata.gtfsvalidator.model.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.outputcomparator.io uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.outputcomparator.io uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.outputcomparator.io, while a change to org.mobilitydata.gtfsvalidator.outputcomparator.io can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.outputcomparator.io uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.processor.notices uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.processor.notices, while a change to org.mobilitydata.gtfsvalidator.processor.notices can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.processor.notices uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.reportsummary uses org.mobilitydata.gtfsvalidator.performance, so a change to org.mobilitydata.gtfsvalidator.performance can break org.mobilitydata.gtfsvalidator.reportsummary, while a change to org.mobilitydata.gtfsvalidator.reportsummary can't break org.mobilitydata.gtfsvalidator.performance.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.reportsummary uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.reportsummary uses org.mobilitydata.gtfsvalidator.model, so a change to org.mobilitydata.gtfsvalidator.model can break org.mobilitydata.gtfsvalidator.reportsummary, while a change to org.mobilitydata.gtfsvalidator.reportsummary can't break org.mobilitydata.gtfsvalidator.model.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.reportsummary uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.reportsummary uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.reportsummary, while a change to org.mobilitydata.gtfsvalidator.reportsummary can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.reportsummary uses a module listed above it, which is the healthy direction.
20→24 org.mobilitydata.gtfsvalidator.reportsummary uses org.mobilitydata.gtfsvalidator.reportsummary.modelpart of a loop✕
Connections
4 pairs of types, where a type in org.mobilitydata.gtfsvalidator.reportsummary uses a type in org.mobilitydata.gtfsvalidator.reportsummary.model.
org.mobilitydata.gtfsvalidator.reportsummary uses org.mobilitydata.gtfsvalidator.reportsummary.model, so a change to org.mobilitydata.gtfsvalidator.reportsummary.model can break org.mobilitydata.gtfsvalidator.reportsummary, while a change to org.mobilitydata.gtfsvalidator.reportsummary can't break org.mobilitydata.gtfsvalidator.reportsummary.model.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→25 org.mobilitydata.gtfsvalidator.reportsummary uses org.mobilitydata.gtfsvalidator.runnerpart of a loop✕
Connections
3 pairs of types, where a type in org.mobilitydata.gtfsvalidator.reportsummary uses a type in org.mobilitydata.gtfsvalidator.runner.
org.mobilitydata.gtfsvalidator.reportsummary uses org.mobilitydata.gtfsvalidator.runner, so a change to org.mobilitydata.gtfsvalidator.runner can break org.mobilitydata.gtfsvalidator.reportsummary, while a change to org.mobilitydata.gtfsvalidator.reportsummary can't break org.mobilitydata.gtfsvalidator.runner.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→28 org.mobilitydata.gtfsvalidator.reportsummary uses org.mobilitydata.gtfsvalidator.utilpart of a loop✕
Connections
3 pairs of types, where a type in org.mobilitydata.gtfsvalidator.reportsummary uses a type in org.mobilitydata.gtfsvalidator.util.
org.mobilitydata.gtfsvalidator.reportsummary uses org.mobilitydata.gtfsvalidator.util, so a change to org.mobilitydata.gtfsvalidator.util can break org.mobilitydata.gtfsvalidator.reportsummary, while a change to org.mobilitydata.gtfsvalidator.reportsummary can't break org.mobilitydata.gtfsvalidator.util.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.mobilitydata.gtfsvalidator.util.geojson uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.util.geojson, while a change to org.mobilitydata.gtfsvalidator.util.geojson can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.util.geojson uses a module listed above it, which is the healthy direction.
21→34 org.mobilitydata.gtfsvalidator.util.geojson uses org.mobilitydata.gtfsvalidator.tablepart of a loop✕
Connections
1 pair of types, where a type in org.mobilitydata.gtfsvalidator.util.geojson uses a type in org.mobilitydata.gtfsvalidator.table.
org.mobilitydata.gtfsvalidator.util.geojson uses org.mobilitydata.gtfsvalidator.table, so a change to org.mobilitydata.gtfsvalidator.table can break org.mobilitydata.gtfsvalidator.util.geojson, while a change to org.mobilitydata.gtfsvalidator.util.geojson can't break org.mobilitydata.gtfsvalidator.table.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in org.mobilitydata.gtfsvalidator.outputcomparator.cli uses a type in org.mobilitydata.gtfsvalidator.outputcomparator.model.
org.mobilitydata.gtfsvalidator.outputcomparator.cli uses org.mobilitydata.gtfsvalidator.outputcomparator.model, so a change to org.mobilitydata.gtfsvalidator.outputcomparator.model can break org.mobilitydata.gtfsvalidator.outputcomparator.cli, while a change to org.mobilitydata.gtfsvalidator.outputcomparator.cli can't break org.mobilitydata.gtfsvalidator.outputcomparator.model.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.outputcomparator.cli uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in org.mobilitydata.gtfsvalidator.outputcomparator.cli uses a type in org.mobilitydata.gtfsvalidator.outputcomparator.model.report.
org.mobilitydata.gtfsvalidator.outputcomparator.cli uses org.mobilitydata.gtfsvalidator.outputcomparator.model.report, so a change to org.mobilitydata.gtfsvalidator.outputcomparator.model.report can break org.mobilitydata.gtfsvalidator.outputcomparator.cli, while a change to org.mobilitydata.gtfsvalidator.outputcomparator.cli can't break org.mobilitydata.gtfsvalidator.outputcomparator.model.report.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.outputcomparator.cli uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.outputcomparator.cli uses org.mobilitydata.gtfsvalidator.model, so a change to org.mobilitydata.gtfsvalidator.model can break org.mobilitydata.gtfsvalidator.outputcomparator.cli, while a change to org.mobilitydata.gtfsvalidator.outputcomparator.cli can't break org.mobilitydata.gtfsvalidator.model.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.outputcomparator.cli uses a module listed above it, which is the healthy direction.
4 pairs of types, where a type in org.mobilitydata.gtfsvalidator.outputcomparator.cli uses a type in org.mobilitydata.gtfsvalidator.outputcomparator.io.
org.mobilitydata.gtfsvalidator.outputcomparator.cli uses org.mobilitydata.gtfsvalidator.outputcomparator.io, so a change to org.mobilitydata.gtfsvalidator.outputcomparator.io can break org.mobilitydata.gtfsvalidator.outputcomparator.cli, while a change to org.mobilitydata.gtfsvalidator.outputcomparator.cli can't break org.mobilitydata.gtfsvalidator.outputcomparator.io.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.outputcomparator.cli uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.processor.summary uses org.mobilitydata.gtfsvalidator.processor.notices, so a change to org.mobilitydata.gtfsvalidator.processor.notices can break org.mobilitydata.gtfsvalidator.processor.summary, while a change to org.mobilitydata.gtfsvalidator.processor.summary can't break org.mobilitydata.gtfsvalidator.processor.notices.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.processor.summary uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.reportsummary.model uses org.mobilitydata.gtfsvalidator.performance, so a change to org.mobilitydata.gtfsvalidator.performance can break org.mobilitydata.gtfsvalidator.reportsummary.model, while a change to org.mobilitydata.gtfsvalidator.reportsummary.model can't break org.mobilitydata.gtfsvalidator.performance.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.reportsummary.model uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.reportsummary.model uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.reportsummary.model, while a change to org.mobilitydata.gtfsvalidator.reportsummary.model can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.reportsummary.model uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.reportsummary.model uses org.mobilitydata.gtfsvalidator.reportsummary, so a change to org.mobilitydata.gtfsvalidator.reportsummary can break org.mobilitydata.gtfsvalidator.reportsummary.model, while a change to org.mobilitydata.gtfsvalidator.reportsummary.model can't break org.mobilitydata.gtfsvalidator.reportsummary.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.reportsummary.model uses a module listed above it, which is the healthy direction.
24→28 org.mobilitydata.gtfsvalidator.reportsummary.model uses org.mobilitydata.gtfsvalidator.utilpart of a loop✕
Connections
1 pair of types, where a type in org.mobilitydata.gtfsvalidator.reportsummary.model uses a type in org.mobilitydata.gtfsvalidator.util.
org.mobilitydata.gtfsvalidator.reportsummary.model uses org.mobilitydata.gtfsvalidator.util, so a change to org.mobilitydata.gtfsvalidator.util can break org.mobilitydata.gtfsvalidator.reportsummary.model, while a change to org.mobilitydata.gtfsvalidator.reportsummary.model can't break org.mobilitydata.gtfsvalidator.util.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
24→34 org.mobilitydata.gtfsvalidator.reportsummary.model uses org.mobilitydata.gtfsvalidator.tablepart of a loop✕
Connections
5 pairs of types, where a type in org.mobilitydata.gtfsvalidator.reportsummary.model uses a type in org.mobilitydata.gtfsvalidator.table.
org.mobilitydata.gtfsvalidator.reportsummary.model uses org.mobilitydata.gtfsvalidator.table, so a change to org.mobilitydata.gtfsvalidator.table can break org.mobilitydata.gtfsvalidator.reportsummary.model, while a change to org.mobilitydata.gtfsvalidator.reportsummary.model can't break org.mobilitydata.gtfsvalidator.table.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.mobilitydata.gtfsvalidator.runner uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.runner, while a change to org.mobilitydata.gtfsvalidator.runner can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.runner uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.runner uses org.mobilitydata.gtfsvalidator.input, so a change to org.mobilitydata.gtfsvalidator.input can break org.mobilitydata.gtfsvalidator.runner, while a change to org.mobilitydata.gtfsvalidator.runner can't break org.mobilitydata.gtfsvalidator.input.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.runner uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.runner uses org.mobilitydata.gtfsvalidator.reportsummary.model, so a change to org.mobilitydata.gtfsvalidator.reportsummary.model can break org.mobilitydata.gtfsvalidator.runner, while a change to org.mobilitydata.gtfsvalidator.runner can't break org.mobilitydata.gtfsvalidator.reportsummary.model.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.runner uses a module listed above it, which is the healthy direction.
25→28 org.mobilitydata.gtfsvalidator.runner uses org.mobilitydata.gtfsvalidator.utilpart of a loop✕
Connections
2 pairs of types, where a type in org.mobilitydata.gtfsvalidator.runner uses a type in org.mobilitydata.gtfsvalidator.util.
org.mobilitydata.gtfsvalidator.runner uses org.mobilitydata.gtfsvalidator.util, so a change to org.mobilitydata.gtfsvalidator.util can break org.mobilitydata.gtfsvalidator.runner, while a change to org.mobilitydata.gtfsvalidator.runner can't break org.mobilitydata.gtfsvalidator.util.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→30 org.mobilitydata.gtfsvalidator.runner uses org.mobilitydata.gtfsvalidator.validatorpart of a loop✕
Connections
2 pairs of types, where a type in org.mobilitydata.gtfsvalidator.runner uses a type in org.mobilitydata.gtfsvalidator.validator.
org.mobilitydata.gtfsvalidator.runner uses org.mobilitydata.gtfsvalidator.validator, so a change to org.mobilitydata.gtfsvalidator.validator can break org.mobilitydata.gtfsvalidator.runner, while a change to org.mobilitydata.gtfsvalidator.runner can't break org.mobilitydata.gtfsvalidator.validator.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
25→34 org.mobilitydata.gtfsvalidator.runner uses org.mobilitydata.gtfsvalidator.tablepart of a loop✕
Connections
2 pairs of types, where a type in org.mobilitydata.gtfsvalidator.runner uses a type in org.mobilitydata.gtfsvalidator.table.
org.mobilitydata.gtfsvalidator.runner uses org.mobilitydata.gtfsvalidator.table, so a change to org.mobilitydata.gtfsvalidator.table can break org.mobilitydata.gtfsvalidator.runner, while a change to org.mobilitydata.gtfsvalidator.runner can't break org.mobilitydata.gtfsvalidator.table.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.mobilitydata.gtfsvalidator.app.gui uses org.mobilitydata.gtfsvalidator.runner, so a change to org.mobilitydata.gtfsvalidator.runner can break org.mobilitydata.gtfsvalidator.app.gui, while a change to org.mobilitydata.gtfsvalidator.app.gui can't break org.mobilitydata.gtfsvalidator.runner.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.app.gui uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.cli uses org.mobilitydata.gtfsvalidator.runner, so a change to org.mobilitydata.gtfsvalidator.runner can break org.mobilitydata.gtfsvalidator.cli, while a change to org.mobilitydata.gtfsvalidator.cli can't break org.mobilitydata.gtfsvalidator.runner.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.cli uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.util uses org.mobilitydata.gtfsvalidator.runner, so a change to org.mobilitydata.gtfsvalidator.runner can break org.mobilitydata.gtfsvalidator.util, while a change to org.mobilitydata.gtfsvalidator.util can't break org.mobilitydata.gtfsvalidator.runner.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.util uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.web.service.util uses org.mobilitydata.gtfsvalidator.runner, so a change to org.mobilitydata.gtfsvalidator.runner can break org.mobilitydata.gtfsvalidator.web.service.util, while a change to org.mobilitydata.gtfsvalidator.web.service.util can't break org.mobilitydata.gtfsvalidator.runner.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.web.service.util uses a module listed above it, which is the healthy direction.
29→32 org.mobilitydata.gtfsvalidator.web.service.util uses org.mobilitydata.gtfsvalidator.web.service.controllerpart of a loop✕
Connections
1 pair of types, where a type in org.mobilitydata.gtfsvalidator.web.service.util uses a type in org.mobilitydata.gtfsvalidator.web.service.controller.
org.mobilitydata.gtfsvalidator.web.service.util uses org.mobilitydata.gtfsvalidator.web.service.controller, so a change to org.mobilitydata.gtfsvalidator.web.service.controller can break org.mobilitydata.gtfsvalidator.web.service.util, while a change to org.mobilitydata.gtfsvalidator.web.service.util can't break org.mobilitydata.gtfsvalidator.web.service.controller.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.mobilitydata.gtfsvalidator.validator uses org.mobilitydata.gtfsvalidator.type, so a change to org.mobilitydata.gtfsvalidator.type can break org.mobilitydata.gtfsvalidator.validator, while a change to org.mobilitydata.gtfsvalidator.validator can't break org.mobilitydata.gtfsvalidator.type.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.validator uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.validator uses org.mobilitydata.gtfsvalidator.util.shape, so a change to org.mobilitydata.gtfsvalidator.util.shape can break org.mobilitydata.gtfsvalidator.validator, while a change to org.mobilitydata.gtfsvalidator.validator can't break org.mobilitydata.gtfsvalidator.util.shape.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.validator uses a module listed above it, which is the healthy direction.
234 pairs of types, where a type in org.mobilitydata.gtfsvalidator.validator uses a type in org.mobilitydata.gtfsvalidator.notice. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
org.mobilitydata.gtfsvalidator.validator uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.validator, while a change to org.mobilitydata.gtfsvalidator.validator can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.validator uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.validator uses org.mobilitydata.gtfsvalidator.input, so a change to org.mobilitydata.gtfsvalidator.input can break org.mobilitydata.gtfsvalidator.validator, while a change to org.mobilitydata.gtfsvalidator.validator can't break org.mobilitydata.gtfsvalidator.input.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.validator uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.validator uses org.mobilitydata.gtfsvalidator.util, so a change to org.mobilitydata.gtfsvalidator.util can break org.mobilitydata.gtfsvalidator.validator, while a change to org.mobilitydata.gtfsvalidator.validator can't break org.mobilitydata.gtfsvalidator.util.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.validator uses a module listed above it, which is the healthy direction.
30→33 org.mobilitydata.gtfsvalidator.validator uses org.mobilitydata.gtfsvalidator.parsingpart of a loop✕
Connections
2 pairs of types, where a type in org.mobilitydata.gtfsvalidator.validator uses a type in org.mobilitydata.gtfsvalidator.parsing.
org.mobilitydata.gtfsvalidator.validator uses org.mobilitydata.gtfsvalidator.parsing, so a change to org.mobilitydata.gtfsvalidator.parsing can break org.mobilitydata.gtfsvalidator.validator, while a change to org.mobilitydata.gtfsvalidator.validator can't break org.mobilitydata.gtfsvalidator.parsing.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
30→34 org.mobilitydata.gtfsvalidator.validator uses org.mobilitydata.gtfsvalidator.tablepart of a loop✕
Connections
20 pairs of types, where a type in org.mobilitydata.gtfsvalidator.validator uses a type in org.mobilitydata.gtfsvalidator.table.
org.mobilitydata.gtfsvalidator.validator uses org.mobilitydata.gtfsvalidator.table, so a change to org.mobilitydata.gtfsvalidator.table can break org.mobilitydata.gtfsvalidator.validator, while a change to org.mobilitydata.gtfsvalidator.validator can't break org.mobilitydata.gtfsvalidator.table.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.mobilitydata.gtfsvalidator.web.service uses org.mobilitydata.gtfsvalidator.runner, so a change to org.mobilitydata.gtfsvalidator.runner can break org.mobilitydata.gtfsvalidator.web.service, while a change to org.mobilitydata.gtfsvalidator.web.service can't break org.mobilitydata.gtfsvalidator.runner.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.web.service uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.web.service uses org.mobilitydata.gtfsvalidator.util, so a change to org.mobilitydata.gtfsvalidator.util can break org.mobilitydata.gtfsvalidator.web.service, while a change to org.mobilitydata.gtfsvalidator.web.service can't break org.mobilitydata.gtfsvalidator.util.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.web.service uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.web.service.controller uses org.mobilitydata.gtfsvalidator.util, so a change to org.mobilitydata.gtfsvalidator.util can break org.mobilitydata.gtfsvalidator.web.service.controller, while a change to org.mobilitydata.gtfsvalidator.web.service.controller can't break org.mobilitydata.gtfsvalidator.util.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.web.service.controller uses a module listed above it, which is the healthy direction.
3 pairs of types, where a type in org.mobilitydata.gtfsvalidator.web.service.controller uses a type in org.mobilitydata.gtfsvalidator.web.service.util.
org.mobilitydata.gtfsvalidator.web.service.controller uses org.mobilitydata.gtfsvalidator.web.service.util, so a change to org.mobilitydata.gtfsvalidator.web.service.util can break org.mobilitydata.gtfsvalidator.web.service.controller, while a change to org.mobilitydata.gtfsvalidator.web.service.controller can't break org.mobilitydata.gtfsvalidator.web.service.util.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.web.service.controller uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.parsing uses org.mobilitydata.gtfsvalidator.type, so a change to org.mobilitydata.gtfsvalidator.type can break org.mobilitydata.gtfsvalidator.parsing, while a change to org.mobilitydata.gtfsvalidator.parsing can't break org.mobilitydata.gtfsvalidator.type.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.parsing uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.parsing uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.parsing, while a change to org.mobilitydata.gtfsvalidator.parsing can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.parsing uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.parsing uses org.mobilitydata.gtfsvalidator.validator, so a change to org.mobilitydata.gtfsvalidator.validator can break org.mobilitydata.gtfsvalidator.parsing, while a change to org.mobilitydata.gtfsvalidator.parsing can't break org.mobilitydata.gtfsvalidator.validator.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.parsing uses a module listed above it, which is the healthy direction.
33→34 org.mobilitydata.gtfsvalidator.parsing uses org.mobilitydata.gtfsvalidator.tablepart of a loop✕
Connections
1 pair of types, where a type in org.mobilitydata.gtfsvalidator.parsing uses a type in org.mobilitydata.gtfsvalidator.table.
org.mobilitydata.gtfsvalidator.parsing uses org.mobilitydata.gtfsvalidator.table, so a change to org.mobilitydata.gtfsvalidator.table can break org.mobilitydata.gtfsvalidator.parsing, while a change to org.mobilitydata.gtfsvalidator.parsing can't break org.mobilitydata.gtfsvalidator.table.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.mobilitydata.gtfsvalidator.table uses org.mobilitydata.gtfsvalidator.performance, so a change to org.mobilitydata.gtfsvalidator.performance can break org.mobilitydata.gtfsvalidator.table, while a change to org.mobilitydata.gtfsvalidator.table can't break org.mobilitydata.gtfsvalidator.performance.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.table uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.table uses org.mobilitydata.gtfsvalidator.type, so a change to org.mobilitydata.gtfsvalidator.type can break org.mobilitydata.gtfsvalidator.table, while a change to org.mobilitydata.gtfsvalidator.table can't break org.mobilitydata.gtfsvalidator.type.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.table uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.table uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.table, while a change to org.mobilitydata.gtfsvalidator.table can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.table uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.table uses org.mobilitydata.gtfsvalidator.input, so a change to org.mobilitydata.gtfsvalidator.input can break org.mobilitydata.gtfsvalidator.table, while a change to org.mobilitydata.gtfsvalidator.table can't break org.mobilitydata.gtfsvalidator.input.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.table uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.table uses org.mobilitydata.gtfsvalidator.util.geojson, so a change to org.mobilitydata.gtfsvalidator.util.geojson can break org.mobilitydata.gtfsvalidator.table, while a change to org.mobilitydata.gtfsvalidator.table can't break org.mobilitydata.gtfsvalidator.util.geojson.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.table uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.table uses org.mobilitydata.gtfsvalidator.validator, so a change to org.mobilitydata.gtfsvalidator.validator can break org.mobilitydata.gtfsvalidator.table, while a change to org.mobilitydata.gtfsvalidator.table can't break org.mobilitydata.gtfsvalidator.validator.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.table uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.table uses org.mobilitydata.gtfsvalidator.parsing, so a change to org.mobilitydata.gtfsvalidator.parsing can break org.mobilitydata.gtfsvalidator.table, while a change to org.mobilitydata.gtfsvalidator.table can't break org.mobilitydata.gtfsvalidator.parsing.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.table uses a module listed above it, which is the healthy direction.
34→35 org.mobilitydata.gtfsvalidator.table uses org.mobilitydata.gtfsvalidator.annotationpart of a loop✕
Connections
2 pairs of types, where a type in org.mobilitydata.gtfsvalidator.table uses a type in org.mobilitydata.gtfsvalidator.annotation.
org.mobilitydata.gtfsvalidator.table uses org.mobilitydata.gtfsvalidator.annotation, so a change to org.mobilitydata.gtfsvalidator.annotation can break org.mobilitydata.gtfsvalidator.table, while a change to org.mobilitydata.gtfsvalidator.table can't break org.mobilitydata.gtfsvalidator.annotation.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
org.mobilitydata.gtfsvalidator.annotation uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.annotation, while a change to org.mobilitydata.gtfsvalidator.annotation can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.annotation uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.annotation uses org.mobilitydata.gtfsvalidator.table, so a change to org.mobilitydata.gtfsvalidator.table can break org.mobilitydata.gtfsvalidator.annotation, while a change to org.mobilitydata.gtfsvalidator.annotation can't break org.mobilitydata.gtfsvalidator.table.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.annotation uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.testing uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.testing, while a change to org.mobilitydata.gtfsvalidator.testing can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.testing uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.testing uses org.mobilitydata.gtfsvalidator.input, so a change to org.mobilitydata.gtfsvalidator.input can break org.mobilitydata.gtfsvalidator.testing, while a change to org.mobilitydata.gtfsvalidator.testing can't break org.mobilitydata.gtfsvalidator.input.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.testing uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.testing uses org.mobilitydata.gtfsvalidator.validator, so a change to org.mobilitydata.gtfsvalidator.validator can break org.mobilitydata.gtfsvalidator.testing, while a change to org.mobilitydata.gtfsvalidator.testing can't break org.mobilitydata.gtfsvalidator.validator.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.testing uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.testing uses org.mobilitydata.gtfsvalidator.table, so a change to org.mobilitydata.gtfsvalidator.table can break org.mobilitydata.gtfsvalidator.testing, while a change to org.mobilitydata.gtfsvalidator.testing can't break org.mobilitydata.gtfsvalidator.table.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.testing uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.notice.schema uses org.mobilitydata.gtfsvalidator.notice, so a change to org.mobilitydata.gtfsvalidator.notice can break org.mobilitydata.gtfsvalidator.notice.schema, while a change to org.mobilitydata.gtfsvalidator.notice.schema can't break org.mobilitydata.gtfsvalidator.notice.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.notice.schema uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.notice.schema uses org.mobilitydata.gtfsvalidator.table, so a change to org.mobilitydata.gtfsvalidator.table can break org.mobilitydata.gtfsvalidator.notice.schema, while a change to org.mobilitydata.gtfsvalidator.notice.schema can't break org.mobilitydata.gtfsvalidator.table.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.notice.schema uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.notice.schema uses org.mobilitydata.gtfsvalidator.annotation, so a change to org.mobilitydata.gtfsvalidator.annotation can break org.mobilitydata.gtfsvalidator.notice.schema, while a change to org.mobilitydata.gtfsvalidator.notice.schema can't break org.mobilitydata.gtfsvalidator.annotation.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.notice.schema uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.processor uses org.mobilitydata.gtfsvalidator.parsing, so a change to org.mobilitydata.gtfsvalidator.parsing can break org.mobilitydata.gtfsvalidator.processor, while a change to org.mobilitydata.gtfsvalidator.processor can't break org.mobilitydata.gtfsvalidator.parsing.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.processor uses a module listed above it, which is the healthy direction.
org.mobilitydata.gtfsvalidator.processor uses org.mobilitydata.gtfsvalidator.annotation, so a change to org.mobilitydata.gtfsvalidator.annotation can break org.mobilitydata.gtfsvalidator.processor, while a change to org.mobilitydata.gtfsvalidator.processor can't break org.mobilitydata.gtfsvalidator.annotation.
Position
Below the diagonal: org.mobilitydata.gtfsvalidator.processor uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 43.7 · Weak · gated by R1, 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
156
High / Critical
A03:2025 — Software Supply Chain Failures
63
High / Critical
A02:2025 — Security Misconfiguration
6
High / Critical
A07:2025 — Authentication Failures
3
High / Critical
Roadmap
Top priorities: Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED; Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with MainTests.java; Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
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.
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).
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
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 — 192
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 — 207
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 — 198
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 13
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 73 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 73 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, 415 of 597 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.
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: the JavaScript/TypeScript half could not be measured — the JavaScript/TypeScript suite(s) run through a browser-driven runner the coverage collector does not drive — web/client/ (cypress) — a gap in the analyzer, not something this repository is missing. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 1,234 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 2 test source file(s) (.js) that it cannot: it reads the test types the .java frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.java, .js) and this repository declares a JVM test suite (repository root, Gradle), but it was not re-run: the analyzer environment could not run it. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D12 Dependency Hygiene — 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. Currency was graded against Maven Central, but whether an artifact is DEPRECATED is not: Maven Central publishes no deprecation marker, exactly as rubygems.org does not. Whether one is UNMAINTAINED is not graded either — no registry publishes a maintenance status, and release age does not stand in for one. Two of this dimension's four signals are therefore unread on a Gradle tree, and its score reflects currency alone.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each ecosystem's manifests (what makes a folder runnable or a published package) need their own proof before D19 judges its units. Until then those folders' READMEs are judged only as documents (boilerplate, structure), never counted as complete.
D19 Documentation Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This kind did not reach the 95 % precision gate in three adjudicated runs (docs/plans/deterministic-engine/adjudication/D19-sample3-v3.md), so by the pre-registered fallback it publishes no row until a re-measurement shows it does. The candidates are counted here, not reported as findings, and the score does not include them.
D21 Naming Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (build.gradle), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
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: 42 commits in the last 90 days, yet 162 of 207 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.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. (rule: no-root-manifest). The renderer reported: the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
C4 Data Retention — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These retention controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks retention controls.
C5 Data-Subject Rights — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These data-subject rights controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks data-subject rights controls.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
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.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations: 28 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
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.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
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").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC1 Text alternatives: Alt-text is detected structurally — the scan sees that an alternative EXISTS, not whether it meaningfully describes the image, and decorative-vs-missing is judged by attribute shape; runtime-injected images and a non-role=img decorative svg are out of scope. This is accessibility readiness, never a WCAG conformance claim.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC4 Keyboard semantics: Keyboard semantics are inferred from markup attributes — interactivity wired purely in script, focus managed at runtime, and component-level handlers are invisible. A clean result means "no static keyboard-trap shape", not a keyboard-operability proof.
AC5 ARIA correctness: ARIA correctness is checked against the static role/attribute shape — roles/attributes set dynamically aren't seen, a valid role says nothing about whether it matches the element's real behaviour, and required-state checks are suppressed when a JSX spread could supply them. The two-branch toggle check (a control whose state is conveyed only by which of two mutually exclusive branches renders) reads CONDITIONALS THAT ARE ATTRIBUTES — Vue v-if/v-else/v-show and Alpine x-if/x-show — so the same toggle written as a Svelte {#if} block or a JSX ternary is control flow the markup model never projects as a branch and is not seen at all.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
5 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was JsonReportSummaryGenerator.<init> at 29. A further 1 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being EntityImplementationGenerator.getDefaultValue at 26 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EntityImplementationGenerator.java (EntityImplementationGenerator.getDefaultValue at 26). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with JsonReportSummaryGenerator.<init> (cyclomatic 29), GeoJsonFileLoader.extractFeature (cyclomatic 24), CsvFileLoader.load (cyclomatic 18). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 5 together lifts Cyclomatic Complexity from 8.9 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 22 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 30 down to 30 or less in Cognitive Complexity — start with GeoJsonFileLoader.extractFeature (cognitive 59), OverlappingPickupDropOffZoneValidator.validate (cognitive 37), JsonReportSummaryGenerator.<init> (cognitive 31). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 6.6 to about 7.3/10, projected with the scoring formula itself and assuming each lands exactly at 30; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.0 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 4 TooManyMethods finding(s) in God Classes — start with FeedMetadata.java, RowParser.java, GtfsValidatorApp.java. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 3 ClassTooLong finding(s) in God Classes — start with FeedMetadata.java, TableContainerIndexGenerator.java, EntityImplementationGenerator.java. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 MethodTooLong finding(s) in God Classes — start with ValidationReportComparator.java, ColumnarTableContainerGenerator.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
22 duplicated block group(s) detected. 3.3 % of the production lines (1,232 of 37,490) are in a reported copy. A further 37 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
Edited copy of a member (10 corresponding lines) · ×4main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:350
Edited copy of a member (9 corresponding lines) · ×4main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ParentStationDistanceValidator.java:111
Edited copy of a member (7 corresponding lines) · ×4main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TransfersInSeatTransferTypeValidator.java:159
Edited copy of a member (8 corresponding lines) · ×3core/src/main/java/org/mobilitydata/gtfsvalidator/notice/StartAndEndRangeEqualNotice.java:58
+ 30 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with FeedMetadata.java, ShapePoints.java, StopToShapeMatcher.java. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 4 Edited copy of a member (10 corresponding lines) finding(s) in Code Duplication — start with TableColumnsGenerator.java (2), ShapeToStopMatchingValidator.java, ResolvedNotice.java. — One of this dimension's main actionable groups (4 warning-level).
Resolve the 4 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with ParentStationDistanceValidator.java, DuplicateFareMediaValidator.java, PathwayReachableLocationValidator.java. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.5 / 10Stronggated by 1 serious finding✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
16 production modules (Gradle), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; 1 module(s) off the main sequence, with abstractness counted on 12 of the 16 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: :core
What to do
Resolve the 1 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 2 Low cohesion finding(s) in Cohesion (LCOM4) — start with DefaultFieldValidator.java, FeedMetadata.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D10 · Test Quality9.6 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
1 skipped (1 with a documented reason), 29 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 1234 tests. Measured on the .java suite only — at least 2 test source file(s) (.js) went unread, so its test quality is unmeasured and is not in these counts.
No assertions (empty test): contextLoadsweb/service/src/test/java/org/mobilitydata/gtfsvalidator/web/service/MainTests.java:12
No assertions: fromGtfsShape_noUserDistance · ×28main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePointsTest.java:59
Resolve the 1 No assertions (empty test) finding(s) in Test Quality — start with MainTests.java. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 28 No assertions finding(s) in Test Quality — start with ShapePointsTest.java (8), StopToShapeMatcherTest.java (8), StopPointsTest.java (3). — One of this dimension's main actionable groups (28 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
This repository's Gradle dependency graph was RESOLVED BY A BUILD, across every subproject rather than the root alone: 235 artifact(s) resolved, 233 of them gradable against Maven Central, and 166 behind a shipped release. Where a version was requested and a different one won conflict resolution, the RESOLVED version is what is graded — grading the request would recommend an upgrade already applied. Known CVEs in the same graph are a separate question again, reported under D30.
Outdated (compile): com.google.guava:guava · ×166
Detailed fixes: d12_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: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 40 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 17 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Resolve the 2 Hotspot finding(s) in Churn × Complexity Hotspots — start with CsvFileLoader.java, JsonReportSummaryGenerator.java. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.2 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
16 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java. Counted over 205 of the 444 production source files in this repository: 237 are under the ~2,400-byte size floor this dimension measures over, and the remaining 2 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×2
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
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.
11 deducted task-comment markers across 37490 LoC (0.0/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 8 TodoComment finding(s) in Explicit Debt — start with EntityImplementationGenerator.java, StopTimesGeographyIdPresenceValidatorTest.java, TranslationFieldAndReferenceValidator.java. — One of this dimension's main actionable groups (8 warning-level).
Resolve the 3 FixmeComment finding(s) in Explicit Debt — start with TableDescriptorGenerator.java, GtfsFrequencyEndRangeValidatorTest.java, GtfsShapeLatLonValidatorTest.java. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 19 document(s) read across 2 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.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.
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with build.gradle. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
2 of 15 build units (Gradle, Python) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion · ×2main/build.gradle:1
What to do
Resolve the 2 Projects may be oversized for their cohesion finding(s) in Project Cohesion — start with build.gradle (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
34 % of calls cross a namespace and 11 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
1 finding(s): 0 critical, 1 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
156 finding(s): 0 critical, 155 high, 1 medium, 0 low. 132 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 3 file(s) — `gradlew` (line 72, line 173), `REDACTED` (line 74), `REDACTED` (lines 20–34) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 7 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 1 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 12 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (4), REDACTED (2), REDACTED. — One of this dimension's main actionable groups (12 issue-level).
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (7). — One of this dimension's main actionable groups (7 issue-level).
Resolve the 1 REDACTED finding(s) charged to Static Analysis (SAST) — the other 132 are reported here at file:line but scored by D36 (supply-chain provenance), which charges them once. — One of this dimension's main actionable groups (133 issue-level, 1 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 24 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (21), REDACTED (3). — One of this dimension's main actionable groups (24 issue-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 Critical vulnerability finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 1 High IaC finding(s) in IaC & Container Security — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Low IaC finding(s) in IaC & Container Security — start with REDACTED (2). — One of this dimension's main actionable groups (2 recommendation-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether 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.
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 16 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (16 warning-level).
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).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
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 1 end-of-life framework(s), read from 3 platform declaration(s) and 76 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.
End-of-life framework: Spring Boot 2web/service/build.gradle:1
What to do
Resolve the 1 End-of-life framework finding(s) in Platform End-of-Life — start with build.gradle. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d44_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC1 · Text alternatives10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether non-text content carries a text alternative — img/area/input[type=image] have alt, a meaningful svg has a title or aria-label, video has a captions track, and object/embed/canvas have a name or fallback content. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: every img/area/input[type=image] checked for alt, svg[role=img] for a title/aria-label, video for a captions <track>. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: image/media elements — img, area, input[type=image], svg, video, object, embed, canvas — across the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and dynamic-attribute elements are skipped. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is NOT read by any producer, so it contributes no element to this population; where such a frontend is present the card discloses it as an analyzer gap rather than scoring around it.
Do you agree with this assessment?
AC2 · Forms & labels6.2 / 10Adequate✓ Tool-verified
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one). — web/client/src/lib/Alert.svelte:11
This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it. (×3) — web/client/src/lib/forms/FileField.svelte:51, web/client/src/lib/forms/SelectField.svelte:40, web/client/src/lib/forms/TextField.svelte:33
What to do
Give every control a programmatic label (a <label for> / wrapping <label> / aria-label) and every button text — a placeholder is not a label.
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). — main/src/main/resources/report.html:2
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. — main/src/main/resources/report.html:2
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. (×2) — main/src/main/resources/report.html:252, web/client/src/routes/rules.html/+page.svelte:361
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether interactive behaviour is keyboard-reachable — no click handler on a non-interactive element lacking a role, tabindex and key handler, no element the repo's own CSS styles `cursor: pointer` without giving it any of the three, no unfocusable element whose only binding is a mouse enter/leave pair or a double-click, no positive tabindex, no href-less anchor, no placeholder-href (#/javascript) link acting as a button. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: click handlers on non-interactive elements lacking role+tabindex+key handler, positive tabindex values, and href-less anchors. Components skipped, spreads suppressed. Deterministic, hard fact per element.
Coverage: Population: elements that pose a keyboard-semantics question, in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) — a non-natively-interactive element carrying a click handler, a double-click or hover enter/leave binding, a pointer-only gesture on a tabindex="0" element, or `cursor: pointer` from the repo's own CSS; an href-less or placeholder-href (#, javascript:) anchor; and any element with a positive tabindex. Natively interactive elements used correctly (<button>, <a href>, form controls) are NOT in the population — there is nothing to judge — so a page of nothing but correct controls gives AC4 nothing to measure. Keyboard reachability is judged from the markup, never from a rendered page. ★ An interactive element declared in a tagged-template (html`…`) or hyperscript frontend is NOT in this population — no producer reads either — so an empty population is reported as an analyzer gap, never as "this repository has no interactive elements".
An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action. (×3) — main/src/main/resources/report.html:279, main/src/main/resources/report.html:305, main/src/main/resources/report.html:361
What to do
Make custom controls keyboard-operable (role + tabindex + key handler), drop positive tabindex, and give anchors a real href.
Other · Accessibility — Whether ARIA is used correctly — valid non-abstract roles, the ARIA state a role requires, valid (non-misspelled) aria-* attribute names, in-enum values for token-typed aria-* attributes, and no aria-hidden on (or wrapping) a focusable element. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: role values checked against the WAI-ARIA role set (abstract/invalid flagged), required ARIA state for a role, and aria-hidden on a focusable element. Deterministic, role/attribute level.
Coverage: Population: elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx) that carry a role or an aria-* attribute; roles and token values are checked against the ARIA enums exhaustively within that set. An expression-valued (dynamic) role or aria-* value is skipped rather than guessed, and markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
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 singleton services avoid mutable shared instance state that concurrent callers would race on.
Method: Roslyn scan: singleton field mutations unguarded by lock or Interlocked, per type; syntax-based guard detection. Deterministic, traceable per field.
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.
`GtfsStopSchema` declares 16 abstract methods: `levelId`, `locationType`, `parentStation`, `platformCode`, `stopAccess`, `stopCode`, `stopDesc`, `stopId`, `stopLat`, `stopLon`, `stopName`, `stopTimezone`, `stopUrl`, `ttsStopName`, `wheelchairBoarding`, `zoneId`. 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. — main/src/main/java/org/mobilitydata/gtfsvalidator/table/GtfsStopSchema.java:24
`GtfsStopTimeSchema` declares 18 abstract methods: `arrivalTime`, `continuousDropOff`, `continuousPickup`, `departureTime`, `dropOffBookingRuleId`, `dropOffType`, `endPickupDropOffWindow`, `locationGroupId`, `locationId`, `pickupBookingRuleId`, `pickupType`, `shapeDistTraveled`, `startPickupDropOffWindow`, `stopHeadsign`, `stopId`, `stopSequence`, `timepoint`, `tripId`. 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. — main/src/main/java/org/mobilitydata/gtfsvalidator/table/GtfsStopTimeSchema.java:38
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.
`csvRowNumber` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it. — main/src/main/java/org/mobilitydata/gtfsvalidator/table/GtfsGeoJsonFeature.java:45
What to do
Finish or delete the methods that still throw "not implemented" or return a placeholder under a TODO, and replace placeholder text before shipping.
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.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
`docs/ARCHITECTURE.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `output-comparator`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape. — docs/ARCHITECTURE.md:5
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.
Update docs/ARCHITECTURE.md so it draws the parts the code has today: add output-comparator.
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.
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.
Do you agree with this assessment?
P2 · Observability5.5 / 10Adequate✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 4/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `app/pkg`, `cli`, `output-comparator`, `web/client`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Add a health-check endpoint (Spring Boot Actuator's /actuator/health, or a /health route) so orchestrators and load balancers can probe liveness/readiness.
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 16 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
`web/client/package.json` 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`. — web/client/package.json:18
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.
This step syncs the release over the live copy with delete (`actions/upload-artifact/merge` with `delete-merged: true`): files the new build lacks are removed in place and the rest are overwritten, so the previous release is gone and a half-finished sync serves a mix of both. There is no staged copy to switch back to. (×2) — REDACTED:221, REDACTED:108
What to do
Upload each release beside the live one (a release-unique path) and switch to it, so the previous release stays one switch away; or drop the delete from the live sync.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Readiness — Whether outbound HTTP calls are wrapped in resilience (retry/timeout/circuit-breaker) so a failing dependency doesn't cascade.
Method: Source scan: outbound HTTP clients and what bounds them — resilience handlers (Polly, AddStandardResilienceHandler) on .NET; on Go, the JVM, Python, JavaScript/TypeScript, Ruby, PHP, Rust, Elixir, Swift, Dart and Erlang, a timeout, deadline, retry or breaker beside each call, or a process-wide client default (a framework-wide deadline such as Drupal core's, Laravel's or actix's awc counts). Exhaustive, deterministic.
`HttpClients.createDefault(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout. — core/src/main/java/org/mobilitydata/gtfsvalidator/util/HttpGetUtil.java:62
What to do
Set connect and read timeouts on every client (`RestTemplateBuilder.connectTimeout/readTimeout`, WebClient `responseTimeout`, `HttpRequest.Builder.timeout`, `HttpURLConnection.setReadTimeout`, Feign `connectTimeout`/`readTimeout` in configuration), and wrap calls to dependencies in resilience4j `@Retry`/`@CircuitBreaker`/`@TimeLimiter` (or Spring Retry).
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 24 plain JS — the untyped files are web/client/cypress/e2e/error_messages.cy.js, web/client/cypress/e2e/validator.cy.js, web/client/cypress/support/commands.js, web/client/cypress/support/e2e.js, web/client/src/lib/Alert.svelte, web/client/src/lib/Button.svelte (+18 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
load has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/client/src/routes/rules.html/+page.js:3
generateReport has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — web/client/src/routes/+page.svelte:349
Do you agree with this assessment?
R3 · Large Files8.0 / 10Strong✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
web/client/src/routes/+page.svelte has 443 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — web/client/src/routes/+page.svelte:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling10.0 / 10Exemplary✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each package.json script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: package.json scanned for test/lint/typecheck script wiring. Deterministic presence check.
The package in `web/client` declares the lint script `lint` (`prettier --plugin-search-dir . --check . && eslint .`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `web/client` (or the workspace's task runner). — web/client/package.json:13
Do you agree with this assessment?
R7 · Dead Code5.9 / 10Adequate✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 8 application, 8 tooling and 4 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (8 application, 8 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (web/client/src/lib/StatusModal.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — web/client/src/lib/CopyButton.svelte
no import path from any entry point (8 application, 8 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (web/client/src/lib/CopyButton.svelte, web/client/src/lib/StatusModal.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — web/client/src/lib/Button.svelte
no import path from any entry point (8 application, 8 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×8) — web/client/src/lib/forms/FileField.svelte, web/client/src/lib/DropTarget.svelte, web/client/src/lib/forms/SelectField.svelte, …
no import path from any entry point (8 application, 8 tooling, 4 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (web/client/src/lib/forms/FileField.svelte, web/client/src/lib/forms/SelectField.svelte, web/client/src/lib/forms/TextField.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — web/client/src/lib/forms/LabeledField.svelte
no import path from any entry point (8 application, 8 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (web/client/src/lib/Button.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — web/client/src/lib/ButtonContent.svelte
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Only what this repository's own non-C# files could be read for was assessed — markup this repository SHIPS is scored for third-party script integrity whether or not the repository serves it itself, since a page handed to a consumer runs in that consumer’s origin. Nothing else in this dimension was assessed: the transport, cookie, input-validation and crypto controls are read from a source model that was not loaded for this repository’s language, so their absence here is not a finding about this repository.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`https://code.jquery.com/jquery-3.6.0.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 3 such include(s) across the repository's markup. — main/src/main/resources/report.html:7
What to do
Pin third-party scripts and verify them: name an exact version in the URL and add an `integrity="sha384-…"` hash alongside `crossorigin="anonymous"` (both are required — an integrity hash on a cross-origin script without `crossorigin` is not evaluated, it blocks the script). Where the vendor ships a continuously-updated loader and publishes no stable hash (tag managers, analytics, chat widgets), Subresource Integrity is not available: constrain it instead with a `Content-Security-Policy` that names the exact origins allowed to execute, and drop the script from the pages that do not need it. Where the page is shipped inside a package that others host, prefer vendoring the asset and serving it from the app’s own origin, so no consumer inherits a third-party dependency they did not choose.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
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.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. 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.
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`debug` at line 207 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — web/service/src/main/java/org/mobilitydata/gtfsvalidator/web/service/util/StorageHelper.java:207
`debug` at line 210 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — web/service/src/main/java/org/mobilitydata/gtfsvalidator/web/service/util/StorageHelper.java:210
`error` at line 212 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text. — web/service/src/main/java/org/mobilitydata/gtfsvalidator/web/service/util/StorageHelper.java:212
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/39 of this repository's Java package directories are under a non-null default: a `package-info.java` declaring `@NullMarked` (JSpecify) or `@NonNullApi`, `@ParametersAreNonnullByDefault`, `@NonNullByDefault`, `@DefaultQualifier(NonNull.class)`; a `module-info.java` declaring `@NullMarked`; every type in it `@NullMarked`; or a build that runs NullAway with the package in `AnnotatedPackages`, or the Checker Framework's `NullnessChecker`. Elsewhere every reference admits null and no checker warns on the dereference that throws a `NullPointerException`.
What to do
Declare the default where Java declares it: `@NullMarked` (org.jspecify.annotations) in each package's `package-info.java`, or once in `module-info.java`, and run NullAway (Error Prone) or the Checker Framework so the declaration is enforced. Then annotate the real exceptions `@Nullable` and resolve the suppressions rather than adding to them: a `@SuppressWarnings("NullAway")` or `castToNonNull(x)` on a value the checker could show to be null is a `NullPointerException` waiting for the path that makes it true — where the value genuinely cannot be null, say something the checker can see instead (a null check, `Objects.requireNonNull`, a non-null field initialised in the constructor).
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 15 of 55 WCAG 2.2 Level A/AA success criteria (27%; ≈30% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 40 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 1 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 4 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
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 — 51 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.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) exited before it served a page. Likely cause (our sandbox): `npm run` found no package.json in the folder where our sandbox ran it. This is a limit of our sandbox, not of your repository. Last output: "npm error code ENOENT / npm error syscall open / npm error path <repo>/package.json / npm error errno -2 / npm error enoent Could not read package.json: Error: ENOENT: no such file or directory, open '<repo>/package.json' / npm error enoent This is related to npm not being able to find a file. / npm error enoent / npm error A complete log of this run can be found in: <path>" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
D11 Test Reliability — Test reliability not included — the .java suite was found but not re-run
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
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"]`.
D25 ADR Conformance — no ADRs to check
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.
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 measured — JavaScript/TypeScript suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (85 value object(s))
ED1 Event-Driven — not scored — this repository shows none of the 3 signals this lens looks for
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
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.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 4 test file(s) reach none of 19 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — X1 reached only 5% of this repository's production lines — java (37,077 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 5% of this repository's production lines — java (37,077 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 was 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
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
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
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
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.
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.
AC2 · Forms & labels· <input> without a programmatic label · ×2
<input> without a programmatic label web/client/src/lib/forms/FileField.svelte:51— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<input> without a programmatic label web/client/src/lib/forms/TextField.svelte:33— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
AC2 · Forms & labels· <button> with no accessible text · ×1
<button> with no accessible text web/client/src/lib/Alert.svelte:11— A button with no text and no aria-label has no accessible name. Add visible text or an aria-label (an icon-only button still needs one).
AC2 · Forms & labels· <select> without a programmatic label · ×1
<select> without a programmatic label web/client/src/lib/forms/SelectField.svelte:40— This control has no associated label. Add a <label for> / wrapping <label> / aria-label / aria-labelledby so assistive tech can name it.
<html> without a lang main/src/main/resources/report.html:2— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D10 · Test Quality· No assertions (empty test) · ×1
No assertions (empty test): contextLoads web/service/src/test/java/org/mobilitydata/gtfsvalidator/web/service/MainTests.java:12— Test method has an empty body — it asserts nothing and exercises no code.
No assertions: fromGtfsShape_noUserDistance main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePointsTest.java:59— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fromGtfsShape_withDecreasingUserDistance main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePointsTest.java:93— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fromGtfsShape_withUserDistance main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePointsTest.java:76— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: hasUserDistance main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePointsTest.java:110— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchFromLocation main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePointsTest.java:178— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchFromLocationAndMatchesFromLocation_sameAsFullScan main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePointsTest.java:208— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchFromUserDist main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePointsTest.java:161— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchesFromLocation main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePointsTest.java:186— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fromStopTimes_largeStation main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopPointsTest.java:87— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: fromStopTimes_smallStation main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopPointsTest.java:69— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: hasUserDistance main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopPointsTest.java:105— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchUsingGeoDistance_largeStation main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcherTest.java:292— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchUsingGeoDistance_normal main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcherTest.java:201— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchUsingGeoDistance_outOfOrder main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcherTest.java:245— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchUsingGeoDistance_stopFarAway main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcherTest.java:270— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchUsingGeoDistance_tooManyMatches main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcherTest.java:223— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchUsingUserDistance_fullUserDistances main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcherTest.java:135— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchUsingUserDistance_partialUserDistances main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcherTest.java:157— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: matchUsingUserDistance_stopTooFarAway main/src/test/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcherTest.java:179— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: withinFractionOrMargin core/src/test/java/org/mobilitydata/gtfsvalidator/util/MathUtilTest.java:30— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: getStopOrParentLatLng_infiniteLoop main/src/test/java/org/mobilitydata/gtfsvalidator/util/StopUtilTest.java:84— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: getStopOrParentLatLng_noLatLng main/src/test/java/org/mobilitydata/gtfsvalidator/util/StopUtilTest.java:98— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: getStopOrParentLatLng_valid main/src/test/java/org/mobilitydata/gtfsvalidator/util/StopUtilTest.java:59— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: createJobShouldReturn500ErrorIfSaveJobFileFromUrlThrowsException web/service/src/test/java/org/mobilitydata/gtfsvalidator/web/service/controller/CreateJobEndpointTest.java:244— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: createJobShouldReturn500ErrorIfSaveMetadataThrowsException web/service/src/test/java/org/mobilitydata/gtfsvalidator/web/service/controller/CreateJobEndpointTest.java:229— This method's body runs code, and no assertion was recognised in it. Recognised: JUnit's assertion methods (assertEquals, assertTrue, assertInstanceOf, assertThrows, assertThrowsExactly, assertTimeoutPreemptively, assertAll and the rest of JUnit 5's list), assertThat (AssertJ, Hamcrest, Truth), fail, Mockito's verify and the `assert` statement, in the test body and in helper methods of the test's own class or an in-repository base class, followed three calls deep. Verification through a helper on another object or in another class, through a custom matcher library, or through a harness that fails by throwing under some other name is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
TodoComment processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EntityImplementationGenerator.java:170— // TODO: Support all types or throw an exception. — 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 main/src/test/java/org/mobilitydata/gtfsvalidator/validator/StopTimesGeographyIdPresenceValidatorTest.java:58— // TODO: Put back when this notice is ready to be published. — 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 main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TranslationFieldAndReferenceValidator.java:133— // TODO check for JSON Tables here — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment main/src/main/java/org/mobilitydata/gtfsvalidator/util/StopUtil.java:35— // TODO: Replace with `getOptionalStopOrParentLatLng` everywhere. Falling back to — 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 main/src/main/java/org/mobilitydata/gtfsvalidator/table/GtfsGeoJsonFeature.java:43— // TODO: Change the interface hierarchy so we dont need this. It's not relevant for geojson — 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 main/src/main/java/org/mobilitydata/gtfsvalidator/table/GtfsLocationGroupStopsSchema.java:13— // TODO: Put back the foreign key annotation when ready to publish the notice — 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 main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/HtmlReportGenerator.java:58— // TODO: handle null metadata — 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 core/src/main/java/org/mobilitydata/gtfsvalidator/notice/NoticeContainer.java:111— // TODO: This would be the spot to add customization of notice severity levels in the future. — 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.
Duplicated block (5 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:193— main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:193-197 | main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:216-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:193` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePoints.java:111— main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePoints.java:111-115 | main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePoints.java:166-171 — 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 `main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePoints.java:111` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcher.java:49— main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcher.java:49-53 | main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/StopToShapeMatcher.java:85-89 — 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. 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 × 2) core/src/main/java/org/mobilitydata/gtfsvalidator/notice/IOError.java:34— core/src/main/java/org/mobilitydata/gtfsvalidator/notice/IOError.java:34-38 | core/src/main/java/org/mobilitydata/gtfsvalidator/notice/URISyntaxError.java:34-38 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `exception` to `IOException` in one and `URISyntaxException` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/LocationHasStopTimesValidator.java:117— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/LocationHasStopTimesValidator.java:117-121 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/MissingLevelIdValidator.java:92-96 — 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.
TooManyMethods: FeedMetadata main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:19— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RowParser core/src/main/java/org/mobilitydata/gtfsvalidator/parsing/RowParser.java:42— TooManyMethods — 35 methods. The bar is 30 methods; this is 5 over it, 1.17× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: GtfsValidatorApp app/gui/src/main/java/org/mobilitydata/gtfsvalidator/app/gui/GtfsValidatorApp.java:63— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TableColumnsGenerator processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:42— TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×4
Edited copy of a member (10 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:350— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:350-359 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:410-419 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:193— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:193-205 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:208-217 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) core/src/main/java/org/mobilitydata/gtfsvalidator/notice/ResolvedNotice.java:64— core/src/main/java/org/mobilitydata/gtfsvalidator/notice/ResolvedNotice.java:64-73 | core/src/main/java/org/mobilitydata/gtfsvalidator/notice/schema/ReferencesSchema.java:80-89 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:378— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:378-389 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:391-400 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×4
Edited copy of a member (9 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ParentStationDistanceValidator.java:111— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ParentStationDistanceValidator.java:111-119 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ParentStationDistanceValidator.java:148-156 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/DuplicateFareMediaValidator.java:31— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/DuplicateFareMediaValidator.java:31-39 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/DuplicateRouteNameValidator.java:48-56 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PathwayReachableLocationValidator.java:199— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PathwayReachableLocationValidator.java:199-207 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:286-295 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableDescriptorGenerator.java:172— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableDescriptorGenerator.java:172-181 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableContainerIndexGenerator.java:280-288 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×4
Edited copy of a member (7 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TransfersInSeatTransferTypeValidator.java:159— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TransfersInSeatTransferTypeValidator.java:159-165 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TransfersTripReferenceValidator.java:182-188 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EntityImplementationGenerator.java:208— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EntityImplementationGenerator.java:208-214 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:157-168 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/OverlappingFrequencyValidator.java:97— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/OverlappingFrequencyValidator.java:97-103 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TimeframeOverlapValidator.java:111-118 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/DateTripsValidator.java:66— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/DateTripsValidator.java:66-72 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/FeedServiceWindowValidator.java:78-85 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
AC4 · Keyboard semantics· Link used as a button (placeholder href) · ×3
Link used as a button (placeholder href) main/src/main/resources/report.html:279— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
Link used as a button (placeholder href) main/src/main/resources/report.html:305— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
Link used as a button (placeholder href) main/src/main/resources/report.html:361— An <a href="#"> (or javascript:) with a click handler is a button dressed as a link — it announces the wrong role and stops working without JS. Use a <button> for an action.
FixmeComment processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableDescriptorGenerator.java:73— // FIXME: Add a way to disable all caching with a command-line flag. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/src/test/java/org/mobilitydata/gtfsvalidator/validator/GtfsFrequencyEndRangeValidatorTest.java:32— // FIXME: Cover autogenerated end-range validators by unit tests in "processor". — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment main/src/test/java/org/mobilitydata/gtfsvalidator/validator/GtfsShapeLatLonValidatorTest.java:31— // FIXME: Cover autogenerated lat-lon validators by unit tests in "processor" (see issue #846).
ClassTooLong: FeedMetadata main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:19— ClassTooLong — 520 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 120 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TableContainerIndexGenerator processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableContainerIndexGenerator.java:33— ClassTooLong — 465 significant lines (blank, comment-only and punctuation-only lines excluded), 19 methods. The bar is 400 significant lines; this is 65 over it, 1.16× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EntityImplementationGenerator processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EntityImplementationGenerator.java:62— ClassTooLong — 413 significant lines (blank, comment-only and punctuation-only lines excluded), 28 methods. The bar is 400 significant lines; this is 13 over it, 1.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×3
Edited copy of a member (8 corresponding lines) core/src/main/java/org/mobilitydata/gtfsvalidator/notice/StartAndEndRangeEqualNotice.java:58— core/src/main/java/org/mobilitydata/gtfsvalidator/notice/StartAndEndRangeEqualNotice.java:58-65 | core/src/main/java/org/mobilitydata/gtfsvalidator/notice/StartAndEndRangeOutOfOrderNotice.java:60-68 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) core/src/main/java/org/mobilitydata/gtfsvalidator/notice/StartAndEndRangeEqualNotice.java:68— core/src/main/java/org/mobilitydata/gtfsvalidator/notice/StartAndEndRangeEqualNotice.java:68-75 | core/src/main/java/org/mobilitydata/gtfsvalidator/notice/StartAndEndRangeOutOfOrderNotice.java:76-84 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/FareAttributeAgencyIdValidator.java:45— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/FareAttributeAgencyIdValidator.java:45-52 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/RouteAgencyIdValidator.java:44-51 — 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.
Duplicated block (9 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:395— main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:395-403 | main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:417-425 — 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 `main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:395` 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 (9 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopStationDistanceValidator.java:218— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopStationDistanceValidator.java:218-226 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopStationDistanceValidator.java:262-270 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) core/src/main/java/org/mobilitydata/gtfsvalidator/type/GtfsDate.java:103— core/src/main/java/org/mobilitydata/gtfsvalidator/type/GtfsDate.java:103-111 | core/src/main/java/org/mobilitydata/gtfsvalidator/type/GtfsTime.java:102-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ParentStationDistanceValidator.java:112— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ParentStationDistanceValidator.java:112-119 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ParentStationDistanceValidator.java:149-156 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (8 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:249— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:249-256 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:310-317 — 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 `main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:249` 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 (8 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:352— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:352-359 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:412-419 — 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 `main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:352` 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.
AC3 · Page structure· Heading level jumps from h2 to h4 · ×2
Heading level jumps from h2 to h4 main/src/main/resources/report.html:252— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Heading level jumps from h2 to h4 web/client/src/routes/rules.html/+page.svelte:361— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Hotspot: core/src/main/java/org/mobilitydata/gtfsvalidator/table/CsvFileLoader.java core/src/main/java/org/mobilitydata/gtfsvalidator/table/CsvFileLoader.java:46— core/src/main/java/org/mobilitydata/gtfsvalidator/table/CsvFileLoader.java changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 18 in CsvFileLoader.load at line 46. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:02:27 -05:00' --until='2026-11-16 19:02:27 -05:00' --full-history --no-merges -- core/src/main/java/org/mobilitydata/gtfsvalidator/table/CsvFileLoader.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/JsonReportSummaryGenerator.java main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/JsonReportSummaryGenerator.java:22— main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/JsonReportSummaryGenerator.java changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 29 in JsonReportSummaryGenerator.<init> at line 22. 1 of those changes was a fix/bug commit, and the other 1 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-18..2026-11-16, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-18 19:02:27 -05:00' --until='2026-11-16 19:02:27 -05:00' --full-history --no-merges -- main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/JsonReportSummaryGenerator.java`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
MethodTooLong: ValidationReportComparator.compareValidationRuns output-comparator/src/main/java/org/mobilitydata/gtfsvalidator/outputcomparator/cli/ValidationReportComparator.java:39— MethodTooLong — compareValidationRuns runs 124 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 24 over it, 1.24× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ColumnarTableContainerGenerator.generateGtfsContainerClass processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/ColumnarTableContainerGenerator.java:80— MethodTooLong — generateGtfsContainerClass runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:135— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:135-143 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:189-197 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:246-256 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:307-317 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.java:52— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.java:52-108 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EndRangeValidatorGenerator.java:58-130 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/LatLonValidatorGenerator.java:60-87 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/MixedCaseValidatorGenerator.java:50-144 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×2
Edited copy of a member (18 corresponding lines) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EndRangeValidatorGenerator.java:141— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EndRangeValidatorGenerator.java:141-159 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/LatLonValidatorGenerator.java:119-136 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/util/StopUtil.java:37— main/src/main/java/org/mobilitydata/gtfsvalidator/util/StopUtil.java:37-55 | main/src/main/java/org/mobilitydata/gtfsvalidator/util/StopUtil.java:78-95 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×2
Edited copy of a member (15 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:340— main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:340-354 | main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:365-383 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/GtfsTripServiceIdForeignKeyValidator.java:53— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/GtfsTripServiceIdForeignKeyValidator.java:53-67 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TimeframeServiceIdForeignKeyValidator.java:51-65 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×2
Edited copy of a member (13 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:393— main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:393-405 | main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:415-427 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) app/gui/src/main/java/org/mobilitydata/gtfsvalidator/app/gui/GtfsValidatorApp.java:218— app/gui/src/main/java/org/mobilitydata/gtfsvalidator/app/gui/GtfsValidatorApp.java:218-231 | app/gui/src/main/java/org/mobilitydata/gtfsvalidator/app/gui/GtfsValidatorApp.java:263-275 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×2
Edited copy of a member (12 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:287— main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:287-298 | main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:692-703 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:664— main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:664-677 | main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:679-690 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Low cohesion: DefaultFieldValidator (LCOM4 5) core/src/main/java/org/mobilitydata/gtfsvalidator/validator/DefaultFieldValidator.java:32— DefaultFieldValidator's methods fall into 5 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 5 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.
Low cohesion: FeedMetadata (LCOM4 5) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:19— FeedMetadata's methods fall into 5 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 5 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.
Dead file (~3 LoC) web/client/src/lib/Alert.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~3 LoC) web/client/src/lib/ButtonContent.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (web/client/src/lib/Button.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
AC3 · Page structure· Page without a main landmark · ×1
Page without a main landmark main/src/main/resources/report.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
JsonReportSummaryGenerator.<init> (cyclomatic 29) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/JsonReportSummaryGenerator.java:22— JsonReportSummaryGenerator.<init> has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GeoJsonFileLoader.extractFeature (cyclomatic 24) main/src/main/java/org/mobilitydata/gtfsvalidator/table/GeoJsonFileLoader.java:122— GeoJsonFileLoader.extractFeature has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CsvFileLoader.load (cyclomatic 18) core/src/main/java/org/mobilitydata/gtfsvalidator/table/CsvFileLoader.java:46— CsvFileLoader.load has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
OverlappingPickupDropOffZoneValidator.validate (cyclomatic 17) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/OverlappingPickupDropOffZoneValidator.java:30— OverlappingPickupDropOffZoneValidator.validate has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Arguments.validate (cyclomatic 16) cli/src/main/java/org/mobilitydata/gtfsvalidator/cli/Arguments.java:202— Arguments.validate has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
GeoJsonFileLoader.extractFeature (cognitive 59) main/src/main/java/org/mobilitydata/gtfsvalidator/table/GeoJsonFileLoader.java:122— GeoJsonFileLoader.extractFeature has cognitive complexity 59 (threshold 15). Drivers by points: if/else 21 (51 pts), loops 2 (5 pts), boolean chains 3 (nesting depth added 33). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
OverlappingPickupDropOffZoneValidator.validate (cognitive 37) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/OverlappingPickupDropOffZoneValidator.java:30— OverlappingPickupDropOffZoneValidator.validate has cognitive complexity 37 (threshold 15). Drivers by points: if/else 7 (25 pts), boolean chains 6, loops 3 (6 pts) (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JsonReportSummaryGenerator.<init> (cognitive 31) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/JsonReportSummaryGenerator.java:22— JsonReportSummaryGenerator.<init> has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 16, boolean chains 8, if/else 5 (7 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ValidationPerformanceCollector.generateLogString (cognitive 27) output-comparator/src/main/java/org/mobilitydata/gtfsvalidator/outputcomparator/io/ValidationPerformanceCollector.java:141— ValidationPerformanceCollector.generateLogString has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 5 (9 pts), ternaries 1 (3 pts), boolean chains 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CsvFileLoader.load (cognitive 24) core/src/main/java/org/mobilitydata/gtfsvalidator/table/CsvFileLoader.java:46— CsvFileLoader.load has cognitive complexity 24 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 3 (5 pts), error handling 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ShapeIncreasingDistanceValidator.validate (cognitive 23) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:58— ShapeIncreasingDistanceValidator.validate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StopTimeTravelSpeedValidator.validateFarStops (cognitive 23) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopTimeTravelSpeedValidator.java:200— StopTimeTravelSpeedValidator.validateFarStops has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (16 pts), loops 3 (7 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CorruptedSourcesCollector.generateLogString (cognitive 23) output-comparator/src/main/java/org/mobilitydata/gtfsvalidator/outputcomparator/io/CorruptedSourcesCollector.java:81— CorruptedSourcesCollector.generateLogString has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 6 (14 pts), if/else 3 (5 pts), boolean chains 2, loops 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ValidationReport.hasOutOfMemoryError (cognitive 21) core/src/main/java/org/mobilitydata/gtfsvalidator/model/ValidationReport.java:136— ValidationReport.hasOutOfMemoryError has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (17 pts), loops 2 (4 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
NoticeSchemaGenerator.generateSchemaForNotice (cognitive 21) core/src/main/java/org/mobilitydata/gtfsvalidator/notice/schema/NoticeSchemaGenerator.java:87— NoticeSchemaGenerator.generateSchemaForNotice has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (16 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CalendarUtil.createServicePeriod (cognitive 21) main/src/main/java/org/mobilitydata/gtfsvalidator/util/CalendarUtil.java:29— CalendarUtil.createServicePeriod has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 4, ternaries 3 (4 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AgencyConsistencyValidator.validate (cognitive 20) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/AgencyConsistencyValidator.java:61— AgencyConsistencyValidator.validate has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (15 pts), loops 3 (5 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PickupDropOffWindowValidator.validate (cognitive 20) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PickupDropOffWindowValidator.java:44— PickupDropOffWindowValidator.validate has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 6 (12 pts), boolean chains 4, if/else 4 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MissingTripEdgeValidator.validate (cognitive 19) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/MissingTripEdgeValidator.java:51— MissingTripEdgeValidator.validate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RouteNameValidator.validate (cognitive 19) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/RouteNameValidator.java:47— RouteNameValidator.validate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (13 pts), boolean chains 6 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Analyser.analyzeGtfsFileType (cognitive 19) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/Analyser.java:50— Analyser.analyzeGtfsFileType has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ParentStationValidator.validate (cognitive 18) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ParentStationValidator.java:72— ParentStationValidator.validate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, loops 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ValidationReportComparator.compareValidationRuns (cognitive 18) output-comparator/src/main/java/org/mobilitydata/gtfsvalidator/outputcomparator/cli/ValidationReportComparator.java:39— ValidationReportComparator.compareValidationRuns has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Arguments.validate (cognitive 17) cli/src/main/java/org/mobilitydata/gtfsvalidator/cli/Arguments.java:202— Arguments.validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 6, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ShapeToStopMatchingValidator.validate (cognitive 17) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:121— ShapeToStopMatchingValidator.validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StopTimeArrivalAndDepartureTimeValidator.validate (cognitive 17) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopTimeArrivalAndDepartureTimeValidator.java:55— StopTimeArrivalAndDepartureTimeValidator.validate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (9 pts), ternaries 1 (4 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocationHasStopTimesValidator.validate (cognitive 16) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/LocationHasStopTimesValidator.java:62— LocationHasStopTimesValidator.validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 4 (5 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PathwayReachableLocationValidator.traversePathways (cognitive 16) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PathwayReachableLocationValidator.java:124— PathwayReachableLocationValidator.traversePathways has cognitive complexity 16 (threshold 15). Drivers by points: if/else 3 (8 pts), loops 4 (6 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StopStationDistanceValidator.validate (cognitive 16) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopStationDistanceValidator.java:76— StopStationDistanceValidator.validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 5 (7 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StopTimeTravelSpeedValidator.validateConsecutiveStops (cognitive 16) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopTimeTravelSpeedValidator.java:262— StopTimeTravelSpeedValidator.validateConsecutiveStops has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), loops 2 (5 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
StopTimesTripBlockOrderValidator.validate (cognitive 16) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopTimesTripBlockOrderValidator.java:36— StopTimesTripBlockOrderValidator.validate has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 2, loops 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
load (cognitive 16) web/client/src/routes/rules.html/+page.js:3— load has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (8 pts), boolean chains 2, error handling 2, other 2, ternaries 1 (2 pts) (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FileTooLong: model/FeedMetadata.java main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java— FileTooLong — 536 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: FeedMetadata (19-841). The bar is 500 significant lines; this is 36 over it, 1.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×1
Edited copy of a member (24 corresponding lines) core/src/main/java/org/mobilitydata/gtfsvalidator/io/ValidationReportDeserializer.java:88— core/src/main/java/org/mobilitydata/gtfsvalidator/io/ValidationReportDeserializer.java:88-111 | core/src/main/java/org/mobilitydata/gtfsvalidator/io/ValidationReportDeserializer.java:116-139 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) core/src/main/java/org/mobilitydata/gtfsvalidator/validator/DefaultValidatorProvider.java:87— core/src/main/java/org/mobilitydata/gtfsvalidator/validator/DefaultValidatorProvider.java:87-113 | core/src/main/java/org/mobilitydata/gtfsvalidator/validator/DefaultValidatorProvider.java:120-140 | core/src/main/java/org/mobilitydata/gtfsvalidator/validator/DefaultValidatorProvider.java:145-167 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 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 (22 corresponding lines) · ×1
Edited copy of a member (22 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/FareAttributeAgencyIdValidator.java:55— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/FareAttributeAgencyIdValidator.java:55-78 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/RouteAgencyIdValidator.java:54-75 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) app/gui/src/main/java/org/mobilitydata/gtfsvalidator/app/gui/GtfsValidatorApp.java:200— app/gui/src/main/java/org/mobilitydata/gtfsvalidator/app/gui/GtfsValidatorApp.java:200-216 | app/gui/src/main/java/org/mobilitydata/gtfsvalidator/app/gui/GtfsValidatorApp.java:245-261 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:192— main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:192-205 | main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/FeedMetadata.java:215-228 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×1
Edited copy of a member (11 corresponding lines) app/gui/src/main/java/org/mobilitydata/gtfsvalidator/app/gui/GtfsValidatorApp.java:486— app/gui/src/main/java/org/mobilitydata/gtfsvalidator/app/gui/GtfsValidatorApp.java:486-498 | cli/src/main/java/org/mobilitydata/gtfsvalidator/cli/Arguments.java:167-177 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×1
Edited copies of one member (3 members, 13+ corresponding lines) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:430— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:430-443 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableColumnsGenerator.java:445-458 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/TableDescriptorGenerator.java:328-340 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) core/src/main/java/org/mobilitydata/gtfsvalidator/notice/schema/FieldSchema.java:39— core/src/main/java/org/mobilitydata/gtfsvalidator/notice/schema/FieldSchema.java:39-50 | core/src/main/java/org/mobilitydata/gtfsvalidator/notice/schema/FieldTypeSchema.java:62-74 | core/src/main/java/org/mobilitydata/gtfsvalidator/util/ServicePeriod.java:183-196 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies 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) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.java:42— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.java:42-50 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/LatLonValidatorGenerator.java:50-58 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/MixedCaseValidatorGenerator.java:40-48 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×1
Edited copy of a member (6 corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TransferDistanceValidator.java:98— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TransferDistanceValidator.java:98-103 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TransferWalkingSpeedValidator.java:132-138 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×1
Edited copy of a member (5 corresponding lines) core/src/main/java/org/mobilitydata/gtfsvalidator/notice/RuntimeExceptionInLoaderError.java:27— core/src/main/java/org/mobilitydata/gtfsvalidator/notice/RuntimeExceptionInLoaderError.java:27-31 | core/src/main/java/org/mobilitydata/gtfsvalidator/notice/RuntimeExceptionInValidatorError.java:28-33 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×1
Edited copies of one member (3 members, 5+ corresponding lines) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/LocationHasStopTimesValidator.java:147— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/LocationHasStopTimesValidator.java:147-152 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PathwayDanglingGenericNodeValidator.java:100-105 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopZoneIdValidator.java:173-177 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 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 (20 lines × 2) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.java:53— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.java:53-72 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/MixedCaseValidatorGenerator.java:51-70 — 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 `processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.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 (19 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/MissingTripEdgeValidator.java:57— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/MissingTripEdgeValidator.java:57-75 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/MissingTripEdgeValidator.java:76-94 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) core/src/main/java/org/mobilitydata/gtfsvalidator/io/ValidationReportDeserializer.java:89— core/src/main/java/org/mobilitydata/gtfsvalidator/io/ValidationReportDeserializer.java:89-109 | core/src/main/java/org/mobilitydata/gtfsvalidator/io/ValidationReportDeserializer.java:117-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopTimeTravelSpeedValidator.java:501— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopTimeTravelSpeedValidator.java:501-516 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/StopTimeTravelSpeedValidator.java:592-607 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (15 lines × 4) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.java:56— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.java:56-70 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EndRangeValidatorGenerator.java:62-76 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/LatLonValidatorGenerator.java:64-78 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/MixedCaseValidatorGenerator.java:54-68 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/CurrencyAmountValidatorGenerator.java:56` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) core/src/main/java/org/mobilitydata/gtfsvalidator/parsing/RowParser.java:243— core/src/main/java/org/mobilitydata/gtfsvalidator/parsing/RowParser.java:243-255 | core/src/main/java/org/mobilitydata/gtfsvalidator/parsing/RowParser.java:259-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (11–12 lines × 2) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PathwayStopAccessValidator.java:65— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PathwayStopAccessValidator.java:65-76 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PathwayStopAccessValidator.java:79-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–10 lines × 2) processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EndRangeValidatorGenerator.java:142— processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/EndRangeValidatorGenerator.java:142-148 | processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/LatLonValidatorGenerator.java:120-129 — 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 `processor/src/main/java/org/mobilitydata/gtfsvalidator/processor/LatLonValidatorGenerator.java:120` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7 lines × 4) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:136— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:136-142 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:190-196 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:247-253 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:308-314 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:255` calls `getDistanceMeters`, `shapePtLatLon` and `main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeIncreasingDistanceValidator.java:143` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 3) main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:287— main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:287-293 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:351-357 | main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java:411-417 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (43 lines × 2) core/src/main/java/org/mobilitydata/gtfsvalidator/notice/PointNearOriginNotice.java:58— core/src/main/java/org/mobilitydata/gtfsvalidator/notice/PointNearOriginNotice.java:58-100 | core/src/main/java/org/mobilitydata/gtfsvalidator/notice/PointNearPoleNotice.java:58-100 — before extracting anything, compare `core/src/main/java/org/mobilitydata/gtfsvalidator/notice/PointNearOriginNotice.java` and `core/src/main/java/org/mobilitydata/gtfsvalidator/notice/PointNearPoleNotice.java` as WHOLE FILES: 92% 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 `core/src/main/java/org/mobilitydata/gtfsvalidator/notice/PointNearOriginNotice.java:58` 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.
End-of-life framework: Spring Boot 2 web/service/build.gradle:1— web/service/build.gradle depends on `org.springframework.boot` at a version that pins Spring Boot 2, and Spring Boot 2.x, open-source support ended 2023-11-24. The constraint cannot admit a different major, so this repository stays on it until the declaration is edited. An end-of-life framework receives no further releases, including security releases.
Off the main sequence: :core — :core: abstractness 0.16, instability 0.13, distance 0.72 — zone of pain — concrete and depended on by 7 project(s), so it's rigid to change.
Unfinished stub — returns a placeholder under a TODO marker main/src/main/java/org/mobilitydata/gtfsvalidator/table/GtfsGeoJsonFeature.java:45— `csvRowNumber` is a shipped method whose whole body returns a default value under a TODO/FIXME — a placeholder standing in for the implementation. Implement it or remove it.
Outbound HTTP without resilience core/src/main/java/org/mobilitydata/gtfsvalidator/util/HttpGetUtil.java:62— `HttpClients.createDefault(` makes an outbound HTTP call, and nothing bounds it: no timeout, deadline, retry or circuit breaker is set for it here, and the client has no process-wide default. A slow or failing dependency will hold this service's request, thread or connection until the call gives up on its own — or never, for a client with no default timeout.
Complex function load (cyclomatic 12, cognitive 16) web/client/src/routes/rules.html/+page.js:3— load has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateReport (cyclomatic 11, cognitive 12) web/client/src/routes/+page.svelte:349— generateReport has cyclomatic complexity 11 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
R3 · Large Files· web/client/src/routes/+page.svelte · ×1
web/client/src/routes/+page.svelte: 443 lines of code web/client/src/routes/+page.svelte:1— web/client/src/routes/+page.svelte has 443 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R6 · Tooling· This package's lint script runs in no CI job · ×1
This package's lint script runs in no CI job web/client/package.json:13— The package in `web/client` declares the lint script `lint` (`prettier --plugin-search-dir . --check . && eslint .`), but no step of this repository's CI runs it, by name, through another script, a Makefile target or a workspace runner, and no CI step runs the linter over the package itself. The rules it sets are enforced nowhere a pull request can fail. Run it in CI: a step that runs `npm run lint` in `web/client` (or the workspace's task runner).
Dead file (~44 LoC) web/client/src/lib/CopyButton.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (web/client/src/lib/StatusModal.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~40 LoC) web/client/src/lib/Button.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (web/client/src/lib/CopyButton.svelte, web/client/src/lib/StatusModal.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~38 LoC) web/client/src/lib/forms/FileField.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~37 LoC) web/client/src/lib/DropTarget.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~35 LoC) web/client/src/lib/forms/SelectField.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~31 LoC) web/client/src/lib/countryCodes.js— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~28 LoC) web/client/src/lib/forms/TextField.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~27 LoC) web/client/src/lib/StatusModal.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~9 LoC) web/client/src/lib/forms/LabeledField.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), but 3 in-repo import(s) from 3 other file(s) do name it (web/client/src/lib/forms/FileField.svelte, web/client/src/lib/forms/SelectField.svelte, web/client/src/lib/forms/TextField.svelte) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~5 LoC) web/client/src/lib/forms/Form.svelte— no import path from any entry point (8 application, 8 tooling, 4 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Third-party script without Subresource Integrity main/src/main/resources/report.html:7— `https://code.jquery.com/jquery-3.6.0.min.js` is executed by this page with no Subresource Integrity. Whoever can answer that request — the CDN, anyone who compromises it, anyone on the network path — runs arbitrary script in this page's origin, with its session. The URL also names no version, so it resolves to whatever that origin serves at fetch time — the executed bytes can change with nobody touching this repository. 3 such include(s) across the repository's markup.
Duplicated predicate main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePoints.java:91— `!points.isEmpty() && Iterables.getLast(points).hasUserDistance()` appears character-identically in 2 files — main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePoints.java, main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/StopPoints.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate main/src/main/java/org/mobilitydata/gtfsvalidator/validator/FareAttributeAgencyIdValidator.java:46— `agencyTable == null || agencyTable.entityCount() == 0` appears character-identically in 2 files — main/src/main/java/org/mobilitydata/gtfsvalidator/validator/FareAttributeAgencyIdValidator.java, main/src/main/java/org/mobilitydata/gtfsvalidator/validator/RouteAgencyIdValidator.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate main/src/main/java/org/mobilitydata/gtfsvalidator/validator/GtfsTripServiceIdForeignKeyValidator.java:73— `calendarContainer.byServiceId(childKey).isPresent() || !calendarDateContainer.byServiceId(childKey).isEmpty()` appears character-identically in 2 files — main/src/main/java/org/mobilitydata/gtfsvalidator/validator/GtfsTripServiceIdForeignKeyValidator.java, main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TimeframeServiceIdForeignKeyValidator.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PickupDropOffTypeValidator.java:48— `header.hasColumn(GtfsStopTime.START_PICKUP_DROP_OFF_WINDOW_FIELD_NAME) || header.hasColumn(GtfsStopTime.END_PICKUP_DROP_OFF_WINDOW_FIELD_NAM…` appears character-identically in 2 files — main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PickupDropOffTypeValidator.java, main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PickupDropOffWindowValidator.java. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Interpolated log message defeats structured logging web/service/src/main/java/org/mobilitydata/gtfsvalidator/web/service/util/StorageHelper.java:207— `debug` at line 207 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging web/service/src/main/java/org/mobilitydata/gtfsvalidator/web/service/util/StorageHelper.java:210— `debug` at line 210 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.debug("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging web/service/src/main/java/org/mobilitydata/gtfsvalidator/web/service/util/StorageHelper.java:212— `error` at line 212 is handed a message assembled at the call — a string concatenated with a value, or `String.format` — through SLF4J or log4j 2, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.error("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or `log.atInfo().addKeyValue("order_id", orderId).log("order moved")` with SLF4J 2's fluent API. An exception goes last, as the throwable argument, not into the text.
Fat interface: GtfsStopSchema (16 abstract methods) main/src/main/java/org/mobilitydata/gtfsvalidator/table/GtfsStopSchema.java:24— `GtfsStopSchema` declares 16 abstract methods: `levelId`, `locationType`, `parentStation`, `platformCode`, `stopAccess`, `stopCode`, `stopDesc`, `stopId`, `stopLat`, `stopLon`, `stopName`, `stopTimezone`, `stopUrl`, `ttsStopName`, `wheelchairBoarding`, `zoneId`. 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: GtfsStopTimeSchema (18 abstract methods) main/src/main/java/org/mobilitydata/gtfsvalidator/table/GtfsStopTimeSchema.java:38— `GtfsStopTimeSchema` declares 18 abstract methods: `arrivalTime`, `continuousDropOff`, `continuousPickup`, `departureTime`, `dropOffBookingRuleId`, `dropOffType`, `endPickupDropOffWindow`, `locationGroupId`, `locationId`, `pickupBookingRuleId`, `pickupType`, `shapeDistTraveled`, `startPickupDropOffWindow`, `stopHeadsign`, `stopId`, `stopSequence`, `timepoint`, `tripId`. 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.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 6 significant file(s) lose their only recent owner: main/src/main/java/org/mobilitydata/gtfsvalidator/validator/ShapeToStopMatchingValidator.java, output-comparator/src/main/java/org/mobilitydata/gtfsvalidator/outputcomparator/io/ValidationPerformanceCollector.java, main/src/main/java/org/mobilitydata/gtfsvalidator/util/shape/ShapePoints.java, output-comparator/src/main/java/org/mobilitydata/gtfsvalidator/outputcomparator/cli/ValidationReportComparator.java, core/src/main/java/org/mobilitydata/gtfsvalidator/model/ValidationReport.java, output-comparator/src/main/java/org/mobilitydata/gtfsvalidator/outputcomparator/io/OutOfMemorySourcesCollector.java. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 5 significant file(s) lose their only recent owner: core/src/main/java/org/mobilitydata/gtfsvalidator/notice/NoticeContainer.java, main/src/main/java/org/mobilitydata/gtfsvalidator/reportsummary/model/ReportSummary.java, core/src/main/java/org/mobilitydata/gtfsvalidator/notice/Notice.java, core/src/main/java/org/mobilitydata/gtfsvalidator/validator/ValidatorUtil.java, core/src/main/java/org/mobilitydata/gtfsvalidator/notice/ResolvedNotice.java. Pair on, review, or document these before any departure.
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×2
Projects may be oversized for their cohesion main/build.gradle:1— `main` (17884 LoC, 222 module-visible types across 10 directories) overshoots its size bounds. 2 of 15 build unit(s) (Gradle, Python) overshoot their size bounds, lowering Project Cohesion to 7.5/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.
Projects may be oversized for their cohesion core/build.gradle:1— `core` (9855 LoC, 142 module-visible types across 13 directories) overshoots its size bounds. 2 of 15 build unit(s) (Gradle, Python) overshoot their size bounds, lowering Project Cohesion to 7.5/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.
Irreversible deploy step: sync deletes the live copy REDACTED:221— This step syncs the release over the live copy with delete (`actions/upload-artifact/merge` with `delete-merged: true`): files the new build lacks are removed in place and the rest are overwritten, so the previous release is gone and a half-finished sync serves a mix of both. There is no staged copy to switch back to.
Irreversible deploy step: sync deletes the live copy REDACTED:108— This step syncs the release over the live copy with delete (`actions/upload-artifact/merge` with `delete-merged: true`): files the new build lacks are removed in place and the rest are overwritten, so the previous release is gone and a half-finished sync serves a mix of both. There is no staged copy to switch back to.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 4 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (16 single-owned of 205 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 205 of the 444 production source files in this repository met that bar). They are anonymized user #3 (2 file(s)), anonymized user #4 (1 file(s)), anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: main/src/main/java/org/mobilitydata/gtfsvalidator/validator/PathwayModeFieldsValidator.java, main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TripShapeIdConditionalValidator.java, main/src/main/java/org/mobilitydata/gtfsvalidator/validator/MatchingFeedAndAgencyLangValidator.java, core/src/main/java/org/mobilitydata/gtfsvalidator/notice/MixedCaseRecommendedFieldNotice.java, main/src/main/java/org/mobilitydata/gtfsvalidator/validator/TransferStopIdsConditionalValidator.java.
No ADRs found web/service/build.gradle:3— 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 `web/service/build.gradle` makes this repository a deployable product (line 3).
D28 · Secrets (history)· Rotate the exposed credentials · ×1
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· Architecture diagram out of date · ×1
Architecture diagram out of date docs/ARCHITECTURE.md:5— `docs/ARCHITECTURE.md` draws the system's parts, and the drawing no longer matches the code: it leaves out `output-comparator`, which the repository has beside the units it does draw. A diagram of a system that no longer exists misleads the reader it was drawn for, so it is not credited as documenting the shape.
Logging is not universal — Only 4/8 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `app/pkg`, `cli`, `output-comparator`, `web/client`.
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 16 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 web/client/package.json:18— `web/client/package.json` 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`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types· Java packages are not null-marked everywhere · ×1
Java packages are not null-marked everywhere — 0/39 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`.
Skipped (documented): outOfMemoryErrorWithoutReport_isReported output-comparator/src/test/java/org/mobilitydata/gtfsvalidator/outputcomparator/cli/ValidationReportComparatorTest.java:470— Skipped with a documented reason — a deferral, not lazy debt: skipped at run time by a JUnit assumption
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.
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 01a1e749-c149-77f1-a99c-08baa8ebb2a3 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 192 · Warnings: 207 · Recommendations: 31 · Info: 167 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 02:15 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.