Public report of PartlySaneStudios/partly-sane-skies, 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, 04:52 UTC · Survey ID cd_068545fcc49b45eea681b56fc7868d58
PartlySaneStudios/partly-sane-skies
Measured 17 November 2026, 04:52 UTC, at code version a8b5646
Bus factor is not measured: No living knowledge left to concentrate.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A small codebase: 19,592 lines of product code in 1 project, tests not counted · Estimated rebuild effort: about 0.1 person-years · Weakest lens: Production Readiness, 35.0
Findings by how serious they are
9 critical105 serious120 minor
14 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
17 November 2026, 04:52 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
40of 40 dimensions measured by tools.
229of 234 findings point to an exact file and line, so you can open each one in the code. The other 5 concern the repository as a whole, such as missing documentation.
40dimensions across 5 lenses, read from 19,592 lines of product code in 1 project.
PartlySaneStudios/partly-sane-skies falls short of our standard for production because the project has no automated tests and we found no automated security scanning of the code, its secrets or its dependencies. It scores 47.9 out of 100 and is rated Weak, and eight of its nine critical findings are security problems.
Production Readiness, at 35.0, is the weakest lens and counts most in the score. The best first step for the work it takes is improving the documentation, worth about 7.9 points. Adding automated security scanning would lift Production Readiness itself, worth about 8.1 points. Raising Production Readiness to 70 would lift the score to about 58.7.
Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with. Two secrets can leak from the build pipeline, and the project has no automated tests, so a change can break it without warning. Pinning each tool to an exact version, limiting each secret to its own step and adding automated tests would close these risks. Giving the pull-request workflow read-only access would fix the pipeline that outsiders can trigger with write access.
The product code is 19,592 lines, about €20,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 Production Readiness rose from 35.0 to 70, the lowest score rated Strong, the score would rise from 47.9 to about 58.7.
Code composition: what the lines of code are
Product code 100%
Rebuild cost: about €20,000 · Estimate
Cost to rebuild
€6,500 to €33,000, for 109 to 345 hours of work, about 0.1 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 48. 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
Small: 19,592 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 Documentation finding(s) in Documentation Quality — start with README.md.
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.
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 €20,000 to build again, about 0.1 person-years of work. Its weakest lens is Production Readiness, at 35.0 (Weak). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Documentation finding(s) in Documentation Quality. Of all the actions in this report, it raises the score most for the work it takes: about 7.9 points for low effort, because it clears the 1 Documentation Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
99 modules, with 119 dependencies between them. 2 loops run through 4 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 59 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
PartlySaneSkies uses config.psconfig, so a change to config.psconfig can break PartlySaneSkies, while a change to PartlySaneSkies can't break config.psconfig.
Position
Below the diagonal: PartlySaneSkies uses a module listed above it, which is the healthy direction.
api.events.EventHandler uses api.events.PSSEvent, so a change to api.events.PSSEvent can break api.events.EventHandler, while a change to api.events.EventHandler can't break api.events.PSSEvent.
Position
Below the diagonal: api.events.EventHandler uses a module listed above it, which is the healthy direction.
features.debug.CrystalHollowsGemstoneMapper uses utils.geometry.vectors, so a change to utils.geometry.vectors can break features.debug.CrystalHollowsGemstoneMapper, while a change to features.debug.CrystalHollowsGemstoneMapper can't break utils.geometry.vectors.
Position
Below the diagonal: features.debug.CrystalHollowsGemstoneMapper uses a module listed above it, which is the healthy direction.
features.dungeons.TerminalWaypoints uses features.dungeons.TerminalWaypoints.F7Puzzle, so a change to features.dungeons.TerminalWaypoints.F7Puzzle can break features.dungeons.TerminalWaypoints, while a change to features.dungeons.TerminalWaypoints can't break features.dungeons.TerminalWaypoints.F7Puzzle.
Position
Below the diagonal: features.dungeons.TerminalWaypoints uses a module listed above it, which is the healthy direction.
features.dungeons.TerminalWaypoints uses utils.geometry.vectors, so a change to utils.geometry.vectors can break features.dungeons.TerminalWaypoints, while a change to features.dungeons.TerminalWaypoints can't break utils.geometry.vectors.
Position
Below the diagonal: features.dungeons.TerminalWaypoints uses a module listed above it, which is the healthy direction.
features.mining.crystalhollows.gemstonewaypoints.GemstoneData uses utils.geometry.vectors, so a change to utils.geometry.vectors can break features.mining.crystalhollows.gemstonewaypoints.GemstoneData, while a change to features.mining.crystalhollows.gemstonewaypoints.GemstoneData can't break utils.geometry.vectors.
Position
Below the diagonal: features.mining.crystalhollows.gemstonewaypoints.GemstoneData uses a module listed above it, which is the healthy direction.
render.gui.components uses render.gui.hud.cooldown, so a change to render.gui.hud.cooldown can break render.gui.components, while a change to render.gui.components can't break render.gui.hud.cooldown.
Position
Below the diagonal: render.gui.components uses a module listed above it, which is the healthy direction.
api.events uses api.events.PSSEvent, so a change to api.events.PSSEvent can break api.events, while a change to api.events can't break api.events.PSSEvent.
Position
Below the diagonal: api.events uses a module listed above it, which is the healthy direction.
api.events uses api.events.PSSEvents, so a change to api.events.PSSEvents can break api.events, while a change to api.events can't break api.events.PSSEvents.
Position
Below the diagonal: api.events uses a module listed above it, which is the healthy direction.
api.events uses api.events.EventHandler, so a change to api.events.EventHandler can break api.events, while a change to api.events can't break api.events.EventHandler.
Position
Below the diagonal: api.events uses a module listed above it, which is the healthy direction.
features.discord.webhooks.WebhookMenu uses config.psconfig, so a change to config.psconfig can break features.discord.webhooks.WebhookMenu, while a change to features.discord.webhooks.WebhookMenu can't break config.psconfig.
Position
Below the diagonal: features.discord.webhooks.WebhookMenu uses a module listed above it, which is the healthy direction.
features.discord.webhooks.WebhookMenu uses render.gui.components, so a change to render.gui.components can break features.discord.webhooks.WebhookMenu, while a change to features.discord.webhooks.WebhookMenu can't break render.gui.components.
Position
Below the diagonal: features.discord.webhooks.WebhookMenu uses a module listed above it, which is the healthy direction.
18→24 features.discord.webhooks.WebhookMenu uses features.discord.webhookspart of a loop✕
Connections
3 pairs of types, where a type in features.discord.webhooks.WebhookMenu uses a type in features.discord.webhooks.
features.discord.webhooks.WebhookMenu uses features.discord.webhooks, so a change to features.discord.webhooks can break features.discord.webhooks.WebhookMenu, while a change to features.discord.webhooks.WebhookMenu can't break features.discord.webhooks.
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.
events.minecraft uses api.events.PSSEvent, so a change to api.events.PSSEvent can break events.minecraft, while a change to events.minecraft can't break api.events.PSSEvent.
Position
Below the diagonal: events.minecraft uses a module listed above it, which is the healthy direction.
events.minecraft.player uses utils.geometry.vectors, so a change to utils.geometry.vectors can break events.minecraft.player, while a change to events.minecraft.player can't break utils.geometry.vectors.
Position
Below the diagonal: events.minecraft.player uses a module listed above it, which is the healthy direction.
events.minecraft.player uses api.events, so a change to api.events can break events.minecraft.player, while a change to events.minecraft.player can't break api.events.
Position
Below the diagonal: events.minecraft.player uses a module listed above it, which is the healthy direction.
events.minecraft.render uses api.events, so a change to api.events can break events.minecraft.render, while a change to events.minecraft.render can't break api.events.
Position
Below the diagonal: events.minecraft.render uses a module listed above it, which is the healthy direction.
events.skyblock.dungeons uses api.events, so a change to api.events can break events.skyblock.dungeons, while a change to events.skyblock.dungeons can't break api.events.
Position
Below the diagonal: events.skyblock.dungeons uses a module listed above it, which is the healthy direction.
features.discord.webhooks uses config.psconfig, so a change to config.psconfig can break features.discord.webhooks, while a change to features.discord.webhooks can't break config.psconfig.
Position
Below the diagonal: features.discord.webhooks uses a module listed above it, which is the healthy direction.
features.discord.webhooks uses features.discord.webhooks.WebhookMenu, so a change to features.discord.webhooks.WebhookMenu can break features.discord.webhooks, while a change to features.discord.webhooks can't break features.discord.webhooks.WebhookMenu.
Position
Below the diagonal: features.discord.webhooks uses a module listed above it, which is the healthy direction.
data.skyblockdata uses events.data, so a change to events.data can break data.skyblockdata, while a change to data.skyblockdata can't break events.data.
Position
Below the diagonal: data.skyblockdata uses a module listed above it, which is the healthy direction.
features.debug uses utils.geometry.vectors, so a change to utils.geometry.vectors can break features.debug, while a change to features.debug can't break utils.geometry.vectors.
Position
Below the diagonal: features.debug uses a module listed above it, which is the healthy direction.
features.debug uses features.debug.CrystalHollowsGemstoneMapper, so a change to features.debug.CrystalHollowsGemstoneMapper can break features.debug, while a change to features.debug can't break features.debug.CrystalHollowsGemstoneMapper.
Position
Below the diagonal: features.debug uses a module listed above it, which is the healthy direction.
features.debug uses events.minecraft, so a change to events.minecraft can break features.debug, while a change to features.debug can't break events.minecraft.
Position
Below the diagonal: features.debug uses a module listed above it, which is the healthy direction.
features.debug uses events.minecraft.render, so a change to events.minecraft.render can break features.debug, while a change to features.debug can't break events.minecraft.render.
Position
Below the diagonal: features.debug uses a module listed above it, which is the healthy direction.
features.debug uses features.discord.webhooks, so a change to features.discord.webhooks can break features.debug, while a change to features.debug can't break features.discord.webhooks.
Position
Below the diagonal: features.debug uses a module listed above it, which is the healthy direction.
features.dungeons uses features.dungeons.TerminalWaypoints.F7Puzzle, so a change to features.dungeons.TerminalWaypoints.F7Puzzle can break features.dungeons, while a change to features.dungeons can't break features.dungeons.TerminalWaypoints.F7Puzzle.
Position
Below the diagonal: features.dungeons uses a module listed above it, which is the healthy direction.
features.dungeons uses utils.geometry.vectors, so a change to utils.geometry.vectors can break features.dungeons, while a change to features.dungeons can't break utils.geometry.vectors.
Position
Below the diagonal: features.dungeons uses a module listed above it, which is the healthy direction.
features.dungeons uses features.dungeons.TerminalWaypoints, so a change to features.dungeons.TerminalWaypoints can break features.dungeons, while a change to features.dungeons can't break features.dungeons.TerminalWaypoints.
Position
Below the diagonal: features.dungeons uses a module listed above it, which is the healthy direction.
features.dungeons uses events.data, so a change to events.data can break features.dungeons, while a change to features.dungeons can't break events.data.
Position
Below the diagonal: features.dungeons uses a module listed above it, which is the healthy direction.
features.dungeons uses events.minecraft, so a change to events.minecraft can break features.dungeons, while a change to features.dungeons can't break events.minecraft.
Position
Below the diagonal: features.dungeons uses a module listed above it, which is the healthy direction.
features.dungeons uses events.minecraft.render, so a change to events.minecraft.render can break features.dungeons, while a change to features.dungeons can't break events.minecraft.render.
Position
Below the diagonal: features.dungeons uses a module listed above it, which is the healthy direction.
features.dungeons uses events.skyblock.dungeons, so a change to events.skyblock.dungeons can break features.dungeons, while a change to features.dungeons can't break events.skyblock.dungeons.
Position
Below the diagonal: features.dungeons uses a module listed above it, which is the healthy direction.
features.farming uses events.minecraft.player, so a change to events.minecraft.player can break features.farming, while a change to features.farming can't break events.minecraft.player.
Position
Below the diagonal: features.farming uses a module listed above it, which is the healthy direction.
features.foraging uses render.gui.hud.cooldown, so a change to render.gui.hud.cooldown can break features.foraging, while a change to features.foraging can't break render.gui.hud.cooldown.
Position
Below the diagonal: features.foraging uses a module listed above it, which is the healthy direction.
features.foraging uses utils.geometry.vectors, so a change to utils.geometry.vectors can break features.foraging, while a change to features.foraging can't break utils.geometry.vectors.
Position
Below the diagonal: features.foraging uses a module listed above it, which is the healthy direction.
features.foraging uses events.minecraft.player, so a change to events.minecraft.player can break features.foraging, while a change to features.foraging can't break events.minecraft.player.
Position
Below the diagonal: features.foraging uses a module listed above it, which is the healthy direction.
features.mining.crystalhollows.gemstonewaypoints uses utils.geometry.vectors, so a change to utils.geometry.vectors can break features.mining.crystalhollows.gemstonewaypoints, while a change to features.mining.crystalhollows.gemstonewaypoints can't break utils.geometry.vectors.
Position
Below the diagonal: features.mining.crystalhollows.gemstonewaypoints uses a module listed above it, which is the healthy direction.
2 pairs of types, where a type in features.mining.crystalhollows.gemstonewaypoints uses a type in features.mining.crystalhollows.gemstonewaypoints.GemstoneData.
features.mining.crystalhollows.gemstonewaypoints uses features.mining.crystalhollows.gemstonewaypoints.GemstoneData, so a change to features.mining.crystalhollows.gemstonewaypoints.GemstoneData can break features.mining.crystalhollows.gemstonewaypoints, while a change to features.mining.crystalhollows.gemstonewaypoints can't break features.mining.crystalhollows.gemstonewaypoints.GemstoneData.
Position
Below the diagonal: features.mining.crystalhollows.gemstonewaypoints uses a module listed above it, which is the healthy direction.
features.mining.crystalhollows.gemstonewaypoints uses events.data, so a change to events.data can break features.mining.crystalhollows.gemstonewaypoints, while a change to features.mining.crystalhollows.gemstonewaypoints can't break events.data.
Position
Below the diagonal: features.mining.crystalhollows.gemstonewaypoints uses a module listed above it, which is the healthy direction.
features.mining.crystalhollows.gemstonewaypoints uses events.minecraft.render, so a change to events.minecraft.render can break features.mining.crystalhollows.gemstonewaypoints, while a change to features.mining.crystalhollows.gemstonewaypoints can't break events.minecraft.render.
Position
Below the diagonal: features.mining.crystalhollows.gemstonewaypoints uses a module listed above it, which is the healthy direction.
features.mining.events uses events.minecraft, so a change to events.minecraft can break features.mining.events, while a change to features.mining.events can't break events.minecraft.
Position
Below the diagonal: features.mining.events uses a module listed above it, which is the healthy direction.
31→34 features.mining.events uses events.skyblock.miningpart of a loop✕
Connections
1 pair of types, where a type in features.mining.events uses a type in events.skyblock.mining.
features.mining.events uses events.skyblock.mining, so a change to events.skyblock.mining can break features.mining.events, while a change to features.mining.events can't break events.skyblock.mining.
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.
data.cache.PetData uses data.skyblockdata, so a change to data.skyblockdata can break data.cache.PetData, while a change to data.cache.PetData can't break data.skyblockdata.
Position
Below the diagonal: data.cache.PetData uses a module listed above it, which is the healthy direction.
data.cache.VisitorLogbookData uses data.skyblockdata, so a change to data.skyblockdata can break data.cache.VisitorLogbookData, while a change to data.cache.VisitorLogbookData can't break data.skyblockdata.
Position
Below the diagonal: data.cache.VisitorLogbookData uses a module listed above it, which is the healthy direction.
events.skyblock.mining uses api.events, so a change to api.events can break events.skyblock.mining, while a change to events.skyblock.mining can't break api.events.
Position
Below the diagonal: events.skyblock.mining uses a module listed above it, which is the healthy direction.
events.skyblock.mining uses features.mining.events, so a change to features.mining.events can break events.skyblock.mining, while a change to events.skyblock.mining can't break features.mining.events.
Position
Below the diagonal: events.skyblock.mining uses a module listed above it, which is the healthy direction.
features.dungeons.party.partymanager uses events.minecraft, so a change to events.minecraft can break features.dungeons.party.partymanager, while a change to features.dungeons.party.partymanager can't break events.minecraft.
Position
Below the diagonal: features.dungeons.party.partymanager uses a module listed above it, which is the healthy direction.
features.dungeons.party.partymanager uses data.skyblockdata, so a change to data.skyblockdata can break features.dungeons.party.partymanager, while a change to features.dungeons.party.partymanager can't break data.skyblockdata.
Position
Below the diagonal: features.dungeons.party.partymanager uses a module listed above it, which is the healthy direction.
features.farming.garden uses features.gui, so a change to features.gui can break features.farming.garden, while a change to features.farming.garden can't break features.gui.
Position
Below the diagonal: features.farming.garden uses a module listed above it, which is the healthy direction.
features.farming.garden uses events.data, so a change to events.data can break features.farming.garden, while a change to features.farming.garden can't break events.data.
Position
Below the diagonal: features.farming.garden uses a module listed above it, which is the healthy direction.
features.farming.garden uses events.minecraft, so a change to events.minecraft can break features.farming.garden, while a change to features.farming.garden can't break events.minecraft.
Position
Below the diagonal: features.farming.garden uses a module listed above it, which is the healthy direction.
features.farming.garden uses features.discord.webhooks, so a change to features.discord.webhooks can break features.farming.garden, while a change to features.farming.garden can't break features.discord.webhooks.
Position
Below the diagonal: features.farming.garden uses a module listed above it, which is the healthy direction.
features.farming.garden uses data.skyblockdata, so a change to data.skyblockdata can break features.farming.garden, while a change to features.farming.garden can't break data.skyblockdata.
Position
Below the diagonal: features.farming.garden uses a module listed above it, which is the healthy direction.
features.items.rngdrop uses render.gui.components, so a change to render.gui.components can break features.items.rngdrop, while a change to features.items.rngdrop can't break render.gui.components.
Position
Below the diagonal: features.items.rngdrop uses a module listed above it, which is the healthy direction.
features.items.rngdrop uses features.discord.webhooks, so a change to features.discord.webhooks can break features.items.rngdrop, while a change to features.items.rngdrop can't break features.discord.webhooks.
Position
Below the diagonal: features.items.rngdrop uses a module listed above it, which is the healthy direction.
features.items.rngdrop uses data.skyblockdata, so a change to data.skyblockdata can break features.items.rngdrop, while a change to features.items.rngdrop can't break data.skyblockdata.
Position
Below the diagonal: features.items.rngdrop uses a module listed above it, which is the healthy direction.
features.skills uses events.minecraft, so a change to events.minecraft can break features.skills, while a change to features.skills can't break events.minecraft.
Position
Below the diagonal: features.skills uses a module listed above it, which is the healthy direction.
features.skills uses features.discord.webhooks, so a change to features.discord.webhooks can break features.skills, while a change to features.skills can't break features.discord.webhooks.
Position
Below the diagonal: features.skills uses a module listed above it, which is the healthy direction.
features.skills uses data.skyblockdata, so a change to data.skyblockdata can break features.skills, while a change to features.skills can't break data.skyblockdata.
Position
Below the diagonal: features.skills uses a module listed above it, which is the healthy direction.
data.cache uses data.cache.PetData, so a change to data.cache.PetData can break data.cache, while a change to data.cache can't break data.cache.PetData.
Position
Below the diagonal: data.cache uses a module listed above it, which is the healthy direction.
data.cache uses data.cache.VisitorLogbookData, so a change to data.cache.VisitorLogbookData can break data.cache, while a change to data.cache can't break data.cache.VisitorLogbookData.
Position
Below the diagonal: data.cache uses a module listed above it, which is the healthy direction.
features.gui.hud uses render.gui.components, so a change to render.gui.components can break features.gui.hud, while a change to features.gui.hud can't break render.gui.components.
Position
Below the diagonal: features.gui.hud uses a module listed above it, which is the healthy direction.
features.gui.hud uses events.minecraft, so a change to events.minecraft can break features.gui.hud, while a change to features.gui.hud can't break events.minecraft.
Position
Below the diagonal: features.gui.hud uses a module listed above it, which is the healthy direction.
features.gui.hud uses data.skyblockdata, so a change to data.skyblockdata can break features.gui.hud, while a change to features.gui.hud can't break data.skyblockdata.
Position
Below the diagonal: features.gui.hud uses a module listed above it, which is the healthy direction.
features.gui.hud uses features.items.rngdrop, so a change to features.items.rngdrop can break features.gui.hud, while a change to features.gui.hud can't break features.items.rngdrop.
Position
Below the diagonal: features.gui.hud uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 64.5 · Adequate · gated by X4 ·
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
8
High / Critical
Roadmap
Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; 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; Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md.
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.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Code Duplication: Edited copies of one member (3 members, 18+ corresponding lines)
How the grades work
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 9
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 — 105
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 — 120
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 14
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 40 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.7, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 40 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, 229 of 234 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.
D12 Dependency Hygiene — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 1 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Not scored — this repository's 1 Maven/Gradle manifest(s) were read and none of the dependency coordinates they declare carries a version resolvable from the manifest itself: every one is inherited from a parent POM, a <dependencyManagement> block, an imported BOM or a Gradle version reference the catalogue does not define. Licences are resolved from the POMs Maven Central publishes, which requires a version to ask about, and grading whichever release happens to be newest today would be a verdict about a dependency graph this repository has not pinned. NOT a finding that this repository's licences are compliant: this dimension asserts nothing about its licensing in either direction.
D16 Bus Factor — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. All 105 significant source file(s) were last meaningfully changed so long ago that no living knowledge remains — nothing since has been substantial enough to re-establish ownership (a broad, mechanical sweep that touches many files shallowly does not count, and neither does no activity at all). There is no concentration to measure, so the bus factor is not scored. This is not a clean bill: nobody currently holds working knowledge of this code (see D34 Knowledge Freshness). Counted over 105 of the 166 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
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 — 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is an ADMISSION gap, not an environment fault: it declares a published package (build.gradle.kts), but no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict.
D24 Comment Value — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
D26 Project Cohesion — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `(repository root)` (19592 LoC, 267 module-visible types across 60 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
D32 Data Compliance (PII/GDPR) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `src/main/kotlin/me/partlysanestudios/partlysaneskies/commands/PSSCommandRunnable.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/RequestRunnable.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/PetData.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/chat/ChatManager.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/chat/WordEditor.kt`, … (+2 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
D44 Platform End-of-Life — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
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.
ED5 Idempotency — 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 decides whether a handler's mutation is safe to re-run by recognising its persistence writes (a database save, a repository write, an event publish) and its guards. Those markers are .NET member names, so in this repository's language a write such as `repository.save(order)` is not recognised and a same-named call on an unrelated library type could be. The handlers were found; their idempotency was neither confirmed nor ruled out.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and this repository's Kotlin is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
P1 CI/CD gates — 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
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.
D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
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.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
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").
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
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.
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 ModChecker.run at 24. 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 StringUtils.colorCodeToColor at 17 — 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: src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/StringUtils.kt (StringUtils.colorCodeToColor at 17). They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
Bring the 5 bodies over 15 down to 15 or less in Cyclomatic Complexity — start with ModChecker.run (cyclomatic 24), PermPartyManager.registerCommand (cyclomatic 23), DebugKey.onDebugKeyPress (cyclomatic 19). — 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 9.1 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.
+ 13 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 18 bodies over 15 down to 15 or less in Cognitive Complexity — start with PermPartyManager.registerCommand (cognitive 53), ModChecker.run (cognitive 44), SkyblockPlayer.instantiateData (cognitive 42). — 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 18 together lifts Cognitive Complexity from 7.2 to about 10.0/10, projected with the scoring formula itself and assuming each lands exactly at 15.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes9.1 / 10Stronggated by 5 serious findings✓ 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 3 MethodTooLong finding(s) in God Classes — start with PartlySaneSkies.kt, PartyManagerGui.java, SkyblockPlayer.kt. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 1 ClassTooLong finding(s) in God Classes — start with PSSMainMenu.kt. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 FileTooLong finding(s) in God Classes — start with PSSMainMenu.kt. — One of this dimension's main actionable groups (1 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.
40 duplicated block group(s) detected. 8.5 % of the production lines (1,674 of 19,592) are in a reported copy. A further 23 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.
+ 47 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 3 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with RangeHighlight.kt, MainMenuOptionMenu.kt, ItemInformationBar.kt. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 3 Duplicated block (5 lines × 4) finding(s) in Code Duplication — start with RenderPrimitives.kt, CropMilestoneWebhook.kt, PartyMember.java. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Members sharing a duplicated core (4 members, 50+ identical tokens) finding(s) in Code Duplication — start with CrystalHollowsGemstoneMapper.kt, CropMilestoneWebhook.kt. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d4_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.
What it measures: How much of the code is actually exercised by tests.
Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
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.
6 deducted task-comment markers across 19592 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 6 TodoComment finding(s) in Explicit Debt — start with HealthAlert.kt, ExampleWebhook.kt, WordEditor.kt. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
0 of 1 documentation facets pass in full; short on: F2 example. 15 document(s) read across 1 unit(s).
Documentation: no build, run or usage exampleREADME.md:1
What to do
Resolve the 1 Documentation finding(s) in Documentation Quality — start with README.md. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d19_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
1 naming inconsistencies among 11 declarations measured against a convention their peers follow.
`obtainSkyCryptPlayerJSONData` spells `JSON` where 14 names in the project spell it `Json`src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/SkyCryptUtils.kt:39
What to do
Resolve the 1 `obtainSkyCryptPlayerJSONData` spells `JSON` where 14 names in the… finding(s) in Naming Consistency — start with SkyCryptUtils.kt. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d21_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.
62 % of calls cross a namespace and 1 % 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: Secret scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
8 finding(s): 0 critical, 7 high, 1 medium, 0 low. 5 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 1 file(s) — `gradlew` (line 72, line 177) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them.
REDACTED
REDACTED
REDACTED
REDACTED
What to do
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
No action in Static Analysis (SAST) — all 5 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (5 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
105 of 105 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is src/main/kotlin/me/partlysanestudios/partlysaneskies/config/OneConfigScreen.kt. Counted over 105 of the 166 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Most significant orphaned file · ×3src/main/kotlin/me/partlysanestudios/partlysaneskies/config/OneConfigScreen.kt:1
Dormant codebase
What to do
Resolve the 102 Orphaned file finding(s) in Knowledge Freshness — start with ProfitMinionCalculator.java, PartyMember.java, EndOfFarmNotifier.kt. — One of this dimension's main actionable groups (102 recommendation-level).
Resolve the 3 Most significant orphaned file finding(s) in Knowledge Freshness — start with OneConfigScreen.kt, PSSMainMenu.kt, PartlySaneSkies.kt. — One of this dimension's main actionable groups (3 recommendation-level).
Resolve the 1 Dormant codebase finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 3 Change coupling finding(s) in Change Coupling — start with PSSMainMenu.kt, ExampleWebhook.kt, PartlySaneSkies.kt. — One of this dimension's main actionable groups (3 warning-level).
Resolve the 2 Change-coupling hub finding(s) in Change Coupling — start with ScaledPixelConstraint.kt, ThemeManager.kt. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether the codebase has a recognisable, scale-appropriate structure (a named architectural style, or modular enough for its size) rather than being an ad-hoc ball of mud.
Method: Roslyn plus csproj analysis: architecture style detection (DDD, clean, vertical-slice, CQRS) and structure fitness for repo size. Deterministic.
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.
Other · Architecture — Whether feature slices stay independent (no direct cross-slice references) — the discipline that makes vertical-slice architecture pay off.
Method: Roslyn scan (vertical-slice gated): feature slices resolved from namespaces (.Features.*, .Slices.*) or project names; cross-slice type references detected. Deterministic, traceable.
`DropBannerDisplay` (slice 'gui') depends on `Drop` from slice 'items'. — src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/hud/DropBannerDisplay.kt:35
What to do
Keep slices independent: share cross-slice needs via an explicit contract/shared-kernel, not direct references between slices.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Do you agree with this assessment?
P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
What to do
Run the test suite in CI via an explicit runner step (`gradle test` for the toolchain this pipeline already uses) and gate merges on it.
Do you agree with this assessment?
P2 · Observability7.0 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
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 2 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:13
`build.gradle.kts` 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`. — build.gradle.kts:42
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.
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether 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. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
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.
`catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:114
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether log calls use message templates (queryable) rather than interpolated strings.
Method: Roslyn syntax scan: every log call-site counted; interpolated-string first-argument violations flagged. Population is all log calls, not estimated. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `trace`/`debug`/`info`/`warn`/`error`/`fatal`/`verbose`/`silly`/`http`/`log` call on a receiver named for a logger, in a package whose own or an enclosing `package.json` declares a logger that carries values as fields (pino, pino-http, nestjs-pino, Fastify, winston, bunyan, tslog, LogTape, roarr), whose first deciding argument is a template literal with substitutions; an object-literal fields argument is stepped over, a plain string message clears the call. Python is read the same way: a `debug`/`info`/`warning`/`error`/`exception`/`critical`/`log` call on a logger in a file that imports the standard library’s `logging` or structlog (loguru, which formats at the call, is not judged), whose message is a whole f-string with a non-constant field; a `%`-formatted, `.format()`-ed or concatenated message is not convicted, as in C#. PHP is read the same way: a PSR-3 level call (`emergency`…`debug`, `log`) on a logger (`$logger`, `$this->logger`, Laravel’s `Log::`, `logger()`, `\Drupal::logger()`) in a package whose `composer.json` requires a PSR-3 logger or a framework that hands one out (psr/log, Monolog, Laravel, Symfony, Drupal, CakePHP), or a file that imports one, whose message is a double-quoted string interpolating a variable; a single-quoted message clears the call, and `sprintf` or `.` concatenation is not convicted, as in C#. Dart is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on Sentry’s structured logger (`Sentry.logger`) whose message is a whole string literal interpolating a value (`$name`, `${…}`); the `Sentry.logger.fmt` template API clears the call. Dart that logs only through loggers with one message and no fields (package:logging, package:logger, talker, dart:developer) is not applicable rather than a reach gap. Ruby is read the same way: a `trace`/`debug`/`info`/`warn`/`error`/`fatal` call on the console gem’s `Console` (declared by a Gemfile, gemspec or Gemfile.lock, or required) or, where SemanticLogger, Ougai or dry-logger is declared or required, on a receiver named for a logger (`logger`, `@logger`, `Rails.logger`, `log`), whose first deciding argument is, as the whole argument, a double-quoted string interpolating a non-constant value (`#{…}`, `#@ivar`); a plain literal clears the call, keyword arguments are the fields, and a block, `%`-format or `+` concatenation is not convicted. Ruby that logs only through the standard Logger (Rails.logger) is not applicable rather than a reach gap. Deterministic.
`warn` at line 39 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/me/partlysanestudios/partlysaneskies/api/events/PSSEvents.kt:39
`warn` at line 42 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/me/partlysanestudios/partlysaneskies/api/events/PSSEvents.kt:42
`warn` at line 48 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text. — src/main/kotlin/me/partlysanestudios/partlysaneskies/api/events/PSSEvents.kt:48
Other · Code Health — Whether Kotlin's null safety is not undermined by not-null assertions — `String` cannot hold null and `String?` must be checked before use in every Kotlin module, and each `!!` is a run-time `NullPointerException` the author has told the compiler cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 3 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.
D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 3 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 1 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
P6 Release Hygiene — not evidenced — no changelog, version stamp or semver release tag in the repo
Not included — 69 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AX1 Captive dependencies — Not applicable: this repository's Java imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Kotlin imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean.
AX4 Dependency direction — not applicable to a vertical-slice architecture (the inward-dependency rule is for layered/clean styles)
AX8 Test isolation — no test/production split to check
AX9 CQS / query purity — no CQRS query handlers detected — query purity is not applicable to this codebase
AXB1 Runtime evidence locked — no reproducible boot — This repository has nothing the runtime tiers could boot or serve — no markup, no UI framework or web-server dependency, no UI component source, no native UI project and no API definition — nothing here is a surface to boot — so runtime a11y/egress/header evidence has no subject here. Not applicable: this is neither a gap in the scan nor a finding about your code.
C1 Data Protection — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no data at rest for these controls to protect.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C3 Audit Trail — No personal data detected in a persisted data model — no PII-named column (email, first_name, date_of_birth, phone_number, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no sensitive data whose changes an audit trail would record. If it does (through a store configured outside this repository, for instance), the trail belongs to wherever that data is stored.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named field (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a Room, JPA or MongoDB entity, an Exposed or Ktorm table, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (Room, Exposed, SQLDelight, Realm, JPA, JDBC, MongoDB, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
D12 Dependency Hygiene — Not scored — 1 Maven/Gradle manifest(s) were read, stating a version for 0 dependency(ies) and leaving 1 to a parent or an imported BOM, but no build resolved the dependency graph, so the outdated signal was not established. NOT a finding that these dependencies are current or healthy.
D14 License Compliance — JVM licences not graded — no declared coordinate carries a version the manifest itself resolves
D16 Bus Factor — dormant codebase — no living knowledge left to concentrate
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D20 ADR Quality — N/A — ADRs are expected on deployable products with a user-facing host, not consumed libraries; no ADR log is required here.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .java, .kt, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
D32 Data Compliance (PII/GDPR) — 7 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
D5 Coupling — Not applicable — this Gradle build ships 1 production module(s), so there is no coupling BETWEEN modules to measure. (Its test and non-production modules are not part of the shipped graph.)
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
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (18 value object(s))
ED1 Event-Driven — not scored — this repository shows only 1 of the 3 signals this lens looks for (1 event handler(s))
ED5 Idempotency — Not assessed, and this one is on us: 1 command handler(s) or message consumer(s) were found here, but this check does not yet recognise persistence writes in this repository's language. Idempotency was neither confirmed nor ruled out — this is a limit of the analyzer, not a finding about your code.
ES1 Event Sourcing — not scored — this repository shows only 1 of the 3 signals this lens looks for (an Axon event-sourcing framework (@Aggregate/@CommandHandler/@EventSourcingHandler annotations))
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JVM source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `@Benchmark` in a Java, Kotlin or Scala file importing JMH or kotlinx-benchmark, Jetpack Benchmark's `measureRepeated` in a file importing androidx.benchmark, or JMH/kotlinx-benchmark/androidx.benchmark in a pom.xml, Gradle or sbt build, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
PF3 Async & latency hygiene — Not applicable: this repository declares no async functions, so there is no asynchronous code for a blocking call to stall.
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
X1 Async correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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 and Kotlin were read, and no request in it can be cancelled by a caller (Ktor, OkHttp's newCall or a URL stream, from a suspend function) — a Java request off Android takes no token: it is cancelled through the handle it returns (Future.cancel, Call.cancel, a Disposable), ambiently (io.grpc.Context) or by interrupting its thread, not through a parameter; a Kotlin request outside a suspend function has no caller's cancellation to honour
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
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X24 Document value interpolated into markup unescaped — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
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.
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.
No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (JUnit (with Kotest or MockK on Kotlin)), and run it in CI so the gap cannot reopen.
TodoComment src/main/kotlin/me/partlysanestudios/partlysaneskies/features/dungeons/HealthAlert.kt:35— // TODO: do with regex — 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 src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/ExampleWebhook.kt:22— // TODO: Debug key event — 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 src/main/kotlin/me/partlysanestudios/partlysaneskies/features/chat/WordEditor.kt:26— // TODO change to map? — 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 src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/MinionData.java:300— // TODO: use repo — 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 src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManager.java:138— // TODO: reparty is no longer needed, might aswell remove it — 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 src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:279— // TODO: please for the love of god automate this whenever you rewrite this code — 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.
MethodTooLong: PartlySaneSkies.init src/main/kotlin/me/partlysanestudios/partlysaneskies/PartlySaneSkies.kt:190— MethodTooLong — init runs 154 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 54 over it, 1.54× 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: PartyManagerGui.createJoinFloorButtons src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:194— MethodTooLong — createJoinFloorButtons runs 132 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 32 over it, 1.32× 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: SkyblockPlayer.instantiateData src/main/kotlin/me/partlysanestudios/partlysaneskies/data/skyblockdata/SkyblockPlayer.kt:57— MethodTooLong — instantiateData 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.
Change coupling: PSSMainMenu.kt ↔ ElementaUtils.kt src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/mainmenu/PSSMainMenu.kt:1— `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/mainmenu/PSSMainMenu.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/ElementaUtils.kt` change together 62% of the time (13 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `0fe15ca3` Added text scale; `97d77ffe` Improved gui; `6933db6b` Revert "Revert "Revert "Revert "Revert "Revert "Revert "Revert "Custo… (at that commit the file was still `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/CustomMainMenu.kt`) — run `git show` on any of them.
Change coupling: ExampleWebhook.kt ↔ WebhookMenu.kt src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/ExampleWebhook.kt:1— `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/ExampleWebhook.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/discord/webhooks/WebhookMenu.kt` change together 55% of the time (6 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `902d7254` Added rng drop webhook; `7254bb4c` WebhookEvent -> Webhook + license comment; `7a13a716` Created the config editor in webhook gui — run `git show` on any of them.
Change coupling: PartlySaneSkies.kt ↔ ElementaUtils.kt src/main/kotlin/me/partlysanestudios/partlysaneskies/PartlySaneSkies.kt:1— `src/main/kotlin/me/partlysanestudios/partlysaneskies/PartlySaneSkies.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/ElementaUtils.kt` change together 52% of the time (11 of the 21 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `73ff8f39` Abstracted side bars and changed compost value to kotlin; `6933db6b` Revert "Revert "Revert "Revert "Revert "Revert "Revert "Revert "Custo…; `96c1472d` Revert "Revert "Revert "Revert "Revert "Revert "Revert "Custom Menu R… — run `git show` on any of them.
Duplicated block (9 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:61— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:61-69 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:79-87 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/mainmenu/MainMenuOptionMenu.kt:207— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/mainmenu/MainMenuOptionMenu.kt:207-215 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/mainmenu/PSSMainMenu.kt:623-631 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/ItemInformationBar.kt:85— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/ItemInformationBar.kt:85-93 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/MarketInformationBar.kt:153-161 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/ItemInformationBar.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/MarketInformationBar.kt` as WHOLE FILES: 87% 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.
Duplicated block (5 lines × 4) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:65— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:65-69 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:76-80 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:120-125 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:138-143 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:65` 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 (5 lines × 4) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:75— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:75-79 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt:74-78 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/PetLevelUpWebhook.kt:88-92 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/SkillUpgradeWebhook.kt:77-81 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:75` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 4) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:184— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:184-188 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:228-232 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:235-239 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:241-245 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:184` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Change-coupling hub: ScaledPixelConstraint.kt → PartlySaneSkies.kt, OneConfigScreen.kt, DebugKey.kt, ThemeManager.kt, ElementaUtils.kt src/main/kotlin/me/partlysanestudios/partlysaneskies/render/gui/constraints/ScaledPixelConstraint.kt— `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/gui/constraints/ScaledPixelConstraint.kt` changes together with 5 other files — `src/main/kotlin/me/partlysanestudios/partlysaneskies/PartlySaneSkies.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/config/OneConfigScreen.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/DebugKey.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/ElementaUtils.kt` — none of which declares a dependency on it: one file is the hub of 5 separate couplings, not 5 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 5.
Change-coupling hub: ThemeManager.kt → DebugKey.kt, PSSMainMenu.kt, ElementaUtils.kt src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt— `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt` changes together with 3 other files — `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/DebugKey.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/mainmenu/PSSMainMenu.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/ElementaUtils.kt` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (4 members, 50+ identical tokens) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:193— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:193-212 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:214-233 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:235-254 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/PercyMode.kt:127-147 — 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) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:81— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:81-114 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt:80-113 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryMilestoneWebhook.kt:89-122 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/SkillUpgradeWebhook.kt:83-117 — 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.
Duplicated block (10 lines × 3) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:194— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:194-203 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:215-224 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:236-245 — 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. Note first that the copies are not typed on the same thing: the declarations holding them bind `gemstones` to `List<Gemstone>` in one and `List<PrettyGemstone>` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (10 lines × 3) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:243— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:243-252 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:268-277 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:292-301 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:243` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (9–10 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:65— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:65-73 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:120-129 — 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 `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:65` 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–10 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:76— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:76-84 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:138-147 — 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 `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:76` 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 (7 lines × 3) src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt:126— src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt:126-132 | src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/PostRequest.kt:138-144 | src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/SystemUtils.kt:80-86 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/PostRequest.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:162— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:162-168 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:188-195 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:228-236 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:162` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:87— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:87-93 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:156-163 — 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 `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:87` 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 (7 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BeamRenderer.kt:45— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BeamRenderer.kt:45-51 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BlockHighlightRenderer.kt:56-62 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BeamRenderer.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BlockHighlightRenderer.kt` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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.
Duplicated block (8 lines × 3) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:72— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:72-79 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt:71-78 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/SkillUpgradeWebhook.kt:74-81 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:72` 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 × 3) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/PartyFriendManager.java:44— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/PartyFriendManager.java:44-51 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManager.java:148-155 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/permpartyselector/PermParty.java:40-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/PartyFriendManager.java:44` 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) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:67— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:67-71 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:82-86 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:191— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:191-195 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:207-211 — 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 `src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:191` 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.
ModChecker.run (cyclomatic 24) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:79— ModChecker.run 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.
PermPartyManager.registerCommand (cyclomatic 23) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/permpartyselector/PermPartyManager.java:77— PermPartyManager.registerCommand has cyclomatic complexity 23 (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.
DebugKey.onDebugKeyPress (cyclomatic 19) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/DebugKey.kt:59— DebugKey.onDebugKeyPress has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
Minion.getBaseItemsPerMinute (cyclomatic 19) src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/MinionData.java:145— Minion.getBaseItemsPerMinute has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ProfitMinionCalculator.getBestMinionSettings (cyclomatic 18) src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:474— ProfitMinionCalculator.getBestMinionSettings 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.
PermPartyManager.registerCommand (cognitive 53) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/permpartyselector/PermPartyManager.java:77— PermPartyManager.registerCommand has cognitive complexity 53 (threshold 15). Drivers by points: if/else 33 (50 pts), loops 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModChecker.run (cognitive 44) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:79— ModChecker.run has cognitive complexity 44 (threshold 15). Drivers by points: if/else 16 (28 pts), error handling 5 (11 pts), loops 4 (5 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SkyblockPlayer.instantiateData (cognitive 42) src/main/kotlin/me/partlysanestudios/partlysaneskies/data/skyblockdata/SkyblockPlayer.kt:57— SkyblockPlayer.instantiateData has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (24 pts), loops 6 (18 pts) (nesting depth added 27). 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.
ProfitMinionCalculator.getBestMinionSettings (cognitive 40) src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:474— ProfitMinionCalculator.getBestMinionSettings has cognitive complexity 40 (threshold 15). Drivers by points: if/else 7 (23 pts), loops 5 (11 pts), match/switch 1 (4 pts), boolean chains 2 (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiscordRPC.init (cognitive 28) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/discord/DiscordRPC.kt:26— DiscordRPC.init has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (18 pts), error handling 3 (9 pts), loops 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
GemstoneWaypointRender.onWaypointRenderEvent (cognitive 26) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/mining/crystalhollows/gemstonewaypoints/GemstoneWaypointRender.kt:20— GemstoneWaypointRender.onWaypointRenderEvent has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (16 pts), loops 4 (10 pts) (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.
AutoGG.onChat (cognitive 24) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/dungeons/AutoGG.kt:16— AutoGG.onChat has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (24 pts) (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.
CrystalHollowsGemstoneMapper.extractGemstone (cognitive 23) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:256— CrystalHollowsGemstoneMapper.extractGemstone has cognitive complexity 23 (threshold 15). Drivers by points: if/else 4 (16 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DiscordEmbedSerializer.serialize (cognitive 21) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/discord/webhooks/WebhookSerializer.kt:33— DiscordEmbedSerializer.serialize has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 3, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EndOfFarmNotifier.registerFarmNotifierCommand (cognitive 21) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/EndOfFarmNotifier.kt:308— EndOfFarmNotifier.registerFarmNotifierCommand has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (11 pts), error handling 3 (6 pts), boolean chains 4 (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.
Minion.getBaseItemsPerMinute (cognitive 21) src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/MinionData.java:145— Minion.getBaseItemsPerMinute has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (15 pts), boolean chains 4, loops 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DebugKey.onDebugKeyPress (cognitive 20) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/DebugKey.kt:59— DebugKey.onDebugKeyPress has cognitive complexity 20 (threshold 15). Drivers by points: if/else 19 (20 pts) (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
StringUtils.wrapText (cognitive 20) src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/StringUtils.kt:51— StringUtils.wrapText has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 5 (8 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.
ChatColors.getChatColor (cognitive 19) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/chat/ChatColors.kt:40— ChatColors.getChatColor has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (18 pts), match/switch 1 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
CooldownHud.onScreenRender (cognitive 19) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/hud/CooldownHud.kt:55— CooldownHud.onScreenRender has cognitive complexity 19 (threshold 15). Drivers by points: loops 6 (11 pts), if/else 6 (8 pts) (nesting depth added 7). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ThemeManager.tick (cognitive 18) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:51— ThemeManager.tick has cognitive complexity 18 (threshold 15). Drivers by points: error handling 3 (9 pts), loops 3 (6 pts), if/else 3 (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.
CrystalHollowsGemstoneMapper.getPrettyData (cognitive 17) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:78— CrystalHollowsGemstoneMapper.getPrettyData has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (8 pts), error handling 2 (6 pts), if/else 1 (3 pts) (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
MarketInformationBar.loadAuction (cognitive 16) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/MarketInformationBar.kt:77— MarketInformationBar.loadAuction has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ClassTooLong: PSSMainMenu src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/mainmenu/PSSMainMenu.kt:66— ClassTooLong — 460 significant lines (blank, comment-only and punctuation-only lines excluded), 6 methods. The bar is 400 significant lines; this is 60 over it, 1.15× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: mainmenu/PSSMainMenu.kt src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/mainmenu/PSSMainMenu.kt— FileTooLong — 518 significant lines (blank, comment-only and punctuation-only lines excluded), about 89% of them inside a single declaration: PSSMainMenu (66-641). The bar is 500 significant lines; this is 18 over it, 1.04× 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.
D4 · Code Duplication· Near-duplicate member family (4 members, 15 shared lines) · ×1
Near-duplicate member family (4 members, 15 shared lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:52— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:52-79 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt:52-78 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryMilestoneWebhook.kt:54-87 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/SkillUpgradeWebhook.kt:53-81 — These 4 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 21 shared lines) · ×1
Near-duplicate member family (3 members, 21 shared lines) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:109— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:109-170 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:194-341 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:437-488 — These 3 members are variants of one another: a block of 21 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
Near-duplicate member pair (25 shared lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:58— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:58-93 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:107-163 — These two members are variants of one another: 25 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (93 corresponding lines) · ×1
Edited copy of a member (93 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:114— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:114-206 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:208-321 — These two members are one piece of code written twice and then edited apart: 93 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (56 corresponding lines) · ×1
Edited copy of a member (56 corresponding lines) src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:191— src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:191-247 | src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:249-304 — These two members are one piece of code written twice and then edited apart: 56 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (103 corresponding lines) · ×1
Edited copy of a member (103 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt:49— src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt:49-151 | src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/PostRequest.kt:54-163 — These two members are one piece of code written twice and then edited apart: 103 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 (40 corresponding lines) · ×1
Edited copy of a member (40 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BeamRenderer.kt:23— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BeamRenderer.kt:23-62 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BlockHighlightRenderer.kt:24-72 — These two members are one piece of code written twice and then edited apart: 40 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×1
Edited copy of a member (18 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:174— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:174-191 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:202-219 — 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 (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/EndOfFarmNotifier.kt:240— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/EndOfFarmNotifier.kt:240-262 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/EndOfFarmNotifier.kt:264-286 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 22+ corresponding lines) · ×1
Edited copies of one member (3 members, 22+ corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:229— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:229-252 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:255-277 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:280-301 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 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 (19 corresponding lines) · ×1
Edited copy of a member (19 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/PetData.kt:56— src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/PetData.kt:56-74 | src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/VisitorLogbookData.kt:31-49 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/PartyFriendManager.java:40— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/PartyFriendManager.java:40-58 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManager.java:140-164 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/permpartyselector/PermParty.java:37-54 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×1
Edited copy of a member (28 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:89— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:89-116 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/VisitorTradeValue.kt:54-89 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:188— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:188-209 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:221-242 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:250-270 — 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 (21 corresponding lines) · ×1
Edited copy of a member (21 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/CategoriesBar.kt:121— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/CategoriesBar.kt:121-141 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/SettingsBar.kt:219-239 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×1
Edited copy of a member (17 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/BitsShopValue.kt:65— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/BitsShopValue.kt:65-83 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/SkymartValue.kt:56-72 — 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 (9 corresponding lines) · ×1
Edited copy of a member (9 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/SkyCryptUtils.kt:18— src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/SkyCryptUtils.kt:18-27 | src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/SkyCryptUtils.kt:29-37 — 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 (16 corresponding lines) · ×1
Edited copy of a member (16 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/PetData.kt:78— src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/PetData.kt:78-93 | src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/VisitorLogbookData.kt:53-68 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/StatsData.kt:32— src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/StatsData.kt:32-44 | src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/StatsData.kt:46-58 | src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/StatsData.kt:60-71 — 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 copy of a member (7 corresponding lines) · ×1
Edited copy of a member (7 corresponding lines) src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/PetData.kt:201— src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/PetData.kt:201-208 | src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/VisitorLogbookData.kt:139-145 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×1
Edited copy of a member (8 corresponding lines) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/permpartyselector/PermParty.java:73— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/permpartyselector/PermParty.java:73-80 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/permpartyselector/PermPartyManager.java:222-233 — 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 (37–38 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt:114— src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt:114-151 | src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/PostRequest.kt:127-163 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/PostRequest.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt:114` 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 (27 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt:56— src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt:56-82 | src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/PostRequest.kt:62-88 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/PostRequest.kt` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/GetRequest.kt: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 (20–21 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:129— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:129-149 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:221-240 — 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 (20 lines × 4) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:82— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:82-101 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt:81-100 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryMilestoneWebhook.kt:90-109 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/SkillUpgradeWebhook.kt:84-103 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:82` 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 (20 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderEuclid.kt:31— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderEuclid.kt:31-50 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderEuclid.kt:81-100 — 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 `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderEuclid.kt:31` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (16–18 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BeamRenderer.kt:24— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BeamRenderer.kt:24-39 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BlockHighlightRenderer.kt:25-42 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BeamRenderer.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/waypoint/BlockHighlightRenderer.kt` as WHOLE FILES: 87% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. 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. 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 (15 lines × 4) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:58— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:58-72 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt:57-71 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryMilestoneWebhook.kt:66-80 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/SkillUpgradeWebhook.kt:60-74 — before extracting anything, compare `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:58` 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 (14 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:193— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:193-206 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:226-239 — 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 `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt: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. 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 (12 lines × 3) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:114— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:114-125 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:132-143 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:150-161 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:114` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:162— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:162-172 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:189-199 — 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 `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:162` 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 (4–7 lines × 6) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:158— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:158-164 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:166-172 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:174-180 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:182-188 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:190-196 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:198-201 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. 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 (5 lines × 3) src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:65— src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:65-69 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:76-80 | src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:87-91 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:65` 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) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/CategoriesBar.kt:147— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/CategoriesBar.kt:147-154 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/SettingsBar.kt:245-252 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/sound/EnhancedSound.kt:66— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/sound/EnhancedSound.kt:66-77 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/sound/EnhancedSound.kt:90-101 — 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 `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/sound/EnhancedSound.kt:66` 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 (10 lines × 2) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/EndOfFarmNotifier.kt:327— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/EndOfFarmNotifier.kt:327-336 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/EndOfFarmNotifier.kt:352-362 — 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 `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/EndOfFarmNotifier.kt:327` 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 (10 lines × 4) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:197— src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:197-206 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:218-227 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:239-248 | src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/PercyMode.kt:130-139 — there are 4 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 4 sites; resolving a subset leaves the remainder to drift apart. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/PercyMode.kt:143` calls `GsonBuilder`, `setPrettyPrinting`, `create` and `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:209` 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 (18–19 lines × 2) src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:214— src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:214-231 | src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:270-288 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:214` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:232` calls `setWidth`, `PixelConstraint`, `getWidth` and `src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:289` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/PartyFriendManager.java:46— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/PartyFriendManager.java:46-58 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/permpartyselector/PermParty.java:42-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/PartyFriendManager.java:46` 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 (7 lines × 21) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:112— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:112-118 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:122-128 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:132-138 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:142-148 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:202-208 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:212-218 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:222-228 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:232-238 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:242-248 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:252-258 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:262-268 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:273-279 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:283-289 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:293-299 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:303-309 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:313-319 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:323-329 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:333-339 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:439-445 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:449-455 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:459-465 — there are 21 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 21 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:112` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 4) src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:388— src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:388-393 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:396-401 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:404-409 | src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:411-417 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:388` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:388` calls `setTextScale`, `TextScaledPixelConstraint` and `src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:411` does not — after which the two agree again for 5 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:109— src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:109-114 | src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:117-122 — 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 `src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:109` 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 (25 lines × 2) src/main/java/me/partlysanestudios/partlysaneskies/mixin/mods/MixinDungeonGuideCollectDiagnostics.java:1— src/main/java/me/partlysanestudios/partlysaneskies/mixin/mods/MixinDungeonGuideCollectDiagnostics.java:1-25 | src/main/java/me/partlysanestudios/partlysaneskies/mixin/mods/MixinEssentialsTelemetryManager.java:1-26 — 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 `src/main/java/me/partlysanestudios/partlysaneskies/mixin/mods/MixinDungeonGuideCollectDiagnostics.java:1` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. 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.
Swallowed exception (caught, then discarded) src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:114— `catch (e: Exception)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Orphaned file src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/ProfitMinionCalculator.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyMember.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/EndOfFarmNotifier.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManagerGui.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/security/modschecker/ModChecker.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/StringUtils.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/themes/ThemeManager.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/java/me/partlysanestudios/partlysaneskies/features/economy/minioncalculator/MinionData.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/permpartyselector/PermPartyManager.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/data/skyblockdata/SkyblockPlayer.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/items/rngdrop/RareDropGUI.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/endoffarmnotifer/RangeHighlight.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/discord/webhooks/WebhookMenu.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/CrystalHollowsGemstoneMapper.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/AuctionElement.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/CoinsToBoosterCookies.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/MinecraftUtils.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/java/me/partlysanestudios/partlysaneskies/features/dungeons/party/partymanager/PartyManager.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/SettingsBar.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CompostValue.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/VisitorTradeValue.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/dungeons/PlayerRating.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/economy/auctionhousemenu/AuctionHouseGui.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/debug/DebugKey.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/render/RenderPrimitives.kt:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
+ 77 more in this group — see findings.md.
D34 · Knowledge Freshness· Most significant orphaned file · ×3
Most significant orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/config/OneConfigScreen.kt:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/features/gui/mainmenu/PSSMainMenu.kt:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Most significant orphaned file src/main/kotlin/me/partlysanestudios/partlysaneskies/PartlySaneSkies.kt:1— One of the orphaned files carrying the most lost knowledge — ranked by size weighted by the file's role in the codebase, the same weighting behind the score above, so core code outranks equally large plumbing. A reasonable place to start a read-through before the aggregate risk above bites.
Duplicated predicate src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:74— `config.find("multipleOf10")?.asBoolean == true && newLevelInt % 10 == 0` appears character-identically in 4 files — src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt, src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt, src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryMilestoneWebhook.kt, src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/SkillUpgradeWebhook.kt. 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 src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:76— `config.find("multipleOf5")?.asBoolean == false && config.find("multipleOf10")?.asBoolean == false` appears character-identically in 4 files — src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt, src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt, src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryMilestoneWebhook.kt, src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/SkillUpgradeWebhook.kt. 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 src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt:72— `config.find("multipleOf5")?.asBoolean == true && newLevelInt % 5 == 0` appears character-identically in 4 files — src/main/kotlin/me/partlysanestudios/partlysaneskies/features/farming/garden/CropMilestoneWebhook.kt, src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryLevelUpWebhook.kt, src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/BestiaryMilestoneWebhook.kt, src/main/kotlin/me/partlysanestudios/partlysaneskies/features/skills/SkillUpgradeWebhook.kt. 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 src/main/kotlin/me/partlysanestudios/partlysaneskies/api/events/PSSEvents.kt:39— `warn` at line 39 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/kotlin/me/partlysanestudios/partlysaneskies/api/events/PSSEvents.kt:42— `warn` at line 42 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Interpolated log message defeats structured logging src/main/kotlin/me/partlysanestudios/partlysaneskies/api/events/PSSEvents.kt:48— `warn` at line 48 is handed a message assembled at the call — a string template with `$…` values in it, a concatenation or `String.format` — through SLF4J, log4j 2 or kotlin-logging, so the logger receives one finished string: the values in it cannot be queried, filtered or aggregated as fields, every occurrence reads as a different message, and the string is built even when the level is filtered out. Pass a constant pattern and the values beside it instead: `log.warn("Order {} moved to {}", orderId, status)`, which keeps the pattern and its arguments apart on the event for a structured encoder (logstash-logback-encoder, log4j 2's JsonTemplateLayout, OpenTelemetry), or with kotlin-logging `logger.atInfo { message = "Order moved"; payload = mapOf("order_id" to orderId, "status" to status) }`. An exception goes last, as the throwable argument, not into the text.
Documentation: no build, run or usage example README.md:1— the repository holds project manifests and neither `README.md` nor the documents it links hold a code block or a command. Show the command that builds or runs it, or a usage snippet.
D21 · Naming Consistency· `obtainSkyCryptPlayerJSONData` spells `JSON` where 14 names in the project spell it `Json` · ×1
`obtainSkyCryptPlayerJSONData` spells `JSON` where 14 names in the project spell it `Json` src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/SkyCryptUtils.kt:39— 14 of 15 names in project repository spell the token `Json` (14 of 15; unit: names in project repository containing `Json`). Peers: PartlySaneSkies.loadMainMenuJson (src/main/kotlin/me/partlysanestudios/partlysaneskies/PartlySaneSkies.kt:404); Config.loadFromJson (src/main/kotlin/me/partlysanestudios/partlysaneskies/config/psconfig/Config.kt:60); Config.saveToJson (src/main/kotlin/me/partlysanestudios/partlysaneskies/config/psconfig/Config.kt:77); ConfigOption.loadFromJson (src/main/kotlin/me/partlysanestudios/partlysaneskies/config/psconfig/ConfigOption.kt:11); ConfigOption.saveToJson (src/main/kotlin/me/partlysanestudios/partlysaneskies/config/psconfig/ConfigOption.kt:13). Rename to `obtainSkyCryptPlayerJsonData`. [rule N6]
Dormant codebase — 105 of 105 significant files have no living knowledge — the codebase as a whole is dormant, not 105 separate risks. Counted over 105 of the 166 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over. Re-engage owners or document before change.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
M2 · Architecture documentation· No architecture diagram/doc · ×1
No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
No SAST REDACTED:13— 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 2 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 build.gradle.kts:42— `build.gradle.kts` 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`.
Silent fallback default on parse failure src/main/kotlin/me/partlysanestudios/partlysaneskies/utils/HypixelUtils.kt:66— `getBits` answers `0` when `NumberFormatException` is thrown, with no log or throw — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment in the catch or in the KDoc, and the row stops firing.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that. semgrep could not parse 7 file(s) — `src/main/kotlin/me/partlysanestudios/partlysaneskies/commands/PSSCommandRunnable.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/api/RequestRunnable.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/data/cache/PetData.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/chat/ChatManager.kt`, `src/main/kotlin/me/partlysanestudios/partlysaneskies/features/chat/WordEditor.kt`, … (+2 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
none (dependency manifest found, not scanned for vulnerabilities here)
—
none (dependency manifest found, not scanned for vulnerabilities here): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Gradle build (build.gradle/build.gradle.kts) — not scanned yet).
0
—
Run 01a1e7d9-694f-7b56-be87-ed6274af8109 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 9 · Warnings: 105 · Recommendations: 120 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 17-11-2026 @ 04:52 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.